Configuration file updating verification method and device

Abstract

The invention discloses a configuration file updating verification method and device, and belongs to the field of embedded device configuration file updating. The method comprises the following steps: receiving a user configuration modification storage request; updating a first version identifier and a second version identifier in the user configuration; receiving a configuration file updating request; obtaining a first version identifier and a second version identifier of operation configuration of the operation equipment; comparing the first version identifier and the second version identifier of the operation configuration and the user configuration to generate a version tree congeneric identifier; and if the version tree congeneric identifier is true, updating the user configuration to the running equipment. According to the invention, the problems of investment cost caused by additional deployment and configuration of a management server in the prior art and high requirement on embedded equipment by deployment of a version control system in the prior art are solved; the correctness when different operation and maintenance engineer stations update the configuration file to the equipment is ensured, and the operation and maintenance efficiency is improved.

Description

Technical Field

[0001] The invention belongs to the field of configuration file updating of embedded devices, and in particular relates to a configuration file updating verification method and device. Background Art

[0002] Substation data acquisition equipment usually needs to be configured according to the deployment interval. In addition, in order to facilitate daily operation and maintenance, the equipment configuration file can be modified and backed up by multiple operation and maintenance engineer stations, which will result in multiple configuration files with different contents stored in different operation and maintenance engineer stations. If the configuration file is modified and updated to the equipment operation by mistake based on the non-operational configuration, it may cause the equipment to malfunction. In addition, as the scene requirements change, the configuration file after the equipment program is upgraded may be different from the grammatical structure of the configuration file backed up by the operation and maintenance engineer station. The incorrect use of the configuration file may cause the equipment to fail to operate normally.

[0003] In actual applications, the operation and maintenance personnel are generally required to obtain the running configuration of the running equipment, modify the running configuration to obtain a new configuration, and then update the new configuration to the equipment operation. However, it cannot be ruled out that the operation and maintenance personnel mistakenly use the backup configuration of the local operation and maintenance engineer station as the running configuration, and in some scenarios, the operation and maintenance personnel need to modify the configuration file offline outside the substation to improve the operation and maintenance efficiency, and then directly update the configuration to the equipment operation after entering the station.

[0004] There are many configuration update verification schemes in the prior art. One type requires the deployment of a configuration management server to centrally manage all configuration file modifications for all devices, which requires additional server and communication investment. Its essence is still to verify the backup configuration and the new configuration. When the backup configuration and the running configuration are inconsistent, the verification function will still be lost. Another type requires the deployment of a version control system in the device to record all modifications to the configuration file of this device. This solution has additional requirements for the computing performance and storage space of the device, but substation data acquisition equipment is generally an embedded device, and the use of this type of solution is limited. Summary of the invention

[0005] In order to solve the problems existing in the prior art, the embodiment of the present invention proposes a configuration file update verification method and device. The technical solution is as follows:

[0006] A first aspect of an embodiment of the present invention provides a configuration file update verification method, comprising:

[0007] Receive user configuration modification and save request;

[0008] Updating the first version identifier and the second version identifier in the user configuration;

[0009] receiving a configuration file update request;

[0010] Obtain a first version identifier and a second version identifier of a running configuration of a running device;

[0011] Compare the first version identifier and the second version identifier of the running configuration and the user configuration to generate a version tree same-belonging identifier;

[0012] If the version tree sameness flag is true, the user configuration is updated to the running device.

[0013] In some embodiments, before receiving a user configuration modification and saving request, the process includes:

[0014] receiving a running configuration backup request;

[0015] Get the running device running configuration as user configuration;

[0016] Set the first edit flag of the user configuration association to true.

[0017] In some embodiments, after comparing the first version identifier and the second version identifier of the running configuration with the user configuration to generate a version tree same identifier, the method further includes:

[0018] If the version tree sameness flag is false, execute the subsequent steps according to the update strategy;

[0019] If the update strategy is to cancel the update, keep the version tree same flag as false;

[0020] If the update policy is mandatory update, the update version tree same flag is true;

[0021] If the update strategy is online merging, the running configuration of the running device is obtained, and the user configuration and the running configuration are merged.

[0022] In some embodiments, updating the first version identifier and the second version identifier in the user configuration includes:

