A configuration file management system of a distributed power supply access unit

Abstract

The application discloses a configuration file management system of a distributed power supply access unit, which is connected with the distributed power supply access unit through a user terminal, and comprises a performance module, a data storage module and an application module, wherein the performance module is used for providing an interface for interaction with a user, the data storage module is used for storing configuration files and first serialization files, the configuration files comprise a plurality of mapping files, and the application module is connected to the data storage module, the performance module and the distributed power supply access unit respectively and used for loading the mapping files and the configuration files from the data storage module. The system provides a clear management process for the configuration files, effectively manages conversion rules and configuration files, realizes the input and issuance of the configuration files, and meets system safety and other links.

Description

Technical Field

[0001] This invention relates to the field of system configuration, and more specifically to a configuration file management system for a distributed power access unit. Background Technology

[0002] Distributed power access units are devices used by power information acquisition and management systems to communicate with low-voltage distributed photovoltaic inverters, energy storage devices, charging piles, etc., and have functions such as protocol conversion and execution of control commands. Distributed power sources are widely distributed and diverse, covering various forms such as solar photovoltaic, wind power, and small hydropower. Taking photovoltaic power sources as an example: inverters generally use Modbus communication, but there are significant differences in protocol definitions between different series of products from different manufacturers. The register addresses, function codes, data types, and unit definitions of the same data are inconsistent; in addition, after inverter upgrades, the data definitions often undergo radical changes.

[0003] For distributed power access units that implement protocol conversion through configuration files, multiple mapping files for mutual conversion between the target device's communication protocol and standard protocols are recorded in the configuration file. Switching between the mapping file sets of the distributed power access unit is achieved by loading the configuration file, solving the problems of increased development and maintenance costs, and reduced equipment safety and operational stability caused by modifying the program every time the original configuration file changes. While loading the mapping file set through configuration files solves some problems, new challenges will arise with industry development. Due to the increasing number of distributed power supply manufacturers, the continuous launch of new products, and frequent program upgrades to existing products, the number of mapping relationships—i.e., conversion rules—between distributed power supplies (such as inverters) and DL / T698 or DL / T645 protocol data has increased dramatically. Such a large number of conversion rules, if not effectively managed, will lead to a series of problems: 1. Large number of conversion rules: Conversion rules are the mapping relationships between distributed power supplies (i.e., inverters, etc.) and DL / T698 or DL / T645 protocol data. With the increase in manufacturers, the launch of new products, and program upgrades to existing products, the number of conversion rules will increase significantly. Therefore, management of conversion rules is necessary; secondly, configuration files involve a wide range of issues: a configuration file is a collection of different conversion rules. The types of distributed power sources in a region are limited, and can be adapted using a single configuration file. However, the types, manufacturers, models, and versions of distributed power sources differ across regions. Therefore, configuration file management is required; thirdly, configuration file upgrades are crucial: as manufacturers and equipment upgrade, configuration files for the same region also need to be upgraded to adapt to the new conversion rules. Therefore, how to solve the unified management and distribution of configuration files is a pressing problem that needs to be addressed. Summary of the Invention

[0004] (I) Purpose of the Invention

[0005] The purpose of this invention is to provide a configuration file management system for distributed power access units. This system provides a clear management process for configuration files, effectively manages conversion rules and configuration files, realizes the input and distribution of configuration files, and meets system security requirements.

[0006] (II) Technical Solution

[0007] To address the above problems, this invention provides a configuration file management system for a distributed power access unit. The configuration file management system connects to the distributed power access unit via a user terminal. The system includes: a presentation module, a data storage module, and an application module, wherein:

[0008] The presentation module is used to provide an interface for interaction with the user, through which user commands are received and the results of configuration file distribution are displayed;

[0009] The data storage module is used to store a configuration file and a first serialized file. The configuration file includes several mapping files, and the first serialized file is generated from the corresponding configuration file.

