Method and system for solving updating of multi-terminal maintenance real-time dynamic iteration configuration set

Abstract

The invention discloses a method and a system for solving updating of a multi-terminal maintenance real-time dynamic iteration configuration set, and relates to the technical field of equipment configuration. The method comprises the following steps: creating an XML (Extensible Markup Language) file as an equipment configuration set template according to open configuration attributes of equipment; when the open configuration attribute of the equipment is updated, modifying the XML file so as to update the equipment configuration set template; rendering a configuration set interface according to the equipment configuration set template, and then generating an equipment configuration file according to configuration information input by a user on the configuration set interface; automatically issuing a device configuration file according to the associated device selected by the user; and performing configuration attribute updating on the device side based on the issued device configuration file. According to the method, the equipment configuration method based on the extensible markup language is introduced, on-demand rendering of the configuration set interface is achieved, meanwhile, the user-defined configuration set is used for supporting batch issuing of configuration, and the problem of pain points of multi-terminal maintenance is effectively solved.

Description

Technical Field

[0001] The present invention relates to the technical field of device configuration, and in particular to a method and system for solving the problem of multi-terminal maintenance real-time dynamic iterative configuration set update. Background Art

[0002] With the continuous iteration and upgrading of building intercom system functions and the increasing demand for customized equipment in smart community projects, loading different device configurations to achieve differentiated device function opening to meet various customized needs has become the current mainstream solution.

[0003] At present, the mainstream implementation method of building intercom system equipment configuration is: R&D personnel develop building intercom system equipment functions according to the different needs of the landing projects and generate customized upgrade packages for the corresponding projects according to the needs; construction personnel use the customized upgrade packages provided by R&D personnel to upgrade each type of equipment in the project one by one according to the project needs; and operation and maintenance personnel collect new needs in the later stage of the project, complete the demand list, and require R&D to complete the corresponding configuration settings based on the list and generate new customized upgrade packages. Although this solution has been widely used, there are still the following pain points:

[0004] (1) Problems in the R&D stage: With the continuous iteration of device functions, R&D personnel need to frequently optimize and refactor the code according to the latest requirements list to complete the customized configuration of different landing projects, thereby generating corresponding customized upgrade packages to adapt to the opening of new functions and new configurations of the device. This not only increases the workload of R&D, but also makes it difficult to configure different landing projects in parallel, affecting development efficiency and progress.

[0005] (2) Problems during the construction phase: Due to the different requirements for building intercom system equipment configuration in different projects, construction personnel need to use customized upgrade packages for each device in the project according to the specific needs of each project. This not only increases the complexity of construction personnel's operations, but also prolongs the project implementation cycle.

[0006] (3) Problems in the operation and maintenance phase: When faced with new requirements and new configurations proposed by the implementation project, the operation and maintenance personnel often need to wait for the R&D personnel to complete the requirement configuration according to the requirement list and generate a customized upgrade package before they can complete the preparation work for the configuration update of the implementation project. This process leads to a long requirement update cycle, which affects the timeliness and efficiency of operation and maintenance. In view of this, it is necessary to propose a more convenient and effective way to solve the above problems. Summary of the invention

[0007] The technical problem to be solved by the present invention is to provide a method and system for solving the real-time dynamic iterative configuration set update of multi-terminal maintenance. By introducing a device configuration method based on extensible markup language, on-demand rendering of the configuration set interface is realized, and custom configuration sets are used to support batch distribution of configurations, effectively solving the pain points of multi-terminal maintenance.

[0008] In a first aspect, the present invention provides a method for solving multi-terminal maintenance real-time dynamic iterative configuration set update, comprising:

[0009] Create an XML file as a device configuration set template based on the device's open configuration attributes; when the device's open configuration attributes are updated, modify the XML file to update the device configuration set template;

[0010] Render the configuration set interface according to the device configuration set template, and then generate the device configuration file according to the configuration information entered by the user on the configuration set interface;

[0011] Automatically issue device configuration files based on the associated devices selected by the user;

[0012] The configuration attributes are updated on the device side based on the issued device configuration file.

