Server, management system, test system, method and computer program product

By processing data in a closed loop between the test platform and the actual vehicle, a copy of the vehicle software is generated and a problem identifier is added. This solves the problem of the vehicle software having problems in the actual environment after passing the test environment, and enables efficient software testing and dynamic adjustment, reducing operating costs.

CN119003368APending Publication Date: 2024-11-22BEIJING JIDU TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411230918.5
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-09-03
Publication Date
2024-11-22

AI Technical Summary

Technical Problem

Even after the vehicle software passes the test environment, problems still exist in the real environment. The testing process is costly and inefficient, making it difficult to identify and resolve problems in the real environment in advance.

Method used

After conducting the first phase of testing on the testing platform, the vehicle software is released to a designated actual vehicle for the second phase of testing. This establishes a closed loop of test data, generates a copy of the vehicle software and adds problem markers, dynamically adjusts the software status, and utilizes the management platform and server for data synchronization and feedback processing.

Benefits of technology

Identifying and resolving issues in real-world vehicle environments in advance reduces operating costs, improves the efficiency of creating new software packages, and ensures the stability and reliability of software in real-world environments.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119003368A_ABST
    Figure CN119003368A_ABST
Patent Text Reader

Abstract

The invention provides a server, a management system, a test system and method, and a computer program product. Wherein the server executes the following processes: receiving whole vehicle software, wherein the whole vehicle software passes a first-stage test, and the first-stage test is a test performed on the whole vehicle software based on a test case; storing the whole vehicle software in a memory; sending the whole vehicle software to a specified actual vehicle for performing a second-stage test on the whole vehicle software; and receiving test data of a second-stage test of the whole vehicle software.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to a server, a whole vehicle software test management system, a whole vehicle software test system, a whole vehicle software test method and a computer program product. Background Art

[0002] The vehicle software needs to undergo various tests before it is released. These tests can be performed in a simulated environment. After the tests are completed without any problems, the vehicle software will be released to the public for use. Since the test environment is different from the actual environment, even if the vehicle software passes the test environment, there will still be many problems / risks in the actual environment.

[0003] In addition, during the testing process of the vehicle software, personnel are needed to query test problems and find corresponding software files, etc., which has high operating costs and low efficiency. Summary of the invention

[0004] In order to solve one of the above technical problems, the present disclosure provides a server, a whole vehicle software test management system, a whole vehicle software test system, a whole vehicle software test method and a computer program product.

[0005] The present disclosure provides a server, comprising one or more processors and one or more memories, wherein the memories at least store a computer program, and when the computer program is executed by the processor, the management system performs the following process: receiving whole vehicle software, wherein the whole vehicle software is the whole vehicle software that has passed the first stage test and the first stage test is a test of the whole vehicle software based on a test case; storing the whole vehicle software in the memory; sending the whole vehicle software to a designated actual vehicle for performing a second stage test on the whole vehicle software; and receiving test data of the second stage test of the whole vehicle software.

[0006] According to the server of at least one embodiment of the present disclosure, the server inserts the software data of the whole vehicle software into the first file, and inserts the software file of the whole vehicle software into the second file.

[0007] According to a server of at least one embodiment of the present disclosure, during the process of saving the whole vehicle software to the memory, it is determined whether there is a whole vehicle software version corresponding to the whole vehicle software. If so, the whole vehicle software completely replaces the original whole vehicle software stored in the memory; or, if not, the software data of the whole vehicle software is inserted into the first file, and the software file of the whole vehicle software is inserted into the second file.

[0008] According to a server of at least one embodiment of the present disclosure, when it is determined based on the test data of the second phase test that a problem in the test data reaches a problem threshold, a whole vehicle software copy is generated based on the whole vehicle software undergoing the second phase test, and a problem identifier is added to the whole vehicle software copy.

[0009] According to another aspect of the present disclosure, a whole vehicle software test management system is provided, comprising a processor and a memory, wherein the memory stores a computer program, and when the computer program is executed by the processor, the management system performs the following process: sending the whole vehicle software to a test platform, wherein the whole vehicle software is used to perform a first phase test on the test platform and the first phase test is a test of the whole vehicle software based on a test case; receiving test data of the first phase test of the whole vehicle software from the test platform; and in the case of determining that the whole vehicle software passes the first phase test, sending the whole vehicle software that passes the first phase test to a server, wherein the whole vehicle software that passes the first phase test is used to be sent via the server to a designated actual vehicle for performing a second phase test of the whole vehicle software.

[0010] According to the management system of at least one embodiment of the present disclosure, when it is determined that the whole vehicle software or at least one software file among the multiple software files of the whole vehicle software has not passed the first stage test, a whole vehicle software copy is generated based on the whole vehicle software undergoing the first stage test, and an error identifier of failing the first stage test is added to the whole vehicle software copy.

[0011] According to another aspect of the present disclosure, a whole vehicle software testing system is provided, including a management platform, a testing platform, a server and a designated actual vehicle, wherein the management platform sends the whole vehicle software to the testing platform; the testing platform performs a first phase test on the whole vehicle software, wherein the first phase test is a test on the whole vehicle software based on a test case; the management platform receives test data of the first phase test of the whole vehicle software from the testing platform; when it is determined that the whole vehicle software passes the first phase test, the management platform sends the whole vehicle software that passes the first phase test to the server; the server sends the whole vehicle software that passes the first phase test to the designated actual vehicle; the designated actual vehicle performs a second phase test on the whole vehicle software that passes the first phase test; and the server receives the test data of the second phase test and sends the test data of the second phase test to the management platform.

