Autonomous concurrent program-controlled switching method for electric power SCADA (supervisory control and data acquisition)

Abstract

An electric power SCADA autonomous concurrent program-controlled switching method comprises the steps that before program-controlled switching operation, scheduling auditing is conducted, and a prefabricated program-controlled card is generated; on the day of program-controlled switching operation, the switching operation is automatically executed by the work area after the scheduling agrees to authorize; the operation parameters of all the related stations in the section are inspected before the switching is started officially; after inspection and detection are normal, the production management information system sends an operation command for manually setting a corresponding non-telecontrol switch on an interface to the SCADA system, and the SCADA system immediately sets and realizes live-line derivation after receiving the operation command; after the inspection and detection are normal, the operator sends an instruction to the SCADA system to call out the program control card in the switching of the switch in the power transformation and distribution substation; and after the switching operation is completed, the SCADA system returns an execution result to the production management information system. According to the invention, deep fusion of a production management information system and an electric power SCADA system is realized, safety card control measures are added, misoperation of electric power remote switching operation is prevented, and the operation reliability of equipment operation is improved.

Description

Technical Field

[0001] The present invention relates to the technical field of power system control, and in particular to a method for autonomous concurrent program-controlled switching of power SCADA. Background Art

[0002] In recent years, cutting-edge science and technology have been deeply applied across all industries, with the railway system being a prime example. The Beijing-Zhangjiakou High-Speed ​​Railway and the Beijing-Xiong'an High-Speed ​​Railway, for example, seamlessly integrate technologies such as the Beidou system and 5G networks with railway operations, achieving a humanized, intelligent, and streamlined approach to railway development. Rapidly advancing railway information technology and highly reliable network communications are enabling all railway personnel to continuously explore their professional potential, pursuing what their predecessors dared not. This invention utilizes scientific and technological means to address several issues exposed in power substation switching operations, and possesses significant potential for widespread adoption.

[0003] Currently, switching operations at unmanned power substations are organized and implemented by the dispatchers of each section. This inevitably results in on-site work teams queuing for switching operations, reducing actual on-site operating time and lowering maintenance efficiency. Furthermore, given the broad jurisdiction of section dispatchers, dispatchers are responsible for multiple important tasks, including ticket review, operational process monitoring, and emergency response command. The switching process involves multiple steps, including electrical quantity verification, station confirmation, protection activation and deactivation, and switch operation. Manual switching by dispatchers alone can result in omissions. Therefore, improving the accuracy and efficiency of switching operations, while taking into account on-site waiting times and avoiding erroneous shutdowns and re-energizations, is a major issue that must be addressed following the unmanned transformation of power substations. Summary of the Invention

[0004] In view of the above problems, the present invention is proposed to provide a method for autonomous concurrent program-controlled switching of electric power SCADA, which overcomes the above problems or at least partially solves the above problems.

[0005] In order to solve the above technical problems, the embodiments of the present application disclose the following technical solutions:

[0006] In a first aspect, an embodiment of the present invention discloses a method for autonomous concurrent program-controlled switching of a power SCADA system, comprising:

[0007] S100. Before a program-controlled switching operation, the work area submits a work ticket and a switching ticket. The dispatcher reviews and approves the operation after verification.

[0008] S200. Prefabricated program control cards according to standardized switching procedures;

[0009] S300. On the day of the program-controlled switching operation, the operator uses the production management information system to apply to the dispatcher for authorization to start work. After the dispatcher agrees to the authorization, the work area will independently perform the switching operation.

[0010] S400. Before the formal start of the switching operation, the operating parameters of all relevant stations in the section shall be inspected;

[0011] S500. After the inspection is normal, the operator enters the corresponding switching operation step instruction, and the production management information system sends an operation command to the SCADA system to manually set the corresponding non-teleoperated switch on the interface. After receiving it, the SCADA system immediately sets it and realizes the live derivation;

[0012] S600. After the inspection is normal, the operator sends a command to the SCADA system to call up the program control card for switching the switch in the power substation; after the switching operation is completed, the SCADA system returns the execution result to the production management information system.

[0013] Furthermore, in S200, the prefabricated programmable control card includes steps for inspecting the telesignaling and telemetering values ​​of the booths at both ends of the section and each station, operating the high-voltage circuit breakers, operating and disabling protection, and re-inspecting the telesignaling and telemetering values ​​of the booths at both ends of the section and each station after the operation; during actual operation, the work area issues a switching ticket based on the work ticket one day before the operation, and the steps in the switching ticket involving operating the switches of unmanned power substations directly select the corresponding programmable control card number.

[0014] Furthermore, in S300, the user is authorized to start work through login authentication and authorization card. The login authentication is to verify the validity of the user. Only when the users on both sides are consistent can subsequent business operations be performed; the authorization card is for manual authorization confirmation by program control. After the card authorization is successful, the production management system can initiate subsequent card requirements.

[0015] Furthermore, when the production management system logs in to the authentication and authorization card, it will send a request to the SCADA system. After receiving the request, the SCADA system returns the login or authorization token. If there is a network fluctuation and the production management system fails to obtain the authorization information, it will return the corresponding success token when requesting the SCADA system interface again.

