Invoicing method and device based on polymorphic application, electronic device, and storage medium

Abstract

The present invention discloses an invoicing method and device based on polymorphic applications, an electronic device, and a storage medium, which relate to the technical field of intelligent distribution network of power systems or other related fields, wherein the method comprises: temporally dividing a database to obtain a polymorphic application; importing an invoicing model into an operating state application in the polymorphic application; after the model import is completed, synchronizing the application data of the operating state application to the research state application in the polymorphic application; receiving an invoicing instruction, and selecting a target invoicing model used for this invoicing operation based on the invoicing temporal requirements carried by the invoicing instruction; responding to the invoicing instruction, calling the research state application corresponding to the target invoicing model through the target invoicing model to generate a target operation ticket. The present invention solves the technical problem in the related art that due to the lack of isolation between the issuance of the operation ticket and the monitoring of the power grid operation, the state changes of the operating equipment involved in the invoicing action affect the monitoring accuracy, thereby affecting the safety of the power grid operation.

Description

Technical Field

[0001] The present invention relates to the technical field of intelligent distribution networks for power systems, and in particular to a method and device for issuing invoices based on polymorphic applications, an electronic device, and a storage medium. Background Art

[0002] For operations involving changes in the line operating status, an operation ticket must be issued based on the equipment model information and topology after the line operating status is changed before the actual change of the line operating status, as the basis for the actual change operation.

[0003] In the existing technology, the method of manually modifying the content of the operation ticket is time-consuming and prone to errors. In addition, the invoicing process involves changes in the operating status of the equipment, such as switch position changes, which will affect the power operation monitoring and dispatching end's monitoring results of the actual operating status of the power grid. The invoicing method in the existing technology will greatly reduce the dispatcher's work efficiency and the accuracy of power grid operation monitoring, and it is very easy to cause misjudgment or misoperation of the power grid operation status, thereby threatening the safety of power grid operation.

[0004] To address the above-mentioned problems, no effective solutions have been proposed so far. Summary of the Invention

[0005] The embodiments of the present invention provide an invoicing method and device, an electronic device, and a storage medium based on polymorphic applications, so as to at least solve the technical problem in the related art that due to the lack of isolation between the issuance of operation tickets and the monitoring of power grid operation, the changes in the status of the operating equipment involved in the invoicing action affect the monitoring accuracy, thereby affecting the safety of power grid operation.

[0006] According to one aspect of an embodiment of the present invention, an invoicing method based on polymorphic applications is provided, comprising: temporally partitioning a database to obtain polymorphic applications, wherein the polymorphic applications refer to data applications corresponding to various temporal requirements for an invoicing model; importing the invoicing model into a running application in the polymorphic application, wherein the invoicing model comprises a red graph model and a black graph model, and the running application comprises a red graph application and a black graph application; after the model import is completed, synchronizing the application data of the running application to the research application in the polymorphic application, wherein the research application comprises a red graph research application and a black graph research application; receiving an invoicing instruction, and selecting a target invoicing model to be used for this invoicing operation based on the invoicing temporal requirements carried by the invoicing instruction; responding to the invoicing instruction, calling the research application corresponding to the target invoicing model through the target invoicing model to generate a target operation ticket.

[0007] Furthermore, the running state application and the research state application have a one-to-one correspondence, including: the red state application corresponds to the red state application, the black state application corresponds to the black state application, and the database table relationships and database table structures used by the data applications with the corresponding relationships are consistent.

[0008] Furthermore, the step of importing the invoicing model into the running application in the polymorphic application includes: obtaining model import parameters and calling a model import program, wherein the model import parameters include: red map model import parameters and black map model import parameters; inputting the red map model import parameters into the model import program to obtain a red map import program; importing the red map model into the red map state application through the red map import program; inputting the black map model import parameters into the model import program to obtain a black map import program; importing the black map model into the black map state application through the black map import program.

[0009] Furthermore, after the model import is completed, the step of synchronizing the application data of the running application to the research application in the polymorphic application includes: after the model import is completed, based on the preset data synchronization method and corresponding relationship, synchronizing the red image application data to the red image research application, and synchronizing the black image application data to the black image research application, wherein the preset data synchronization method is: one-way data synchronization.

[0010] Furthermore, the invoicing instruction is obtained through the following steps: receiving a graphic click action through an interactive interface to obtain graphic click information, wherein the interactive interface is used to display graphic controls to be selected, each graphic control to be selected corresponds to one of the invoicing models, and the graphic controls to be selected include at least: a red graphic control and a black graphic control; based on the graphic click information, determining the invoicing temporal requirements of the current invoicing operation, and generating the invoicing instruction.

[0011] Furthermore, the step of determining the invoicing temporal requirement of the current invoicing operation based on the graphic click information includes: when the graphic click information indicates that the red graphic control is clicked, determining that the invoicing temporal requirement is a future state; when the graphic click information indicates that the black graphic control is clicked, determining that the invoicing temporal requirement is a real-time state.

[0012] Furthermore, the step of selecting the target invoicing model used for this invoicing operation based on the invoicing temporal requirement carried by the invoicing instruction includes: when the invoicing temporal requirement is in the future state, selecting the red image model as the target invoicing model; or, when the invoicing temporal requirement is in the real-time state, selecting the black image model as the target invoicing model.

[0013] Furthermore, the step of generating a target operation ticket by calling the research state application corresponding to the target invoicing model through the target invoicing model includes: when the target invoicing model is the red map model, calling the red map research state application and obtaining the future state power grid topology information in the red map research state application data; performing a topology check on the future state power grid topology information based on the red map model to obtain a first check result, and generating the target operation ticket based on the first check result; or, when the target invoicing model is the black map model, calling the black map research state application and obtaining the real-time power grid topology information in the black map research state application data; performing a topology check on the real-time power grid topology information based on the black map model to obtain a second check result, and generating the target operation ticket based on the second check result.