[0010] The application module is connected to the data storage module, the presentation module, and the distributed power access unit, respectively. It is used to load the mapping file and configuration file from the data storage module, classify and manage the mapping file and configuration file, obtain the corresponding first serialized file according to the user instruction, send it to the distributed power access unit, and send the sending result to the presentation module for display.

[0011] Furthermore, the application module includes:

[0012] The security management unit is used to perform security authentication on the received user commands before sending them to the configuration file management unit;

[0013] Configuration file management unit: used to receive user instructions after security authentication, load configuration files from the data storage module, input, modify, delete, filter and sort the configuration files, and forward the user instructions after security authentication to the mapping file management unit and the configuration file distribution unit respectively;

[0014] The mapping file management unit is used to receive forwarded user instructions, load mapping files from the data storage module, and perform tasks such as entering, modifying, deleting, sending request instructions, and querying mapping files.

[0015] The configuration file distribution unit is used to receive forwarded user instructions, obtain the corresponding first serialized file from the data storage module according to the user instructions, distribute the first serialized file to the distributed power access unit, and send the distribution result to the display module for display after being authenticated by the security management unit.

[0016] Furthermore, the system also includes a transmission module, which includes an access API unit for communicating with external systems.

[0017] Furthermore, the input of the mapping file includes:

[0018] Obtain the storage structure information corresponding to the mapping file within the distributed power access unit; both the mapping file and the manufacturer's protocol document are obtained based on the interface or the API unit, and the mapping file and the manufacturer's protocol document correspond one-to-one.

[0019] The mapping file is used to generate a second serialized file based on the storage structure information. The second serialized file is the corresponding conversion file of the mapping file.

[0020] The manufacturer's agreement document, the mapping file corresponding to the manufacturer's agreement document, and the second serialization file are associated to obtain the association information;

[0021] A second metadata is added to the associated information to form the final mapping file record and stored in the mapping file record list. The second metadata is the metadata of the mapping file.

[0022] Furthermore, modifying the mapping file includes:

[0023] Find the first target mapping file in the mapping file record list. The first target mapping file is the target mapping file to be modified.

[0024] Modifying the data in the first target mapping file includes: changing the manufacturer's mapping file, uploading a new mapping file, modifying the data in the first target mapping file, and modifying the second metadata of the first target mapping file;

[0025] The modified mapping file is checked, and the changes are saved to the data storage module after the check is passed.

[0026] Furthermore, deleting the mapping file includes:

[0027] Search the mapping file record table for the second target mapping file, which is the target mapping file to be deleted;

[0028] After user confirmation, delete the second target mapping file and the second serialization file corresponding to the second target mapping file.

[0029] Furthermore, the configuration file distribution unit, used to receive forwarded user instructions, retrieve the corresponding first serialized file from the data storage module according to the user instructions, and distribute the first serialized file to the distributed power supply access unit, includes:

[0030] Establish a connection with the distributed power access unit to be distributed through the user terminal;

[0031] After the user selects the first serialization file, the first serialized file selected by the user is read and sent out through a preset protocol;

[0032] Determine whether to terminate the distribution process based on whether the distribution is normal or abnormal.

[0033] Furthermore, the process of entering the configuration file includes:

[0034] Populate the first metadata of the configuration file;

[0035] Bind the user-selected mapping file to the current configuration file;

[0036] Check whether the first metadata is valid, and adjust the first metadata accordingly based on the check result to generate the final configuration file metadata;

[0037] The final configuration file metadata and the selected mapping file are integrated into a new configuration file and stored in the configuration file table;

[0038] Based on the configuration file table, a first serialized file of the configuration file is generated.

[0039] Furthermore, the modification of the configuration file includes:

[0040] Locate the target configuration file to be modified in the configuration file table;

[0041] Modifying the data in the target configuration file to be modified includes: modifying the mapping file record list and the first metadata of the configuration file;

[0042] The modified information is checked, and once the check is passed, the changes are saved to the data storage module.

[0043] Furthermore, the presentation module includes a web interface and an app interface.

[0044] (III) Beneficial Effects

