Method and System for Web Publishing of Operation Tickets in Centralized Control Stations Based on Microservice Architecture

Abstract

The present invention proposes an operating ticket Web publishing method for a centralized control station system based on a microservice architecture, which uses a method based on database synchronization to replace the synchronization of operating ticket files. When the status of the operating ticket changes, only the data volume of one field needs to be synchronized, improving the efficiency of data transmission. An online configuration tool based on Web is developed in Zone IV. According to the user's requirements, the display style of the operating ticket is edited online using the configuration tool, and then an intermediate file in xml format is formed. The operating ticket Web publishing function module obtains the operating ticket information from the database and then generates an operating ticket file in a specific format and style according to the xml file. In this way, the operating ticket Web publishing module only depends on the intermediate template file, and changes in styles and formats do not require re-coding, improving the user experience.

Description

Technical Field

[0001] The present invention relates to the field of power systems, and in particular to a method and system for publishing operation tickets of centralized control stations on the Web based on a microservice architecture. Background Art

[0002] In the field of power systems, the intelligent monitoring system of centralized control station equipment is an automated system established between the dispatching system and the substation to centrally monitor and manage multiple unmanned substations. The Web publishing of operation tickets is an important functional module in the centralized control station system. It mainly publishes the operation tickets in Area I to Area IV in real time through Web publishing, so that users can browse the system's operation ticket information in Area IV through the Web. At the same time, users can also perform operations such as information backfilling and archiving on the operation tickets in Area IV, realizing real-time synchronization of the operation ticket information in Area I and Area IV, and meeting the needs of real-time circulation of the operation ticket information of the centralized control station system in Area I and Area IV.

[0003] The current implementation scheme for Web publishing of operation tickets of the centralized control station system is as follows: the operation ticket information is formed into a file in Area I, and then the operation ticket file is synchronized to Area IV through the forward and reverse isolation devices; the application in Area IV parses the operation ticket file through the file format agreed upon with Area I, and then displays it in a specific format on the Web page; the implementation of the archiving function depends on the file format agreed upon by Areas I / IV, and the application in Area IV forms a document in a specific format based on the file format agreed upon with Area I.

[0004] The above implementation scheme has the problems of low efficiency and waste of bandwidth resources during data synchronization. The operation ticket needs to go through multiple operations in Area I, and each operation needs to update the operation ticket file, and then synchronize the entire file to Area IV. A change in status also requires synchronization of the entire operation ticket file, resulting in a huge waste of bandwidth resources; in terms of operation ticket display, the Area IV application is completely dependent on the file format agreed upon by Areas I / IV. When the user modifies the display method of the operation ticket, the function module related to the operation ticket release needs to be recoded, resulting in the instability of the entire system function, affecting the development efficiency of the entire centralized control station system, and the user experience is poor. Summary of the invention

[0005] The object of the present invention is to provide a method and system suitable for Web publishing of centralized control station operation tickets based on a microservice architecture.

[0006] To achieve the above object, the present invention provides a method for publishing a centralized control station operation ticket on the Web based on a microservice architecture, characterized in that the method is executed in Zone I in the centralized control station system, and the method comprises the following steps:

[0007] S1: parse the operation ticket generation instruction, and generate the operation ticket according to the operation ticket generation instruction;

[0008] S2: Execute operations on the operation ticket. Among them, the operations cause the status of the operation ticket to change. Among them, the change in the status of the operation ticket is at least partially identified by a change in the fields in the operation ticket. Among them, the operations performed on the operation ticket include review, execution, suspension, backfilling, or archiving operations;

[0009] S3: Record the change in the status of the operation ticket into the database;

[0010] S4: Repeatedly execute steps S2 - S3;

[0011] S5: If it is determined that all operations on the operation ticket are completed, stop repeatedly executing steps S2 - S3;

[0012] S6: In response to the database being updated, synchronize the operation ticket information in the database to the database in Zone IV.

[0013] In a preferred embodiment, steps S2 - S4 are specifically:

[0014] Execute a first operation on the operation ticket. Among them, the first operation causes a first change in the status of the operation ticket;

[0015] Record the first change in the status of the operation ticket into the database;

[0016] Execute a second operation on the operation ticket that has undergone the first operation. Among them, the second operation causes a second change in the status of the operation ticket;

[0017] Record the second change in the status of the operation ticket into the database.

[0018] In a preferred embodiment, when the operation ticket is reviewed, the review field in the operation ticket changes from a first value to a second value. When the operation ticket is executed, the execution field in the operation ticket changes from a first value to a second value. When the operations on the operation ticket are completed, the execution field in the operation ticket changes from the second value to a third value.

