New energy vehicle hardware-in-the-loop function verification cloud platform system and method

Abstract

The invention discloses a new energy vehicle hardware-in-the-loop function verification cloud platform system. The system comprises a remote test management module used for generating a task allocation instruction according to a submitted hardware-in-the-loop test task; the hardware intelligent allocation module is used for creating a test schedule database based on the state information of all the test cabinets and the upper computer, and allocating resources required by the current test according to a task allocation instruction and an operation time sequence table; the cloud test module is used for constructing a test environment and establishing a test case; and the test case sharing module is used for matching task identification fields for the first time, adding reference identifiers when the test cases are reused subsequently, and scoring to generate recommendation results. The problems that equipment, a test environment and test cases cannot be shared and the test management efficiency is low in an existing hardware-in-the-loop test are solved, intelligent resource allocation, test case reuse and remote management are integrated through the cloud platform, cross-regional resource sharing and unified scheduling are achieved, the test efficiency and the hardware utilization rate are remarkably improved, and the new energy vehicle development period is shortened.

Description

Technical Field

[0001] The technical field of this invention is the intersection of automotive electronics testing and cloud computing, specifically referring to a cloud platform system and method for hardware-in-the-loop functional verification of new energy vehicles. Background Technology

[0002] With the continuous shortening of the development cycle of new energy vehicles, simulation testing for new energy vehicles has been widely used in the industry. Currently, hardware-in-the-loop simulation testing technology is widely used in the field of new energy vehicle development. This technology mostly connects the real controller and the virtual vehicle model through a real-time processor to form a closed-loop "controller-simulator" system.

[0003] In existing technologies, autonomous driving simulation hardware can be shared through a cloud platform, with the platform management module forwarding control commands and feedback information in real time. The core of this approach is to enable remote access to physical hardware by multiple users. For example, testers in different regions can apply to use specified hardware-in-the-loop devices through the cloud platform. However, this solution cannot achieve cross-project reuse of test environments (such as rack configuration and communication protocols). The environment needs to be rebuilt for each test, and there is a lack of collaborative management mechanisms for test cases. Test cases developed by different teams form information silos. In existing technologies, resource management can also be achieved through physically isolated availability domains (such as autonomous driving domains and infrastructure domains) and cloud management platforms, which optimizes the deployment efficiency of IaaS (Infrastructure as a Service) / PaaS (Platform as a Service) and reduces the cost of multi-domain resource management. However, this solution focuses on general cloud service management and does not design a dedicated architecture for the special needs of hardware-in-the-loop testing (such as real-time requirements and device heterogeneity). Furthermore, it lacks support for core functions such as intelligent allocation of test devices and sharing of test cases, and cannot solve the efficiency bottleneck of hardware-in-the-loop testing.

[0004] To address the aforementioned shortcomings, a cloud platform system for hardware-in-the-loop functional verification of new energy vehicles is invented. By establishing a hardware channel resource identification table, it enables rapid cross-rack migration of the test environment. Based on multi-dimensional tags (controller model / functional level) and a dynamic scoring mechanism, it achieves intelligent recommendation of test cases. Combined with the equipment operation table (including idle period prediction and fault migration marking) and task priority algorithm, it resolves conflicts between multiple projects. It also has a problem indexing mechanism layered by controller functional domain, supporting real-time collaborative processing of technical issues. Summary of the Invention

[0005] The purpose of this invention is to provide a cloud platform system and method for hardware-in-the-loop functional verification of new energy vehicles. This invention can solve the problems of traditional hardware-in-the-loop testing equipment being scattered in laboratories in various locations, making it impossible for remote teams to share physical equipment, test environment configurations, and test case libraries. Furthermore, the process from task allocation to report generation relies on manual coordination, lacking automated scheduling mechanisms and standardized management, which leads to redundant development.

[0006] To achieve this objective, the present invention provides a cloud platform system for hardware-in-the-loop functional verification of new energy vehicles, comprising: The remote test management module is used to generate task allocation instructions based on the submitted hardware-in-the-loop test tasks; The hardware intelligent allocation module is used to create a test schedule database based on the status information of all test racks and all host computers required for hardware-in-the-loop testing. The test schedule database contains runtime sequence tables for all test racks and all host computers. Based on the task allocation instruction and the runtime sequence tables, the module selects the test racks and host computers required for the current hardware-in-the-loop test from all test racks and all host computers. The cloud-based testing module is used to build a test environment based on the test rack and host computer required for current hardware-in-the-loop testing. The test environment is combined with task allocation instructions to create test cases. The test case sharing module is used to match test cases with the task identifier field in the task assignment instruction when test cases are first created. When test cases are reused in subsequent tests, a reference identifier is added to the test cases according to the task identifier field. After each test case is reused, the reference identifier of the reused test case is used to score the reused test case, and a test case recommendation result is generated based on the scores of all reused test cases.