[0023] If the first edit flag associated with the user configuration is true, the first version flag in the user configuration is replaced with the second version flag in the user configuration, the second version flag is reset to the combination of the unique flag of the operation and maintenance engineer station and the edit version, and the first edit flag associated with the user configuration is set to false;

[0024] If the first edit flag associated with the user configuration is false, the edit version in the second version flag of the user configuration is increased by one step.

[0025] In some embodiments, comparing the first version identifier and the second version identifier of the running configuration and the user configuration to generate a version tree common identifier includes:

[0026] If the first version identifiers of the user configuration and the running configuration are the same, the unique identifier of the operation and maintenance engineer station in the second version identifier is the same, and the edit version in the second version identifier of the user configuration is greater than the edit version in the second version identifier of the running configuration, then the update version tree sameness identifier is true;

[0027] If the user configuration first version identifier and the running configuration second version identifier are the same, then the update version tree sameness identifier is true.

[0028] A second aspect of an embodiment of the present invention provides a configuration file update verification device, comprising:

[0029] A first receiving module, used to receive a user configuration modification and saving request;

[0030] A first processing module, used to update a first version identifier and a second version identifier in a user configuration;

[0031] A second receiving module, used for receiving a configuration file update request;

[0032] A first query module is used to obtain a first version identifier and a second version identifier of a running configuration;

[0033] The second processing module is used to compare the first version identifier and the second version identifier of the running configuration with the user configuration, and generate a version tree same-belonging identifier;

[0034] The update module is used to update the user configuration to the running device if the version tree sameness flag is true.

[0035] According to a third aspect of an embodiment of the present invention, a computer device is provided, comprising a memory, at least one processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the above method when executing the program.

[0036] According to a fourth aspect of an embodiment of the present invention, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the above method is performed.

[0037] Beneficial effect: The present invention updates the first version identifier and the second version identifier in the user configuration in the user configuration editing stage, compares the running configuration with the first version identifier and the second version identifier of the user configuration in the configuration update stage to generate a version tree same-belonging identifier, and updates the user configuration to the device operation when the version tree same-belonging identifier is true; avoids the investment cost caused by the additional deployment of a configuration management server in one of the prior arts, and the problem of high requirements for embedded devices for deploying a version control system in the second prior art; ensures the correctness of different operation and maintenance engineer stations when updating configuration files to the device, and improves the operation and maintenance efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0038] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for use in the embodiments will be briefly introduced below. It should be understood that the following drawings only show certain embodiments of the present application and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying creative work.

[0039] Figure 1 A schematic diagram showing a structure of an implementation environment provided by an embodiment of the present invention is shown;

[0040] Figure 2 A schematic diagram of a flow chart of a configuration file updating method provided by an embodiment of the present invention is shown;

[0041] Figure 3 A schematic diagram of the structure of a device provided by an embodiment of the present invention is shown;

[0042] Figure 4 A schematic structural diagram of a computer device provided by an embodiment of the present invention is shown. DETAILED DESCRIPTION

[0043] The present invention will be further described in detail below with reference to the accompanying drawings.

[0044] To make the purpose, technical scheme and advantages of the embodiments of the present application clearer, the technical scheme in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, rather than all of the embodiments. The components of the embodiments of the present application generally described and shown in the drawings here can be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of the present application provided in the drawings is not intended to limit the scope of the application claimed for protection, but merely represents the selected embodiments of the present application. Based on the embodiments of the present application, all other embodiments obtained by those skilled in the art without making creative work belong to the scope of protection of the present application.

[0045] Please refer to Figure 1 , which shows a schematic diagram of a structure of an implementation environment provided by an embodiment of the present invention. The implementation environment includes: at least one operation and maintenance engineer station 120 and an operation device 140.

[0046] The operation and maintenance engineer station 120 provides a function of storing and editing user configurations, and is used to update configuration files to the operating device 140 .

[0047] At least one operation and maintenance engineer station 120 is connected to the operation device 140 via a wired or wireless network.

[0048] The operation device 140 applies the user configuration from the operation and maintenance engineering station 120 as the operation configuration, and provides functions including but not limited to signal acquisition, data processing and storage, and signal output. The present invention does not limit the functional use of the operation device.