[0014] According to another aspect of an embodiment of the present invention, an invoicing device based on a polymorphic application is also provided, comprising: a partitioning unit for temporally partitioning a database to obtain a polymorphic application, wherein the polymorphic application refers to a data application corresponding to multiple temporal requirements for an invoicing model; an importing unit for importing the invoicing model into an operating application in the polymorphic application, wherein the invoicing model comprises a red graph model and a black graph model, and the operating application comprises a red graph application and a black graph application; a synchronization unit for synchronizing the application data of the operating application to the research application in the polymorphic application after the model import is completed, wherein the research application comprises a red graph research application and a black graph research application; a receiving unit for receiving an invoicing instruction, and selecting a target invoicing model to be used for this invoicing operation based on the invoicing temporal requirements carried by the invoicing instruction; a responding unit for responding to the invoicing instruction, calling the research application corresponding to the target invoicing model through the target invoicing model, and generating a target operation ticket.

[0015] Furthermore, the running state application and the research state application have a one-to-one correspondence, including: the red state application corresponds to the red state application, the black state application corresponds to the black state application, and the database table relationships and database table structures used by the data applications with the corresponding relationships are consistent.

[0016] Furthermore, the import unit includes: an acquisition module for acquiring model import parameters and calling a model import program, wherein the model import parameters include: red image model import parameters and black image model import parameters; a first input module for inputting the red image model import parameters into the model import program to obtain a red image import program; a first import module for importing the red image model into the red image state application through the red image import program; a second input module for inputting the black image model import parameters into the model import program to obtain a black image import program; a second import module for importing the black image model into the black image state application through the black image import program.

[0017] Furthermore, the synchronization unit includes: a synchronization module, which is used to synchronize the red image application data to the red image research application, and synchronize the black image application data to the black image research application based on a preset data synchronization method and corresponding relationship after the model import is completed, wherein the preset data synchronization method is: one-way data synchronization.

[0018] Furthermore, the invoicing device based on polymorphic applications also includes: a receiving module, used to receive graphic click actions through an interactive interface to obtain graphic click information, wherein the interactive interface is used to display graphic controls to be selected, each of the graphic controls to be selected corresponds to one of the invoicing models, and the graphic controls to be selected include at least: a red graphic control and a black graphic control; a determination module, used to determine the invoicing temporal requirements of the current invoicing operation based on the graphic click information, and generate the invoicing instruction.

[0019] Furthermore, the determination module includes: a first determination sub-module, used to determine that the invoicing temporal requirement is a future state when the graphic click information indicates that the red image control is clicked; and a second determination sub-module, used to determine that the invoicing temporal requirement is a real-time state when the graphic click information indicates that the black image control is clicked.

[0020] Furthermore, the receiving unit includes: a first selection module, used to select the red graph model as the target invoicing model when the invoicing temporal requirement is in the future state; a second selection module, used to select the black graph model as the target invoicing model when the invoicing temporal requirement is in the real-time state.

[0021] Furthermore, the response unit includes: a first calling module, which is used to call the red map research application and obtain the future power grid topology information in the red map research application data when the target invoicing model is the red map model; a first generating module, which is used to perform a topological check on the future power grid topology information based on the red map model to obtain a first check result, and generate the target operation ticket based on the first check result; a second calling module, which is used to call the black map research application and obtain the real-time power grid topology information in the black map research application data when the target invoicing model is the black map model; a second generating module, which is used to perform a topological check on the real-time power grid topology information based on the black map model to obtain a second check result, and generate the target operation ticket based on the second check result.

[0022] According to another aspect of an embodiment of the present invention, a computer-readable storage medium is further provided, wherein the computer-readable storage medium includes a stored computer program, wherein when the computer program is running, the device where the computer-readable storage medium is located is controlled to execute any of the above-mentioned invoicing methods based on polymorphic applications.

[0023] According to another aspect of an embodiment of the present invention, an electronic device is also provided, comprising one or more processors and a memory, wherein the memory is used to store one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors implement any one of the above-mentioned invoicing methods based on polymorphic applications.

[0024] In the present invention, an invoicing method based on polymorphic applications is proposed, which first performs temporal division on the database to obtain polymorphic applications, wherein the polymorphic applications refer to data applications corresponding to various temporal requirements of the invoicing model, and then imports the invoicing model into the running application in the polymorphic application, wherein the invoicing model includes: a red graph model and a black graph model, and the running application includes: a red graph application and a black graph application. After the model import is completed, the application data of the running application is synchronized to the research application in the polymorphic application, wherein the research application includes: a red graph research application and a black graph research application. Then, the invoicing instruction is received, and the target invoicing model used for this invoicing operation is selected based on the invoicing temporal requirements carried by the invoicing instruction. Finally, the invoicing instruction is responded to, and the research application corresponding to the target invoicing model is called through the target invoicing model to generate a target operation ticket.

[0025] In the present invention, data timeliness is ensured by temporally partitioning the database to generate polymorphic applications. Invoicing can be supported according to different time requirements based on the temporal isolation characteristics of the data application. Invoicing models (red graph model and black graph model) representing different invoicing requirements are imported into the running application, and then the application data of the running application is synchronized to the corresponding research application (red graph research application and black graph research application). This ensures the data validity and invoicing timeliness of the research application used to analyze invoicing. After receiving the invoicing instruction, the appropriate target invoicing model is selected based on the invoicing temporal requirements to call the corresponding research application to generate the target operation ticket, and complete the invoicing operation, thereby ensuring that the invoicing operation and the generated operation ticket meet the requirements, and at the same time will not interfere with the real-time monitoring system.