[0019] The present invention provides a system applicable to the Web publishing of operation tickets in a centralized control station based on a microservices architecture, characterized in that the system includes an operation ticket function module, a database, and a synchronization service module. Among them, the system is configured to perform the following operations:

[0020] S1: Parse the operation ticket generation instruction and generate an operation ticket according to the operation ticket generation instruction;

[0021] S2: Perform operations on the operation ticket. Among them, the operations cause the status of the operation ticket to change. Among them, the change in the status of the operation ticket is at least partially identified by a change in the fields in the operation ticket. Among them, the operations performed on the operation ticket include review, execution, suspension, backfilling, or archiving operations;

[0022] S3: Record the change in the status of the operation ticket in the database;

[0023] S4: Repeat steps S2 - S3;

[0024] S5: If it is determined that all operations on the operation ticket are completed, stop repeating steps S2 - S3;

[0025] S6: In response to the database being updated, synchronize the operation ticket information in the database to the database in Zone IV.

[0026] In a preferred embodiment, steps S2 - S4 are specifically as follows:

[0027] Perform a first operation on the operation ticket. Among them, the first operation causes a first change in the status of the operation ticket;

[0028] Record the first change in the status of the operation ticket in the database;

[0029] Perform a second operation on the operation ticket on which the first operation has been performed. Among them, the second operation causes a second change in the status of the operation ticket;

[0030] Record the second change in the status of the operation ticket in the database.

[0031] In a preferred embodiment, when the operation ticket is reviewed, the review field in the operation ticket changes from a first value to a second value. When the operation ticket is executed, the execution field in the operation ticket changes from a first value to a second value. When the operations on the operation ticket are completed, the execution field in the operation ticket changes from the second value to a third value.

[0032] The present invention provides a method for Web publishing of operation tickets applicable to centralized control stations based on a microservices architecture. The method is characterized in that the method is executed in Zone IV of the centralized control station system. The method includes the following steps:

[0033] Read the status of the operation ticket in the database;

[0034] Online edit the display style of the operation ticket to form an intermediate file in xml format;

[0035] Generate an operation ticket file based on the status of the operation ticket in the database and the intermediate file in xml format.

[0036] In a preferred embodiment, the display style of the online edited operation ticket is executed via a Web configuration tool, where the Web configuration tool is an operation ticket style editing tool based on a browser, where the Web configuration tool is a separate software with a B / S architecture, and the Web configuration tool is deployed on the application server in Zone IV.

[0037] The present invention provides a system applicable to the Web publishing of operation tickets in a centralized control station based on a microservices architecture, characterized in that the system includes an operation ticket Web publishing function module, a database, and a synchronization service module, where the system is configured to perform the following operations:

[0038] Read the status of the operation ticket in the database;

[0039] Online edit the display style of the operation ticket to form an intermediate file in xml format;

[0040] Generate an operation ticket file based on the status of the operation ticket in the database and the intermediate file in xml format.

[0041] In a preferred embodiment, the display style of the online edited operation ticket is executed via a Web configuration tool, where the Web configuration tool is an operation ticket style editing tool based on a browser, where the Web configuration tool is a separate software with a B / S architecture, and the Web configuration tool is deployed on the application server in Zone IV.

[0042] Compared with the prior art, the present invention has the following advantages. The present invention proposes a method for Web publishing of operation tickets in a centralized control station system based on a microservices architecture, which uses a method based on database synchronization instead of operation ticket file synchronization. When the status of the operation ticket changes, only the data volume of one field needs to be synchronized, improving the efficiency of data transmission; develop a Web-based online configuration tool in Zone IV, and according to the user's needs, use the configuration tool to online edit the display style of the operation ticket, and then form an intermediate file in xml format. The operation ticket Web publishing function module obtains the operation ticket information from the database, and then generates an operation ticket file in a specific format and style according to the xml file. In this way, the operation ticket Web publishing module only depends on the intermediate template file, and changes in style and format do not require re-coding, improving the user experience; according to the design principles of the microservices architecture, develop the operation ticket Web publishing module into a standard microservice, completely separating the front-end page and the back-end service. The back-end service interface provides standard json format data for the front-end page. The operation ticket Web publishing module that becomes a standard microservice is completely decoupled from the entire application system in Zone IV, facilitating later transplantation and expansion and improving the stability of the system. BRIEF DESCRIPTION OF THE DRAWINGS

[0043] Figure 1 is a schematic diagram of the system architecture according to an embodiment of the present invention.

[0044] Figure 2 It is a schematic flowchart of a method according to an embodiment of the present invention. Specific embodiments