[0007] Preferably, it also includes a problem sharing module for building a multi-level directory, establishing a hardware-in-the-loop test problem index based on the multi-level directory, and each hardware-in-the-loop test problem index has a corresponding solution. A certain solution corresponds to one or more hardware-in-the-loop test problem indexes. The hardware-in-the-loop test problem indexes and corresponding solutions are stored in the cloud expert database to obtain an expert Q&A system. The expert Q&A system scores a solution based on the number of times the corresponding question index is used in that solution, and generates a solution recommendation result based on the scores of all solutions.

[0008] Preferably, the multi-level directory includes a first-level domain directory for classification according to controller type, a second-level directory of controller functions created based on the first-level domain directory, a third-level directory of controller function failure issues associated with the second-level directory of controller functions, and a hardware-in-the-loop test issue index generated by the issue sharing module based on the selected third-level directory path of the controller function failure issue.

[0009] Preferably, the remote test management module is used to mark whether each tested test case has passed or failed during the hardware-in-the-loop testing process based on the test case recommendation results, and to generate the real-time progress of the hardware-in-the-loop testing based on the ratio of the number of marked test cases to the total number of test cases.

[0010] Preferably, the remote test management module generates a test report after the test is completed; Before the test report is generated, if a hardware-in-the-loop test problem index is received, the problem sharing module obtains the corresponding solution based on the solution recommendation results corresponding to the hardware-in-the-loop test problem index.

[0011] Preferably, the remote test management module assigns different permissions to different user types, including project requirement users, testers, and system administrators; The user requesting the project is the one proposing the test and has the authority to propose the test task. The system administrator has the authority to decide whether to accept the test task. If the system administrator accepts the test task, the system administrator will assign the test task to the corresponding tester to perform hardware-in-the-loop testing.

[0012] Preferably, the specific steps for testers to conduct the test are as follows: Testers log into the cloud platform system and accept the test tasks assigned by the system. The hardware intelligent allocation module allocates test racks and host computer resources for the test tasks and switches the set number of test racks according to the runtime sequence table of all test racks and host computers in the test schedule database. If it is necessary to reuse the test environment and corresponding test cases, the reused test environment is modified as needed to complete the test environment setup. Then, the reused test cases are modified as needed to complete the establishment of the test case library. During the hardware-in-the-loop testing process based on the test case recommendation results, each tested test case is marked as having passed or failed. The real-time progress of the hardware-in-the-loop testing is generated based on the ratio of the number of marked test cases to the total number of test cases. After the test is completed, a test report is generated for the testers to view and modify. The testers modify it as needed and then send the final test report to the project users via cloud computer to complete one round of testing. The above testing process is repeated until the test is completed.

[0013] Preferably, the hardware intelligent allocation module allocates a host computer and a test cabinet to the current hardware-in-the-loop test according to the status information of all test cabinets and all host computers based on the task allocation instructions. At this time, the host computer and the test cabinet can cover the current hardware-in-the-loop test, and both the host computer and the test cabinet are in an idle period. If the host computer and test cabinet cannot cover the hardware-in-the-loop test, but multiple test cabinets and multiple test host computers working together can meet the test requirements, or one test cabinet and multiple test host computers working together can meet the test requirements, or multiple test cabinets and one test host computer working together can meet the test requirements, and both the host computer and test cabinet are in a downtime, then the cloud computer will mark the host computer and test cabinet used, and mark the usage time of the host computer and test cabinet used, and put the markings of the host computer and test cabinet used and the usage time markings of the host computer and test cabinet used into the runtime sequence table.

[0014] The present invention discloses a cloud platform method for hardware-in-the-loop functional verification of new energy vehicles, which includes: Generate task allocation instructions based on the submitted hardware-in-the-loop test tasks; A test scheduling database is created based on the status information of all test racks and all host computers required for hardware-in-the-loop testing. The test scheduling database contains runtime sequence tables for all test racks and all host computers. Based on the task allocation instruction and the runtime sequence tables, the test racks and host computers required for the current hardware-in-the-loop test are selected from all test racks and all host computers. The test environment is built based on the test rack and host computer required for current hardware-in-the-loop testing. Test cases are then created in the test environment in conjunction with task allocation instructions. When a test case is created for the first time, the cloud computer matches the test case according to the task identifier field in the task allocation instruction; when a test case is reused in a subsequent test case, a reference identifier is added to the test case according to the task identifier field; after each test case is reused, the reference identifier of the reused test case is used to score the reused test case, and a test case recommendation result is generated based on the scores of all reused test cases.