[0049] Please refer to Figure 2 , which shows a schematic diagram of the process of the configuration file update verification method provided by an embodiment of the present invention. In this embodiment, the configuration file verification update method is applied to Figure 1 The operation and maintenance engineer station 120 is used as an example. The method includes:

[0050] Step 204, receiving a user configuration modification and saving request;

[0051] The user configuration is a configuration file backed up by the operation and maintenance engineer station, which is used to turn on / off specific functions of the target device or improve / reduce specific performance of the target device to meet specific needs of the usage scenario. The request is generated when the operation and maintenance personnel modify and save the user configuration.

[0052] Step 205, updating the first version identifier and the second version identifier in the user configuration;

[0053] Step 206, receiving a configuration file update request;

[0054] Only when the locally modified user configuration is updated to the running device, the user configuration will be used as the running configuration by the running device, thereby enabling / disabling specific functions of the running device or improving / degrading specific performance. The update request is generated when the operation and maintenance personnel trigger the configuration update operation.

[0055] Step 207, obtaining a first version identifier and a second version identifier of a running configuration of the running device;

[0056] The running configuration comes from the factory preset or the last configuration update, and like the user configuration, carries a specially defined first version identifier and a second version identifier.

[0057] Step 208, comparing the first version identifier and the second version identifier of the running configuration and the user configuration, and generating a version tree same identifier;

[0058] Step 210: If the version tree sameness flag is true, update the user configuration to the running device.

[0059] The update action is implemented through a wired or wireless network established between the operation and maintenance engineer station and the running equipment, including but not limited to file transfer, database reading and writing, sending a restart instruction for the running equipment, etc.

[0060] The configuration file update verification method provided by the embodiment of the present application is to update the first version identifier and the second version identifier in the user configuration in the user configuration editing stage, compare the running configuration with the first version identifier and the second version identifier of the user configuration in the configuration update stage to generate a version tree same identifier, and update the user configuration to the device operation when the version tree same identifier is true; avoids the investment cost caused by the additional deployment of configuration management servers in one of the prior arts and the high requirements of the deployed version control system on embedded devices in the second prior art; ensures the correctness of different operation and maintenance engineer stations when updating configuration files to the device, and improves the operation and maintenance efficiency.

[0061] In an optional embodiment, before receiving the user configuration modification and saving request in step 204, the following steps are included:

[0062] Step 201, receiving a running configuration backup request;

[0063] Modification and saving based on the running configuration of the running device can reduce the probability of configuration update abnormalities. The operation and maintenance personnel can generate this request by manually performing a backup operation in the pre-editing stage, or the operation and maintenance engineer station can generate this request based on the backup strategy; the backup strategy may include: scheduled backup, startup backup, pre-editing backup, etc.

[0064] Step 202, obtaining the running configuration of the running device as the user configuration;

[0065] Step 203: Set the first edit flag associated with the user configuration to true.

[0066] Each user configuration of each operation and maintenance engineer station is associated with an independent first-editing identifier, which is used to distinguish whether this user configuration has been edited and saved by this station after being backed up on this station, affecting the subsequent update logic of the first version identifier and the second version identifier; this identifier can be represented by any method with temporal and spatial invariance of true and false judgment results, such as a numerical value (0 indicates false, 1 indicates true), a Boolean value (false indicates false, true indicates true), etc.

[0067] In an optional embodiment, in step 208, after comparing the first version identifier and the second version identifier of the running configuration and the user configuration to generate a version tree same identifier, the following further includes:

[0068] Step 209: If the version tree sameness flag is false, execute subsequent steps according to the update strategy.

[0069] The update strategy can be selected from a list including cancel update, forced update, online merge, etc.; the update strategy can be pre-configured or selected online by the operation and maintenance engineer. The present invention does not limit the update strategy list and setting time. This step also includes:

[0070] Step 2091, if the update strategy is to cancel the update, keep the version tree sameness flag as false;

[0071] Step 2092, if the update policy is mandatory update, the update version tree sameness flag is true;

[0072] Step 2093: If the update strategy is online merging, obtain the running configuration of the running device, and merge the user configuration with the running configuration; the merging operation is as follows:

[0073] For configuration items that are the same between the user configuration and the running configuration, the content of the running configuration is replaced with the content of the user configuration;

[0074] For configuration items in the user configuration that are not included in the running configuration, create the configuration item in the running configuration and copy the content of the configuration item in the user configuration to add it to the configuration item;

[0075] For configuration items in the running configuration that are not included in the user configuration, the content of the configuration item in the running configuration is retained;

[0076] Update the version tree's sibling flag to true.

[0077] In an optional embodiment, step 205, updating the first version identifier and the second version identifier in the user configuration, includes:

[0078] Step 2051, if the first edit flag associated with the user configuration is true, the first version flag in the user configuration is replaced with the second version flag in the user configuration, the second version flag is reset to a combination of the unique flag of the operation and maintenance engineer station and the edit version, and the first edit flag associated with the user configuration is set to false;

[0079] The unique identifier of the operation and maintenance engineer station is used to identify the uniqueness of the operation and maintenance engineer station. According to the requirements of the application scenario, the uniqueness can be divided into local uniqueness and global uniqueness.

[0080] The local uniqueness means that all operation and maintenance engineer stations that can update the configuration of the same running device have different unique identifiers, and the unique identifiers of the operation and maintenance engineer stations that update the configuration of different running devices can be the same. The local unique identifier can be specified by the operation and maintenance personnel when the operation and maintenance engineer station is first deployed, or automatically generated according to the strategy, which includes the node number of the operation and maintenance engineer station, the IPv4 tail address, etc. and their combination.

[0081] The term "globally unique" means that all operation and maintenance engineer stations have different unique identifiers. The globally unique identifier can be automatically generated when the operation and maintenance engineer station is first deployed. The generation method can use UUID (Universally Unique Identifier) ​​or a custom strategy. The custom strategy includes the deployment time of the operation and maintenance engineer station, hard disk serial number, motherboard serial number, CPU serial number, BIOS serial number, contract number and other fields and their combinations.

[0082] The edited version is used to reflect the editing history of the user configuration in the operation and maintenance engineer station associated with the unique identifier. This field can be represented by any method with time and space invariance of size determination results, such as a numerical value (0, 1, ...), a string (0.0.2, 0.1.1, ...); the reset edited version is to update the edited version to the preset minimum version, such as a numerical value 0, a string 0.0.1, etc.

[0083] In an optional embodiment, the above step 205 further includes:

[0084] Step 2052: If the first edit flag associated with the user configuration is false, increase the edit version in the second version flag of the user configuration by one step.

[0085] When the edit version is represented by a numerical value, the step size may be 1, and the edit version increases by one step, that is, from 1 to 2, 100 to 101, and so on; when the edit version is represented by a string, the step size may be 0.0.1, and the edit version increases by one step, that is, from 0.0.1 to 0.0.2, 0.0.100 to 0.0.101. The edit version field can be progressively advanced by combining with different bases, such as base 256, from 0.0.256 to 0.1.1.

[0086] In an optional embodiment, step 208, comparing the first version identifier and the second version identifier of the running configuration and the user configuration to generate a version tree common identifier, includes:

[0087] Step 2081, if the first version identifiers of the user configuration and the running configuration are the same, the unique identifier of the operation and maintenance engineer station in the second version identifier is the same, and the edit version in the second version identifier of the user configuration is greater than the edit version in the second version identifier of the running configuration, then the update version tree sameness identifier is true;

[0088] The size comparison of the edited versions needs to adopt a method in which the edited versions are associated and the size determination result is time-space invariant.

[0089] In an optional embodiment, the above step 208 further includes:

[0090] Step 2082: If the user configuration first version identifier and the running configuration second version identifier are the same, then the update version tree sameness identifier is true.

[0091] The following is an apparatus embodiment of the present invention. For details not described in detail in the apparatus embodiment, reference may be made to the corresponding method embodiment described above.

[0092] Please refer to Figure 3 , which shows a structural block diagram of a configuration file update verification device provided by an embodiment of the present invention. The configuration file update verification device provided by this embodiment can be implemented by software, hardware or a combination of both. Figure 1 All or part of the central operation and maintenance engineer station 120.