[0013] Furthermore, the configuration properties open on the device side are based on the JSON structure. The property name in JSON is the key value in the XML file. The tag name in XML is the same as the key, and the key and tag name are guaranteed to be unique under the same object. The configuration properties include basic properties and associated properties.

[0014] Furthermore, the configuration set interface is rendered according to the device configuration set template, including: reading the XML file, automatically generating corresponding form components and a tree navigation bar according to the tree hierarchy according to the basic attributes and associated attributes, and generating verification rules and prompt information according to the description in the associated attributes.

[0015] Furthermore, a default template is generated for configuring default values ​​of attributes in the device configuration set template; a customized template is generated for configuring custom values ​​of attributes in the device configuration set template; when rendering the configuration set interface, the key values ​​in the default template or customized template are assigned to each item in the form to realize two-way data binding.

[0016] Furthermore, after completing the device configuration in the configuration set interface, the device configuration file, template information and associated devices are stored on the server; when the configuration information entered by the user on the configuration set interface includes attachments, the device configuration file, attachments, template information and associated devices are stored on the server; when the device side updates the configuration properties based on the issued device configuration file, the attachments are obtained from the server.

[0017] In a second aspect, the present invention provides a system for solving multi-terminal maintenance real-time dynamic iterative configuration set update, comprising:

[0018] The template creation module is used to create an XML file as a device configuration set template according to the configuration attributes opened by the device; when the configuration attributes opened by the device are updated, the XML file is modified to update the device configuration set template;

[0019] The configuration file generation module is used to render the configuration set interface according to the device configuration set template, and then generate the device configuration file according to the configuration information entered by the user on the configuration set interface;

[0020] Configuration distribution module, used to automatically distribute device configuration files according to the associated devices selected by the user;

[0021] The configuration update module is used to update the configuration attributes on the device side based on the issued device configuration file.

[0022] Furthermore, in the template creation module, the configuration properties open on the device side are based on the JSON structure, the attribute name in the JSON is the key value in the XML file, the tag name in the XML is the same as the Key, and the Key and tag name are guaranteed to be unique under the same Object, and the configuration properties include basic properties and associated properties.

[0023] Furthermore, in the configuration file generation module, the configuration set interface is rendered according to the device configuration set template, including: reading the XML file, automatically generating corresponding form components and tree navigation bars according to the tree hierarchy according to the basic attributes and associated attributes, and generating verification rules and prompt information according to the description in the associated attributes.

[0024] Furthermore, in the template creation module, a default template is generated for configuring the default values ​​of the attributes in the device configuration set template; a customized template is generated for configuring the custom values ​​of the attributes in the device configuration set template; in the configuration file generation module, when rendering the configuration set interface, the key values ​​in the default template or customized template are assigned to each item in the form to realize two-way data binding.

[0025] Furthermore, in the configuration file generation module, after completing the device configuration in the configuration set interface, the device configuration file, template information and associated devices are stored in the server; when the configuration information entered by the user on the configuration set interface includes attachments, the device configuration file, attachments, template information and associated devices are stored in the server; in the configuration update module, when the device side updates the configuration properties based on the issued device configuration file, the attachments are obtained from the server.

[0026] The technical solution provided in the embodiments of the present invention has at least the following technical effects:

[0027] R&D personnel do not need to modify the platform code due to new device functions or new configurations. They only need to maintain the device configuration set template XML file based on the device functions, which greatly improves development efficiency, reduces the workload of R&D, and improves the flexibility and scalability of the system. Construction personnel can create device configuration sets based on different project requirements, and the configuration set interface corresponding to the device configuration template will be automatically rendered. Construction personnel configure the equipment through the configuration set interface, and after selecting the associated equipment, batch distribution based on different scenarios can be achieved, which significantly improves construction efficiency and simplifies the configuration process.

[0028] The above description is only an overview of the technical solution of the present invention. In order to more clearly understand the technical means of the present invention, it can be implemented according to the contents of the specification. In order to make the above and other purposes, features and advantages of the present invention more obvious and easy to understand, the specific implementation methods of the present invention are listed below. BRIEF DESCRIPTION OF THE DRAWINGS