[0015] The present invention provides a computer program product, comprising a computer program that, when executed by a processor, implements the steps of a cloud platform method for hardware-in-the-loop functional verification of new energy vehicles.

[0016] The beneficial effects of this invention are as follows: This invention proposes a cloud platform system for hardware-in-the-loop functional verification of new energy vehicles. Through a cloud-based testing module, it achieves cloud-based deployment of hardware-in-the-loop testing, breaking through the geographical limitations of traditional local testing and allowing users in different locations to log in and conduct remote testing via cloud computers. The system automatically allocates host computers and test cabinets according to user permissions and supports rapid portability of test environments. Seamless matching of test environments is achieved through a cabinet hardware channel resource identifier table, significantly improving testing flexibility and scalability. Through a test case sharing module, a task identifier field (including the controller under test, software version, and functional level) is added when a test case is first created. Subsequent reuse is accompanied by a reference identifier (such as the referenced target controller and the number of references). Test cases are scored and ranked based on the number of references and the number of referenced controller types, generating recommended test case results. Through a problem sharing module, a multi-level directory is constructed (including a controller type first-level domain directory, a functional second-level directory, and a fault problem third-level directory). A hardware-in-the-loop test problem index is generated based on the directory path, with each index associated with a solution. The system scores and ranks solutions based on their usage frequency, generating recommended solution results and providing real-time expert-level guidance, effectively shortening the problem-solving cycle and reducing the risk of test interruption. The system utilizes a hardware intelligent allocation module to create a test scheduling database and runtime sequence table, and monitors the status of all test racks and host computers in real time. Based on task allocation instructions and the status of idle devices, the system intelligently allocates resources, prioritizing idle racks or combining multiple devices to meet testing needs, optimizing hardware utilization and reducing device idle time. A remote test management module assigns permissions to different user types (project requirement users, testers, system administrators) to enable the approval, allocation, and monitoring of test tasks. The system displays the pass / fail status of test cases in real time, calculates progress percentages, generates test reports, and automatically retains historical data based on task orders and user information. This invention, by integrating a cloud-based testing module, a test case sharing module, a problem sharing module, a hardware intelligent allocation module, and a remote test management module, achieves cloud-based management of hardware-in-the-loop testing, solving the problems of unshared device resources, low testing efficiency, and geographical limitations in existing technologies. Attached Figure Description

[0017] Figure 1 This is a schematic diagram of the structure of the present invention; Figure 2 This is a schematic diagram of the cloud testing process of the present invention. Detailed Implementation

[0018] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of the present invention, not all of them. Therefore, the following detailed description of the embodiments of the present invention provided in the accompanying drawings is not intended to limit the scope of the claimed invention, but merely to represent selected embodiments of the invention. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without inventive effort are within the scope of protection of the present invention.

[0019] The present invention will be further described in detail below with reference to the accompanying drawings and specific embodiments: Example 1 A cloud platform system for hardware-in-the-loop functional verification of new energy vehicles, such as Figure 1 As shown, it includes: The remote test management module is used to generate task allocation instructions based on the submitted hardware-in-the-loop test tasks; The hardware intelligent allocation module is used to create a test schedule database based on the status information of all test racks and all host computers required for hardware-in-the-loop testing. The test schedule database contains runtime sequence tables for all test racks and all host computers. Based on the task allocation instruction and the runtime sequence tables, the module selects the test racks and host computers required for the current hardware-in-the-loop test from all test racks and all host computers. The cloud-based testing module is used to build a test environment based on the test rack and host computer required for current hardware-in-the-loop testing. The test environment is combined with task allocation instructions to create test cases. The test case sharing module is used to match test cases with the task identifier field in the task allocation instruction when test cases are first created. When test cases are reused in subsequent tests, a reference identifier is added to the test cases according to the task identifier field. After each test case is reused, the reference identifier of the reused test case is used to score the reused test case. Based on the scores of all reused test cases, a test case recommendation result is generated, and the recommended test cases are selected for testing.

[0020] In the above technical solution, the test cabinet includes cabinets for different controllers, such as vehicle controller cabinets and motor controller cabinets. The host computer functions include: 1. setting up the software environment and connecting it to the test cabinet; 2. controlling the host computer to simulate and send signals for the controller to receive; 3. controlling the host computer to receive signals from the controller under test.

