Application configuration method, vehicle, computer equipment and program product
By performing configuration file updates based on a finite state machine in the vehicle and recording update progress information, the problem of difficulty in continuing to update after the vehicle configuration file update is solved, and the reliability and continuity of configuration file is improved.
Patent Information
- Application Number
- CN202411497045.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-10-24
- Publication Date
- 2025-02-07
AI Technical Summary
Vehicle profile updates are frequent and complex, resulting in increased maintenance and management difficulties. The existing technology is difficult to continue to update after configuration file updates are interrupted, affecting reliability and continuity.
By performing the configuration file update process based on the finite state machine in the target vehicle and recording the update progress information, the update process continues based on the recorded update progress information after the configuration file update process is interrupted.
Improves the reliability and continuity of configuration file issuance, ensuring that the vehicle can continue to update if there is an interruption or abnormality during configuration file update.
Smart Images
Figure CN119396459A_ABST
Abstract
Description
Technical Field
[0001] The present disclosure relates to the field of vehicle technology, and in particular, to an application configuration method, a vehicle, a computer device, and a program product. Background Art
[0002] With the rapid development and popularization of new energy vehicle (EV) technology, the vehicle's electronic control unit (ECU) has become more and more complex and intelligent. This complexity and intelligence is not only reflected in the core control system of the vehicle, but also in various auxiliary systems, such as automatic driving assistance, in-vehicle entertainment system, remote diagnosis and safety monitoring.
[0003] In order to improve vehicle performance, user experience and meet increasingly stringent safety and environmental regulations, vehicle configuration files need to be updated frequently. These configuration files contain the settings and parameters of various vehicle systems to ensure that the vehicle can maintain optimal working conditions in different environments and usage conditions. The increasing frequency and complexity of configuration file updates have brought new challenges to vehicle maintenance and management. Summary of the invention
[0004] The embodiments of the present disclosure at least provide an application configuration method, a vehicle, a computer device, and a program product.
[0005] In a first aspect, an embodiment of the present disclosure provides an application configuration method, which is applied to a target vehicle, comprising:
[0006] Receiving a configuration control request for a target application under any functional module of the target vehicle sent by a server;
[0007] In the case where the configuration control request indicates that the configuration file is to be issued, executing a configuration file update process of the target application based on the finite state machine of the functional module, and recording update progress information of the configuration file update process;
[0008] After the configuration file update process is interrupted, in response to the configuration file update process being restarted, the configuration file update process is continued based on the update progress information.
[0009] In a possible implementation, the configuration file update process includes multiple update nodes;
[0010] The update progress information recording the configuration file update process includes:
[0011] Before the configuration file update process is completed, after any update node is executed based on the finite state machine, the update progress information of the update node is stored in the database.
[0012] In a possible implementation manner, the update progress information includes multiple items of the following information:
[0013] The target application includes an application identifier, a configuration file version number, an update node identifier, and a task type.
[0014] In a possible implementation manner, when the configuration control request indicates that the configuration file is to be issued, the configuration control request carries a configuration file acquisition method; wherein the configuration file acquisition method includes message queue telemetry transmission MQTT and hypertext transfer protocol http;
[0015] The finite state machine based on the functional module executes the configuration file update process of the target application, including:
[0016] Based on the finite state machine of the functional module, the configuration file is obtained from the server according to the configuration file obtaining method carried in the configuration control request.
[0017] In a possible implementation manner, the configuration file acquisition method is determined based on the size of the configuration file and / or the update frequency of the configuration file.
[0018] In a possible implementation manner, the method further includes:
[0019] traversing the database in response to a restart of the target vehicle after an interruption in the profile update process;
[0020] When it is detected that the database stores update progress information of an unfinished configuration file update process, the configuration file update process is restarted.
[0021] In a possible implementation manner, the method further includes:
[0022] After the configuration file update process is completed, the update progress information related to the configuration file update process in the database is cleared.
[0023] In a second aspect, an embodiment of the present disclosure further provides a vehicle, which can be used to execute the steps of the above-mentioned first aspect or any possible implementation method of the first aspect.
[0024] In a third aspect, an embodiment of the present disclosure further provides a computer device, comprising: a processor and a memory, wherein the memory stores machine-readable instructions executable by the processor, and when the computer device is running, the machine-readable instructions are executed by the processor to perform the steps of the above-mentioned first aspect, or any possible implementation of the first aspect.
[0025] In a fourth aspect, an embodiment of the present disclosure further provides a computer program product, including a computer program, which, when executed, implements the method described in the above-mentioned first aspect, or any possible implementation manner of the first aspect.
[0026] In the application configuration method, vehicle, computer device and program product provided by the embodiments of the present disclosure, after the target vehicle receives the configuration control request sent by the server, if the configuration control request is for the issuance of a configuration file, the configuration file update process can be executed based on a finite state machine, and the update progress information can be recorded during the execution of the configuration file update process. If the configuration file update process is terminated, the configuration file update process can be continued based on the recorded update progress information after the configuration file update process is restarted. In this way, the update can be continued in the event of an interruption or abnormality during the configuration file update process, thereby improving the reliability and continuity of the configuration file issuance.
[0027] In order to make the above-mentioned objectives, features and advantages of the present disclosure more obvious and easy to understand, preferred embodiments are specifically cited below and described in detail with reference to the attached drawings. BRIEF DESCRIPTION OF THE DRAWINGS
[0028] In order to more clearly illustrate the technical solutions of the embodiments of the present disclosure, the following is a brief introduction to the drawings required for use in the embodiments. The drawings herein are incorporated into the specification and constitute a part of the specification. These drawings illustrate embodiments consistent with the present disclosure and are used together with the specification to illustrate the technical solutions of the present disclosure. It should be understood that the following drawings only illustrate certain embodiments of the present disclosure and should not be regarded as limiting the scope. For ordinary technicians in this field, other relevant drawings can also be obtained based on these drawings without creative work.
[0029] Figure 1 A flow chart of an application configuration method provided by an embodiment of the present disclosure is shown;
[0030] Figure 2 A schematic diagram of an application configuration device provided by an embodiment of the present disclosure is shown;
[0031] Figure 3 A schematic diagram of the structure of a computer device provided by an embodiment of the present disclosure is shown. DETAILED DESCRIPTION
[0032] In order to make the purpose, technical solutions and advantages of the embodiments of the present disclosure clearer, the technical solutions in the embodiments of the present disclosure will be clearly and completely described below in conjunction with the drawings in the embodiments of the present disclosure. Obviously, the described embodiments are only part of the embodiments of the present disclosure, rather than all the embodiments. The components of the embodiments of the present disclosure generally described and shown in the drawings here can be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of the present disclosure provided in the drawings is not intended to limit the scope of the present disclosure claimed for protection, but merely represents selected embodiments of the present disclosure.
[0033] After research, it was found that when the configuration file is sent to the vehicle, network instability may cause data loss or transmission errors, or the update may be interrupted due to abnormal conditions during the process of updating the configuration file on the vehicle side. In this case, the configuration file is usually updated again after the vehicle is restarted, which may cause the vehicle side to repeatedly request the configuration file from the server, and the reliability is low.
[0034] Based on the above research, the present disclosure provides an application configuration method, a vehicle, a computer device, and a program product. After the target vehicle receives a configuration control request sent by a server, if the configuration control request is for the issuance of a configuration file, the configuration file update process can be executed based on a finite state machine, and the update progress information can be recorded during the execution of the configuration file update process. If the configuration file update process is terminated, the configuration file update process can be continued based on the recorded update progress information after the configuration file update process is restarted. In this way, the update can be continued in the event of an interruption or abnormality in the configuration file update process, thereby improving the reliability and continuity of the configuration issuance.
[0035] It should be noted that similar reference numerals and letters denote similar items in the following drawings, and therefore, once an item is defined in one drawing, further definition and explanation thereof is not required in subsequent drawings.
[0036] The term "and / or" herein only describes an association relationship, indicating that three relationships may exist. For example, A and / or B may represent the following three situations: A exists alone, A and B exist at the same time, and B exists alone. In addition, the term "at least one" herein represents any combination of at least two of any one or more of a plurality of. For example, including at least one of A, B, and C may represent including any one or more elements selected from the set consisting of A, B, and C.
[0037] It can be understood that before using the technical solutions disclosed in the embodiments of the present disclosure, the personal information involved in the present disclosure (including but not limited to attribute information, facial images, etc.) is obtained with the authorization of the user. Specifically, it can be through a pop-up window in the page, information push, etc., sending a prompt message requesting authorization to the user, and obtaining the above personal information after the user agrees to the authorization.
[0038] To facilitate understanding of this embodiment, an application configuration method disclosed in the embodiment of the present disclosure is first introduced in detail. The executor of the application configuration method provided in the embodiment of the present disclosure is generally a target vehicle.
[0039] See also Figure 1 As shown, it is a flowchart of an application configuration method provided by an embodiment of the present disclosure, the method includes steps 101 to 103, wherein:
[0040] Step 101: Receive a configuration control request for a target application under any functional module of the target vehicle sent by a server.
[0041] Step 102: When the configuration control request indicates that the configuration file is to be sent, based on the finite state machine of the functional module, execute a configuration file update process of the target application, and record update progress information of the configuration file update process.
[0042] Step 103: After the configuration file update process is interrupted, in response to the configuration file update process being restarted, the configuration file update process is continued based on the update progress information.
[0043] The following is a detailed description of the above steps.
[0044] For step 101,
[0045] Optionally, the functional modules of the target vehicle may include: a telematics & connectivity antenna module (TCAM), a body gateway module (BGM), a cockpit domain controller (CDC), an automatic driving control unit (AD Control Unit, ACU), etc. Different functional modules may include different applications.
[0046] Optionally, different configuration control requests may indicate different configuration tasks. Exemplarily, the configuration control request may indicate any of the following configuration tasks:
[0047] Collect configuration versions, distribute configuration files, and delete configurations.
[0048] Among them, configuration version collection can be understood as reporting the configuration version of the target vehicle's application to the server; configuration file distribution can be understood as issuing a new configuration file to the target vehicle's application; and configuration deletion can be understood as deleting the configuration file of the target vehicle's application.
[0049] Optionally, based on the type field in the configuration control request, the type of configuration task indicated by the configuration control request may be determined.
[0050] In one possible implementation, each functional module may include its own corresponding configuration service module (i.e., ConfigServer module), and the configuration control request may carry the identifier of the functional module and the application identifier of the target application. After receiving the configuration control request, the vehicle terminal may send the configuration control request to the configuration service module of the corresponding functional module based on the identifier of the functional module carried in the configuration control request, and the configuration service module may execute a response operation (i.e., subsequent operation) of the configuration control request.
[0051] For step 102 and step 103,
[0052] In the case where the configuration control request indicates that the configuration file is sent, the configuration control request carries a configuration file acquisition method; wherein the configuration file acquisition method includes message queue telemetry transmission MQTT and hypertext transfer protocol http. Accordingly, the finite state machine based on the functional module executes the configuration file update process of the target application under the functional module, which may include the finite state machine based on the functional module, according to the configuration file acquisition method carried by the configuration control request, to obtain the configuration file from the server.
[0053] MQTT transmission and http transmission have different transmission characteristics. MQTT transmission has the characteristics of high transmission timeliness, but can only transmit small configuration files. http transmission has the characteristics of high transmission security and can transmit large configuration files. Therefore, in the specific implementation, the transmission method can be dynamically selected for different configuration files based on the different transmission characteristics of MQTT and http. The transmission here refers to the transmission from the server to the target vehicle.
[0054] Specifically, the configuration file acquisition method may be determined dynamically by the server according to the configuration file. Exemplarily, the configuration file acquisition method may be determined based on the size of the configuration file and / or the update frequency of the configuration file.
[0055] For example, if the size of the configuration file exceeds the preset byte threshold, the configuration file is transmitted via http, otherwise, the configuration file can be transmitted via MQTT. Alternatively, if the update frequency of the configuration file exceeds the preset frequency, the configuration file can be transmitted via MQTT, otherwise, the configuration file can be transmitted via http.
[0056] Here, the update frequency of the configuration file may be characterized based on the number of updates of the configuration file within a preset time before the current moment.
[0057] The finite state machine may include multiple states. For different configuration file acquisition methods, the finite state machine may include different states.
[0058] Exemplarily, when the configuration file acquisition method is MQTT, the state of the finite state machine may include: downloading the configuration file, checking data integrity, storing the configuration file, configuration distribution, configuration status exception, etc.; when the configuration file acquisition method is http, the state of the finite state machine may include downloading the configuration file, signature verification, decryption, configuration distribution, etc.
[0059] Optionally, the configuration file update process includes multiple update nodes, and different states of the finite state machine correspond to different update nodes of the configuration file update process, or finite state machines in different states are used to execute different update nodes of the configuration file update process. The current update node can be determined by the state of the finite state machine.
[0060] In one possible implementation, when recording the update progress information of the configuration file update process, the update progress information of the update node (i.e., the update node that has just been executed) can be stored in the database before the configuration file update process is completed and after any update node is executed based on the finite state machine.
[0061] The update progress information may include multiple items of the following information:
[0062] The target application includes an application identifier, a configuration file version number, an update node identifier, and a task identifier.
[0063] Here, each configuration file update process may be regarded as an update task, and the task identifier may refer to an identifier of the update task.
[0064] Optionally, for the same update task, only the update progress information of one update node can be stored in the database. After the finite state machine executes the new update node, the update progress information of the update task stored in the database can be overwritten by the update progress information of the most recently executed update node; or, for the same update task, the update progress information of each completed update node can be stored.
[0065] In a possible implementation, after the configuration file update process is completed, the update progress information related to the configuration file update process in the database may be cleared.
[0066] In a possible implementation, after the profile update process is interrupted, when determining whether to restart the profile update process, the database may be traversed in response to the target vehicle being restarted, and then when it is detected that update progress information of an incomplete profile update process is stored in the database, the profile update process may be restarted.
[0067] Optionally, since all update progress information related to the configuration file update process in the database will be cleared after the configuration file update process is executed, if the update progress information of a configuration file update process is traversed in the database, it can be determined that the configuration file update process is not completed.
[0068] Since the finite state machine records the update progress information of the update nodes executed before the configuration file update process is interrupted, after the configuration file update process is restarted, the configuration file update process can be continued based on the recorded update progress information and on the basis of the configuration file update process executed before the interruption.
[0069] In a possible implementation, the configuration file update process of the target application is executed based on the finite state machine of the functional module, which may include saving the configuration file locally based on the finite state machine. To ensure the security of the configuration file, after the configuration file is saved locally, a signature algorithm check may be performed to verify the integrity and consistency of the configuration file. If the check result does not match the signature value transmitted by the server, it indicates that the configuration file may have been tampered with or an error has occurred. Therefore, an error message may be fed back to the server to wait for the next instruction from the server. If the check passes, the configuration file is distributed to the corresponding target application to update the configuration file of the target application.
[0070] In actual applications, for configuration files transmitted in different ways, the corresponding signature algorithm verification methods may be different. For example, for configuration files transmitted based on MQTT, a hash value can be generated based on timestamp, version information, application identifier, and configuration file identifier (such as generating a message digest algorithm fifth edition (Message Digest Algorithm 5, MD5) hash value), and then verified with the signature value transmitted by the server. For configuration files transmitted based on http, when generating hash values, Uniform Resource Locator (URL) parameters can also be combined. The specific method for generating hash values will not be described in detail here.
[0071] In one possible implementation, after receiving the configuration file, the target application can first perform an integrity check on the configuration file and feed back the check result to the server through the ConfigServer. To prevent configuration update failure, the ConfigServer can set a timeout mechanism. If the target application does not feed back the check result within the preset time, the ConfigServer can resend the configuration file to the target application to ensure that the target application can receive the new configuration file.
[0072] In one possible implementation, after the vehicle is restarted, the version information of the configuration file persisted by the target vehicle (i.e., the configuration file that has been configured) can also be automatically reported to the server. The server can compare the version information of the configuration file persisted by the target vehicle with the version information of the latest published configuration file recorded by the server. If there is inconsistency, a configuration control request can be resent to the target vehicle. The configuration control request is used to instruct the target vehicle to upgrade the configuration file to the latest published version.
[0073] Optionally, the target vehicle can also perform a self-check of the configuration file. If the target vehicle detects that a certain configuration file has been deleted, but the configuration information of the configuration file is still stored in the persistent database, the configuration file can be automatically reapplied according to the configuration information.
[0074] Here, the configuration information may exemplarily include a configuration file identifier, a configuration file version number, etc.
[0075] In the case where the configuration control request indicates configuration version collection, the ConfigServer can send a version collection command to the target application after receiving the configuration control request. After receiving the version collection command, the target application can report the version information of the configuration file currently in use to the ConfigServer. After the collection is completed, the ConfigServer can report the collected version information to the server. In this way, the server can obtain the version information of the configuration file of the target application.
[0076] In the case where the configuration indication request indicates configuration deletion, the ConfigServer can send a configuration deletion command to the target application after receiving the configuration control request. After receiving the configuration deletion command, the target application can delete the local configuration file and send the deletion result to the ConfigServer, so that the ConfigServer can feedback the deletion result to the server.
[0077] In the application configuration method provided by the embodiment of the present disclosure, after the target vehicle receives the configuration control request sent by the server, if the configuration control request is for the issuance of a configuration file, the configuration file update process can be executed based on the finite state machine, and the update progress information can be recorded during the execution of the configuration file update process. If the configuration file update process is terminated, the configuration file update process can be continued based on the recorded update progress information after the configuration file update process is restarted. In this way, the update can be continued even if there is an interruption or anomaly in the configuration file update process, thereby improving the reliability and continuity of the configuration file issuance.
[0078] Those skilled in the art will appreciate that, in the above method of specific implementation, the order in which the steps are written does not imply a strict execution order and does not constitute any limitation on the implementation process. The specific execution order of the steps should be determined by their functions and possible internal logic.
[0079] Based on the same inventive concept, an application configuration device corresponding to the application configuration method is also provided in the embodiment of the present disclosure. Since the principle of solving the problem by the device in the embodiment of the present disclosure is similar to the above-mentioned application configuration method in the embodiment of the present disclosure, the implementation of the device can refer to the implementation of the method, and the repeated parts will not be repeated.
[0080] Reference Figure 2 , which is a schematic diagram of the architecture of an application configuration device provided by an embodiment of the present disclosure, the device includes: a receiving module 201, a recording module 202, and a processing module 203; wherein,
[0081] The receiving module 201 is used to receive a configuration control request for a target application under any functional module of the target vehicle sent by the server;
[0082] The recording module 202 is used to execute the configuration file update process of the target application based on the finite state machine of the functional module when the configuration control request indicates that the configuration file is sent, and record the update progress information of the configuration file update process;
[0083] The processing module 203 is used for, in response to the restart of the configuration file update process after the configuration file update process is interrupted, continuing to execute the configuration file update process based on the update progress information.
[0084] In a possible implementation, the configuration file update process includes multiple update nodes;
[0085] The recording module 202 is used to:
[0086] Before the configuration file update process is completed, after any update node is executed based on the finite state machine, the update progress information of the update node is stored in the database.
[0087] In a possible implementation manner, the update progress information includes multiple items of the following information:
[0088] The target application includes an application identifier, a configuration file version number, an update node identifier, and a task type.
[0089] In a possible implementation manner, when the configuration control request indicates that the configuration file is to be issued, the configuration control request carries a configuration file acquisition method; wherein the configuration file acquisition method includes message queue telemetry transmission MQTT and hypertext transfer protocol http;
[0090] The recording module 202 is used to:
[0091] Based on the finite state machine of the functional module, the configuration file is obtained from the server according to the configuration file obtaining method carried in the configuration control request.
[0092] In a possible implementation manner, the configuration file acquisition method is determined based on the size of the configuration file and / or the update frequency of the configuration file.
[0093] In a possible implementation manner, the processing module 203 is used to:
[0094] traversing the database in response to a restart of the target vehicle after an interruption in the profile update process;
[0095] When it is detected that the database stores update progress information of an unfinished configuration file update process, the configuration file update process is restarted.
[0096] In a possible implementation manner, the recording module 202 is used to:
[0097] After the configuration file update process is completed, the update progress information related to the configuration file update process in the database is cleared.
[0098] For descriptions of the processing flow of each module in the device and the interaction flow between each module, reference may be made to the relevant descriptions in the above method embodiment, which will not be described in detail here.
[0099] Based on the same technical concept, the embodiment of the present disclosure also provides a computer device. Figure 3 As shown, it is a schematic diagram of the structure of a computer device 300 provided in an embodiment of the present disclosure, including a processor 301, a memory 302, and a bus 303. Among them, the memory 302 is used to store execution instructions, including a memory 3021 and an external memory 3022; the memory 3021 here is also called an internal memory, which is used to temporarily store the operation data in the processor 301, and the data exchanged with the external memory 3022 such as a hard disk. The processor 301 exchanges data with the external memory 3022 through the memory 3021. When the computer device 300 is running, the processor 301 communicates with the memory 302 through the bus 303, so that the processor 301 executes the following instructions:
[0100] Receiving a configuration control request for a target application under any functional module of the target vehicle sent by a server;
[0101] In the case where the configuration control request indicates that the configuration file is to be issued, executing a configuration file update process of the target application based on the finite state machine of the functional module, and recording update progress information of the configuration file update process;
[0102] After the configuration file update process is interrupted, in response to the configuration file update process being restarted, the configuration file update process is continued based on the update progress information.
[0103] In a possible implementation, in the instructions executed by the processor 301, the configuration file update process includes multiple update nodes;
[0104] The update progress information recording the configuration file update process includes:
[0105] Before the configuration file update process is completed, after any update node is executed based on the finite state machine, the update progress information of the update node is stored in the database.
[0106] In a possible implementation manner, in the instruction executed by the processor 301, the update progress information includes multiple items of the following information:
[0107] The target application includes an application identifier, a configuration file version number, an update node identifier, and a task type.
[0108] In a possible implementation manner, in the instruction executed by the processor 301, when the configuration control request indicates that the configuration file is issued, the configuration control request carries a configuration file acquisition method; wherein the configuration file acquisition method includes message queue telemetry transmission MQTT and hypertext transfer protocol http;
[0109] The finite state machine based on the functional module executes the configuration file update process of the target application, including:
[0110] Based on the finite state machine of the functional module, the configuration file is obtained from the server according to the configuration file obtaining method carried in the configuration control request.
[0111] In a possible implementation manner, in the instructions executed by the processor 301, the configuration file acquisition method is determined based on the size of the configuration file and / or the update frequency of the configuration file.
[0112] In a possible implementation manner, in the instruction executed by the processor 301, the method further includes:
[0113] traversing the database in response to a restart of the target vehicle after an interruption in the profile update process;
[0114] When it is detected that the database stores update progress information of an unfinished configuration file update process, the configuration file update process is restarted.
[0115] In a possible implementation manner, in the instruction executed by the processor 301, the method further includes:
[0116] After the configuration file update process is completed, the update progress information related to the configuration file update process in the database is cleared.
[0117] The embodiment of the present disclosure also provides a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the steps of the application configuration method described in the above method embodiment are executed. The storage medium can be a volatile or non-volatile computer-readable storage medium.
[0118] The present disclosure also provides a computer program product that carries a program code. The program code includes instructions that can be used to execute the steps of the application configuration method described in the above method embodiment. For details, please refer to the above method embodiment, which will not be repeated here.
[0119] The computer program product may be implemented in hardware, software or a combination thereof. In one optional embodiment, the computer program product is implemented as a computer storage medium. In another optional embodiment, the computer program product is implemented as a software product, such as a software development kit (SDK).
[0120] Those skilled in the art can clearly understand that, for the convenience and simplicity of description, the specific working process of the system and device described above can refer to the corresponding process in the aforementioned method embodiment, and will not be repeated here. In the several embodiments provided in the present disclosure, it should be understood that the disclosed system, device and method can be implemented in other ways. The device embodiments described above are merely schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some communication interfaces, and the indirect coupling or communication connection of the device or unit can be electrical, mechanical or other forms.
[0121] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
[0122] In addition, each functional unit in each embodiment of the present disclosure may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
[0123] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a non-volatile computer-readable storage medium that is executable by a processor. Based on this understanding, the technical solution of the present disclosure, or the part that contributes to the prior art or the part of the technical solution, can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present disclosure. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.
[0124] Finally, it should be noted that the above-described embodiments are only specific implementation methods of the present disclosure, which are used to illustrate the technical solutions of the present disclosure, rather than to limit them. The protection scope of the present disclosure is not limited thereto. Although the present disclosure is described in detail with reference to the above-described embodiments, ordinary technicians in the field should understand that any technician familiar with the technical field can still modify the technical solutions recorded in the above-described embodiments within the technical scope disclosed in the present disclosure, or can easily think of changes, or make equivalent replacements for some of the technical features therein; and these modifications, changes or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the embodiments of the present disclosure, and should be included in the protection scope of the present disclosure. Therefore, the protection scope of the present disclosure should be based on the protection scope of the claims.
Claims
1. An application configuration method, characterized in that: Applied to target vehicles, including: Receiving a configuration control request for a target application under any functional module of the target vehicle sent by a server; In the case where the configuration control request indicates that the configuration file is to be issued, executing a configuration file update process of the target application based on the finite state machine of the functional module, and recording update progress information of the configuration file update process; After the configuration file update process is interrupted, in response to the configuration file update process being restarted, the configuration file update process is continued based on the update progress information.
2. The method according to claim 1, characterized in that The configuration file update process includes multiple update nodes; The update progress information recording the configuration file update process includes: Before the configuration file update process is completed, after any update node is executed based on the finite state machine, the update progress information of the update node is stored in the database.
3. The method according to claim 2, characterized in that The update progress information includes multiple items of the following information: The target application includes an application identifier, a configuration file version number, an update node identifier, and a task type.
4. The method according to claim 1, characterized in that: In the case where the configuration control request indicates that the configuration file is to be issued, the configuration control request carries a configuration file acquisition method; wherein the configuration file acquisition method includes message queue telemetry transmission MQTT and hypertext transfer protocol http; The finite state machine based on the functional module executes the configuration file update process of the target application, including: Based on the finite state machine of the functional module, the configuration file is obtained from the server according to the configuration file obtaining method carried in the configuration control request.
5. The method according to claim 4, characterized in that The configuration file acquisition method is determined based on the size of the configuration file and / or the update frequency of the configuration file.
6. The method according to claim 2, characterized in that The method further comprises: traversing the database in response to a restart of the target vehicle after an interruption in the profile update process; When it is detected that the database stores update progress information of an unfinished configuration file update process, the configuration file update process is restarted.
7. The method according to claim 2 or 6, characterized in that: The method further comprises: After the configuration file update process is completed, the update progress information related to the configuration file update process in the database is cleared.
8. A vehicle, characterized in that: The vehicle is used to execute the steps of the application configuration method described in any one of claims 1 to 7 above.
9. A computer device, characterized in that: include: A processor and a memory, wherein the memory stores machine-readable instructions executable by the processor, and when the computer device is running, the machine-readable instructions are executed by the processor to perform the steps of the application configuration method according to any one of claims 1 to 7.
10. A computer program product, comprising a computer program, characterized in that When the computer program is executed, the steps of the application configuration method according to any one of claims 1 to 7 are implemented.