Configuration update monitoring method, vehicle, computer equipment and program product

Abstract

The invention provides a configuration updating monitoring method, a vehicle, computer equipment and a program product, and the method comprises the steps: receiving a software configuration updating instruction issued by a cloud end through a main configuration management module, and determining a target electronic control unit where associated target software is located; sending a software configuration updating instruction to a slave configuration management module in the target electronic control unit, and obtaining instruction receiving state information fed back by the slave configuration management module; under the condition that the instruction receiving state information indicates successful receiving, the slave configuration management module is used for distributing a configuration file indicated by the software configuration updating instruction to target software, and distribution state information of the configuration file under each state node is fed back to the master configuration management module; the main configuration management module is used for feeding back instruction receiving state information and distribution state information to the cloud; and the cloud is used for generating a configuration updating statistical result by using the instruction receiving state information and the distribution state information corresponding to each vehicle.

Description

Technical Field

[0001] The present disclosure relates to the technical field of vehicle factories, and in particular to a configuration update monitoring method, a vehicle, a computer device, and a program product. Background Art

[0002] As vehicles develop towards intelligence and automation, various functions on the vehicle can be realized through various application software deployed on the Electronic Control Unit (ECU). In order to realize the functional update of the application software, the parameter configuration of the application software on the vehicle can be updated through the configuration update instructions issued by the cloud software system. For example, the cloud software system modifies the cycle of vehicle log upload by issuing log update configuration instructions, modifies the algorithm in the application software by issuing algorithm update instructions, and modifies the vehicle startup animation by issuing animation update instructions.

[0003] However, current configuration update technologies only focus on the delivery of configurations and whether the update is successful, and cannot better locate problems when they occur. Summary of the invention

[0004] The embodiments of the present disclosure at least provide a monitoring method, a vehicle, a computer device, and a program product for configuration update.

[0005] In a first aspect, an embodiment of the present disclosure provides a configuration update monitoring method, which is applied to a vehicle, and includes:

[0006] Using the main configuration management module, receiving the software configuration update instruction sent from the cloud, and determining the target electronic control unit where the target software associated with the software configuration update instruction is located;

[0007] Sending the software configuration update instruction to the slave configuration management module in the target electronic control unit, and obtaining instruction reception status information fed back by the slave configuration management module;

[0008] In the case where the instruction reception status information indicates successful reception, the configuration file indicated by the software configuration update instruction is distributed to the target software by using the slave configuration management module, and the distribution status information of the configuration file under each status node is fed back to the master configuration management module; the distribution status information is used to indicate the real-time flow status of the configuration file;

[0009] The main configuration management module is used to feed back the instruction reception status information and the distribution status information to the cloud; the cloud is used to generate configuration update statistics using the instruction reception status information and the distribution status information corresponding to each vehicle.

[0010] In this implementation, the main configuration management module is used to receive the configuration update instructions from the cloud, and the configuration update instructions are sent to the slave configuration management module in the target ECU, so that the configuration update instructions sent from the cloud can be accurately transferred to the target ECU. The slave configuration management module receives the status information through the feedback instruction and reports it to the cloud by the main configuration management module, so that the real-time monitoring of the instruction reception result can be achieved. By downloading the configuration file from the slave configuration management module and distributing it to the target software, the configuration file can be accurately sent to the target software and applied, so as to achieve the purpose of configuration update. At the same time, by feeding back the distribution status information under each state node to the main configuration management module and reporting it to the cloud by the main configuration management module, the real-time flow status of the configuration file can be monitored. In the whole scheme, through the communication between the main configuration management module, the slave configuration management module set in each ECU, and the cloud, the configuration update instruction and the configuration file indicated by the configuration update instruction are circulated in the cloud-ECU-application software. While accurately sending configuration update instructions and configuration files to the target software, the instruction reception status information and real-time distribution status information are reported to the cloud, realizing real-time status monitoring and statistics of the configuration update process in the cloud, and then realizing the evaluation of the configuration effect and obtaining the configuration update statistics. In this way, through real-time reporting of the configuration update process, the flow status of the configuration update can be timely understood in the cloud, and the real-time monitoring of the configuration update process can be realized. Then, the monitoring results can be used to timely locate problems that occur during the update process, so as to achieve the purpose of improving business operation effects.

[0011] In a possible implementation, the distribution status information includes at least configuration file download status, configuration file distribution status, configuration file verification status, configuration file abnormal status, and configuration file application status.

[0012] In this implementation, the configuration file download status is used to indicate whether the configuration file is successfully downloaded to the slave configuration management module; the configuration file distribution status is used to indicate whether the configuration file is successfully sent to the target software in the target ECU; the configuration file verification status is used to indicate whether the configuration file has passed the verification; the configuration file abnormality status is used to indicate whether there is an abnormality in the configuration file; the configuration file application status is used to indicate whether the configuration file is successfully applied to the target software. By feeding back the distribution status of the configuration file at each status node to the cloud in real time, the cloud can be helped to monitor the complete configuration update process in detail.

[0013] In a possible implementation manner, the configuration file verification status includes a first verification status for indicating whether the configuration file is complete; the configuration file distribution status includes a first distribution status for indicating that the configuration file has been sent to the target software;

[0014] The method of distributing the configuration file indicated by the software configuration update instruction to the target software by using the slave configuration management module, and feeding back the distribution status information of the configuration file under each status node to the master configuration management module, comprises:

[0015] In the case where the software configuration update instruction includes a configuration file download address, downloading the configuration file according to the configuration file download address, and feeding back the configuration file download status to the main configuration management module in real time;

[0016] When the configuration file download status indicates that the download is successful, performing integrity check on the configuration file, and feeding back the obtained first check status to the main configuration management module;

[0017] When the first verification status indicates that the configuration file is complete, the configuration file is sent to the target software, and the first distribution status is fed back to the main configuration management module.

[0018] This implementation method can help the cloud to timely understand whether the target ECU has received the configuration file and whether the configuration file is complete by reporting the configuration file download status and the first verification status. If the file is complete, sending the configuration file to the target software can ensure that the target software can apply the complete and correct configuration file.

[0019] In a possible implementation, the configuration file verification status further includes a second verification status for indicating whether the file format of the configuration file matches the target software; the configuration file distribution status further includes a second distribution status for indicating whether the target software successfully receives the configuration file;

[0020] After sending the configuration file to the target software, the method further includes:

[0021] In the case where the target software successfully receives the configuration file, feeding back to the main configuration management module a second distribution status indicating that the configuration file has been successfully received;

[0022] Performing format verification on the configuration file using the target software, and feeding back the obtained second verification status to the main configuration management module;

[0023] When the second verification status indicates that the configuration file matches the target software, overwriting the stored configuration file with the configuration file, and determining a file update timing according to an update rule of the target software, and when the file update timing is reached, performing a configuration update on the target software using the stored configuration file;

[0024] According to the configuration update result, the configuration file application status is generated and fed back to the main configuration management module.

[0025] This implementation method can help the cloud to monitor the reception, processing and use status of the configuration file by reporting the second distribution status, the second inspection status and the configuration file application status.

[0026] In a possible implementation, when the file update opportunity is reached, updating the configuration of the target software using the stored configuration file includes:

[0027] When the file update opportunity is reached, detecting whether a configuration file is stored in the storage space of the target software, and generating a file loss status according to the detection result;

[0028] When the file loss status indicates that the configuration file is not lost, performing an abnormality detection on the configuration file stored in the storage space to obtain a file detection status, and feeding back the file loss status and the file detection status as the configuration file abnormality status to the main configuration management module;

