Vehicle electronic manual resource updating method and system and vehicle

By adopting cold start detection, successful update judgment, continuous detection and periodic query control methods in the intelligent cockpit of the car, the problem of mismatch between the vehicle and the cloud resources is solved, and the intelligent update and latest status maintenance of the vehicle resources are achieved. , improves user experience and saves traffic.

CN119046295APending Publication Date: 2024-11-29CHINA FAW CO LTD +1

Patent Information

Application Number
CN202411065886.8
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-08-05
Publication Date
2024-11-29

AI Technical Summary

Technical Problem

In the existing automotive smart cockpit electronic manual resource update method, the mismatch between the resources on the vehicle end and the cloud end leads to errors in the update content, affecting the user experience.

Method used

Using cold start detection, successful update judgment, continuous detection and periodic query control phases, by comparing local resource versions with cloud resource versions, perform update operations adaptively, and circulate query resource updates in each operation cycle to ensure that Car resources are always up to date.

Benefits of technology

It realizes intelligent update of vehicle-side resources, ensuring that resources are always up-to-date, improving user experience, and saving traffic consumption for online updates.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119046295A_ABST
    Figure CN119046295A_ABST
Patent Text Reader

Abstract

The invention relates to the technical field of vehicles, and discloses a vehicle electronic manual resource updating method and system, electronic equipment, a storage medium and a vehicle, and the method comprises the following steps: a cold start detection stage: comparing a local resource version with a cloud resource version, and adaptively executing an updating operation according to a comparison result; in the updating success judgment stage, corresponding error processing operation is adaptively executed according to the confirmation result; in the continuous detection stage, the updating operation is executed according to a preset strategy on the basis of a comparison result of the latest cloud resource version and the local resource version; and a periodic query control stage: in each operation cycle, circularly querying the resource update condition from the cloud, and stopping querying after reaching a preset number of times until the next operation cycle is reset. According to the method, the update version most suitable for the current vehicle can be intelligently selected, so that the resources of the vehicle end are always kept in the latest and most complete state, meanwhile, the flow consumed by online update is saved, and the user experience is improved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the field of vehicle technology, and in particular to a vehicle electronic manual resource updating method, system, electronic equipment, storage medium and vehicle. Background Art

[0002] At present, in the field of smart cockpits for automobiles, there is a method for online updating of electronic manual products from the vehicle side to the cloud. That is, considering the principle of saving traffic, the vehicle side can obtain full packages or incremental packages from the cloud for update. Full update means obtaining the latest full package from the cloud to update local resources in an overwriting manner, while incremental update means obtaining the latest incremental resources from the cloud for incremental update. The incremental packages and full packages on the cloud are both generated by subjective operations of operators. When operators operate on the cloud to produce full versions, the product list on the cloud will automatically generate full packages and incremental packages of the electronic manual, and the contents are all full packages, but the names are different, and the essence is the same; when operators operate on the cloud to produce incremental versions, the product list on the cloud will also automatically generate full packages and incremental packages of the electronic manual, but the full package is the latest full resource, and the incremental package is the latest full resource compared to the last full resource. A full version of the electronic manual resource will be pre-installed before the vehicle is sold.

[0003] In the existing technology, the vehicle side can only automatically obtain the latest incremental package from the cloud. Only when the vehicle side resources are empty will the full package be automatically obtained from the cloud. That is, when the full resources on the vehicle side are different, the latest incremental package will be automatically obtained from the cloud. This will cause some vehicle side resources to not match the incremental package, and errors will occur in the updated electronic manual content.

[0004] Therefore, the present application provides a vehicle electronic manual resource updating method to solve the above technical problems. Summary of the invention

[0005] The purpose of the present invention is to provide a vehicle electronic manual resource updating method, system, electronic device, storage medium and vehicle, so as to solve the technical problem in the prior art that electronic manual resources are not matched and errors are likely to occur when updating, thus affecting the user experience.

[0006] In order to solve the above technical problems, the present invention provides a vehicle electronic manual resource updating method, comprising:

[0007] In the cold start detection phase, in response to the user entering the electronic manual, a comparison is performed between the local resource version and the cloud resource version, and an update operation is adaptively performed according to the comparison result;

[0008] In the update success judgment phase, in response to the update operation, it is determined whether the update is successful, and corresponding error handling operations are adaptively performed according to the confirmation result;

[0009] In the continuous detection phase, resources are requested from the cloud in real time, and based on the comparison result between the latest cloud resource version and the local resource version, the update operation is performed according to the preset strategy;

[0010] In the periodic query control stage, in each operation cycle, the cloud is cyclically queried for resource update status, and the query is stopped after reaching a preset number of times until the next operation cycle is reset.

[0011] In some specific embodiments, in the cold start detection phase, in response to a user entering the electronic manual, a comparison is performed between the local resource version and the cloud resource version, and an update operation is adaptively performed according to the comparison result, further comprising:

[0012] Display the loading interface;

[0013] Check whether there is a full version to be installed locally, and choose to install the full version, check the incremental version, or request the latest full version from the cloud based on the comparison result between the full version and the local preset resource version;

[0014] When there is no preset resource version locally and no full version to be installed, a request is made to the cloud to download the full version, and based on the comparison result between the latest incremental version on the cloud and the local version, a corresponding choice is made as to whether to download the incremental version.

[0015] In some specific embodiments, in the update success judgment stage, in response to the update operation, determining whether the update is successful, and adaptively performing corresponding error handling operations according to the confirmation result further include:

[0016] In response to the update operation, determine whether the update is successful and confirm the update status, including checking the integrity, version information and dependencies of the new resources;

[0017] When the update is successful, the corresponding electronic manual interface is loaded;

[0018] When the update fails, the error handling process is executed, including trying to roll back the previous version. When the rollback fails or is not feasible, the resource package that failed to be installed is deleted and obtained again from the cloud when entering next time.

