An optimization method for OTA upgrade and related device
By detecting the daily restart conditions of the vehicle communication terminal and controlling the upgrade tasks of the OTA component, the problems of file corruption and system bugs caused by daily restarts during the OTA upgrade process are solved, thus achieving the stability and reliability of OTA upgrades.
Patent Information
- Application Number
- CN202310843810.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2023-07-10
- Publication Date
- 2026-02-03
- Estimated Expiration
- 2043-07-10
AI Technical Summary
During OTA upgrades, the daily restarts of the vehicle communication terminal can lead to corrupted upgrade files or system bugs, a problem that is difficult to avoid effectively with current technology.
By acquiring the upgrade disk plan, detecting the daily restart conditions, controlling the upgrade tasks of the OTA components, and avoiding conflicts between the upgrade tasks and the daily restart, including stopping or disconnecting the upgrade network channel when the first engine shutdown signal is detected, sending a lock-up failure signal to exit the upgrade mode, and executing the upgrade task normally when the daily restart conditions are not met.
It improves the stability of OTA upgrade tasks when the vehicle communication terminal restarts, avoids upgrade file corruption and system bugs, and ensures normal updates of vehicle firmware or software systems.
Smart Images

Figure CN116708395B_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of automotive electronic control technology, and in particular to an optimization method and related equipment for OTA upgrades. Background Technology
[0002] OTA (Over-the-Air Technology) updates and upgrades vehicle systems by downloading software update packages from remote cloud servers over the network. It is a powerful technology that can upgrade systems without data loss. Both vehicle firmware and software upgrades can be completed via OTA, so the stability of OTA upgrades is of paramount importance. Summary of the Invention
[0003] This application provides an optimized method for OTA upgrades, which can improve the stability of OTA upgrade tasks when encountering daily restarts of the vehicle communication terminal.
[0004] The first aspect of this application provides an optimized method for OTA (Over-The-Air) upgrades for in-vehicle communication terminals, the method comprising:
[0005] Obtain the upgrade disk installation plan for OTA components, wherein the upgrade disk installation plan includes the upgrade appointment time;
[0006] The daily restart condition of the vehicle communication terminal is detected based on the upgrade appointment time;
[0007] Based on the aforementioned daily restart conditions, the upgrade task of the OTA component is controlled.
[0008] Optionally, the daily restart condition includes a first engine shutdown signal, which indicates the moment when the vehicle first loses power on that day. The step of controlling the OTA component upgrade task based on the daily restart condition includes:
[0009] Upon detecting the first engine shutdown signal, the OTA component upgrade task is aborted.
[0010] Optionally, the step of suspending the OTA component upgrade task upon detecting the first engine shutdown signal includes:
[0011] Upon detecting the first engine shutdown signal, the upgrade network channel of the OTA component is disconnected to abort the OTA component upgrade task.
[0012] Optionally, the step of suspending the OTA component upgrade task upon detecting the first engine shutdown signal includes:
[0013] Upon detecting the first engine shutdown signal, a lock-holding failure data signal is sent to the OTA component to cause the OTA component to exit the upgrade mode based on the lock-holding failure data signal.
[0014] Optionally, the upgrade disk installation plan includes an estimated upgrade time, following the step of suspending the OTA component upgrade task.
[0015] Also includes:
[0016] The estimated upgrade time will be sent to the mobile terminal belonging to the vehicle.
[0017] The upgrade appointment time is redefined based on the upgrade appointment time instruction issued by the mobile terminal.
[0018] Optionally, the upgrade disk disposal scheme includes multiple sets of upgrade tasks, each set of upgrade tasks including multiple sets of objects to be upgraded and corresponding upgrade times.
[0019] Also includes:
[0020] If the daily restart conditions are not met, send the multiple sets of upgrade tasks to the mobile terminal to which the vehicle belongs;
[0021] The upgrade task is executed based on the selection instruction sent by the mobile terminal. The selection instruction is used to select at least one group of objects to be upgraded and their corresponding upgrade times or to abort the upgrade task.
[0022] Optionally, sending the multiple sets of upgrade tasks to the mobile terminal to which the vehicle belongs includes:
[0023] Obtain the version number of the object to be upgraded;
[0024] The multiple sets of upgrade tasks are classified according to the version number;
[0025] The multiple sets of upgrade tasks are generated in a sequential order based on their levels and corresponding upgrade times, and then sent to the mobile terminal to which the vehicle belongs.
[0026] A second aspect of this application provides an OTA upgrade optimization device for an in-vehicle communication terminal, the device comprising:
[0027] The acquisition unit is used to acquire the upgrade disk landing scheme of the OTA component, wherein the upgrade disk landing scheme includes the upgrade appointment time;
[0028] The detection unit is used to detect the daily restart conditions of the vehicle communication terminal based on the upgrade appointment time;
[0029] The control unit is used to control the upgrade task of the OTA component based on the daily restart conditions.
[0030] Optionally, the daily restart condition includes a first engine shutdown signal, which indicates the moment the vehicle first loses power on that day. Based on the daily restart condition, the OTA component's upgrade task is controlled.
[0031] The detection unit is also used to abort the OTA component upgrade task when the first engine shutdown signal is detected.
[0032] Optionally, upon detecting the first engine shutdown signal, the OTA component upgrade task is aborted.
[0033] The control unit is further configured to disconnect the upgrade network channel of the OTA component to terminate the upgrade task of the OTA component upon detecting the first engine shutdown signal.
[0034] Optionally, upon detecting the first engine shutdown signal, the OTA component upgrade task is aborted.
[0035] The control unit is further configured to send a lock-holding failure data signal to the OTA component upon detecting the first engine shutdown signal, so that the OTA component exits the upgrade mode based on the lock-holding failure data signal.
[0036] Optionally, the upgrade disk installation plan includes an estimated upgrade time, following the step of suspending the OTA component upgrade task.
[0037] Also includes:
[0038] A determining unit is used to send the estimated upgrade time to the mobile terminal to which the vehicle belongs;
[0039] The upgrade appointment time is redefined based on the upgrade appointment time instruction issued by the mobile terminal.
[0040] Optionally, the upgrade disk disposal scheme includes multiple sets of upgrade tasks, each set of upgrade tasks including multiple sets of objects to be upgraded and corresponding upgrade times.
[0041] Also includes:
[0042] The sending unit is used to send the multiple sets of upgrade tasks to the mobile terminal to which the vehicle belongs if the daily restart conditions are not met.
[0043] The execution unit executes the upgrade task based on the selection instruction sent by the mobile terminal. The selection instruction is used to select at least one group of objects to be upgraded and their corresponding upgrade times or to abort the upgrade task.
[0044] Optionally, the sending unit is used to send the multiple sets of upgrade tasks to the mobile terminal to which the vehicle belongs, including:
[0045] Obtain the version number of the object to be upgraded;
[0046] The multiple sets of upgrade tasks are classified according to the version number;
[0047] The multiple sets of upgrade tasks are generated in a sequential order based on their levels and corresponding upgrade times, and then sent to the mobile terminal to which the vehicle belongs.
[0048] A third aspect of this application provides an electronic device, which includes at least one processor and at least one memory connected to the processor, wherein the processor is configured to call program instructions in the memory to execute an OTA upgrade optimization method as described in any of the first aspects.
[0049] A fourth aspect of this application provides a storage medium including a stored program, wherein, when the program is executed, it controls the device where the storage medium is located to perform an OTA upgrade optimization method as described in any of the first aspects.
[0050] In summary, this application provides an optimized OTA upgrade method that obtains an OTA component upgrade disk placement scheme, the upgrade disk placement scheme including an upgrade appointment time; detecting the daily restart condition of the vehicle communication terminal based on the upgrade appointment time; and controlling the OTA component upgrade task based on the daily restart condition. When the vehicle communication terminal checks whether the daily restart condition is met based on the user-set OTA upgrade appointment time, if a conflict occurs between a non-fixed-time daily restart and a relatively fixed-time OTA upgrade task, and the vehicle communication terminal's daily restart condition is met, the vehicle communication terminal will stop the upgrade task before the OTA component downloads the upgrade file value to avoid file corruption or system bugs caused by forced interruption of the upgrade file download. If the vehicle communication terminal's daily restart condition is not met, the OTA component upgrade task will be executed normally to complete the normal update of the vehicle firmware or software system.
[0051] Correspondingly, the OTA upgrade optimization device, electronic device, and computer-readable storage medium provided in the embodiments of this application also have the above-mentioned technical effects. Attached Figure Description
[0052] Various other advantages and benefits will become apparent to those skilled in the art upon reading the following detailed description of preferred embodiments. The accompanying drawings are for illustrative purposes only and are not intended to limit the scope of this application. Furthermore, the same reference numerals denote the same parts throughout the drawings. In the drawings:
[0053] Figure 1 A schematic flowchart illustrating a possible optimized method for OTA upgrades provided in an embodiment of this application;
[0054] Figure 2 A schematic structural block diagram of a possible OTA upgrade optimization device provided in this application embodiment;
[0055] Figure 3 A schematic diagram of the hardware structure of a possible OTA upgrade optimization device provided in an embodiment of this application;
[0056] Figure 4 A schematic structural block diagram of a possible electronic device provided in an embodiment of this application;
[0057] Figure 5 This is a schematic structural block diagram of a possible computer-readable storage medium provided for embodiments of this application. Detailed Implementation
[0058] This application provides an optimized method and related equipment for OTA upgrades, which can improve the stability of OTA upgrade tasks when encountering daily restarts of vehicle communication terminals.
[0059] The terms "first," "second," "third," "fourth," etc. (if present) in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus. The technical solutions of the embodiments of this application will now be clearly and completely described in conjunction with the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of them.
[0060] The in-vehicle communication terminal, also known as the in-vehicle TBOX (Telematics Box), is an intelligent in-vehicle terminal that can exchange vehicle data with remote automotive service providers and receive commands from user mobile terminals to control the vehicle. It performs a large amount of data interaction daily, resulting in a significant amount of cached data, which can slow down the normal operation of the in-vehicle TBOX. Daily restarts can clear the daily cache to ensure the operating speed of the in-vehicle TBOX. However, since the timing of the daily restart depends on the first power-off of the vehicle and is not fixed, and OTA (Over-The-Air) updates can upgrade the vehicle firmware and in-vehicle software system, if the in-vehicle TBOX restarts during the OTA download process, the TBOX will not interrupt the OTA download process normally, which may lead to corruption of the downloaded upgrade files or cause system bugs (malfunctions).
[0061] Therefore, there is an urgent need to provide an optimization method and related equipment for OTA upgrades to at least solve the above-mentioned technical problems.
[0062] Firstly, please refer to Figure 1 This is a schematic flowchart of an optimization method for OTA upgrade provided in an embodiment of this application, which may specifically include: S110-S130.
[0063] S110, obtain the upgrade disk solution for OTA components.
[0064] For example, the in-vehicle TBOX can obtain OTA upgrade disk download solutions. An upgrade disk download solution refers to the process of downloading upgrade files from the vehicle's TSP (Telematics Service Provider) platform or the OTA cloud platform to the local machine. The aforementioned upgrade disk download solution includes an upgrade appointment time, which can be set by the user or by the system default.
[0065] S120 detects the daily restart conditions of the vehicle communication terminal based on the upgrade appointment time.
[0066] For example, a daily reboot refers to a system restart performed once a day by the vehicle's TBOX. The process includes clearing the cache, restarting, and then hibernating. The timing of the daily reboot is not fixed and depends on the vehicle's first power-off time that day. The upgrade scheduling time, however, is usually set relatively fixed by the user. When the upgrade scheduling time conflicts with the daily reboot time, such as when the OTA component is downloading upgrade files during the cache clearing phase of the daily reboot, the download process is forcibly interrupted. Since downloading upgrade files typically takes a long time, the vehicle TBOX will restart after clearing the cache, before the download is complete. A reboot of the vehicle TBOX at this point could lead to corrupted download files or system bugs. The vehicle TBOX can detect the daily reboot condition when the upgrade scheduling time arrives and is about to download upgrade files. Based on whether there is a conflict between the upgrade scheduling time and the daily reboot, it can take appropriate action to avoid forcibly interrupting the upgrade file download process.
[0067] S130 controls the upgrade tasks of OTA components based on daily restart conditions.
[0068] For example, if the in-vehicle TBOX meets the daily restart conditions, and the aforementioned upgrade appointment time conflicts with the daily restart, the in-vehicle TBOX can control the OTA component to suspend the upgrade task. Specifically, when the upgrade appointment time arrives, the in-vehicle TBOX can check whether the daily restart conditions are met. If they are met, the OTA component's upgrade task can be suspended to avoid the OTA component being forcibly interrupted halfway through downloading the upgrade file by the in-vehicle TBOX restart. If the daily restart conditions are not met, the OTA component can be controlled to perform the upgrade task normally and download the upgrade file.
[0069] According to the above embodiment, an optimized OTA upgrade method is provided. Based on the user-set OTA upgrade appointment time, the vehicle TBOX checks whether the daily restart condition is met. If a conflict occurs between a daily restart at an irregular time and an OTA upgrade task with a relatively fixed time, and the daily restart condition of the vehicle TBOX is met, the vehicle TBOX will stop the upgrade task before the OTA component downloads the upgrade file value to avoid file corruption or system bugs caused by the forced interruption of the upgrade file download. If the daily restart condition of the vehicle TBOX is not met, the OTA component upgrade task will be executed normally to complete the normal update of the vehicle firmware or software system.
[0070] According to some embodiments, the aforementioned daily restart conditions include a first shutdown signal, which characterizes the moment when the vehicle is first powered down on that day. The control of the OTA component upgrade task based on the aforementioned daily restart conditions includes:
[0071] Upon detecting the first engine shutdown signal, the OTA component upgrade task is aborted.
[0072] For example, the vehicle-mounted TBOX can determine whether the daily restart condition is met by detecting the vehicle's first ignition shutdown signal. The first ignition shutdown signal can be used to indicate the moment when the vehicle is first powered off that day. If the first ignition shutdown signal is detected when the aforementioned upgrade appointment time arrives, the vehicle-mounted TBOX can determine that the daily restart and the OTA component upgrade task conflict at this time, thereby suspending the OTA component upgrade task to avoid file corruption or system bugs caused by the forced interruption of the download of upgrade files. It is easy to understand that, in some cases, after detecting the vehicle's first ignition shutdown signal, it can further check for the absence of messages on the vehicle's CAN (Controller Area Network) bus to improve the accuracy of the daily restart condition judgment and avoid suspending the OTA component upgrade task when the daily restart condition is not met.
[0073] According to some embodiments, the above-mentioned termination of the OTA component upgrade task upon detecting the first engine shutdown signal includes:
[0074] Upon detecting the aforementioned first engine shutdown signal, the upgrade network channel of the aforementioned OTA component is disconnected to terminate the upgrade task of the aforementioned OTA component.
[0075] For example, upon detecting the first engine shutdown signal, the vehicle TBOX can disconnect the upgrade network channel of the OTA component, preventing the OTA component from downloading upgrade files. This avoids the OTA component being interrupted by the vehicle TBOX restarting during the download process, thus preventing file corruption or system bugs.
[0076] According to some embodiments, the above-mentioned termination of the OTA component upgrade task upon detecting the first engine shutdown signal includes:
[0077] Upon detecting the aforementioned first engine shutdown signal, a lock-holding failure data signal is sent to the aforementioned OTA component, causing the aforementioned OTA component to exit the upgrade mode based on the aforementioned lock-holding failure data signal.
[0078] For example, when the first engine shutdown signal is detected, the vehicle TBOX can send a lock failure data signal to the OTA component. The aforementioned lock state is used to indicate that the vehicle TBOX is kept awake. The lock failure means that the vehicle TBOX needs to be restarted daily and cannot be kept awake, thereby causing the OTA component to exit the upgrade mode. This avoids the OTA component being interrupted by the vehicle TBOX's daily restart during the download of upgrade files, which could cause file corruption or system bugs.
[0079] According to some embodiments, the above-described upgrade disk installation scheme includes an estimated upgrade time, following the step of suspending the upgrade task of the above-described OTA component.
[0080] Also includes:
[0081] Send the estimated upgrade time to the mobile terminal associated with the vehicle;
[0082] The upgrade appointment time is redefined based on the upgrade appointment time instruction issued by the aforementioned mobile terminal.
[0083] For example, when the upgrade appointment time of the OTA component conflicts with the daily restart time of the vehicle TBOX, the OTA component upgrade task is suspended, and then the estimated upgrade time in the upgrade disk solution is sent to the vehicle user's mobile terminal. The user can issue an upgrade appointment time instruction based on the estimated upgrade time, and the vehicle TBOX can re-determine the next upgrade appointment time based on the upgrade appointment time instruction.
[0084] According to the above embodiment, an optimized method for OTA upgrades is provided. Due to the conflict between the daily reboot and the original upgrade appointment time, in order to avoid the OTA component being interrupted by the daily reboot of the vehicle TBOX during the download of upgrade files, resulting in file corruption or system bugs and the termination of the upgrade task, in order to allow the vehicle to be upgraded again at a suitable time, the estimated upgrade time of this upgrade can be sent to the vehicle user's mobile terminal. The user can reschedule the next upgrade appointment time based on the estimated upgrade time, so that the vehicle's firmware or software system can be updated as soon as possible.
[0085] According to some embodiments, the above-described upgrade disk disposal scheme includes multiple sets of upgrade tasks, each set of upgrade tasks including multiple sets of objects to be upgraded and corresponding upgrade times.
[0086] Also includes:
[0087] If the above-mentioned daily restart conditions are not met, send the above-mentioned multiple sets of upgrade tasks to the mobile terminal to which the vehicle belongs;
[0088] The upgrade task is executed based on the selection instruction sent by the mobile terminal. The selection instruction is used to select at least one group of objects to be upgraded and their corresponding upgrade times or to abort the upgrade task.
[0089] For example, if the scheduled upgrade time has arrived and the vehicle TBOX does not meet the daily restart conditions, an OTA component upgrade task can be performed. It is easy to understand that OTA upgrades include vehicle firmware and software systems. It is possible that a single upgrade task includes updates to multiple different upgrade objects. At the same time, different upgrade objects also correspond to different file packages. Different file packages occupy different storage capacities, so the upgrade time required is also different.
[0090] It can be explained that since the OTA component upgrade task needs to be performed when the vehicle is turned off, and the time when the vehicle user will restart the vehicle after turning off the engine is difficult to determine, multiple sets of upgrade tasks can be sent to the vehicle user's mobile terminal before downloading the upgrade file. This allows the user to select based on the upgrade time corresponding to different upgrade objects and issue a selection command based on the selection. The OTA component will then execute the upgrade task according to the selection command. For example, if the vehicle is expected to be started in 1 hour, one or more upgrade objects can be selected for upgrade, and the upgrade time is within 1 hour. In other cases, if the upgrade time of the above multiple upgrade objects is generally long, or if the user will restart the vehicle in a short period of time, a selection command to stop the upgrade task can be issued to make the OTA component stop the upgrade task.
[0091] According to the above embodiment, an optimization method for OTA upgrades is provided. Based on the selection command issued by the vehicle user's mobile terminal, at least one of multiple upgrade tasks can be selected to perform an upgrade or abort the upgrade task. This allows the vehicle user to select at least one of multiple upgrade tasks or abort the upgrade task according to the time when the vehicle restarts. This can avoid file corruption or system bugs caused by the sudden interruption of the upgrade task due to the vehicle suddenly restarting before the OTA upgrade task is completed.
[0092] According to some embodiments, sending the aforementioned multiple sets of upgrade tasks to the mobile terminal to which the vehicle belongs includes:
[0093] Obtain the version number of the object to be upgraded;
[0094] Based on the aforementioned version numbers, the above-mentioned multiple sets of upgrade tasks are classified into different levels;
[0095] Based on the order of the multiple upgrade tasks generated according to their levels and corresponding upgrade times, the multiple upgrade tasks are sent to the mobile terminal to which the vehicle belongs.
[0096] For example, the vehicle-mounted TBOX can obtain the current version number of the upgrade object corresponding to multiple sets of upgrade tasks, compare the current version number with the version number to be upgraded, and classify the multiple sets of upgrade tasks based on the comparison results.
[0097] It can be noted that some upgrade tasks may have older version numbers due to a lack of updates over a long period of time, thus making the upgrade more urgent and correspondingly higher in level. Alternatively, if the version to be upgraded is more important, the corresponding level may also be increased.
[0098] Multiple upgrade tasks sent to vehicle users' mobile terminals can be arranged in order based on the upgrade task level and corresponding upgrade time. Higher-level upgrade tasks are placed at the top so that users can notice them first. At the same time, for upgrade tasks of the same level but different times, the one with the shorter upgrade time can be placed at the top so that users can select it first.
[0099] According to the above embodiment, an optimization method for OTA upgrades is provided. The level of multiple upgrade tasks is determined based on the current version number of multiple upgrade tasks, and the upgrade tasks are arranged in order of level and corresponding upgrade time to prompt the user. This allows the user to prioritize the upgrade of more urgent items within a limited upgrade time, which saves time and improves the stability of the vehicle firmware system and software system.
[0100] The optimization method for OTA upgrades has been described above. The optimization device for OTA upgrades in the embodiments of this application is described below.
[0101] Please see Figure 2 One embodiment of the OTA upgrade optimization device described in this application may include:
[0102] The acquisition unit 201 is used to acquire the upgrade disk landing scheme of the OTA component, the upgrade disk landing scheme including the upgrade appointment time;
[0103] Detection unit 202 is used to detect the daily restart conditions of the above-mentioned vehicle communication terminal based on the above-mentioned upgrade appointment time;
[0104] Control unit 203 is used to control the upgrade task of the above-mentioned OTA component based on the above-mentioned daily restart conditions.
[0105] According to the OTA upgrade optimization device provided in the above embodiment, the vehicle TBOX checks whether the daily restart condition is met based on the OTA upgrade appointment time set by the user. If the daily restart at an irregular time conflicts with the OTA upgrade task with a relatively fixed time, and the daily restart condition of the vehicle TBOX is met, the vehicle TBOX will stop the upgrade task before the OTA component downloads the upgrade file value, so as to avoid file corruption or system bugs caused by the forced interruption of the download of the upgrade file. If the daily restart condition of the vehicle TBOX is not met, the OTA component upgrade task will be executed normally to complete the normal update of the vehicle firmware or software system.
[0106] above Figure 2 The OTA upgrade optimization device in the embodiments of this application has been described from the perspective of modular functional entities. The following is a detailed description of the OTA upgrade optimization device in the embodiments of this application from the perspective of hardware processing. Please refer to [link / reference]. Figure 3The hardware structure diagram of an OTA upgrade optimization device provided in this application embodiment includes:
[0107] The system includes an input device 301, an output device 302, a processor 303, and a memory 304, wherein the number of processors 303 can be one or more. Figure 3 Taking a processor 303 as an example. In some embodiments of this application, the input device 301, output device 302, processor 303, and memory 304 can be connected via a bus or other means, wherein... Figure 3 Taking the example of a connection between China and Israel via a bus.
[0108] Specifically, by calling the operation instructions stored in memory 304, processor 303 is used to execute the steps of the above-mentioned OTA upgrade optimization method as proposed in any of the first aspects above.
[0109] For specific implementation details, please refer to [link / reference]. Figure 4 , Figure 4 This is a schematic structural block diagram of an electronic device provided in an embodiment of this application. When the processor 420 executes the computer program 411 in the memory 410, it can achieve... Figure 1 Any one of the corresponding implementation methods in the embodiments. Since the electronic device described in this embodiment is a device used to implement a system resource management device in the embodiments of this application, those skilled in the art can understand the specific implementation method and its various variations of the electronic device in this embodiment based on the method described in the embodiments of this application. Therefore, how the electronic device implements the method in the embodiments of this application will not be described in detail here. Any device used by those skilled in the art to implement the method in the embodiments of this application falls within the scope of protection of this application.
[0110] Please see Figure 5 , Figure 5 This is a schematic diagram illustrating an embodiment of a computer-readable storage medium provided in this application.
[0111] like Figure 5 As shown, this embodiment provides a computer-readable storage medium 500 on which a computer program 511 is stored. When the computer program 511 is executed by a processor, it implements the steps of the OTA upgrade optimization method as proposed in any of the first aspects above.
[0112] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create a machine for implementing the flowchart illustrations. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.
[0113] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.
[0114] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.
[0115] This application also provides a computer program product, which includes computer software instructions that, when executed on a processing device, cause the processing device to perform actions such as... Figure 1 The process of the OTA upgrade optimization method in the corresponding embodiment.
[0116] The aforementioned computer program product includes one or more computer instructions. When the aforementioned computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The aforementioned computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The aforementioned computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the aforementioned computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The aforementioned computer-readable storage medium may be any available medium that a computer can store or a data storage device such as a server or data center that integrates one or more available media. The aforementioned available media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., DVDs), or semiconductor media (e.g., solid-state disks (SSDs)).
[0117] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.
[0118] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of the units described above is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection between devices or units through some interfaces, and may be electrical, mechanical, or other forms.
[0119] The units described above as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.
[0120] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.
[0121] If the aforementioned integrated units are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.
[0122] The above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the foregoing embodiments, or make equivalent substitutions for some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application.
Claims
1. An optimization method for OTA upgrades, characterized in that, For use in vehicle-mounted communication terminals, including: Obtain the upgrade disk installation plan for OTA components, wherein the upgrade disk installation plan includes the upgrade appointment time; Based on the upgrade appointment time, the daily restart condition of the vehicle communication terminal is detected. The daily restart condition includes the first shutdown signal, which can characterize the moment when the vehicle is first powered off on the same day. Based on the aforementioned daily restart conditions, control the upgrade tasks of the OTA component; The step of controlling the OTA component upgrade task based on the daily restart condition includes: suspending the OTA component upgrade task upon detecting the first engine shutdown signal.
2. The method according to claim 1, characterized in that, The step of suspending the OTA component upgrade task upon detecting the first engine shutdown signal includes: Upon detecting the first engine shutdown signal, the upgrade network channel of the OTA component is disconnected to abort the OTA component upgrade task.
3. The method according to claim 1, characterized in that, The step of suspending the OTA component upgrade task upon detecting the first engine shutdown signal includes: Upon detecting the first engine shutdown signal, a lock-holding failure data signal is sent to the OTA component to cause the OTA component to exit the upgrade mode based on the lock-holding failure data signal.
4. The method according to any one of claims 1 to 3, characterized in that, The upgrade disk installation plan includes an estimated upgrade time, following the step of suspending the OTA component upgrade task. The method further includes: The estimated upgrade time will be sent to the mobile terminal belonging to the vehicle. The upgrade appointment time is redefined based on the upgrade appointment time instruction issued by the mobile terminal.
5. The method according to claim 1, characterized in that, The upgrade disk disposal plan includes multiple sets of upgrade tasks, each set of upgrade tasks comprising multiple sets of objects to be upgraded and corresponding upgrade times. The method further includes: If the daily restart conditions are not met, send the multiple sets of upgrade tasks to the mobile terminal to which the vehicle belongs; The upgrade task is executed based on the selection instruction sent by the mobile terminal. The selection instruction is used to select at least one group of objects to be upgraded and their corresponding upgrade times or to abort the upgrade task.
6. The method according to claim 5, characterized in that, Sending the multiple sets of upgrade tasks to the mobile terminal to which the vehicle belongs includes: Obtain the version number of the object to be upgraded; The multiple sets of upgrade tasks are classified according to the version number; The multiple sets of upgrade tasks are generated in a sequential order based on their levels and corresponding upgrade times, and then sent to the mobile terminal to which the vehicle belongs.
7. An optimization device for OTA upgrades, characterized in that, For use in vehicle-mounted communication terminals, including: The acquisition unit is used to acquire the upgrade disk landing scheme of the OTA component, wherein the upgrade disk landing scheme includes the upgrade appointment time; The detection unit is used to detect the daily restart conditions of the vehicle communication terminal based on the upgrade appointment time. The daily restart conditions include the first shutdown signal, which can characterize the moment when the vehicle is first powered off on the same day. A control unit is configured to control the upgrade task of the OTA component based on the daily restart condition, wherein controlling the upgrade task of the OTA component based on the daily restart condition includes: suspending the upgrade task of the OTA component upon detecting the first engine shutdown signal.
8. An electronic device, characterized in that, The electronic device includes at least one processor and at least one memory connected to the processor, wherein the processor is configured to call program instructions in the memory to execute the OTA upgrade optimization method as described in any one of claims 1 to 6.
9. A storage medium, characterized in that, The storage medium includes a stored program, wherein, when the program is executed, it controls the device where the storage medium is located to perform the OTA upgrade optimization method as described in any one of claims 1 to 6.
Citation Information
Patent Citations
Control method and device for dual reservation function and vehicle
CN114462652A