[0029] When the file detection status indicates that there is no abnormality in the configuration file, the target software is updated by using the stored configuration file.

[0030] This implementation method can improve the accuracy of the configuration file applied to the target software by detecting loss and anomalies of the configuration file before applying the configuration file; and can help the cloud to monitor whether there are abnormal problems in the configuration file in a timely manner by reporting the abnormal status of the configuration file.

[0031] In a possible implementation manner, when the distribution status information under any status node indicates that the configuration file fails to be transferred, the distribution status information further includes a transfer failure reason;

[0032] The reason for the transfer failure includes one of the following: failure to download the configuration file, failure to distribute the configuration file, failure to pass the configuration file verification, anomaly in the configuration file, and failure to apply the configuration file.

[0033] This implementation method, when the configuration file fails to be transferred, can help the cloud to promptly understand the problems existing in the configuration update process and fix them by reporting the reasons for the transfer failure, thereby improving the success rate of the configuration update.

[0034] In a possible implementation manner, the configuration file includes multiple configuration files, and different configuration files are used to configure and update different functions of the target software;

[0035] The distribution status information includes distribution status information corresponding to each of the configuration files.

[0036] This implementation method can monitor the configuration update status of each function of the target software in detail by issuing multiple configuration files to the target software and monitoring the circulation status of each configuration file.

[0037] In a possible implementation, the using the main configuration management module to feed back the instruction reception status information and the distribution status information to the cloud includes:

[0038] In the event that there is an abnormality in the network communication between the main configuration management module and the cloud, storing the instruction reception status information and the distribution status information in the main configuration management module;

[0039] In response to the network communication being restored, the instruction reception status information and the distribution status information are fed back to the cloud.

[0040] This implementation method can realize persistent storage of information by storing instruction receiving status information and distributing status information in the main configuration management module. When the network returns to normal, the information is reported to the cloud, and various status information reported from the configuration management module can be uploaded to the cloud in a timely manner.

[0041] In a second aspect, an embodiment of the present disclosure further provides a vehicle, including a controller, wherein the controller includes:

[0042] a memory for storing machine-readable instructions; and

[0043] A processor is used to call and execute the machine-readable instructions stored in the memory to implement the above-mentioned configuration update monitoring method, or the steps in any possible implementation of the above-mentioned configuration update monitoring method.

[0044] In a third aspect, an optional implementation of the present disclosure further provides a computer device, a processor, and a memory, wherein the memory stores machine-readable instructions executable by the processor, and the processor is used to execute the machine-readable instructions stored in the memory, and when the machine-readable instructions are executed by the processor, the steps of the above-mentioned first aspect, or any possible implementation of the first aspect are performed.

[0045] In a fourth aspect, an optional implementation of the present disclosure further provides a computer program product, which, when executed, executes the steps of the above-mentioned first aspect, or any possible implementation of the first aspect.

[0046] 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

[0047] 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.

[0048] Figure 1 A schematic diagram showing a configuration delivery process of a prior art provided by an embodiment of the present disclosure;

[0049] Figure 2 A flowchart of a configuration update monitoring method provided by an embodiment of the present disclosure is shown;

[0050] Figure 3 An architectural diagram of a configuration update provided by an embodiment of the present disclosure is shown;

[0051] Figure 4 An interactive flow chart of a configuration update monitoring method provided by an embodiment of the present disclosure is shown;

[0052] Figure 5 A schematic diagram of the structure of a computer device provided by an embodiment of the present disclosure is shown. DETAILED DESCRIPTION

[0053] In order to make the purpose, technical scheme and advantages of the embodiments of the present disclosure clearer, the technical scheme 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 of the embodiments. The components of the embodiments of the present disclosure generally described and shown here can be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of the present disclosure is not intended to limit the scope of the present disclosure claimed for protection, but merely represents the selected embodiments of the present disclosure. Based on the embodiments of the present disclosure, all other embodiments obtained by those skilled in the art without making creative work belong to the scope of protection of the present disclosure.

[0054] In addition, the terms "first", "second", etc. in the description and claims of the embodiments of the present disclosure and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the terms used in this way can be interchangeable where appropriate, so that the embodiments described herein can be implemented in an order other than that illustrated or described herein.

[0055] The "multiple or several" mentioned in this article refers to two or more. "And / or" describes the association relationship of the associated objects, indicating that there can be three relationships. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. The character " / " generally indicates that the associated objects are in an "or" relationship.

[0056] Research has found that with the continuous improvement of vehicle networking and intelligence, more and more electronic components and application software are configured in vehicles. Application software is deployed in electronic components to provide users with different vehicle functions. In order to provide users with more timely and functional application services, it is often necessary to configure and update application software in a timely manner. For example, modify the car computer startup animation, update the vehicle light show effect, update the vehicle voice, etc. However, the current configuration update technology can be Figure 1 As shown in the figure, the operator (configuration manager) configures and updates information through the cloud configuration platform, and sends the configuration information to the vehicle through the vehicle's 4 / 5G gateway. After receiving the configuration information, the vehicle feeds back a receiving response message to the cloud, and then the vehicle distributes the configuration information to each software module for application. Figure 1 It can be seen that the current configuration update technology only focuses on how to send the configuration file to the application software, ignoring the monitoring of various states of configuration information in the vehicle, such as circulation, verification, and application, resulting in the inability of operators to timely understand the circulation status of configuration updates in the cloud.

[0057] Based on the above research, the present disclosure provides a configuration update monitoring method, vehicle, computer equipment and program product. The main configuration management module receives the configuration update instruction from the cloud, and sends the configuration update instruction to the slave configuration management module in the target ECU, so that the configuration update instruction sent from the cloud can be accurately transferred to the target ECU. The slave configuration management module receives the status information through the feedback instruction and reports it to the cloud by the main configuration management module, so that the real-time monitoring of the instruction reception result can be achieved. By downloading the configuration file from the slave configuration management module and distributing it to the target software, the configuration file can be accurately sent to the target software and applied, so as to achieve the purpose of configuration update. At the same time, by feeding back the distribution status information under each state node to the main configuration management module and reporting it to the cloud by the main configuration management module, the real-time flow status of the configuration file can be monitored. In the whole scheme, through the communication between the main configuration management module, the slave configuration management module set in each ECU, and the cloud, the configuration update instruction and the configuration file indicated by the configuration update instruction are circulated in the cloud-ECU-application software. While accurately sending configuration update instructions and configuration files to the target software, the instruction reception status information and real-time distribution status information are reported to the cloud, realizing real-time status monitoring and statistics of the configuration update process in the cloud, and then realizing the evaluation of the configuration effect and obtaining the configuration update statistics. In this way, through real-time reporting of the configuration update process, the flow status of the configuration update can be timely understood in the cloud, and the real-time monitoring of the configuration update process can be realized. Then, the monitoring results can be used to timely locate problems that occur during the update process, so as to achieve the purpose of improving business operation effects.

[0058] The defects existing in the above solutions are the results obtained by the inventor after practice and careful research. Therefore, the discovery process of the above problems and the solutions proposed by the present disclosure for the above problems below should be the contributions made by the inventor to the present disclosure during the disclosure process.

[0059] 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.

[0060] It is understandable that before using the technical solutions disclosed in the embodiments of the present disclosure, the types, scope of use, usage scenarios, etc. of the personal information involved in the present disclosure should be informed to the user and the user's authorization should be obtained in an appropriate manner in accordance with relevant laws and regulations.