[0029] The present invention will be further described below in conjunction with embodiments with reference to the accompanying drawings.

[0030] Figure 1 A schematic diagram of the configuration process of the multi-terminal collaborative maintenance device of the present invention;

[0031] Figure 2 is an overall flow chart of the method in Embodiment 1 of the present invention;

[0032] Figure 3 This is a flow chart of the dynamic rendering configuration set interface in the first embodiment of the present invention;

[0033] Figure 4 This is a flow chart of data clipping in Embodiment 1 of the present invention;

[0034] Figure 5 It is a schematic diagram of the structure of the system in the second embodiment of the present invention. DETAILED DESCRIPTION

[0035] The embodiments of the present application provide a method and system for solving the real-time dynamic iterative configuration set update problem of multi-terminal maintenance. By introducing a device configuration method based on extensible markup language, on-demand rendering of the configuration set interface is achieved, and custom configuration sets are used to support batch distribution of configurations, thereby effectively solving the pain points of multi-terminal maintenance.

[0036] The technical solution in the embodiment of the present invention has the following general idea:

[0037] An innovative solution is proposed. By introducing a device configuration method based on Extensible Markup Language (XML), a series of attribute definitions are used to achieve on-demand rendering of the configuration set interface. At the same time, a custom configuration set is used to support batch distribution of configurations, effectively solving the pain point of multi-terminal maintenance.

[0038] During the specific implementation process, R&D personnel create an XML file corresponding to the device configuration set based on the configuration properties of the current device as a device configuration set template. The platform uses this template to render the configuration set interface on demand to meet the needs of different devices. Construction personnel log in to the system through the device configuration set module and create a device configuration set according to project requirements. After completing the device configuration in the configuration interface, you can select the associated device and save the configuration file, attachment information, and template information to store it on the server, and implement batch distribution of configurations based on the associated devices.

[0039] When a device opens a new configuration or adds a new function, the R&D personnel only need to update the device configuration set template to synchronize the configuration interface, and the operation and maintenance personnel can complete the adjustment of the device configuration set based on the latest template. If the template has not been updated, the operation and maintenance personnel can also download and manually update the corresponding device configuration template, and then upload it to the system to complete the temporary update of the device configuration set.

[0040] This solution achieves a clear division of labor: the operation staff is only responsible for the management of the equipment configuration template, the construction staff focuses on the configuration settings, the platform is responsible for the interface rendering and verification based on the equipment configuration template, and the equipment side focuses on updating the equipment configuration template. In this way, the flexibility and maintenance efficiency of the system are improved, and the management process of multi-terminal equipment configuration is significantly optimized. The specific process is shown in the figure below: Figure 1 .

[0041] Embodiment 1

[0042] This embodiment provides a method for solving the problem of multi-terminal maintenance of real-time dynamic iteration configuration set update. Figure 2 As shown, including:

[0043] S1. Create an XML file as a device configuration set template according to the configuration attributes opened by the device; when the configuration attributes opened by the device are updated, modify the XML file to update the device configuration set template;

[0044] In one possible implementation, the protocol for creating an XML file is as follows:

[0045] (a) The configuration properties open on the device side are based on the JSON structure, and the corresponding XML files that can support on-demand rendering of the configuration set are constructed according to the protocol rules;

[0046] (b) The attribute name in JSON is the key value in the XML file. The tag name in XML is the same as the key, and the key and tag name are guaranteed to be unique in the same object.

[0047] (c) The XML root node base should contain the protocolVersion structure: name_manufacturer name_13-digit timestamp.

[0048] Configuration properties include basic properties and associated properties, which can be shown in the following table:

[0049] (a) Basic attribute description

[0050] (b) Description of associated attributes

[0051]

[0052]

[0053] Subsequent other configuration file data verification rules and new component designs can be implemented by expanding the associated attributes. R&D personnel build the device configuration template according to the device configuration requirements and generate the corresponding XML file according to the above protocol content to complete the device configuration initialization work through the above steps.

[0054] S2. Rendering a configuration set interface according to the device configuration set template, and then generating a device configuration file according to the configuration information input by the user on the configuration set interface.