[0016] Furthermore, in S400, inspection of the operating parameters of all relevant sites in the section is achieved through inspection cards. The specific method includes: the production management system sends a command to retrieve the inspection interface, waits for the SCADA system to return whether the conditions for executing the inspection command are met, and after confirming that the conditions for executing the inspection command are met, sends the inspection execution command. After receiving the execution command, the SCADA system automatically executes the inspection command. After the execution is completed, the result is displayed to the dispatcher in the form of a report, and the execution status result is returned to the production management system. The production management system background polls and retrieves the card execution status to confirm the execution result.

[0017] Furthermore, in S500, after the non-remote switch is actually operated by the on-site operator, the production management information system sends an operation command to the SCADA system to manually set the corresponding non-remote switch on the interface. After receiving the command, the SCADA system immediately sets it and has a corresponding energized derivation diagram on the SCADA system HMI interface. The production management system can also obtain the setting result, and the SCADA system will return the result accordingly.

[0018] Furthermore, in S600, the specific method for executing the programmable card includes: the production management system sends a command to call the programmable interface, waits for the SCADA system to return whether the command can be executed, and after confirming that the command can be executed, sends an execution programmable command. After receiving the execution command, the SCADA system automatically executes the programmable command, and after the execution is completed, returns the execution status result to the production management system. The production management system background polls and retrieves the card execution status to confirm the execution result.

[0019] Furthermore, the production management system and the SCADA system exchange information through GRPC communication. When the production management system has a demand request, the production management system is the client of GRPC, and the interface server in the SCADA system acts as the server of GRPC; when the SCADA system has information feedback to the production management system, the production management acts as the server of GRPC, and the interface server of the SCADA system acts as the client of GRPC.

[0020] Furthermore, the SCADA system uses a binary remote procedure call method for data transmission, including two groups of RPC client and server communication interactions, one of which is the interaction between the interface server as the RPC client and the processing server as the RPC server, and the other is the interaction between the interface server as the RPC server and the processing server as the RPC client. The specific method of interaction between the interface server as the RPC client and the processing server as the RPC server includes:

[0021] The interface server acts as an RPC client and calls the local RPC client program when it receives a request from the production management system;

[0022] The RPC client program of the interface server generates a message, puts the required command data of the production management system into the message as a parameter, and adds the corresponding code of the process to be called on the processing server in the message;

[0023] The interface server calls the local operating system network interface to send the message generated by the RPC client program to the processing server via the SCADA system backbone network;

[0024] After receiving the message sent by the interface server, the processing server acts as the RPC server and calls the local RPC server program;

[0025] The server-side program of the processing server analyzes the message, determines which procedure needs to be called based on the corresponding code in the message, and then executes the corresponding local call;

[0026] The processing server executes a local call to analyze the command data and then executes the corresponding command.

[0027] Furthermore, the specific method for interaction between the interface server acting as an RPC server and the processing server acting as an RPC client includes:

[0028] The processing server acts as another RPC client for communication and calls the local RPC client program after processing the corresponding command;

[0029] The RPC client program generates a message, puts the execution result data as a parameter into the message, and adds the corresponding code of the procedure to be called on the RPC server in the message;

[0030] The RPC client calls the local operating system network interface to send the message generated by the RPC client program to the RPC server via the SCADA system backbone network.

[0031] After receiving the message sent by the RPC client, the RPC server where the interface server is located acts as the RPC server and calls the local RPC server program.

[0032] The RPC server program analyzes the message, determines which procedure needs to be called based on the corresponding code in the message, and then executes the corresponding local call.

[0033] The RPC server performs local call analysis and execution results, and sends them to the GRPC client production management system through GRPC communication.

[0034] The beneficial effects of the above technical solutions provided by the embodiments of the present invention include at least:

[0035] The present invention discloses a method for autonomous concurrent program-controlled switching of electric power SCADA, comprising: before the program-controlled switching operation, a work area submits a work ticket and a switching ticket, and the dispatcher approves the operation after reviewing them; a program-controlled card is prefabricated according to a standardized switching procedure; on the day of the program-controlled switching operation, an operator applies to the dispatcher for a start-up authorization using a production management information system, and the work area autonomously performs the switching operation after the dispatcher agrees to the authorization; before the switching operation officially begins, an inspection of the operating parameters of all relevant sites in the section is completed; after the inspection is normal, the operator inputs the corresponding switching operation step instruction, and the production management information system sends an operation command to the SCADA system to manually set the corresponding non-teleoperated switch on the interface, and the SCADA system immediately sets the switch on receipt and realizes live deduction; after the inspection is normal, the operator sends an instruction to the SCADA system to call out the program-controlled card for switching the switch in the power substation; after the switching operation is completed, the SCADA system returns the execution result to the production management information system.

[0036] The present invention discloses a method for autonomous concurrent program-controlled switching of electric power SCADA, which can quickly understand the real-time topology of the power grid and perform a series of tasks such as optimized scheduling and fault diagnosis in the operation and management of the power system, thereby providing strong support for the business and application of the power supply scheduling system, and can play a great role in the implementation of power in the rail transit industry. The present invention uses scientific and technological means to solve the problems exposed in the switching operations of power substations, realizes the deep integration of the section production management information system and the conventional power SCADA system, adds safety card control measures, prevents the misoperation of the remote switching operation of electric power, improves the reliability of equipment operation, promotes the safety of switching operations, solves the problem of the work group waiting too long to start work, saves operation time, improves efficiency, and has strong promotion value.

[0037] The technical solution of the present invention is further described in detail below through the accompanying drawings and embodiments. BRIEF DESCRIPTION OF THE DRAWINGS