[0021] In some preferred embodiments of the present invention, when performing hardware-in-the-loop testing, the test object is the controller on a new energy vehicle, such as the vehicle controller, motor controller and battery controller.

[0022] For hardware-in-the-loop cloud testing, its purpose is to place all local devices in the cloud for testing and management. Both local and remote testing users can connect to the cloud computer via network cable. After a user successfully logs in through the interface to the cloud computer, the cloud computer identifies and assigns permissions to the logged-in user based on the cloud user permission table. The system allocates host computers and server racks according to user permissions for testing. Test case projects are created on the host computer, then downloaded to the server rack for testing. The results are then fed back from the server rack to the host computer. Users can then perform tests via their computers through the cloud computer. For example: Figure 2 As shown, the remote test management module is managed using a cloud customer management system. The device allocation table is used for allocating rack resources, and the device operation table is the runtime sequence table. Customers 1, 2, to N are all users with project requirements. The expert sharing library, or cloud-based expert library, is used to store hardware-in-the-loop test problem indexes and corresponding solutions. When Customer 1 logs in, their permissions allow access to Host Computer 1 and 2, as well as Test Rack 1. Customer 1 can only see Host Computer 1 and 2 through the cloud computer. Customer 1's computer will then connect to Host Computer 1 and 2 via the cloud computer, creating test projects on Host Computer 1 and 2 and downloading them to Test Rack 1. The results from Test Rack 1 are fed back to Host Computer 1 and 2, and Customer 1 can view the test results on the client side via the cloud computer.

[0023] Regarding the mapping relationship between the controller under test model, test function, and rack number, some optimized technical solutions include: after the hardware intelligent allocation module allocates test equipment, adding an index column to the information of the controller under test model, the test case library corresponding to the problem sharing module, and the equipment number, indicating that this resource is currently conducting an experiment collaboratively.

[0024] For test cases, a test case library is established based on different test functions. Some optimized technical solutions include: when a user performs a test for the first time and creates a test project on the host computer, a test case library is created based on different test functions. This test case library is stored on the host computer. The test cases in the test case library are marked with fields. When it is first created, it has: the controller under test, the software version, the first-level function of the controller under test, and the second-level function of the controller under test. Only when the test case is referenced by other test cases will the following be added: the referenced first-level function of the target controller, the referenced second-level function of the target controller, the referenced target controller, and the number of references. When a user creates a test case for the first time, the test case is saved on the host computer used that time, and also on the cloud computer's hard drive. This test case identifies the controller under test, the software version, the primary function of the controller under test, and the secondary function of the controller under test. All test cases and identifiers are stored on the cloud computer's hard drive. When the user conducts a test again, or when another user performs a test, they can search for test cases related to the controller, software version, or function based on the test case identifiers through the cloud computer, and reuse them to achieve sharing. At the same time, this or multiple shared test cases on the cloud computer's hard drive are identified by the reference to the primary function of the target controller, the reference to the secondary function of the target controller, the reference to the target controller, and the number of references, serving as a record of the original test case being referenced. Simultaneously, the cloud computing machine will categorize and statistically analyze the number of times test cases are referenced, the controller types referenced, and the relevant primary functions of the target controller referenced. For each difference in the number of references, controller types, or relevant primary functions of the target controller, 1 point is awarded. The higher the score of a test case, the higher its generality. Therefore, test cases will be sorted in the cloud computer's test case library from highest to lowest score to facilitate faster retrieval of reusable test cases in the future. The specific calculation formula is: Score = α × Number of References + β × Number of Controller Types, where α is the weighting coefficient for the number of test case references, and β is the weighting coefficient for the number of controller types. For example: User 1 conducts their first test, creating Test Case Library 1 on host computer 1, and recording the controller under test, software version, primary functions of the controller under test, and secondary functions of the controller under test, and storing this information on the cloud computer's hard drive, denoted as "Test Case Library Cloud-1". When using host computer 2 for the second time, since it tests the same type of controller as before and wants to share the previous test case library, it can retrieve test cases based on the identifiers in the previous test case library and move them to host computer 2. Simultaneously, the cloud computer will automatically mark the moved, shared, and reused test cases with the following tags: referencing primary functions related to the target controller, referencing secondary functions related to the target controller, referencing the target controller, and the number of references. The cloud computer will then sort the test cases in its test case library based on their scores and update "Test Case Library Cloud-1." At the same time, the newly generated test case library will be stored on the cloud computer's hard drive, forming "Test Case Library Cloud-2."