[0019] In some specific embodiments, during the continuous detection phase, resources are requested from the cloud in real time, and based on the comparison result between the latest cloud resource version and the local resource version, the update operation is performed according to a preset strategy, further comprising:

[0020] After the electronic manual is loaded and displays the content, it continues to request resources from the cloud;

[0021] Compare the latest full version on the cloud with the local version, and perform the update operation accordingly according to the comparison result;

[0022] Compare the latest incremental version in the cloud with the local version, and perform the update operation accordingly according to the comparison result;

[0023] The user is prompted whether to update, and in response to the user's choice, the update operation is executed or the current interface is continued.

[0024] In some specific embodiments, prompting the user whether to update, and in response to the user selecting to perform the update operation or continue the current interface, further includes:

[0025] Generate a pop-up window containing update prompts based on the type and version information of the update resource;

[0026] A pop-up window prompts the user to choose whether to update immediately;

[0027] When the user chooses to cancel the update, the record will be kept and the update will be automatically attempted the next time the user enters the account.

[0028] When the user chooses to update, the loading interface is displayed and the update operation is performed;

[0029] Determine whether the update is successful and perform corresponding error handling operations based on the judgment result.

[0030] In some specific embodiments, the periodic query control stage, in each operation cycle, cyclically queries the cloud for resource update status, and stops querying after reaching a preset number of times until the next operation cycle is reset, further comprising:

[0031] Setting an upper limit on the number of queries within each of the operation cycles;

[0032] In each of the operation cycles, the cloud is cyclically queried for resource updates until the preset upper limit of the number of queries is reached;

[0033] After reaching the upper limit of the query times, stop querying until the query times are reset at the beginning of the next operation cycle;

[0034] In each of the operation cycles, the local resources are kept synchronized with the cloud.

[0035] Based on the same concept, the present invention also provides a vehicle electronic manual resource updating system, comprising:

[0036] A cold start detection phase module is configured to perform a comparison between a local resource version and a cloud resource version in response to a user entering the electronic manual, and adaptively perform an update operation according to the comparison result;

[0037] An update success judgment phase module is configured to respond to the update operation, determine whether the update is successful, and adaptively perform corresponding error handling operations according to the confirmation result;

[0038] A continuous detection phase module is configured to request resources from the cloud in real time, and based on the comparison result of the latest cloud resource version with the local resource version, perform the update operation according to a preset strategy;

[0039] The periodic query control phase module is configured to cyclically query the cloud for resource update status in each operation cycle, and stop querying after reaching a preset number of times until the next operation cycle is reset.

[0040] Based on the same concept, the present invention also provides an electronic device, comprising: a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory communicate with each other through the communication bus; a computer program is stored in the memory, and when the computer program is executed by the processor, the processor executes the steps of the vehicle electronic manual resource updating method.

[0041] Based on the same concept, the present invention also provides a computer-readable storage medium storing a computer program executable by an electronic device. When the computer program runs on the electronic device, the electronic device executes the steps of the vehicle electronic manual resource updating method.

[0042] Based on the same concept, the present invention also provides a vehicle, wherein the vehicle is provided with the vehicle electronic manual resource updating system as described above.

[0043] Compared with the prior art, the invention has the following beneficial effects:

[0044] The present invention discloses a vehicle electronic manual resource updating method, system, electronic device, storage medium and vehicle, which can intelligently select the update version most suitable for the current vehicle, so that the resources on the vehicle side are always kept in the latest and most complete state, while saving the traffic consumed by online updates and improving user experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0045] Figure 1 It is a flowchart of a vehicle electronic manual resource updating method of the present invention in some specific embodiments;

[0046] Figure 2 It is a flow chart of a vehicle electronic manual resource updating method in some applications of the present invention;

[0047] Figure 3 It is a schematic diagram of the first part of a process of a vehicle electronic manual resource updating method of the present invention in some applications;

[0048] Figure 4 It is a flow chart of the second part of a phase of a vehicle electronic manual resource updating method in some applications of the present invention;

[0049] Figure 5 A schematic diagram of the third part of a process flow of a vehicle electronic manual resource updating method in some applications of the present invention;

[0050] Figure 6 A schematic diagram of the first part of the two-stage process of a vehicle electronic manual resource update method in some applications of the present invention;

[0051] Figure 7 A schematic diagram of the second part of the two-stage flow chart of a vehicle electronic manual resource updating method in some applications of the present invention;

[0052] Figure 8 A schematic diagram of the third part of the two-stage flow chart of a vehicle electronic manual resource updating method in some applications of the present invention;

[0053] Fig. 9 It is a structural schematic diagram of a vehicle electronic manual resource updating system of the present invention in some specific embodiments;

[0054] Fig.10 It is a schematic diagram of the structure of an electronic device in some specific embodiments of the present invention. DETAILED DESCRIPTION

[0055] In order to make the purpose, technical solutions and advantages of the present application clearer, the present application will be further described in detail below in conjunction with the accompanying drawings. Obviously, the described embodiments are only part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the present application.

[0056] The terms used in the embodiments of the present application are only for the purpose of describing specific embodiments, and are not intended to limit the present application. The singular forms "a", "said" and "the" used in the embodiments of the present application and the appended claims are also intended to include plural forms, unless the context clearly indicates other meanings, and "multiple" generally includes at least two.

[0057] It should be understood that the term "and / or" used in this article is only a description of the association relationship of associated objects, indicating that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this article generally indicates that the associated objects before and after are in an "or" relationship.

[0058] It should be understood that although the terms first, second, third, etc. may be used to describe in the embodiments of the present application, these descriptions should not be limited to these terms. These terms are only used to distinguish the descriptions. For example, without departing from the scope of the embodiments of the present application, the first may also be referred to as the second, and similarly, the second may also be referred to as the first.