[0038] The accompanying drawings are used to provide a further understanding of the present invention and constitute a part of the specification. Together with the embodiments of the present invention, they are used to explain the present invention and do not constitute a limitation of the present invention. In the accompanying drawings:

[0039] Figure 1 This is a flow chart of a method for autonomous and concurrent program-controlled switching of power SCADA in embodiment 1 of the present invention;

[0040] Figure 2 This is an overall framework diagram of a method for autonomous concurrent program-controlled switching of power SCADA in Example 1 of the present invention;

[0041] Figure 3This is a flowchart of GRPC communication interaction between the production management system and the SCADA system in Example 1 of the present invention;

[0042] Figure 4 This is a schematic diagram of obtaining command data of a production management system through RPC in Example 1 of the present invention;

[0043] Figure 5 This is a schematic diagram of obtaining execution result data of a SCADA system through RPC in Example 3 of the present invention. DETAILED DESCRIPTION

[0044] Exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. Although exemplary embodiments of the present disclosure are shown in the accompanying drawings, it should be understood that the present disclosure can be implemented in various forms and should not be limited by the embodiments set forth herein. Rather, these embodiments are provided to enable a more thorough understanding of the present disclosure and to fully convey the scope of the present disclosure to those skilled in the art.

[0045] In order to solve the problems existing in the prior art, an embodiment of the present invention provides a method for autonomous and concurrent program-controlled switching of power SCADA.

[0046] Example 1: The present invention discloses a method for autonomous and concurrent program-controlled switching of power SCADA, such as Figure 1 ,include:

[0047] S100. Before performing a program-controlled switching operation, the work area submits a work ticket and a switching ticket. The dispatcher reviews and approves the operation after verification. The work ticket clarifies the operation content, scope, safety measures, and personnel division of labor. Key information such as the operation time, equipment name, and operating steps must be detailed. The switching ticket compiles the switching operation sequence for specific equipment (such as circuit breakers and disconnectors) and must strictly correspond to the work ticket to ensure correct operational logic. Both tickets must be completed by qualified personnel, consistent with on-site conditions, and reviewed and signed by the work area manager.

[0048] During program-controlled switching operations, the submission and approval of work and switching tickets are key to ensuring safety. Through a three-tiered control system consisting of strict work area preparation, professional dispatch review, and on-site closed-loop execution, the risk of misoperation can be effectively reduced.

[0049] S200. Prefabricate program-controlled cards according to standardized switching procedures; in S200 of this embodiment, the prefabricated program-controlled cards include steps for inspecting the telemetering values ​​of the booths at both ends of the section and each station, operating the high-voltage circuit breakers, operating the protection, and re-inspecting the telemetering values ​​of the booths at both ends of the section and each station after the operation; during actual operation, the work area issues a switching ticket based on the work ticket one day before the operation, and the steps in the switching ticket involving operating the switches of unmanned power substations directly select the corresponding program-controlled card number.

[0050] Specifically, according to power safety regulations, switching operation program control cards for all power substations are pre-compiled. Professional technical management personnel review and test each card one by one. After confirmation, they are entered into the SCADA system for use. The pre-made switching operation program control cards include steps such as checking the telemetering values ​​of the booths at both ends of the section and each station, operating high-voltage circuit breakers, protecting the deployment and withdrawal of protection, and re-checking the telemetering values ​​of the booths at both ends of the section and each station after the operation, thereby improving the accuracy of switching. During actual operation, the work area issues a switching ticket based on the work ticket the day before the operation. The steps in the switching ticket involving operating the switches of unmanned power substations can be directly selected by selecting the corresponding program control card number, reducing the risk of selecting the wrong switch at each step when issuing the switching ticket. At the same time, the number of items in the switching ticket is greatly reduced, the workload of switching ticket review is reduced, and the switching ticket is simplified and standardized. By pre-making standardized switching program control cards, the operating process can be standardized, efficient, and safe.

[0051] S300. On the day of the program-controlled switching operation, the operator uses the production management information system to apply to the dispatcher for start-up authorization. After the dispatcher agrees to the authorization, the work area independently performs the switching operation. In S300 of this embodiment, the user is authorized to start work through login authentication and authorization card. Among them, login authentication is to verify the validity of the user. Only when the users on both sides are consistent can subsequent business operations be performed; the authorization card is for manual authorization confirmation of program control. After the card authorization is successful, the production management system can initiate subsequent card requirements.

[0052] When logging in to authenticate and authorize a card, the production management system sends a request to the SCADA system. Upon receiving the request, the SCADA system returns a login or authorization token. If network fluctuations prevent the production management system from obtaining authorization information, a subsequent request to the SCADA system interface returns a corresponding success token. Section site inspections prior to switching operations are crucial for ensuring power grid security. Through standardized inspection content, streamlined implementation procedures, and the use of intelligent tools, comprehensive control of equipment status and risk mitigation can be achieved.

[0053] S400. Before the formal start of the switching operation, the operating parameters of all relevant sites in the section are inspected first; in S400 of this embodiment, the operating parameters of all relevant sites in the section are inspected through inspection cards. The specific method includes: the production management system sends a command to retrieve the inspection interface, waits for the SCADA system to return whether the conditions for executing the inspection command are met, and after confirming that the conditions for executing the inspection command are met, the inspection execution command is sent. After receiving the execution command, the SCADA system automatically executes the inspection command. After the execution is completed, the result is displayed to the dispatcher in the form of a report, and the execution status result is returned to the production management system. The production management system background polls and retrieves the card execution status to confirm the execution result.

