Log collection method and system for OTA upgrade

Abstract

A cloud platform issues an upgrading task, a log acquisition point and a log acquisition item to a vehicle-mounted terminal, and configures a brushing and writing process information acquisition switch, if the brushing and writing process information acquisition switch is configured to be closed, brushing and writing process information acquisition is completed, and if the brushing and writing process information acquisition switch is not configured to be closed, brushing and writing process information acquisition is completed. The vehicle-mounted terminal executes a flashing process according to the upgrading task, in the execution process, logs are generated based on the log collection points and the log collection items and sent to the cloud platform, the cloud platform visually displays the logs, the logs can be automatically collected according to needs in the upgrading process, and the upgrading efficiency is improved after collection. According to the technical scheme, the cloud platform visually displays the logs, even if problems occur in the upgrading process, due to the fact that the logs are collected in different processes in the upgrading process, the problem point can be visually known in the visual display process, and therefore the problem point in the upgrading process can be visually and accurately positioned.

Description

Technical Field

[0001] This invention relates to the field of log collection technology, and in particular to a method and system for collecting logs during OTA upgrades. Background Technology

[0002] As vehicle OTA (Over-The-Air) technology becomes increasingly widespread, there are more and more OTA upgrade programs on the vehicle side, and the number of upgrade problems encountered during OTA upgrades is also increasing. When a vehicle encounters problems during an OTA upgrade, such as the upgrade task being stuck in the download, flashing, or upgrade failure phase, the existing troubleshooting methods usually involve checking the reported fault codes or reporting the entire flashing log. Such methods cannot intuitively identify the problem, nor can they specifically collect log information of the specific code point where the problem occurred. Summary of the Invention

[0003] The technical problem to be solved by this invention is to provide a log collection method and system for OTA upgrades, which can intuitively and accurately locate the problem points in the upgrade process.

[0004] To solve the above-mentioned technical problems, the present invention adopts the following technical solution: A method for collecting logs during OTA upgrades, comprising the following steps: The cloud platform sends upgrade tasks, log collection points, and log collection items to the vehicle terminal and configures the switch for collecting information during the flashing process. If the flashing process information collection switch is configured to be off, the vehicle terminal executes the flashing process according to the upgrade task. During the execution, logs are generated based on the log collection points and log collection items, and the logs are sent to the cloud platform. The cloud platform provides a visual representation of the logs.

[0005] To solve the above-mentioned technical problems, another technical solution adopted by the present invention is as follows: An OTA upgrade log collection system includes a cloud platform and an in-vehicle terminal. The cloud platform includes a first memory, a first processor, and a first computer program stored in the first memory and executable on the first processor. The in-vehicle terminal includes a second memory, a second processor, and a second computer program stored in the second memory and executable on the second processor. When the first processor executes the first computer program, it implements the steps performed by the cloud platform in the above-described OTA upgrade log collection method. When the second processor executes the second computer program, it implements the steps performed by the vehicle terminal in the above-described OTA upgrade log collection method.

[0006] The beneficial effects of this invention are as follows: The cloud platform sends upgrade tasks, log collection points, and log collection items to the vehicle terminal, and configures a flashing process information collection switch. If the flashing process information collection switch is configured to be off, it indicates that the flashing process information collection is complete. The vehicle terminal executes the flashing process according to the upgrade task. During the execution, logs are generated based on the log collection points and log collection items, and the logs are sent to the cloud platform. The cloud platform visualizes the logs. In the process of executing the flashing process, this invention generates logs based on the configured log collection points and log collection items, and can automatically collect logs as needed during the upgrade. After collection, the cloud platform visualizes the logs. Even if problems occur during the upgrade process, since logs have been collected at different stages of the upgrade process, the visualization can intuitively show where the problem is, thus intuitively and accurately locating the problem during the upgrade process. Attached Figure Description