[0059] As used herein, the words "if" and "if" may be interpreted as "at the time of" or "when" or "in response to determining" or "in response to detecting", depending on the context. Similarly, the phrases "if it is determined" or "if (stated condition or event) is detected" may be interpreted as "when it is determined" or "in response to determining" or "when detecting (stated condition or event)" or "in response to detecting (stated condition or event)", depending on the context.

[0060] It should also be noted that the term "includes", "comprising" or any other variation thereof is intended to cover non-exclusive inclusion, so that a commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprising a ..." do not exclude the existence of other identical elements in the commodity or device including the elements.

[0061] It should be particularly noted that any symbols and / or numbers in the specification that are not marked in the accompanying drawings are not drawing marks.

[0062] Reference Figure 1 , a vehicle electronic manual resource updating method, comprising:

[0063] S101, cold start detection phase, in response to the user entering the electronic manual, performing a comparison between the local resource version and the cloud resource version, and adaptively performing an update operation according to the comparison result;

[0064] It is understandable that the cold start detection phase is automatically triggered when the user enters the e-manual. First, check whether the resource package of the e-manual already exists locally, including the full resource package and possible incremental resource packages. Extract version information from the local resource package, including key fields such as version number and release date. Send a request to the cloud server to query the latest version information of the full resource package and incremental resource package. Compare the local resource version with the cloud resource version to determine whether an update is needed. Based on the results of the version comparison, perform corresponding update operations, including downloading new resource packages, installing updates, error handling, etc.

[0065] When comparing versions, first compare the latest full resource package version on the cloud with the local full resource package version. If the cloud version is higher than the local version, a full update is required. If a full resource package already exists locally and the version is newer (not lower than the latest full version on the cloud), then further compare whether there is an available incremental resource package on the cloud and check whether its version is higher than the local incremental resource package version. If so, perform an incremental update.

[0066] For example, a full update:

[0067] Scenario description: The user installs the e-manual application for the first time, or the local resource package version is too old and needs to be fully updated.

[0068] Detect that there is no local resource package or the resource package version is too old. Send a request to the cloud to obtain the latest full resource package version information. Found that the cloud version is higher than the local version, decided to perform a full update. Download the full resource package provided by the cloud to the local. Install the new resource package and overwrite the original resources. Verify whether the update is successful. If successful, load the new resources. If failed, perform error handling.

[0069] Incremental updates:

[0070] Scenario description: The user has installed a newer version of the electronic manual application, and the cloud has released a new incremental resource package.

[0071] Detect that there is a full resource package locally, and the version is not lower than the latest full version in the cloud. Send a request to the cloud to query whether there is an available incremental resource package. Found that there is an incremental resource package in the cloud, and the version is higher than the local incremental resource package version. Download the incremental resource package provided by the cloud to the local. Install the incremental resource package and update the local resources. Verify whether the update is successful. If successful, load the updated resources. If failed, perform error handling.

[0072] In some of these applications, during the cold start detection phase, in response to the user entering the electronic manual, a comparison is performed between the local resource version and the cloud resource version, and the update operation is adaptively performed based on the comparison result, and a loading interface is displayed; a query is made as to whether there is a full version to be installed locally, and based on the comparison result between the full version and the local preset resource version, a choice is made to install the full version, check the incremental version, or request the latest full version from the cloud; when there is no preset resource version locally and no full version to be installed, a request is made to the cloud to download the full version, and based on the comparison result between the latest incremental version on the cloud and the local version, a choice is made as to whether to download the incremental version.

[0073] It is understandable that after the user triggers the operation of entering the electronic manual, a "loading" interface is first displayed, which is used to inform the user that resources are being prepared to improve the user experience. Traverse the local storage area to find out whether there is a full version resource package that has been downloaded but not yet installed. If it exists, record its version number. Read the resource version number currently in use from the local preset resources. Compare the full version to be installed with the local preset resource version.

[0074] Case A: If the full version to be installed is higher than the local preset resource version, choose to install the full version.

[0075] Case B: If the full version to be installed is not higher than the local preset resource version, check the incremental version.

[0076] In case B, further query the cloud to see if there is an incremental update package applicable to the current local preset resource version.

[0077] Send a request to the cloud, including the version number of the current local preset resource.

[0078] The cloud returns a list of available incremental versions, as well as information such as the update range and size of each incremental version.

[0079] Compare the incremental version returned by the cloud with the local preset resource version, and select the highest and applicable incremental version for download.

[0080] If there is neither a preset resource version nor a full version to be installed locally, directly request the cloud to download the latest full version resource package.

[0081] During the download process, the loading interface is continuously displayed, and contains download progress information.

[0082] After the download is complete, install the full version resource package and update the local resource version number.

[0083] If there are incremental versions available in the cloud that are suitable for the newly installed full version while or after downloading the full version, choose whether to continue downloading and installing these incremental versions based on user settings or system policies.

[0084] S102, update success determination phase, in response to the update operation, determining whether the update is successful, and adaptively performing corresponding error handling operations according to the confirmation result;

[0085] It is understandable that the update success judgment phase is automatically triggered after the update operation is completed. First, the status of the update operation is checked to confirm whether the update process has ended. Confirming whether the update is successful includes file integrity verification, version information comparison, etc. Based on the verification results, it is determined whether the update is successful. If the update fails, the corresponding error handling operations are performed according to the specific cause of the failure, such as rolling back to the old version, recording error logs, notifying users, etc.

[0086] Monitor the status of the update process to ensure that all update tasks (such as file downloads, installations, configuration updates, etc.) have been completed. Use a timer or callback mechanism to periodically check the status of the update process until a signal that the update is complete is received.