[0012] According to another aspect of the present disclosure, a whole vehicle software testing method is provided, comprising: sending the whole vehicle software to a testing platform, wherein the whole vehicle software is used for performing a first phase test on the testing platform and the first phase test is a test of the whole vehicle software based on a test case; receiving test data of the first phase test of the whole vehicle software from the testing platform; and in a case where it is determined that the whole vehicle software has passed the first phase test, sending the whole vehicle software that has passed the first phase test to a server, wherein the whole vehicle software that has passed the first phase test is used to be sent via the server to a designated actual vehicle that performs a second phase test of the whole vehicle software.

[0013] According to another aspect of the present disclosure, a whole vehicle software testing method is provided, comprising: receiving whole vehicle software, wherein the whole vehicle software is whole vehicle software that has passed a first stage test and the first stage test is a test performed on the whole vehicle software based on a test case; sending the whole vehicle software to a designated actual vehicle for performing a second stage test on the whole vehicle software; and receiving test data of the second stage test of the whole vehicle software.

[0014] According to another aspect of the present disclosure, a computer program product is provided. The computer program product includes a computer program. When the computer program is executed by a processor, it is used to implement at least any of the methods described above. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] The accompanying drawings illustrate exemplary embodiments of the present disclosure and together with the description serve to explain the principles of the present disclosure. These drawings are included to provide a further understanding of the present disclosure and are incorporated in and constitute a part of this specification.

[0016] Figure 1 A schematic diagram of a whole vehicle software testing system according to an embodiment of the present disclosure is shown.

[0017] Figure 2 A schematic diagram of a whole vehicle software testing system according to another embodiment of the present disclosure is shown.

[0018] Figure 3 An interactive schematic diagram of a whole vehicle software testing system according to an embodiment of the present disclosure is shown.

[0019] Figure 4 An interactive schematic diagram of a whole vehicle software testing system according to another embodiment of the present disclosure is shown.

[0020] Figure 5 A schematic diagram showing how to handle problems that arise in the first phase of testing.

[0021] Figure 6A schematic flowchart of a method for creating a whole vehicle software copy according to an embodiment of the present disclosure is shown.

[0022] Figure 7 A schematic flowchart of a method for adding an identifier of a whole vehicle software copy, etc. according to an embodiment of the present disclosure is shown.

[0023] Figure 8 A schematic flowchart of a method for creating a whole vehicle software copy according to another embodiment of the present disclosure is shown.

[0024] Fig. 9 A schematic flow chart of a synchronization method according to an embodiment of the present disclosure is shown.

[0025] Fig.10 An example of data insertion is shown.

[0026] Fig.11 A schematic diagram of a feedback process specifying an actual vehicle problem is shown.

[0027] Fig.12 A schematic diagram of the vehicle software management system is shown.

[0028] Fig.13 A schematic diagram of a server according to an embodiment of the present disclosure is shown. Fig.14 A schematic flowchart of a vehicle software testing method according to an embodiment of the present disclosure is shown.

[0029] Fig.15 A schematic flowchart of a vehicle software testing method according to another embodiment of the present disclosure is shown. DETAILED DESCRIPTION

[0030] The present disclosure is further described in detail below in conjunction with the accompanying drawings and examples. It is understood that the specific examples described herein are only used to explain the relevant content, rather than to limit the present disclosure. It should also be noted that, for ease of description, only the parts related to the present disclosure are shown in the accompanying drawings.

[0031] It should be noted that, in the absence of conflict, the embodiments and features of the embodiments in the present disclosure can be combined with each other. The technical solution of the present disclosure will be described in detail below with reference to the accompanying drawings and in combination with the embodiments.

[0032] Testing is required during the deployment and update of vehicle software. Pre-released vehicle software is usually tested in a test environment. In order to discover and expose problems with vehicle software as early as possible, the vehicle software in the test environment is pre-placed in the present disclosure to a specified actual vehicle, so that problems can be discovered and solved in advance. In addition, during the testing process, errors are actively analyzed and copies are created, etc., thereby reducing operating costs and improving the efficiency of creating new software packages. At the same time, a closed loop is formed with the test data of the specified actual vehicle, so that the vehicle software and other states can be dynamically adjusted according to the test results. To this end, the following technical solution is proposed in the present disclosure.

[0033] In the present disclosure, "vehicle" may include different types of transportation tools or movable objects, for example, a vehicle may include a car, an aircraft, a robot or other types of transportation tools or movable objects, etc. In addition, a server may be a server with a physical form or a cloud server, and the present disclosure does not limit the type of server.

[0034] Figure 1 A schematic diagram of a vehicle software testing system according to an embodiment of the present disclosure is shown. In the vehicle software testing system, a management platform 100, a test platform 200, a server 300 and a designated actual vehicle may be included. The management platform 100 may be a software management device or a software management platform for the vehicle software, and the user of the management platform 100 may be an operation and maintenance personnel or a developer of an enterprise. The management platform 100 may be in any suitable form such as a desktop computer, a laptop computer, an internal server, and / or a cloud server. The test platform 200 is a related device for testing the vehicle software in the first phase, such as a test platform, and / or a test electronic device. Test cases may be stored in the memory of the test platform 200, and the vehicle software may be tested in the first phase based on the test cases. The test platform 200 may send test results, etc. to the management platform 100. In the present disclosure, the management platform 100 and the test platform 200 each include at least one processor and at least one memory.

[0035] In the present disclosure, the management platform 100 and the test platform 200 can communicate via wired or wireless means. The test platform 200 can receive the vehicle software from the management platform 100 and perform a first phase test on the vehicle software. During the first phase test or after the first phase test is completed, the test platform 200 can send test data, etc. to the management platform 100.