[0045] The above-mentioned technical solution of the present invention has the following beneficial technical effects: The present invention provides a configuration file management system for a distributed power access unit. The system provides a clear management process for configuration files by setting up a presentation module, an application module, and a data storage module. The application module is used to load the mapping file and configuration file from the data storage module, classify and manage the mapping file and configuration file, and obtain the corresponding first serialized file according to the user instruction, and send it to the distributed power access unit. At the same time, the sending result is sent to the presentation module for display. The system uses the mapping file as the smallest management data unit for configuration file management, which facilitates the combination of protocols included in the configuration file. Attached Figure Description

[0046] Figure 1 This is a schematic diagram of the configuration file management system of the distributed power access unit of the present invention;

[0047] Figure 2 This is a diagram showing the configuration file structure of the present invention;

[0048] Figure 3 This is a schematic diagram of the configuration file management system according to an embodiment of the present invention;

[0049] Figure 4 This is the mapping file management unit of the present invention for the process of entering mapping files from different manufacturers;

[0050] Figure 5 This is the process by which the mapping file management unit of this invention modifies mapping files from different manufacturers;

[0051] Figure 6 This is the mapping file management unit of this invention's process for deleting mapping files from different manufacturers;

[0052] Figure 7 This is the configuration file management unit's input process for configuration files in this embodiment of the invention;

[0053] Figure 8 This is the process by which the configuration file management unit modifies the configuration file in this embodiment of the invention;

[0054] Figure 9 This is the deletion process of the configuration file management unit in this embodiment of the invention;

[0055] Figure 10 This is the configuration file distribution process according to an embodiment of the present invention;

[0056] Figure 11 This is a schematic diagram of the data flow of the configuration file management system according to an embodiment of the present invention. Detailed Implementation

[0057] To make the objectives, technical solutions, and advantages of this invention clearer, the invention will be further described in detail below with reference to specific embodiments and the accompanying drawings. It should be understood that these descriptions are merely exemplary and not intended to limit the scope of the invention. Furthermore, descriptions of well-known structures and techniques are omitted in the following description to avoid unnecessarily obscuring the concept of the invention.

[0058] Before detailing the configuration file management system of this invention, Figure 2 This refers to the configuration file's related elements and basic structural components. Figure 2 Each component is explained below:

[0059] 1. Manufacturer's Agreement Description Document A1 (Manufacturer's Agreement Document): This is a detailed document provided by the inverter manufacturer regarding the equipment's protocol. It includes the applicable product series, definitions related to reading and setting operations in the Modbus communication protocol, data formats, etc. It is an important basis for reading and operating the equipment.

[0060] 2. Mapping File a2: The mapping file plays a crucial role in the system for conversion and association. It maps each operation required by the DL / T698 or DL / T645 protocol or other higher-level protocols on the inverter to a set of corresponding Modbus frame elements in the manufacturer's protocol description document, and provides the corresponding data parsing rules. Furthermore, the configuration mapping file also includes metadata such as the manufacturer's protocol description document version, the mapping file version, and the applicable equipment series, providing a basis for subsequent file management.

[0061] 3. Serialized file a3 (a3 is the second serialized file): Serialization processing converts the mapping file a2 and metadata a4 into a format that is easier to store and transmit, reducing the amount of data transmitted and improving transmission speed. Serialized file formats include, but are not limited to, JSON, XML, YAML, bin, etc. The serialized file includes the second serialized file a3 and the first serialized file a9.

[0062] 4. Metadata a4 (a4 is the second metadata): Provides additional descriptive information for the mapped file record a5, including but not limited to the applicable region, to provide a basis for subsequent file management. The metadata includes the second metadata a4 and the first metadata a7.

[0063] 5. Mapping file record a5: A set of corresponding manufacturer protocol description documents a1, mapping file a2, serialization file a3, and metadata a4 is called a mapping file record a5. The mapping file record is the smallest unit for the system to manage mapping files.