[0087] File integrity check: Calculate the checksum of the updated file and compare it with the checksum of the cloud or source file to ensure that the file has not been tampered with during the transmission and installation process.

[0088] Version information comparison: Read the version number of the updated resource and compare it with the latest version number provided by the cloud to ensure that the correct version is updated.

[0089] Functional testing: For critical updates, basic functional testing can be performed to verify that the updated resources work as expected.

[0090] If all validation steps pass, the update is considered successful.

[0091] If any problems are found during the verification process (such as file checksum mismatch, version information error, functional test failure, etc.), the update is considered to have failed.

[0092] Implement error handling:

[0093] Rollback operation: If the update fails and the system supports rollback, the resources will be rolled back to the state before the update automatically or the user will be prompted to ensure the stability and availability of the application.

[0094] Error logging: Records detailed error information, timestamps, and possible reasons for failure to facilitate subsequent problem analysis and resolution.

[0095] User notification: Notify users of update failures through pop-ups, notification bars, or in-app messages, and provide possible solutions or suggestions.

[0096] For example, the electronic manual application is undergoing resource updates, which include new document and image resources.

[0097] Update status detection: The download and installation operations have been monitored to be completed and all files have been placed in the specified directory.

[0098] Verify the update result:

[0099] File integrity check: Calculate the MD5 checksum of the newly downloaded document and compare it with the checksum provided by the cloud, and find that they are exactly the same.

[0100] Version information comparison: Read the version number "2.1.0" of the new resource and match it with the latest version number on the cloud.

[0101] Functional testing: Perform simple document opening and image loading tests to confirm that resources can be used normally.

[0102] Update successful: Since all verification steps are passed, the update is successful.

[0103] Subsequent operations: Load the updated resources for users to view and use.

[0104] If a file checksum mismatch is found during the verification process, error handling operations are performed, such as recording an error log, rolling back to an old version of the resource, and notifying the user of the update failure through a pop-up window, suggesting that the user try again or contact technical support.

[0105] In some of these applications, in the update success judgment stage, in response to the update operation, it is determined whether the update is successful, and the corresponding error handling operations are adaptively performed according to the confirmation result. In response to the update operation, it is determined whether the update is successful and the update status is confirmed, including checking the integrity, version information and dependencies of the new resources; when the update is successful, the corresponding e-manual interface is loaded; when the update fails, the error handling process is executed, including trying to roll back the previous version. When the rollback fails or is not feasible, the resource package that failed to install is deleted and obtained again from the cloud when entering next time.

[0106] It is understandable that after the user triggers the update operation, the new resource package starts to be downloaded and installed to the specified location. After the update operation is completed, the status code or return value of the update process is first checked to preliminarily determine whether the update is successful. If the new resource package depends on other components or libraries, it is also checked whether these dependencies are satisfied or need to be updated at the same time. If all checks pass, the update is considered successful, and the updated electronic manual interface is loaded for the user to use.

[0107] If the update fails, first try to roll back the resource to the state before the update. After the rollback is successful, notify the user that the update failed and restore to the old version, and record the error log for subsequent analysis. If the rollback fails or is not feasible for some reason (such as the old version of the resource has been deleted), perform the next step.

[0108] Delete resource packages that failed to install: To prevent system status confusion, you need to delete resource packages that failed to install and their related files.

[0109] Re-acquire resources: The next time the user enters the electronic manual, it will automatically detect and prompt the user to re-acquire the resource package from the cloud for updating.

[0110] S103, continuous detection phase, requesting resources from the cloud in real time, and performing the update operation according to a preset strategy based on the comparison result between the latest cloud resource version and the local resource version;

[0111] It is understandable that; set a scheduled task that is executed periodically, such as detecting cloud resources once an hour. Or listen to specific events (such as changes in network status, manual triggering by the user, etc.) to trigger the detection process. When the detection task is executed, a request is sent to the cloud server through an HTTP request or other protocol to request the latest resource version information. The request contains the current version number of the local resource so that the cloud can return difference information or a complete update package. After receiving the cloud response, parse the version number of the cloud resource and compare it with the version number of the local resource. The comparison logic includes simple string comparisons (such as increasing the version number). In addition to the version number, the importance and necessity of the update can be further evaluated based on the update log or summary information returned by the cloud.

[0112] Determine whether to perform the update operation based on the preset update strategy.

[0113] The preset strategies include:

[0114] If the cloud version is higher than the local version and the difference reaches a certain threshold (such as a change in the major version number), a forced update is performed.

[0115] If only the minor version number or revision number has changed, and the updated content does not affect the current functionality, you can choose to delay the update or prompt the user to update.

[0116] If the local version is already up to date or the updated content is not meaningful to the current user, the update is not performed.

[0117] The update operation includes downloading update packages, replacing local files, and restarting services.

[0118] In some of these applications, during the continuous detection phase, resources are requested from the cloud in real time, and based on the comparison results of the latest cloud resource version and the local resource version, update operations are performed according to preset strategies. After the electronic manual is loaded and displays the content, resources are continuously requested from the cloud; the latest full version on the cloud is compared with the local version, and update operations are performed accordingly based on the comparison results; the latest incremental version on the cloud is compared with the local version, and update operations are performed accordingly based on the comparison results; the user is prompted whether to update, and the update operation is performed or the current interface is continued in response to the user's choice.

[0119] It is understandable that after the user starts the e-manual application, the content stored on the local device is first loaded and displayed. While the e-manual is loading and displaying the content, start the background service or set a timer to send a request to the cloud at regular intervals (such as every hour, every day, etc.) to obtain the latest resource version information. The request includes the current local version number so that the cloud returns difference information or an update package. After obtaining the latest full resource version information from the cloud, compare it with the locally stored resource version.

