WO2013162089A1

WO2013162089A1 - Method for recovering failure of wind power generation control system

Info

Publication number: WO2013162089A1
Application number: PCT/KR2012/003161
Authority: WO
Inventors: 김영환; 함경선; 황태호; 손재기
Original assignee: 전자부품연구원
Priority date: 2012-04-25
Filing date: 2012-04-25
Publication date: 2013-10-31

Abstract

Provided is a method for recovering failure of a wind power generation control system. The method for recovering failure of the wind power generation control system monitors problems occurring in a plurality of components for supporting execution of applications, which are used in the wind power generation control system, and recovers work of a component from which the problem occurred in a different component. As a result, a problem occurring in the wind power generation control system can be automatically resolved, thereby preventing in advance discontinuation of power generation and unstable power generation.

Description

How to recover from wind power generation control system

The present invention relates to a wind power generation control system, and more particularly, to a method for enduring and recovering from a failure occurring in the wind power generation control system.

Advances in IT technology have exploded the power consumption of devices operated by electricity in modern society. This has led to increased demand for fossil fuels and increased costs for electricity use.

However, in order to cope with the increasing demand for electricity, the focus on environmentally friendly renewable energy has been focused on the environmental problems of limited fossil fuel and carbon emissions, which are the main causes of air pollution.

Among renewables, wind energy is growing rapidly around the world, and wind power capacity has grown at an average annual rate of over 30% over the past decade. This growth is made possible by many advantages, such as low cost, indefinite, clean and green.

Currently, many wind power generators are installed in coasts and mountains where winds are windy not only in Korea but also abroad. Due to environmental factors such as vibration and electromagnetic noise, and software and hardware problems of controllers controlling wind turbines A lot of money is being spent.

The present invention has been made to solve the above problems, an object of the present invention is to provide a method for recovering a wind power generation control system that can automatically solve the problems occurring in the wind power generation control system.

According to the present invention for achieving the above object, a method for recovering a wind power generation control system includes: monitoring a problem occurrence of a plurality of components to support execution of applications used in the wind power generation control system; And restoring the work of the component, which has been identified as a problem, through the monitoring step to another component.

The monitoring may include identifying a component that does not receive a specific signal periodically received from the plurality of components as a component that has a problem.

In addition, the method for recovering a wind power generation control system includes: searching for a component capable of performing a task of a component having a problem among the plurality of components; And restoring the work of the component in which the problem occurred in the component found in the searching step.

In addition, the wind power generation control system recovery method may include: generating a new component if a component capable of performing a task of a component having a problem in the searching step is not found; And restoring the work of the component in which the problem occurs in the new component generated in the generating step.

In addition, the method for recovering the wind power generation control system may further include storing work environments being performed in the plurality of components, wherein the restoring step includes the work of the failed component among the work environments stored in the storing step. It is preferable to perform the restoration with reference to the environment.

The work environment may include information about at least one application that is being executed in the component and work data that is being processed through the at least one application.

In addition, the information on the application and the job data may be stored and managed by different managers.

On the other hand, according to the present invention, a computer-readable recording medium comprising: monitoring the occurrence of a problem of a plurality of components to support the execution of applications used in the wind power generation control system; And restoring the work of the component, which has been identified as a problem, through the monitoring step to another component. The program capable of performing the method for recovering a wind power control system, comprising: a.

As described above, according to the present invention, it is possible to automatically solve the problems occurring in the wind power generation control system, it is possible to prevent the power generation interruption and unstable power generation in advance. In addition, maintenance can be prevented, resulting in a reduction in maintenance costs.

In addition, it is possible to prevent a problem occurring in one part of the wind power generation control system from expanding to another part.

1 is a view showing the structure of a wind power generation control system to which the present invention is applicable;

2 is a diagram illustrating a structure of a packet transmitted by RC;

3 shows the structure of a database for job data;

4 is a view illustrating an RC management table;

5 shows an application management table, and

