OTA upgrade test method and device, automobile and medium
Through the automated OTA upgrade test method, the existing test relies on the problem of low efficiency that the existing test depends on manual operation, realizing the comparison and visual results of automated attributes, which improves test efficiency and saves costs.
Patent Information
- Application Number
- CN202411449588.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-10-16
- Publication Date
- 2025-01-28
Smart Images
Figure CN119377113A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the technical field of vehicle-mounted systems, and in particular to a method, device, vehicle and medium for OTA upgrade testing. Background Art
[0002] When a new car is released, the in-vehicle system needs to be updated. On the one hand, it is to optimize and upgrade the functions to adapt to the ever-changing car needs of consumers, and on the other hand, it is to fix security vulnerabilities and improve the reliability and stability of the in-vehicle system. In this context, OTA (Over-the-Air) upgrade technology came into being.
[0003] If the OTA upgrade fails, the user will not be able to obtain the latest vehicle system. If the OTA upgrade is successful, it does not mean that the tester can sit back and relax. Therefore, the tester attaches great importance to the OTA upgrade test. The success of the OTA upgrade may cause the failure of old functions and change user settings. These failures will affect the consumer's car experience, and some serious failures may even endanger the driving safety of the car owner.
[0004] The current OTA upgrade test mainly includes system testing of new functions and regression testing of old functions. The regression test of old functions is particularly dependent on "attribute value checking". These attribute values do not come from the static attributes of the configuration table, but from the dynamic attributes of the underlying hardware, vehicle system, etc. However, dynamic attributes are generated by code logic. If the attribute value of the old function has not changed (except for a few attributes), it can be considered that the regression test of the old function has passed, and the probability of failure of the code logic of the old function is low.
[0005] At present, the regression testing of old functions is basically done manually, which is time-consuming and laborious. Taking the charging module of a certain car company as an example, testers need to check the attribute values of dozens of setting items, and these attribute values need to be recorded one by one. After the OTA upgrade is completed, the attribute values of these setting items are recorded again to compare whether there are any changes before and after. There are more than a dozen other modules like the charging module in the car, and the number of attribute values is large. It is time-consuming and laborious to rely solely on manual testing. Summary of the invention
[0006] In order to solve or partially solve the problems existing in the related art, the present application provides a method, device, vehicle and medium for OTA upgrade testing, which can improve the testing efficiency.
[0007] The first aspect of the present application provides a method for OTA upgrade testing, including: In response to a trigger operation associated with an over-the-air (OTA) upgrade, obtaining attribute information of the vehicle system before the OTA upgrade; Initiating an OTA upgrade of the vehicle system; After the OTA upgrade is successful, obtaining the attribute information of the vehicle system after the OTA upgrade; The execution of an attribute comparison task is triggered and the comparison result is displayed, wherein the attribute comparison task includes comparing the attribute information of the vehicle system before and after the OTA upgrade.
[0008] In one embodiment, the step of responding to a trigger operation associated with an over-the-air (OTA) upgrade also includes: Push the attribute capture tool to the vehicle-mounted system, so that the attribute capture tool is deployed in the vehicle-mounted system to capture the attribute data of the vehicle-mounted system.
[0009] In one implementation, obtaining the attribute information of the vehicle-mounted system includes: Sending a target broadcast to the attribute crawler, so that the attribute crawler crawls the attribute data after receiving the target broadcast; Receiving the attribute data sent by the attribute crawler; The attribute data is converted into the attribute information.
[0010] In one implementation, the attribute data includes attribute data of underlying hardware and the system, the attribute data of the system includes attribute data of self-developed applications and native system, and the attribute capture tool captures the attribute data, including: The attribute capture tool captures the attribute data of the underlying hardware by calling the software development kit SDK of the underlying hardware on the vehicle-mounted system; or, The attribute capture tool captures the attribute data of the self-developed application by calling the SDK of the self-developed application on the vehicle-mounted system; or, The attribute capture tool captures the system's native attribute data by calling the system's native API on the vehicle-mounted system.
[0011] In one embodiment, the converting the attribute data into the attribute information includes: The attribute data is converted into a String format and stored in a json file in the form of a key-value pair Key-Value, thereby obtaining the attribute information.
[0012] In one embodiment, obtaining the attribute information of the vehicle-mounted system further includes: Give the json file a unique name.
[0013] In one embodiment, the initiating an OTA upgrade of the vehicle system includes: Determine the ROM corresponding to the OTA upgrade package according to the trigger operation, and obtain the OTA upgrade package, wherein the trigger operation includes a ROM selection operation; The vehicle-mounted system is OTA upgraded according to the obtained OTA upgrade package.
[0014] In one embodiment, triggering the execution of the attribute comparison task and displaying the comparison result includes: After acquiring the attribute information of the vehicle system after the OTA upgrade, comparing the attribute information of the vehicle system before and after the OTA upgrade according to the Diff command to generate an attribute difference file; Use the Diff2html tool to generate an attribute difference comparison page for the attribute difference file.
[0015] In one embodiment, triggering the execution of the attribute comparison task and displaying the comparison result includes: The difference attributes in the attribute difference comparison page are marked.
[0016] In one embodiment, it further comprises: Report the relevant data generated when the OTA upgrade test method is executed.
[0017] A second aspect of the present application provides an OTA upgrade test device, including: A first attribute acquisition module, configured to acquire attribute information of the vehicle system before OTA upgrade in response to a trigger operation associated with OTA upgrade; An OTA upgrade module, configured to initiate an OTA upgrade of the vehicle system; A second attribute acquisition module, which is configured to obtain attribute information of the vehicle system after the OTA upgrade is successful; The attribute comparison module is configured to trigger the execution of an attribute comparison task and display the comparison result, wherein the attribute comparison task includes comparing the attribute information of the vehicle system before and after the OTA upgrade.
[0018] A third aspect of the present application provides a car, comprising: Processor; and The memory stores executable codes thereon, and when the executable codes are executed by the processor, the processor is caused to execute the method as described above.
[0019] A fourth aspect of the present application provides a computer-readable storage medium having executable code stored thereon. When the executable code is executed by a processor of an electronic device, the processor is caused to execute the method as described above.
[0020] The technical solution provided by this application may have the following beneficial effects: The technical solution of the present application, first, in response to the trigger operation associated with the OTA upgrade of the over-the-air download technology, obtains the attribute information of the vehicle system before the OTA upgrade; second, starts the OTA upgrade of the vehicle system; after the OTA upgrade is successful, obtains the attribute information of the vehicle system after the OTA upgrade; finally, triggers the execution of the attribute comparison task and displays the comparison result, wherein the attribute comparison task includes comparing the attribute information before and after the OTA upgrade of the vehicle system. The present application can automatically obtain the attribute information before and after the OTA upgrade of the vehicle system and perform attribute comparison and visually display the comparison results, which can improve the test efficiency and save labor costs.
[0021] It should be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present application. BRIEF DESCRIPTION OF THE DRAWINGS
[0022] The above and other objects, features and advantages of the present application will become more apparent by describing in more detail exemplary embodiments of the present application in conjunction with the accompanying drawings, wherein the same reference numerals generally represent the same components in the exemplary embodiments of the present application.
[0023] Figure 1 It is a flowchart of the OTA upgrade test method shown in an embodiment of the present application; Figure 2 It is a schematic diagram of the architecture of the OTA upgrade test solution shown in the embodiment of the present application; Figure 3 It is a structural schematic diagram of an OTA upgrade test device shown in an embodiment of the present application; Figure 4 It is a schematic diagram of the structure of a car shown in an embodiment of the present application. DETAILED DESCRIPTION
[0024] The embodiments of the present application will be described in more detail below with reference to the accompanying drawings. Although the embodiments of the present application are shown in the accompanying drawings, it should be understood that the present application can be implemented in various forms and should not be limited by the embodiments described herein. On the contrary, these embodiments are provided to make the present application more thorough and complete, and to fully convey the scope of the present application to those skilled in the art.
[0025] The terms used in this application are for the purpose of describing specific embodiments only and are not intended to limit this application. The singular forms of "a", "said" and "the" used in this application and the appended claims are also intended to include plural forms unless the context clearly indicates other meanings. It should also be understood that the term "and / or" used herein refers to and includes any or all possible combinations of one or more associated listed items.
[0026] It should be understood that although the terms "first", "second", "third", etc. may be used in this application to describe various information, this information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other. For example, without departing from the scope of this application, the first information may also be referred to as the second information, and similarly, the second information may also be referred to as the first information. Thus, the features defined as "first" and "second" may explicitly or implicitly include one or more of the features. In the description of this application, the meaning of "multiple" is two or more, unless otherwise clearly and specifically defined.
[0027] The current OTA upgrade test mainly includes system testing of new functions and regression testing of old functions. The regression testing of old functions is particularly dependent on "attribute value checking", but the regression testing of old functions is basically done manually, which is time-consuming and laborious.
[0028] In response to the above problems, an embodiment of the present application provides a method for OTA upgrade testing, which can automatically obtain the attribute information of the vehicle system before and after OTA upgrade and perform attribute comparison and visually display the comparison results, thereby improving test efficiency and saving labor costs.
[0029] The technical solution of the embodiments of the present application is described in detail below with reference to the accompanying drawings.
[0030] Figure 1 It is a flow chart of the OTA upgrade test method shown in an embodiment of the present application.
[0031] like Figure 1 As shown, an embodiment of the present application provides a method for OTA upgrade testing, which can be applied to a PC terminal. The PC terminal and the vehicle terminal are two different terminals, and a software assistant is deployed on the PC terminal. The software assistant can execute steps S101 to S104.
[0032] Step S101: In response to a trigger operation associated with an over-the-air (OTA) upgrade, obtain attribute information of the vehicle system before the OTA upgrade.
[0033] In one embodiment, before step S101 , the software assistant pushes the attribute capture tool to the vehicle-mounted system, so that the attribute capture tool is deployed in the vehicle-mounted system to capture the attribute data of the vehicle-mounted system.
[0034] Among them, the software assistant and the attribute grabbing tool are deployed on different terminals. The software assistant is deployed on the PC terminal, and the attribute grabbing tool is deployed on the vehicle terminal during operation. When the attribute grabbing tool is deployed on the vehicle terminal, that is, the attribute grabbing tool is on the vehicle system, the software assistant can obtain the attribute information of the vehicle system through the attribute grabbing tool.
[0035] Furthermore, in step S101, obtaining the attribute information of the vehicle-mounted system may include: Sending a target broadcast to the attribute crawler, so that the attribute crawler crawls the attribute data after receiving the target broadcast; Receive attribute data sent by the attribute crawler; Convert attribute data into attribute information.
[0036] In this embodiment, the software assistant and the attribute capture tool belong to different terminals. In order to distinguish and process the acquired attribute information of the vehicle-mounted system, the software assistant can send a target broadcast to the attribute capture tool. The target broadcast carries the Nanoid identifier. Nanoid is a tool for generating concise, secure and unique identifiers. Among them, the target broadcast carries the Nanoid identifier, which can make the attribute data captured by the attribute capture tool unique, which is convenient for later data processing and analysis. The attribute capture tool sends the captured attribute data to the software assistant, and the software assistant receives the attribute data sent by the attribute capture tool and converts the received attribute data into attribute information. The conversion of attribute data into attribute information can include: converting the attribute data into a String format, and storing it in a json file in the form of a key-value pair Key-Value, that is, obtaining the attribute information, and the interface of the obtained attribute information is concise when displayed.
[0037] Furthermore, obtaining the attribute information of the vehicle-mounted system may also include: uniquely naming the JSON file.
[0038] The target broadcast carries the Nanooid identifier, and the Nanooid identifier is used as the attribute comparison task ID to name the json file, which can accurately find the attribute information corresponding to the vehicle system before and after the OTA upgrade. Each attribute capture is a task, and a unique and non-repetitive Nanooid identifier is used. The Nanooid is carried when the software assistant sends the target broadcast. When the broadcast receiving module in the attribute capture tool receives the broadcast, the Nanooid will be used as the attribute comparison task ID for the naming of the attribute value json file.
[0039] Obviously, attribute capture is the core of the embodiment of the present application. The attribute data in the embodiment of the present application includes the attribute data of the underlying hardware and the system. The attribute data of the system includes the attribute data of the self-developed application and the system native. The attribute capture tool captures the attribute data, including: The attribute capture tool captures the attribute data of the underlying hardware by calling the software development kit SDK of the underlying hardware on the vehicle system; The attribute capture tool captures the attribute data of the self-developed application by calling the SDK of the self-developed application on the vehicle system; The attribute capture tool captures the system's native attribute data by calling the system's native API on the vehicle system.
[0040] In this embodiment, the attribute data captured by the attribute capture tool, that is, the attribute value, divides the attribute value into the underlying hardware attribute value and the system attribute value. Among them, the underlying hardware attribute value directly captures the underlying hardware data by calling the relevant underlying SDK, and there is no need to directly parse the message of the CAN and LIN buses; and the system attribute value is divided into the attribute value of the self-developed application and the attribute value of the vehicle-mounted (Android native) system. The attribute value of the self-developed application needs to call the self-developed SDK to obtain the corresponding configuration, and the attribute value of the Android native system needs to call the system native API to obtain data. All of the above attribute data need to be converted into String type before attribute comparison, and a json file that saves all attribute values is generated in the form of Key-Value.
[0041] Step S102: Start OTA upgrade of the vehicle system.
[0042] Wherein, step S102 may include: Determine the ROM corresponding to the OTA upgrade package according to the trigger operation, and obtain the OTA upgrade package, wherein the trigger operation includes a ROM selection operation; Perform OTA upgrade on the vehicle system based on the obtained OTA upgrade package.
[0043] In the embodiment of the present application, the software assistant deployed on the PC terminal pre-stores multiple ROMs corresponding to the OTA upgrade package, and the OTA upgrade package is obtained by selecting the required ROM on the visual interface. Among them, when the vehicle system and the software assistant of the PC terminal are connected, the OTA upgrade can be implemented. For example, click on OTA upgrade, select the corresponding ROM, and it can be automatically pushed to the vehicle system. After pushing the OTA upgrade package, the OTA upgrade command is automatically generated and executed, and the upgrade is waited for to be completed. After obtaining the attribute information of the vehicle system before the OTA upgrade, the OTA upgrade of the vehicle system is automatically started. After the OTA upgrade is successful, go to step S103 to obtain the attribute information of the vehicle system after the OTA upgrade, so as to compare the attribute information before and after the OTA upgrade of the vehicle system.
[0044] Step S103: After the OTA upgrade is successful, obtain the property information of the vehicle system after the OTA upgrade.
[0045] The OTA upgrade success is used as a trigger condition for obtaining the attribute information of the vehicle system again. After the OTA upgrade is successful, the attribute information of the vehicle system after the OTA upgrade is automatically obtained. The method of obtaining the attribute information of the vehicle system after the OTA upgrade can refer to step S101, which will not be described in detail here.
[0046] Step S104: triggering the execution of the attribute comparison task and displaying the comparison result, wherein the attribute comparison task includes comparing the attribute information before and after the OTA upgrade of the vehicle system.
[0047] In step S104, the execution of the attribute comparison task is triggered and the comparison result is displayed, including: After obtaining the attribute information of the vehicle system after OTA upgrade, compare the attribute information before and after OTA upgrade of the vehicle system according to the Diff command to generate an attribute difference file; Use the Diff2html tool to generate a property difference comparison page for the property difference file.
[0048] In this embodiment, the attribute information obtained after the vehicle system OTA upgrade can be used as a trigger condition for executing the attribute comparison task. After the attribute information after the vehicle system OTA upgrade is obtained, the attribute comparison task is automatically executed. The comparison logic relies on the Diff command. By directly comparing two json files that save the attribute values, a difference string can be generated, and then the Diff2html tool can be used to generate an attribute difference comparison page.
[0049] Further, in step S104, the execution of the attribute comparison task is triggered and the comparison result is displayed, including: marking the difference attributes in the attribute difference comparison page. In this embodiment, the number of attributes is numerous, and the attributes that are different before and after the OTA upgrade can be highlighted by color highlighting, etc., so as to facilitate users to quickly find the problem.
[0050] Preferably, the embodiment of the present application may also include: reporting the relevant data generated when the OTA upgrade test method is executed. The software assistant records the relevant data generated when the OTA upgrade test method is executed and reports it to the cloud server. The relevant data can be used as a test basis and can also provide real and effective quality data. The cloud server can be implemented by the high-performance Python web framework FastAPI, and the relevant data is stored in the relational database MySQL.
[0051] The following is a detailed description with reference to a specific embodiment.
[0052] The embodiment of the present application provides a method for OTA upgrade testing, which involves a PC terminal, a vehicle terminal and a cloud server during execution. The PC terminal and the vehicle terminal are two different terminals, and a software assistant is deployed on the PC terminal, and an attribute capture tool is deployed on the vehicle terminal. The attribute capture tool can be in the form of an Android App, such as Figure 2 shown.
[0053] The attribute capture tool includes a broadcast processing module, an attribute capture module, a background service Service and an APP interface, wherein the broadcast processing module is used to receive broadcasts for capturing attribute values and trigger the capture of attribute values; the attribute capture module is used to capture the attribute values of the vehicle-mounted system; the background service Service is used to reside in the system background to ensure that the App can also work in the background; the App interface is convenient for users to operate on the interface. Among them, the capture logic of attribute values is the most critical. The embodiment of the present application divides attribute values into underlying hardware attribute values and system attribute values. The underlying hardware attribute values directly capture the data of the underlying hardware by calling the relevant underlying SDK, without directly parsing the messages of the CAN and LIN buses. The system attribute values are divided into the attribute values of self-developed applications and the attribute values of the vehicle-mounted (Android native) system. The attribute values of self-developed applications need to call the self-developed SDK to obtain the corresponding configuration; the attribute values of the Android native system need to call the system native API to obtain data. All of the above data need to be finally converted into String type in the software assistant, and a json file that saves all attribute values is generated in the form of Key-Value. It should be noted that each attribute capture is a task, and a unique and non-repetitive Nanoid identifier can be used. The Nanoid is carried when the software assistant sends a broadcast. When the broadcast receiving module receives the broadcast, it will use the Nanoid as the task ID to facilitate the naming and distinction of the attribute value json file.
[0054] The software assistant of the PC terminal, also known as the PC tool software, is written in Electron and the front-end JavaScript framework Vue.js. Electron is an open source framework that uses JavaScript, HTML and CSS to build cross-platform desktop applications. It allows developers to use the front-end technology stack to develop desktop applications. The software assistant integrates the four most critical functions of OTA upgrade, attribute acquisition, attribute comparison and data reporting. For the OTA upgrade function, specifically open the PC tool software. When the vehicle system and the software assistant of the PC terminal are connected, the OTA upgrade can be implemented. For example, click OTA upgrade and select the corresponding ROM, which can be automatically pushed to the vehicle system. After pushing the OTA upgrade package, the OTA upgrade command is automatically generated and executed, and the upgrade is completed. For the attribute acquisition function of the PC terminal, before the OTA upgrade, the PC tool software will push the attribute capture tool to the vehicle system and install it. Then open the interface of the PC tool software and send a broadcast of the captured attributes to the attribute capture tool, which can trigger the attribute capture tool to capture the attribute value to feedback to the PC tool software. After the acquisition is completed, a json file is obtained. Also, after the OTA upgrade is completed, a broadcast is sent to the attribute capture tool to obtain the attribute value once. For the attribute comparison function, after the second attribute acquisition is completed, the attribute value comparison can be triggered. Among them, the comparison logic relies on the Diff command. By directly comparing the two json files that save the attribute values, a difference string can be generated, and then Diff2html can be used to generate a difference comparison page. For the data reporting function, the PC-side tool software will record the relevant data generated during the entire process and report it to the cloud server. The relevant data includes OTA task information, vehicle system attribute information, comparison results, etc. The relevant data can be used as a basis for testing and can also provide real and effective quality data.
[0055] The cloud server is implemented by the FastAPI framework, and the data is stored in MySQL. The main logic includes reporting the environment and attribute acquisition results after the attributes are acquired; reporting the OTA upgrade task information before the OTA upgrade, and reporting the upgrade results (success or failure) after the upgrade is completed; and reporting the attribute comparison results after the comparison.
[0056] The embodiment of the present application can automatically obtain the attribute values required for the OTA upgrade test before and after, and automatically compare the attribute values before and after the OTA upgrade, give a visual comparison result, integrate the OTA upgrade test and attribute inspection process, realize automated testing, and help testers quickly locate the changed attribute values, thereby improving test efficiency and reducing test costs. The entire process does not require human participation, reduces human operation errors, and provides real and accurate quality data. Among them, the automated attribute capture and attribute comparison of the embodiment of the present application greatly saves a lot of manpower. After actual testing, the labor cost can be reduced from 12 people / day to 0.5 people / day.
[0057] It should be emphasized that the attribute capture tool of the embodiment of the present application can automatically capture all vehicle attributes after receiving the broadcast.
[0058] As an optional embodiment of the present application, the functions performed by the OTA upgrade test method provided in the embodiment of the present application can also be integrated into the vehicle terminal. However, the processing power of the vehicle terminal is limited. Therefore, the four most critical functions of OTA upgrade, attribute acquisition, attribute comparison and data reporting can be integrated into the software assistant of the PC terminal, and the broadcast processing module, attribute capture module, background service Service and APP interface are integrated into the attribute capture tool of the vehicle terminal.
[0059] Corresponding to the aforementioned application function implementation method embodiment, the present application also provides an OTA upgrade test device, electronic device and corresponding embodiments.
[0060] Figure 3 It is a structural diagram of the OTA upgrade test device shown in an embodiment of the present application.
[0061] See also Figure 3 The present application embodiment provides an OTA upgrade test device, including: A first attribute acquisition module 301, which is configured to obtain attribute information of the vehicle system before OTA upgrade in response to a trigger operation associated with OTA upgrade; An OTA upgrade module 302 is configured to initiate an OTA upgrade of the vehicle system; A second attribute acquisition module 303 is configured to acquire attribute information of the vehicle system after the OTA upgrade is successful; The attribute comparison module 304 is configured to trigger the execution of an attribute comparison task and display the comparison result, wherein the attribute comparison task includes comparing the attribute information before and after the OTA upgrade of the vehicle system.
[0062] Furthermore, the device may also include a push module, which is configured to push the attribute capture tool to the vehicle system before responding to a trigger operation associated with an over-the-air download technology OTA upgrade, so that the attribute capture tool is deployed in the vehicle system to capture attribute data of the vehicle system.
[0063] In the first attribute acquisition module 301 or the second attribute acquisition module 303, acquiring the attribute information of the vehicle-mounted system may further include: Sending a target broadcast to the attribute crawler, so that the attribute crawler crawls the attribute data after receiving the target broadcast; Receive attribute data sent by the attribute crawler; The attribute data is converted into attribute information. Specifically, the attribute data is converted into a String format and stored in a json file in the form of a key-value pair Key-Value, that is, the attribute information is obtained and the json file is uniquely named.
[0064] The first attribute acquisition module 301, the OTA upgrade module 302, the second attribute acquisition module 303, the attribute comparison module 304 and the push module can all be integrated in the software assistant of the PC terminal.
[0065] Furthermore, the OTA upgrade module 302 may include a configuration unit and an upgrade unit; the configuration unit is configured to determine the ROM corresponding to the OTA upgrade package according to a trigger operation to obtain the OTA upgrade package, wherein the trigger operation includes a ROM selection operation; the upgrade unit is configured to perform OTA upgrade on the vehicle system according to the obtained OTA upgrade package.
[0066] Furthermore, in the attribute comparison module 304, the execution of the attribute comparison task is triggered and the comparison result is displayed, including: After obtaining the attribute information of the vehicle system after OTA upgrade, compare the attribute information before and after OTA upgrade of the vehicle system according to the Diff command to generate an attribute difference file; Use the Diff2html tool to generate a property difference comparison page for the property difference file.
[0067] Furthermore, in the attribute comparison module 304, triggering the execution of the attribute comparison task and displaying the comparison result may further include marking the difference attributes in the attribute difference comparison page.
[0068] Preferably, the device may further include a reporting module, and the reporting module is configured to report relevant data generated when the OTA upgrade test method is executed.
[0069] Furthermore, the device may also include an attribute capture tool, which is deployed on the vehicle terminal. The attribute data includes the attribute data of the underlying hardware and the system, the attribute data of the system includes the attribute data of the self-developed application and the system native, and the attribute capture tool captures the attribute data, including: The attribute capture tool captures the attribute data of the underlying hardware by calling the software development kit SDK of the underlying hardware on the vehicle system; The attribute capture tool captures the attribute data of the self-developed application by calling the SDK of the self-developed application on the vehicle system; The attribute capture tool captures the system's native attribute data by calling the system's native API on the vehicle system.
[0070] Regarding the device in the above embodiment, the specific manner in which each module performs the operation has been described in detail in the embodiment of the method, and will not be elaborated again here.
[0071] Figure 4 It is a schematic diagram of the structure of a car shown in an embodiment of the present application.
[0072] See also Figure 4 , the car 400 includes a memory 401 and a processor 402 .
[0073] The processor 402 may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or the processor may be any conventional processor, etc.
[0074] The memory 401 may include various types of storage units, such as system memory, read-only memory (ROM), and permanent storage devices. Among them, ROM can store static data or instructions required by the processor 402 or other modules of the computer. The permanent storage device may be a readable and writable storage device. The permanent storage device may be a non-volatile storage device that does not lose the stored instructions and data even after the computer is powered off. In some embodiments, the permanent storage device uses a large-capacity storage device (such as a magnetic or optical disk, flash memory) as a permanent storage device. In some other embodiments, the permanent storage device may be a removable storage device (such as a floppy disk, an optical drive). The system memory may be a readable and writable storage device or a volatile readable and writable storage device, such as a dynamic random access memory. The system memory may store some or all instructions and data required by the processor at runtime. In addition, the memory 401 may include any combination of computer-readable storage media, including various types of semiconductor storage chips (such as DRAM, SRAM, SDRAM, flash memory, programmable read-only memory), and disks and / or optical disks may also be used. In some embodiments, the memory 401 may include a readable and / or writable removable storage device, such as a laser disc (CD), a read-only digital versatile disc (such as a DVD-ROM, a double-layer DVD-ROM), a read-only Blu-ray disc, an ultra-density optical disc, a flash memory card (such as an SD card, a mini SD card, a Micro-SD card, etc.), a magnetic floppy disk, etc. Computer-readable storage media do not include carrier waves and transient electronic signals transmitted wirelessly or wired.
[0075] The memory 401 stores executable codes, and when the executable codes are processed by the processor 402 , the processor 402 can execute part or all of the above-mentioned methods.
[0076] In addition, the method according to the present application may also be implemented as a computer program or a computer program product, which includes computer program code instructions for executing some or all of the steps in the above method of the present application.
[0077] Alternatively, the present application can also be implemented as a computer-readable storage medium (or non-transitory machine-readable storage medium or machine-readable storage medium) on which executable code (or computer program or computer instruction code) is stored. When the executable code (or computer program or computer instruction code) is executed by a processor of an electronic device (or server, etc.), the processor executes part or all of the steps of the above-mentioned method according to the present application.
[0078] The embodiments of the present application have been described above, and the above description is exemplary, not exhaustive, and is not limited to the disclosed embodiments. Many modifications and changes will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the described embodiments. The selection of terms used herein is intended to best explain the principles of the embodiments, practical applications, or improvements to the technology in the market, or to enable other persons of ordinary skill in the art to understand the embodiments disclosed herein.
Claims
1. A method for OTA upgrade testing, characterized in that: include: In response to a trigger operation associated with an over-the-air (OTA) upgrade, obtaining attribute information of the vehicle system before the OTA upgrade; Initiating an OTA upgrade of the vehicle system; After the OTA upgrade is successful, obtaining the attribute information of the vehicle system after the OTA upgrade; The execution of an attribute comparison task is triggered and the comparison result is displayed, wherein the attribute comparison task includes comparing the attribute information of the vehicle system before and after the OTA upgrade.
2. The method according to claim 1, characterized in that The method further includes, before responding to a trigger operation associated with an over-the-air (OTA) upgrade: Push the attribute capture tool to the vehicle-mounted system, so that the attribute capture tool is deployed in the vehicle-mounted system to capture the attribute data of the vehicle-mounted system.
3. The method according to claim 2, characterized in that Acquiring attribute information of the vehicle-mounted system, including: Sending a target broadcast to the attribute crawler, so that the attribute crawler crawls the attribute data after receiving the target broadcast; Receiving the attribute data sent by the attribute crawler; The attribute data is converted into the attribute information.
4. The method according to claim 2 or 3, characterized in that: The attribute data includes the attribute data of the underlying hardware and the system, the attribute data of the system includes the attribute data of the self-developed application and the native system, and the attribute capture tool captures the attribute data, including: The attribute capture tool captures the attribute data of the underlying hardware by calling the software development kit SDK of the underlying hardware on the vehicle-mounted system; or, The attribute capture tool captures the attribute data of the self-developed application by calling the SDK of the self-developed application on the vehicle-mounted system; or, The attribute capture tool captures the system's native attribute data by calling the system's native API on the vehicle-mounted system.
5. The method according to claim 3, characterized in that: The converting the attribute data into the attribute information includes: The attribute data is converted into a String format and stored in a json file in the form of a key-value pair Key-Value, thereby obtaining the attribute information.
6. The method according to claim 5, characterized in that Acquiring the attribute information of the vehicle-mounted system also includes: Give the json file a unique name.
7. The method according to claim 1, characterized in that The initiating OTA upgrade of the vehicle system includes: Determine the ROM corresponding to the OTA upgrade package according to the trigger operation, and obtain the OTA upgrade package, wherein the trigger operation includes a ROM selection operation; The vehicle-mounted system is OTA upgraded according to the obtained OTA upgrade package.
8. The method according to claim 1, characterized in that The triggering of the execution of the attribute comparison task and displaying the comparison result includes: After acquiring the attribute information of the vehicle system after the OTA upgrade, comparing the attribute information of the vehicle system before and after the OTA upgrade according to the Diff command to generate an attribute difference file; Use the Diff2html tool to generate an attribute difference comparison page for the attribute difference file.
9. The method according to claim 8, characterized in that The triggering of the execution of the attribute comparison task and displaying the comparison result includes: The difference attributes in the attribute difference comparison page are marked.
10. The method according to claim 1, characterized in that Also includes: Report the relevant data generated when the OTA upgrade test method is executed.
11. An OTA upgrade test device, characterized in that: include: A first attribute acquisition module, configured to acquire attribute information of the vehicle system before OTA upgrade in response to a trigger operation associated with OTA upgrade; An OTA upgrade module, configured to initiate an OTA upgrade of the vehicle system; A second attribute acquisition module, which is configured to obtain attribute information of the vehicle system after the OTA upgrade is successful; The attribute comparison module is configured to trigger the execution of an attribute comparison task and display the comparison result, wherein the attribute comparison task includes comparing the attribute information of the vehicle system before and after the OTA upgrade.
12. A car, characterized in that: include: processor; as well as A memory having executable codes stored thereon, which, when executed by the processor, causes the processor to execute the method according to any one of claims 1 to 10.
13. A computer-readable storage medium, characterized in that: An executable code is stored thereon, and when the executable code is executed by a processor of an electronic device, the processor is caused to execute the method as claimed in any one of claims 1 to 10.