[0007] Figure 1 This is a flowchart illustrating the steps of an OTA upgrade log collection method according to an embodiment of the present invention. Figure 2 This is a schematic diagram of the structure of an OTA upgrade log collection system according to an embodiment of the present invention; Figure 3 This is a flowchart illustrating the overall log collection process in the OTA upgrade log collection method according to an embodiment of the present invention. Figure 4 This is a flowchart illustrating the log collection process during the write operation in the OTA upgrade log collection method of this invention. Detailed Implementation

[0008] To explain in detail the technical content, objectives, and effects of the present invention, the following description is provided in conjunction with the embodiments and accompanying drawings.

[0009] Please refer to Figure 1 A method for collecting logs during OTA upgrades, comprising the following steps: The cloud platform sends upgrade tasks, log collection points, and log collection items to the vehicle terminal and configures the switch for collecting information during the flashing process. If the flashing process information collection switch is configured to be off, the vehicle terminal executes the flashing process according to the upgrade task. During the execution, logs are generated based on the log collection points and log collection items, and the logs are sent to the cloud platform. The cloud platform provides a visual representation of the logs.

[0010] As can be seen from the above description, the beneficial effects of the present invention are as follows: The cloud platform sends upgrade tasks, log collection points, and log collection items to the vehicle terminal, and configures a flashing process information collection switch. If the flashing process information collection switch is configured to be off, it indicates that the flashing process information collection is complete. The vehicle terminal executes the flashing process according to the upgrade task. During the execution, logs are generated based on the log collection points and log collection items, and the logs are sent to the cloud platform. The cloud platform visualizes the logs. In the process of executing the flashing process, the present invention generates logs based on the configured log collection points and log collection items, and can automatically collect logs as needed during the upgrade. After collection, the cloud platform visualizes the logs. Even if problems occur during the upgrade process, since logs have been collected at different stages of the upgrade process, the visualization can intuitively show where the problem is, thereby intuitively and accurately locating the problem in the upgrade process.

[0011] Furthermore, before the cloud platform sends the upgrade task, log collection points, and log collection items to the vehicle terminal, it also includes: The cloud platform parses the source code of the program used for OTA upgrades to obtain the process name of the electronic control unit's flashing process and the name of the collection point under the flashing process. The cloud platform generates the flashing process information based on the process name of the flashing process and the collection point name under the flashing process.

[0012] As described above, one way to generate flashing process information is to parse the source code of the program used for OTA upgrades to obtain the process name of the flashing process of the electronic control unit and the name of the collection point under the flashing process. This way, we can know what flashing processes there are and what collection points are under each flashing process. These are nodes where logs can be collected, which helps to automatically collect logs during the subsequent upgrade process.

[0013] Furthermore, before the cloud platform sends the upgrade task, log collection points, and log collection items to the vehicle terminal and configures the flashing process information collection switch, it also includes: The cloud platform issues an upgrade task with instructions to collect information on the flashing process to the same type of vehicle terminal corresponding to the vehicle terminal. The same type of vehicle terminal executes the flashing process according to the upgrade task. During the execution, the process name of each flashing process and the name of the collection point under each flashing process are collected in the order of execution. The same type of vehicle terminal generates flashing process information based on the process name of each flashing process and the name of the collection point under each flashing process. The cloud platform sends a reporting instruction to the vehicle-mounted terminal of the same type; The same type of vehicle terminal sends the flashing process information to the cloud platform; The cloud platform stores the flashing process information.

[0014] As described above, another way to generate flashing process information is to send an upgrade task with flashing process information collection instructions from the cloud platform to the same type of vehicle terminal corresponding to the vehicle terminal. In this way, the same type of vehicle terminal first executes the flashing process once according to the upgrade task. During this process, no logs are collected, only the process name of each flashing process and the name of the collection point under each flashing process are collected to generate flashing process information. Then, the flashing process information is sent to the cloud platform. The flashing process information generated in this way is more in line with the actual needs of the upgrade task, ensuring the validity of the logs collected later.

[0015] Furthermore, before the cloud platform sends the upgrade task, log collection points, and log collection items to the vehicle terminal and configures the flashing process information collection switch, it also includes: The cloud platform configures a log collection switch for each flashing process based on the process name in the flashing process information. The cloud platform configures each log collection point under each writing process and the parameter values ​​required for each log collection point according to the collection point name in the writing process information. The cloud platform configures the log collection items for each log collection point.