[0026] Compared with the existing technology, the above steps use polymorphic applications (operational applications and research applications) to isolate the data applications used for invoicing operations and power grid operation monitoring, and limit the operating equipment status changes involved in the invoicing action to the research application, without affecting the operating data in the operation application, and minimize the impact on real-time monitoring, thereby improving the accuracy of monitoring and the safety of power grid operation, and achieving the technical effect of improving the accuracy of invoicing operations and the accuracy of power grid operation monitoring through the hierarchical structure of polymorphic applications, thereby solving the technical problem in the related technology that due to the lack of isolation between operation ticket issuance and power grid operation monitoring, the operating equipment status changes involved in the invoicing action affect the monitoring accuracy, thereby affecting the safety of power grid operation. BRIEF DESCRIPTION OF THE DRAWINGS

[0027] The drawings described herein are used to provide a further understanding of the present invention and constitute a part of this application. The exemplary embodiments of the present invention and their descriptions are used to explain the present invention and do not constitute an improper limitation of the present invention. In the drawings:

[0028] Figure 1 is a flowchart of an optional invoicing method based on polymorphic applications according to an embodiment of the present invention;

[0029] Figure 2 This is a flowchart of an optional red-black graph model invoicing method based on polymorphic applications according to an embodiment of the present invention;

[0030] Figure 3 is a schematic diagram of an optional invoicing device based on polymorphic applications according to an embodiment of the present invention;

[0031] Figure 4 The figure is a hardware structure block diagram of an electronic device (or mobile device) for an invoicing method based on polymorphic applications according to an embodiment of the present invention. DETAILED DESCRIPTION

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

[0033] It should be noted that the terms "first", "second", etc. in the description and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that the numbers used in this way can be interchanged where appropriate, so that the embodiments of the present invention described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0034] The following embodiments of the present invention can be applied to various systems / applications / devices that require red and black graph model invoicing, and can implement red and black graph model invoicing based on polymorphic applications, ensuring that the invoicing operation and the generated operation ticket meet the requirements while not interfering with the accuracy of the real-time monitoring system. The present invention generates polymorphic applications by temporally partitioning the database, and then imports the invoicing models (red graph model and black graph model) representing different invoicing requirements into the running state application, and synchronizes the application data of the running state application to the corresponding research state application (red graph research state application and black graph research state application). After receiving the invoicing instruction, the appropriate target invoicing model is selected based on the invoicing temporal requirements to call the corresponding research state application to generate the target operation ticket.

[0035] The present invention utilizes polymorphic applications (operational applications and research applications) to isolate the data applications used for billing operations and grid operation monitoring, thereby limiting the state changes of operating equipment involved in billing actions to research applications, without affecting the operating data in the operation application, and minimizing the impact on real-time monitoring.

[0036] The present invention will be described in detail below with reference to various embodiments.

[0037] Example 1

[0038] According to an embodiment of the present invention, an embodiment of an invoicing method based on a polymorphic application is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0039] Figure 1 is a flow chart of an optional invoicing method based on polymorphic applications according to an embodiment of the present invention. Figure 1 As shown, the method includes the following steps:

[0040] Step S101 , temporally partitioning the database to obtain polymorphic applications, wherein the polymorphic applications refer to data applications corresponding to various temporal requirements of the invoicing model.

[0041] Step S102: import the invoicing model into the running state application in the polymorphic application, wherein the invoicing model includes: a red graph model and a black graph model, and the running state application includes: a red graph application and a black graph application.

[0042] Step S103: after the model is imported, the application data of the running application is synchronized to the research application in the multi-state application, wherein the research application includes: a red-image research application and a black-image research application.

[0043] Step S104: receiving an invoicing instruction, and selecting a target invoicing model used for this invoicing operation based on the invoicing temporal requirements carried in the invoicing instruction.

[0044] Step S105 , responding to the invoicing instruction, calling the research application corresponding to the target invoicing model through the target invoicing model to generate a target operation ticket.

[0045] Through the above steps, the database can be temporally divided first to obtain polymorphic applications, wherein polymorphic applications refer to data applications corresponding to various temporal requirements for the invoicing model, and then the invoicing model is imported into the running application in the polymorphic application, wherein the invoicing model includes: red graph model and black graph model, and the running application includes: red graph application and black graph application. After the model import is completed, the application data of the running application is synchronized to the research application in the polymorphic application, wherein the research application includes: red graph research application and black graph research application, and then the invoicing instruction is received, and the target invoicing model used for this invoicing operation is selected based on the invoicing temporal requirements carried by the invoicing instruction, and finally the invoicing instruction is responded to, and the research application corresponding to the target invoicing model is called through the target invoicing model to generate the target operation ticket.

[0046] In an embodiment of the present invention, data timeliness is ensured by temporally partitioning the database to generate polymorphic applications. The temporal isolation characteristics of the data application can support invoicing processing according to different time requirements. The invoicing models (red graph model and black graph model) representing different invoicing requirements are imported into the running application, and then the application data of the running application is synchronized to the corresponding research application (red graph research application and black graph research application). This ensures the data validity and invoicing timeliness of the research application used to analyze invoicing. After receiving the invoicing instruction, the appropriate target invoicing model is selected based on the invoicing temporal requirements to call the corresponding research application to generate the target operation ticket, and complete the invoicing operation, thereby ensuring that the invoicing operation and the generated operation ticket meet the requirements and will not interfere with the real-time monitoring system.

[0047] Compared with the existing technology, the above steps use polymorphic applications (operational applications and research applications) to isolate the data applications used for invoicing operations and power grid operation monitoring, and limit the operating equipment status changes involved in the invoicing action to the research application, without affecting the operating data in the operation application, and minimize the impact on real-time monitoring, thereby improving the accuracy of monitoring and the safety of power grid operation, and achieving the technical effect of improving the accuracy of invoicing operations and the accuracy of power grid operation monitoring through the hierarchical structure of polymorphic applications, thereby solving the technical problem in the related technology that due to the lack of isolation between operation ticket issuance and power grid operation monitoring, the operating equipment status changes involved in the invoicing action affect the monitoring accuracy, thereby affecting the safety of power grid operation.