[0055] In a possible implementation, the configuration set interface is rendered according to the device configuration set template, which is specifically implemented as follows:

[0056] (1) Read the XML file, automatically generate the corresponding form components and tree navigation bar according to the tree hierarchy according to the basic attributes (valueType) and the associated attributes (componentType), and generate the validation rules and prompt information according to the description in the associated attributes, such as Figure 3 The dynamic rendering configuration set interface is shown below.

[0057] (2) When creating a configuration set, use the default template or customized template XML to generate the corresponding configuration interface (generate a default template for configuring default values ​​for attributes in the device configuration set template; generate a customized template for configuring custom values ​​for attributes in the device configuration set template), and generate default values ​​based on the default template or customized template, and assign them to each item in the form based on the Key value to achieve two-way data binding.

[0058] Different projects can use different configuration templates. The isVisible attribute value in the device configuration set controls whether the configuration is displayed, thus achieving configuration template customization.

[0059] For example: In the default template XML file,

[0060] alarmdefaultValue="1"

[0061] time isVisible="false" defaultValue="1"

[0062] Indicates that the default template only allows configuration of alarm-related configurations, and the default value of alarm-related configurations is 1.

[0063] If project A needs to configure time and ringtone, and the default value of alarm is 2, the modified template XML file of project A is as follows:

[0064] alarmdefaultValue="2"

[0065] time isVisible = "true"

[0066] ring

[0067] That is, a customized template for project A.

[0068] R&D personnel update the default template, and operation and maintenance personnel provide customized templates or default templates to construction according to specific project requirements. Construction uses the templates to configure the project.

