Generation method and system of power grid dispatching real-time information

Abstract

The invention provides a power grid dispatching real-time information generation method and system, relates to the technical field of power grid dispatching management, and aims to solve the problems of low automation degree and insufficient pertinence of dispatching information generation. The method comprises the following steps: acquiring event parameters of an electric power security event; judging an event type according to the event parameter, and when the event type is a preset accident type, automatically determining an accident event level based on a preset rule; automatically matching a target information template from a template library according to the event type and the determined accident event level; and automatically filling the accident event level and other event information into the target information template to generate scheduling real-time information. According to the method, the events are classified and graded, and the template is accurately matched, so that the accuracy and pertinence of information generation are improved, and the working efficiency is improved.

Description

Technical Field

[0001] This application relates to the field of power grid dispatch management technology, and in particular to a method, apparatus and system for generating real-time power dispatch information. Background Technology

[0002] In the dispatching and operation management of modern power grids, the timely and accurate transmission of various real-time information is crucial. This information includes emergencies such as equipment failures and line trips, as well as routine dispatching information such as new equipment commissioning and planned power outages and restorations. Currently, a common approach is for dispatchers to rely on manual operation. For example, they pre-create templates for various information in office software. When a specific event occurs, they manually search for and filter the corresponding template, then copy and fill in key information such as the event time and equipment name, and finally transmit the information through the communication system. This purely manual operation process is cumbersome. Especially when power grid emergencies occur, the additional information editing and transmission work is not only time-consuming and labor-intensive, but also prone to errors due to haste, leading to mis-sending or omissions of information, thus affecting the efficiency and accuracy of information transmission.

[0003] To address the aforementioned issues, some automated auxiliary tools have emerged in the existing technology, capable of acquiring power grid event information, performing preliminary fault diagnosis, and generating fault information based on the diagnostic results and preset templates. However, these existing systems still have shortcomings in terms of the accuracy of information generation. They typically match information templates based only on a comprehensive diagnostic result, failing to adequately distinguish the specific types of events and the differences between different severity levels. For example, the system may only vaguely determine that "an accident has occurred," but cannot distinguish whether it is an equipment failure or a line trip, nor can it differentiate between different severity levels of the same type of accident. This results in the generated dispatch information being overly general, failing to accurately reflect the subtle differences in events, and reducing the relevance and effectiveness of the information.

[0004] Therefore, existing technologies still lack a solution that can classify and categorize events in a refined manner, and accurately match and generate differentiated scheduling information accordingly. Summary of the Invention

[0005] The purpose of this application is to provide a method, apparatus and system for generating real-time power dispatch information, which aims to solve the technical problems of low automation, cumbersome operation and easy error in the power grid dispatch information generation process in the prior art, as well as the lack of specificity and inability to accurately match event types and severity levels in the existing automation schemes when generating information.

[0006] To achieve the above objectives, this application provides the following technical solution: In a first aspect, embodiments of this application provide a method for generating real-time power dispatch information. The method includes: acquiring event parameters related to a power safety event; determining the event type of the power safety event based on the event parameters; and, when the event type is a preset accident type requiring level determination, automatically determining the accident event level of the power safety event based on preset accident event judgment rules; automatically matching and obtaining a target information template from a preset template library based on the determined event type and the accident event level determined when the event type is the preset accident type; and automatically filling the determined accident event level and other event information into the target information template to generate real-time dispatch information.

[0007] Based on the above method, optionally, the step of obtaining event parameters related to power safety events includes: automatically obtaining the event parameters from the power grid energy management system or monitoring and data acquisition system.

[0008] Based on the above method, optionally, the event parameters include at least one of the following: number of power plants experiencing power outages, voltage level, load loss, outage duration, and outage equipment.

[0009] Optionally, based on the above method, the step of automatically determining the accident event level based on preset accident event judgment rules includes: passing the event parameters to the rule engine module; the rule engine module loading an independent rule library, and matching the event parameters with the rules in the rule library to determine the accident event level.

[0010] Based on the above method, optionally, the preset accident event judgment rule is set according to the power accident event investigation procedure.

[0011] Based on the above method, optionally, the template library is an information template database; the step of automatically matching and obtaining the target information template from the preset template library includes: using the event type and the accident event level as query conditions to query the information template database to obtain the target information template.