[0048] The embodiment of the present invention is described in detail below in conjunction with the above steps.

[0049] The implementing entity of the embodiment of the present invention can be the power system distribution network system, or the power system operation and maintenance center, the distribution network system dispatching center, combined with the polymorphic application obtained after the temporal division of the database, uses different import parameters to import the red map model and the black map model into the corresponding polymorphic application respectively, so as to realize the storage of the red map model data and the black map model data in the database in separate applications, and synchronize the model data of the red map state and the black map state in one direction to the red map research state application and the black map research state application respectively, so as to facilitate the implementing entity to flexibly select the data application when issuing invoices based on the invoicing model and flexibly switch the invoicing mode.

[0050] Step S101 , performing temporal division on the database to obtain polymorphic applications.

[0051] It should be noted that in the field of smart power distribution networks, dividing a database into different temporal applications typically refers to storing and managing data based on the time dimension. For example, real-time data, historical data, and forecast data are stored and processed separately to optimize data access and improve system performance.

[0052] The polymorphic application in the embodiment of the present invention refers to a data application corresponding to various temporal requirements of the invoicing model. The types of polymorphic applications include at least: running state applications and research state applications, which correspond to the two invoicing models used in the present invention: the red graph model and the black graph model. The above-mentioned running state applications include at least: red graph state applications and black graph state applications. Corresponding to the running state applications, the above-mentioned research state applications include at least: red graph research state applications and black graph research state applications.

[0053] It should be noted that in the power system, black-image applications and red-image applications refer to different modes of monitoring and management of power grid operation. Black-image applications focus on the real-time power grid operation mode and current real-time data (such as the latest power load, power generation, voltage, current, equipment status, etc.), involving real-time monitoring and fault detection, with an emphasis on immediate analysis of the current operating status. Red-image applications focus on the future state of power grid operation. In addition to real-time data, they usually pay additional attention to historical data, trend analysis, forecast data, and records of abnormal events, involving abnormal states or early warnings, with a focus on handling emergencies or potential system risks.

[0054] In the existing technology, the red graph application is called when the red graph model is used as the invoicing model to issue an operation ticket, and the black graph application is called when the black graph model is used as the invoicing model to issue an operation ticket. Data isolation is implemented in the database to ensure that the real-time monitoring system and the fault warning system independently process the required data, avoid data conflicts and impacts, and ensure a certain level of data access efficiency and application reliability.

[0055] However, the processing methods in the existing technology are not perfect enough. Changes in the equipment status during the invoicing process (such as equipment start and stop, switching, load adjustment, and switch position change, etc.) may cause data errors in the red and black diagram application, resulting in reduced accuracy of other tasks supported by the red and black diagram application (such as real-time monitoring and fault analysis), and even lead to misjudgment and erroneous operation of the power system operation status, threatening the security of the power grid.

[0056] The concepts of running state applications and research state applications are proposed in the embodiment of the present invention. Through data copying / data mirroring, red-image research state applications and black-image research state applications are established, which are specifically used for invoicing operations, isolating the invoicing operations from other power grid operations and eliminating their mutual influence.

[0057] Optionally, there is a one-to-one correspondence between the running state application and the research state application, including: the red state application corresponds to the red state application, the black state application corresponds to the black state application, and the database table relationships and database table structures used by the corresponding data applications are consistent. Specifically, the database table relationships and table structures of the red state application and the red state application are consistent, and the database table relationships and table structures of the black state application and the black state application are consistent.

[0058] Step S102: import the invoicing model into the running state application in the polymorphic application, wherein the invoicing model includes: a red graph model and a black graph model, and the running state application includes: a red graph application and a black graph application.

[0059] Specifically, in the scenario of issuing operation tickets, the red chart model and the black chart model have the following differences:

[0060] The Red Chart model is used to plan and predict future grid states, helping to formulate future grid operation plans and operational strategies to address anticipated load changes and system expansion. Operation tickets issued based on the Red Chart model typically involve forecasting and planning future grid states, including adjustments to future system configurations, load management, and possible equipment upgrades or changes.

[0061] The black graph model is used for real-time power grid monitoring and management, providing information on the current grid status for real-time operations and fault handling. Operation tickets issued based on the black graph model involve the implementation of real-time operations, such as real-time equipment adjustment, fault handling, load scheduling, etc. These operation tickets need to quickly respond to the actual operation of the power grid to ensure the stability and security of the system.

[0062] Optionally, step S102 includes: obtaining model import parameters and calling a model import program, wherein the model import parameters include: red map model import parameters and black map model import parameters; inputting the red map model import parameters into the model import program to obtain a red map import program; importing the red map model into a red map application through the red map import program; inputting the black map model import parameters into the model import program to obtain a black map import program; importing the black map model into a black map application through the black map import program.

[0063] In the embodiment of the present invention, detailed import parameters are usually obtained from the model specification document or the model user manual, and the import of the red map model and the black map model is processed separately through the import parameters dedicated to each model (red map and black map), thereby reducing the probability of errors and conflicts, improving the import efficiency and accuracy, and enabling the dispatching center to adapt to various temporal requirements and improve the flexibility and applicability of the power system.

[0064] Step S103: after the model is imported, the application data of the running application is synchronized to the research application in the multi-state application, wherein the research application includes: a red-image research application and a black-image research application.

[0065] Optionally, step S103 includes: after the model import is completed, based on the preset data synchronization method and corresponding relationship, synchronizing the red map application data to the red map research application, and synchronizing the black map application data to the black map research application, wherein the preset data synchronization method is: one-way data synchronization.