[0120] If the cloud version is higher than the local version and the difference is large (such as a change in the major version number), a full update is determined to be required. The user is presented with a full update prompt, including an overview of the update content, update size, and other information, and asked if the user is willing to update. If the user chooses to update, the full update package is downloaded and installed, replacing local resources, and the application or related components are restarted to apply the update.

[0121] While or after a full version comparison, you can also perform an incremental version comparison.

[0122] Incremental updates are suitable for situations where only part of the content has been modified. The update package is smaller and faster to download and install. Get the latest incremental resource version information from the cloud and compare it with the local version.

[0123] If there is an incremental update available and it is applicable to the current local version, the update prompt will also be displayed to the user.

[0124] After the user chooses to update, the incremental update package is downloaded and applied, replacing or modifying only the changed resource parts.

[0125] In some of these applications, the user is prompted whether to update, and in response to the user's choice to perform the update operation or continue the current interface, a pop-up window containing an update prompt is generated based on the type and version information of the updated resource; the pop-up window prompts the user to choose whether to update immediately; when the user chooses to cancel the update, the message is recorded and the update is automatically attempted the next time the user enters; when the user chooses to update, the loading interface is displayed and the update operation is performed; it is determined whether the update is successful, and corresponding error handling operations are performed based on the determination result.

[0126] It is understandable that after receiving the update notification from the cloud, the type of update resource (such as content update, function upgrade, security patch, etc.) and version information (such as version number "1.3.0", update size "50MB", etc.) are parsed. Based on the parsed information, a pop-up window containing detailed update instructions (such as "This update includes the addition of XX function and the fix of XX error") and two options (such as "Update now" and "Not later") is generated. The pop-up window is displayed in a striking way to ensure that users can notice it.

[0127] If the user clicks "Update Now", proceed to the next step.

[0128] If the user clicks "Not now", record the user's choice and display the update prompt pop-up window again the next time the app is started.

[0129] When the user selects "Not Now" and closes the app, log this event.

[0130] The next time the app is started, it checks whether there are any unfinished update tasks. If there are, and the current network conditions meet the update requirements (such as being connected to Wi-Fi and having sufficient power), an update prompt pop-up window will automatically pop up to guide the user to update.

[0131] After the user selects "Update Now", a loading interface (such as a progress bar, a spinning icon, etc.) is displayed to indicate that the update operation is being prepared and executed. The update resource is downloaded, and the display of the loading interface is updated in real time during the download process (such as displaying the download progress). After the download is complete, the update resource is installed or replaced, and the progress information continues to be displayed in the loading interface.

[0132] After the update operation is completed, determine whether the update is successful. If the update is successful, restart the relevant components or the entire application to apply the updated resources. If the update fails (such as due to network interruption, file corruption, etc.), display an error message and provide options to try again or roll back to the old version.

[0133] S104, a periodic query control stage, in each operation cycle, cyclically querying the cloud for resource update status, and stopping the query after reaching a preset number of times until the next operation cycle is reset.

[0134] It is understandable that the operation cycle is set from 0:00 am every day to 0:00 am the next day, or, for more flexible testing, the operation cycle can be set to once every 10 minutes, so as to quickly verify the effect.

[0135] In each operation cycle, the preset number of times to query the cloud for resource updates is set to 5 times. At the beginning of each operation cycle (such as 0:00 a.m. every day), the query cycle is automatically started. Use a timer or background service to ensure that the query operation can be executed as planned. Every time a query request is sent to the cloud and a response is received, the query count counter is increased by 1. Use a global variable or database field to record the current number of queries. When the query count reaches the preset 5 times, stop sending query requests to the cloud. After stopping the query, enter the sleep state or perform other non-query related tasks until the next operation cycle arrives. At the beginning of each new operation cycle (such as a new day starting at 0:00 a.m.), the query count counter is automatically reset to 0. The reset operation ensures that the query count in each operation cycle is independent and is not affected by the previous cycle.

[0136] In some of these applications, in the periodic query control stage, in each operation cycle, the cloud is queried for resource updates in a loop, and the query is stopped after reaching a preset number of times until the next operation cycle is reset, and an upper limit on the number of queries in each operation cycle is set; in each operation cycle, the cloud is queried for resource updates in a loop until the preset upper limit on the number of queries is reached; after reaching the upper limit on the number of queries, the query is stopped until the query number is reset at the beginning of the next operation cycle; in each operation cycle, local resources are kept synchronized with the cloud.

[0137] It is understandable that when the operation cycle ends (e.g., determined by the time interval), the query count counter is automatically reset to zero regardless of whether the query count reaches the upper limit. The reset operation ensures that the query count counter is in the initial state at the beginning of each new operation cycle, thereby avoiding the problem of accumulated query counts across cycles.

[0138] Combine the following Figures 2 to 8 The following describes the embodiments of the vehicle electronic manual resource updating method of the present invention in some applications:

[0139] like Figure 2 , Figure 3 , Figure 4 and Figure 5 As shown, when the vehicle leaves the factory, a version of the full set of resources will be pre-installed in the system, which is called the initial version.

[0140] After the vehicle leaves the factory, the electronic manual will continue to generate updated versions in the cloud, some of which are full packages and some are incremental packages.

[0141] The basic method of updating is: first download the resource package from the cloud to the local vehicle, then install it to replace the preset resources.

[0142] Methods for updating electronic manual resources on the vehicle side:

[0143] Phase 1: Cold start detection:

[0144] The user enters the electronic manual and the loading interface is displayed;

[0145] The electronic manual vehicle-side application queries whether there is a full version to be installed locally (the full package resource version to be installed, which may be the version downloaded last time but not installed completely);

[0146] If there is, compare it with the local prefabricated resource version;

[0147] If it is higher than the local preset resource version, it will be installed. The installation will overwrite the original resources. After completion, the installation package will be deleted. If an abnormal power outage causes the installation to be incomplete, the installation package will also be deleted. Enter the electronic manual to request again next time;