[0061] To facilitate understanding of the present embodiment, a configuration update monitoring method disclosed in the embodiment of the present disclosure is first introduced in detail. The executor of the configuration update monitoring method provided in the embodiment of the present disclosure is generally a terminal device or other processing device with certain computing capabilities, wherein the terminal device may be a vehicle, user equipment (User Equipment, UE), mobile device, user terminal, terminal, personal digital assistant device (Personal Digital Assistant, PDA), handheld device, computer equipment, etc.; in some possible implementation methods, the configuration update monitoring method may be implemented by a processor calling computer-readable instructions stored in a memory.

[0062] The following describes the configuration update monitoring method provided by the embodiment of the present disclosure by taking a vehicle as an example of the execution subject.

[0063] like Figure 2 As shown, it is a flowchart of a configuration update monitoring method provided by an embodiment of the present disclosure, which may include the following steps:

[0064] S201: Utilize the main configuration management module to receive the software configuration update instruction sent from the cloud, and determine the target electronic control unit where the target software associated with the software configuration update instruction is located.

[0065] Here, various domain controllers are deployed in the vehicle, and different domain controllers are used to implement different functions in the vehicle. In the disclosed embodiment, the carrier of the domain controller can be an ECU on the vehicle. The target software can be any application software in the vehicle, and the application software can be deployed in the ECU of the vehicle, and at least one application software can be deployed in one ECU. The application software is used to provide vehicle functions to users. For example, the application software may include vehicle control software, log upload software, map software, voice software, smart driving software, audio and video software, wallpaper software, instrument display software, etc. The target ECU is the ECU deployed with the target software.

[0066] The software configuration update instruction is used to instruct the configuration update of an application software in the vehicle, and the application software is the target software associated with the software configuration update instruction. Configuration updates can include, for example, updating the log upload cycle, updating the lighting effects, updating the boot animation, updating the voice package, updating the map calculation algorithm, etc. Specifically, the operator can set the configuration information in the cloud according to the operational needs, and issue the software configuration update instruction related to the configuration information. The configuration information may include various configuration parameters and configuration resources, and the configuration information may exist in the form of a configuration file. The software configuration update instruction may include information such as the configuration file version number, the configuration file identifier, the target software identifier to which the configuration file belongs, the ECU to which the configuration file belongs, the download address of the configuration file / configuration file, etc. Among them, whether the software configuration instruction includes a configuration file or a configuration file download address is determined according to the size of the configuration file and / or the network communication capability.

[0067] The cloud can specifically include a business operation platform and a configuration management platform. The business operation platform can be used to configure parameters and resources, and analyze business data. The configuration management platform can be used to manage the configuration version of the application software and issue software configuration update instructions.

[0068] The main configuration management module is a module that can communicate directly with the cloud. Specifically, the module can use the communication interface set in the cloud, the cloud gateway and the 4 / 5G gateway on the vehicle to achieve communication with the cloud. The functions of the main configuration management module may include receiving information sent by the cloud (including but not limited to configuration update instructions) through communication with the cloud and forwarding it to the slave configuration management module, and receiving information reported by the slave configuration management module and forwarding it to the cloud, etc.

[0069] The slave configuration management module is used to receive the configuration update instruction converted by the master configuration management module and transfer the configuration file indicated by the configuration update instruction to the target software.

[0070] In the embodiment of the present disclosure, only one master configuration management module may be included and may be deployed on any ECU of the vehicle, and the number of slave configuration management modules may be consistent with the number of ECUs on the vehicle, that is, one slave configuration management module may be deployed in each ECU. For example, the vehicle includes ECU_1 to ECU_N, where N is a positive integer greater than 1, and a master configuration management module and a slave configuration management module may be deployed in ECU_1, and only one slave configuration management module may be deployed in the remaining ECUs (i.e., ECU_2 to ECU_N).

[0071] In specific implementation, after the software configuration update instruction is issued in the cloud, the main configuration management module deployed in the ECU can be used to receive the software configuration update instruction. The main configuration management module is used to parse the software configuration update instruction to determine the target software associated with the software configuration update instruction and the target ECU to which the target software belongs.

[0072] Optionally, after the main configuration management module receives the software configuration update instruction, the main configuration management module may also feedback instruction reception information to the cloud, thereby reporting the status of the configuration change information received by the vehicle to the cloud.

[0073] S202: Sending a software configuration update instruction to a slave configuration management module in a target electronic control unit, and obtaining instruction receiving status information fed back by the slave configuration management module.

[0074] Here, the instruction reception status information is used to indicate whether the target ECU has received the software configuration update instruction. The instruction reception status information can be used to transmit to the cloud whether the vehicle has received the configuration change, so that the cloud can monitor whether the software configuration update instruction can be normally issued to the ECU on the vehicle side.

[0075] In specific implementation, the main configuration management module can be used to send software configuration update instructions to the slave configuration management module in the target ECU. The target ECU generates instruction reception status information and feeds back to the main configuration management module based on whether the software configuration update instruction is successfully received. In this way, the main configuration management module can obtain real-time instruction reception status information for the software configuration update instruction. Among them, in the case where the slave configuration management module in the target ECU successfully receives the software configuration update instruction, the instruction reception status information indicating successful reception can be fed back to the main configuration management module. Conversely, in the case where the slave configuration management module in the target ECU does not successfully receive the software configuration update instruction, the instruction reception status information indicating failed reception can be fed back to the main configuration management module. At the same time, in the case of failed reception, it can be explained that the software configuration update has failed and the target software will not be updated.

[0076] S203: When the instruction reception status information indicates successful reception, the configuration file indicated by the software configuration update instruction is distributed to the target software by the slave configuration management module, and the distribution status information of the configuration file under each status node is fed back to the main configuration management module; the distribution status information is used to indicate the real-time flow status of the configuration file.

[0077] Here, the configuration file is a file used to update the parameters and resources of the target software. The configuration file may include the latest configuration parameters and the latest configuration resources for a certain function of the target software. It may also include information such as the configuration file version number, the configuration file identifier, the target software identifier to which the configuration file belongs, and the ECU to which the configuration file belongs.

[0078] Since the target software can provide at least one function, in order to improve the configuration update efficiency, the configuration file can include at least one, and the software configuration update instruction can include configuration update information related to the configuration file corresponding to at least one function. For example, in the case of updating multiple functions in the target software, each function can correspond to a configuration update information, and the configuration update information can include the configuration file version number corresponding to the function, the configuration file identifier, the target software identifier to which the configuration file belongs, the ECU to which the configuration file belongs, the download address / configuration file of the configuration file, and other information. For example, for map software, the algorithm function of the map software can be updated, the voice function of the map software can be updated, and the display interface of the map software can be updated. At this time, the update of each function can correspond to a configuration update information, and each configuration update information can be uniformly encapsulated in the software configuration update instruction for the map software and sent to the main configuration management module.

[0079] The status node can be understood as each node related to the transfer operation when the configuration file is transferred from the configuration management module and the target software. For example, the status node may include a download status node for downloading the configuration file, a sending status node for routing to the target software, a verification status node for verifying the configuration file, an abnormal status node for detecting whether the configuration file is abnormal, and an application status node for whether the configuration file is applied and effective. Each status node may correspond to at least one distribution status information, and the distribution status information is used to indicate the real-time flow status of the configuration file under the corresponding status node.