[0036] After the test platform 200 completes the first phase of testing and the first phase of testing of the whole vehicle software passes, the management platform 100 can send the whole vehicle software to the server 300. The server 300 stores the whole vehicle software and is capable of sending the whole vehicle software to the designated real vehicle 400. For example, the whole vehicle software can be sent according to the request of the designated real vehicle 400 or sent to a pre-designated real vehicle. After the designated real vehicle 400 receives the whole vehicle software, the second phase of testing of the whole vehicle software can be performed in the actual environment. For example, the whole vehicle software can be installed to the corresponding domain controller and electronic control unit through the whole vehicle controller to perform software testing of the corresponding functions. The designated real vehicle 400 can provide the feedback results of the test to the server 300, and the cloud server 300 can send the feedback results to the management platform or other corresponding devices for processing.

[0037] Figure 2 A schematic diagram of a vehicle software testing system according to another embodiment of the present disclosure is shown. The management platform 1000 and the testing platform 2000 correspond to Figure 1 The management platform 100 and the test platform 200 of the embodiment of the present invention may be referred to as the management platform 100 or the management platform 1000 and the first server 3100. Figure 2In the embodiment of the present invention, the management platform 1000 can communicate with the first server 3100, for example, the first server 3100 can receive the vehicle software from the management platform 1000 and send test data (wherein the test data can include test status, test results, log information, etc.) to the management platform 1000. The first server 3100 can be in the form of a cloud server or a physical server, for example, the first server 3100 can be in the form of a private cloud. The first server 3100 can receive and store the vehicle software from the management platform 1000 and the test results / data from the test platform 2000. After the vehicle software passes the first phase test of the test platform 2000, the vehicle software of the first server 3100 can be synchronized to the second server 3200 based on the control of the management platform 1000. For example, the first server 3100 can receive a synchronization instruction from the management platform 1000, and synchronize the vehicle software that has completed the first phase test to the second server 3200. The second server 3200 can be a cloud server or a physical server, for example, it can be in the form of a public cloud. The whole vehicle software can be released to the designated real vehicle 4000 through the second server 3200. After the whole vehicle software is installed on the designated real vehicle 4000, the second phase of testing of the whole vehicle software is performed on the designated real vehicle. In addition, the second server 3200 can receive feedback results from the designated real vehicle, and can provide the feedback results to the management platform 1000 or other devices (such as the feedback platform described later in this disclosure). The management platform 1000 or other devices process the feedback results accordingly.

[0038] In the present disclosure, vehicle software refers to, for example, an upgrade software package of the vehicle version, etc. The vehicle software is a series of software collections applied to the vehicle to control and manage the operation of various subsystems of the vehicle, and the software collection may include various software files, wherein each software file may be applied to different electronic control units or may perform different functional control, detection, information processing, communication, etc.

[0039] Figure 3 An interactive schematic diagram of a whole vehicle software testing system according to an embodiment of the present disclosure is shown. Figure 3 The schematic diagram shown corresponds to Figure 1 In step S301, the management platform stores the vehicle software to be tested. In step S302, the management platform can send the vehicle software to the test platform via its communication device or I / O interface in a wired or wireless manner, and the test platform receives the vehicle software via its communication device or I / O interface and stores it in the memory of the test platform.

[0040] In step S303, the test platform performs the first phase test of the vehicle software. The test platform may include at least one processor and at least one memory. The processor may call the stored vehicle software and test the vehicle software based on the test cases stored in the memory. The vehicle software may be stored in the program memory, and the test cases may be stored in the data memory, or both may be stored in different storage units of a memory.

[0041] During the first phase of testing, the vehicle software is tested using test cases. Test cases can be basic test cases, such as test cases for vehicle start, stop, acceleration, deceleration, braking, and communication. These test cases are used to perform the first phase of testing on the vehicle software.

[0042] In the case where the vehicle software fails the first phase test of the test case, the vehicle software may be adjusted, and steps S301 to S304 may be repeated after the adjustment is completed.

[0043] In the case where the vehicle software passes the first phase of the test case, the vehicle software can be uploaded to the server in step S305. In step S306, the server stores the vehicle software. In step S307, the server publishes the vehicle software to the specified real vehicle. The publishing can be completed according to the request of the specified real vehicle, or it can be completed by presetting the vehicle and automatically publishing the software to the preset vehicle.

[0044] In step S308, after the designated real vehicle receives the whole vehicle software, it stores and runs the whole vehicle software. In the present disclosure, the test performed by the designated real vehicle is the second phase test corresponding to the above-mentioned first phase test. During the second phase test, in step S309, the designated real vehicle can provide feedback results, and the feedback results are sent to the server. In step S310, the server can process the feedback results. The processing of the feedback results by the server may include sending the feedback results to a management platform or other device (such as the feedback platform below) for further processing of the feedback results. Further processing may include adjusting the whole vehicle software according to the feedback results, for example, the whole vehicle software may be set to a deactivated state or an unreleaseable state, etc. The feedback platform, etc., may communicate with the server, receive information / data from the server, etc., and set the whole vehicle software via the server. In the present disclosure, the test is performed through test cases in the first phase test, and the test is performed using a designated real vehicle in the second phase test, which can expose the problems that may occur in the whole vehicle software in the actual vehicle in advance. In the present disclosure, the actual vehicle is an actual vehicle traveling on a normal road.

[0045] Figure 4FIG. 1 shows an interactive schematic diagram of a vehicle software testing system according to another embodiment of the present disclosure. Figure 4 The schematic diagram shown corresponds to Figure 2 Compared with Figure 3 ,exist Figure 4 The embodiment adds a server (first server) used in the first phase test. In the following description, the steps of the same content are not repeated, and can refer to Figure 3 Description of embodiments.