[0016] As described above, the flashing process information includes the names of each process and each collection point. The process names are used to configure log collection switches for each flashing process, indicating whether log collection is required. Knowing the names of each collection point, the log collection points under each flashing process are configured, along with the required parameter values ​​for each collection point. These parameter values ​​determine whether collection can be triggered when the process reaches that collection point. Finally, the log collection items for each collection point are configured, which determine the specific content of the logs to be collected. This allows testers to flexibly configure the process according to actual needs, thereby improving the flexibility and effectiveness of log collection.

[0017] Furthermore, the process of generating logs based on the log collection points and log collection items during execution includes: During the execution process, the vehicle terminal determines whether the log collection switch for each flashing process is turned on. If so, it determines whether the current conditions for log collection are met based on the log collection points under each flashing process and the parameter values ​​required for each log collection point. If the conditions are met, it generates log content based on the log collection items of each log collection point and obtains the log based on the log content.

[0018] As described above, for each flashing process, if the log collection switch for that process is enabled, the system determines whether the current conditions for log collection are met based on the log collection points under that process and the parameter values ​​required for each log collection point. If the conditions are met, log content is generated based on the log collection items of each log collection point, and logs are obtained based on the log content, thus realizing automatic log collection during the upgrade process.

[0019] Furthermore, sending the logs to the cloud platform includes: The vehicle terminal determines whether the size of the log content in the log is greater than a preset size. If so, the log is sent to the cloud platform in file format; otherwise, the log is sent to the cloud platform in content format.

[0020] As described above, the size of the log content determines whether to send the log to the cloud platform in content or file format, thus dynamically selecting the log reporting format.

[0021] Furthermore, the step of sending the logs to the cloud platform also includes: The vehicle terminal obtains the unique code of the upgrade task corresponding to the log and the unique code of the log collection point; The vehicle-mounted terminal sends the unique code of the upgrade task and the unique code of the log collection point to the cloud platform.

[0022] As described above, when sending logs to the cloud platform, the unique code of the upgrade task corresponding to the log and the unique code of the log collection point are also sent to the cloud platform to facilitate log management and subsequent log retrieval and display.

[0023] Furthermore, it also includes: If the log is in content format, the cloud platform stores the log, the unique code of the upgrade task, and the unique code of the log collection point in the database; If the log is in file format, the cloud platform stores the log in file format on the server, and stores the file path of the log, the unique code of the upgrade task, and the unique code of the log collection point in the database.

[0024] As described above, different storage methods are used for different types of logs to facilitate subsequent log retrieval. Logs in content format have a smaller data size and can be directly displayed on the interface, while logs in file format have a larger data size and can be viewed after downloading the file via a file path.

[0025] Furthermore, the cloud platform provides a visual representation of the logs, including: The cloud platform uses a visualization engine to load the flashing process of the electronic control unit corresponding to the upgrade task, the process name of each flashing process, and the log collection points under each flashing process. The cloud platform determines the unique code of the log collection point corresponding to the unique code of the upgrade task from the database; The cloud platform matches the unique code of the log collection point with each log collection point under each writing process, and displays the logs corresponding to the unique code of the log collection point on the matched log collection point.

[0026] As described above, the cloud platform uses a visualization engine to load the flashing process of the electronic control unit corresponding to the upgrade task, the process name of each flashing process, and the log collection points under each flashing process. Then, based on the unique code of the upgrade task, it determines the unique code of the corresponding log collection point from the database. The unique code of the log collection point is matched with the log collection points under each flashing process, and the logs corresponding to the unique code of the log collection point are displayed on the matched log collection points. This can intuitively display each flashing process, each log collection point under each flashing process, and the logs of each log collection point, so that testers can quickly locate the problem.