[0080] In specific implementation, when the configuration file is transferred from the configuration management module and the target software, it can at least include the following states: downloading the configuration file, successful / failed downloading of the configuration file, the configuration file has been distributed to the target software, successful / failed verification of the configuration file, successful / failed application of the configuration file, missing configuration file, abnormal configuration file. Therefore, the distribution status information can at least include the configuration file download status indicating whether the configuration file is successfully downloaded to the configuration management module, the configuration file distribution status indicating whether the configuration file is successfully sent to the target software, the configuration file verification status indicating whether the configuration file has passed the verification, the configuration file abnormality status indicating whether the configuration file is abnormal, and the configuration file application status indicating whether the configuration file is successfully applied to the target software. Among them, the configuration file download status can specifically include downloading the configuration file, successful / failed downloading of the configuration file; the configuration file distribution status can specifically include the configuration file has been distributed to the software module and the configuration file has not been distributed to the software module; the configuration file verification status can specifically include successful / failed verification of the configuration file; the configuration file abnormality status can include the configuration file is missing, the configuration file is abnormal; the configuration file application status can specifically include successful / failed application of the configuration file.

[0081] Exemplarily, when the instruction reception status information indicates successful reception, that is, when the slave configuration management module in the target ECU successfully receives the software configuration update instruction, the slave configuration management module can be used to distribute the configuration file indicated by the software configuration update instruction to the target software using the local area network on the vehicle, and the slave configuration management module or the target software can be used to determine the distribution status information of the configuration file under each state node in the distribution flow process. Then, the distribution status information can be fed back to the main configuration management module. Among them, the distribution status information under each state node can be uniformly fed back to the main configuration management module by the slave configuration management module, or it can be fed back to the main configuration management module in real time after determination. That is, the distribution status information determined first is fed back to the main configuration management module first, and the distribution status information determined later is fed back to the main configuration management module, and the feedback order of each distribution status information is determined according to the generation order.

[0082] S204: Using the main configuration management module, the command reception status information and the distribution status information are fed back to the cloud; the cloud is used to generate configuration update statistics using the command reception status information and the distribution status information corresponding to each vehicle.

[0083] Here, the configuration update statistics are used to characterize the configuration results of the software configuration update instructions in each vehicle, which may specifically include but are not limited to the reception rate of the software configuration update instructions, the download rate of the configuration file, the verification success rate / failure rate of the configuration file, the application effectiveness rate of the configuration file, and the configuration update failure rate. Among them, when updating the configuration, it is often targeted at a certain number of vehicles, but when the configuration file is issued and applied to the vehicle, due to various reasons such as the vehicle's network problems, file transmission problems, and vehicle problems, the software configuration update instructions cannot be issued to the vehicle normally, the target ECU cannot successfully download the configuration file, the configuration file is abnormal / lost, and the configuration file fails to be applied. Problems such as the problem, resulting in the inability of some vehicles to apply the latest configuration. Therefore, by reporting the various distribution status information of the software update configuration instructions and configuration files during the circulation process to the cloud, the cloud can monitor the configuration application status of each vehicle. In addition, the operator can perform data analysis in different dimensions based on the various distribution status information to obtain the configuration update statistics of different dimensions, thereby providing data support for configuration operations.

[0084] For example, the software configuration update instruction reception rate can be understood as the ratio of vehicles that received the software configuration update instruction to the total number of vehicles that need to receive the instruction. The configuration update failure rate can be understood as the ratio of the number of vehicles that failed to download and verify the configuration file to the total number. The configuration file application effectiveness rate can be understood as the ratio of the number of vehicles that successfully applied the configuration file to the total number of vehicles.

[0085] In specific implementation, after receiving the instruction reception status information and the distribution status information, the main configuration management module can use the main configuration management module to report the instruction reception status information and each distribution status information to the cloud, thereby providing the cloud with the status monitoring data of the configuration file. It is understandable that the instruction reception status information and the distribution status information can be uniformly reported to the cloud by the main configuration management module, or can be reported to the cloud by the main configuration management module immediately after receiving them, which is not specifically limited in the embodiments of the present application.

[0086] Exemplarily, after receiving the instruction reception status information, the main configuration management module can report it to the cloud. Then, after the main configuration management module receives the distribution status information under each status node in steps, it can report each distribution status information to the cloud in steps according to the receiving order.

[0087] In this way, by reporting various states of configuration information such as reception, circulation, verification, and application effectiveness on the vehicle side to the cloud, it can greatly help the execution and effect evaluation of cloud-based operation activities, and realize a closed loop of operation activity planning, execution, and evaluation.

[0088] In the entire configuration update monitoring solution, the configuration update instructions and the configuration files indicated by the configuration update instructions are circulated in the cloud-ECU-application software through the communication between the main configuration management module, the slave configuration management module set in each ECU, and the cloud. While accurately sending the configuration update instructions and configuration files to the target software, the instruction reception status information and real-time distribution status information are reported to the cloud, realizing real-time status monitoring and statistics of the configuration update process in the cloud, and then realizing the evaluation of the configuration effect and obtaining the configuration update statistics. In this way, through the real-time reporting of the configuration update process, the circulation status of the configuration update can be timely understood in the cloud, and the real-time monitoring of the configuration update can be realized, and the monitoring results can be used to achieve the purpose of improving the business operation effect.

[0089] In one embodiment, the configuration files may include multiple configuration files, and different configuration files among the multiple configuration files are used to configure and update different functions of the target software; the distribution status information includes distribution status information corresponding to each configuration file.

[0090] After the main configuration management module sends the software configuration update instruction to the slave configuration management module, the slave configuration management module can distribute the configuration files corresponding to each function to be updated to the target software according to the configuration update information in the software configuration update instruction. At the same time, the distribution status information of each configuration file under each status node can be fed back to the main configuration management module, and then reported to the cloud by the main configuration management module.

[0091] In this way, by issuing multiple configuration files to the target software, the configuration updates of multiple functions of the target software can be realized, and by using multiple configuration files for updating, the problem of long file transmission time caused by placing the update information corresponding to various functions in the same file for issuance can be avoided. By monitoring the flow status of each configuration file, the configuration update status of each function of the target software can be carefully monitored.

[0092] In one embodiment, the configuration file verification status may include a first verification status for indicating whether the configuration file is complete; the configuration file distribution status may include a first distribution status for indicating that the configuration file has been sent to the target software.

[0093] Here, the first distribution status is used to indicate that the configuration file has been sent to the target software. The first verification status may specifically include a verification success status used to indicate that the configuration file is complete, and a verification failure status used to indicate that the configuration file is incomplete.

[0094] The above S203 can be implemented according to the following steps:

[0095] S203-1: When the software configuration update instruction includes a configuration file download address, download the configuration file according to the configuration file download address, and feed back the configuration file download status to the main configuration management module in real time.

[0096] Here, when the size of the configuration file is greater than the set threshold, the software configuration update instruction may include the download address of the configuration file corresponding to the function to be updated. When the size of the configuration file is not greater than the set threshold, the configuration file may be directly carried in the software configuration update instruction. In this way, after the main configuration management module sends the software configuration update instruction to the slave configuration management module, if the slave configuration management module successfully receives the software configuration update instruction, the configuration file may be directly obtained from the instruction without downloading the configuration file. At the same time, the slave configuration management module may feedback the configuration file download status indicating that the configuration file has been successfully downloaded to the main configuration management module. The above-mentioned set threshold can be determined according to the network communication capability between the cloud and the vehicle end.