[0064] 6. Configuration file a8: The configuration file consists of a mapping file list a6 and metadata a7 (first metadata). The mapping file list a6 is composed of a set of mapping file records a5. The metadata a7 provides additional descriptive information to the configuration file a8, including but not limited to the applicable region, providing a basis for subsequent file management.

[0065] 7. Serialized file a9 (first serialized file): The serialized file a9 of the system-generated configuration file a8, in formats including but not limited to JSON, XML, YAML, and bin. Serialized file a9 is used for loading the distributed power source. In the following text, "transmitting the configuration file to the distributed power source" means transmitting the serialized file a9 of configuration file a8 to the distributed power source.

[0066] against Figure 2 The present invention provides a configuration file management system for a distributed power access unit, wherein the configuration file management system is connected to the distributed power access unit through a user terminal, and in conjunction with the configuration file composition method. Figure 1 As shown, the system includes: presentation module 1, application module 2, and data storage module 3. The functions of each module are combined... Figure 3 As shown, combined with Figure 11 The user operation section is explained below:

[0067] I. Presentation Module 1 (corresponding to) Figure 3 The presentation layer (b1) provides an interface for interaction with the user. Presentation layer b1 is the interface between the system and the user, through which user commands are received and the results of configuration file distribution are displayed. This presentation module 1 mainly includes a Web interface (b11) and an App interface (b12).

[0068] (1) Web Interface b11: Implemented via the Web, enabling cross-platform operation. Through the Web interface, users can easily interact with the system and perform various operations on configuration files. Users can manage manufacturer specification mapping files, configuration files, and other operations on the Web interface.

[0069] (2) APP interface b12: APP for accessing this system by mobile phones or other handheld terminals, computers and other devices.

[0070] II. Application Module 2, Application Layer b2: The application module is the core functional implementation layer of the system, encompassing multiple key functional units. It is connected to the data storage module, the presentation module, and the distributed power access unit, respectively. It is used to load the mapping files and configuration files from the data storage module, classify and manage the mapping files and configuration files, obtain the corresponding first serialized file according to the user instruction, and send it to the distributed power access unit. Simultaneously, it sends the sending result to the presentation module for display. This application module 2 includes a security management unit, a mapping file management unit, a configuration file management unit, and a configuration file sending unit. Each unit is described below:

[0071] 1. The security management unit (access security management b24) is used to perform security authentication on received user commands before sending them to the configuration file management unit. The security management unit employs multiple security mechanisms to authorize user operations. Access security management b24 is a crucial module for ensuring the secure operation of the system. It ensures that only authorized users can access and operate system resources through various security mechanisms, such as user authentication, access control, and data encryption. The access security management module also logs each user's operations, providing evidence for subsequent auditing. Furthermore, when the configuration file distribution unit distributes files to the distributed power access unit, the distribution result is authenticated by the security management unit (access security management b24) and then sent to the display module for display.

[0072] 2. The Mapping File Management Unit (Manufacturer Specification Mapping File Management b21) is used to receive forwarded user instructions, load mapping files from the data storage module, and perform operations such as inputting, modifying, deleting, sending request instructions (sending storage request instructions: refers to the mapping file management unit initiating a storage request command to the data storage module) and querying mapping files. The Mapping File Management Unit (Manufacturer Specification Mapping File Management b21) is responsible for comprehensive management of manufacturer specification mapping files. This includes operations such as inputting, storing, modifying (updating and iterating), deleting, sending request instructions, and querying mapping file records a5 from different manufacturers. It supports version management of specification mapping files, recording the modification history of each mapping file for version rollback when needed. Through reasonable management, the accuracy of specification mapping files is ensured, providing basic support for subsequent configuration file management. The Mapping File Management Unit (Manufacturer Specification Mapping File Management b21) is used to input, modify, and delete mapping files from different manufacturers, with the input, modification, and deletion processes as follows:

[0073] 2.1 Entering the mapping file includes:

[0074] a. Obtain the storage structure information corresponding to the mapping file within the distributed power access unit; both the mapping file and the manufacturer's protocol document are uploaded and obtained based on the interface or the API unit, and the mapping file corresponds one-to-one with the manufacturer's protocol document. The system sequentially receives the manufacturer's protocol document uploaded by the user and the corresponding mapping file through the interface or the API unit, then sends it to the configuration file management unit after authentication by the security management unit. The configuration file management unit then internally distributes it to the mapping file management unit and monitors the validity of the data in the mapping file.

[0075] b. Generate a second serialization file from the mapping file based on the storage structure information, wherein the second serialization file is the corresponding conversion file of the mapping file;

[0076] c. Associate the manufacturer's agreement document, the mapping file corresponding to the manufacturer's agreement document, and the second serialization file to obtain association information;

[0077] d. Add second metadata to the associated information to form the final mapping file record and store it in the mapping file record list. The second metadata is the metadata of the mapping file.

[0078] Combination Figure 4 The workflow for the data entry function in the Mapping File Management Unit (Manufacturer Specification Mapping File Management b21) is as follows:

[0079] Step 1: Upload Manufacturer Protocol Description Document: Users upload the manufacturer-provided Modbus protocol description document (PDF, Excel, TXT, etc.) to the configuration file management system.

[0080] Step 2, Mapping File Upload: Users upload the manually entered mapping file (Excel, JSON, or other format files) corresponding to the inverter Modbus protocol description document provided by the manufacturer to the configuration file management system.

[0081] Step 3: Check data validity: The system checks the validity of the mapping file configuration file uploaded by the user, and judges the parameter range, input character format, etc. of the mapping file. A warning is issued when invalid data is found.

[0082] Step 4: Generate serialized file (second serialized file): The system generates a second serialized file based on the storage structure of the mapping file in the distributed power access unit.

[0083] Step 5: Store the manufacturer's protocol description file, mapping file, and second serialization file record: Associate the files passed in and generated in the above process, and store the entry.

[0084] Step 6: Add second metadata: Based on the information provided by the user, the system adds and supplements metadata such as creation time, manufacturer, series, included model, protocol version, and inputter to the stored entries in Step 5 for management purposes.

[0085] Step 7: Save as a mapping file record: The system stores the entries after step 6 into the database.

[0086] 2.2 Modifying the mapping file includes:

[0087] a. Locate the first target mapping file in the mapping file record list. The first target mapping file is the target mapping file to be modified.

[0088] b. Modify the data in the first target mapping file, including: changing the manufacturer's mapping file, uploading a new mapping file, modifying the data in the first target mapping file, and modifying the second metadata of the first target mapping file;

[0089] c. Perform a validity check on the modified mapping file, and save the modified content to the database module after the check passes.

[0090] Combination Figure 5 The modification process for the mapping file management unit (manufacturer specification mapping file management b21) is as follows:

[0091] Step 1: Locate the mapping file record that needs to be modified in the mapping file record table.

[0092] Step 2, data modification, including but not limited to the following four operations: changing the manufacturer's specification mapping file, uploading a new mapping file, directly modifying the mapping file data, and directly modifying the second metadata of the mapping file.

[0093] Step 3, Validity Check: After the data modifications are confirmed, a validity check is performed. The system checks the validity of the mapping file configuration file uploaded by the user, and issues a warning when invalid data is found.

[0094] Step 4: Update and save the version: Once the validity check passes, the version number will be automatically updated, and the changes will be saved to the database.

[0095] 2.3 The process for deleting the mapped file includes:

[0096] a. Locate the second target mapping file in the mapping file record table. The second target mapping file is the target mapping file to be deleted.

[0097] b. After user confirmation, delete the second target mapping file and the second serialization file corresponding to the second target mapping file.

[0098] Combination Figure 6 The deletion process for the mapping file management unit (manufacturer specification mapping file management b21) is as follows:

[0099] Step 1: Locate the mapping file record that needs to be deleted in the mapping file record table.