[0012] Based on the above method, optionally, when no target information template that completely matches the query conditions is found, a second query is performed by reducing the query conditions to obtain the target information template.

[0013] Based on the above method, optionally, the method further includes: before generating the real-time scheduling information, obtaining the event occurrence time through the user interface, and filling the event occurrence time as part of the other event information into the target information template.

[0014] Secondly, embodiments of this application also provide a system for generating real-time power grid dispatch information. This system, corresponding to the method described above, includes: a parameter acquisition module for acquiring event parameters related to power safety events; an analysis and judgment module for determining the event type of the power safety event based on the event parameters, and, when the event type is a preset accident type requiring level judgment, automatically determining the accident event level of the power safety event based on preset accident event judgment rules; a template matching module for automatically matching and acquiring a target information template from a preset template library based on the determined event type and the accident event level determined when the event type is the preset accident type; and an information generation module for automatically filling the determined accident event level and other event information into the target information template to generate real-time dispatch information.

[0015] Based on the above system, optionally, the analysis and judgment module includes: a rule engine unit, which is used to load an independent rule library and match the event parameters according to the rules in the rule library to determine the accident event level.

[0016] Compared with the prior art, this application has the following beneficial effects: 1. Improved the accuracy and relevance of information generation. By first determining the event type and then determining the accident level as needed, and using the combination of event type and accident level to accurately match information templates, it overcomes the shortcomings of existing technologies that rely solely on general diagnostic results, resulting in weak information relevance. This ensures that the generated scheduling information is highly consistent with the specific circumstances of the event. 2. Significantly improved work efficiency by integrating multiple steps that originally required manual judgment, searching, copying, and filling into an automated process, greatly shortening the time for generating dispatch information and allowing dispatchers to focus more on core accident handling tasks. 3. It reduces the workload and pressure on dispatchers. The automated process frees dispatchers from tedious and repetitive information processing work, and can effectively avoid errors caused by distracted operation, especially in emergency situations. 4. Promote the safe and stable operation of the power grid. Through rapid and accurate information transmission, it can ensure that relevant management departments and operation and maintenance units obtain accurate on-site information in the first instance, so as to make timely and correct responses, and provide strong support for ensuring the safe and stable operation of the power grid. Attached Figure Description

[0017] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application. Furthermore, these drawings and textual descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concepts of this application to those skilled in the art through reference to specific embodiments.

[0018] Figure 1 A schematic diagram of the structure of a power dispatch real-time information generation device provided in an embodiment of this application; Figure 2 A flowchart illustrating a method for generating real-time power dispatch information provided in this application embodiment; Figure 3 A schematic diagram of the accident event level determination process provided in the embodiments of this application; Figure 4 This is a schematic diagram illustrating the complete information generation process provided in the embodiments of this application. Detailed Implementation

[0019] To make the objectives, technical solutions, and advantages of this application clearer, the technical solutions in the embodiments of this application will be clearly and completely described below in conjunction with the embodiments of this application. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application. Unless otherwise specified, the following embodiments and features can be combined with each other.

[0020] Example 1 This embodiment provides a method and apparatus for generating real-time power dispatch information. The following will be discussed in conjunction with the attached... Figure 1 To be continued Figure 4 Taking the scenario where the dispatcher manually inputs event parameters as an example, this paper elaborates on the process of the system automatically completing event level judgment, template matching and information generation.

[0021] Please see Figure 1 This document illustrates a schematic diagram of a real-time power dispatch information generation device 100 provided in an embodiment of this application. The device 100 can be specifically implemented as a general-purpose computer, server, workstation, or embedded device. From a hardware perspective, the device 100 typically includes at least one processor 300 and a memory 310 communicatively connected to the processor 300. Furthermore, the device 100 may be configured with input and output devices for human-computer interaction, such as a keyboard, mouse, and monitor. It is understood that the memory 310, as a computer-readable storage medium, stores program code, and when the processor 300 executes this program code, it can implement the steps described below.

[0022] From a software function perspective, the program stored in memory 310 can be organized into a series of functional modules. Specifically, these modules may include: Parameter acquisition module 110 is used to acquire event parameters related to power safety events; The event judgment module 120 is responsible for determining the nature of the event based on the acquired event parameters; The template matching module 130 matches and extracts the corresponding information template from the preset template library 200 according to the nature of the event; And an information generation module 140, used to integrate information and generate the final scheduling message.