[0148] If the local resource version is lower than the local preset resource version, check whether there are prefabricated resources locally. If there are, check whether there are incremental versions to be installed locally (incremental packages to be installed). If not, directly request the latest full version from the cloud.

[0149] If not, determine whether there are preset resources locally;

[0150] If there are resources locally, check whether there is an incremental version to be installed locally (incremental package to be installed);

[0151] If there are no local resources, request the latest full version from the cloud;

[0152] In the case of no local resources (that is, no pre-made resources and no full version to be installed):

[0153] The vehicle side requests the full version from the cloud side, and first determines whether the full version is available on the cloud side. If the full version is not deployed on the cloud side or the full version on the cloud side cannot be successfully obtained, the vehicle side ends the loading, prompts failure, and automatically exits the application. If the full version is available on the cloud side, the latest full version is downloaded, and after completion, it becomes the local version.

[0154] After the vehicle requests the full version from the cloud and downloads it, it queries the cloud to see if the latest incremental version is higher than the local version:

[0155] If the latest incremental version on the cloud is higher than the current local version, the latest incremental version is downloaded. After completion, it becomes the local version and the next step is judged.

[0156] If the latest incremental version on the cloud is less than or equal to the local version, proceed directly to the next step;

[0157] Determine whether the full version or full version + incremental version downloaded from the cloud is updated successfully:

[0158] If yes, the loading is completed and the application interface is displayed;

[0159] Otherwise, if the update is not completed due to abnormal power failure, delete the resource package that failed to be installed, and enter the car guide next time to obtain it from the cloud again;

[0160] When there are resources locally but the version is higher than the full version to be installed, or the full version to be installed has been installed, check whether there is an incremental version to be installed locally (that is, an incremental package that has not been installed, which may be the version that was downloaded last time but not installed completely):

[0161] If there is an incremental version to be installed locally, determine whether the incremental version to be installed is higher than the local version:

[0162] If the incremental version to be installed is higher than the local version, it will be installed and become the local version after completion. After the installation is completed, it will be determined whether the update is successful. If it is successful, the loading will be completed and the application interface will be displayed. If the incremental package installation is not completed due to abnormal power failure, the resource package will be deleted and the next time you enter the car guide, you can get it from the cloud again.

[0163] If the incremental version to be installed is lower than the local version, the incremental version to be installed is deleted, the loading is completed, and the application interface is displayed;

[0164] If there is no incremental version to be installed locally, the loading ends and the application interface is displayed.

[0165] like Figure 6 , Figure 7 and Figure 8 As shown in the following figure, in phase 2, after entering the application, the background continues to detect:

[0166] After loading is complete, the content is displayed and the backend requests resources from the cloud;

[0167] First query the latest full version on the cloud, and compare the size of the latest full package on the cloud with the local version:

[0168] If the latest full version on the cloud is higher than the local version on the vehicle, the latest full version is downloaded to the vehicle, and after the download is complete, it becomes the local version. Then the latest incremental version on the cloud is requested.

[0169] If the latest full version on the cloud is equal to or lower than the local version on the vehicle, directly request the latest incremental version on the cloud;

[0170] Compare the size of the latest incremental version on the cloud and the local version on the vehicle:

[0171] If the latest incremental version on the cloud is higher than the local version on the vehicle, the latest incremental version is downloaded to the vehicle, and after the download is complete, it becomes the local version. Then proceed to the next step of judgment.

[0172] If the latest incremental version on the cloud is lower than or equal to the local version on the vehicle, proceed directly to the next step;

[0173] Determine whether there is a full version, incremental version, or full version + incremental version downloaded from the cloud:

[0174] If there is no pop-up window, it will be displayed normally.

[0175] A pop-up window will pop up asking the user "Do you want to update now?" The user can choose to update / cancel (enter automatic update next time):

[0176] If the user chooses to cancel (enter automatic update next time), the current interface will be continued and the automatic update will be entered next time;

[0177] If the user chooses to update, the update is installed and the interface displays "Loading"; then it is determined whether the update is successful:

[0178] If the installation of the full package or incremental package is not completed due to an abnormal power outage, delete the package and enter the car guide to obtain it from the cloud again next time;

[0179] If the update is successful, the loading process ends, and a new interface is displayed, indicating that the update is successful.

[0180] Query the cloud again. In each operation cycle of the car guide, the cloud is queried 5 times in a cycle. If it exceeds 5 times, no more queries will be made until the query times are reset in the next operation cycle.

[0181] This embodiment is described below in conjunction with application scenarios:

[0182] Scenario 1: The vehicle is pre-installed with local version 00.00.01 when it leaves the factory. This is a full version, i.e., pre-installed resources. Later, the operator releases updated versions, full version 00.00.02 and incremental version 00.00.02, on the cloud. After the user enters the electronic manual (vehicle guide), the application determines that there is a full version 00.00.01 locally and there is no resource package to be installed. It first displays the 00.00.01 version resource to the user, then queries and downloads the latest 00.00.02 full package from the background. After the background download is complete, a pop-up window prompts the user whether to update immediately. The user clicks update, the electronic manual is loaded immediately, and then the update is completed, displaying version 00.00.02.

[0183] Scenario 2: When the vehicle leaves the factory, due to a production line filling error, the preset resources are not successfully integrated. The local version of the vehicle is empty at the beginning. The latest full version on the cloud operation platform is 00.00.22, and the latest incremental version is 00.00.23. After the user enters the electronic manual (vehicle guide), the application first determines that there are no local resources and no resource packages to be installed, then displays that resources are loading, and queries and downloads the latest full version 00.00.22 from the cloud. After completion, it is used as the local version, and then the latest incremental version 00.00.23 is queried and downloaded from the cloud again. Download and update again, and the local version is 00.00.23 after completion. Then the loading is completed and displayed to the user. In this way, the vehicle side is automatically updated to the latest 00.00.23 version from the state of no resources when leaving the factory.