[0066] The purpose of data synchronization in the embodiment of the present invention is to copy the current operating information in the running application to the research application, so as to facilitate the issuance of operation tickets for the power grid (equipment) in the research application. The reason for choosing one-way synchronization is to ensure that data can be synchronized from the running application to the research application to ensure the accuracy and availability of invoicing, but data cannot be updated reversely from the research application to the running application to avoid the displacement data in the invoicing process affecting the source data.

[0067] In an optional embodiment, in the data synchronization operation after the model import is completed, the preset data synchronization method can also be: automated one-way data synchronization, which can reduce the workload of manual intervention and data migration, thereby improving operational efficiency and accuracy.

[0068] Step S104: receiving an invoicing instruction, and selecting a target invoicing model used for this invoicing operation based on the invoicing temporal requirements carried in the invoicing instruction.

[0069] In order to improve the operational efficiency and accuracy of users (i.e., dispatchers), the interaction between users and the dispatching system can be simplified through interactive interfaces and graphic controls, so that users can intuitively select the required invoicing model. Optionally, the invoicing instruction is obtained through the following steps: receiving a graphic click action through the interactive interface to obtain graphic click information, wherein the interactive interface is used to display the graphic controls to be selected, each graphic control to be selected corresponds to an invoicing model, and the graphic controls to be selected include at least: a red graphic control and a black graphic control; based on the graphic click information, the invoicing temporal requirements of this invoicing operation are determined, and an invoicing instruction is generated.

[0070] The embodiment of the present invention automates the process of generating invoicing instructions by clicking on graphics, reduces the possibility of manual input and errors, and improves operational efficiency and accuracy.

[0071] Optionally, the step of determining the invoicing temporal requirement for the current invoicing operation based on the graphic click information includes: if the graphic click information indicates that a red graphic control was clicked, determining the invoicing temporal requirement as a future state; if the graphic click information indicates that a black graphic control was clicked, determining the invoicing temporal requirement as a real-time state. Through clear control mapping, the system can accurately determine the temporal state of invoicing requirements, adapting to different business scenarios and ensuring that invoicing operations meet actual user needs. By using graphic clicks rather than manually entering temporal requirements, the possibility of input errors is reduced, thereby improving the accuracy of invoicing operations.

[0072] In order to select a suitable invoicing model, optionally, the step of selecting the target invoicing model used for this invoicing operation based on the invoicing temporal requirement carried by the invoicing instruction in step S104 includes: when the invoicing temporal requirement is future state, selecting the red graph model as the target invoicing model; or, when the invoicing temporal requirement is real-time state, selecting the black graph model as the target invoicing model.

[0073] The embodiment of the present invention ensures that the system can efficiently handle different types of invoicing requirements by selecting the appropriate invoicing model (red chart model or black chart model) based on the invoicing temporal requirements (future state or real-time state). This selection mechanism not only improves the adaptability and processing efficiency of the system, but also simplifies user operations, supports multiple business scenarios, and reduces operational errors.

[0074] Step S105 , responding to the invoicing instruction, calling the research application corresponding to the target invoicing model through the target invoicing model to generate a target operation ticket.

[0075] Optionally, in step S105, the step of calling the research state application corresponding to the target invoicing model through the target invoicing model to generate a target operation ticket includes: when the target invoicing model is a red map model, calling the red map research state application and obtaining the future state power grid topology information in the red map research state application data; performing a topology check on the future state power grid topology information based on the red map model to obtain a first check result, and generating the target operation ticket based on the first check result; or, when the target invoicing model is a black map model, calling the black map research state application and obtaining the real-time power grid topology information in the black map research state application data; performing a topology check on the real-time power grid topology information based on the black map model to obtain a second check result, and generating the target operation ticket based on the second check result.

[0076] In the embodiment of the present invention, topology verification is used to ensure that the structure of the power grid meets the operating standards in the future or at the current moment, thereby avoiding potential errors and risks; verification is used to prevent structural problems that may cause accidents in the future or current power grid state, thereby ensuring the stability and safety of the power grid; verification can also ensure that the operation of the power grid complies with the prescribed technical standards and business processes, thereby avoiding compliance issues caused by improper operation.

[0077] Specifically, the first verification result refers to the verification result of the red map model based on the topology data of the future power grid, including whether it meets the standards and safety requirements of future plans; the second verification result refers to the verification result of the black map model based on the topology data of the real-time power grid, including whether it meets the standards and safety requirements of current operations.

[0078] If and only if the first or second verification result meets the requirements, a target operation ticket will be generated, and the generated target operation ticket includes the verified data and decision, indicating the specific operation or modification that can be performed. The present invention will be described below in conjunction with another specific embodiment.

[0079] The embodiments of the present invention propose a red-black graph model invoicing method based on polymorphic applications. This method divides the power monitoring system into multiple temporal applications, including red graph state, red graph research state, black graph state, and black graph research state. The red graph model and the black graph model use different import parameters to implement application-specific storage of red graph model data and black graph model data in the database. The red graph model data and the black graph model data are automatically copied to the red graph research state and the black graph research state, respectively. Based on the embodiments of the present invention, dispatchers can flexibly switch invoicing modes by manually switching graphic applications.

[0080] Figure 2 This is a flowchart of an optional red-black graph model invoicing method based on polymorphic application according to an embodiment of the present invention. Figure 2 As shown, the method includes the following steps:

[0081] S1 polymorphic application partitioning;

[0082] S2 model import;

[0083] S3 model data copy;

[0084] S4 graphics application selection;

[0085] S5 operation ticket generation.

[0086] The polymorphic application partitioning step in S1 primarily involves dividing the database storing model data into different temporal applications. The resulting polymorphic applications include: Red Graph Application, Red Graph Research Application, Black Graph Application, and Black Graph Research Application. The database table relationships and table structures between these different data applications must remain consistent.