[0023] In one embodiment of this application, the event judgment module 120 may further include a type judgment unit 121 and a level judgment unit 122. The type judgment unit 121 is responsible for initially classifying events to determine their type, such as "transmission and transformation equipment failure" or "new equipment commissioning." Correspondingly, the level judgment unit 122 is a condition-triggered unit; it is activated only when the judgment result of the type judgment unit 121 indicates that the current event belongs to a preset accident type requiring accident level assessment, in order to execute specific level assessment logic.

[0024] The template library 200 can be a data structure stored in the memory 310. As an optional implementation, the template library 200 can be implemented in the form of a dictionary or a hash table, where the keys can be composed of event type and incident level, and the values ​​correspond to specific text template strings.

[0025] The following will combine Figure 2 The overall method flowchart is shown below, and refer to... Figure 3 and Figure 4 The flowchart shown below provides a detailed description of the working process of this embodiment. For example, in a specific scenario: a 220 kV substation experiences a complete power outage due to a main transformer failure, and the dispatcher needs to immediately generate and issue corresponding dispatch information.

[0026] In step S201, event parameters are acquired. Specifically, the dispatcher operates the system through a graphical user interface provided by the parameter acquisition module 110 on the information generation device 100. This interface can be configured with multiple input controls, such as a drop-down menu named "Event Type," from which the dispatcher can select "Transmission and Transformation Equipment Failure"; a drop-down menu named "Voltage Level," from which "220kV" can be selected; and multiple text input boxes for the dispatcher to fill in information such as "Number of Power Loss Stations" as "1," "Loss Load" as "50 MW," and "Out-of-Power Equipment" as "Main Transformer of XX Substation" based on real-time operating conditions. These data input by the dispatcher collectively constitute the event parameters for this power safety event and serve as the basis for subsequent automated judgment.

[0027] In step S202, the event type is determined. The parameter acquisition module 110 transmits the "power transmission and transformation equipment fault" information selected by the user to the type determination unit 121 in the event determination module 120, which determines the event type of this power safety event accordingly.

[0028] Subsequently, in step S203, it is determined whether the current event is a preset accident type. It should be noted that the type determination unit 121 can maintain a predefined list containing all event types that require accident level assessment, such as "transmission and transformation equipment failure," "line tripping," and "large-scale power outage." The type determination unit 121 compares the current event type "transmission and transformation equipment failure" with this list. Since a match is found, the determination result is "yes," and the process continues to step S204.

[0029] In step S204, the accident event level is automatically determined. Based on the positive judgment result in step S203, the level judgment unit 122 within the event judgment module 120 is activated. This unit receives all event parameters collected by the parameter acquisition module 110, including "number of substations experiencing voltage loss = 1", "voltage level = 220kV", "load loss = 50MW", etc. (Refer to...) Figure 3 The internal processing flow of this step may include: In step S2041, the level judgment unit 122 receives the above event parameters.

[0030] Step S2042: Calculation is performed using preset rules. Specifically, the level judgment unit 122 internally contains a set of preset accident event judgment rules. As a preferred implementation, these rules can be set according to authoritative industry standards, for example, by fully referencing the relevant clauses of the "China Southern Power Grid Co., Ltd. Power Accident Incident Investigation Procedures" for digitization and proceduralization. In this scenario, the judgment logic can be implemented as a function based on the Python language, which contains a series of conditional judgment statements, as shown in the following example: # def determine_accident_level(params): #if params['event_type'] == 'Power transmission and transformation equipment failure': #if params['voltage_level'] == '220kV' and params['num_substations_down']>= 1: ## Rule A: Requires a complete shutdown of all 220kV substations #return "Level IV Power Safety Incident", "Based on regulations and clauses xxx: 220kV substation completely shut down" #if params['lost_load']>= 50 and params['lost_load']<100: ## Rule B: Meets the requirement of a loss load of 50MW or more #return "Level IV Power Safety Incident", "According to regulations and clauses: Load loss reaches 50MW" ## ... Other rules The level judgment unit 122 executes this logic and finds that the input parameters "voltage level = 220kV" and "number of substations experiencing power loss = 1" satisfy the conditions of "Rule A", while the parameter "load loss = 50MW" also satisfies the conditions of "Rule B". After comprehensive judgment, the system determines the accident event level of this event. In step S2043, the level judgment unit 122 outputs the final judgment result: "Power safety level IV event".