[0045] The following will describe in detail the specific embodiments of the present invention with reference to the accompanying drawings. However, it should be understood that the protection scope of the present invention is not limited by the specific embodiments.

[0046] Unless otherwise clearly stated, in the entire specification and claims, the term "comprising" or its variations such as "including" or "having" etc. will be understood to include the stated elements or components, without excluding other elements or other components.

[0047] The existing implementation methods for the Web publishing of operation tickets in the centralized control station system have the following problems: The entire operation ticket file is synchronized across regions. The review of the operation ticket is in Zone IV, and the execution is in Zone I. Moreover, the execution requires multiple steps and multiple synchronizations of the entire file, occupying expensive cross-region synchronization bandwidth resources and having low efficiency; The display format of the operation ticket needs to change according to the needs and habits of different centralized control station users. However, the current function code for the Web publishing of operation tickets completely depends on the file format agreed upon by the region. When the file style and format change, the application programs related to the operation ticket publishing need to be recoded, resulting in a poor user experience; In addition, the code of the function module for the Web publishing of operation tickets is tightly coupled with the applications in the entire Zone IV. Any change in the code of a single function module requires a comprehensive test of the entire system, affecting the development efficiency of the system. Among them, Zone I refers to the production control major zone. Any system with real-time monitoring and control functions should be deployed in Zone I, and the security level requirement for Zone I is the highest. Zone IV refers to the management information major zone. The non-control functions of the management information system and the real-time monitoring system, as well as the operation and maintenance statistical analysis functions, are all deployed in Zone IV, and the security level requirement for Zone IV is relatively high.

[0048] The present invention proposes a method for Web publishing of operation tickets in a centralized control station system based on a microservices architecture. It uses a method based on database synchronization to replace the synchronization of operation ticket files. When the status of an operation ticket changes, only the data volume of one field needs to be synchronized, improving the efficiency of data transmission. A Web-based online configuration tool is developed in Zone IV. According to the user's requirements, the display style of the operation ticket is edited online using the configuration tool, and then an intermediate file in xml format is formed. The operation ticket Web publishing function module obtains the operation ticket information from the database and then generates an operation ticket file in a specific format and style according to the xml file. In this way, the operation ticket Web publishing module only depends on the intermediate template file, and changes in style and format do not require re-coding, improving the user experience. According to the design principles of the microservices architecture, the operation ticket Web publishing module is developed into a standard microservice. The front-end page and the back-end service are completely separated. The back-end service interface provides standard json format data for the front-end page. The operation ticket Web publishing module, which becomes a standard microservice, is completely decoupled from the entire Zone IV application system, facilitating later transplantation and expansion and improving the stability of the system.

[0049] Among them, in a specific embodiment, the Web configuration tool is a browser-based operation ticket style editing tool. The Web configuration tool is a separate software with a B / S architecture. Users edit the operation ticket style by operating such as editing the title, editing text, inserting tables, and inserting pictures on the front-end Web page, and then save it as a template file. This Web configuration tool is deployed on the Zone IV application server and does not require users to install it on the terminal. Users can access it through the browser of their office computers to edit the operation ticket style.

[0050] As Figure 1 and Figure 2 shown, the present invention provides a method for Web publishing of operation tickets applicable to a centralized control station based on a microservices architecture, characterized in that the method is executed in Zone I of the centralized control station system, and the method includes the following steps: S1: Parse the operation ticket generation instruction and generate an operation ticket according to the operation ticket generation instruction; S2: Perform an operation on the operation ticket, wherein the operation causes the status of the operation ticket to change, wherein the change in the status of the operation ticket is at least partially identified by a change in a field in the operation ticket, and the operation performed on the operation ticket includes an audit, execution, suspension, backfill, or archiving operation; S3: Record the change in the status of the operation ticket in the database; S4: Repeat steps S2 - S3; S5: If it is determined that all operations on the operation ticket are completed, stop repeating steps S2 - S3; S6: In response to the database being updated, synchronize the operation ticket information in the database to the database in Zone IV.

[0051] In a preferred embodiment, steps S2 - S4 are specifically as follows: perform a first operation on the operation ticket, where the first operation causes a first change in the status of the operation ticket; record the first change in the status of the operation ticket into the database; perform a second operation on the operation ticket on which the first operation has been performed, where the second operation causes a second change in the status of the operation ticket; record the second change in the status of the operation ticket into the database.

[0052] In a preferred embodiment, when an audit operation is performed on the operation ticket, the audit field in the operation ticket changes from a first value to a second value. When an execution operation is performed on the operation ticket, the execution field in the operation ticket changes from the first value to the second value. When the operation on the operation ticket is completed, the execution field in the operation ticket changes from the second value to a third value.

