Equipment configuration methods and equipment management system
By maintaining lock files locally on the device to determine the configuration status and intercept configuration commands, the problem of multi-terminal configuration conflicts is resolved, thereby improving the flexibility and reliability of device parameter configuration.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- BOE TECHNOLOGY GROUP CO LTD
- Filing Date
- 2026-04-01
- Publication Date
- 2026-06-30
AI Technical Summary
In multi-terminal configuration scenarios, device parameter configurations are prone to conflicts. Existing single-terminal configuration methods lack flexibility and rely on central servers, resulting in resource waste and poor reliability.
By maintaining a lock file for configuration items locally on the device, intercepting configuration commands and determining the configuration status based on the lock file, configuration conflicts across multiple devices can be avoided, achieving fine-grained configuration conflict protection.
It improves the flexibility and reliability of device parameter configuration, reduces dependence on the central server, simplifies the system structure, and improves configuration efficiency and consistency.
Smart Images
Figure CN122308959A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of equipment management, and in particular to an equipment configuration method and an equipment management system. Background Technology
[0002] In scenarios involving multiple devices and machines, a single management platform is typically used to manage all of them. To improve equipment maintenance efficiency and ensure adaptability, device parameters can be configured on multiple devices. For example, parameters can be configured on the management platform, or users can configure parameters directly on the device's local machine.
[0003] However, configuration conflicts can easily occur in multi-device configuration scenarios. For example, if an administrator and a user configure the same parameter of a device on the management platform and the device itself, respectively, configuration conflicts will occur, leading to configuration failure.
[0004] Currently, to address the issue of multi-device configuration conflicts, configuration permissions can be assigned to a specific device or client, thus preventing conflicts at their source. However, this approach is essentially single-device configuration and cannot be applied to multi-device configuration scenarios, resulting in limited device configuration flexibility. To resolve multi-device configuration conflicts, a central server can be introduced. This central server maintains the configuration status of each device's configuration files. When device configuration is required, interaction with the central server is necessary to confirm the configuration status. Configuration can only proceed if the configuration file is not locked. This method requires a separate central server, and device configuration depends on the stability of the connection with the central server, leading to wasted computing resources and poor reliability. Summary of the Invention
[0005] In view of the above-mentioned defects or deficiencies in the prior art, it is desirable to provide a device configuration method and device management system that can perform fine-grained configuration conflict protection for devices and improve the flexibility and reliability of device parameter configuration.
[0006] Firstly, this application provides a device configuration method applied to a device management system, the system including a management platform and at least one device. The method includes: The device intercepts configuration commands, which are used to configure the target configuration item to be configured; the configuration command is issued by the management platform, or the configuration command is a user's local configuration command; Determine the local storage address of the target configuration item on the device, and then query the lock file corresponding to the target configuration item at that storage address; different configuration items correspond to different lock files; If the query result indicates that the target configuration item is currently in an unconfigured state, then the target configuration item is modified to a configured state, and the configuration instruction is performed on the target configuration item; if the query result indicates that the target configuration item is currently in a configured state, then the configuration instruction is ignored.
[0007] In conjunction with the first aspect, in one possible implementation, the device configuration method further includes: the device generating and maintaining a lock file for the target configuration item during the previous configuration process of the target configuration item, and deleting the lock file for the target configuration item when the target configuration item completes its configuration.
[0008] In conjunction with the first aspect, in one possible implementation, the device configuration method further includes: if no lock file corresponding to the target configuration item is found, then the target configuration item is determined to be in an unconfigured state; if a lock file corresponding to the target configuration item is found, then the target configuration item is determined to be in a configured state.
[0009] In conjunction with the first aspect, in one possible implementation, the device configuration method further includes: if the status parameter in the lock file corresponding to the target configuration item indicates that no management platform or other device is currently configuring the target configuration item, then the target configuration item is determined to be in an unconfigured state; if the status parameter in the lock file corresponding to the target configuration item indicates that a management platform or other device is currently configuring the target configuration item, then the target configuration item is determined to be in a configured state.
[0010] In conjunction with the first aspect, in one possible implementation, modifying the target configuration item to a configuration state includes: generating and maintaining a lock file for the target configuration item, or modifying the state parameters in the lock file corresponding to the target configuration item to state parameters that indicate that a management platform or other device is currently configuring the target configuration item.
[0011] In conjunction with the first aspect, in one possible implementation, the configuration instruction includes configuration parameters for the target configuration item and protection parameters for the target configuration item; the protection parameters are used to characterize whether the target configuration item needs configuration conflict protection.
[0012] In conjunction with the first aspect, in one possible implementation, the device configuration method further includes: generating a configuration conflict protection request based on the target configuration item in the user's local configuration instruction, and sending the configuration conflict protection request to the management platform; receiving the configuration instruction returned by the management platform; the configuration instruction is generated by the management platform in response to the configuration conflict protection request, querying the protection parameters of each target configuration item, and based on the target configuration item and the protection parameters of each target configuration item.
[0013] In conjunction with the first aspect, in one possible implementation, if the protection parameter indicates that the target configuration item needs to be protected against configuration conflicts, then the lock file corresponding to the target configuration item is queried to perform configuration conflict protection for the target configuration item.
[0014] In conjunction with the first aspect, in one possible implementation, the device configuration method further includes: the target configuration item includes a first configuration item that needs to be configured to prevent conflict, and a second configuration item that does not need to be configured to prevent conflict; if the lock file is queried and it is determined that there is a first configuration item in a configured state, the configuration instruction is ignored; if the lock file is queried and it is determined that all first configuration items are in an unconfigured state, the first configuration item is modified to a configured state, and the first and second configuration items are configured in response to the configuration instruction.
[0015] In conjunction with the first aspect, in one possible implementation, the device intercepts configuration instructions by: creating a target hook function in the device's operating system and configuring the trigger condition of the target hook function to detect a configuration instruction; and calling the target hook function to intercept the configuration instruction.
[0016] Secondly, this application also provides a device management system. The device configuration method and device management system include a management platform and at least one device. The management platform is used to, in response to a user's configuration operation, determine the device to be configured and the target configuration item to be configured; generate a configuration instruction based on the target configuration item, and send the configuration instruction to the device to be configured; the device is used to intercept the user's local configuration instruction or the configuration instruction sent by the management platform, determine the local storage address of the target configuration item on the device, query the lock file corresponding to the target configuration item at the storage address; if the query result indicates that the target configuration item is currently in an unconfigured state, then modify the target configuration item to a configured state, and configure the target configuration item in response to the configuration instruction; if the query result indicates that the target configuration item is currently in a configured state, then ignore the configuration instruction; different configuration items correspond to different lock files.
[0017] In conjunction with the second aspect, in one possible implementation, the management platform is also used to provide a parameter configuration interface; the parameter configuration interface includes multiple configuration items corresponding to the device and conflict protection requirement configuration items corresponding to each configuration item; the conflict protection requirement configuration items are used to configure the protection parameters of the configuration items, and the protection parameters are used to characterize whether the configuration item needs to be configured for conflict protection; receive the configuration parameters and protection parameters input to the target configuration item, and generate the configuration instructions for the target configuration item.
[0018] This application provides a device configuration method and a device management system. When a management platform or device locally configures a target configuration item in the device, the device intercepts the configuration command, first determines the local storage address of the target configuration item, and then queries the lock file corresponding to the target configuration item at the storage address. If the query result indicates that the target configuration item is currently in an unconfigured state, the target configuration item is modified to a configured state, and the target configuration item is configured in response to the configuration command; if the query result indicates that the target configuration item is currently in a configured state, the configuration command is ignored.
[0019] In this embodiment, the device determines the current configuration status of each target configuration item by using the lock file corresponding to the configuration item maintained locally. By changing the lock file, the current configuration status of the target configuration item is changed, thereby avoiding configuration conflicts of target configuration items in multi-device configuration scenarios. Setting a lock file for each configuration item to represent its configuration status, compared to existing device conflict prevention configuration schemes that use the configuration file containing the configuration item as a unit, this embodiment can achieve device configuration on a unit-by-unit basis, providing finer configuration granularity and enabling refined configuration conflict prevention for the device.
[0020] Furthermore, the device's configuration file is maintained locally on the device. Combined with a pre-defined interceptor for configuration commands, conflict protection for each target configuration item can be achieved locally on the device. This eliminates the need to grant configuration permissions to specific devices, allowing multiple devices to configure the device, significantly improving configuration flexibility. Moreover, there's no need for an additional central server in the system to manage device conflict protection, avoiding a complex system architecture. Consequently, the device doesn't require complex interactions with a central server, and the locally deployed conflict protection solution effectively improves the efficiency and reliability of device parameter configuration. Attached Figure Description
[0021] Other features, objects, and advantages of this application will become more apparent from the following detailed description of non-limiting embodiments with reference to the accompanying drawings: Figure 1 This is a schematic diagram of the structure of the device management system in one embodiment; Figure 2 This is a flowchart illustrating a device configuration method in one embodiment; Figure 3 This is another flowchart illustrating the device configuration method in one embodiment; Figure 4 This is a schematic diagram of the parameter configuration interface of the management platform in one embodiment; Figure 5 This is a schematic diagram of another parameter configuration interface of the management platform in one embodiment; Figure 6 This is another flowchart illustrating the device configuration method in one embodiment; Figure 7 This is another flowchart illustrating the device configuration method in one embodiment; Figure 8 This is another flowchart illustrating the device configuration method in one embodiment; Figure 9 This is another flowchart illustrating the device configuration method in one embodiment. Detailed Implementation
[0022] The present application will now be described in further detail with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and not intended to limit it. Furthermore, it should be noted that, for ease of description, only the parts relevant to the invention are shown in the accompanying drawings.
[0023] It should be noted that, unless otherwise specified, the embodiments and features described in this application can be combined with each other. The present application will now be described in detail with reference to the accompanying drawings and embodiments. Furthermore, the term "and / or" in this document is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. The terms "first" and "second," etc., in the specification and claims of the embodiments of this application are used to distinguish different objects, not to describe a specific order of objects.
[0024] To improve equipment maintenance efficiency and ensure equipment adaptability, it is now possible to configure equipment parameters across multiple devices. For example, device parameters can be configured on a management platform, or users can configure parameters directly on their local devices. However, configuration conflicts can easily occur in multi-device configuration scenarios. Specifically, when administrators and users configure the same device parameter on both the management platform and the device itself, configuration errors can arise, leading to configuration failures.
[0025] To address configuration conflicts across multiple devices, fixed single-write and dynamic single-write methods are commonly used. For example, fixed single-write grants "write" permissions to a specific device or client, allowing the designated device to handle all editing operations and send the new version to other devices after completion. However, this method lacks flexibility and is limited to multi-user collaboration scenarios. Dynamic single-write introduces a central server to store and maintain file lock states. When a user edits a file on one device, they must interact with the central server to confirm the file's lock state (provided the file is not locked) before editing can proceed. This method is complex, requiring a separate central server, and its implementation depends on the stability of the connection to the central server, leading to resource waste and poor reliability. Additionally, in scenarios allowing simultaneous file editing across multiple devices, configuration conflicts can be resolved by merging files edited on different devices during the file submission phase. However, file merging often requires manual user intervention, as the system struggles to make automatic decisions, resulting in high operational complexity and low efficiency.
[0026] Based on this, embodiments of this application provide a device configuration method and a device management system, which can perform fine-grained configuration conflict protection for devices and improve the flexibility and reliability of device parameter configuration.
[0027] The device configuration method provided in this application embodiment can be applied to, for example, Figure 1 The equipment management system shown includes a management platform 10 and at least one device 20. The management platform 10 can be deployed on a client-side application, or accessed via a web interface from the client, enabling the management platform 10 to manage the devices 20. Devices 20 can be smart display devices, wearable devices, production equipment, etc.
[0028] In one embodiment, such as Figure 2 As shown, a device configuration method is provided, which is applied to Figure 1 Taking device 20 as an example, the explanation includes the following steps: Step 101: Device 20 intercepts configuration commands.
[0029] The configuration command is used to configure the target configuration item to be configured.
[0030] The configuration command is issued by the management platform 10, or it is a user-local configuration command.
[0031] In this embodiment, an administrator or user can log in to the management platform on a client and configure the device 20 through the parameter configuration interface provided by the management platform 10. In response to the administrator's parameter configuration operation, the management platform 10 determines at least one target configuration item to be configured and the configuration parameters of each target configuration item, and generates a configuration command based on the at least one target configuration item and the configuration parameters of each target configuration item, which is then sent to the device 20.
[0032] Users can also configure parameters directly on device 20. For example, they can open the configuration file of device 20 through a client connected to device 20, or open the configuration file of device 20 through a display screen integrated on device 20. In response to the user's parameter configuration operation, device 20 determines at least one target configuration item to be configured and the configuration parameters of each target configuration item, and generates a local configuration instruction for the user, i.e., a configuration instruction.
[0033] In one possible implementation, in addition to the identifier or name of the target configuration item and the configuration parameters of the target configuration item, the configuration instruction may also include the identifier of the device 20, the identifier (or name) of the configuration file where each target configuration item is located, the storage address of the configuration file in the device 20, the generation time of the configuration instruction, the user identifier, and other content.
[0034] Device 20 does not directly respond to configuration commands issued by management platform 10 or locally generated configuration commands, to avoid configuration conflicts caused by simultaneous configuration of the same configuration item by management platform 10 or local device. Instead, it first intercepts the configuration command, checks for configuration conflicts among the target configuration items in the command, and determines whether there is a situation where each target configuration item in the command is configured on multiple devices. Only when it is determined that there is no situation where any target configuration item in the command is configured on multiple devices will device 20 respond to the configuration command and configure the target configuration item locally.
[0035] Specifically, for configuration commands issued by management platform 10, a Device Management Agent (DMA) program can be pre-deployed locally on device 20, and the DMA can be configured to intercept configuration commands issued by management platform 10. For configuration commands generated locally on device 20, the operating logic of the operating system on which device 20 depends can be modified in advance to intercept the configuration commands after they are detected but before a response is received. For example, a target hook function can be pre-configured in the operating system to detect and intercept configuration commands.
[0036] Step 102: Determine the local storage address of the target configuration item on device 20, and query the lock file corresponding to the target configuration item at the storage address.
[0037] In this embodiment, device 20 determines whether a configuration conflict exists for the target configuration item by using a lock file. Each device 20 in the device management system maintains its own lock file corresponding to its configuration item locally, specifically in the local storage address of the configuration item. Therefore, after intercepting a configuration command, device 20, based on the mapping relationship between the configuration file and the storage address, first determines the local storage address of the configuration file containing the target configuration item on device 20, i.e., determines the local storage address of the target configuration item. Then, it queries the lock file corresponding to the target configuration item in the storage address, and determines the current configuration status of the target configuration item based on the query result of the lock file corresponding to the target configuration item.
[0038] In one embodiment, device 20 may generate and maintain a corresponding lock file at the storage address of the target configuration item only during the configuration process of the target configuration item. The existence of the lock file reflects the current configuration state of the target configuration item. For example, if a corresponding lock file exists at the storage address of the target configuration item, it indicates that the target configuration item is currently in a configuration state; if a corresponding lock file does not exist at the storage address of the target configuration item, it indicates that the target configuration item is not currently in a configuration state.
[0039] In this scenario, device 20 generates and maintains a lock file for the target configuration item during its previous configuration process, and deletes the lock file when the target configuration item completes its configuration. That is, during the target configuration item's historical configuration process, such as the previous configuration process, device 20 generates a lock file at the storage address where the target configuration item resides. The name of this lock file can include the name of device 20, the name of the configuration file containing the target configuration item, and the name of the target configuration item. The presence of this lock file at the storage address indicates that the target configuration item is currently in a configuration state. After the target configuration item completes its configuration, the corresponding lock file is deleted from its storage address to indicate that the target configuration item is not currently in a configuration state.
[0040] Therefore, after intercepting the configuration command, device 20 can perform a query operation on the lock file corresponding to the target configuration item by checking whether a corresponding lock file exists at the storage address where the target configuration item is located. For example, it can query whether a lock file with the corresponding name exists by searching for the name of the target configuration item. If no lock file corresponding to the target configuration item is found, it is determined that the target configuration item is currently in an unconfigured state; if a lock file corresponding to the target configuration item is found, it is determined that the target configuration item is currently in a configured state.
[0041] In one possible implementation, device 20 can also maintain the lock file of the target configuration item throughout the entire process, and determine the current configuration status of the target configuration item by the specific content of the maintained lock file (i.e., the status parameters in the lock file). For example, the status parameters in the lock file can be 0 or 1. When the status parameter is 0, it indicates that the target configuration item is not currently in a configuration state; when the status parameter is 1, it indicates that the target configuration item is currently in a configuration state. In this case, device 20 modifies the status parameter of the lock file of the target configuration item to 1 during the previous configuration process of the target configuration item, and modifies the status parameter of the corresponding lock file to 0 when the target configuration item completes its configuration.
[0042] Therefore, after intercepting the configuration command, device 20 can first query the corresponding lock file in the storage address where the target configuration item is located by its name, and then determine the status parameters in the lock file. If the status parameters in the lock file corresponding to the target configuration item indicate that the management platform 10 or other device 20 is not currently configuring the target configuration item, then the target configuration item is determined to be in an unconfigured state; if the status parameters in the lock file indicate that the management platform or other device is currently configuring the target configuration item, then the target configuration item is determined to be in a configured state. For example, if the current status parameter in the lock file is 0, it indicates that the management platform 10 or other device 20 is not currently configuring the target configuration item, therefore, the target configuration item is determined to be in an unconfigured state. If the current status parameter in the lock file is 1, it indicates that the management platform 10 or other device 20 is configuring the target configuration item, therefore, the target configuration item is determined to be in a configured state.
[0043] Different configuration items correspond to different lock files. That is, this embodiment of the application can configure the device on a per-configuration-item basis. Compared to device configuration on a per-configuration-file basis, this embodiment of the application can achieve more granular device parameter configuration. In other words, during device configuration, the user can perform configuration operations only on the configuration items in the configuration file that need to be configured or adjusted, without having to configure all configuration items in the configuration file, i.e., without having to repeatedly configure configuration items that do not require configuration or adjustment. After the device 20 intercepts the configuration command, it can use the lock file to perform configuration conflict protection on the corresponding specific configuration items, improving the flexibility of configuration conflict protection during device configuration.
[0044] In one possible implementation, the lock file can be set to a hidden file to prevent it from being visible to the user, thereby preventing the user from modifying the lock file and avoiding affecting the configuration conflict protection of the target configuration items of device 20, thus improving the security of device configuration.
[0045] Step 103: If the query result indicates that the target configuration item is currently in an unconfigured state, then modify the target configuration item to a configured state and configure the target configuration item in response to the configuration command; if the query result indicates that the target configuration item is currently in a configured state, then ignore the configuration command.
[0046] In this embodiment, if the query result of the lock file for the target configuration item indicates that the target configuration item is currently in an unconfigured state, a configuration conflict prevention operation for the target lock file needs to be performed first, and then the target configuration item needs to be configured in response to the configuration command. That is, a lock file for the target configuration item needs to be set so that the set lock file can indicate that the target configuration item is currently in a configured state, preventing configuration conflicts caused by other terminals (management platform 10 or other devices 20) configuring the target configuration item during its current configuration process. Then, in response to the configuration command, the parameters of the target configuration item stored locally on device 20 are replaced with the configuration parameters corresponding to the target configuration item in the configuration command, completing the configuration of the target configuration item.
[0047] The lock file for the target configuration item can be either generated and maintained, or the status parameters in the lock file corresponding to the target configuration item can be modified to indicate that a management platform or other device is currently configuring the target configuration item. Specifically, a lock file with the target configuration item's name can be generated in the storage address where the target configuration item is located, or the status parameters in the lock file corresponding to the target configuration item can be changed so that the modified status parameters indicate that the target configuration item is currently in a configured state, for example, changing the status parameter to 1. Conversely, after configuring the target configuration item, the lock file corresponding to the target configuration item needs to be deleted, or the status parameters in the lock file corresponding to the target configuration item need to be changed so that the modified status parameters indicate that the target configuration item is currently not in a configured state, for example, changing the status parameter to 0.
[0048] In this embodiment of the application, if the query result of the lock file of the target configuration item indicates that the target configuration item is currently in a configuration state, that is, the target configuration item is being configured by the management platform 10 or other devices 20, then the intercepted configuration instruction is ignored to avoid the configuration operation indicated by the intercepted configuration instruction for the target configuration item from conflicting with the current configuration of the target configuration item.
[0049] In one possible implementation, if the query result of the lock file for the target configuration item indicates that the target configuration item is currently in a configuration state, a configuration failure message is generated and returned to the management platform 10 or device 20 that generated the configuration instruction, instructing the management platform 10 or device 20 to display the configuration failure message to the user. The configuration failure message may include the reason for the configuration failure (e.g., configuration conflict), and may also include specific information that caused the configuration conflict (e.g., the identifier of the management platform 10 or device 20 currently configuring the target configuration item, the user identifier, etc.).
[0050] In one possible implementation, after the management platform 10 issues a configuration command, it can wait for the execution result from the device 20. If no execution result is received within a preset time, a configuration failure message can be displayed to the user. This configuration failure message can include the reason for the failure, such as being unable to connect to the device.
[0051] The device configuration method provided in this application embodiment can be summarized as follows: Figure 3 The steps shown are as follows: Step 201: The user triggers the modification operation on the platform (management platform 10) or the device (local device 20); Step 202: Device 20 intercepts configuration commands locally through the device management agent DMA or a pre-set target hook function; Step 203: Device 20 determines whether there is a configuration conflict for the target configuration item indicated by the configuration instruction by querying the lock file; Step 204: If a configuration conflict exists, a conflict error message will be displayed. Step 205: If there are no configuration conflicts, generate the lock file corresponding to the target configuration item; Step 206: Execute device configuration operation (save operation) in response to configuration command; Step 207: After the device configuration is complete, delete the lock file corresponding to the target configuration item to complete the conflict protection configuration.
[0052] In the method provided in this application embodiment, when the management platform or device locally configures a target configuration item in the device, the device intercepts the configuration command, first determines the local storage address of the target configuration item, and then queries the lock file corresponding to the target configuration item at the storage address. If the query result indicates that the target configuration item is currently in an unconfigured state, the target configuration item is modified to a configured state, and the target configuration item is configured in response to the configuration command; if the query result indicates that the target configuration item is currently in a configured state, the configuration command is ignored. In this application embodiment, the device determines the current configuration state of each target configuration item through the lock file corresponding to the configuration item maintained locally, and changes the current configuration state of the target configuration item by changing the lock file, thereby avoiding configuration conflicts of target configuration items in multi-terminal configuration scenarios. By setting a lock file for each configuration item to represent the configuration state of the configuration item, compared with the prior art device conflict protection configuration scheme based on the configuration file where the configuration item is located, this application embodiment can realize device configuration based on configuration items, with finer configuration granularity, and can perform fine-grained configuration conflict protection for the device. Furthermore, the device's configuration file is maintained locally on the device. Combined with a pre-defined interceptor for configuration commands, conflict protection for each target configuration item can be achieved locally on the device. This eliminates the need to grant configuration permissions to specific devices, allowing multiple devices to configure the device, significantly improving configuration flexibility. Moreover, there's no need for an additional central server in the system to manage device conflict protection, avoiding a complex system architecture. Consequently, the device doesn't require complex interactions with a central server, and the locally deployed conflict protection solution effectively improves the efficiency and reliability of device parameter configuration.
[0053] In one embodiment, considering that not all configuration items need to be protected against configuration conflicts, in order to avoid performing configuration conflict protection operations on configuration items that do not need to be protected against configuration conflicts, resulting in a waste of storage and computing resources, the configuration instruction may include the configuration parameters of the target configuration item and the protection parameters of the target configuration item.
[0054] In this embodiment, for the case where the device 20 is configured through the management platform 10, the management platform 10 can provide a parameter configuration interface. This parameter configuration interface can include multiple configuration items corresponding to the device 20 and conflict prevention requirement configuration items corresponding to each configuration item. The multiple configuration items corresponding to the device 20 can be displayed as a configuration file, i.e., as shown below. Figure 4As shown, the parameter configuration interface can include a list of configuration files, displaying multiple configuration files corresponding to device 20 (e.g., redis.conf and nginx.conf in the diagram). The parameter configuration interface can also include multiple configuration items for device 20, such as `server.port` (indicating the server port), `spring.datasource.url` (indicating the database connection address), and `logging.level.root` (indicating the root log level). The parameter configuration interface can also include conflict protection requirement configuration items corresponding to each configuration item of device 20, i.e., "Whether conflict protection is required" in the diagram. The configuration item whose content is modified is the target configuration item, and the modified content is the configuration parameter of the target configuration item. For example, the configuration parameter of the `server.port` item is 8080, the configuration parameter of the `spring.datasource.url` item is `jdbc:mysql: / / localhost:3306 / db`, and the configuration parameter of the `logging.level.root` item is `INFO`.
[0055] Users can click on a configuration file in the configuration file list to navigate to multiple configuration items corresponding to that file. For example, ... Figure 5 As shown, clicking on the nginx.conf configuration file will navigate to several configuration items within nginx.conf, namely the `worker_processes` item (indicated by the number of worker processes) and the `server_name` item (indicated by the server name). Users can modify the parameters of these configuration items by changing their contents; for example, setting `worker_processes` to `auto` and `server_name` to `example.com`. The configuration item whose contents are modified is the target configuration item, and the modified content becomes the configuration parameters for that target configuration item.
[0056] The parameter configuration interface also includes conflict protection requirement configuration items for each configuration item, i.e., "Whether conflict protection is required" in the figure. Users can configure the protection parameters of the target configuration item by checking the boxes. For example, checking the box indicates that the target configuration item needs conflict protection, and the protection parameter can be 11; not checking the box indicates that the target configuration item does not need conflict protection, and the protection parameter can be 00. That is, the protection parameter is used to indicate whether the target configuration item needs to be configured with conflict protection.
[0057] After the management platform 10 determines the target configuration item of the device 20 and the configuration parameters and protection parameters of the target configuration item in response to the user's configuration operation, it can generate a configuration command based on the target configuration item and the configuration parameters and protection parameters of the target configuration item and send it to the corresponding device 20.
[0058] For the case where configuration is performed locally on device 20, the process of generating configuration instructions, including configuration parameters and protection parameters, may include, for example: Figure 6 The steps shown are as follows: Step 301: Generate a configuration conflict prevention request based on the target configuration item in the user's local configuration instruction, and send the configuration conflict prevention request to the management platform 10.
[0059] In this embodiment, the user opens the configuration file of device 20 locally and configures the parameters of the configuration items in the configuration file. In response to the user's operation, device 20 determines the target configuration item configured by the user and the corresponding configuration parameters, and generates a local configuration command. Then, considering that the management platform 10 maintains the configuration conflict protection requirements for each configuration item of each device 20 and stores the protection information of device 20 (i.e., the protection parameters for each configuration item of each device 20), device 20 generates a configuration conflict protection request based on the target configuration item and sends the configuration conflict protection request to the management platform 10. The protection information can be pre-configured on the management platform 10 by the administrator or user.
[0060] Step 302: Receive the configuration instructions returned by the management platform 10.
[0061] The configuration command is generated by the management platform 10 in response to the configuration conflict protection request, querying the protection parameters of each target configuration item, and based on the target configuration item and the protection parameters of each target configuration item.
[0062] In this embodiment, after receiving a configuration conflict prevention request from device 20, management platform 10 parses the request to obtain the target configuration items and configuration parameters of each target configuration item. Then, based on the target configuration items, it queries the protection information to obtain the corresponding protection parameters. Based on the target configuration items, the configuration parameters of each target configuration item, and the protection parameters, it generates a configuration instruction for device 20 and sends this instruction to device 20, enabling device 20 to receive the configuration instruction returned by management platform 10.
[0063] In one possible implementation, the management platform 10 responds to the configuration conflict protection request sent by the device 20, retrieves the protection parameters of each target configuration item included in the configuration conflict protection request from the protection information, and then returns the protection parameters to the device 20. The device 20 generates configuration instructions based on the target configuration items, the configuration parameters of the target configuration items, and the protection parameters.
[0064] In one possible implementation, the management platform 10 can distribute the protection information corresponding to each device 20 to the corresponding device 20. Thus, in response to user operation, after determining the target configuration item configured by the user, the device 20 can directly query the protection parameters of the target configuration item in its local protection information, and generate configuration instructions based on the target configuration item, the configuration parameters of each target configuration item, and the protection parameters.
[0065] In this embodiment, protection parameters can be pre-configured for device configuration items. Therefore, when configuring the device, the configuration command can include protection parameters corresponding to the target configuration item, distinguishing between target configuration items that require and do not require configuration conflict protection. This avoids performing configuration conflict protection operations on configuration items that do not require protection during actual configuration, preventing waste of device storage and computing resources. In one embodiment, when a device 20 intercepts a configuration instruction containing protection parameters, it does not need to perform configuration conflict protection on all target configuration items in the configuration instruction. Instead, it can first determine whether the target configuration item needs configuration conflict protection based on the protection parameters of each target configuration item. If the protection parameters indicate that the target configuration item needs configuration conflict protection, then the device 20 queries the lock file corresponding to the target configuration item to perform configuration conflict protection on the target configuration item.
[0066] In this embodiment of the application, device 20 parses the configuration instructions to obtain the protection parameters of each target configuration item. If the protection parameter indicates that the target configuration item needs to be protected against configuration conflicts, for example, if the protection parameter is 11, the current configuration status of the target configuration item is determined by querying the lock file corresponding to the target configuration item. If the target configuration item is not currently in a configuration state, the target configuration item is configured based on its configuration parameters to achieve configuration conflict protection for the target configuration item.
[0067] In one possible implementation, the target configuration item can be divided into a first configuration item that requires configuration conflict protection and a second configuration item that does not require configuration conflict protection. In this case, the response to the configuration command may include the following steps: if querying the lock file determines that there is a first configuration item in a configured state, then the configuration command is ignored; if querying the lock file determines that all first configuration items are in an unconfigured state, then the first configuration item is modified to a configured state, and the first and second configuration items are configured in response to the configuration command.
[0068] In this embodiment, if, after intercepting a configuration command but before responding, device 20 determines, by querying the lock file of each first configuration item, that at least one first configuration item is currently in a configuration state, meaning it cannot respond to the configuration command to configure at least one of the first configuration items, then the configuration command can be ignored, and configuration of other first and second configuration items that are not currently in a configuration state is also prohibited, to ensure the consistency of device configuration. In this embodiment, device 20 can display a configuration failure message locally or on the management platform 10, which may include the identifier of the first configuration item with a configuration conflict.
[0069] If it is determined that all first configuration items are in an unconfigured state, that is, if it is determined that there are no configuration conflicts among the target configuration items in the configuration instruction, then the first configuration item is modified to a configured state through the lock file to reflect that the first configuration item is currently in a configured state, and the first and second configuration items are configured in response to the configuration instruction.
[0070] In one possible implementation, for the first configuration item with a configuration conflict, the target configuration item belonging to the same configuration file as the first configuration item can be identified first. Then, the first configuration item with a configuration conflict, as well as the target configuration item belonging to the same configuration file, are ignored, and the remaining target configuration items are configured.
[0071] The device configuration method based on the management platform 10 in the above embodiments can be summarized as follows: Figure 7 The steps shown are as follows: Step 401: The management platform 10 generates a configuration instruction in response to the user's configuration operation and sends it to the device 20; wherein, the configuration instruction may include the address of the configuration file where each target configuration item is located.
[0072] Step 402: Device 20 receives and intercepts the configuration command; Step 403: Device 20 determines whether the address of the configuration file indicated in the configuration instruction exists locally; Step 404: If the address of the configuration file indicated in the configuration instruction does not exist, it means that there is an error in the configuration instruction, and a configuration error message can be returned to the management platform 10. Step 405: If the address of the configuration file indicated in the configuration instruction exists, then the first configuration item in the target configuration item that needs to be protected against conflict can be determined; and for the first configuration item, whether there is a configuration conflict can be determined by whether there is a lock file. Step 406: If a configuration conflict exists, return a configuration conflict prompt to the management platform 10; Step 407: If there are no configuration conflicts, generate the lock file corresponding to the first configuration item; Step 408: Together with the second configuration item that does not require conflict protection (i.e., all target configuration items), match the corresponding configuration item locally on device 20 by the name or identifier of the target configuration item; Step 409: Replace the parameters in the matching configuration items based on the configuration parameters in the configuration instructions (i.e., modify the specific configuration items and save). Step 410: After configuration is complete, delete the lock file corresponding to the first configuration item and return a configuration completion prompt to the management platform 10.
[0073] The method provided in this application embodiment can ignore configuration instructions when there are configuration conflicting configuration items in the target configuration items, and perform configuration operations when there are no configuration conflicting configuration items in the target configuration items, which effectively improves the consistency of device configuration.
[0074] The embodiments described above illustrate a scheme to intercept configuration instructions locally generated by device 20 by modifying the operating system logic of device 20. In another embodiment of this application, the interception of configuration instructions can be achieved by configuring hook functions in the operating system. For example, the "interception of configuration instructions by device 20" mentioned above may include, for instance... Figure 8 The steps shown are as follows: Step 501: Create a target hook function in the operating system of device 20, and configure the trigger condition of the target hook function to detect a configuration command.
[0075] After device 20 has determined the configuration status of the target configuration item by maintaining the lock file locally, it is also necessary to change the execution logic of device 20's operating system to be able to intercept configuration commands. Only by combining the local lock file and configuration command interception can device 20 achieve configuration conflict protection for the target configuration item locally.
[0076] In this embodiment of the application, considering that hook functions can intercept specific processes or events, a target hook function can be created in the operating system of device 20, and the triggering condition of the target hook function can be configured to detect a configuration instruction, so that the target hook function can intercept the configuration instruction when it detects a locally generated configuration instruction.
[0077] Step 502: Call the target hook function to intercept configuration commands.
[0078] In this embodiment of the application, when the operating system of device 20 is running, it can call the target hook function to detect configuration instructions and intercept the configuration instructions when locally generated configuration instructions are detected.
[0079] The method provided in this application embodiment can intercept configuration commands based on the operating system (target hook function), which can effectively improve the interception efficiency and reliability of configuration commands, thereby improving the reliability of device configuration conflict protection.
[0080] The device configuration method based on the local side of device 20 provided in the above embodiments can be summarized as follows: Figure 9 The steps shown are as follows: Step 601: After the user opens the configuration file locally on device 20 and performs configuration operations, configuration instructions are generated; Step 602: The preset target hook function in the operating system detects and intercepts the configuration command, and sends a configuration conflict protection request to the management platform 10 based on the target configuration item in the configuration command; Step 603: In response to the configuration conflict protection request, the management platform 10 determines the first configuration item in the target configuration items that needs to be conflict protected, and returns it to the device 20; Step 604: Device 20 queries the corresponding lock file at the storage address of the first configuration item to determine whether there is a configuration conflict in the first configuration item. Step 605: If a configuration conflict exists, a configuration conflict prompt can be displayed to the user (the identifier or name of the first configuration item with the configuration conflict can be displayed). Step 606: The user can remove the configuration of the first configuration item that has a configuration conflict and update the configuration command, so that the device 20 can perform configuration conflict protection and configuration operation for the updated configuration command. Step 607: If the above lock file query indicates that there is no configuration conflict for the first configuration item, then generate the lock file corresponding to the first configuration item; Step 608: Perform specific configuration operations (save operations) for the first configuration item and the second configuration item that does not require conflict protection. Step 609: After configuration is complete, delete the lock file corresponding to the first configuration item; Step 610: Return a configuration completion message to the user (indicating successful modification).
[0081] In one embodiment, a device management system is provided, comprising a management platform 10 and at least one device 20. The management platform 10 is configured to, in response to a user's configuration operation, determine the device 20 to be configured and the target configuration item to be configured; generate a configuration instruction based on the target configuration item and send the configuration instruction to the device 20 to be configured; the device 20 is configured to intercept the user's local configuration instruction or the configuration instruction sent by the management platform 10, determine the local storage address of the target configuration item on the device 20, query the lock file corresponding to the target configuration item at the storage address; if the query result indicates that the target configuration item is currently in an unconfigured state, modify the target configuration item to a configured state and configure the target configuration item in response to the configuration instruction; if the query result indicates that the target configuration item is currently in a configured state, ignore the configuration instruction; different configuration items correspond to different lock files.
[0082] The management platform 10 is also used to provide a parameter configuration interface; the parameter configuration interface includes multiple configuration items corresponding to the device 20 and conflict protection requirement configuration items corresponding to each configuration item; the conflict protection requirement configuration items are used to configure the protection parameters of the configuration items, and the protection parameters are used to characterize whether the configuration item needs to be configured for conflict protection; the platform receives the configuration parameters and protection parameters input to the target configuration item and generates the configuration instructions for the target configuration item.
[0083] In this embodiment, an administrator or user can log in to the management platform on a client and configure the device 20 through the parameter configuration interface provided by the management platform 10. In response to the administrator's parameter configuration operation, the management platform 10 determines at least one target configuration item to be configured and the configuration parameters of each target configuration item, and generates a configuration command based on the at least one target configuration item and the configuration parameters of each target configuration item, sending it to the device 20. Alternatively, the user can directly configure the parameters locally on the device 20. In response to the user's parameter configuration operation, the device 20 determines at least one target configuration item to be configured and the configuration parameters of each target configuration item, and generates a local configuration command for the user, i.e., a configuration command.
[0084] Device 20 does not directly respond to configuration commands issued by management platform 10 or locally generated configuration commands, to avoid configuration conflicts caused by simultaneous configuration of the same configuration item by management platform 10 or local device. Instead, it first intercepts the configuration command, checks for configuration conflicts among the target configuration items in the command, and determines whether there is a situation where each target configuration item in the command is configured on multiple devices. Only when it is determined that there is no situation where any target configuration item in the command is configured on multiple devices will device 20 respond to the configuration command and configure the target configuration item locally.
[0085] Device 20 determines whether there is a configuration conflict for the target configuration item by checking the lock file. Each device 20 in the device management system maintains its own lock file corresponding to its configuration items locally, specifically in the local storage address of the configuration item. Therefore, after intercepting a configuration command, device 20, based on the mapping relationship between the configuration file and the storage address, first determines the local storage address of the configuration file containing the target configuration item, i.e., determines the local storage address of the target configuration item. Then, it queries the lock file corresponding to the target configuration item in the storage address, and determines the current configuration status of the target configuration item based on the query result of the lock file corresponding to the target configuration item.
[0086] If the query result for the lock file of the target configuration item indicates that the target configuration item is currently in an unconfigured state, then a configuration conflict prevention operation for the target lock file needs to be performed first, and then the target configuration item needs to be configured in response to the configuration command. That is, a lock file for the target configuration item needs to be set so that the set lock file can indicate that the target configuration item is currently in a configured state, preventing configuration conflicts caused by other ends (management platform 10 or other devices 20) configuring the target configuration item during its current configuration process. Then, in response to the configuration command, the parameters of the target configuration item stored locally on device 20 are replaced with the configuration parameters corresponding to the target configuration item in the configuration command, completing the configuration of the target configuration item.
[0087] In one embodiment, when configuring device 20 through management platform 10, management platform 10 can provide a parameter configuration interface. This parameter configuration interface can include multiple configuration items corresponding to device 20 and conflict prevention requirement configuration items corresponding to each configuration item. Users can configure the parameters of configuration items by modifying their content. The configuration item whose content is modified is the target configuration item, and the modified content is the configuration parameter of the target configuration item.
[0088] The parameter configuration interface also includes conflict protection requirement configuration items for each configuration item. Users can configure the protection parameters of the target configuration item by checking boxes. For example, checking a box indicates that the target configuration item needs conflict protection, and the protection parameter can be 11; not checking a box indicates that the target configuration item does not need conflict protection, and the protection parameter can be 00. That is, the protection parameter is used to indicate whether the target configuration item needs to be configured with conflict protection. After the management platform 10 determines the target configuration item of the device 20 and the configuration parameters and protection parameters of the target configuration item in response to the user's configuration operation, it can generate a configuration command based on the target configuration item and its configuration parameters and protection parameters and send it to the corresponding device 20.
[0089] In the device management system provided in this application embodiment, when the management platform or device locally configures a target configuration item in the device, the device intercepts the configuration command, first determines the storage address of the target configuration item on the device, and then queries the lock file corresponding to the target configuration item at the storage address. If the query result indicates that the target configuration item is currently in an unconfigured state, the target configuration item is modified to a configured state, and the configuration command is executed to configure the target configuration item; if the query result indicates that the target configuration item is currently in a configured state, the configuration command is ignored. That is, in this application embodiment, the device determines the current configuration state of each target configuration item through the lock file corresponding to the configuration item maintained locally, and changes the current configuration state of the target configuration item by changing the lock file, thereby avoiding configuration conflicts of target configuration items in multi-terminal configuration scenarios. Moreover, each device in the device management system maintains the lock file locally, combined with the preset interception program for configuration commands, the device can achieve conflict protection of each configuration item locally, without the need for complex system structure and complex configuration operations, effectively improving the efficiency and reliability of device parameter configuration while ensuring the flexibility of device parameter configuration.
[0090] It should be noted that although the operations of the method of the present invention are described in a specific order in the accompanying drawings, this does not require or imply that these operations must be performed in that specific order, or that all of the operations shown must be performed to achieve the desired result. On the contrary, the steps depicted in the flowchart may be performed in a different order. Additionally or alternatively, certain steps may be omitted, multiple steps may be combined into one step, and / or one step may be broken down into multiple steps.
[0091] On the other hand, this application also provides a computer-readable storage medium, which may be included in the computer device described in the above embodiments, or may exist independently and not assembled into the computer device. The aforementioned computer-readable storage medium stores one or more programs that, when used by one or more processors, execute the methods described in this application. For example, it may execute... Figure 2 The steps of the method shown.
[0092] This application provides a computer program product including instructions that, when executed, cause the method described in this application to be performed. For example, it can execute... Figure 2 The steps of the method shown.
[0093] Those skilled in the art will understand that all or part of the processes in the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium. When executed, the computer program can include the processes of the embodiments described above. Any references to memory, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM). The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this application may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, etc., and are not limited to these.
[0094] The above description is merely a preferred embodiment of this application and an explanation of the technical principles employed. Those skilled in the art should understand that the scope of the invention involved in this application is not limited to technical solutions formed by specific combinations of the above-described technical features, but should also cover other technical solutions formed by arbitrary combinations of the above-described technical features or their equivalents without departing from the inventive concept. For example, technical solutions formed by substituting the above features with (but not limited to) technical features with similar functions disclosed in this application.
Claims
1. A device configuration method, characterized by, Applied to an equipment management system, the system including a management platform and at least one device, the method includes: The device intercepts configuration instructions, which are used to configure target configuration items to be configured; the configuration instructions are issued by the management platform, or the configuration instructions are user-local configuration instructions. Determine the local storage address of the target configuration item on the device, and query the lock file corresponding to the target configuration item at the storage address; different configuration items correspond to different lock files; If the query result indicates that the target configuration item is currently in an unconfigured state, then the target configuration item is modified to a configured state, and the target configuration item is configured in response to the configuration instruction; if the query result indicates that the target configuration item is currently in a configured state, then the configuration instruction is ignored.
2. The method according to claim 1, characterized in that, The method further includes: The device generates and maintains a lock file for the target configuration item during the previous configuration process of the target configuration item, and deletes the lock file for the target configuration item when the target configuration item completes its configuration.
3. The method according to claim 2, characterized in that, The method further includes: If no lock file corresponding to the target configuration item is found, the target configuration item is determined to be in an unconfigured state; if a lock file corresponding to the target configuration item is found, the target configuration item is determined to be in a configured state.
4. The method according to claim 1, characterized in that, The method further includes: If the status parameter in the lock file corresponding to the target configuration item indicates that no management platform or other device is currently configuring the target configuration item, then the target configuration item is determined to be in an unconfigured state; if the status parameter in the lock file corresponding to the target configuration item indicates that a management platform or other device is currently configuring the target configuration item, then the target configuration item is determined to be in a configured state.
5. The method according to claim 1, characterized in that, Modifying the target configuration item to a configuration state includes: Generate and maintain a lock file for the target configuration item, or modify the status parameters in the lock file corresponding to the target configuration item to indicate that a management platform or other device is currently configuring the target configuration item.
6. The method according to claim 1, characterized in that, The configuration instruction includes the configuration parameters of the target configuration item and the protection parameters of the target configuration item; the protection parameters are used to characterize whether the target configuration item needs to be protected against configuration conflicts.
7. The method according to claim 6, characterized in that, The method further includes: A configuration conflict prevention request is generated based on the target configuration item in the user's local configuration instruction, and the configuration conflict prevention request is sent to the management platform. The system receives configuration instructions returned by the management platform. These instructions are generated by the management platform in response to the configuration conflict prevention request, by querying the protection parameters of each target configuration item, and based on the target configuration item and its protection parameters.
8. The method according to claim 6, characterized in that, If the protection parameter indicates that the target configuration item needs to be protected against configuration conflicts, then the lock file corresponding to the target configuration item is queried to perform configuration conflict protection for the target configuration item.
9. The method according to claim 6, characterized in that, The method further includes: The target configuration items include a first configuration item that requires configuration conflict protection and a second configuration item that does not require configuration conflict protection. If the lock file query determines that there is a first configuration item in a configured state, the configuration instruction is ignored; if the lock file query determines that the first configuration item is in an unconfigured state, the first configuration item is modified to a configured state, and the first configuration item and the second configuration item are configured in response to the configuration instruction.
10. The method according to claim 1, characterized in that, The device intercepts configuration commands, including: Create a target hook function in the operating system of the device, and configure the trigger condition of the target hook function to detect a configuration command; The target hook function is invoked to intercept the configuration instructions.
11. An equipment management system, characterized in that, The system includes a management platform and at least one device. The management platform is used to respond to user configuration operations, determine the device to be configured and the target configuration item to be configured; generate a configuration instruction based on the target configuration item, and send the configuration instruction to the device to be configured; The device is used to intercept user local configuration commands or configuration commands sent by the management platform, determine the storage address of the target configuration item on the device, and query the lock file corresponding to the target configuration item at the storage address. If the query result indicates that the target configuration item is currently in an unconfigured state, then the target configuration item is modified to a configured state, and the target configuration item is configured in response to the configuration instruction; If the query result indicates that the target configuration item is currently in a configuration state, the configuration instruction is ignored; different configuration items correspond to different lock files.
12. The equipment management system according to claim 11, characterized in that, The management platform is also used to provide a parameter configuration interface; the parameter configuration interface includes multiple configuration items corresponding to the device and conflict protection requirement configuration items corresponding to each configuration item; the conflict protection requirement configuration items are used to configure the protection parameters of the configuration items, and the protection parameters are used to characterize whether the configuration item needs to be configured with conflict protection; Receive configuration parameters and protection parameters input to the target configuration item, and generate configuration instructions for the target configuration item.