[0100] Step 2: Confirm Deletion: After the user confirms the deletion, the mapped file will be deleted from the mapped file record table, and the serialized file corresponding to the mapped file will also be deleted.

[0101] 3. Configuration File Management Unit (Configuration File Management b22): This unit provides comprehensive management functions for configuration files. It allows for operations such as entering, modifying, deleting, creating, editing, filtering, and sorting configuration files. For example, users can categorize and manage configuration files according to their actual needs, facilitating quick retrieval and access to the required files. It also supports version management of configuration files, recording the modification history for version rollback when needed. The processes for entering, modifying, and deleting configuration files are as follows:

[0102] 2.1 The configuration file entry process includes:

[0103] a. Populate the first metadata of the configuration file;

[0104] b. The user selects a mapping file, and the selected mapping file is bound to the current configuration file;

[0105] c. Check if the first metadata is valid, and adjust the first metadata accordingly based on the check result to generate the final configuration file metadata;

[0106] d. Integrate the final configuration file metadata and the selected mapping file into a new configuration file and store it in the configuration file table;

[0107] e. Generate the first serialized file of the configuration file based on the configuration file table.

[0108] Combination Figure 7 The configuration file entry process is as follows:

[0109] Step 1: Populate the first metadata of the configuration file: The user fills in the metadata of the configuration file, supplementing information such as the applicable region;

[0110] Step 2: Bind Mapping Files: The user selects one or more mapping files from the mapping file record table and binds them to the current configuration file;

[0111] Step 3: Check data validity: Check primary metadata and other data for invalid data and issue warnings.

[0112] Step 4: Adjust the primary metadata: The system readjusts the metadata based on the current time, participants, and other information.

[0113] Step 5: Save as configuration file record: The system integrates the final configuration file metadata and mapping file into a configuration file and stores it in the configuration file table.

[0114] Step 6: The system generates the first serialized file of the configuration file based on the configuration file information.

[0115] 2.2 The configuration file modification process includes:

[0116] a. Locate the target configuration file to be modified in the configuration file table;

[0117] b. Modify the data in the target configuration file to be modified, including: modifying the mapping file record list and the first metadata of the configuration file;

[0118] c. Perform a validity check on the modified information, and save the modified content to the database module after the check passes.

[0119] Combination Figure 8 The process for modifying the configuration file is as follows:

[0120] Step 1: Locate the configuration file record that needs to be modified in the configuration file record table;

[0121] Step 2: Data modification, including but not limited to the following operations: modifying the list of mapping files; modifying the first metadata of the configuration file; and performing a validity check after the data modification is confirmed.

[0122] Step 3, Validity Check: The system performs a validity check on the metadata and other information modified by the user, and issues a warning when invalid data is found.

[0123] Step 4: Update and save the version: Once the validity check passes, the version number will be automatically updated, and the changes will be saved to the database.

[0124] 2.3 Configuration file deletion process combined Figure 9 As shown, it includes the following steps:

[0125] Step 1: Locate the configuration file record that needs to be deleted in the configuration file record table.

[0126] Step 2: Confirm Deletion: After the user confirms the deletion, the configuration file will be deleted from the configuration file record table, and the first serialization file corresponding to the configuration file will also be deleted.

[0127] 3. Configuration file distribution unit, used to receive user instructions, distribute configuration files to the distributed power supply access unit, and monitor and provide feedback on the distribution process in real time, specifically including:

[0128] a. Establish a connection with the target device through the user terminal;

[0129] b. After the user selects a first sequence file, the selected first sequence file is read and sent out through a preset protocol, wherein the preset protocol includes protocols supported by the distributed power access unit. For example, the 698, 645 protocol, XMODEM, or other protocols supported by the distributed power access unit.

[0130] c. Determine whether to terminate the distribution process based on whether the distribution is normal or abnormal.

[0131] Combination Figure 10 The configuration file distribution process includes:

[0132] Step 1: The system establishes a connection with the photovoltaic optimizer through devices such as mobile phones, handheld terminals, and computers;