[0027] Please refer to Figure 2 Another embodiment of the present invention provides an OTA upgrade log collection system, including a cloud platform and an in-vehicle terminal. The cloud platform includes a first memory, a first processor, and a first computer program stored in the first memory and executable on the first processor. The in-vehicle terminal includes a second memory, a second processor, and a second computer program stored in the second memory and executable on the second processor. When the first processor executes the first computer program, it implements the steps performed by the cloud platform in the above-described OTA upgrade log collection method. When the second processor executes the second computer program, it implements the steps performed by the vehicle terminal in the above-described OTA upgrade log collection method.

[0028] The OTA upgrade log collection method and system described above are applicable to OTA upgrade scenarios, and are illustrated below through specific implementation methods: Please refer to Figure 1 , Figure 3 and Figure 4 Embodiment 1 of the present invention is as follows: A method for collecting logs during OTA upgrades, comprising the following steps: S1. The cloud platform sends upgrade tasks, log collection points, and log collection items to the vehicle terminal, and configures the flashing process information collection switch.

[0029] Specifically, the cloud platform creates upgrade tasks in advance based on different electronic control units. Each upgrade task contains a unique code. The upgrade task, log collection points, and log collection items are then sent to the vehicle terminal, and a switch for collecting information during the flashing process is configured.

[0030] In one alternative implementation, before S1, the following is also included: The cloud platform parses the source code of the program used for OTA upgrades to obtain the process name of the ECU flashing process and the name of the collection point under the flashing process. The cloud platform generates flashing process information based on the process name of the flashing process and the collection point name under the flashing process. The program source code for OTA upgrade is installed in the vehicle terminal, and the flashing process information includes the calling relationship of each process.

[0031] In another alternative implementation, such as Figure 3 As shown, before S1, it also includes: The cloud platform issues an upgrade task with instructions to collect information on the flashing process to the same type of vehicle terminal corresponding to the vehicle terminal. The same type of vehicle terminal executes the flashing process according to the upgrade task. During the execution, the process name of each flashing process and the name of the collection point under each flashing process are collected in the order of execution. The same type of vehicle terminal generates flashing process information based on the process name of each flashing process and the name of the collection point under each flashing process. The cloud platform sends a reporting instruction to the vehicle-mounted terminal of the same type; The same type of vehicle terminal sends the flashing process information to the cloud platform; The cloud platform stores the flashing process information.

[0032] Current in-vehicle terminals may also be similar to other in-vehicle terminals, such as... Figure 3 As shown, when the current vehicle terminal receives an upgrade task and the flashing process information collection switch is configured to be on, it indicates that the upgrade task includes a flashing process information collection instruction. The current vehicle terminal then executes the operation steps described above for similar vehicle terminals to generate flashing process information for other vehicle terminals. The flashing process information is presented in a flowchart-like format, showing the call relationships between various processes and the collection points under each process. Each process is identified by its process name, and each collection point is identified by its collection point name.

[0033] In summary, this invention generates flashing process information in two ways. One is that the cloud platform generates it from the beginning by parsing the program source code used for OTA upgrades. The other is that the cloud platform sends an upgrade task with flashing process information collection instructions to a vehicle terminal of the same type as the vehicle terminal, so that the vehicle terminal of the same type performs a flashing process once, generating flashing process information during the execution, and then sending it to the cloud platform for storage. After generating flashing process information using the above methods, the flashing process information collection switch can be configured to be turned off in S1. The two methods of generating flashing process information are more flexible and can be selected according to actual needs. Moreover, the flashing process information does not require manual configuration and can be generated automatically.

[0034] In one alternative implementation, such as Figure 3 As shown, before S1, it also includes: The cloud platform configures a log collection switch for each flashing process based on the process name in the flashing process information. The cloud platform configures each log collection point under each flashing process and the parameter values ​​required for each log collection point according to the collection point name in the flashing process information. The log collection point contains a unique code. The cloud platform configures the log collection items for each log collection point.

[0035] The log collection point can be the name of a function in the call process. The log collection points include different types, and the specific type of the log collection point can be determined according to the classification identifier in the collection point name. Different types of log collection points include: (1) Execution start collection point: This collection point is mainly called before the process starts.

