Method and system for managing design rule base of photovoltaic power station

Abstract

The embodiment of the invention provides a management method and system for a design rule base of a photovoltaic power station, and the method comprises the steps: obtaining a rule document and rule data through a heterogeneous data source collection interface to form a rule base, and carrying out the repeatability verification of the collected rule base based on a file hash value and a timestamp; semantic analysis is carried out on the verified rule base, key terms, constraint conditions, an application range and a logic relation in the rule base are extracted, a rule knowledge graph is constructed, nodes represent rule terms, and edges represent the incidence relation of the rule terms; when it is detected that the rule base is updated, the semantic difference degree is calculated by comparing text differences, a new rule base version number is generated through progressive increase, change content is recorded, a change log is generated, and a rule change notification is sent to a user. According to the method, the problems of rule updating lag and inconvenient management are solved, the long-term pain point in industry rule management is solved, and the method has wide application prospect and market value.

Description

Technical Field

[0001] This document relates to the technical field of photovoltaic power station design, and in particular to a management method and system for a photovoltaic power station design rule base. Background Art

[0002] PV power plant design must strictly adhere to national standards, industry specifications, and internal company regulations. These rules are constantly updated in response to technological advancements, policy adjustments, and market changes. However, traditional manual updating methods are inefficient and prone to missing the latest rules, causing the rule base to lag behind actual needs, thus affecting design quality and compliance. Furthermore, the rule base lacks standardized version management and change logging, making it difficult to track rule evolution. Therefore, an efficient and automated system is urgently needed to dynamically update and effectively manage the rule base. Summary of the Invention

[0003] One or more embodiments of this specification provide a method for managing a photovoltaic power station design rule library, including:

[0004] S1. Obtain rule documents and rule data through the heterogeneous data source collection interface to form a rule base, and perform duplication verification on the collected rule base based on the file hash value and timestamp;

[0005] S2. Perform semantic analysis on the verified rule base, extract key clauses, constraints, scope of application, and logical relationships within the rule base, and construct a rule knowledge graph, where nodes represent rule clauses and edges represent relationships between rule clauses.

[0006] S3. When a rule base update is detected, the semantic difference is calculated by comparing text differences, and a new rule base version number is generated incrementally. The changes are recorded, a change log is generated, and a rule change notification is sent to the user.

[0007] Furthermore, the heterogeneous data sources include rule documents published on official websites and industry standard database data; the rule base acquisition method specifically includes:

[0008] Extract the latest rule documents released on the official website through web crawlers;

[0009] Connect to industry standard database and enterprise database through API interface to parse and obtain rule data.

[0010] Furthermore, the method in step S2 specifically includes:

[0011] Extract key terms from the rule base through dependency parsing and named entity recognition, and identify the technical parameters, constraints, and applicable scope of the key terms;

[0012] Identify logical relationships between key clauses based on a logic rule template, including but not limited to conflict relationships and dependency relationships;

[0013] Convert the parsing results into nodes and edges in the knowledge graph, where nodes represent rule clause entities and edges represent the relationships between entities;

[0014] After the knowledge graph is constructed, it is stored according to the categories to which each knowledge graph belongs.

[0015] Furthermore, the method further includes: when generating the change log, using a text matching algorithm based on edit distance to locate differences between versions, and generating a readability summary of the difference content according to a preset template, and sending the readability summary to the user when sending a rule change notification to the user.

[0016] Furthermore, the method further includes: after generating a new rule base version number, performing a historical version backtracking based on the historical rule base version number, and checking any version of the rule base according to the historical rule base version number.

[0017] Furthermore, the recording of the change content and generating a change log specifically includes:

[0018] Automatically generate a summary of rule updates based on the updated content of the rule base, the summary including newly added, modified, and deleted entries in the rule base;

[0019] Export the summary of generated rule updates to generate a change log report for archiving and sharing.

[0020] Furthermore, the method further includes encrypting and storing the rule base, controlling the user's operation authority over the rule data based on the role authority model, and recording operation logs to associate user behavior with data change records, specifically:

[0021] The role-based permission model assigns different permissions based on user roles, including administrators, designers, and reviewers. Permission assignment includes hierarchical configuration of rule editing permissions, version rollback permissions, and log audit permissions.