[0046] In step S401, the management platform stores the whole vehicle software. In step S402, the management platform sends the whole vehicle software to the first server. In step S403, the first server stores the received whole vehicle software. In step S404, the first server sends the whole vehicle software to the test platform. In step S405, the test platform performs the first phase test on the whole vehicle software. In step S406, the test platform sends the test results / data of the whole vehicle software to the first server. In the event that the first phase test of the whole vehicle software fails, the first phase test results / data of the whole vehicle software may be sent to the management platform in step S407. After the whole vehicle software is adjusted and recreated, steps S401 to S406 may be executed again to perform the first phase test.

[0047] When the first phase test of the whole vehicle software passes, in step S408, the whole vehicle software that has passed the first phase test is sent from the first server to the second server. In the process of sending the whole vehicle software from the first server to the second server, the sending can be controlled at the management platform. For example, a synchronization button / control, etc. can be set at the management platform, and the whole vehicle software is synchronized from the first server to the second server through the synchronization button / control. In step S409, the second server stores the whole vehicle software. In step S410, the second server can publish the whole vehicle software to the specified actual vehicle. In step S411, the actual vehicle is specified to run the whole vehicle software, and in step S412, the problems encountered during the operation are fed back to the second server. In step S413, the second server processes the feedback accordingly, such as sending it to the management platform or other devices. As above, the test performed on the specified actual vehicle is the second phase test.

[0048] In the prior art, after the whole vehicle software is created, it is tested in a staging environment, in which unit testing, integration testing, etc. (which can be called advance testing) need to be performed. After passing the test in this test environment, the whole vehicle software is released for vehicle use. Although the test environment can be configured to be as consistent as possible with the real vehicle environment, the difference between the two environments means that there will still be various problems with the whole vehicle software in the real vehicle environment. In this way, various problems / failures may occur during the use of the vehicle user. In the present disclosure, in order to expose the problems of the whole vehicle software in the real vehicle environment in advance, the test case is tested in the first phase of the test, and after the test case is tested, the whole vehicle software is released to the designated real vehicle. The second phase of the test is completed on the designated real vehicle. After the second phase of the test is completed, the whole vehicle software can be released to the public vehicle. In the present disclosure, the advance test of the whole vehicle software is pre-placed to the designated real vehicle.

[0049] In the present disclosure, data in a first-stage test environment (staging environment) and data in a second-stage test environment (production environment) are independent of each other.

[0050] If problems arise in the first phase of testing of the vehicle software and it fails, a copy of the vehicle software can be created based on the vehicle software being tested and the errors can be analyzed. Figure 5 A schematic diagram showing how to handle problems that arise in the first phase of testing.

[0051] In step S501, the vehicle software is stored in the management platform. In step S502, the vehicle software is sent to the first server. In step S503, the management platform can continue to monitor the test results. The management platform can monitor the status of the vehicle software and receive corresponding data. In one example, a WebSocket connection can be created between the management platform and the first server and the WebSocket service can be enabled. The first server can send a message to the management platform to implement monitoring on the management platform.

[0052] In step S504, the first server may store the vehicle software. In step S505, the vehicle software may be sent to the test platform. In step S506, the first server continuously monitors the test results and other information of the test platform. The monitoring method may be the same as the monitoring method of step S503.

[0053] In step S507, the first phase of testing is performed on the whole vehicle software. The whole vehicle software is in the form of multiple software packages, which can also be called software files. Take the electronic control unit (ECU) as an example for illustration. The vehicle system includes dozens of ECUs, and each ECU will have a corresponding software file. During the first phase of testing of the whole vehicle software, multiple tests need to be performed. In this case, it may be necessary to gradually perform corresponding tests on the whole vehicle software. During the testing of the whole vehicle software, there may be a problem that when a problem occurs in the corresponding software file of a certain ECU, the first phase of testing stops. In the present disclosure, when or before a problem occurs, a copy of the whole vehicle software is created relative to the tested whole vehicle software, and when the whole vehicle software is measured, the following test can be continued even if a problem occurs in the test of a certain software file. At the same time, the problem can be fed back to the copy of the whole vehicle software.

[0054] In step S508, the first server continuously obtains the test status / data of the first phase test of the vehicle software, so as to synchronize the test status / data between the first server and the test platform. The test data may be, for example, log information of the test platform.

[0055] In step S510, the first server may perform corresponding processing according to the test status and test data. The corresponding processing at least includes creating a whole vehicle software copy based on the tested whole vehicle software, and setting an identifier to the whole vehicle software copy according to the acquired test data. For example, if a problem occurs during the test, the test data corresponding to the problem may be analyzed, and the corresponding identifier may be set to the whole vehicle software copy for error prompts. Then, the whole vehicle software copy may be synchronized to the management platform in step S511. In step S512, the management platform may perform processing based on the whole vehicle software copy, such as displaying it to facilitate reconfiguration of the whole vehicle software or sending it to other devices, etc. In addition, in step S512, the whole vehicle software that has failed the test may also be set to a disabled state, etc.

[0056] Figure 6A schematic flow chart of a method for creating a whole vehicle software copy according to an embodiment of the present disclosure is shown. During the first phase of testing of the whole vehicle software A, in step S610, the first server continuously monitors the test status of the whole vehicle software A. For each test of the first phase of testing, if there is a test that fails, the test platform will generate a corresponding error log. In some cases, the error log can be generated by a tester. The generation format of the error log can be preset, for example, it can include the whole version, software file ID, corresponding ECU, error cause, etc. The first server can monitor the test status of the whole vehicle software at the beginning of the whole vehicle software test. During the testing and monitoring process, if a test fails, a whole vehicle software copy B of the whole vehicle software A is created in step S620. During the creation process, the whole vehicle software A can be copied as a whole to generate the whole vehicle software copy B. And the first server analyzes the error log data that failed the test, and adds the error identifier to the corresponding position of the whole vehicle software copy B in step S630. The format of the software file that failed the test can also be modified. In step S640, the whole vehicle software copy B can be sent to the management platform.