[0184] Scenario 3: The vehicle is pre-installed with the local version 00.00.15, i.e., the pre-installed resources, when it leaves the factory. The latest full version on the cloud operation platform is 00.00.46, and the latest incremental version is 00.00.52. After the user enters the electronic manual (vehicle guide) for the first time, the application first displays the local resources, i.e., version 00.00.15, and then the background obtains the latest full package from the cloud and completes the download. However, the vehicle unexpectedly loses power during the installation process, and the installation is not completed. The next time the user starts the vehicle and enters the electronic manual (vehicle guide), the application scans the full resource package 00.00.46 that was not installed before, and first displays the resource loading, and then performs the resource installation. After completion, the 00.00.46 resource is displayed to the user, and the local resource version number is updated to 00.00.46. Subsequently, the latest full resource queried from the cloud is still 00.00.46. At this time, it is the same as the version number on the vehicle side, so no update is performed; then the latest incremental version queried from the cloud is 00.00.52, which is higher than the local resource version, so it is downloaded silently in the background. After the download is complete, a pop-up window prompts the user that there is a resource update. The user clicks update, and the application updates the resources. After completion, the latest resource 00.00.52 is presented to the user.

[0185] For the method steps disclosed in the above embodiments, the method steps are described as a series of action combinations for the purpose of simple description, but those skilled in the art should know that the embodiments of the present invention are not limited by the order of the actions described, because according to the embodiments of the present invention, some steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also know that the embodiments described in the specification are all preferred embodiments, and the actions involved are not necessarily required by the embodiments of the present invention.

[0186] like Fig. 9 As shown, the present invention also provides a vehicle electronic manual resource updating system, comprising:

[0187] The cold start detection phase module 201 is configured to perform a comparison between the local resource version and the cloud resource version in response to the user entering the electronic manual, and adaptively perform an update operation according to the comparison result;

[0188] The update success judgment phase module 202 is configured to respond to the update operation, determine whether the update is successful, and adaptively perform corresponding error handling operations according to the confirmation result;

[0189] The continuous detection phase module 203 is configured to request resources from the cloud in real time, and based on the comparison result of the latest cloud resource version and the local resource version, perform the update operation according to a preset strategy;

[0190] The periodic query control phase module 204 is configured to cyclically query the cloud for resource update status in each operation cycle, and stop querying after reaching a preset number of times until the next operation cycle is reset.

[0191] It is worth noting that although only some basic functional modules are disclosed in the embodiments of the present invention, it does not mean that the composition of the present system is limited to the above basic functional modules. On the contrary, what the present embodiment wants to express is that on the basis of the above basic functional modules, those skilled in the art can arbitrarily add one or more functional modules in combination with the prior art to form an infinite number of embodiments or technical solutions. In other words, the present system is open rather than closed. Just because the present embodiment only discloses individual basic functional modules, it cannot be considered that the protection scope of the claims of the present invention is limited to the disclosed basic functional modules. At the same time, for the convenience of description, the above devices are described in terms of functions and are described separately in various units and modules. Of course, when implementing the present invention, the functions of each unit and module can be implemented in the same or one or more software and / or hardware.

[0192] like Fig.10 As shown, the present invention also provides an electronic device, comprising: a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory communicate with each other via the communication bus; a computer program is stored in the memory, and when the computer program is executed by the processor, the processor executes the steps of the vehicle electronic manual resource update method.

[0193] Fig.10 Schematic diagram of the structure of an electronic device provided by an embodiment of the present invention. Fig.10 The electronic device provided in the embodiment of the present invention includes: one or more processors 710 and a storage device 720; the processor 710 in the electronic device may be one or more, Fig.10A processor 710 is taken as an example; the storage device 720 is used to store one or more programs; the one or more programs are executed by the one or more processors 710, so that the one or more processors 710 implement the vehicle electronic manual resource update method as described in any one of the embodiments of the present invention.

[0194] The electronic device may further include: an input device 730 and an output device 740 .

[0195] The processor 710, storage device 720, input device 730 and output device 740 in the electronic device can be connected via a bus or other means. Fig.10 The example of connecting through bus is taken in the following.

[0196] The storage device 720 in the electronic device is a computer-readable storage medium that can be used to store one or more programs, which can be software programs, computer executable programs and modules, such as program instructions / modules corresponding to the vehicle electronic manual resource update method provided in the embodiment of the present invention. The processor 710 executes various functional applications and data processing of the electronic device by running the software programs, instructions and modules stored in the storage device 720, that is, the vehicle electronic manual resource update method in the above method embodiment is implemented.

[0197] The storage device 720 may include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application required for at least one function; the data storage area may store data created according to the use of the electronic device, etc. In addition, the storage device 720 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, or other non-volatile solid-state storage device. In some instances, the storage device 720 may further include a memory remotely arranged relative to the processor 710, and these remote memories may be connected to the device via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0198] The input device 730 may be used to receive input digital or character information and generate key signal input related to user settings and function control of the electronic device. The output device 740 may include a display device such as a display screen.

[0199] The present invention also provides a computer-readable storage medium storing a computer program executable by an electronic device. When the computer program runs on the electronic device, the electronic device executes the steps of the vehicle electronic manual resource updating method.

[0200] Specifically, the computer storage medium of the embodiment of the present invention can adopt any combination of one or more computer-readable media. The computer-readable medium can be a computer-readable signal medium or a computer-readable storage medium. The computer-readable storage medium can be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples (non-exhaustive list) of computer-readable storage media include: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present embodiment, the computer-readable storage medium can be any tangible medium containing or storing a program, which can be used by an instruction execution system, device or device or used in combination with it.