[0036] (2) Execution end collection point: This collection point is mainly called after the process ends. The configuration of this collection point is: collect logs when successful or when unsuccessful. This collection point requires the input of the execution result success / failure indicator. The collection point will dynamically determine whether to collect and report logs based on the configuration of the cloud platform.

[0037] (3) Polling timeout collection point: This collection point is mainly called at the process polling point (for monitoring download, write timeout, etc.). This collection point requires input of the time / number of times the current polling has been completed. The collection point will collect and report logs based on the timeout time threshold / number threshold configured on the cloud platform.

[0038] (4) Exception handling collection point: This collection point is mainly used to trigger after an exception is thrown.

[0039] (5) Specific condition collection point: This collection point mainly requires that logs be collected only when a certain condition value reaches the condition threshold configured by the platform (such as vehicle speed > 30). The comparison operator and condition threshold can be set. This collection point can be used to monitor the number of download retries or the number of write retries.

[0040] (6) Custom collection point: Called in the custom section. The custom section refers to the collection point set by the terminal program without specific rules. It is matched with the platform based on the name.

[0041] Each flashing process is located by its process name in the flashing process information, and its log collection switch is configured to be on or off. On means log collection is required, off means no log collection is required. Then, based on the collection point names in the flashing process information, each log collection point under each flashing process is configured, along with the required parameter values ​​for each log collection point. For example, for a polling timeout collection point, the required parameter values ​​include the current polling time / number of polls and the timeout threshold / number of polls configured on the cloud platform. For a specific condition collection point, the required parameter values ​​include the condition value, the configured condition threshold, and the comparison operator. Next, the log collection items for each log collection point are configured, which may include the current request message, the current response message, the current process's custom flashing log, the current process's entry parameters, the current process's error log, return value, performance logs (including but not limited to CPU usage, memory usage, etc.), and the CAN ID (Controller Area Network Identifier, used to uniquely identify messages in CAN bus communication), service request code, and vehicle DID (Database ID). Identifiers (data identifiers) are used to obtain different data values ​​from the electronic control unit. Request and response messages refer to the request and response messages between the vehicle terminal and the cloud platform, or the request and response messages between the vehicle terminal and the electronic control unit node to be upgraded.

[0042] S2. The vehicle terminal executes the flashing process according to the upgrade task. During the execution, logs are generated based on the log collection points and log collection items, and the logs are sent to the cloud platform. Figure 3 As shown.

[0043] Among them, such as Figure 4 As shown, the process of generating logs based on the log collection points and log collection items during execution includes: During the execution process, the vehicle terminal determines whether the log collection switch for each flashing process is turned on. If so, it determines whether the current conditions for log collection are met based on the log collection points under each flashing process and the parameter values ​​required for each log collection point. If the conditions are met, it generates log content based on the log collection items of each log collection point and obtains the log based on the log content.

[0044] For example, when the vehicle terminal executes process 1, it checks whether the log collection switch for process 1 is set to start. If not, no logs are collected. If so, it determines each log collection point under process 1. Assuming that one of the log collection points is the polling timeout collection point at the process polling point, it checks whether the time consumed by the current polling has reached the timeout threshold. If it has, it generates the corresponding log content based on the log collection item.

[0045] Sending the logs to the cloud platform includes: The vehicle-mounted terminal determines whether the size of the log content in the log is greater than a preset size. If so, it sends the log to the cloud platform as a file; otherwise, it sends the log to the cloud platform as content. In one optional implementation, the preset size is 1000 bytes.

[0046] Sending the logs to the cloud platform also includes: The vehicle terminal obtains the unique code of the upgrade task corresponding to the log and the unique code of the log collection point; The vehicle-mounted terminal sends the unique code of the upgrade task and the unique code of the log collection point to the cloud platform.

[0047] Send the logs, along with the unique codes of their corresponding upgrade tasks and the log collection points, to the cloud platform.