[0022] Encrypt and store the contents of the rule base and its change log;

[0023] Record user query, update and download operations, record data changes, and generate operation logs.

[0024] One or more embodiments of this specification provide a management system for a photovoltaic power station design rule library, including:

[0025] Rule base acquisition module: used to obtain rule documents and rule data through the heterogeneous data source acquisition interface to form a rule base, and perform duplication verification on the collected rule base based on the file hash value and timestamp;

[0026] Rule parsing module: used to perform semantic analysis on the verified rule base, extract key terms, constraints, scope of application and logical relationships in the rule base, and construct a rule knowledge graph, where nodes represent rule terms and edges represent the relationship between rule terms;

[0027] Rule base update module: When a rule base update is detected, it calculates the semantic difference by comparing text differences, incrementally generates a new rule base version number, records the changes, generates a change log, and sends a rule change notification to the user.

[0028] One or more embodiments of this specification provide an electronic device, including:

[0029] processor; and,

[0030] A memory is arranged to store computer-executable instructions, which, when executed, enable the processor to implement the steps of the above-mentioned method for managing a photovoltaic power plant design rule base.

[0031] One or more embodiments of this specification provide a storage medium for storing computer-executable instructions, which, when executed, implement the steps of the above-mentioned method for managing a photovoltaic power station design rule library.

[0032] By adopting the embodiment of the present invention, an efficient and automated dynamic update and management system for the photovoltaic power station design rule base is proposed, which solves the problems of delayed rule updates and inconvenient management, provides an efficient and reliable rule base management tool for photovoltaic power station design, solves the long-standing pain points in industry rule management, and has broad application prospects and market value.

[0033] 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 in accordance with 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 specifically listed below. BRIEF DESCRIPTION OF THE DRAWINGS

[0034] In order to more clearly illustrate one or more embodiments of this specification or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are only some embodiments recorded in this specification. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0035] Figure 1 A flowchart of a method for managing a photovoltaic power station design rule library provided in one or more embodiments of this specification;

[0036] Figure 2 A schematic diagram of the composition of a management system for a photovoltaic power station design rule base provided in one or more embodiments of this specification;

[0037] Figure 3 A schematic diagram of the structure of an electronic device provided in one or more embodiments of this specification. DETAILED DESCRIPTION

[0038] In order to enable those skilled in the art to better understand the technical solutions in one or more embodiments of this specification, the technical solutions in one or more embodiments of this specification will be clearly and completely described below in conjunction with the drawings in one or more embodiments of this specification. Obviously, the described embodiments are only part of the embodiments of this specification, not all of the embodiments. Based on one or more embodiments of this specification, all other embodiments obtained by ordinary technicians in this field without making creative efforts should fall within the scope of protection of this document.

[0039] Method Example

[0040] According to an embodiment of the present invention, a method for managing a photovoltaic power station design rule base is provided. Figure 1 A flowchart of a method for managing a photovoltaic power station design rule library provided in one or more embodiments of this specification is shown in FIG. Figure 1 As shown, the management method of the photovoltaic power station design rule base according to an embodiment of the present invention specifically includes:

[0041] S1. Obtain rule documents and rule data through the heterogeneous data source collection interface to form a rule base, and perform duplication verification on the collected rule base based on the file hash value and timestamp.

[0042] The heterogeneous data sources include rule documents published on official websites and industry specification database data. Through web crawler technology, the official website is automatically accessed, and the latest rule documents are extracted according to the preset crawling rules and paths. These documents may contain various rule information such as laws, policies, and standards, presented in text form; the API interface is used to connect with the industry specification database and the enterprise database, and by calling the API interface, a request is sent to the database according to the parameters and format specified by the interface to obtain the rule data therein. These data may be structured, such as rule entries and rule attributes in tabular form, or they may be semi-structured and require further analysis to extract useful rule information. The rule documents and rule data collected above are integrated together to form a complete rule library.