[0025] In the above technical solution, the test functions include, for example, testing the vehicle's high voltage, vehicle torque output, vehicle thermal management, vehicle insulation, and vehicle fault triggering functions.

[0026] In the above technical solution, a remote test management module is designed to coordinate the test process by assigning task instructions, ensuring the orderly execution of tasks; the intelligent hardware allocation module dynamically schedules test cabinets and host computers based on runtime sequence tables, solving the problems of geographical limitations and idle hardware resources; the cloud test module builds the test environment and generates test cases, while the test case sharing module automatically recommends highly reusable test cases through reference identification and scoring mechanisms (reference count + controller type number weight), significantly improving test efficiency and realizing global scheduling of hardware resources and intelligent reuse of test cases.

[0027] The above technical solution also includes a problem sharing module for building a multi-level directory, establishing a hardware-in-the-loop test problem index based on the multi-level directory, and each hardware-in-the-loop test problem index has a corresponding solution. A certain solution corresponds to one or more hardware-in-the-loop test problem indexes. The hardware-in-the-loop test problem indexes and corresponding solutions are stored in the cloud expert database to obtain an expert Q&A system. The expert Q&A system scores a solution based on the number of times the corresponding question index is used in that solution, and generates a solution recommendation result based on the scores of all solutions.

[0028] The above technical solution incorporates a problem-sharing module to construct a multi-level expert Q&A system (controller type + function + fault). Its purpose is to address real-time technical obstacles during testing, achieving accurate matching of frequently asked questions by indexing and associating solutions and ranking them based on usage frequency. The design, independent of the test case library, ensures that the expert database focuses on technical guidance, enhancing the system's modularity.

[0029] In the above technical solution, the multi-level directory includes a first-level domain directory for dividing according to controller type, a second-level directory of controller functions created based on the first-level domain directory, a third-level directory of controller function failure issues associated with the second-level directory of controller functions, and a hardware-in-the-loop test issue index generated by the issue sharing module according to the selected third-level directory path of the controller function failure issue.

[0030] For the expert Q&A system, i.e., the cloud-based expert shared library, which resides in the cloud computer, some optimized technical solutions include: real-time sharing of Q&A in the cloud-based expert shared library, categorized by locally testable controller types, with question titles containing: controller name + primary function + secondary function, establishing a question index with attached solutions, each index corresponding to one solution, and storing it in the cloud-based expert library. Users are granted real-time Q&A entry permissions; after entry, authorization is granted by the cloud before formally entering the cloud-based expert library system to provide answers. When a user needs to ask a question, the system prompts them to enter the question title "controller name + primary function + secondary function." Each time a user indexes a question, one point is added to each solution deemed useful by the user. Question statistics are implemented, and questions are sorted in the cloud system according to their scores, with systems that have answered user questions most frequently appearing given priority. The specific formula is: Score = γ × number of citations in the past month × number of citations in the past three months, where γ is the weighting coefficient for the number of times a solution is cited.

[0031] For question-answering systems, some optimized technical solutions include: First, the question-answering system allows users to select which domain the question belongs to, such as driving, braking, or environment. If necessary, users can also choose not to select which domain the question belongs to. Then, users can enter keywords, such as vehicle controller. Based on this keyword, the system will search for questions with this keyword in the relevant system.

[0032] In the above technical solution, the remote test management module is used to mark whether each tested test case has passed or not during the hardware-in-the-loop testing process based on the test case recommendation results, and to generate the real-time progress of the hardware-in-the-loop testing based on the ratio of the number of marked test cases to the total number of test cases.

[0033] In the above technical solution, after the test is completed, the remote test management module generates a test report based on the test task sheet, the pass status of the test case library, the target user, the test user, and the system time obtained during the test. The test user can view and modify the report. After modification, the test user sends the final test report to the project user via the cloud computer, thus completing one round of testing. Before the test report is generated, if a hardware-in-the-loop test problem index is received, the problem sharing module obtains the corresponding solution based on the solution recommendation results corresponding to the hardware-in-the-loop test problem index.

[0034] Regarding test reports, some optimized technical solutions include: when the test report is officially sent to the project users, the test report and test tasks are jointly stored on the cloud computer as statistics for the number of future tests.

[0035] In the above technical solution, real-time progress is generated by identifying the pass rate of test cases, allowing project stakeholders to transparently track task status; before generating test reports, an expert database solution is invoked to ensure report accuracy, collaboratively achieving closed-loop management of the entire test lifecycle and avoiding process interruptions due to unforeseen problems.