[0097] In specific implementation, after receiving the software configuration update instruction, the slave configuration management module can parse the software configuration update instruction to determine whether it includes the configuration file download address or the configuration file. In the case of including the configuration file, the slave configuration management module can directly obtain the configuration file, and can feed back the configuration file download status indicating that the configuration file is successfully downloaded to the main configuration management module. In the case that the software configuration update instruction includes the configuration file download address, the slave configuration management module can start downloading the configuration file according to the download address, and feed back the real-time configuration file download status to the main configuration management module. For example, when starting to download the configuration file, the download status of "configuration file downloading" can be fed back to the main configuration management module; when the configuration file is successfully downloaded, the download status of "configuration file download successful" can be fed back to the main configuration management module, and the following S203-2 is executed; when the configuration file download fails, the download status of "configuration file download failed" can be fed back to the main configuration management module, and the configuration update of the function corresponding to the configuration file is terminated.

[0098] S203-2: When the configuration file download status indicates that the download is successful, perform integrity check on the configuration file, and feed back the obtained first check status to the main configuration management module.

[0099] Here, the first verification status may include configuration file verification success and configuration file verification failure.

[0100] Exemplarily, when the configuration file is successfully downloaded from the configuration management module, the slave configuration management module will also feedback to the main configuration management module the download status of the configuration file indicating successful downloading. At this time, the slave configuration management module can perform a preliminary verification on the downloaded configuration file to obtain a preliminary verification result. The preliminary verification here may include but is not limited to file integrity verification and security verification. Furthermore, the first verification status that matches the preliminary verification result can be fed back to the main configuration management module, and then fed back to the cloud by the main configuration management module. Among them, when the preliminary verification result indicates that the verification is passed, the first verification status can be that the configuration file is complete and the verification is successful, and then the following step S203-3 can be continued. When the preliminary verification result indicates that the verification fails, the first verification status can be that the configuration file is incomplete and the verification fails, and then the configuration update of the function corresponding to the configuration file will be terminated.

[0101] It is understandable that, when the software configuration update instruction includes a configuration file, the integrity check can be directly performed on the configuration file to obtain a first check state.

[0102] S203 - 3 : When the first verification status indicates that the configuration file is complete, the configuration file is sent to the target software, and the first distribution status is fed back to the main configuration management module.

[0103] For example, when the preliminary verification result indicates that the verification is passed, the first verification status may indicate that the configuration file is complete and safe. Furthermore, the slave configuration management module may route the configuration file to the target software associated with the configuration file through the local area network of the vehicle, and feed back the first distribution status indicating that the configuration file has been sent to the target software to the master configuration management module, and the master configuration management module then feeds back the first distribution status to the cloud.

[0104] Furthermore, not only the configuration management module will check the configuration file, but the target software may also check the configuration file, for example, perform format configuration verification on the configuration file to determine whether the file format of the configuration file is a format that the target software can recognize. Therefore, the configuration file verification status may also include a second verification status for indicating whether the file format of the configuration file matches the target software. At the same time, when the configuration management module routes the configuration file to the target software, the routing may be successful or it may fail. Therefore, the configuration file distribution status may also include a second distribution status for indicating whether the target software has successfully received the configuration file.

[0105] After sending the configuration file to the target software, you can continue to use the following steps to transfer the configuration file:

[0106] S203 - 4 : When the target software successfully receives the configuration file, a second distribution status indicating successful receipt of the configuration file is fed back to the main configuration management module.

[0107] Exemplarily, when the target software successfully receives the configuration file routed from the slave configuration management module, the target software can be used to feed back the second distribution status indicating the successful reception of the configuration file to the slave configuration management module, and continue to execute the following S203-5. After receiving the second distribution status, the slave configuration management module can feed back the status to the master configuration management module, and the master configuration management module then feeds back the second distribution status to the cloud.

[0108] It is understandable that, in the case where the target software fails to successfully receive the configuration file routed by the slave configuration management module, the target software can be used to feed back the second distribution status indicating that the configuration file has not been successfully received to the slave configuration management module, and end the configuration update of the function corresponding to the configuration file. After receiving the second distribution status, the slave configuration management module can feed back the status to the main configuration management module, and the main configuration management module then feeds back the second distribution status to the cloud.

[0109] S203-5: Use the target software to perform format verification on the configuration file, and feed back the obtained second verification status to the main configuration management module.

[0110] In specific implementation, after the target software receives the configuration file, the configuration file may be format checked to determine whether the file format of the configuration file is a format that the target software can recognize. Then, the second verification state may be determined based on the format verification result. Among them, if the format verification passes, the second verification state may be that the configuration file format matches and the verification is successful, and then the following S203-6 may be executed; if the format verification fails, the second verification state may be that the configuration file format does not match and the verification fails, the obtained configuration file is deleted, and the configuration update of the function corresponding to the configuration file is terminated.

[0111] It is understandable that, in addition to format verification, the target software may also perform security verification on the configuration file to obtain a verification result, which may affect the second verification state.

[0112] After obtaining the second verification status, the target software can be used to feed back the second verification status to the slave configuration management module. After receiving the second verification status, the slave configuration management module can feed back the second verification status to the master configuration management module, and then the master configuration management module feeds back the second verification status to the cloud.

[0113] S203-6: When the second verification status indicates that the configuration file matches the target software, the configuration file is used to overwrite the stored configuration file, and the file update timing is determined according to the update rule of the target software, and when the file update timing is reached, the target software is configured and updated using the stored configuration file.

[0114] Here, the target software of the target type may have different update rules, such as updating when the vehicle system is restarted, updating when the vehicle is in P gear, updating when the function of the target software is not running, etc. The file update timing is the timing of using the configuration file to update the target software.

[0115] Exemplarily, when the format check result indicates that the check is passed, the second check status may indicate that the configuration file matches the target software and is safe. At this time, the configuration file may be used to overwrite the configuration file stored locally in the target software, thereby realizing the storage of the latest configuration file. It is understandable that when the configuration file is for a certain function of the target software, the configuration file may be used to overwrite the stored configuration file corresponding to the function, and the stored configuration files corresponding to other functions may be retained.

[0116] It should be noted that in order to avoid the target software from being unable to update due to configuration file damage (such as configuration file abnormality or loss), a default configuration file can also be set in each target software. The default configuration file can be stored in the target software all the time and will not be overwritten by the new configuration file. When the cloud does not send the first configuration file for the target software, or the first configuration file verification fails, or the configuration file sent for the nth time (n is greater than or equal to 1) passes the verification but is damaged and unusable during subsequent use, the default configuration file can be used to configure the parameters of the target software to ensure that the target software can function normally. Among them, the default configuration file can include default files corresponding to various functions in the target software.

[0117] When the format check result indicates that the check has passed, the update rules of the target software and the current running status of the target software can also be determined, and the file update timing can be determined based on the update rules and the current running status. For example, for the intelligent driving function, if the vehicle is not currently running the intelligent driving function, the file update timing can be determined to be updated immediately; if the vehicle is currently running the intelligent driving function, the file update timing can be determined to be updated immediately when the intelligent driving function stops. Furthermore, when the file update timing is reached, the configuration file stored in the target software can be used to update the target software and obtain the configuration update result. Among them, the configuration update result may include a successful configuration update and a failed configuration update.

[0118] It is understandable that for the target software, there is currently a new version of the configuration file waiting to be updated, but before the time to update the file arrives, the target software receives an updated version of the configuration file. In this case, the updated version of the configuration file can be used to overwrite the previous version of the configuration file, and when the time to update the file arrives, the updated version of the configuration file can be used to update the configuration of the target software.

[0119] S203-7: Generate the configuration file application status according to the configuration update result and feed it back to the main configuration management module.

[0120] For example, when the configuration update result is that the configuration update is successful, the target software after the function update can be obtained, and the configuration file application status at this time can be that the configuration file application is successful. Then, the configuration file application status indicating that the configuration file application is successful can be fed back to the slave configuration management module using the target software. The slave configuration management module can forward it to the master configuration management module, and then the master configuration management module feeds back the configuration file application success status to the cloud.