[0043] For the collected rule documents, calculate their hash values. If the hash values ​​of the two files are the same, then it can be assumed that the contents of the two files are completely consistent. By comparing the hash value of the newly collected rule document with the hash value of the corresponding document in the existing rule library, it is possible to quickly determine whether the document already exists in the rule library, thereby avoiding repeated storage of documents with the same content. In addition, when verifying the rule library, check the timestamps of the newly collected rule documents and rule data, and compare them with the timestamps of the existing data in the rule library. If the timestamp of the newly collected data is later than the timestamp of the corresponding data in the rule library, it means that the newly collected data is an updated version and the relevant content in the rule library needs to be updated; if the timestamps are the same or earlier than the timestamp in the rule library, it may be duplicate data, and corresponding deduplication processing can be performed to avoid duplicate rule documents and data in the rule library, ensuring the accuracy and timeliness of the rule library.

[0044] S2. Perform semantic analysis on the verified rule base, extract key terms, constraints, scope of application and logical relationships in the rule base, and construct a rule knowledge graph, where nodes represent rule terms and edges represent the association relationships between rule terms.

[0045] Conduct an in-depth analysis of the verified rule base and extract valuable information from the rule text through dependency syntax analysis and named entity recognition, including key terms, i.e. the main content of the rules, technical parameters, constraints, i.e. the limiting conditions of the rules, scope of application, i.e. the objects and scenarios to which the rules apply, and logical relationships between rules, such as sequence, cause and effect, etc. Based on the logical rule template, identify the logical relationships between key terms, including but not limited to conflict relationships and dependency relationships.

[0046] Key terms, constraints, and scopes of application derived from semantic analysis are used as nodes, and the logical relationships between them as edges to construct a knowledge graph. Once the knowledge graph is constructed, it is stored according to its category. This classification can be based on the rule's domain, industry, application scenario, and other factors, making it easier for users to quickly find relevant knowledge graphs as needed.

[0047] S3. When a rule base update is detected, the semantic difference is calculated by comparing text differences, and a new rule base version number is generated incrementally. The changes are recorded, a change log is generated, and a rule change notification is sent to the user.

[0048] Regularly check file hash values, timestamps, or obtain update notifications through the API interface to detect whether the rule base has been updated. When a new version or content change is detected in the rule document or data in the rule base, first use a text comparison tool or algorithm to compare the text differences between the old and new versions, including insertions, deletions, and modifications. Then calculate the semantic difference and use natural language processing (NLP) technology to evaluate the impact of the change in text content on the actual meaning of the rules. After the content is updated, a new version number is generated for each update. The version number is usually incremented, for example, starting from 1.0.0, and the version number is incremented after each update, such as 1.0.1, 1.1.0, etc. The version number format is designed according to specific needs. Common formats include major version number, minor version number, and revision number. The version number increment method is determined by the nature and importance of the update.

[0049] Record the specific content of the rule base update in detail, including new rules, modified rules, and deleted rules, and organize the recorded changes into a detailed change log. Specifically, it includes: automatically generating a summary of the rule update based on the updated content of the rule base, and the summary includes new, modified, and deleted entries in the rule base; exporting the generated summary of the rule update, generating a change log report, and archiving and sharing it. When generating the change log, a text matching algorithm based on edit distance is used to locate the differences between versions, and a readable summary of the difference content is generated according to a preset template. The readable summary is sent to the user when the rule change notification is sent to the user. The change log usually includes information such as the version number, update date, description of the change content, affected rule clauses, etc., and can be provided to the user in the form of a document or an online log.

[0050] After generating a new rule base version number, perform historical version backtracking based on the historical rule base version number, and view any version of the rule base based on the historical rule base version number.

[0051] The rule base is encrypted and stored, and the user's operation permissions on the rule data are controlled based on the role permission model. At the same time, operation logs are recorded to associate user behavior with data change records. Specifically: the role permission model assigns different permissions according to user roles. The user roles include administrators, designers, and reviewers. The permission allocation includes hierarchical configuration of rule editing permissions, version rollback permissions, and log audit permissions; the content of the rule base and its change logs are encrypted and stored; users' query, update, and download operations are recorded, data changes are recorded, and operation logs are generated.