[0048] Following S2, it also includes: If the log is in content format, the cloud platform stores the log, the unique code of the upgrade task, and the unique code of the log collection point in the database; If the log is in file format, the cloud platform stores the log in file format on the server and stores the file path of the log, the unique code of the upgrade task, and the unique code of the log collection point in the database. The file name of the log stored in file format is unique.

[0049] S3. The cloud platform provides a visual display of the logs, specifically including S31-S33: S31. The cloud platform uses a visualization engine to load the flashing process of the electronic control unit corresponding to the upgrade task, the process name of each flashing process, and the log collection points under each flashing process.

[0050] S32. The cloud platform determines the unique code of the log collection point corresponding to the unique code of the upgrade task from the database based on the unique code of the upgrade task.

[0051] S33. The cloud platform matches the unique code of the log collection point with each log collection point under each writing process, and displays the log corresponding to the unique code of the log collection point on the matched log collection point.

[0052] The final display shows the various flashing processes of the upgrade task (represented by process names), the log collection points under each flashing process (represented by collection point names), and the logs collected by each log collection point, so that testers can intuitively view the collected logs and quickly locate the problem points.

[0053] Please refer to Figure 2 Embodiment two of the present invention is as follows: An OTA upgrade log collection system includes a cloud platform and an in-vehicle terminal. The cloud platform includes a first memory, a first processor, and a first computer program stored in the first memory and executable on the first processor. The in-vehicle terminal includes a second memory, a second processor, and a second computer program stored in the second memory and executable on the second processor. When the first processor executes the first computer program, it implements the steps performed by the cloud platform in the above-described OTA upgrade log collection method. When the second processor executes the second computer program, it implements the steps performed by the vehicle terminal in the above-described OTA upgrade log collection method.

[0054] In summary, this invention provides a method and system for collecting logs during OTA upgrades. The cloud platform sends upgrade tasks, log collection points, and log collection items to the vehicle terminal and configures a switch for collecting flashing process information. If the flashing process information collection switch is configured to be off, it indicates that the flashing process information collection is complete. The vehicle terminal executes the flashing process according to the upgrade task. During execution, logs are generated based on the log collection points and log collection items, and these logs are sent to the cloud platform. The cloud platform then visualizes the logs. This invention generates logs based on the configured log collection points and log collection items during the flashing process, enabling it to collect logs as needed during the upgrade. After collection, the cloud platform visualizes the logs. Even if problems occur during the upgrade process, because logs have been collected at different stages of the upgrade process, the visualization clearly shows the location of the problem, allowing for intuitive and accurate identification of issues during the upgrade process. In addition, the cloud platform uses a visualization engine to load the flashing process of the electronic control unit corresponding to the upgrade task, the process name of each flashing process, and the log collection points under each flashing process. Then, based on the unique code of the upgrade task, it determines the unique code of the corresponding log collection point from the database. The unique code of the log collection point is matched with the log collection points under each flashing process, and the logs corresponding to the unique code of the log collection point are displayed on the matched log collection points. This can intuitively display each flashing process, each log collection point under each flashing process, and the logs of each log collection point, so that testers can quickly locate the problem.

[0055] The above description is merely an embodiment of the present invention and does not limit the patent scope of the present invention. Any equivalent modifications made based on the content of the present invention specification and drawings, or direct or indirect applications in related technical fields, are similarly included within the patent protection scope of the present invention.

Claims

1. A method for collecting logs during OTA upgrades, characterized in that, Including the following steps: The cloud platform sends upgrade tasks, log collection points, and log collection items to the vehicle terminal and configures the switch for collecting information during the flashing process. If the flashing process information collection switch is configured to be off, the vehicle terminal executes the flashing process according to the upgrade task. During the execution, logs are generated based on the log collection points and log collection items, and the logs are sent to the cloud platform. The cloud platform provides a visual representation of the logs.

2. The OTA upgrade log collection method according to claim 1, characterized in that, Before the cloud platform sends the upgrade task, log collection points, and log collection items to the vehicle terminal, it also includes: The cloud platform parses the source code of the program used for OTA upgrades to obtain the process name of the electronic control unit's flashing process and the name of the collection point under the flashing process. The cloud platform generates the flashing process information based on the process name of the flashing process and the collection point name under the flashing process.