[0057] Figure 7 A schematic diagram of a method for adding identification, etc. of a complete vehicle software copy according to an embodiment of the present disclosure is shown. For example, during the test process of ECU1, if there is a problem with software package 2 of ECU1, the format suffix of the software package can be modified, that is, the software file (software package 2) is modified from a first format to a second format, wherein the second format is related to the software tool of the management platform, that is, a format that can be opened and displayed by the software tool of the management platform. As an example, the format suffix can be modified from bin format to vbf format. In addition, an error message field (error identification) can be added to the software file (software package 2), wherein the corresponding error can be prompted in the error message field. Figure 7 The example of FIG. 1 shows that the errMsg field is added to software package 2. After the vehicle software copy is synchronized to the management platform, the software tool of the management platform displays error content and the like.

[0058] exist Figure 6 In the embodiment, if a test fails, the error log data is analyzed, the format suffix of the corresponding software file is modified in the vehicle software copy and an error mark is added, and then the test is continued. If another test fails, the above process is repeated. However, in the present disclosure, the processing can also be performed after all the tests of the vehicle software are completed. Figure 8 A schematic flowchart of a method for creating a whole vehicle software copy according to another embodiment of the present disclosure is shown.

[0059] In step S810, the first server monitors the first phase test of the vehicle software A and obtains test data, etc. In step S820, it is determined whether all tests of the first phase test have passed. If all tests have passed, the vehicle software A can be synchronized to the second server in step S830 (which can be based on the synchronization operation of the management platform). If not all tests have passed, a vehicle software copy B is created on the first server in step S840. In step S850, the first server analyzes all error log data and queries whether there is a software file corresponding to the error log data. If so, in step S860, an error identifier is added to the corresponding software file of the vehicle software copy B and the file format of the corresponding software file can also be modified. After the addition and modification of the vehicle software copy B are completed, in step S870, the vehicle software copy B can be sent to the management platform. Display and processing are performed on the management platform, so as to facilitate the reconfiguration of the vehicle software.

[0060] In the present disclosure, the test log (error log data) of the test platform is actively associated, and specific problems are analyzed based on the test log, and the problems are reflected in the vehicle software copy. The vehicle software copy can be provided to operation and maintenance personnel or developers, etc. These personnel can create new vehicle software based on the content / information of the vehicle software copy. This can reduce operating costs and improve the efficiency of creating vehicle software.

[0061] In the above description, if the vehicle software fails the first phase test, a corresponding vehicle software copy is created and an identification is set, and the staff can generate a new vehicle software based on the vehicle software copy according to the identification information. And the new vehicle software is tested again in the first phase. After the vehicle software passes the first phase test, the vehicle software can be released to the designated actual vehicle, and the second phase test is performed on the designated actual vehicle.

[0062] The database used for the first phase test can be set up on the first server, and the database used for the second phase test can be set up on the second server. The database used for the first phase test and the database used for the second phase test store the data and files of each phase respectively, and the two databases are completely independent, so as to ensure that the data will not be contaminated by each other.

[0063] When the vehicle software passes the first phase test, the vehicle software can be synchronized from the first phase test database (such as the database of the first server) to the second phase test database (such as the database of the second server). Fig. 9A schematic flow chart of a synchronization method according to an embodiment of the present disclosure is shown. In the process of starting synchronization, for example, a synchronization button can be clicked on the management platform. In step S910, it is determined whether there is a whole vehicle software (stored whole vehicle software) corresponding to the synchronized whole vehicle software in the second-stage test database, where "correspondence" can be a version correspondence, for example, there can be whole vehicle software with the same major version number or there can be whole vehicle software with the same version number, etc., which can be pre-set according to actual conditions. If there is a corresponding whole vehicle software in the second-stage test database, then in step S920, the synchronized whole vehicle software is used to fully replace the whole vehicle software originally stored in the second-stage test database. Full replacement means replacing all files of the stored whole vehicle software. If there is no corresponding whole vehicle software in the second-stage test database, then in step S930, the synchronized whole vehicle software is inserted into the second-stage test database.

[0064] During the insertion process of step S930, different contents of the whole vehicle software are inserted into different files. After synchronization, the second server starts to traverse the software data and software files of the synchronized whole vehicle software. In the present disclosure, software data can be understood as the information content of the software, for example, it can contain information such as version number, vehicle model, baseline ECU, etc. Software files can be understood as software file entities with specific formats and uses, such as program files, configuration files, etc. Software data can be inserted into a first file (also referred to as a first table), and software files can be inserted into a second file (also referred to as a second table). In this way, the corresponding software data is contained in the first file, and each corresponding software file is contained in the second file. Fig.10 An example of data insertion is shown. The software data contained in the first file is the version number, baseline, vehicle model, and ECU ID. The second file contains the software files contained in the ECU with the corresponding ID, such as the software files file1_1 and file1_2 contained in ECU1 with ID1. Fig.10 In the figure, only one ECU is shown, and the same method can be used for other ECUs. By setting corresponding contents in the first file and the second file, data responsibilities can be made clear and query efficiency can be improved.

[0065] In the second phase of testing, the vehicle software is tested based on the problems reported by the specified actual vehicles. In the process of specifying the actual vehicle feedback problems, the actual vehicle users can collect problems through the smartphone side (such as APP, WeChat applet) or the vehicle side (such as display screen, voice acquisition equipment). In the process of collecting problems, the problems can be classified (for example, problem type: smart driving, smart cockpit, etc.), and a problem description can also be attached. As an example, the feedback problem can include software version, priority, status, fault description, reporter and other information.