[0087] Regarding the model import step in S2, the embodiment of the present invention uses different model startup parameters to start the model import program to distinguish the red map model from the black map model, and then imports the invoicing model into the corresponding red map application and black map application in the database respectively.

[0088] Regarding the model data copying step in S3, after the model import is completed in S2, the red image application data and the black image application data are automatically copied to the red image research application and the black image research application respectively.

[0089] Data synchronization between the Red Image State App and the Red Image Research State App, and between the Black Image State App and the Black Image Research State App, is one-way. That is, any data changes in the Red Image State App and the Black Image State App will be synchronized to the Red Image Research State App and the Black Image Research State App, but any data changes in the Red Image Research State App and the Black Image Research State App will not be synchronized to the Red Image State App and the Black Image App.

[0090] The above-mentioned one-way synchronous data synchronization method ensures that the dispatching center obtains correct model information when using the research application to perform invoicing operations, while also ensuring that operations such as switch changes caused by the invoicing operation will not affect the dispatching center's monitoring accuracy of the actual operating status of the power grid equipment.

[0091] Regarding the graphic application selection step in S4, the dispatching center is supported to select the grid operation mode by switching the graphic application on the graphic control provided by the interactive interface, and to choose to issue invoices for the red or black graph.

[0092] Regarding the operation ticket generation step in S5, when the dispatching center issues the ticket, it automatically performs topology verification on the power grid / system topology diagram corresponding to the different power grid operation modes represented by the black graph research state application and the red graph research state application based on the graphic application selection result in S4.

[0093] The embodiment of the present invention also supports the selection of traditional point-to-picture ticket issuance method or intelligent ticket issuance method to generate operation tickets. The generated operation tickets include the following contents: operation task, operation steps, serial number, order-receiving unit, and operation content.

[0094] The beneficial effects brought about by the embodiments of the present invention are that the proposed red-black graph model invoicing method based on polymorphic applications expands the database structure hierarchy, divides the model data information through multiple temporal applications, and realizes different invoicing methods based on polymorphic applications calling the red-black graph model, which provides more options for scheduling invoicing while reducing the scheduling workload and improving the safety of power grid operation.

[0095] The present invention is described below in conjunction with another optional embodiment.

[0096] Example 2

[0097] The invoicing device based on polymorphic applications provided in this embodiment includes multiple implementation units, each of which corresponds to each implementation step in the above-mentioned embodiment 1.

[0098] Figure 3 is a schematic diagram of an optional invoicing device based on polymorphic applications according to an embodiment of the present invention, such as Figure 3 As shown, the device may include: a dividing unit 31, an importing unit 32, a synchronization unit 33, a receiving unit 34, and a responding unit 35.

[0099] The partitioning unit 31 is used to perform temporal partitioning on the database to obtain polymorphic applications, wherein the polymorphic applications refer to data applications corresponding to various temporal requirements of the invoicing model.

[0100] The importing unit 32 is used to import the invoicing model into the running state application in the polymorphic application, wherein the invoicing model includes: a red graph model and a black graph model, and the running state application includes: a red graph state application and a black graph state application.

[0101] The synchronization unit 33 is used to synchronize the application data of the running state application to the research state application in the multi-state application after the model import is completed, wherein the research state application includes: a red-map research state application and a black-map research state application.

[0102] The receiving unit 34 is configured to receive an invoicing instruction and select a target invoicing model to be used in this invoicing operation based on the invoicing temporal requirement carried in the invoicing instruction.

[0103] The response unit 35 is used to respond to the invoicing instruction, call the research application corresponding to the target invoicing model through the target invoicing model, and generate a target operation ticket.

[0104] The above-mentioned invoicing device based on polymorphic application can first perform temporal division on the database through the division unit 31 to obtain polymorphic application, wherein the polymorphic application refers to the data application corresponding to the various temporal requirements of the invoicing model, and then import the invoicing model into the running application in the polymorphic application through the import unit 32, wherein the invoicing model includes: red graph model and black graph model, and the running application includes: red graph application and black graph application. After the model import is completed, the application data of the running application is synchronized to the research application in the polymorphic application through the synchronization unit 33, wherein the research application includes: red graph research application and black graph research application, and then receive the invoicing instruction through the receiving unit 34, and select the target invoicing model used for this invoicing operation based on the invoicing temporal requirements carried by the invoicing instruction, and finally respond to the invoicing instruction through the response unit 35, call the research application corresponding to the target invoicing model through the target invoicing model, and generate the target operation ticket.

[0105] In an embodiment of the present invention, data timeliness is ensured by temporally partitioning the database to generate polymorphic applications. The temporal isolation characteristics of the data application can support invoicing processing according to different time requirements. The invoicing models (red graph model and black graph model) representing different invoicing requirements are imported into the running application, and then the application data of the running application is synchronized to the corresponding research application (red graph research application and black graph research application). This ensures the data validity and invoicing timeliness of the research application used to analyze invoicing. After receiving the invoicing instruction, the appropriate target invoicing model is selected based on the invoicing temporal requirements to call the corresponding research application to generate the target operation ticket, and complete the invoicing operation, thereby ensuring that the invoicing operation and the generated operation ticket meet the requirements and will not interfere with the real-time monitoring system.

[0106] Compared with the existing technology, the above steps use polymorphic applications (operational applications and research applications) to isolate the data applications used for invoicing operations and power grid operation monitoring, and limit the operating equipment status changes involved in the invoicing action to the research application, without affecting the operating data in the operation application, and minimize the impact on real-time monitoring, thereby improving the accuracy of monitoring and the safety of power grid operation, and achieving the technical effect of improving the accuracy of invoicing operations and the accuracy of power grid operation monitoring through the hierarchical structure of polymorphic applications, thereby solving the technical problem in the related technology that due to the lack of isolation between operation ticket issuance and power grid operation monitoring, the operating equipment status changes involved in the invoicing action affect the monitoring accuracy, thereby affecting the safety of power grid operation.