[0069] (3) When editing a configuration set, read the configuration file corresponding to the configuration set, and trim the configuration file data based on the defaultValue and valueType in the default template or customized template XML (the trimming rules are as follows: if the attribute name and attribute type in the configuration file are consistent with the attribute Key value and valueType in the template file XML, and the sub-attribute, sub-attribute name, and type are consistent, then retain the attribute; otherwise, the attribute uses the default value defaultValue. Figure 4 Data clipping rules are shown in the figure to ensure that the generated configuration file is suitable for the configuration template. The clipped data is assigned to each item in the form based on the Key value to achieve two-way data binding.

[0070] When using a customized template, the construction personnel upload the customized template or import the device configuration compressed package; when using the default template, the construction personnel select the device type and manufacturer to automatically use the corresponding default template. After rendering the configuration set interface, the device configuration file is generated according to the configuration information entered by the user on the configuration set interface. The configuration set is usually created and edited by the construction party. The specific steps are as follows:

[0071] (1) The construction party inputs configuration information and configures equipment functions according to project requirements;

[0072] (2) After completing the configuration, click Save Configuration and select Associate Device.

[0073] When using a custom template, save the configuration, configuration template, and attachment information to the server. When you open the configuration interface again, use the custom template to render the interface. When using the default template, save the configuration and attachment information to the server. When you open the configuration interface again, use the default template to render the interface.

[0074] S3, automatically issuing a device configuration file according to the associated device selected by the user; the steps may include:

[0075] (1) The server obtains the corresponding device according to the associated device selected in the configuration set;

[0076] (2) Obtain the device IP in the local area network, push the configuration file to the corresponding device, and complete the batch update of device configuration;

[0077] (3) Obtain the IP address of the device registered to the cloud, push the configuration file to the corresponding device, and complete the batch update of device configuration.

[0078] S4. Update the configuration attributes on the device side based on the issued device configuration file.

[0079] In one possible implementation, after completing the device configuration in the configuration set interface, the device configuration file, template information, and associated devices are stored on the server; when the configuration information entered by the user on the configuration set interface includes attachments, the device configuration file, attachments, template information, and associated devices are stored on the server; when the device side updates the configuration properties based on the issued device configuration file, the attachments are obtained from the server.

[0080] Preferably, the operation and maintenance end can also maintain and update the configuration set and perform subsequent iterative maintenance. The specific steps are as follows:

[0081] (1) The operation and maintenance side lists the configuration required for the functions according to the actual needs of the project

[0082] (2) After developing the corresponding functions according to the list, after adding or opening configuration attributes, update the device template file and generate a new default template

[0083] (3) Update the corresponding template file after the next version is released to update the device configuration interface

[0084] When the device template file is not updated or a certain configuration is missing from the template, the operation and maintenance personnel can download the default configuration template and write the corresponding configuration template file according to the template protocol, and then update the device interface by uploading the configuration template, thereby realizing the newly added or newly opened attribute configuration of the device.

[0085] Based on the same inventive concept, the present application also provides a system corresponding to the method in Example 1, see Example 2 for details.

[0086] Embodiment 2

[0087] In this embodiment, a system is provided to solve the problem of multi-terminal maintenance of real-time dynamic iteration configuration set update. Figure 5 As shown, including:

[0088] The template creation module is used to create an XML file as a device configuration set template according to the configuration attributes opened by the device; when the configuration attributes opened by the device are updated, the XML file is modified to update the device configuration set template;

[0089] The configuration file generation module is used to render the configuration set interface according to the device configuration set template, and then generate the device configuration file according to the configuration information entered by the user on the configuration set interface;

[0090] Configuration distribution module, used to automatically distribute device configuration files according to the associated devices selected by the user;

[0091] The configuration update module is used to update the configuration attributes on the device side based on the issued device configuration file.

[0092] In one possible implementation, in the template creation module, the configuration attributes opened on the device side are based on the JSON structure, the attribute name in the JSON is the key value in the XML file, the tag name in the XML is the same as the Key, and the Key and tag name are guaranteed to be unique under the same Object, and the configuration attributes include basic attributes and associated attributes.

[0093] In one possible implementation, in the configuration file generation module, the configuration set interface is rendered according to the device configuration set template, including: reading the XML file, automatically generating corresponding form components and a tree navigation bar according to the tree hierarchy according to the basic attributes and associated attributes, and generating verification rules and prompt information according to the description in the associated attributes.

[0094] In one possible implementation, in the template creation module, a default template is generated for configuring the default values ​​of the attributes in the device configuration set template; a customized template is generated for configuring the custom values ​​of the attributes in the device configuration set template; in the configuration file generation module, when rendering the configuration set interface, the key values ​​in the default template or the customized template are assigned to each item in the form to realize two-way data binding.

[0095] In a possible implementation, in the configuration file generation module, after completing the device configuration in the configuration set interface, the device configuration file, template information and associated devices are stored in the server; when the configuration information entered by the user on the configuration set interface includes attachments, the device configuration file, attachments, template information and associated devices are stored in the server; in the configuration update module, when the device side updates the configuration properties based on the issued device configuration file, the attachments are obtained from the server.

[0096] Since the system introduced in the second embodiment of the present invention is a system used to implement the method of the first embodiment of the present invention, those skilled in the art can understand the specific structure and deformation of the system based on the method introduced in the first embodiment of the present invention, so it is not described here in detail. All systems used in the method of the first embodiment of the present invention belong to the scope of protection of the present invention.

[0097] The technical solution of the present invention eliminates the need for R&D personnel to modify platform codes due to new equipment functions or newly added configurations. Instead, they only need to maintain the equipment configuration set template XML file based on the equipment functions, thereby greatly improving development efficiency, reducing the workload of R&D, and improving the flexibility and scalability of the system. Construction personnel can create equipment configuration sets based on different project requirements, and automatically render the configuration set interface corresponding to the equipment configuration template. Construction personnel configure the equipment through the configuration set interface, and after selecting the associated equipment, batch distribution based on different scenarios can be achieved, which significantly improves construction efficiency and simplifies the configuration process. Operation and maintenance personnel do not need to have an in-depth understanding of development tools, but only need to be familiar with the XML format and protocol to render the equipment configuration set interface according to different requirements, and flexibly respond to equipment configuration expansion and upgrades in different scenarios. Through this solution, operation and maintenance work becomes more efficient and convenient, effectively reduces maintenance costs, and improves the operability and flexibility of equipment management.

[0098] Those skilled in the art will appreciate that embodiments of the present invention may be provided as methods, systems, or computer program products. Therefore, the present invention may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the present invention may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0099] The present invention is described with reference to flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to embodiments of the present invention. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as the combination of processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0100] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0101] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0102] Although the specific implementation modes of the present invention are described above, those skilled in the art should understand that the specific implementation modes described are only illustrative and are not intended to limit the scope of the present invention. Equivalent modifications and changes made by those skilled in the art in accordance with the spirit of the present invention should be included in the scope of protection of the claims of the present invention.