[0201] The present invention also provides a vehicle, wherein the vehicle is provided with the vehicle electronic manual resource updating system as described above.

[0202] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit it. Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or replace some or all of the technical features therein with equivalents. However, these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present invention.

Claims

1. A vehicle electronic manual resource updating method, characterized in that: include: In the cold start detection phase, in response to the user entering the electronic manual, a comparison is performed between the local resource version and the cloud resource version, and an update operation is adaptively performed according to the comparison result; In the update success judgment phase, in response to the update operation, it is determined whether the update is successful, and corresponding error handling operations are adaptively performed according to the confirmation result; In the continuous detection phase, resources are requested from the cloud in real time, and based on the comparison result between the latest cloud resource version and the local resource version, the update operation is performed according to the preset strategy; In the periodic query control stage, in each operation cycle, the cloud is cyclically queried for resource update status, and the query is stopped after reaching a preset number of times until the next operation cycle is reset.

2. The vehicle electronic manual resource updating method according to claim 1, characterized in that: In the cold start detection phase, in response to the user entering the electronic manual, a comparison is performed between the local resource version and the cloud resource version, and an update operation is adaptively performed according to the comparison result, further comprising: Display the loading interface; Check whether there is a full version to be installed locally, and choose to install the full version, check the incremental version, or request the latest full version from the cloud based on the comparison result between the full version and the local preset resource version; When there is no preset resource version locally and no full version to be installed, a request is made to the cloud to download the full version, and based on the comparison result between the latest incremental version on the cloud and the local version, a corresponding choice is made as to whether to download the incremental version.

3. The vehicle electronic manual resource updating method according to claim 1, characterized in that: The update success judgment stage, in response to the update operation, determines whether the update is successful, and adaptively performs corresponding error handling operations according to the confirmation result, further includes: In response to the update operation, determine whether the update is successful and confirm the update status, including checking the integrity, version information and dependencies of the new resources; When the update is successful, the corresponding electronic manual interface is loaded; When the update fails, the error handling process is executed, including trying to roll back the previous version. When the rollback fails or is not feasible, the resource package that failed to be installed is deleted and obtained again from the cloud when entering next time.

4. The vehicle electronic manual resource updating method according to claim 2, characterized in that: The continuous detection phase requests resources from the cloud in real time, and based on the comparison result between the latest cloud resource version and the local resource version, performs the update operation according to the preset strategy, further including: After the electronic manual is loaded and displays the content, it continues to request resources from the cloud; Compare the latest full version on the cloud with the local version, and perform the update operation accordingly according to the comparison result; Compare the latest incremental version in the cloud with the local version, and perform the update operation accordingly according to the comparison result; The user is prompted whether to update, and in response to the user's selection, the update operation is performed or the current interface is continued.

5. The vehicle electronic manual resource updating method according to claim 4, characterized in that: Prompting the user whether to update, and in response to the user choosing to execute the update operation or continue the current interface, further comprising: Generate a pop-up window containing update prompts based on the type and version information of the update resource; A pop-up window prompts the user to choose whether to update immediately; When the user chooses to cancel the update, the record will be kept and the update will be automatically attempted the next time the user enters the account. When the user chooses to update, the loading interface is displayed and the update operation is performed; Determine whether the update is successful and perform corresponding error handling operations based on the judgment result.

6. The vehicle electronic manual resource updating method according to claim 1, characterized in that: The periodic query control stage, in each operation cycle, cyclically queries the cloud for resource updates, stops querying after reaching a preset number of times, and waits until the next operation cycle is reset, further comprising: Setting an upper limit on the number of queries within each of the operation cycles; In each of the operation cycles, the cloud is cyclically queried for resource updates until the preset upper limit of the number of queries is reached; After reaching the upper limit of the query times, stop querying until the query times are reset at the beginning of the next operation cycle; In each of the operation cycles, the local resources are kept synchronized with the cloud.

7. A vehicle electronic manual resource updating system, characterized in that: include: A cold start detection phase module is configured to perform a comparison between a local resource version and a cloud resource version in response to a user entering the electronic manual, and adaptively perform an update operation according to the comparison result; An update success judgment phase module is configured to respond to the update operation, determine whether the update is successful, and adaptively perform corresponding error handling operations according to the confirmation result; A continuous detection phase module is configured to request resources from the cloud in real time, and based on the comparison result of the latest cloud resource version with the local resource version, perform the update operation according to a preset strategy; The periodic query control phase module is configured to cyclically query the cloud for resource update status in each operation cycle, and stop querying after reaching a preset number of times until the next operation cycle is reset.

8. An electronic device, characterized in that: include: A processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory communicate with each other via the communication bus; a computer program is stored in the memory, and when the computer program is executed by the processor, the processor executes the steps of the method described in any one of claims 1 to 6.

9. A computer-readable storage medium, characterized in that: It stores a computer program executable by an electronic device, and when the computer program runs on the electronic device, the electronic device executes the steps of the method described in any one of claims 1 to 6.

10. A vehicle, characterized in that: The vehicle is provided with the vehicle electronic manual resource updating system as claimed in claim 7.

Citation Information

Patent Citations

  • Vehicle data updating method, OTA cloud end and vehicle data updating system

    CN113778498A

  • Data updating method and device, electronic equipment and storage medium

    CN116303490A

  • Display device and update rollback control method

    CN118092965A

  • Vehicle software updating method and device, server, vehicle and medium

    CN118349260A

  • Device for vehicle, vehicle, server, communication system, method for operating device for vehicle, method for operating server, and program

    JP2021047725A

Cited By

  • Static map and patch combined AGV vehicle end map updating method and device

    CN120910182A

  • Electronic specification integration system and method

    CN122346456A