[0107] Optionally, the running state application and the research state application have a one-to-one correspondence, including: the red state application corresponds to the red state research state application, the black state application corresponds to the black state research state application, and the database table relationships and database table structures used by the corresponding data applications are consistent.

[0108] Optionally, the import unit includes: an acquisition module for acquiring model import parameters and calling a model import program, wherein the model import parameters include: red image model import parameters and black image model import parameters; a first input module for inputting the red image model import parameters into the model import program to obtain a red image import program; a first import module for importing the red image model into a red image state application through the red image import program; a second input module for inputting the black image model import parameters into the model import program to obtain a black image import program; a second import module for importing the black image model into a black image state application through the black image import program.

[0109] Optionally, the synchronization unit includes: a synchronization module, which is used to synchronize the red image application data to the red image research application, and synchronize the black image application data to the black image research application based on the preset data synchronization method and corresponding relationship after the model import is completed, wherein the preset data synchronization method is: one-way data synchronization.

[0110] Optionally, the invoicing device based on polymorphic applications also includes: a receiving module, used to receive graphic click actions through an interactive interface to obtain graphic click information, wherein the interactive interface is used to display graphic controls to be selected, each graphic control to be selected corresponds to an invoicing model, and the graphic controls to be selected include at least: a red graphic control and a black graphic control; a determination module, used to determine the invoicing temporal requirements of this invoicing operation based on the graphic click information, and generate an invoicing instruction.

[0111] Optionally, the determination module includes: a first determination submodule, used to determine that the invoicing temporal requirement is a future state when the graphic click information indicates that the red graphic control is clicked; and a second determination submodule, used to determine that the invoicing temporal requirement is a real-time state when the graphic click information indicates that the black graphic control is clicked.

[0112] Optionally, the receiving unit includes: a first selection module for selecting the red graph model as the target invoicing model when the invoicing temporal requirement is in the future state; a second selection module for selecting the black graph model as the target invoicing model when the invoicing temporal requirement is in the real-time state.

[0113] Optionally, the response unit includes: a first calling module, which is used to call the red map research application and obtain the future power grid topology information in the red map research application data when the target invoicing model is the red map model; a first generating module, which is used to perform topology verification on the future power grid topology information based on the red map model to obtain a first verification result, and generate a target operation ticket based on the first verification result; a second calling module, which is used to call the black map research application and obtain the real-time power grid topology information in the black map research application data when the target invoicing model is the black map model; a second generating module, which is used to perform topology verification on the real-time power grid topology information based on the black map model to obtain a second verification result, and generate a target operation ticket based on the second verification result.

[0114] The above-mentioned invoicing device based on polymorphic applications may also include a processor and a memory. The above-mentioned division unit 31, import unit 32, synchronization unit 33, receiving unit 34, response unit 35, etc. are all stored in the memory as program units, and the processor executes the above-mentioned program units stored in the memory to realize the corresponding functions.

[0115] The processor includes a kernel, which retrieves the corresponding program unit from memory. One or more kernels can be configured, and kernel parameters are adjusted to respond to invoicing instructions. The target invoicing model then calls the corresponding research application to generate the target operation ticket.

[0116] The above-mentioned memory may include non-permanent memory in a computer-readable medium, random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM, and the memory includes at least one memory chip.

[0117] The present application also provides a computer program product, which, when executed on a data processing device, is suitable for executing a program initialized with the following method steps: temporally dividing the database to obtain polymorphic applications, wherein the polymorphic applications refer to data applications corresponding to various temporal requirements for the invoicing model; importing the invoicing model into the running application in the polymorphic application, wherein the invoicing model includes: a red graph model and a black graph model, and the running application includes: a red graph application and a black graph application; after the model import is completed, synchronizing the application data of the running application to the research application in the polymorphic application, wherein the research application includes: a red graph research application and a black graph research application; receiving an invoicing instruction, and selecting the target invoicing model used for this invoicing operation based on the invoicing temporal requirements carried by the invoicing instruction; responding to the invoicing instruction, calling the research application corresponding to the target invoicing model through the target invoicing model, and generating a target operation ticket.

[0118] According to another aspect of an embodiment of the present invention, a computer-readable storage medium is further provided, which includes a stored computer program, wherein when the computer program is running, the device where the computer-readable storage medium is located is controlled to execute the invoicing method based on polymorphic applications of any one of the above-mentioned embodiments.

[0119] According to another aspect of an embodiment of the present invention, an electronic device is also provided, comprising one or more processors and a memory, wherein the memory is used to store one or more programs, wherein when the one or more programs are executed by one or more processors, the one or more processors implement the polymorphic application-based invoicing method of any one of the above-mentioned embodiments.

[0120] Figure 4 FIG is a hardware structure block diagram of an electronic device (or mobile device) for an invoicing method based on polymorphic applications according to an embodiment of the present invention. Figure 4 As shown, the electronic device may include one or more ( Figure 4(As shown in the figure, 402a, 402b, ..., 402n are used) processor 402 (processor 402 may include but is not limited to a processing device such as a microprocessor MCU or a programmable logic device FPGA), memory 404 for storing data. In addition, it may also include: a display, an input / output interface (I / O interface), a universal serial bus (USB) port (which may be included as one of the ports of the I / O interface), a network interface, a keyboard, a power supply and / or a camera. It will be understood by those skilled in the art that Figure 4 The structure shown is only for illustration and does not limit the structure of the above electronic device. Figure 4 More or fewer components than shown, or with Figure 4 Different configurations shown.

[0121] The serial numbers of the above embodiments of the present invention are for description only and do not represent the advantages or disadvantages of the embodiments.

[0122] In the above embodiments of the present invention, the description of each embodiment has its own focus. For parts that are not described in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0123] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. Among them, the device embodiments described above are only exemplary. For example, the division of the units can be a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of units or modules, which can be electrical or other forms.