[0031] As a preferred implementation, in order to enhance the transparency and credibility of the system, in step S2044, the system can also output the specific procedural clauses on which this conclusion is based, such as "According to procedural clause xxx: 220kV substation completely shut down", and display this judgment basis on the user interface for dispatcher to verify.

[0032] After determining the incident level, the process proceeds to step S205, where a target information template is matched based on the event type and / or incident level. For example... Figure 4 As shown in steps S401 and S402, the template matching module 130 receives two key pieces of information from the event judgment module 120: the event type "transmission and transformation equipment failure" and the accident event level "power safety level IV event". The template matching module 130 can use these two pieces of information to form a composite query key, such as "transmission and transformation equipment failure_level IV", and search for it in the preset template library 200. Assume that the template library 200 contains the following entries: "Transmission and Transformation Equipment Fault - Level IV": "{Time}, {Voltage Level} kV, {Equipment Name} fault, {Substation Name} loss of voltage. According to the 'Investigation Regulations for Power Accidents of China Southern Power Grid Co., Ltd.', this constitutes a power safety {Accident Level} event." Template matching module 130 successfully matched and obtained the template string, which is then used as the target information template. Understandably, this dual matching mechanism of "type + level" ensures the accuracy of the selected template, thus avoiding the use of overly general templates.

[0033] In step S206, other event information is obtained. Before generating the final information, it may be necessary to supplement information not included in the initial parameters but required by the template. In this embodiment, since the target information template contains a {time} placeholder, such as... Figure 4 As shown in step S403, the information generation module 140 can trigger an interactive operation, such as popping up a time selection control on the display to prompt the dispatcher to enter or select the exact time the event occurred. The dispatcher selects "October 26, 14:30", and this time information is captured and included as part of "Other Event Information".

[0034] In step S207, information is automatically filled in to generate complete scheduling information. This step corresponds to... Figure 4 Step S404. The information generation module 140 performs a string replacement operation, filling in the acquired accident event level "Level IV Power Safety Event", event time "October 26, 14:30", and the information initially obtained from the parameter acquisition module 110, such as "Voltage Level = 220kV", "Equipment Name = Main Transformer", and "Substation Name = XX Substation", into the corresponding placeholders in the target information template. After filling, a complete and formatted real-time dispatch information is generated: "October 26, 14:30, 220kV main transformer failure, XX substation lost power. According to the 'China Southern Power Grid Co., Ltd. Power Accident Incident Investigation Regulations', this constitutes a Level IV Power Safety Event." In step S208, the scheduling information is output. This step corresponds to... Figure 4 Step S405. The information generation module 140 outputs the generated complete information text to a designated area of ​​the display (such as a text box) and provides convenient operations such as "copy". After the dispatcher reviews and confirms that there are no errors, he can copy the information with one click and paste it into the corresponding communication system for publication.

[0035] Through the technical solution of this embodiment, a series of tedious operations such as judgment, search, copying, and filling that previously required dispatchers to perform manually are now highly automated. This not only greatly shortens the information generation time but also improves the accuracy of the information, allowing dispatchers to focus more on the accident handling itself.

[0036] Example 2 This embodiment is a further optimization of Embodiment 1, mainly improving the method of "obtaining event parameters" in step S201, aiming to automate the acquisition of event parameters and thus elevate the automation level of the entire information generation process to a new level. The system structure of this embodiment is similar to... Figure 1 The results are basically the same, but the functionality of the parameter acquisition module 110 has been expanded.

[0037] In this embodiment, the information generation device 100 establishes a real-time communication connection with the power grid's energy management system or monitoring and data acquisition system via a network interface. The parameter acquisition module 110 can integrate a data interface unit, which can be implemented as a message queue consumer, a web service client, or a parser for a dedicated communication protocol. Its function is to continuously listen for and receive real-time alarms or event messages issued by the aforementioned external systems.

[0038] The following is a detailed description of a scenario where parameters are automatically acquired based on a monitoring and data acquisition system. Assume a 500 kV transmission line trips due to a fault.