6 is a flowchart provided to explain a method for recovering from a failure in a wind power generation control system according to an exemplary embodiment of the present invention.

Hereinafter, with reference to the drawings will be described the present invention in more detail.

1 is a view showing the structure of a wind power generation control system to which the present invention is applicable. The wind power generation control system shown in FIG. 1 corresponds to a system for controlling any one of the facilities (blade, wind turbine, generator, etc.) constituting the wind power generator.

The wind power generation control system shown in FIG. 1 is a high availability fault tolerance control system designed to automatically recover from failures to withstand various failures that may occur.

As shown in FIG. 1, a wind power generation control system performing such a function includes a plurality of applications 110-1 to 110 -M, a plurality of RCs 120-1 to 120 -N, and an FTSM ( 130, hypervisor 140, and hardware 150.

The applications 110-1 to 110 -M are applications that perform a function required for wind power control.

Redundancy Components (RCs) 120-1 through 120-N are components that support the execution of applications 110-1 through 110-M. In the RCs 120-1 to 120-N, daemons 125-1 to 125-N are provided to periodically transmit their operating states to the watchdog manager 137 of the FTSM 130, which will be described later. do.

RCs 120-1 through 120 -N are managed by FTSM 130. Meanwhile, the RCs 120-1 to 120 -N are divided into a general redundancy component (GRC) 120-1 and critical redundancy components (CRCs) 120-2 to 120 -N.

The GRC 120-1 is a component that does not require backup data when transferring a job that is being performed to another component. That is, the GRC 120-1 may be regarded as a component that performs a task that does not require data backup.

Here, when it is necessary to transfer the work being performed to another component, a problem such as a failure or an error occurs in the GRC 120-1.

The CRCs 120-2 to 120 -N are components that require backed up job data when transferring a job that is being performed to another component. That is, the CRCs 120-2 to 120 -N may be regarded as a component that performs a job requiring a backup of job data.

Work data backup is necessary to restore the state of the wind power generation control system to the state before the problem, in order to ensure the durability of the operation of the wind power generation control system.

Fault-Tolerant Service Middleware (FTSM) 130 provides an interface between the RCs 120-1 through 120 -N and the hypervisor 140. In this case, communication between the FTSM 130 and the RCs 120-1 to 120 -N may be performed according to TCP / IP.

In addition, the FTSM 130 is a high availability middleware employing a redundancy component technique and a backup data backup technique of the CRCs 120-2 to 120 -N to recover a failure of the wind power control system.

As shown in FIG. 1, the FTSM 130 includes a network interface manager 131, a data manager 133, a system control manager 135, and a watchdog manager 137.

The

managers

133, 135, and 137 constituting the FTSM 130 may communicate with each other through IPC.

The network interface manager (NIM) 131 provides an interface for data transfer with the RCs 120-1 to 120 -N and data transfer between the

managers

133, 135, and 137.

The network interface manager 131 receives / analyzes the packet transmitted by the RCs 120-1 to 120-N and delivers the packet to the corresponding manager that should receive the packet.

2 illustrates a structure of a packet transmitted by the RCs 120-1 to 120 -N. As shown in FIG. 2, the packet transmitted by the RCs 120-1 to 120 -N includes an RC # field, a Manager field, and a Request field.

1) The RC # field is a field containing the RC number (#m) of transmitting a packet, 2) the Manager field is a field containing a manager to receive the packet, and 3) a request is one of the functions provided by the manager. Corresponds to the field that contains the functionality that the RC wants to request.

The data manager 133 is a manager for backing up work data of the CRCs 120-2 to 120 -N. The job data is classified and stored for each of the CRCs 120-2 to 120 -N.

Specifically, the data manager 133 stores the data requested by the CRCs 120-2 to 120 -N to the hypervisor 140 to be described later along with the request time, and the stored request data corresponds to the job data. .