[0121] When the configuration update result is a configuration update failure, the target software can be restored to the version before the update, or the target software can be restored to the default version using the default configuration file to ensure that the target software can run normally. At this time, the configuration file application status can be a configuration file application failure. Then, the target software can be used to feedback the configuration file application failure status to the slave configuration management module. The slave configuration management module can forward it to the master configuration management module, and the master configuration management module will then feedback the configuration file application failure status to the cloud.

[0122] In one embodiment, the step of “updating the configuration of the target software using the stored configuration file” in S203-6 may also be implemented according to the following steps:

[0123] S203-6-1: When the file update timing is reached, detect whether the storage space of the target software stores the configuration file, and generate a file loss status according to the detection result.

[0124] Here, the file missing status is used to indicate whether the configuration file is missing.

[0125] During specific implementation, when the time for file update is reached, it is possible to detect whether a configuration file is stored in the storage space of the target software and obtain a detection result. That is, it is detected whether there is a configuration file corresponding to the new version configuration. When the detection result indicates that there is a configuration file, a file loss status can be generated to indicate that the configuration file is not lost. Optionally, when the detection result indicates that there is a configuration file, it is also possible to determine whether the version number of the configuration file is higher than the version number of the function corresponding to the configuration file in the target software. If so, it is determined that the function needs to be updated using the configuration file. If not, it is determined that the function is already the latest version and does not need to be updated.

[0126] If the file loss status indicates that the configuration file is not lost, and the version number of the configuration file is higher than the version number of the corresponding function, the following S203-6-2 can be executed. On the contrary, if the file loss status indicates that the configuration file is lost, and / or the version number of the configuration file is not higher than the version number of the corresponding function, the configuration update of the function corresponding to the configuration file using the configuration file can be terminated.

[0127] S203-6-2: When the file loss status indicates that the configuration file is not lost, perform an abnormality detection on the configuration file stored in the storage space to obtain a file detection status, and feed back the file loss status and the file detection status as the configuration file abnormality status to the main configuration management module.

[0128] Here, the file detection status is used to indicate whether there is an abnormality in the configuration file. Abnormality detection may include abnormality detection of file content, abnormality detection of file format, abnormality detection of file size, etc.

[0129] Exemplarily, when the configuration file is not lost, one or more abnormality detections can be performed on the stored configuration file to obtain abnormality detection results. The file detection status is determined according to the abnormality detection results. Furthermore, the file loss status and the file detection status can be used together as the configuration file abnormality status, and the target software can be used to feed back the configuration file abnormality status to the slave configuration management module, and then the slave configuration management module can be used to feed back the configuration file abnormality status to the master configuration management module, and finally the master configuration management module can feed back to the cloud.

[0130] Optionally, after obtaining the file loss status, the target software, the slave configuration management module and the master configuration management module can be used to directly feed back the file loss status to the cloud. Then, after obtaining the file detection status later, the target software, the slave configuration management module and the master configuration management module can be used to feed back the file detection status to the cloud. In this way, the distribution status information determined in real time can be fed back to the cloud in real time.

[0131] Among them, when the file detection status indicates that there is no abnormality in the file, the following S203-6-3 can be executed; when the file detection status indicates that there is an abnormality in the file, the configuration update of the function corresponding to the target software using the configuration file can be terminated.

[0132] S203-6-3: When the file detection status indicates that there is no abnormality in the configuration file, the target software is updated using the stored configuration file.

[0133] Exemplarily, when there is no abnormality in the configuration file, the configuration file can be used to update the configuration of the target software.

[0134] It is understandable that based on the above embodiments, the transfer of configuration files may fail at any state node. In order to facilitate the cloud operators to analyze according to the reported distribution status information, when the distribution status information at any state node indicates that the configuration file transfer has failed, the distribution status information also includes the reason for the transfer failure. Here, the reason for the transfer failure is used to describe the specific reason for the failure of the configuration file transfer. Among them, the reason for the transfer failure may include one of the following: configuration file download failure, configuration file distribution failure, configuration file verification failure, configuration file exception, and configuration file application failure.

[0135] Exemplarily, if the configuration file download fails under the download status node, the distribution status information corresponding to the status node may include the configuration file download failure and the reason for the download failure, for example, the reason for the download failure may be request timeout, file download address abnormality, etc. If the configuration file distribution fails under the send status node, the distribution status information corresponding to the status node may include the configuration file distribution failure and the reason for the distribution failure, for example, the reason for the distribution failure may be request timeout, transmission interruption, target software abnormality, etc. If the configuration file verification fails under the verify status node, the distribution status information corresponding to the status node may include the configuration file verification failure and the reason for the verification failure, for example, the reason for the verification failure may be incomplete file, file format does not match the target software, file has security virus, etc. If the configuration file is abnormal under the abnormal status node, the distribution status information corresponding to the status node may include the configuration file abnormality and the reason for the abnormality, for example, the reason for the abnormality may be configuration file loss, unknown abnormality in the configuration file, risk in the configuration file, etc. If the configuration file application fails under the apply status node, the distribution status information corresponding to the status node may include the configuration file application failure and the reason for the application failure, for example, the reason for the application failure may be configuration file incompatibility, target software update permission is not enabled, target software and configuration file conflict, etc.

[0136] In this way, when the configuration file fails to transfer, by reporting the reason for the transfer failure, the cloud can promptly understand the problems in the configuration update process and fix them, thereby improving the success rate of the configuration update.

[0137] Optionally, in the process of updating the target software using the configuration file, it is also possible to continue to detect whether the configuration file is lost or abnormal. If not, the configuration file application status can be generated after the target software is updated using the configuration file. If so, it can be said that the configuration file is damaged and unavailable during use, which may cause the target software to be updated abnormally after a certain progress. Therefore, in order to further ensure that the target software will not be abnormal due to the update, if the configuration file is detected to be lost or abnormal during the update process, the default configuration file can be used to update the target software, thereby ensuring that the basic functions of the target software can operate normally. At this time, the configuration file abnormality status indicating that the configuration file is damaged, and the configuration file application status indicating that the configuration file has not been successfully applied to the target software, can be fed back to the main configuration management module together, and then fed back to the cloud by the main configuration management module.

[0138] In one embodiment, the above S204 may be implemented according to the following steps:

[0139] S204-1: When there is an abnormality in the network communication between the main configuration management module and the cloud, the instruction reception status information and the distribution status information are stored in the main configuration management module.

[0140] In specific implementation, the connectivity and quality of network communication affect the success rate of information reporting. Therefore, after obtaining the instruction reception status information and the distribution status information under each status node using the main configuration management module, it is also possible to first detect whether there is an abnormality in the network communication between the main configuration management module and the cloud. If not, the instruction reception status information and the distribution status information can be sent to the cloud.

[0141] If so, in order to improve the success rate of information reporting, the instruction receiving status information and the distribution status information may be first stored in the storage space of the main configuration management module.

[0142] S204-2: In response to the network communication being restored, the instruction reception status information and the distribution status information are fed back to the cloud.

[0143] Exemplarily, when the network communication between the main configuration management module and the cloud is restored to normal, the main configuration management module can be used to report the stored instruction reception status information and distribution status information to the cloud.

[0144] Optionally, regardless of whether there is an abnormality in the network communication between the main configuration management module and the cloud, when the main configuration management module receives the instruction reception status information and the distribution status information, the instruction reception status information and the distribution status information can be persistently stored. After the storage is completed, the main configuration management module can be used to report the stored instruction reception status information and the distribution status information to the cloud.