[0093] The device includes:

[0094] The first receiving module 31 is used to receive a user configuration modification and saving request;

[0095] A first processing module 32, used to update the first version identifier and the second version identifier in the user configuration;

[0096] A second receiving module 33, configured to receive a configuration file update request;

[0097] A first query module 34 is used to obtain a first version identifier and a second version identifier of a running configuration;

[0098] The second processing module 35 is used to compare the first version identifier and the second version identifier of the running configuration with the user configuration, and generate a version tree same-belonging identifier;

[0099] The updating module 36 is used to update the user configuration to the running device if the version tree sameness flag is true.

[0100] In an optional embodiment, before the first receiving module 31, it includes:

[0101] The third receiving module 37 is used to receive a running configuration backup request;

[0102] A first acquisition module 38, used to acquire the running configuration of the running device as the user configuration;

[0103] The third processing module 39 is used to set the first editing flag associated with the user configuration to true.

[0104] The first processing module 32 includes:

[0105] The first processing unit 321 is used to replace the first version identifier in the user configuration with the second version identifier in the user configuration if the first edit identifier associated with the user configuration is true, and reset the second version identifier to a combination of the unique identifier of the operation and maintenance engineer station and the edit version, and set the first edit identifier associated with the user configuration to false;

[0106] In an optional embodiment, the first processing module 32 further includes:

[0107] The second processing unit 322 is configured to increase the edit version in the user-configured second version identifier by a step size if the first edit identifier associated with the user configuration is false;

[0108] The second processing module 35 comprises:

[0109] The third processing unit 351 is used to update the version tree sameness flag to true if the user configuration and the running configuration first version flag are the same, the operation and maintenance engineer station unique flag in the second version flag is the same, and the edit version in the user configuration second version flag is greater than the edit version in the running configuration second version flag;

[0110] In an optional embodiment, the second processing module 35 further includes:

[0111] The fourth processing unit 352 is configured to update the version tree sameness flag to true if the user configuration first version flag and the running configuration second version flag are the same.

[0112] Corresponds to Figure 2 A configuration file update verification method in the present application embodiment also provides a computer device 40, such as Figure 4 As shown, the device includes a memory 41, a processor 42, and a computer program stored in the memory 41 and executable on the processor 42, wherein the configuration update method is implemented when the processor 42 executes the computer program.

[0113] Specifically, the memory 41 and the processor 42 can be general-purpose memories and processors, which are not specifically limited here. When the processor 42 runs the computer program stored in the memory 41, the configuration update method can be executed.

[0114] Corresponds to Figure 2 A configuration file update verification method in the present application, an embodiment of the present application 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 above-mentioned configuration update method are executed.

[0115] Specifically, the storage medium can be a general storage medium, such as a mobile disk, a hard disk, etc. When the computer program on the storage medium is run, the above-mentioned configuration update method can be executed. The configuration file update verification method and device provided in the embodiment of the present application are to update the first version identifier and the second version identifier in the user configuration in the user configuration editing stage, compare the running configuration with the first version identifier and the second version identifier of the user configuration in the configuration update stage to generate a version tree same identifier, and update the user configuration to the device operation when the version tree same identifier is true; avoid the investment cost brought by the additional deployment of a configuration management server in one of the prior arts and the high requirements of the deployed version control system on embedded devices in the second prior art; ensure the correctness of different operation and maintenance engineer stations when updating configuration files to the device, and improve the operation and maintenance efficiency.

[0116] In the embodiments provided in the present application, it should be understood that the disclosed methods and devices 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, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

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

[0118] In addition, each functional unit in the embodiments provided in the present application 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.

[0119] 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 computer-readable storage medium. Based on this understanding, the technical solution of the present application, 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 methods described in each embodiment of the present application. 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.

[0120] It should be noted that similar numbers and letters represent similar items in the following figures. Therefore, once an item is defined in one figure, it does not need to be further defined and explained in subsequent figures. In addition, the terms "first", "second", "third", etc. are only used to distinguish the description and are not to be understood as indicating or implying relative importance.