In order to identify the data requested by the CRCs 120-2 through 120-N to the hypervisor 140, all packets transmitted from the CRCs 120-2 through 120-N to the hypervisor 140 are all data. It may be implemented to be delivered through the manager 133.

In addition, for storing, retrieving, and extracting work data, the data manager 133 includes a repository, and builds a database for work data.

The structure of the database for job data is shown in FIG. As shown in FIG. 3, the database for working data includes an RC # field, a Time field, a Type field, a Data Size field, and a Data field.

1) The RC # field is a field in which the number (#m) of the RC that has requested data from the hypervisor 140 is stored. 2) The Time field is a field containing a data request time. 3) The Type field is a type of data. (Eg, wind direction data, temperature data, etc.), and 4) the Data Size field is a field in which the size of data is stored, and 5) the Data field is a field in which actual data is stored.

The system control manager 135 is a manager that performs management / control such as creation, removal, and recovery of the RCs 121-1 to 120-N.

Specifically, the system control manager 135 assigns priorities to the RCs 121-1 to 120-N, respectively, and designates the RC with the highest priority as the GRC 120-1. In addition, IPs are dynamically allocated to the RCs 121-1 through 120 -N for data communication between the RCs 121-1 through 120 -N and the FTSM 130.

In addition, the system control manager 135 restores the work that was being performed in the RC that cannot perform the work due to a problem to another RC. Upon restoration, the system control manager 135 may 1) store information on the 'applications that were running in the RC where the problem occurred' stored in the watchdog manager 137 to be described later, and 2) the 'problem stored in the data manager 133. Uses the generated RC's work data. The failure recovery process by the system control manager 135 will be described later in detail with reference to FIG. 6.

The watchdog manager 137 monitors the states of the RCs 121-1 through 120 -N. To this end, the watchdog manager 137 periodically receives a heartbeat signal from the daemons 125-1 to 125-N provided in the RCs 121-1 to 120-N, respectively.

If there is an RC that does not transmit the heartbeat signal for the period, the watchdog manager 137 determines that the RC has a problem. If a problem RC occurs, the watchdog manager 137 notifies the system control manager 135 of the fact.

In addition, the watchdog manager 137 receives information about applications running in the RCs 121-1 to 120 -N, creates a table along with the states of the RCs, and manages the same.

4 is a diagram illustrating an RC management table. As shown in FIG. 4, the RC management table includes an RC # field, an IP field, a status field, and an application field.

1) The RC # field is a field that contains the RC number. 2) The IP field is a field that contains the IP address assigned to the RC of the number listed in the RC # field. 3) The Status field is stored in the RC # field. 4) The Application field is a field that contains information on applications running in the RC of the number included in the RC # field.

In addition, the watchdog manager 137 receives information on operating states of applications running in the RCs 121-1 to 120 -N, prepares and manages the information in a table.

5 is a diagram illustrating an application management table. As shown in FIG. 5, the application management table includes an RC # field, an Application field, a CPU% field, a MEM% field, and a Stat field.

1) The RC # field is a field that contains the RC number. 2) The Application field is a field that contains information about the application running in the RC of the number listed in the RC # field. 3) The CPU% field is an Application field. 4) The MEM% field is a field that contains the CPU share of the application listed in the Application field, and 5) the Stat field is a field that contains the process operation state of the application listed in the Application field.

The hyper visor 140 allocates and manages the hardware 150 resources used in the wind power control system to the RCs 121-1 to 120-N.

Hereinafter, a process of repairing a failure occurring in the wind power generation control system shown in FIG. 1 will be described in detail with reference to FIG. 6. 6 is a flowchart provided to explain a method for recovering from a failure in a wind power generation control system according to an exemplary embodiment of the present invention.

As shown in FIG. 6, while the RCs 120-1 to 120 -N are performing the operation (S210), a watchdog manager (WM) 137 and a data manager (FTSM 130) of the FTSM 130 are provided. Data Manager (DM) 133 stores the working environment of the RCs 120-1 to 120-N (S220).