[0053] The present invention provides a system applicable to the Web publishing of operation tickets in a centralized control station based on a microservices architecture, characterized in that the system includes an operation ticket function module, a database, and a synchronization service module. The system is configured to perform the following operations: S1: Parse an operation ticket generation instruction and generate an operation ticket according to the operation ticket generation instruction; S2: Perform an operation on the operation ticket, where the operation causes a change in the status of the operation ticket, and the change in the status of the operation ticket is at least partially identified by a change in a field in the operation ticket. The operations performed on the operation ticket include audit, execution, suspension, backfill, or archiving operations; S3: Record the change in the status of the operation ticket into the database; S4: Repeat steps S2 - S3; S5: If it is determined that all operations on the operation ticket are completed, stop repeating steps S2 - S3; S6: In response to the database being updated, synchronize the operation ticket information in the database to the database in Zone IV.

[0054] In a preferred embodiment, steps S2 - S4 are specifically as follows: perform a first operation on the operation ticket, where the first operation causes a first change in the status of the operation ticket; record the first change in the status of the operation ticket into the database; perform a second operation on the operation ticket on which the first operation has been performed, where the second operation causes a second change in the status of the operation ticket; record the second change in the status of the operation ticket into the database. An example of the database is as follows:

[0055] Operation ticket information table: wfticket

[0056]

[0057] In a preferred embodiment, when an operation ticket is audited, the audit field in the operation ticket changes from a first value to a second value. When the operation ticket is executed, the execution field in the operation ticket changes from the first value to the second value. When the operation on the operation ticket is completed, the execution field in the operation ticket changes from the second value to a third value. In a specific example, when the corresponding field in the operation ticket changes, it means that the status of the operation ticket has changed. For example, when the user successfully audits the operation ticket, the field [auditState] changes from 0 to 1, indicating that the audit status of the operation ticket changes from [not audited] to [audited]; when the user successfully executes the operation ticket, the field [actionFlag] changes from 0 to 1, indicating that the execution status of the operation ticket changes from [not executed] to [executing]; when the user successfully completes the execution of the operation ticket, the field [actionFlag] changes from 1 to 2, indicating that the execution status of the operation ticket changes from [executing] to [completed]. The backfilling and archiving operations do not change the status of the operation.

[0058] The present invention provides a method for Web publishing of operation tickets applicable to a centralized control station based on a microservices architecture. The method is characterized in that it is executed in the IV area of the centralized control station system. The method comprises the following steps: reading the status of the operation ticket in the database; online editing the display style of the operation ticket to form an intermediate file in xml format; generating an operation ticket file based on the status of the operation ticket in the database and the intermediate file in xml format.

[0059] In a preferred embodiment, the online editing of the display style of the operation ticket is executed via a Web configuration tool. The Web configuration tool is an operation ticket style editing tool based on a browser. The Web configuration tool is a separate software with a B / S architecture and is deployed on the IV area application server.

[0060] The present invention provides a system for Web publishing of operation tickets applicable to a centralized control station based on a microservices architecture. The system is characterized in that it comprises an operation ticket Web publishing function module, a database, and a synchronization service module. The system is configured to perform the following operations: reading the status of the operation ticket in the database; online editing the display style of the operation ticket to form an intermediate file in xml format; generating an operation ticket file based on the status of the operation ticket in the database and the intermediate file in xml format.

[0061] In a preferred embodiment, the online editing of the display style of the operation ticket is executed via a Web configuration tool. The Web configuration tool is an operation ticket style editing tool based on a browser. The Web configuration tool is a separate software with a B / S architecture and is deployed on the IV area application server.

[0062] It should be understood that in various embodiments of the present invention, the written sequence of the above processes does not mean the sequence of execution. The execution sequence of each process should be determined by its function and internal logic, and should not constitute any limitation to the implementation process of the embodiments of the present invention.

[0063] It should be understood that the above specific embodiments of the present invention are only used for exemplary illustration or explanation of the principles of the present invention, and do not constitute a limitation to the present invention. Therefore, any modifications, equivalent replacements, improvements, etc. made without departing from the spirit and scope of the present invention shall be included within the protection scope of the present invention. In addition, the appended claims of the present invention are intended to cover all variations and modifications that fall within the scope and boundaries of the appended claims, or equivalent forms of such scope and boundaries.

Claims