[0039] At this point, the process no longer starts with manual input, but is triggered by an external system. Upon detecting a line tripping event, the monitoring and data acquisition system immediately broadcasts an event alarm message on its internal network. This message typically uses a structured data format (such as JSON), and its content might look like the following: { "eventType": "LineTrip", "eventTimestamp": "2023-10-27T10:15:30.123Z", "sourceSystem": "SCADA", "eventDetails": { "deviceId": "L521_Guangzhou_to_Shenzhen", "deviceName": "Guangzhou-Shenzhen First Line", "voltageLevel": 500, / / Unit: kV "preFaultLoad": 850, / / Unit: MW "tripReasonCode": "A_PHASE_GROUND_FAULT" } } The execution process of step S201 is as follows: After receiving the above message, the data interface unit of the parameter acquisition module 110 in the information generation device 100 immediately parses it and extracts the value of the eventType field "LineTrip", the value of the eventTimestamp field "2023-10-27T10:15:30.123Z", and various detailed data in the eventDetails object.

[0040] In addition, the parameter acquisition module 110 may also include data conversion and mapping logic to convert the raw data parsed from the message into standard event parameters required by this method. For example: mapping the value of eventType "LineTrip" to the internally defined event type "line trip"; extracting the outage equipment information "Guangzhou-Shenzhen Line A" from the deviceId or deviceName field; directly using the value of the voltageLevel field as the voltage level parameter "500kV"; using the value of the preFaultLoad field "850" as the loss load parameter "850MW"; and converting eventTimestamp into a localized time format and temporarily storing it for later use. Through this series of automatic parsing and conversion, the parameter acquisition module 110 can successfully collect a complete set of event parameters without any manual intervention.

[0041] After this, the process is highly similar to that in Example 1: In steps S202 and S203, the type judgment unit 121 of the event judgment module 120 receives the event type "line trip" and determines that it belongs to the preset accident type that needs to be graded.

[0042] In step S204, the level determination unit 122 is activated and receives parameters such as "voltage level = 500kV" and "load loss = 850MW". This unit performs calculations based on internally fixed judgment rules based on official regulations. For example, the regulations may stipulate that "a 500kV line tripping, causing an interruption of an important transmission line" or "load loss exceeding XXX MW" constitutes a specific level of accident. Assuming that according to these rules, the system determines that this event constitutes a "Level III power safety event".

[0043] In step S205, the template matching module 130 receives the event type "line trip" and the accident level "Level III", and uses this as a composite key to perform precise matching in the template library 200 to obtain a dedicated target information template for "Level III line trip accident".

[0044] In steps S206, S207, and S208, the information generation module 140 automatically fills all the automatically acquired information, including event time, device name, voltage level, and determined accident level, into the placeholders in the template to generate the final dispatch information. Since all information is automatically acquired, this process requires no manual interaction. The generated complete information can be directly displayed on the dispatcher's screen with a "Confirm Send" button, or, under certain highly automated configurations, can even be directly pushed to a designated communication system or alarm platform via an interface.

[0045] Compared to Example 1, this example brings significant benefits through the automated acquisition of event parameters. The response time for information generation is reduced from minutes to seconds, achieving near-instantaneous response. Simultaneously, by eliminating errors potentially introduced by manual input (such as entering the wrong numbers or selecting the wrong options) at the source, the reliability of the information is greatly improved. Understandably, this rapid and accurate information generation capability is of paramount value for emergency power grid incidents requiring time-sensitive handling.

[0046] Example 3 This embodiment aims to illustrate how the technical solution provided in this application processes routine scheduling information that is not related to accidents, thus demonstrating the completeness of its logical judgment and the breadth of its application scenarios. This embodiment will focus on explaining... Figure 2 The "No" branch path in step S203 of the flowchart. The system structure and module functions are basically the same as those described in Example 1.

[0047] In the daily dispatching work of the power grid, in addition to handling sudden accidents and events, dispatchers also need to frequently issue various planned and notification information, such as the commissioning of new equipment, planned power outages and restorations, and the issuance of dispatching instructions. Although these events also require the generation of formatted information, they are not accidents in themselves, and therefore do not require assessment of accident event levels.

[0048] Suppose a dispatcher needs to issue a dispatch message about a newly built 110 kV substation that is about to be put into operation.

[0049] The process also begins with step S201, obtaining event parameters. On the graphical user interface of the information generation device 100, the dispatcher selects "New Equipment Commissioning" from the "Event Type" drop-down menu. Simultaneously, input boxes related to this event type can be displayed on the interface to guide the dispatcher in entering the "Equipment Name" (e.g., "Chengnan 110kV Substation"), "Voltage Level" ("110kV"), and "Planned Commissioning Time" (e.g., "10:00 AM, November 1, 2023").