[0133] Step 2: The user selects the first sequence file to be distributed;

[0134] Step 3: The system distributes the first sequence file selected by the user via a specific protocol;

[0135] Step 4: The system exits and returns to the distribution status when the distribution process is completed or an exception such as timeout occurs.

[0136] III. Data Storage Module 3 (Data Layer b3) is used to store configuration files and the first serialized file. The configuration file includes several mapping files. The mapping file contained in the configuration file refers to the record (a unique identifier) ​​of the mapping file within the configuration file, not the file itself. Therefore, to view the mapping file from the configuration file, the component first retrieves the ID corresponding to the mapping file from the configuration file. Then, based on this key, it retrieves the relevant information of the mapping file from the database and displays it on the interface. The first serialized file is generated from the corresponding configuration file, and the second serialized file is generated from the corresponding mapping file. The data storage module 3 is used to store various types of data information and retrieve corresponding data from the stored data information according to the user's query instructions. The data storage module 3 (Data Layer b3) is mainly responsible for data storage and management, and its core component is the database. Database b31 is used to store various data generated during system operation, including configuration files, manufacturer specification mapping files, user information, operation logs, etc. Through reasonable database design, efficient data storage structure and indexing mechanism are adopted to ensure data storage and query efficiency. Simultaneously, the database also has data backup and recovery functions, regularly backing up data to prevent data loss and enabling rapid data recovery in case of failure, ensuring the normal operation of the system.

[0137] IV. The system also includes a transmission module 4 (transmission layer b4), which includes an access API unit for communicating with external systems and interacting with external devices. External Access API (b41): The configuration file management system of the distributed power access unit provides an external access API, allowing data interaction between the configuration file management system and external systems. For example, other power management systems can obtain configuration file information from this system or send configuration file update commands to this system through the external access API, thereby achieving broader business integration and data flow.

[0138] This invention provides a configuration file management system for distributed power access units. The system offers a clear management process for configuration files, managing conversion rules and configuration files, enabling the input and distribution of configuration files, while also meeting system security requirements. It has the following advantages:

[0139] (1) The system uses mapping files as the smallest management data unit for configuration file management, which facilitates the combination of protocols contained in the configuration file;

[0140] (2) The system supports multiple terminal devices to distribute configuration files to the distributed power access unit, which reduces the operational difficulty for maintenance personnel to the greatest extent.

[0141] (3) The system provides an external API interface, which provides the ability to expand functions and share data while ensuring the security and trustworthiness of the other end.

[0142] (4) The system provides access control and logs all operations, providing traceable evidence for personnel and system operations and providing basic security for the system.

[0143] It should be understood that the specific embodiments described above are merely illustrative or explanatory of the principles of the present invention and do not constitute a limitation thereof. Therefore, any modifications, equivalent substitutions, improvements, etc., made without departing from the spirit and scope of the present invention should be included within the protection scope of the present invention. Those skilled in the art should understand that embodiments of the present invention can be provided as methods, systems, or computer program products. Therefore, the present invention can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present invention can take the form of a computer program product embodied 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. The present invention is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the present invention. These computer program instructions can also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable apparatus for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the functions specified in one or more boxes. The steps in the method of this embodiment can be adjusted, merged, and deleted according to actual needs. The modules in the system of this embodiment can be merged, divided, and deleted according to actual needs.

Claims