1. A method for Web publishing of operation tickets applicable to centralized control stations based on a microservices architecture, characterized in that The method includes performing the following steps in Zone I of the centralized control station system: S1: Parse the operation ticket generation instruction and generate an operation ticket according to the operation ticket generation instruction; S2: Perform an operation on the operation ticket, wherein the operation causes a change in the state of the operation ticket, wherein the change in the state of the operation ticket is at least partially identified by a change in a field in the operation ticket, and the operation performed on the operation ticket includes an audit, execution, suspension, backfill or archiving operation; S3: Record the change in the state of the operation ticket in the database; S4: Repeat steps S2 - S3; S5: If it is determined that all operations on the operation ticket are completed, stop repeating steps S2 - S3; S6: In response to the database being updated, synchronize the operation ticket information in the database to the database in Zone IV; The method further includes performing the following steps in Zone IV of the centralized control station system: Read the state of the operation ticket in the database; Online edit the display style of the operation ticket to form an intermediate file in xml format; Generate an operation ticket file based on the state of the operation ticket in the database and the intermediate file in xml format.

2. The method for Web publishing of operation tickets applicable to centralized control stations based on a microservices architecture as described in claim 1, wherein, Steps S2 - S4 are specifically: Perform a first operation on the operation ticket, wherein the first operation causes a first change in the state of the operation ticket; Record the first change in the state of the operation ticket in the database; Perform a second operation on the operation ticket on which the first operation has been performed, wherein the second operation causes a second change in the state of the operation ticket; Record the second change in the state of the operation ticket in the database.

3. The method for Web publishing of operation tickets applicable to centralized control stations based on a microservices architecture as described in claim 1, wherein, After the audit operation is performed on the operation ticket, the audit field in the operation ticket changes from a first value to a second value. When the execution operation is performed on the operation ticket, the execution field in the operation ticket changes from a first value to a second value. When the operation on the operation ticket is completed, the execution field in the operation ticket changes from the second value to a third value.

4. The method for Web publishing of operation tickets applicable to centralized control stations based on a microservices architecture according to claim 1, characterized in that, Online editing the display style of the operation ticket is performed via a Web configuration tool, wherein the Web configuration tool is an operation ticket style editing tool based on a browser, wherein the Web configuration tool is a separate software with a B / S architecture, and the Web configuration tool is deployed on the Zone IV application server.

5. A system based on a microservices architecture and applicable to the Web publishing of operation tickets for centralized control stations, characterized in that, The system includes an operation ticket function module, a database, and a synchronization service module, wherein the system is configured to perform the following operations in Zone I of the centralized control station system: S1: Parse the operation ticket generation instruction and generate an operation ticket according to the operation ticket generation instruction; S2: Perform an operation on the operation ticket, wherein the operation causes a change in the state of the operation ticket, wherein the change in the state of the operation ticket is at least partially identified by a change in a field in the operation ticket, and the operation performed on the operation ticket includes an audit, execution, suspension, backfill or archiving operation; S3: Record the change in the state of the operation ticket in the database; S4: Repeat steps S2 - S3; S5: If it is determined that all operations on the operation ticket are completed, stop repeating steps S2 - S3; S6: In response to the database being updated, synchronize the operation ticket information in the database to the database in Zone IV; The system is further configured to perform the following operations in Zone IV of the centralized control station system: Read the status of the operation ticket in the database; Online edit the display style of the operation ticket to form an intermediate file in xml format; Generate an operation ticket file based on the status of the operation ticket in the database and the intermediate file in xml format.

6. The system for Web publishing of operation tickets applicable to centralized control stations based on a microservices architecture as claimed in claim 5, wherein, Steps S2 - S4 are specifically as follows: Perform a first operation on the operation ticket, where the first operation causes a first change in the status of the operation ticket; Record the first change in the status of the operation ticket into the database; Perform a second operation on the operation ticket that has undergone the first operation, where the second operation causes a second change in the status of the operation ticket; Record the second change in the status of the operation ticket into the database.

7. The system for Web publishing of operation tickets applicable to centralized control stations based on a microservices architecture as claimed in claim 6, wherein, After the operation ticket is audited, the audit field in the operation ticket changes from the first value to the second value. When the operation ticket is executed, the execution field in the operation ticket changes from the first value to the second value. When the operation on the operation ticket is completed, the execution field in the operation ticket changes from the second value to the third value.

8. The system for Web publishing of operation tickets applicable to a centralized control station in a microservices architecture according to claim 5, characterized in that, Online editing of the display style of the operation ticket is performed via a Web configuration tool. The Web configuration tool is an operation ticket style editing tool based on a browser. The Web configuration tool is a stand-alone software with a B / S architecture and is deployed on the Zone IV application server.

Images