[0066] Fig.11 A schematic diagram of a feedback process for a specified actual vehicle problem is shown. In the schematic diagram, a feedback platform is provided. The feedback platform is similar to a management platform and can be a computer device, a physical server or a cloud server set up within the enterprise. The server can be Figure 3 The server of the embodiment may also be Figure 4 One of the first server and the second server of the embodiment may be, for example, the second server, or may be different from Figure 3 and Figure 4 The server of the embodiment is another server.

[0067] In step S1101, the feedback platform can receive feedback issues from the second phase of testing of the specified actual vehicle. After receiving the feedback issues, the feedback platform can analyze and process the feedback issues. The number of issues, issue priority, and issue attribution are stored according to the version dimension. For example, the issue priority can be divided into high-severity issues, medium-severity issues, and low-severity issues. In step S1103, the server can monitor the stored version dimension and obtain corresponding information. The version dimension can be used to classify and count issues from multiple dimensions. The classification and statistics of issues can be completed on the feedback platform or on the server.

[0068] As an example, the rules of the version dimension can be set as follows. If the total number of problems reaches a first threshold or the number of problems with high severity and problems with medium severity reaches a second threshold, the management platform can be prohibited from releasing the whole vehicle software. If the total number of problems reaches a third threshold that is greater than the first threshold or the number of problems with high severity and problems with medium severity reaches a fourth threshold that is greater than the second threshold, the whole vehicle software can be set to a disabled state. When set to a disabled state, a copy of the whole vehicle software can be generated, and problem identifiers, etc. can be added to the copy of the whole vehicle software, the format of the software file can be changed, etc. The content can refer to the description above (the error identifier is added to the copy of the whole vehicle software, the format of the software file is changed, etc.).

[0069] exist Fig.11 In the example of , on the server side, the software status can be controlled in step S1104, information from the feedback platform can be stored, and a copy can be created. In addition, the information and status can be sent to the management platform in step S1105, and the management platform can update the status of the vehicle software in step S1106 and update the version list of the vehicle software in step S1107, where the vehicle software copy is newly added. These contents can refer to the above description.

[0070] In the present disclosure, an association is established with a specified actual vehicle, such as receiving relevant information from the specified actual vehicle through a feedback platform, so that the status of the entire vehicle software can be dynamically adjusted (release prohibited / deactivation, etc.) according to the feedback issues of the specified actual vehicle, which facilitates maintenance and reduces costs.

[0071] According to a further embodiment of the present disclosure, a management system is provided, wherein the management system is a management system for vehicle software. The vehicle software management system may correspond to Figure 3 The management platform shown, or corresponding to Figure 4 The management platform shown and the first server, or corresponding to Figure 4 The first server is shown.

[0072] Fig.12 The schematic diagram of the vehicle software management system is shown. The vehicle software may include one or more processors, one or more memories (the memories may also be in the form of databases), and a communication device or an I / O interface, etc. The memory at least stores a computer program, and when the computer program is executed by the processor, the management system performs the following process.

[0073] The vehicle software is sent to the test platform through the communication device or I / O interface of the management system, wherein the vehicle software is used for the first phase test on the test platform and the first phase test is a test of the vehicle software based on the test case. The test platform may include at least one processor and at least one memory. The processor may call the stored vehicle software and test the vehicle software based on the test case stored in the memory. The test case may be a basic test case, for example, including a test case for vehicle starting, stopping, accelerating, decelerating, braking and communication.

[0074] The test data of the first phase test of the vehicle software from the test platform is received through the communication device or I / O interface of the management system. The management system can monitor the status of the vehicle software tested by the test platform and can receive the test data from the test platform.

[0075] When it is determined that the whole vehicle software has passed the first stage test, the whole vehicle software that has passed the first stage test is sent to the server through the communication device or I / O interface of the management system, wherein the whole vehicle software that has passed the first stage test is used to be sent via the server to the designated actual vehicle for the second stage test of the whole vehicle software.

[0076] If it is determined that the vehicle software or at least one of the multiple software files of the vehicle software has not passed the first phase test, the management system can generate a vehicle software copy based on the vehicle software that has undergone the first phase test. An error mark indicating that the vehicle software has not passed the first phase test is added to the vehicle software copy. For details, please refer to the above relative Figures 6 to 8 Related descriptions of embodiments of the present invention.

[0077] Among them, the management system can add error identification to the software files that have not passed the first phase of testing in the whole vehicle software copy based on the test data. And the management system can also display the error identification or information related to the error identification. In the present disclosure, the test log (error log data) of the test platform is actively associated, and the specific problem is analyzed based on the test log, and the problem is reflected in the whole vehicle software copy. The whole vehicle software copy can be provided to operation and maintenance personnel or developers, etc., who can create new whole vehicle software based on the content / information of the whole vehicle software copy. This can reduce operating costs and improve the efficiency of creating whole vehicle software.

[0078] After the vehicle software is adjusted relative to the vehicle software copy, the above steps can be repeated: sending the vehicle software to the test platform and receiving test data until the vehicle software passes the first phase of testing. The vehicle software that passes the first phase of testing is then sent to the server for the second phase of testing.

[0079] For the contents related to the management system, please refer to the above description, which will not be repeated here for the sake of brevity.

[0080] According to a further embodiment of the present disclosure, a server is provided, which may correspond to Figure 3 The server shown, or corresponding to Figure 4 The second server shown, or corresponding to Fig.11 The server shown.

[0081] Fig.13 A schematic diagram of a server of an embodiment of the present disclosure is shown, wherein the server may include one or more processors and one or more memories (which may also be in the form of databases), and the memories at least store a computer program. When the computer program is executed by the processor, the server performs the following process.