[0145] Optionally, in order to prevent the storage space corresponding to the main configuration management module from being over-occupied, the instruction reception status information and distribution status information stored in the main configuration management module may also be deleted in response to triggering a target condition. The target condition may include at least one of the following: the usage rate of the storage space of the main configuration management module reaches the target threshold, the latest reception status information and the latest distribution status information of each configuration file are successfully sent to the cloud, and a deletion instruction issued by the cloud is received.

[0146] Among them, after the target condition is triggered, all instruction reception status information and distribution status information stored in the main configuration management module can be deleted, or the latest configuration file corresponding to each target software, or the latest configuration file corresponding to each function of each target software can be determined first, and then the reception status information and distribution status information of each configuration file except the latest configuration file can be deleted.

[0147] Optionally, before the reception status information and distribution status information corresponding to a certain version of the configuration file are uploaded to the cloud, if the main configuration management module receives the reception status information and distribution status information corresponding to an updated version of the configuration file and uploads them to the cloud, when the network is restored, only the reception status information and distribution status information corresponding to the updated version of the configuration file may be uploaded to the cloud, or the reception status information and distribution status information corresponding to each version of the configuration file may be uploaded to the cloud.

[0148] like Figure 3 The figure shows an architecture diagram of a configuration update provided by an embodiment of the present disclosure, in which the operation personnel can configure resources and parameters on the business operation platform according to the operation plan, obtain the configuration file, and then publish the operation business on the configuration management platform. The configuration management platform can manage the configuration version and issue the configuration file, and store the status information reported by the main configuration management module, and the status information includes the instruction reception status information and the distribution status information. The vehicle-to-cloud communication between the vehicle side and the cloud is realized through the cloud gateway, and the software configuration update instruction is issued to the main configuration management module in ECU1 through the vehicle's 4 / 5G gateway. Among them, ECU_1 can be any one of the multiple ECUs in the vehicle, Figure 3There are multiple ECUs (ECU_1 to ECU_N) in the vehicle shown in the figure, and each ECU may include one or more application software. The structure of the slave configuration management module in each ECU is consistent with the structure of the slave configuration management module in ECU_2. The master configuration management module receives the software configuration update instruction and determines the target electronic control unit and the target software. The master configuration management module can send the software configuration update instruction to the slave configuration management module of the target ECU, and the slave configuration management module performs configuration version management, configuration file download, configuration status reporting, and distributes the downloaded configuration file to the target software. Among them, the target ECU can be an ECU configured with a master configuration management module, or it can be other ECUs. Figure 3 Taking the target ECU as ECU2 as an example, the target ECU includes application software 1 to 3, wherein the target software is any one of the application software 1 to 3. The configuration version management of the slave configuration management module can update the configuration of the target software according to the software configuration update instruction, and record the version information of the target software, etc. The target software can feedback the configuration file distribution status, configuration file verification status, configuration file abnormal status, and configuration file application status of the configuration file to the slave configuration management module, and the slave configuration management module will report this status information to the main configuration management module. The main configuration management module can report this status information to the configuration management platform in the cloud to monitor the status information. The cloud operators can perform status data statistics, business data analysis, and prepare business operation reports based on the reported information. The slave configuration management module and the main configuration management module can also store various status information. Figure 3 In the configuration management module, the configuration status reported by the slave configuration management module may include instruction reception status information and configuration file distribution status information under each status node, and the configuration status reported by the master configuration management module may include various status information reported by the slave configuration management module. The configuration status reported by the application software may include configuration file verification status, configuration file abnormal status, configuration file application status, etc.

[0149] exist Figure 3 In the example, the target ECU is ECU_2. In the specific implementation, the target ECU can be any ECU in the vehicle. The configuration file transfer process between each ECU and the main configuration management module is similar to that of ECU_2. Figure 3 Not shown one by one.

[0150] like Figure 4 As shown, an interactive flow chart of a configuration update monitoring method provided by an embodiment of the present disclosure may include the following steps:

[0151] S401: The operation personnel initiates business operation configuration on the business operation platform.

[0152] S402: The business operation platform requests the configuration management platform to update the configuration.

[0153] S403: The configuration management platform generates a new configuration file.

[0154] S404: The configuration management platform issues a software configuration update instruction.

[0155] S405: The main configuration management module on the vehicle side reports that the update instruction has been received.

[0156] exist Figure 4 In the figure, the main configuration management module and the slave configuration management module are both described as vehicle-side configuration management modules.

[0157] S406: The main configuration module sends the software configuration update instruction to the slave configuration management module, and the slave configuration management module downloads the configuration file.

[0158] S407: Report configuration downloading.

[0159] S408: Report that the configuration download is successful.

[0160] S409: Distribute the configuration file to the target software.

[0161] At this point, the main configuration management module can be used to report the configuration file distribution status.

[0162] S410: The target software performs configuration verification.

[0163] S411: The target software reports the configuration file verification status.

[0164] S412: The main configuration management module reports the configuration file verification status to the configuration management platform.

[0165] S413: Target software application configuration file.

[0166] Here, before applying the configuration file, file loss detection and file anomaly detection can also be performed to obtain and report the abnormal state of the configuration file. During the application of the configuration file, file loss detection can also be performed to obtain and report the abnormal state of the configuration file.

[0167] S414: The target software reports the application status of the configuration file.

[0168] There is no strict execution order between S411 to S414.

[0169] S415: The main configuration management module reports the configuration file application status to the configuration management platform.

[0170] S416: The configuration management platform synchronizes the status information reported by the vehicle end to the operation platform in real time.

[0171] S417: The operator performs configuration status statistics and determines the configuration update statistics result.

[0172] Regarding the specific implementation steps of the above S401 to S417, reference may be made to the above embodiments and will not be repeated here.

[0173] In the embodiment of the present disclosure, after the software configuration update instruction is issued, the status information of the configuration information circulating in the vehicle end is monitored in the cloud, while the prior art only focuses on whether the configuration file has been issued and has reached the vehicle, ignoring the monitoring of various status information. The present disclosure sets up a special configuration file management module (including a main configuration management module and a slave configuration management module) on the vehicle end, and the configuration management module uniformly receives the configuration change information issued by the cloud, downloads the configuration file, and then distributes the configuration file to the application software on different ECUs on the vehicle end through the local area network. At the same time, the configuration management module is used to track the status of the configuration file, and the key node status of the configuration file in the transmission process of different ECUs and different software modules on the vehicle end is uploaded to the cloud in real time. The cloud can display the status data of all vehicle update configurations in real time, providing support for data operations.

[0174] 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.

[0175] In addition, an embodiment of the present disclosure further provides a vehicle, wherein the vehicle includes a controller, wherein the controller includes:

[0176] a memory for storing machine-readable instructions; and

[0177] The processor is used to call and execute the machine-readable instructions stored in the memory to implement the steps of monitoring the configuration update as described in the above embodiments.

[0178] Based on the same technical concept, the embodiment of the present application also provides a computer device. Figure 5 FIG. 1 is a schematic diagram of a computer device provided in an embodiment of the present application, including:

[0179] Processor 501 , memory 502 and bus 503 . The memory 502 stores machine-readable instructions executable by the processor 501, and the processor 501 is used to execute the machine-readable instructions stored in the memory 502. When the machine-readable instructions are executed by the processor 501, the processor 501 performs the following steps: S201: using the main configuration management module, receiving the software configuration update instruction issued by the cloud, and determining the target electronic control unit where the target software associated with the software configuration update instruction is located; S202: sending the software configuration update instruction to the slave configuration management module in the target electronic control unit, and obtaining the instruction reception status information fed back by the slave configuration management module; S203: when the instruction reception status information indicates successful reception, using the slave configuration management module to distribute the configuration file indicated by the software configuration update instruction to the target software, and feeding back the distribution status information of the configuration file under each state node to the main configuration management module; the distribution status information is used to indicate the real-time flow status of the configuration file; and S204: using the main configuration management module, feeding back the instruction reception status information and the distribution status information to the cloud; the cloud is used to generate configuration update statistics using the instruction reception status information and the distribution status information corresponding to each vehicle.

[0180] The above-mentioned memory 502 includes a memory 5021 and an external memory 5022; the memory 5021 here is also called an internal memory, which is used to temporarily store the calculation data in the processor 501, as well as the data exchanged with the external memory 5022 such as a hard disk. The processor 501 exchanges data with the external memory 5022 through the memory 5021. When the computer device is running, the processor 501 communicates with the memory 502 through the bus 503, so that the processor 501 executes the execution instructions mentioned in the above method embodiment.

[0181] 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 configuration update monitoring method described in the above method embodiment are executed. The storage medium can be a volatile or non-volatile computer-readable storage medium.

[0182] The computer program product of the configuration update monitoring method provided in the embodiment of the present disclosure includes a computer-readable storage medium storing program code, and the instructions included in the program code can be used to execute the steps of the configuration update monitoring method described in the above method embodiment. Please refer to the above method embodiment for details, which will not be repeated here.

[0183] The computer program product may be implemented in hardware, software or a combination thereof. In one optional embodiment, the computer program product is embodied as a computer storage medium, and in another optional embodiment, the computer program product is embodied as a software product, such as a software development kit (SDK) and the like.

[0184] 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.

[0185] 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.

[0186] 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.

[0187] 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.

[0188] If the technical solution of this application involves personal information, the product using the technical solution of this application has clearly informed the personal information processing rules and obtained the individual's voluntary consent before processing the personal information. If the technical solution of this application involves sensitive personal information, the product using the technical solution of this application has obtained the individual's separate consent before processing the sensitive personal information, and at the same time meets the "explicit consent" requirement. For example, on personal information collection devices such as cameras, clear and prominent signs are set to inform that the personal information collection scope has been entered and personal information will be collected. If the individual voluntarily enters the collection scope, it is deemed that he or she agrees to the collection of his or her personal information; or on the device that processes personal information, the personal information processing rules are notified by obvious signs / information, and the individual's authorization is obtained through pop-up information or by asking the individual to upload his or her personal information; among them, the personal information processing rules may include information such as the personal information processor, the purpose of personal information processing, the processing method, and the type of personal information processed.

[0189] 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. A monitoring method for configuration update, characterized in that: Applied to vehicles, including: Using the main configuration management module, receiving the software configuration update instruction sent from the cloud, and determining the target electronic control unit where the target software associated with the software configuration update instruction is located; Sending the software configuration update instruction to the slave configuration management module in the target electronic control unit, and obtaining instruction reception status information fed back by the slave configuration management module; In the case where the instruction reception status information indicates successful reception, the configuration file indicated by the software configuration update instruction is distributed to the target software by using the slave configuration management module, and the distribution status information of the configuration file under each status node is fed back to the master configuration management module; the distribution status information is used to indicate the real-time flow status of the configuration file; The main configuration management module is used to feed back the instruction reception status information and the distribution status information to the cloud; the cloud is used to generate configuration update statistics using the instruction reception status information and the distribution status information corresponding to each vehicle.

2. The method according to claim 1, characterized in that The distribution status information at least includes configuration file download status, configuration file distribution status, configuration file verification status, configuration file abnormal status, and configuration file application status.

3. The method according to claim 2, characterized in that The configuration file verification status includes a first verification status for indicating whether the configuration file is complete; the configuration file distribution status includes a first distribution status for indicating that the configuration file has been sent to the target software; The method of distributing the configuration file indicated by the software configuration update instruction to the target software by using the slave configuration management module, and feeding back the distribution status information of the configuration file under each status node to the master configuration management module, comprises: In the case where the software configuration update instruction includes a configuration file download address, downloading the configuration file according to the configuration file download address, and feeding back the configuration file download status to the main configuration management module in real time; When the configuration file download status indicates that the download is successful, performing integrity check on the configuration file, and feeding back the obtained first check status to the main configuration management module; When the first verification status indicates that the configuration file is complete, the configuration file is sent to the target software, and the first distribution status is fed back to the main configuration management module.

4. The method according to claim 3, characterized in that The configuration file verification state further includes a second verification state for indicating whether the file format of the configuration file matches the target software; the configuration file distribution state further includes a second distribution state for indicating whether the target software successfully receives the configuration file; After sending the configuration file to the target software, the method further includes: In the case where the target software successfully receives the configuration file, feeding back to the main configuration management module a second distribution status indicating that the configuration file has been successfully received; Performing format verification on the configuration file using the target software, and feeding back the obtained second verification status to the main configuration management module; When the second verification status indicates that the configuration file matches the target software, overwriting the stored configuration file with the configuration file, and determining a file update timing according to an update rule of the target software, and when the file update timing is reached, performing a configuration update on the target software using the stored configuration file; According to the configuration update result, the configuration file application status is generated and fed back to the main configuration management module.

5. The method according to claim 4, characterized in that When the file update opportunity is reached, updating the configuration of the target software using the stored configuration file includes: When the file update opportunity is reached, detecting whether a configuration file is stored in the storage space of the target software, and generating a file loss status according to the detection result; When the file loss status indicates that the configuration file is not lost, performing an abnormality detection on the configuration file stored in the storage space to obtain a file detection status, and feeding back the file loss status and the file detection status as the configuration file abnormality status to the main configuration management module; When the file detection status indicates that there is no abnormality in the configuration file, the target software is updated by using the stored configuration file.

6. The method according to claim 2, characterized in that When the distribution status information under any status node indicates that the configuration file fails to be transferred, the distribution status information also includes a transfer failure reason; The reason for the transfer failure includes one of the following: failure to download the configuration file, failure to distribute the configuration file, failure to pass the configuration file verification, anomaly in the configuration file, and failure to apply the configuration file.

7. The method according to claim 1, characterized in that The configuration files include a plurality of configuration files, and different configuration files are used to configure and update different functions of the target software; The distribution status information includes distribution status information corresponding to each of the configuration files.

8. The method according to claim 1, characterized in that The utilizing the main configuration management module to feed back the instruction receiving status information and the distribution status information to the cloud comprises: In the event that there is an abnormality in the network communication between the main configuration management module and the cloud, storing the instruction reception status information and the distribution status information in the main configuration management module; In response to the network communication being restored, the instruction reception status information and the distribution status information are fed back to the cloud.

9. A vehicle, characterized in that: A controller is included, the controller comprising: a memory for storing machine-readable instructions; and A processor is used to call and execute the machine-readable instructions stored in the memory to implement the steps of the configuration update monitoring method according to any one of claims 1 to 8.

10. A computer device, characterized in that: include: A processor and a memory, wherein the memory stores machine-readable instructions executable by the processor, and the processor is used to execute the machine-readable instructions stored in the memory. When the machine-readable instructions are executed by the processor, the processor executes the steps of the configuration update monitoring method as described in any one of claims 1 to 8.

11. A computer program product, which, when executed by a computer device, performs the steps of the configuration update monitoring method according to any one of claims 1 to 8.

Images