[0052] Furthermore, this embodiment provides a user-friendly query and retrieval interface. Users can search for relevant content in the rule base by entering keywords. The system will search for matching rule clauses in the rule base based on the keywords entered by the user, and quickly locate the content that the user is interested in. In addition to keyword search, the system also supports precise matching of rule clauses. Users can enter complete rule clauses or specific rule numbers, and the system will accurately find rule content that fully matches them. Users can filter rules according to their needs, such as by region, time or standard type, and provide an API interface to support other design systems to call rule base data. Among them, filtering by region includes selecting a specific country, province or city to obtain rules applicable to the region; filtering by time range includes selecting a specific year, quarter or date range to obtain rules that are effective or updated within that time period; filtering by rule standard type includes selecting regulations, industry standards, internal corporate rules, etc., which can help users quickly find specific types of rules and improve the pertinence of queries.

[0053] The beneficial effects of the present invention are as follows:

[0054] By adopting the embodiment of the present invention, real-time collection and dynamic update of rule data are achieved through web crawlers and API interfaces, ensuring that the rule base is always up-to-date; through NLP technology and knowledge graph construction, the rule content can be efficiently parsed and integrated, improving the availability and retrieval efficiency of the rules; version management and change log functions are provided, and users can view the evolution history of the rule base at any time to ensure that the design and review work is based on evidence; the workload of manual maintenance is reduced, and the risk of design quality problems caused by rule lags is reduced; data encryption and permission control are used to protect the integrity and access security of the rule base; in summary, the present invention proposes an efficient and automated dynamic update and management system for photovoltaic power station design rule base, which solves the problems of rule update lag and management inconvenience, provides an efficient and reliable rule base management tool for photovoltaic power station design, solves the long-standing pain points in industry rule management, and has broad application prospects and market value.

[0055] System Example

[0056] According to an embodiment of the present invention, a management system for a photovoltaic power station design rule base is provided. Figure 2 A schematic diagram of a management system for a photovoltaic power station design rule base provided in one or more embodiments of this specification is shown in FIG. Figure 2 As shown, the management system of the photovoltaic power station design rule base according to an embodiment of the present invention specifically includes:

[0057] Rule base acquisition module 20: used to acquire rule documents and rule data through the heterogeneous data source acquisition interface to form a rule base, and perform duplication verification on the acquired rule base based on the file hash value and timestamp;

[0058] Rule parsing module 22: used to perform semantic parsing on the verified rule base, extract key terms, constraints, applicable scope and logical relationships in the rule base, and construct a rule knowledge graph, where nodes represent rule terms and edges represent the relationship between rule terms;

[0059] The rule base update module 24 is used to calculate the semantic difference by comparing text differences when a rule base update is detected, generate a new rule base version number incrementally, record the changed content, generate a change log, and send a rule change notification to the user.

[0060] The embodiment of the present invention is a system embodiment corresponding to the above-mentioned method embodiment. The specific operations of each module can be understood by referring to the description of the method embodiment, which will not be repeated here.

[0061] Device Example 1

[0062] An embodiment of the present invention provides an electronic device, such as Figure 3 As shown, it includes: a memory 30, a processor 32, and a computer program stored in the memory 30 and executable on the processor 32. When the computer program is executed by the processor 32, the following method steps are implemented:

[0063] S1. Obtain rule documents and rule data through the heterogeneous data source collection interface to form a rule base, and perform duplication verification on the collected rule base based on the file hash value and timestamp;

[0064] S2. Perform semantic analysis on the verified rule base, extract key clauses, constraints, scope of application, and logical relationships within the rule base, and construct a rule knowledge graph, where nodes represent rule clauses and edges represent relationships between rule clauses.

[0065] S3. When a rule base update is detected, the semantic difference is calculated by comparing text differences, and a new rule base version number is generated incrementally. The changes are recorded, a change log is generated, and a rule change notification is sent to the user.

[0066] Device Example 2

[0067] An embodiment of the present invention provides a computer-readable storage medium having stored thereon a program for implementing information transmission. When the program is executed by the processor 32, the following method steps are implemented:

[0068] S1. Obtain rule documents and rule data through the heterogeneous data source collection interface to form a rule base, and perform duplication verification on the collected rule base based on the file hash value and timestamp;

[0069] S2. Perform semantic analysis on the verified rule base, extract key clauses, constraints, scope of application, and logical relationships within the rule base, and construct a rule knowledge graph, where nodes represent rule clauses and edges represent relationships between rule clauses.