[0036] In the above technical solution, the remote test management module assigns different permissions to different user types, including project requirement users, testers, and system administrators. The user requesting the project is the one proposing the test and has the authority to propose the test task. The system administrator has the authority to decide whether to accept the test task. If the system administrator accepts the test task, the system administrator will assign the test task to the corresponding tester to perform hardware-in-the-loop testing. If the system administrator does not accept the test task, the project will stop running.

[0037] In some preferred embodiments of this invention, the specific steps for testing by the tester are as follows: Testers log into the cloud platform system and accept the test tasks assigned by the system. The hardware intelligent allocation module allocates test racks and host computer resources for the test tasks and switches between a set number (two or more) of test racks based on the runtime sequence table of all test racks and host computers in the test schedule database. If it is necessary to reuse the test environment and corresponding test cases, the reused test environment is modified as needed to complete the test environment setup. Then, the reused test cases are modified as needed to complete the establishment of the test case library. During the hardware-in-the-loop testing process based on the test case recommendation results, each tested test case is marked as having passed or failed. The real-time progress of the hardware-in-the-loop testing is generated based on the ratio of the number of marked test cases to the total number of test cases. After the test is completed, a test report is generated for the testers to view and modify. The testers modify it as needed and then send the final test report to the project users via cloud computer to complete one round of testing. The above testing process is repeated until the test is completed.

[0038] For setting up a test environment, some optimized technical solutions include: The test environment can be set up using the following methods: 1. Build a test environment using software and hardware resources; 2. Build a test environment based on the dynamic model, vehicle environment model, driver model, etc., of the simulated external environment of the controller under test.

[0039] For communication between the cloud testing module and the hardware allocation module, some optimized technical solutions include: after the intelligent hardware allocation module allocates the resources needed for the experiment, it will "inform" the cloud testing module. After the cloud testing module allocates the experimental tasks, it will also poll (referring to the data communication mechanism where the host computer actively queries the status of the test cabinet and controller at fixed intervals) the hardware allocation module at set intervals to see if the hardware resources have been allocated.

[0040] In the above technical solution, by clearly defining the user permission hierarchy and test task execution process, the system administrator's task allocation mechanism ensures the authority of resource scheduling and reduces the risk of conflict; when reusing the environment, corrections are made, and combined with test case reuse, it is beneficial to significantly shorten the preparation cycle; the dynamic modification mechanism of test reports is beneficial to improve delivery flexibility.

[0041] In the above technical solution, the hardware intelligent allocation module allocates a host computer and a test cabinet to the current hardware-in-the-loop test according to the status information of all test cabinets and all host computers based on the task allocation instructions. At this time, the host computer and the test cabinet can cover the current hardware-in-the-loop test, and both the host computer and the test cabinet are in the off period. If the host computer and test cabinet cannot cover the hardware-in-the-loop test, but multiple test cabinets and multiple test host computers working together can meet the test requirements, or one test cabinet and multiple test host computers working together can meet the test requirements, or multiple test cabinets and one test host computer working together can meet the test requirements, and both the host computer and test cabinet are in a downtime, then the cloud computer will mark the host computer and test cabinet used, and mark the usage time of the host computer and test cabinet used, and put the markings of the host computer and test cabinet used and the usage time markings of the host computer and test cabinet used into the runtime sequence table. For example, when using the first test rack, the host computer downloads the software testing environment to the first test rack and puts the runtime sequence table of the first test rack into the cloud computer. When the first rack has a next test task, but the current test process has not yet been completed, the second test rack is arranged according to the runtime sequence table of the test work in the cloud computer. At this time, it is necessary to match the software of the host computer's test environment with the second rack and share the test environment according to the cloud test allocation principle.

[0042] To address rack failures, some optimized technical solutions include: When a rack fails, the hardware allocation module polls to check if any device is conducting an experiment. If the failure prevents the experiment from proceeding, it sends a message to the cloud testing module. The cloud testing module pauses the experiment and marks a breakpoint. The hardware allocation module then re-allocates resources and informs the cloud testing module again to confirm that hardware resources have been allocated. Once resources are allocated, the cloud testing module resumes the experiment from the previous breakpoint.

[0043] Regarding the conflict resolution process during allocation, some optimized technical solutions include: when a project needs test resources, the remote test management module first assigns the test task to a level. The highest-level test has the highest priority when applying for rack space at the same time and will not be preempted; when test tasks of the same level apply at the same time, they will be allocated according to the order in which the application signals are triggered.