[0050] Next, in step S202, the event type is determined. The parameter acquisition module 110 passes the user-selected "new equipment put into production" to the type determination unit 121 of the event determination module 120.

[0051] Step S203 is a crucial step in achieving differentiated processing. In this step, the type judgment unit 121 compares its internally maintained list of preset accident types (such as "transmission and transformation equipment failure", "line tripping", etc.) with the current event type "new equipment commissioning". Since "new equipment commissioning" is not in this list, the judgment result is "no".

[0052] according to Figure 2 As shown in the process, when the judgment result of step S203 is "no", the execution of step S204, "automatically determine the accident event level", will be skipped. This means that the level judgment unit 122 in the event judgment module 120 remains inactive in this task, and the system does not perform any calculations or judgments related to the accident level. This design of using differentiated processing paths for events of different natures reflects the logical completeness of this technical solution.

[0053] The process jumps directly to step S205, where the target information template is matched based on the event type and / or accident level. At this point, the only valid matching criterion received by the template matching module 130 from the event judgment module 120 is the event type "New Equipment Commissioning" (accident level information is empty or does not exist). Therefore, the template matching module 130 uses only "New Equipment Commissioning" as the query key to search the template library 200. Assume the template library 200 stores the following templates: "New Equipment Commissioning": "{Date}, {Voltage Level} kV {Equipment Name} is scheduled to be put into operation at {Time}. Relevant units are requested to make preparations and pay attention to safety." Template matching module 130 successfully matched and obtained this template for regular events that does not contain incident level placeholders.

[0054] Subsequently, in steps S206, S207, and S208, the information generation module 140 performs information filling and output. It fills the information such as "equipment name," "voltage level," and "planned commissioning time" entered by the dispatcher in step S201 into the corresponding placeholders in the target information template. The final generated and output complete information is: "On November 1, 2023, the 110kV Chengnan 110kV substation is scheduled to be put into operation at 10:00 AM. Relevant units are requested to make preparations and pay attention to safety." This embodiment clearly demonstrates the flexibility and versatility of the proposed solution. It not only efficiently and accurately processes emergency incident information requiring complex level judgments, but also simplifies and standardizes the generation process of daily dispatch information. By processing all types of dispatch information through a unified platform, dispatchers avoid switching between multiple different tools or template files, further improving overall work efficiency and standardization.

[0055] Example 4 This embodiment provides a more robust and scalable implementation of the template library construction and template matching process, and describes an advanced implementation of the incident level judgment module. This embodiment mainly deepens the internal implementation of the template library 200, the event judgment module 120, and the template matching module 130 in Embodiment 1 to support more complex application scenarios.

[0056] In this embodiment, a more structured approach is provided for constructing the template library 200. For example, instead of a simple in-memory data structure, an information template database is used, which can be a relational database (such as MySQL or PostgreSQL) or a document-oriented database (such as MongoDB). Taking a relational database as an example, a table named `templates` can be designed to store all information templates, and its table structure can be designed as follows: CREATE TABLE templates ( id INT AUTO_INCREMENT PRIMARY KEY, event_type VARCHAR(100) NOT NULL, -- Event type, such as 'line trip' accident_level VARCHAR(50), -- Accident level, such as 'Level IV', can be NULL for non-accident categories. voltage_level_condition VARCHAR(50), -- Voltage level condition, such as '>=220', can be NULL. template_content TEXT NOT NULL,-- Template content priority INT DEFAULT 0 -- Priority, used for selection during fuzzy matching. ); CREATE INDEX idx_match ON templates (event_type, accident_level, voltage_level_condition); In this design, each template is stored as a record, containing explicit indexed fields such as `event_type` and `accident_level`. Other fields, such as `voltage_level_condition`, can be used for more granular matching. Indexing these fields can significantly improve query speed.

[0057] For the level judgment unit 122 in the event judgment module 120, this embodiment introduces a more flexible implementation method, namely, using an independent rule engine unit. This rule engine unit itself does not hardcode any judgment logic, but instead loads an external, independent rule library at runtime. This rule library can be a file (such as a DRL file) or a database table, which defines the judgment rules for all incident events. This design decouples business rules from program logic, allowing for updates to industry regulations where only the rule library needs to be modified without recompiling and deploying the entire application, thus greatly improving the system's maintainability and flexibility.