3. The OTA upgrade log collection method according to claim 1, characterized in that, Before the cloud platform sends the upgrade task, log collection points, and log collection items to the vehicle terminal and configures the flashing process information collection switch, it also includes: The cloud platform issues an upgrade task with instructions to collect information on the flashing process to the same type of vehicle terminal corresponding to the vehicle terminal. The same type of vehicle terminal executes the flashing process according to the upgrade task. During the execution, the process name of each flashing process and the name of the collection point under each flashing process are collected in the order of execution. The same type of vehicle terminal generates flashing process information based on the process name of each flashing process and the name of the collection point under each flashing process. The cloud platform sends a reporting instruction to the vehicle-mounted terminal of the same type; The same type of vehicle terminal sends the flashing process information to the cloud platform; The cloud platform stores the flashing process information.

4. A log collection method for OTA upgrades according to claim 2 or 3, characterized in that, Before the cloud platform sends the upgrade task, log collection points, and log collection items to the vehicle terminal and configures the flashing process information collection switch, it also includes: The cloud platform configures a log collection switch for each flashing process based on the process name in the flashing process information. The cloud platform configures each log collection point under each writing process and the parameter values ​​required for each log collection point according to the collection point name in the writing process information. The cloud platform configures the log collection items for each log collection point.

5. The OTA upgrade log collection method according to claim 4, characterized in that, The process of generating logs based on the log collection points and log collection items during execution includes: During the execution process, the vehicle terminal determines whether the log collection switch for each flashing process is turned on. If so, it determines whether the current conditions for log collection are met based on the log collection points under each flashing process and the parameter values ​​required for each log collection point. If the conditions are met, it generates log content based on the log collection items of each log collection point and obtains the log based on the log content.

6. The OTA upgrade log collection method according to claim 1, characterized in that, Sending the logs to the cloud platform includes: The vehicle terminal determines whether the size of the log content in the log is greater than a preset size. If so, the log is sent to the cloud platform in file format; otherwise, the log is sent to the cloud platform in content format.

7. The OTA upgrade log collection method according to claim 6, characterized in that, Sending the logs to the cloud platform also includes: The vehicle terminal obtains the unique code of the upgrade task corresponding to the log and the unique code of the log collection point; The vehicle-mounted terminal sends the unique code of the upgrade task and the unique code of the log collection point to the cloud platform.

8. The OTA upgrade log collection method according to claim 7, characterized in that, Also includes: If the log is in content format, the cloud platform stores the log, the unique code of the upgrade task, and the unique code of the log collection point in the database; If the log is in file format, the cloud platform stores the log in file format on the server, and stores the file path of the log, the unique code of the upgrade task, and the unique code of the log collection point in the database.

9. The OTA upgrade log collection method according to claim 8, characterized in that, The cloud platform provides a visual representation of the logs, including: The cloud platform uses a visualization engine to load the flashing process of the electronic control unit corresponding to the upgrade task, the process name of each flashing process, and the log collection points under each flashing process. The cloud platform determines the unique code of the log collection point corresponding to the unique code of the upgrade task from the database; The cloud platform matches the unique code of the log collection point with each log collection point under each writing process, and displays the logs corresponding to the unique code of the log collection point on the matched log collection point.

10. An OTA (Over-The-Air) upgrade log collection system, comprising a cloud platform and an in-vehicle terminal, wherein the cloud platform includes a first memory, a first processor, and a first computer program stored in the first memory and executable on the first processor, and the in-vehicle terminal includes a second memory, a second processor, and a second computer program stored in the second memory and executable on the second processor, characterized in that, When the first processor executes the first computer program, it implements the steps of the cloud platform as described in the log collection method for OTA upgrades as claimed in any one of claims 1-9; When the second processor executes the second computer program, it implements the steps performed by the vehicle terminal in the log collection method for OTA upgrade as described in any one of claims 1-9.

Images