[0054] S500. After the inspection is normal, the operator enters the corresponding switching operation step instruction, and the production management information system sends an operation command to the SCADA system to manually set the corresponding non-teleoperated switch on the interface. After receiving it, the SCADA system immediately sets it and realizes the live derivation;

[0055] In S500 of this embodiment, after the non-remote switch is actually operated by the on-site operator, the production management information system sends an operation command to the SCADA system to manually set the corresponding non-remote switch on the interface. After receiving the command, the SCADA system immediately sets the switch and displays a corresponding energized derivation diagram on the SCADA system HMI interface. The production management system can also obtain the setting result, and the SCADA system will return the result accordingly.

[0056] S600. After the inspection is normal, the operator sends a command to the SCADA system to call up the program control card for switching the switch in the power substation; after the switching operation is completed, the SCADA system returns the execution result to the production management information system.

[0057] In S600 of this embodiment, the specific method for executing the programmable card includes: the production management system sends a command to call the programmable interface, waits for the SCADA system to return whether the command can be executed, and after confirming that the command can be executed, sends an execution programmable command. After receiving the execution command, the SCADA system automatically executes the programmable command, and after the execution is completed, returns the execution status result to the production management system. The production management system background polls and retrieves the card execution status to confirm the execution result.

[0058] In this embodiment, the information instructions initiated by the production management system and transmitted to the SCADA system through the interface will be retained by the production management system; after receiving the information instructions, the SCADA system will first retain them and return them to the production management system for verification; the production management system will compare the received information instructions with the previously issued ones, and after confirming that they are correct, it will issue a permission instruction to the SCADA system; after receiving the permission instruction, the production management system will retrieve the retained instructions to perform the operation. After the operation is completed, the SCADA system will transmit the completion information to the production management system; the production management system will retain it after receiving it, and return it to the SCADA system for confirmation; after receiving the return information, the SCADA system will check it with the retained completion information and then send a confirmation message to the production management system; the production management system will receive the confirmation message only when it represents that the instruction information interaction is completed. The information and data initiated by the SCADA system and transmitted to the production management system are also retained and returned according to the above principles.

[0059] In this embodiment, information commands (such as a switching card) from the production management system are transmitted to the SCADA system via an interface. The SCADA system then retrieves the switching card. The "Execute" button in the switching card is then transmitted back to the production management system, which then selects whether to execute the command. After the production management system confirms the execution, the command is then transmitted back to the SCADA system, which executes the switching card. In other words, the execution of the switching card command through the network requires a "Confirm" button as a buffer.

[0060] If the SCADA system encounters a step that cannot be executed during the switching card execution process, it will prompt "Ignore," "Abort," or "Retry," accompanied by an audible alarm. The dispatcher will then make an intervention selection on the SCADA program card (similar to manually retrieving the program card). If the dispatcher selects "Abort," indicating that the switching operation is not complete, the SCADA system will transmit this information to the production management system. Upon receiving this information, the production management system will sound an audible alarm and a selection prompt. The dispatcher will contact the on-site operator and manually intervene on the production management system interface, selecting "Retry" (re-execute the switching card), "Terminate" (abort the switching operation and stop it), or "Continue" (continue execution based on the existing steps). The production management system will then transmit the dispatcher's selection to the site, where the on-site work leader will confirm the execution. This process retains information such as the operator's name and operation time. That is to say, when the dispatcher selects "Ignore", "Abort" or "Retry" on the SCADA subsystem program control card, it is for a specific switching step in this card; when the dispatcher and on-site personnel select "Retry", "Terminate" or "Continue" on the production management system interface, it means retrying, terminating, or ignoring the entire switching card and continuing to execute the card control table.

[0061] In this embodiment, the program control of the SCADA system is divided into "external control / internal control" modes. Since the production management system can control the SCADA system to perform switching operations, this is an "external control" relative to the SCADA system. When the SCADA system operates the switching card itself, it is "internal control". The scheduling end of the production management system is also divided into "control / remote control" modes. The control state means that the dispatcher can execute the network operation program control card in the scheduling end interface of the production management system process card control table, which cannot be performed on site; the remote control state means that after authorization by the dispatcher, the on-site work leader can execute the network operation program control card through the process card control table on the mobile terminal.

[0062] Specifically, an "External Control / Internal Control" switch is set on the SCADA system interface. Normally, the SCADA system defaults to internal control, and the "External Control / Internal Control" switch displays "External Control." When the dispatcher clicks the "External Control" button, a pop-up window appears on the SCADA system prompting, "Please confirm whether to switch to external control mode." After the dispatcher selects "Yes," the SCADA system switches to external control mode, allowing it to receive operational instructions from the production management system, and the "External Control" button changes to "Internal Control." While the SCADA system is in external control mode, if there are problems with information transmission between the production management system and the SCADA system, or if an exception occurs during the execution of a program control card (such as failure to execute and requiring manual intervention), the SCADA system automatically reverts to internal control mode and displays a pop-up window indicating that the "External Control / Internal Control" switch changes to "External Control." While in external control mode (with the "External Control / Internal Control" switch displaying "Internal Control"), the dispatcher can click the "Internal Control" button at any time to disconnect information from the external system.