[0124] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple units. Some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.

[0125] In addition, the functional units in the various embodiments of the present invention may be integrated into a single processing unit, each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.

[0126] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, server or network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present invention. The aforementioned storage medium includes: U disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), mobile hard disk, magnetic disk or optical disk, etc. Various media that can store program codes.

[0127] The above is only a preferred embodiment of the present invention. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present invention. These improvements and modifications should also be regarded as within the scope of protection of the present invention.

Claims

1. A billing method based on polymorphic application, characterized in that: include: Temporally partition the database to obtain polymorphic applications, where the polymorphic applications refer to data applications corresponding to various temporal requirements of the invoicing model; Importing the invoicing model into a running-state application in the polymorphic application, wherein the invoicing model includes a red-graph model and a black-graph model, and the running-state application includes a red-graph application and a black-graph application; After the model is imported, the application data of the running state application is synchronized to the research state application in the polymorphic application, wherein the research state application includes: a red map research state application and a black map research state application; receiving an invoicing instruction and selecting a target invoicing model for the current invoicing operation based on an invoicing temporal requirement carried in the invoicing instruction, including: selecting the red graph model as the target invoicing model when the invoicing temporal requirement is future, or selecting the black graph model as the target invoicing model when the invoicing temporal requirement is real-time; In response to the invoicing instruction, the research state application corresponding to the target invoicing model is called through the target invoicing model to generate a target operation ticket, including: when the target invoicing model is the red map model, calling the red map research state application and obtaining the future state power grid topology information in the red map research state application data; performing a topology check on the future state power grid topology information based on the red map model to obtain a first check result, and generating the target operation ticket based on the first check result; or, when the target invoicing model is the black map model, calling the black map research state application and obtaining the real-time power grid topology information in the black map research state application data; performing a topology check on the real-time power grid topology information based on the black map model to obtain a second check result, and generating the target operation ticket based on the second check result.

2. The invoicing method according to claim 1, characterized in that: The running state application and the research state application have a one-to-one correspondence, including: the red state application corresponds to the red state application, the black state application corresponds to the black state application, and the database table relationships and structures used by the data applications with the corresponding relationships are consistent.

3. The invoicing method according to claim 1, characterized in that: The step of importing the invoicing model into the running application in the polymorphic application includes: Obtain model import parameters and call a model import program, wherein the model import parameters include: red map model import parameters and black map model import parameters; Inputting the red map model import parameters into the model import program to obtain the red map import program; Importing the red map model into the red map state application through the red map import program; Inputting the black image model import parameters into the model import program to obtain a black image import program; The black image model is imported into the black image application through the black image import program.

4. The invoicing method according to claim 1, characterized in that: After the model is imported, the step of synchronizing the application data of the running application to the research application in the polymorphic application includes: After the model import is completed, based on the preset data synchronization method and corresponding relationship, the red map application data is synchronized to the red map research application, and the black map application data is synchronized to the black map research application, wherein the preset data synchronization method is: one-way data synchronization.

5. The invoicing method according to claim 1, characterized in that: The invoicing instruction is obtained through the following steps: Receiving a graphic click action through an interactive interface to obtain graphic click information, wherein the interactive interface is used to display graphic controls to be selected, each of the graphic controls to be selected corresponds to one of the invoicing models, and the graphic controls to be selected include at least a red graphic control and a black graphic control; The invoicing temporal requirement of the current invoicing operation is determined based on the graphic click information, and the invoicing instruction is generated.

6. The invoicing method according to claim 5, characterized in that: The step of determining the invoicing temporal requirement of the current invoicing operation based on the graphic click information includes: When the graphic click information indicates that the red graphic control is clicked, determining that the invoicing temporal requirement is a future temporal requirement; When the graphic click information indicates that the black graphic control is clicked, it is determined that the invoicing temporal requirement is real-time.

7. A billing device based on polymorphic application, characterized in that: include: A partitioning unit, configured to perform temporal partitioning on the database to obtain polymorphic applications, wherein the polymorphic applications refer to data applications corresponding to various temporal requirements of the invoicing model; An importing unit, configured to import the invoicing model into a running-state application in the polymorphic application, wherein the invoicing model includes a red-graph model and a black-graph model, and the running-state application includes a red-graph application and a black-graph application; A synchronization unit, configured to synchronize the application data of the running application to the research application in the polymorphic application after the model import is completed, wherein the research application includes: a red-image research application and a black-image research application; a receiving unit, configured to receive an invoicing instruction and select a target invoicing model to be used for the current invoicing operation based on an invoicing temporal requirement carried in the invoicing instruction, including: selecting the red graph model as the target invoicing model when the invoicing temporal requirement is future, or selecting the black graph model as the target invoicing model when the invoicing temporal requirement is real-time; A response unit is used to respond to the invoicing instruction, call the research state application corresponding to the target invoicing model through the target invoicing model, and generate a target operation ticket, including: when the target invoicing model is the red map model, call the red map research state application and obtain the future state power grid topology information in the red map research state application data; perform a topology check on the future state power grid topology information based on the red map model to obtain a first check result, and generate the target operation ticket based on the first check result; or, when the target invoicing model is the black map model, call the black map research state application and obtain the real-time power grid topology information in the black map research state application data; perform a topology check on the real-time power grid topology information based on the black map model to obtain a second check result, and generate the target operation ticket based on the second check result.

8. An electronic device, characterized in that: It includes one or more processors and a memory, wherein the memory is used to store one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors implement the invoicing method based on polymorphic applications as described in any one of claims 1 to 6.

Images