[0082] The server receives the vehicle software. The vehicle software may come from Figure 4The first server. The vehicle software is the vehicle software that has passed the first phase test and the first phase test is a test of the vehicle software based on the test case. The server saves the vehicle software to the memory. The server can publish the vehicle software to a specified actual vehicle. The vehicle software is run on the specified actual vehicle to implement the second phase test. The server can also receive test data of the second phase test of the vehicle software.

[0083] When the server receives the vehicle software and stores the vehicle software, the software data of the vehicle software can be inserted into the first file, and the software file of the vehicle software can be inserted into the second file. The description of the software data and software file can refer to the above description.

[0084] During the process of saving the whole vehicle software to the memory, the server determines whether there is a whole vehicle software version corresponding to the whole vehicle software. If so, the whole vehicle software completely replaces the original whole vehicle software stored in the memory; if not, the software data of the whole vehicle software is inserted into the first file, and the software file of the whole vehicle software is inserted into the second file.

[0085] When the server determines that the problem in the test data reaches the problem threshold based on the test data of the second phase test, a vehicle software copy is generated based on the vehicle software undergoing the second phase test, and a problem identifier is added to the vehicle software copy. For the relevant content of the problem threshold, please refer to the rules of the version dimension described above.

[0086] For the contents related to the server, please refer to the above description, which will not be repeated here for the sake of brevity.

[0087] According to a further embodiment of the present disclosure, a vehicle software testing method is also provided. Fig.12 The management system is executed. Fig.14 A schematic flow chart of the vehicle software testing method is shown.

[0088] In step S1410, the vehicle software is sent to the test platform, wherein the vehicle software is used for the first phase test on the test platform and the first phase test is a test of the vehicle software based on the test case, and in step S1420, the test data of the first phase test of the vehicle software from the test platform is received. In step S1440, if it is determined that the vehicle software has passed the first phase test, the vehicle software that has passed the first phase test is sent to the server, wherein the vehicle software that has passed the first phase test is used to be sent via the server to the designated actual vehicle for the second phase test of the vehicle software.

[0089] In addition, the whole vehicle software testing method may also include step S1430, in which it is determined whether the whole vehicle software has passed the first stage test, and if it has passed the first stage test, step S1440 is executed. If the first stage test has not been passed, for example, if the whole vehicle software or at least one of the multiple software files in the whole vehicle software has not passed the first stage test, step S1450 is executed. In step S1450, a whole vehicle software copy is generated based on the whole vehicle software that has undergone the first stage test. In step S1460, the test data is analyzed, and based on the analyzed test data, an error mark may be added to the whole vehicle software copy, wherein in the process of adding the error mark, an error mark may be added for the software file that has not passed the first stage test. In addition, as described above, the file format of the corresponding software file may also be modified. In addition, the error may also be presented to an operator or developer, etc.

[0090] In step S1470, a new vehicle software is obtained. The relevant personnel can adjust the original vehicle software according to the error to obtain the new vehicle software. The management platform / server can receive the new vehicle software and then continue to execute step S1410. Finally, the vehicle software that can be tested in the second phase is obtained.

[0091] According to a further embodiment of the present disclosure, a vehicle software testing method is also provided. The vehicle software testing method can be performed on the server or Figure 4 Executed on the second server as shown. Fig.15 A schematic flow chart of the vehicle software testing method is shown.

[0092] In step S1510, the server receives the whole vehicle software, wherein the whole vehicle software is the whole vehicle software that has passed the first phase test and the first phase test is the test of the whole vehicle software based on the test case. In step S1550, the whole vehicle software is sent to the designated actual vehicle for the second phase test of the whole vehicle software. In step S1560, the test data of the second phase test of the whole vehicle software is received, wherein the test data is the test data from the designated actual vehicle.

[0093] The vehicle software testing method of this embodiment may also include step S1530, in the process of storing the vehicle software, determining whether there is a vehicle software version corresponding to the vehicle software. If so, in step S1540, the original vehicle software stored in the memory is completely replaced by the received vehicle software. If not, in step S1550, the software data of the vehicle software is inserted into the first file, and the software file of the vehicle software is inserted into the second file.

[0094] The vehicle software testing method of this embodiment may also include step S1570, in which it is determined whether the problem in the test data reaches the problem threshold based on the test data of the second phase test. When the problem threshold is reached, in step S1580, a vehicle software copy is generated based on the vehicle software undergoing the second phase test, and a problem identifier is added to the vehicle software copy in step S1590. For the description of the problem threshold, please refer to the above content. For example, according to the rules of the version dimension, the release of the vehicle software may be prohibited or the vehicle software may be disabled. For example, when the vehicle software is disabled, a vehicle software copy may be generated.

[0095] Furthermore, the whole vehicle software can be further adjusted based on the whole vehicle software copy, and new whole vehicle software can be generated. The first stage test and the second stage test can be performed again for the new whole vehicle software until the conditions for release to public vehicles are met.

[0096] The present disclosure also provides a computer program product, and the method of the present disclosure can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer program or instruction is loaded and executed, the process or function of the present disclosure is executed in whole or in part. A computer-readable storage medium can be used as an implementation of a computer program product, that is, the present disclosure also provides a computer-readable storage medium, which includes a computer program, and when the computer program is executed by a processor, any of the above methods is implemented.

[0097] The computer program or instructions may be stored in a readable storage medium or transmitted from one readable storage medium to another readable storage medium, for example, the computer program or instructions may be transmitted from one website, computer, server or data center to another website, computer, server or data center by wired or wireless means. The readable storage medium may be any available medium that can be accessed or a data storage device such as a server, data center, etc. that integrates one or more available media. The available medium may be a magnetic medium, such as a floppy disk, a hard disk, or a magnetic tape; it may also be an optical medium, such as a digital video disk; it may also be a semiconductor medium, such as a solid state drive. The computer readable storage medium may be a volatile or non-volatile storage medium, or may include both volatile and non-volatile types of storage media.