[0063] The scheduling interface of the production management system is equipped with a "control / remote control" conversion button. When SCADA is in internal control mode, the "control / remote control" conversion button on the scheduling interface is gray and cannot be selected; when SCADA is switched to external control mode, the scheduling interface of the production management system is in control state by default, and the "control / remote control" conversion button displays "remote control"; when the dispatcher clicks the "remote control" button, a pop-up window will appear in the production management system: Please confirm whether to execute the "remote control" mode; after the dispatcher selects "yes", the process card control table of the production management system is switched to remote control mode, and the network operation program card can be executed on site. At this time, the "control / remote control" conversion button on the scheduling end displays "control", and the dispatcher can click the "control" button at any time to cut off the information transmission between the site and the SCADA system.

[0064] In this embodiment, when the SCADA system is in the "external control" mode, it receives instructions from the production management system to perform program control operations and feedback information. When an abnormal situation such as a jam or suspension occurs during the program control operation, the SCADA system will first immediately terminate the external control mode and switch to the internal control mode, and the "external control / internal control" conversion button will display "external control"; second, it will issue a text prompt and an audio alarm to remind the dispatcher to intervene; and third, it will send a "program control abnormality, waiting for the dispatcher to handle" message to the production management system. After the production management system receives the "program control abnormality, waiting for the dispatcher to handle" message sent by the SCADA system, it should display a pop-up window on the dispatch end office screen, accompanied by inactivated "retry" and "continue" selection buttons. If the dispatch end has previously set the "remote control" mode, the information will also be displayed on the on-site mobile phone terminal.

[0065] After the dispatcher discovers the alarm, there are two ways to handle it:

[0066] The first approach: The dispatcher selects an action within the process control card, such as "Ignore," "Retry this item," or "Terminate process control." If the card completes execution, the SCADA system sends a "Successful Execution" message to the production management system. The dispatcher activates the "Continue" button on the dispatcher's pop-up window and clicks "Continue" on the production management system's dispatcher process control table. This allows the dispatcher to continue the process according to the dispatcher's instructions. If the dispatcher has previously enabled "remote control," this information will be displayed on the site's mobile phone terminal, and the site personnel will proceed according to the dispatcher's instructions on the mobile phone process control table. If the card fails to execute or the dispatcher selects "Terminate process control," the SCADA system sends an "Execution Failed" message to the production management system, which will display it on the dispatcher's process control table. If "remote control" was previously enabled, this information will also be displayed on the site's mobile phone terminal. The dispatcher and site personnel will then proceed according to the original process flow on the production management system's process control table. (The termination function is a pre-existing feature of the production management system, allowing users to terminate the operation at any step.)

[0067] The second processing method: After checking and confirming that the instantaneous voltage does not meet the requirements or the instantaneous channel is blocked, which does not affect the main process of the program, the dispatcher closes the stuck program control card in the SCADA system (the SCADA system sends a "retry" message to the production management system), and restores the SCADA system to external control mode. At this time, the "retry" button is activated on the production management system interface of the dispatch end; if the dispatcher selects the "remote control" mode on the production management system interface, the "retry" button on the mobile phone interface of the on-site work leader is activated. After clicking this button, the single-step operation on the process card control table can be executed again.

[0068] In order to better understand this embodiment, this embodiment also discloses the overall framework of the present invention. Figure 2As shown, it involves three modules: production management system module, middleware module, and SCADA system module. The present invention focuses on the SCADA system module.

[0069] The middleware is responsible for converting and interacting data between the production management system and the SCADA system. The interface server in the SCADA system processes GRPC requests from the middleware (which converts the production management system) and sends the request content to the processing server. The processing server then sends the corresponding data content to the workstation for interface retrieval and other processing.

[0070] Interface server:

[0071] a. Receiving function: used to receive GRPC requests and use RPC communication technology to send the data content in GRPC to the processing server.

[0072] b. Sending function: The received GRPC request maintains the connection, and after the processing server returns the execution result information of the RPC, the execution result information is returned to the middleware and sent to the production management system through the middleware.

[0073] Processing Server:

[0074] a. Receiving function: Receives the RPC data content sent by the interface server, and uses the message mechanism to send the message content to the HMI of the designated workstation. The HMI is responsible for calling the program control and inspection interface.

[0075] b. Sending function: Receive the execution result messages of the program control interface and the inspection interface, then convert the message content into RPC and send it to the interface server.

[0076] In some preferred embodiments, the production management system and the SCADA system exchange information through GRPC communication. When the production management system has a demand request, the production management system is the client of GRPC, and the interface server in the SCADA system acts as the server of GRPC; when the SCADA system has information feedback to the production management system, the production management acts as the server of GRPC, and the interface server of the SCADA system acts as the client of GRPC.

[0077] Specifically, the application of GRPC in the power SCADA switching scenario solves the pain points of high latency, difficult integration, poor reliability and other existing problems in traditional solutions through the four core advantages of high-performance communication, cross-language protocol compatibility, security reinforcement and simplified operation and maintenance. Therefore, the present invention uses the GRPC technical path. GRPC generates cross-language client / server code through standardized Protobuf interface definitions to achieve transparent protocol interaction. The production management system and the SCADA system communicate and exchange information through GRPC. When the production management system has a demand request, the production management system is the client of GRPC, and the interface server in the SCADA system acts as the server of GRPC. When the SCADA system has information feedback to the production management system, the production management acts as the server of GRPC, and the interface server of the SCADA system acts as the client of GRPC.

[0078] The specific interaction process is as follows: Figure 3 As shown in the figure, the production management system acts as a GRPC client and sends the following types of requests to the SCADA system:

[0079] (1) The GRPC client sends a request to verify user information;

[0080] (2) The GRPC client sends a verification application authorization request;

[0081] (3) The GRPC client sends an authorization result request;

[0082] (4) The GRPC client sends a request to set object parameters;

[0083] (5) The GRPC client sends a result request for setting object parameters;

[0084] (6) The GRPC client sends a request to retrieve the inspection interface;

[0085] (7) The GRPC client sends an inspection request;

[0086] (8) The GRPC client sends a request to obtain the inspection results;

[0087] (9) The GRPC client sends a request to retrieve the program control;

[0088] (10) The GRPC client sends a request to execute program control;

[0089] (11) The GRPC client sends a request to obtain the program control result;

[0090] (12) The GRPC client sends a request to obtain synchronization table information;

[0091] (13) The GRPC client sends a request to obtain synchronization table data information;

[0092] (14) The GRPC client sends each task status request.

[0093] The interface server of the SCADA system acts as the server of GRPC at this time. After receiving the above requests, it processes the information and then acts as the client of RPC communication to send the above information to the processing server (RPC server) of the SCADA system. After receiving it, the RPC server sends the message to the corresponding workstation to process the task of the production management system.

[0094] When the SCADA system workstation completes the task, it sends information to the RPC client (interface server). The RPC client processes the received information and sends it to the RPC server (interface server). After the information is processed, if the interface server wants to send the result information to the production management system, it acts as a GRPC client and sends the following types of result information to the GRPC server (production management system).

[0095] (1) The GRPC client sends the verification result information of the user;

[0096] (2) The GRPC client sends authorization result information;

[0097] (3) The GRPC client sends the result information of setting parameters;

[0098] (4) The GRPC client sends the inspection interface to retrieve the result information;

[0099] (5) The GRPC client sends execution inspection information;

[0100] (6) The GRPC client sends the inspection execution results;

[0101] (7) The GRPC client sends the program-controlled call result information;

[0102] (8) GRPC client sends program execution information;

[0103] (9) The GRPC client sends the program execution result information;

[0104] (10) GRPC client sends synchronization table information;

[0105] (11) GRPC client sends synchronization table data information;

[0106] (12) The GRPC client sends the status of each task.

[0107] In some preferred embodiments, data transmission is performed within the SCADA system through a binary remote procedure call method, including two groups of RPC client and server communication interactions, one group is the interaction between the interface server as the RPC client and the processing server as the RPC server, and the other group is the interaction between the interface server as the RPC server and the processing server as the RPC client; the specific method of interaction between the interface server as the RPC client and the processing server as the RPC server is as follows: Figure 4 ,include:

[0108] The interface server acts as an RPC client and calls the local RPC client program when it receives a request from the production management system;

[0109] The RPC client program of the interface server generates a message, puts the required command data of the production management system into the message as a parameter, and adds the corresponding code of the process to be called on the processing server in the message;

[0110] The interface server calls the local operating system network interface to send the message generated by the RPC client program to the processing server via the SCADA system backbone network;

[0111] After receiving the message sent by the interface server, the processing server acts as the RPC server and calls the local RPC server program;

[0112] The server-side program of the processing server analyzes the message, determines which procedure needs to be called based on the corresponding code in the message, and then executes the corresponding local call;

[0113] The processing server executes a local call to analyze the command data and then executes the corresponding command.

[0114] In some preferred embodiments, the specific method of interaction between the interface server as the RPC server and the processing server as the RPC client is as follows: Figure 5 ,include:

[0115] The processing server acts as another RPC client for communication and calls the local RPC client program after processing the corresponding command;

[0116] The RPC client program generates a message, puts the execution result data as a parameter into the message, and adds the corresponding code of the procedure to be called on the RPC server in the message;

[0117] The RPC client calls the local operating system network interface to send the message generated by the RPC client program to the RPC server via the SCADA system backbone network.

[0118] After receiving the message sent by the RPC client, the RPC server where the interface server is located acts as the RPC server and calls the local RPC server program.

[0119] The RPC server program analyzes the message, determines which procedure needs to be called based on the corresponding code in the message, and then executes the corresponding local call.

[0120] The RPC server performs local call analysis and execution results, and sends them to the GRPC client production management system through GRPC communication.

[0121] In this embodiment, in order to ensure that the instructions regarding SCADA content in the power outage process card control table are accurately executed after passing through the network, the switching card directory table within the SCADA system should allow the production management system to access or actively transmit it to the production management system to maintain the consistency of the instruction object names of both parties (the name within the SCADA system is used as the benchmark, and the production management system verifies and synchronizes with the benchmark).

[0122] To ensure consistent names between the two systems, the SCADA system incorporates a data synchronization function. This ensures that upon completion of tasks such as modifications to the SCADA remote control interface, the SCADA system automatically sends a synchronization command to the production management system database while the SCADA system maintenance personnel save the update. Upon receiving this command, the production management system immediately updates the relevant data within the database and then sends a successful update message to the SCADA system. The update process is considered complete only after the SCADA system receives this message. Furthermore, to ensure name consistency, the SCADA system database sends synchronization commands to the production management system database twice daily at fixed times (05:00 and 17:00). The production management system immediately updates the relevant data within its own database based on these commands.