[0070] S3. When a rule base update is detected, the semantic difference is calculated by comparing text differences, and a new rule base version number is generated incrementally. The changes are recorded, a change log is generated, and a rule change notification is sent to the user.

[0071] The computer-readable storage medium in this embodiment includes, but is not limited to, ROM, RAM, magnetic disk, or optical disk.

[0072] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit it. Although the present invention has been described in detail with reference to the above embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the above embodiments, or replace some or all of the technical features therein with equivalents. However, these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present invention.

Claims

1. A method for managing a photovoltaic power station design rule base, characterized in that: include: S1. Obtain rule documents and rule data through the heterogeneous data source collection interface to form a rule base, and perform duplication verification on the collected rule base based on the file hash value and timestamp; S2. Perform semantic analysis on the verified rule base, extract key clauses, constraints, scope of application, and logical relationships within the rule base, and construct a rule knowledge graph, where nodes represent rule clauses and edges represent relationships between rule clauses. S3. When a rule base update is detected, the semantic difference is calculated by comparing text differences, and a new rule base version number is generated incrementally. The changes are recorded, a change log is generated, and a rule change notification is sent to the user.

2. The method according to claim 1, wherein The heterogeneous data sources include rule documents published on official websites and industry standard database data; the rule base acquisition method specifically includes: Extract the latest rule documents released on the official website through web crawlers; Connect to industry standard database and enterprise database through API interface to parse and obtain rule data.

3. The method according to claim 1, wherein The method described in step S2 specifically includes: Extract key terms from the rule base through dependency parsing and named entity recognition, and identify the technical parameters, constraints, and applicable scope of the key terms; Identify logical relationships between key clauses based on a logic rule template, including but not limited to conflict relationships and dependency relationships; Convert the parsing results into nodes and edges in the knowledge graph, where nodes represent rule clause entities and edges represent the relationships between entities; After the knowledge graph is constructed, it is stored according to the categories to which each knowledge graph belongs.

4. The method according to claim 1, wherein The method further includes: when generating the change log, using a text matching algorithm based on edit distance to locate differences between versions, generating a readability summary of the difference content according to a preset template, and sending the readability summary to the user when sending a rule change notification to the user.

5. The method according to claim 1, wherein The method further includes: after generating a new rule base version number, tracing back to a historical version based on the historical rule base version number, and checking any version of the rule base according to the historical rule base version number.

6. The method according to claim 1, wherein The recording of the change content and generating the change log specifically includes: Automatically generate a summary of rule updates based on the updated content of the rule base, the summary including newly added, modified, and deleted entries in the rule base; Export the summary of generated rule updates to generate a change log report for archiving and sharing.

7. The method according to claim 1, wherein The method further includes encrypting and storing the rule base, controlling the user's operation rights on the rule data based on a role-based permission model, and recording operation logs to associate user behavior with data change records, specifically: The role-based permission model assigns different permissions based on user roles, including administrators, designers, and reviewers. Permission assignment includes hierarchical configuration of rule editing permissions, version rollback permissions, and log audit permissions. Encrypt and store the contents of the rule base and its change log; Record user query, update and download operations, record data changes, and generate operation logs.

8. A management system for a photovoltaic power station design rule base, characterized in that: include: Rule base acquisition module: used to obtain rule documents and rule data through the heterogeneous data source acquisition interface to form a rule base, and perform duplication verification on the collected rule base based on the file hash value and timestamp; Rule parsing module: used to perform semantic analysis on the verified rule base, extract key terms, constraints, scope of application and logical relationships in the rule base, and construct a rule knowledge graph, where nodes represent rule terms and edges represent the relationship between rule terms; Rule base update module: When a rule base update is detected, it calculates the semantic difference by comparing text differences, incrementally generates a new rule base version number, records the changes, generates a change log, and sends a rule change notification to the user.

9. An electronic device, characterized in that: include: processor; as well as, A memory arranged to store computer-executable instructions, wherein when the computer-executable instructions are executed, the processor implements the steps of the method for managing a photovoltaic power plant design rule base according to any one of claims 1 to 7.

10. A storage medium, characterized in that: Used to store computer-executable instructions, which, when executed, implement the steps of managing the photovoltaic power station design rule library as claimed in any one of claims 1 to 7.

Images