[0098] Those skilled in the art will appreciate that the embodiments of the present disclosure may be provided as methods, systems, or computer program products. Therefore, the present disclosure may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the present disclosure may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0099] The present disclosure is described with reference to flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to the present disclosure. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as the combination of processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0100] These computer program instructions may also be stored in a computer readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer readable memory produce an article of manufacture including an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0101] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process in the computer or other programmable device. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0102] In the description of this specification, the description with reference to the terms "one embodiment / method", "some embodiments / methods", "example", "specific example", or "some examples" etc. means that the specific features, structures, or characteristics described in conjunction with the embodiment / method or example are included in at least one embodiment / method or example of the present disclosure. In this specification, the schematic representations of the above terms do not necessarily refer to the same embodiment / method or example. Moreover, the specific features, structures, or characteristics described may be combined in any one or more embodiments / methods or examples in a suitable manner. In addition, those skilled in the art may combine and combine different embodiments / methods or examples described in this specification and features of different embodiments / methods or examples, unless they are contradictory.

[0103] In addition, the terms "first" and "second" are used for descriptive purposes only and should not be understood as indicating or implying relative importance or implicitly indicating the number of the indicated technical features. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one of the features. In the description of the present disclosure, "plurality" means at least two, such as two, three, etc., unless otherwise clearly and specifically defined.

[0104] Those skilled in the art should understand that the above embodiments are only for the purpose of clearly illustrating the present disclosure, and are not intended to limit the scope of the present disclosure. For those skilled in the art, other changes or modifications may be made based on the above disclosure, and these changes or modifications are still within the scope of the present disclosure.

Claims

1. A server, It is characterized in that The server comprises one or more processors and one or more memories, wherein the memories at least store a computer program, and when the computer program is executed by the processor, the server performs the following process: Receiving whole vehicle software, wherein the whole vehicle software is whole vehicle software that has passed the first phase test and the first phase test is a test performed on the whole vehicle software based on a test case; Storing the vehicle software in a memory; Sending the vehicle software to a designated actual vehicle for a second phase of testing of the vehicle software; as well as Receive test data from the second phase of testing of the whole vehicle software.

2. The server according to claim 1, It is characterized in that The server inserts the software data of the whole vehicle software into the first file, and inserts the software file of the whole vehicle software into the second file.

3. The server according to claim 1, It is characterized in that In the process of saving the vehicle software to the memory, determining whether there is a vehicle software version corresponding to the vehicle software, If it exists, the original vehicle software stored in the memory is completely replaced by the vehicle software; or, If it does not exist, the software data of the whole vehicle software is inserted into the first file, and the software file of the whole vehicle software is inserted into the second file.

4. The server according to any one of claims 1 to 3, It is characterized in that When it is determined based on the test data of the second phase test that the problem in the test data reaches the problem threshold, a whole vehicle software copy is generated based on the whole vehicle software undergoing the second phase test, and a problem identifier is added to the whole vehicle software copy.

5. A vehicle software test management system, It is characterized in that The system comprises a processor and a memory, wherein the memory stores a computer program. When the computer program is executed by the processor, the vehicle software test management system performs the following process: Sending the whole vehicle software to the test platform, wherein the whole vehicle software is used to perform a first phase test on the test platform and the first phase test is a test performed on the whole vehicle software based on a test case; Receiving test data of the first phase test of the whole vehicle software from the test platform; as well as When it is determined that the whole vehicle software has passed the first stage test, the whole vehicle software that has passed the first stage test is sent to a server, wherein the whole vehicle software that has passed the first stage test is used to be sent via the server to a designated actual vehicle that undergoes a second stage test of the whole vehicle software.

6. The vehicle software test management system according to claim 1, It is characterized in that When it is determined that the whole vehicle software or at least one of the multiple software files of the whole vehicle software has failed the first stage test, a whole vehicle software copy is generated based on the whole vehicle software that has undergone the first stage test, and an error identifier of failing the first stage test is added to the whole vehicle software copy.

7. A vehicle software testing system, It is characterized in that Including management platform, test platform, server and designated actual vehicle, The management platform sends the vehicle software to the test platform; The test platform performs a first phase test on the vehicle software, wherein the first phase test is a test performed on the vehicle software based on a test case; The management platform receives test data of the first phase test of the whole vehicle software from the test platform; When it is determined that the vehicle software has passed the first phase test, the management platform sends the vehicle software that has passed the first phase test to the server; The server sends the vehicle software that has passed the first phase test to the designated actual vehicle; The designated actual vehicle performs a second phase test on the vehicle software that has passed the first phase test; and The server receives the test data of the second phase test, and sends the test data of the second phase test to the management platform.

8. A vehicle software testing method, It is characterized in that include: Sending the whole vehicle software to the test platform, wherein the whole vehicle software is used to perform a first phase test on the test platform and the first phase test is a test performed on the whole vehicle software based on a test case; Receiving test data of the first phase test of the whole vehicle software from the test platform; as well as When it is determined that the whole vehicle software has passed the first stage test, the whole vehicle software that has passed the first stage test is sent to a server, wherein the whole vehicle software that has passed the first stage test is used to be sent via the server to a designated actual vehicle that undergoes a second stage test of the whole vehicle software.

9. A vehicle software testing method, It is characterized in that include: Receiving whole vehicle software, wherein the whole vehicle software is whole vehicle software that has passed the first phase test and the first phase test is a test performed on the whole vehicle software based on a test case; Sending the vehicle software to a designated actual vehicle for a second phase of testing of the vehicle software; as well as Receive test data from the second phase of testing of the whole vehicle software.

10. A computer program product, It is characterized in that The computer program product comprises a computer program, which is used to implement at least the method according to claim 8 or 9 when executed by a processor.