[0123] The present embodiment discloses a method for autonomous concurrent program-controlled switching of electric power SCADA, comprising: before a program-controlled switching operation, a work area submits a work ticket and a switching ticket, and the dispatcher approves the operation after reviewing and verifying them; program-controlled cards are prefabricated according to a standardized switching procedure; on the day of the program-controlled switching operation, an operator applies to the dispatcher for a start-up authorization using a production management information system, and after the dispatcher agrees to the authorization, the work area autonomously performs the switching operation; before the switching operation officially begins, an inspection of the operating parameters of all relevant stations in the section is completed; after the inspection is normal, the operator inputs the corresponding switching operation step instruction, and the production management information system sends an operation command to the SCADA system to manually set the corresponding non-teleoperated switch on the interface, and the SCADA system immediately sets the switch on receipt and implements live deduction; after the inspection is normal, the operator sends an instruction to the SCADA system to call out the program-controlled card for switching the switch in the power substation; after the switching operation is completed, the SCADA system returns the execution result to the production management information system.

[0124] The present embodiment discloses a method for autonomous concurrent program-controlled switching of electric power SCADA, which can quickly understand the real-time topology of the power grid and perform a series of tasks such as optimized scheduling and fault diagnosis in the operation and management of the power system, thereby providing strong support for the business and application of the power supply scheduling system, and can play a great role in the implementation of power in the rail transit industry. The present invention uses scientific and technological means to solve the problems exposed in the switching operations of power substations, realizes the deep integration of the section production management information system and the conventional power SCADA system, adds safety control measures, prevents the misoperation of remote power switching operations, improves the reliability of equipment operation, promotes the safety of switching operations, solves the problem of the work group waiting too long to start work, saves operation time, improves efficiency, and has strong promotion value.

[0125] It should be understood that the specific order or hierarchy of steps in the disclosed processes is an example of an exemplary method. Based on design preferences, it should be understood that the specific order or hierarchy of steps in the process can be rearranged without departing from the scope of the present disclosure. The accompanying method claims present elements of the various steps in an exemplary order and are not intended to be limited to the specific order or hierarchy described.

[0126] In the foregoing detailed description, various features are grouped together in a single embodiment to simplify the disclosure. This method of disclosure should not be interpreted as reflecting an intention that embodiments of the claimed subject matter require more features than are expressly recited in each claim. On the contrary, as reflected in the appended claims, the invention comprises less than all the features of any individual disclosed embodiment. The appended claims are therefore hereby expressly incorporated into the detailed description, with each claim standing on its own as a separate preferred embodiment of the invention.

[0127] Those skilled in the art will also appreciate that the various illustrative logic blocks, modules, circuits, and algorithmic steps described in conjunction with the embodiments herein may be implemented as electronic hardware, computer software, or a combination thereof. In order to clearly illustrate the interchangeability between hardware and software, the various illustrative components, blocks, modules, circuits, and steps described above are generally described around their functions. Whether such functions are implemented as hardware or software depends on the specific application and the design constraints imposed on the entire system. A skilled person may implement the described functions in an adaptable manner for each specific application, but such implementation decisions should not be interpreted as departing from the scope of protection of this disclosure.

[0128] The steps of the methods or algorithms described in conjunction with the embodiments herein may be directly embodied as hardware, software modules executed by a processor, or a combination thereof. The software module may be located in a RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, register, hard disk, removable disk, CD-ROM, or any other form of storage medium well known in the art. An exemplary storage medium is connected to the processor so that the processor can read information from the storage medium and write information to the storage medium. Of course, the storage medium may also be an integral part of the processor. The processor and storage medium may be located in an ASIC. The ASIC may be located in a user terminal. Of course, the processor and storage medium may also be present in a user terminal as discrete components.

[0129] For software implementation, the techniques described in this application can be implemented using modules (e.g., procedures, functions, etc.) that perform the functions described in this application. These software codes can be stored in a memory unit and executed by a processor. The memory unit can be implemented within the processor or external to the processor. In the latter case, it is communicatively coupled to the processor via various means, which are well known in the art.

[0130] The foregoing description includes examples of one or more embodiments. Of course, it is not possible to describe all possible combinations of components or methods for the purposes of describing the above embodiments, but one of ordinary skill in the art will recognize that the various embodiments may be further combined and arranged. Therefore, the embodiments described herein are intended to encompass all such changes, modifications and variations that fall within the scope of the appended claims. Furthermore, to the extent the term "comprising" is used in the specification or claims, the term is intended to be encompassed in a manner similar to the term "including," as explained in terms of "including," used as a transitional word in the claims. Furthermore, any use of the term "or" in the specification of the claims is intended to mean a "non-exclusive or."

Claims

1. A method for autonomous and concurrent program-controlled switching of electric power SCADA, characterized in that: include: S100. Before a program-controlled switching operation, the work area submits a work ticket and a switching ticket. The dispatcher reviews and approves the operation after verification. S200. Prefabricated program control cards according to standardized switching procedures; S300. On the day of the program-controlled switching operation, the operator uses the production management information system to apply to the dispatcher for authorization to start work. After the dispatcher agrees to the authorization, the work area will independently perform the switching operation. S400. Before the official start of the switching operation, the operating parameters of all relevant stations in the section shall be inspected; S500. After the inspection is normal, the operator enters the corresponding switching operation step instruction, and the production management information system sends an operation command to the SCADA system to manually set the corresponding non-teleoperated switch on the interface. After receiving it, the SCADA system immediately sets it and realizes the live derivation; S600. After the inspection is normal, the operator sends a command to the SCADA system to call up the program control card for switching the switch in the power substation; after the switching operation is completed, the SCADA system returns the execution result to the production management information system.