Specifically, the watchdog manager 137 receives information about applications running in the RCs 121-1 through 120 -N and stores the information in a table, and the data manager 133 stores the CRCs 120-2 through the data. 120-N) stores the work data requested by the hypervisor 140 in a database, and the stored application information and the work data correspond to the work environment.

Meanwhile, the watchdog manager 137 monitors the states of the RCs 121-1 to 120 -N and detects whether a failure occurs in the RCs 121-1 to 120 -N (S230). In step S230, the watchdog manager 137 determines whether the heartbeat signal is periodically received from the daemons 125-1 to 125-N provided in the RCs 121-1 to 120-N, respectively. Is performed by.

If a failure is detected in any one of the RCs 121-1 to 120-N in step S230 (S230-Y), the watchdog manager 137 notifies the system control manager 135 of the failed RC (S240). .

Then, the system control manager 135 searches for another available RC (S250). If another available RC is found in step S250 (S260-Y), the system control manager 135 restores the work being performed in the failed RC to the searched RC (S280).

The other available RC retrieved in step S260 may be a spare RC, which is an RC that is not currently performing any work.

On the other hand, if there is no other RC available in step S260 (S260-N), the system control manager 135 creates a new RC (S270), and restores the work being performed in the failed RC to the newly created RC (S280). .

Restoration at step S280 is dependent on the type of RC that failed.

If the failed RC is GRC, the system control manager 135

1) In step S260, the RC created in the search or step S270 is designated as GRC,

2) From the table of the watchdog manager 137, identify the applications that were running in the failed GRC and request that the newly designated GRC be executed.

3) Remove the broken GRC

The restoration is performed by the process.

On the other hand, if the broken RC is a CRC,

1) The system control manager 135 identifies the applications that were running in the failed CRC from the table of the watchdog manager 137, requests to execute the applications identified in the RC generated in the search or the S270 in step S260,

2) The executed applications extract work data of the failed CRC from the database of the data manager 133,

3) The system control manager 135 removes the broken GRC.

The restoration is performed by the process.

On the other hand, the fault recovery method of the wind power generation control system shown in FIG. 6 may be implemented as a computer program.

In addition, although the preferred embodiment of the present invention has been shown and described above, the present invention is not limited to the specific embodiments described above, but the technical field to which the invention belongs without departing from the spirit of the invention claimed in the claims. Of course, various modifications can be made by those skilled in the art, and these modifications should not be individually understood from the technical spirit or the prospect of the present invention.

Claims

Monitoring problem occurrences of a plurality of components to support execution of applications used in the wind power control system; And

Restoring the work of the component that is identified as a problem through the monitoring step to another component; Wind power control system recovery method comprising a.
The method of claim 1,

The monitoring step,

Identifying a component that does not receive a specific signal periodically received from the plurality of components as a component that has a problem; wind power control system recovery method comprising a.
The method of claim 1,

Searching for a component capable of performing a task of a component having a problem among the plurality of components; And

Restoring the work of the component in which a problem occurs in the component found in the search step; Wind power control system recovery method further comprising.
The method of claim 3,

Generating a new component if a component that can perform a task of a component having a problem in the searching step is not found; And

Restoring the work of the component in which a problem occurs in the new component generated in the generating step; Wind turbines control system recovery method further comprising.
The method of claim 1,

Storing working working environments in the plurality of components;

The restoration step,

Wind turbines control system recovery method characterized in that for performing the restoration with reference to the work environment of the broken component of the work environment stored in the storing step.
The method of claim 5,

The working environment,

And information about at least one application that was running in the component and job data that is being processed through the at least one application.
The method of claim 6,

The information about the application and the job data,

Wind turbine control system recovery method characterized in that stored and managed by different managers.
Monitoring problem occurrences of a plurality of components to support execution of applications used in the wind power control system; And

Restoring the work of the component that is identified as a problem through the monitoring step to another component; a computer-readable record containing a program that can perform a method for recovering a wind power control system, comprising: media.