[0044] To address downtime, some optimized technical solutions include: Downtime calculation is based on historical data, such as the total number of tests conducted in the previous year and the number of tests conducted in each domain (new energy domain), to predict downtime during equipment operation. These conditions (i.e., the downtime included in different predicted devices) are weighted. For example, when testing the vehicle controller, the downtime of the vehicle controller itself can be compared, and if the result is 60% of the total downtime, the downtime of devices interoperable with the vehicle controller can be compared, and if the result is 30% of the total downtime, then other maintenance and other factors account for the remaining 10% of the total downtime.

[0045] The above technical solution refines the hardware allocation logic, prioritizing the allocation of single-device coverage testing needs. When a single device cannot meet the testing requirements, a multi-device collaborative solution is initiated. By marking resource usage times and updating the runtime sequence table, dynamic avoidance of resource conflicts and load balancing are achieved, solving the problem of inefficient resource management in existing technologies.

[0046] In the above technical solution, the remote test management module, hardware intelligent allocation module, cloud test module, test case sharing module, and issue sharing module are all part of the cloud platform and are all important links in completing the test. When a test comes in, the remote test management module allocates the test task, the hardware intelligent allocation module allocates the test rack and host computer, and after obtaining the test resources, the cloud test module performs environment matching, the test case sharing module provides the test plan, and if problems are encountered, the issue sharing module can assist in solving them. Finally, after the test is completed, the report is sent to the user through the remote test management module, and the test resources of the hardware intelligent allocation module are released.

[0047] Example 2 A method for hardware-in-the-loop functional verification cloud platform for new energy vehicles, comprising: Generate task allocation instructions based on the submitted hardware-in-the-loop test tasks; A test scheduling database is created based on the status information of all test racks and all host computers required for hardware-in-the-loop testing. The test scheduling database contains runtime sequence tables for all test racks and all host computers. Based on the task allocation instruction and the runtime sequence tables, the test racks and host computers required for the current hardware-in-the-loop test are selected from all test racks and all host computers. The test environment is built based on the test rack and host computer required for current hardware-in-the-loop testing. Test cases are then created in the test environment in conjunction with task allocation instructions. When a test case is created for the first time, the cloud computer matches the test case according to the task identifier field in the task allocation instruction; when a test case is reused in a subsequent test case, a reference identifier is added to the test case according to the task identifier field; after each test case is reused, the reference identifier of the reused test case is used to score the reused test case, and a test case recommendation result is generated based on the scores of all reused test cases.

[0048] Example 3 A computer program product includes a computer program, characterized in that, when the computer program is executed by a processor, it implements the steps of the method described in Embodiment 2.

[0049] The contents not described in detail in this specification are existing technologies known to those skilled in the art.

Claims

1. A cloud platform system for hardware-in-the-loop functional verification of new energy vehicles, characterized in that, It includes: The remote test management module is used to generate task allocation instructions based on the submitted hardware-in-the-loop test tasks; The hardware intelligent allocation module is used to create a test schedule database based on the status information of all test racks and all host computers required for hardware-in-the-loop testing. The test schedule database contains runtime sequence tables for all test racks and all host computers. Based on the task allocation instruction and the runtime sequence tables, the module selects the test racks and host computers required for the current hardware-in-the-loop test from all test racks and all host computers. The cloud-based testing module is used to build a test environment based on the test rack and host computer required for current hardware-in-the-loop testing. The test environment is combined with task allocation instructions to create test cases. The test case sharing module is used to match test cases with the task identifier field in the task assignment instruction when test cases are first created. When test cases are reused in subsequent tests, a reference identifier is added to the test cases according to the task identifier field. After each test case is reused, the reference identifier of the reused test case is used to score the reused test case, and a test case recommendation result is generated based on the scores of all reused test cases.

2. The cloud platform system for hardware-in-the-loop functional verification of new energy vehicles according to claim 1, characterized in that: It also includes a problem sharing module for building multi-level directories, establishing a hardware-in-the-loop test problem index based on the multi-level directories, and each hardware-in-the-loop test problem index has a corresponding solution. A certain solution corresponds to one or more hardware-in-the-loop test problem indexes. The hardware-in-the-loop test problem indexes and corresponding solutions are stored in the cloud expert database to obtain an expert Q&A system. The expert Q&A system scores a solution based on the number of times the corresponding question index is used in that solution, and generates a solution recommendation result based on the scores of all solutions.