2. A method for autonomous and concurrent program-controlled switching of electric power SCADA according to claim 1, characterized in that: In S200, the prefabricated programmable control card includes the steps of inspecting the telesignaling and telemetering values ​​of the booths at both ends of the section and each station, operating the high-voltage circuit breaker, operating and disabling the protection, and re-inspecting the telesignaling and telemetering values ​​of the booths at both ends of the section and each station after the operation; during actual operation, the work area issues a switching ticket based on the work ticket one day before the operation, and the steps in the switching ticket involving operating the switches of the unmanned power substation directly select the corresponding programmable control card number.

3. The method for autonomous and concurrent program-controlled switching of electric power SCADA according to claim 1, characterized in that: In S300, the user is authorized to start work through login authentication and authorization card. Login authentication is to verify the validity of the user. Only when the users on both sides are consistent can subsequent business operations be performed; authorization card is for manual authorization confirmation by program control. After the card authorization is successful, the production management system can initiate subsequent card requirements.

4. A method for autonomous and concurrent program-controlled switching of electric power SCADA as claimed in claim 3, characterized in that: When the production management system logs in to authenticate and authorize the card, it will send a request to the SCADA system. After receiving the request, the SCADA system returns the login or authorization token. If there is a network fluctuation and the production management system fails to obtain the authorization information, it will return the corresponding success token when requesting the SCADA system interface again.

5. The method for autonomous and concurrent program-controlled switching of electric power SCADA according to claim 1, characterized in that: In S400, inspection of the operating parameters of all relevant sites in the section is achieved through inspection cards. The specific method includes: the production management system sends a command to retrieve the inspection interface, waits for the SCADA system to return whether the conditions for executing the inspection command are met, and then sends the inspection command after confirming that the conditions for executing the inspection command are met. After receiving the execution command, the SCADA system automatically executes the inspection command. After the execution is completed, the result is displayed to the dispatcher in the form of a report, and the execution status result is returned to the production management system. The production management system background polls and retrieves the card execution status to confirm the execution result.

6. The method for autonomous and concurrent program-controlled switching of electric power SCADA according to claim 1, characterized in that: In S500, after the on-site operator actually operates the non-remote switch, the production management information system sends an operation command to the SCADA system to manually set the corresponding non-remote switch on the interface. After receiving the command, the SCADA system immediately sets the switch and displays a corresponding energized derivation diagram on the SCADA system HMI interface. The production management system can also obtain the setting result, and the SCADA system will return the result accordingly.

7. The method of autonomous concurrent program-controlled switching of electric power SCADA according to claim 1, characterized in that: In S600, the specific method for executing the program-controlled card includes: the production management system sends a command to call the program-controlled interface, waits for the SCADA system to return whether the command can be executed, and after confirming that the command can be executed, sends an execution program-controlled command. After receiving the execution command, the SCADA system automatically executes the program-controlled command, and after the execution is completed, returns the execution status result to the production management system. The production management system background polls and retrieves the card execution status to confirm the execution result.

8. The method for autonomous and concurrent program-controlled switching of electric power SCADA according to claim 1, characterized in that: The production management system and the SCADA system communicate and exchange information through GRPC. When the production management system has a demand request, the production management system is the client of GRPC, and the interface server in the SCADA system acts as the server of GRPC; when the SCADA system has information feedback to the production management system, the production management acts as the server of GRPC, and the interface server of the SCADA system acts as the client of GRPC.

9. The method for autonomous and concurrent program-controlled switching of electric power SCADA according to claim 1, characterized in that: The SCADA system uses binary remote procedure call method to transmit data internally, including two groups of RPC client and server communication interactions. One group is the interaction between the interface server as RPC client and the processing server as RPC server, and the other group is the interaction between the interface server as RPC server and the processing server as RPC client. The specific methods for interaction between the interface server acting as an RPC client and the processing server acting as an RPC server include: The interface server acts as an RPC client and calls the local RPC client program when it receives a request from the production management system; The RPC client program of the interface server generates a message, puts the required command data of the production management system into the message as a parameter, and adds the corresponding code of the process to be called on the processing server in the message; The interface server calls the local operating system network interface to send the message generated by the RPC client program to the processing server via the SCADA system backbone network; After receiving the message sent by the interface server, the processing server acts as the RPC server and calls the local RPC server program; The server-side program of the processing server analyzes the message, determines which procedure needs to be called based on the corresponding code in the message, and then executes the corresponding local call; The processing server executes a local call to analyze the command data and then executes the corresponding command.

10. The method for autonomous and concurrent program-controlled switching of electric power SCADA according to claim 9, characterized in that: The specific methods for interaction between the interface server acting as an RPC server and the processing server acting as an RPC client include: The processing server acts as another RPC client for communication and calls the local RPC client program after processing the corresponding command; The RPC client program generates a message, puts the execution result data as a parameter into the message, and adds the corresponding code of the procedure to be called on the RPC server in the message; The RPC client calls the local operating system network interface to send the message generated by the RPC client program to the RPC server via the SCADA system backbone network. After receiving the message sent by the RPC client, the RPC server where the interface server is located acts as the RPC server and calls the local RPC server program. The RPC server program analyzes the message, determines which procedure needs to be called based on the corresponding code in the message, and then executes the corresponding local call. The RPC server performs local call analysis and execution results, and sends them to the GRPC client production management system through GRPC communication.

Images