Claims

1. A method for solving multi-terminal maintenance real-time dynamic iterative configuration set update, characterized in that: include: Create an XML file as a device configuration set template based on the device's open configuration attributes; when the device's open configuration attributes are updated, modify the XML file to update the device configuration set template; Render the configuration set interface according to the device configuration set template, and then generate the device configuration file according to the configuration information entered by the user on the configuration set interface; Automatically issue device configuration files based on the associated devices selected by the user; The configuration attributes are updated on the device side based on the issued device configuration file.

2. The method according to claim 1, characterized in that: The configuration properties open on the device side are based on the JSON structure. The property name in JSON is the key value in the XML file. The tag name in XML is the same as the key, and the key and tag name are guaranteed to be unique under the same object. Configuration properties include basic properties and associated properties.

3. The method according to claim 2, characterized in that: Rendering the configuration set interface according to the device configuration set template includes: reading the XML file, automatically generating corresponding form components and a tree navigation bar according to the tree hierarchy according to the basic attributes and associated attributes, and generating verification rules and prompt information according to the description in the associated attributes.

4. The method according to claim 1, characterized in that: Generate a default template for configuring the default values ​​of the attributes in the device configuration set template; generate a customized template for configuring the custom values ​​of the attributes in the device configuration set template; When rendering the configuration set interface, the key value in the default template or custom template is assigned to each item in the form to achieve two-way data binding.

5. The method according to claim 1, characterized in that: After completing the device configuration in the configuration set interface, the device configuration file, template information and associated devices are stored on the server; when the configuration information entered by the user on the configuration set interface includes attachments, the device configuration file, attachments, template information and associated devices are stored on the server; when the device side updates the configuration properties based on the issued device configuration file, the attachments are obtained from the server.

6. A system for solving multi-terminal maintenance real-time dynamic iterative configuration set update, characterized in that: include: The template creation module is used to create an XML file as a device configuration set template according to the configuration attributes opened by the device; when the configuration attributes opened by the device are updated, the XML file is modified to update the device configuration set template; The configuration file generation module is used to render the configuration set interface according to the device configuration set template, and then generate the device configuration file according to the configuration information entered by the user on the configuration set interface; Configuration distribution module, used to automatically distribute device configuration files according to the associated devices selected by the user; The configuration update module is used to update the configuration attributes on the device side based on the issued device configuration file.

7. The system according to claim 6, characterized in that: In the template creation module, the configuration attributes opened on the device side are based on the JSON structure. The attribute name in the JSON is the key value in the XML file. The tag name in the XML is the same as the Key, and the Key and tag name are guaranteed to be unique under the same Object. The configuration attributes include basic attributes and associated attributes.

8. The system according to claim 6, characterized in that: In the configuration file generation module, the configuration set interface is rendered according to the device configuration set template, including: reading the XML file, automatically generating corresponding form components and tree navigation bars according to the tree hierarchy according to the basic attributes and associated attributes, and generating verification rules and prompt information according to the description in the associated attributes.

9. The system according to claim 6, characterized in that: In the template creation module, a default template is generated for configuring the default values ​​of the attributes in the device configuration set template; a customized template is generated for configuring the custom values ​​of the attributes in the device configuration set template; In the configuration file generation module, when rendering the configuration set interface, the key value in the default template or customized template is assigned to each item in the form to achieve two-way data binding.

10. The system according to claim 6, characterized in that: In the configuration file generation module, after completing the device configuration in the configuration set interface, the device configuration file, template information and associated devices are stored in the server; when the configuration information input by the user in the configuration set interface includes attachments, the device configuration file, attachments, template information and associated devices are stored in the server; In the configuration update module, when the device updates the configuration attributes based on the issued device configuration file, it obtains the attachment from the server.

Images