[0058] Combining the improved structure described above, a more complex processing flow is as follows. Assume a 220 kV line tripping event occurs, and after analysis, it is determined to be a "Level IV" accident.

[0059] The execution process of steps S201 to S204 is similar to that of the aforementioned embodiment, but the internal implementation is different. In step S204, the event judgment module 120 passes the event parameters (event type = 'line trip', voltage level = 220, ...) to its internal rule engine unit. The rule engine unit loads the rule base and takes the parameters as fact input. The engine automatically matches all applicable rules and, based on the definition of the rules, finally derives the accident event level as "Level IV".

[0060] The key improvement is reflected in the template matching process in step S205. After receiving the event type "line trip" and the accident level "Level IV", the template matching module 130 no longer searches in memory, but executes a database query. It can construct a Structured Query Language (SQL) statement to query the information template database: SELECT template_content FROM templates WHERE event_type = 'line trip' AND accident_level = 'Level IV' ORDER BY priority DESC LIMIT 1; The database can quickly locate the record that meets all the conditions using the index and return the corresponding template_content. This method maintains extremely high matching efficiency even when the number of templates reaches tens of thousands.

[0061] Furthermore, this embodiment also provides a backup strategy for when exact matching fails, namely, fallback matching. Suppose that for a rare "Level VI" accident, there is no exact corresponding template for "event_type + accident_level" in the database. When the template matching module 130 executes the query `SELECT ... WHERE event_type = 'accident' AND accident_level = 'Level VI'`, if the returned result set is empty, the module can initiate a secondary query logic, widening the matching range by reducing the query conditions. For example, it can try ignoring the accident level and querying only based on the event type: `SELECT template_content FROM templates WHERE event_type = 'accident' AND accident_level IS NULL ORDER BY priority DESC LIMIT 1;` This query will attempt to find a general template prepared for the "accident" type that does not distinguish between specific levels. If the query succeeds, the system can use this general template to continue generating information, thus ensuring that the system can still provide basic services even when the template configuration is incomplete, enhancing the system's robustness.

[0062] The subsequent information filling and output steps (S206 to S208) are the same as in Example 1. After the information generation module 140 obtains the template, it combines it with other information to complete the filling and output.

[0063] The solution presented in this embodiment makes the power dispatching real-time information generation system highly modular, scalable, and maintainable. The use of a rule engine simplifies and speeds up the updating of the accident level judgment logic, while database-based template management and hierarchical query strategies ensure high performance and high reliability when handling large-scale, complex, and ever-changing template requirements.

[0064] Based on the solutions of the above embodiments, compared with the prior art, this application has the following beneficial effects: 1. Improved the accuracy and relevance of information generation. By first determining the event type and then determining the accident level as needed, and using the combination of event type and accident level to accurately match information templates, it overcomes the shortcomings of existing technologies that rely solely on general diagnostic results, resulting in weak information relevance. This ensures that the generated scheduling information is highly consistent with the specific circumstances of the event. 2. Significantly improved work efficiency by integrating multiple steps that originally required manual judgment, searching, copying, and filling into an automated process, greatly shortening the time for generating dispatch information and allowing dispatchers to focus more on core accident handling tasks. 3. It reduces the workload and pressure on dispatchers. The automated process frees dispatchers from tedious and repetitive information processing work, and can effectively avoid errors caused by distracted operation, especially in emergency situations. 4. Promote the safe and stable operation of the power grid. Through rapid and accurate information transmission, it can ensure that relevant management departments and operation and maintenance units obtain accurate on-site information in the first instance, so as to make timely and correct responses, and provide strong support for ensuring the safe and stable operation of the power grid.

[0065] It is understood that the same or similar parts in the above embodiments can be referred to each other, and the contents not described in detail in some embodiments can be referred to the same or similar contents in other embodiments.

[0066] It should be noted that in the description of this invention, the terms "first," "second," etc., are used for descriptive purposes only and should not be construed as indicating or implying relative importance. Furthermore, in the description of this invention, unless otherwise stated, "a plurality of" means at least two.

[0067] Any process or method description in the flowchart or otherwise herein can be understood as representing a module, segment, or portion of code comprising one or more executable instructions for implementing a particular logical function or process, and the scope of the preferred embodiments of the invention includes additional implementations in which functions may be performed not in the order shown or discussed, including substantially simultaneously or in reverse order depending on the functions involved, as will be understood by those skilled in the art to which embodiments of the invention pertain.