1. A configuration file management system for a distributed power supply access unit, characterized in that, The configuration file management system is connected to the distributed power access unit via a user terminal. The system includes: a presentation module, a data storage module, and an application module, wherein: The presentation module is used to provide an interface for interaction with the user, through which user commands are received and the results of configuration file distribution are displayed; The data storage module is used to store a configuration file and a first serialized file. The configuration file includes several mapping files, and the first serialized file is generated from the corresponding configuration file. The application module is connected to the data storage module, the display module, and the distributed power access unit, respectively. It is used to load the mapping file and configuration file from the data storage module, classify and manage the mapping file and configuration file, obtain the corresponding first serialized file according to the user instruction, and send it to the distributed power access unit, while simultaneously sending the sending result to the display module for display. The application module includes a mapping file management unit, used to receive forwarded user instructions, load the mapping file from the data storage module, and perform input, modification, deletion, sending request instructions, and querying of the mapping file. Inputting the mapping file includes: Obtain the storage structure information corresponding to the mapping file within the distributed power access unit; both the mapping file and the manufacturer's protocol document are obtained based on the interface or the API access unit, and the mapping file and the manufacturer's protocol document correspond one-to-one. The mapping file is used to generate a second serialized file based on the storage structure information. The second serialized file is the corresponding conversion file of the mapping file. The manufacturer's agreement document, the mapping file corresponding to the manufacturer's agreement document, and the second serialization file are associated to obtain the association information; A second metadata is added to the associated information to form the final mapping file record and stored in the mapping file record list. The second metadata is the metadata of the mapping file.

2. The configuration file management system for the distributed power supply access unit according to claim 1, characterized in that, The application module includes: The security management unit is used to perform security authentication on the received user commands before sending them to the configuration file management unit; Configuration file management unit: used to receive user instructions after security authentication, load configuration files from data storage module, input, modify, delete, filter and sort configuration files, and forward the user instructions after security authentication to mapping file management unit and configuration file distribution unit respectively; The configuration file distribution unit is used to receive forwarded user instructions, obtain the corresponding first serialized file from the data storage module according to the user instructions, distribute the first serialized file to the distributed power access unit, and send the distribution result to the display module for display after being authenticated by the security management unit.

3. The configuration file management system for the distributed power supply access unit according to claim 1, characterized in that, The system also includes a transmission module, which includes an access API unit for communicating with external systems.

4. The configuration file management system for the distributed power supply access unit according to claim 3, characterized in that, Modifying the mapping file includes: Find the first target mapping file in the mapping file record list. The first target mapping file is the target mapping file to be modified. Modifying the data in the first target mapping file includes: changing the manufacturer's mapping file, uploading a new mapping file, modifying the data in the first target mapping file, and modifying the second metadata of the first target mapping file; The modified mapping file is checked, and the changes are saved to the data storage module after the check is passed.

5. The configuration file management system for the distributed power supply access unit according to claim 3, characterized in that, Deleting the mapping file includes: Search the mapping file record table for the second target mapping file, which is the target mapping file to be deleted; After user confirmation, delete the second target mapping file and the second serialization file corresponding to the second target mapping file.

6. The configuration file management system for the distributed power supply access unit according to claim 2, characterized in that, The configuration file distribution unit is used to receive forwarded user instructions, obtain the corresponding first serialized file from the data storage module according to the user instructions, and distribute the first serialized file to the distributed power supply access unit, including: Establish a connection with the distributed power access unit to be distributed through the user terminal; After the user selects the first serialization file, the first serialization file selected by the user is read and sent out through the preset protocol; Determine whether to terminate the distribution process based on whether the distribution is normal or abnormal.

7. The configuration file management system for the distributed power supply access unit according to claim 2, characterized in that, The process of entering the configuration file includes: Populate the first metadata of the configuration file; Bind the user-selected mapping file to the current configuration file; Check whether the first metadata is valid, and adjust the first metadata accordingly based on the check result to generate the final configuration file metadata; The final configuration file metadata and the selected mapping file are integrated into a new configuration file and stored in the configuration file table; Based on the configuration file table, a first serialized file of the configuration file is generated.

8. The configuration file management system for the distributed power supply access unit according to claim 7, characterized in that, The modification of the configuration file includes: Locate the target configuration file to be modified in the configuration file table; Modifying the data in the target configuration file to be modified includes: modifying the mapping file record list and the first metadata of the configuration file; The modified information is checked, and once the check is passed, the changes are saved to the data storage module.

9. The configuration file management system for the distributed power supply access unit according to claim 7, characterized in that, The presentation modules include a web interface and an app interface.

Images