[0121] Finally, it should be noted that the above-described embodiments are only specific implementation methods of the present application, which are used to illustrate the technical solutions of the present application, rather than to limit them. The protection scope of the present application is not limited thereto. Although the present application is described in detail with reference to the above-mentioned 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-mentioned embodiments within the technical scope disclosed in the present application, 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 application. They should all be included in the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A configuration file update verification method, characterized in that: include: Receive user configuration modification and save request; Updating the first version identifier and the second version identifier in the user configuration; receiving a configuration file update request; Obtain a first version identifier and a second version identifier of a running configuration of a running device; Compare the first version identifier and the second version identifier of the running configuration and the user configuration to generate a version tree same-belonging identifier; If the version tree sameness flag is true, the user configuration is updated to the running device.

2. The method according to claim 1, characterized in that Before receiving a request to save a user configuration modification, include: receiving a running configuration backup request; Get the running device running configuration as user configuration; Set the first edit flag of the user configuration association to true.

3. The method according to claim 1, characterized in that After comparing the first version identifier and the second version identifier of the running configuration with the user configuration to generate a version tree same identifier, the method further includes: If the version tree sameness flag is false, execute the subsequent steps according to the update strategy; If the update strategy is to cancel the update, keep the version tree same flag as false; If the update policy is mandatory update, the update version tree same flag is true; If the update strategy is online merging, the running configuration of the running device is obtained, and the user configuration and the running configuration are merged.

4. The method according to claim 1, 2 or 3, characterized in that: Updating the first version identifier and the second version identifier in the user configuration includes: If the first edit flag associated with the user configuration is true, the first version flag in the user configuration is replaced with the second version flag in the user configuration, the second version flag is reset to the combination of the unique flag of the operation and maintenance engineer station and the edit version, and the first edit flag associated with the user configuration is set to false; If the first edit flag associated with the user configuration is false, the edit version in the second version flag of the user configuration is increased by one step.

5. The method according to claim 1, 2 or 3, characterized in that: Comparing the first version identifier and the second version identifier of the running configuration with the user configuration to generate a version tree same identifier includes: If the first version identifiers of the user configuration and the running configuration are the same, the unique identifier of the operation and maintenance engineer station in the second version identifier is the same, and the edit version in the second version identifier of the user configuration is greater than the edit version in the second version identifier of the running configuration, then the update version tree sameness identifier is true; If the user configuration first version identifier and the running configuration second version identifier are the same, then the update version tree sameness identifier is true.

6. A configuration file update verification device, characterized in that: include: A first receiving module, used to receive a user configuration modification and saving request; A first processing module, used to update a first version identifier and a second version identifier in a user configuration; A second receiving module, used for receiving a configuration file update request; A first query module is used to obtain a first version identifier and a second version identifier of a running configuration; The second processing module is used to compare the first version identifier and the second version identifier of the running configuration with the user configuration, and generate a version tree same-belonging identifier; The update module is used to update the user configuration to the running device if the version tree sameness flag is true.

7. The device according to claim 6, characterized in that Before the first receiving module, it includes: A third receiving module is used to receive a running configuration backup request; A first acquisition module, used for acquiring a running configuration of a running device as a user configuration; The third processing module is used to set the first editing flag associated with the user configuration to true.

8. The device according to claim 6 or 7, characterized in that The first processing module comprises: A first processing unit is configured to replace the first version identifier in the user configuration with the second version identifier in the user configuration if the first editing identifier associated with the user configuration is true, and reset the second version identifier to a combination of the unique identifier of the operation and maintenance engineer station and the edit version, and set the first editing identifier associated with the user configuration to false; The second processing unit is configured to increase the edit version in the second version identifier of the user configuration by a step size if the first edit identifier associated with the user configuration is false.

9. The device according to claim 6 or 7, characterized in that The second processing module comprises: The third processing unit is configured to update the version tree sameness flag to true if the first version flags of the user configuration and the running configuration are the same, the unique flags of the operation and maintenance engineer station in the second version flags are the same, and the edit version in the second version flag of the user configuration is greater than the edit version in the second version flag of the running configuration; The fourth processing unit is configured to update the version tree sameness flag to true if the user configuration first version flag and the running configuration second version flag are the same.

10. A computer device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 5 are implemented.

11. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 5 are executed.

Images