[0068] It should be understood that various parts of the present invention can be implemented in hardware, software, firmware, or a combination thereof. In the above embodiments, multiple steps or methods can be implemented in software or firmware stored in memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, it can be implemented using any one or a combination of the following techniques known in the art: discrete logic circuits having logic gates for implementing logical functions on data signals, application-specific integrated circuits (ASICs) having suitable combinational logic gates, programmable gate arrays (PGAs), field-programmable gate arrays (FPGAs), etc.

[0069] Those skilled in the art will understand that all or part of the steps of the methods described in the above embodiments can be implemented by a program instructing related hardware. The program can be stored in a computer-readable storage medium, and when executed, the program includes one or a combination of the steps of the method embodiments.

[0070] Furthermore, the functional units in the various embodiments of this invention can be integrated into a single processing module, or each unit can exist physically separately, or two or more units can be integrated into a single module. The integrated module can be implemented in hardware or as a software functional module. If the integrated module is implemented as a software functional module and sold or used as an independent product, it can also be stored in a computer-readable storage medium. The aforementioned storage medium can be a read-only memory, a disk, or an optical disk, etc.

[0071] In the description of this specification, references to terms such as "one embodiment," "some embodiments," "example," "specific example," or "some examples," etc., indicate that a specific feature, structure, material, or characteristic described in connection with that embodiment or example is included in at least one embodiment or example of the invention. In this specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples.

[0072] Although embodiments of the present invention have been shown and described above, it is understood that the above embodiments are exemplary and should not be construed as limiting the present invention. Those skilled in the art can make changes, modifications, substitutions and variations to the above embodiments within the scope of the present invention.

Claims

1. A method for generating real-time power grid dispatch information, characterized in that, include: Obtain event parameters related to power safety incidents; Based on the event parameters, the event type of the power safety event is determined, and when the event type is a preset accident type that requires level determination, the accident event level of the power safety event is automatically determined based on the preset accident event judgment rules. Based on the determined event type and the event level determined when the event type is the preset accident type, the target information template is automatically matched and obtained from the preset template library. The determined accident event level and other event information are automatically filled into the target information template to generate real-time scheduling information.

2. The method according to claim 1, characterized in that, The step of obtaining event parameters related to power safety events includes: The event parameters are automatically obtained from the power grid energy management system or monitoring and data acquisition system.

3. The method according to claim 1 or 2, characterized in that, The event parameters include at least one of the following: number of power plants experiencing power outages, voltage level, load loss, outage duration, and equipment experiencing power outages.

4. The method according to claim 1, characterized in that, The step of automatically determining the accident / event level based on preset accident / event judgment rules includes: The event parameters are passed to the rule engine module; The rule engine module loads an independent rule base and matches the rules in the rule base with the event parameters to determine the incident level.

5. The method according to claim 1, characterized in that, The preset accident event judgment rules are set in accordance with the power accident event investigation procedures.

6. The method according to claim 1, characterized in that, The template library is an information template database; The step of automatically matching and obtaining the target information template from the preset template library includes: The event type and the accident event level are used as query conditions to query the information template database to obtain the target information template.

7. The method according to claim 6, characterized in that, If no target information template that completely matches the query conditions is found, a second query is performed by reducing the query conditions to obtain the target information template.

8. The method according to claim 1, characterized in that, The method further includes: Before generating the real-time scheduling information, the event occurrence time is obtained through the user interface, and the event occurrence time is filled into the target information template as part of the other event information.

9. A system for generating real-time information on power grid dispatching, characterized in that, include: The parameter acquisition module is used to acquire event parameters related to power safety incidents; The analysis and judgment module is used to determine the event type of the power safety event based on the event parameters, and when the event type is a preset accident type that requires level judgment, it automatically determines the accident event level of the power safety event based on preset accident event judgment rules. The template matching module is used to automatically match and obtain target information templates from a preset template library based on the determined event type and the event level determined when the event type is the preset accident type. The information generation module is used to automatically fill the determined accident event level and other event information into the target information template to generate real-time scheduling information.

10. The system according to claim 9, characterized in that, The analysis and judgment module includes: A rule engine unit is used to load an independent rule base and match the event parameters with the rules in the rule base to determine the incident event level.

Images