3. The cloud platform system for hardware-in-the-loop functional verification of new energy vehicles according to claim 2, characterized in that: The multi-level directory includes a first-level domain directory for classification based on controller type, a second-level directory of controller functions created based on the first-level domain directory, a third-level directory of controller function failure issues associated with the second-level directory of controller functions, and a hardware-in-the-loop test issue index generated by the issue sharing module based on the selected third-level directory path of the controller function failure issue.

4. The cloud platform system for hardware-in-the-loop functional verification of new energy vehicles according to claim 2, characterized in that: The remote test management module is used to mark whether each tested test case has passed or failed during the hardware-in-the-loop testing process based on the test case recommendation results. The module generates the real-time progress of the hardware-in-the-loop testing based on the ratio of the number of marked test cases to the total number of test cases.

5. The cloud platform system for hardware-in-the-loop functional verification of new energy vehicles according to claim 4, characterized in that: The remote test management module generates a test report after the test is completed; Before the test report is generated, if a hardware-in-the-loop test problem index is received, the problem sharing module obtains the corresponding solution based on the solution recommendation results corresponding to the hardware-in-the-loop test problem index.

6. The cloud platform system for hardware-in-the-loop functional verification of new energy vehicles according to claim 1, characterized in that: The remote test management module assigns different permissions to different user types, including project requirement users, testers, and system administrators. The user requesting the project is the one proposing the test and has the authority to propose the test task. The system administrator has the authority to decide whether to accept the test task. If the system administrator accepts the test task, the system administrator will assign the test task to the corresponding tester to perform hardware-in-the-loop testing.

7. The cloud platform system for hardware-in-the-loop functional verification of new energy vehicles according to claim 6, characterized in that: The specific steps for testers to conduct testing are as follows: Testers log into the cloud platform system and accept the test tasks assigned by the system. The hardware intelligent allocation module allocates test racks and host computer resources for the test tasks and switches the set number of test racks according to the runtime sequence table of all test racks and host computers in the test schedule database. If it is necessary to reuse the test environment and corresponding test cases, the reused test environment is modified as needed to complete the test environment setup. Then, the reused test cases are modified as needed to complete the establishment of the test case library. During the hardware-in-the-loop testing process based on the test case recommendation results, each tested test case is marked as having passed or failed. The real-time progress of the hardware-in-the-loop testing is generated based on the ratio of the number of marked test cases to the total number of test cases. After the test is completed, a test report is generated for the testers to view and modify. The testers modify it as needed and then send the final test report to the project users via cloud computer to complete one round of testing. The above testing process is repeated until the test is completed.

8. The cloud platform system for hardware-in-the-loop functional verification of new energy vehicles according to claim 1, characterized in that: The hardware intelligent allocation module allocates a host computer and a test cabinet to the current hardware-in-the-loop test according to the status information of all test cabinets and all host computers and the task allocation instruction. At this time, the host computer and the test cabinet can cover the current hardware-in-the-loop test, and both the host computer and the test cabinet are in the off period. If the host computer and test cabinet cannot cover the hardware-in-the-loop test, but multiple test cabinets and multiple test host computers working together can meet the test requirements, or one test cabinet and multiple test host computers working together can meet the test requirements, or multiple test cabinets and one test host computer working together can meet the test requirements, and both the host computer and test cabinet are in a downtime, then the cloud computer will mark the host computer and test cabinet used, and mark the usage time of the host computer and test cabinet used, and put the markings of the host computer and test cabinet used and the usage time markings of the host computer and test cabinet used into the runtime sequence table.

9. A method for verifying hardware-in-the-loop functionality in a cloud platform for new energy vehicles, characterized in that, It includes: Generate task allocation instructions based on the submitted hardware-in-the-loop test tasks; A test scheduling database is created based on the status information of all test racks and all host computers required for hardware-in-the-loop testing. The test scheduling database contains runtime sequence tables for all test racks and all host computers. Based on the task allocation instruction and the runtime sequence tables, the test racks and host computers required for the current hardware-in-the-loop test are selected from all test racks and all host computers. The test environment is built based on the test rack and host computer required for current hardware-in-the-loop testing. Test cases are then created in the test environment in conjunction with task allocation instructions. When a test case is created for the first time, the cloud computer matches the test case according to the task identifier field in the task allocation instruction; when a test case is reused in a subsequent test case, a reference identifier is added to the test case according to the task identifier field; after each test case is reused, the reference identifier of the reused test case is used to score the reused test case, and a test case recommendation result is generated based on the scores of all reused test cases.

10. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method of claim 9.

Images