WO2013162090A1

WO2013162090A1 - Middleware for controlling failure endurance of wind power generation control system

Info

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

Abstract

Provided is a plan for controlling failure endurance of a wind power generation control system. A program for controlling failure endurance of the wind power generation control system, according to the present invention, comprises: a plurality of components for supporting the execution of applications which are used in the wind power generation control system; and a middleware for monitoring failure of the components through communication with the components. As a result, failure endurance of the wind power generation control system can be controlled, thereby preventing in advance discontinuation of power generation and unstable power generation.

Description

Middleware for fault tolerance control of wind power generation control system

The present invention relates to a wind power generation control system, and more particularly to a middleware for controlling the tolerance to the failure generated 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.

SUMMARY OF THE INVENTION The present invention has been made to solve the above problems, and an object of the present invention is to provide a computer-readable recording medium containing a program for controlling the tolerance for a failure occurring in a wind power generation control system. .

According to the present invention for achieving the above object, a computer-readable recording medium comprising: a plurality of components for supporting the execution of applications used in the wind power generation control system; And middleware for monitoring faults of the components through communication with the components. The program for fault tolerance control of the wind power generation control system is included.

In addition, the plurality of components may include: a first component that does not require backup of work data in order to transfer a work that was being performed due to a failure to another component; And at least one second component required to back up data on the working environment in order to transfer the work that was being performed due to the failure to another component.

In addition, the program for the fault tolerance control of the wind power generation control system, the plurality of components, may further include at least one third component that is not currently performing work.

The middleware may store information on an application running in the at least one second components and work data for the at least one second components.

The program for fault tolerance control of the wind power generation control system may further include a hypervisor that allocates and manages hardware resources used in the wind power generation control system to the plurality of components. The middleware may include the plurality of middleware. It may provide an interface between the components of and the hypervisor.

The job data may be data requested by the at least one second component to the hypervisor.

The middleware may designate one of the plurality of components as the first component.

On the other hand, the fault tolerance control method of the wind power generation control system according to the present invention, the middleware communication with a plurality of components for supporting the execution of applications used in the wind power generation control system; And monitoring, by the middleware, failure of the components through communication in the communication step.

As described above, according to the present invention, it is possible to control the tolerance for failures generated in the wind power generation control system, thereby preventing 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 an applicable wind power generation control system according to an embodiment of the present invention,

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 diagram illustrating an RC management table, and

5 is a diagram illustrating an application management table.

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 control system according to an embodiment of the present invention. The wind power generation control system according to the present embodiment 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 according to the present embodiment is a high availability failure 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.

On the other hand, the restoration by the system control manager 135 depends on the type of the failed RC.

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

1) Specify another available RC (for example, a RC that is currently not doing anything) or a newly created RC as GRC,

2) From the table of the watchdog manager 137, which will be described later, identify the applications that were running in the failed GRC and request to execute the newly designated GRC.

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 and requests to execute the applications identified in another available RC or newly created RC,

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.

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.

On the other hand, in the wind power control system shown in Figure 1 components other than the hardware 150 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

A plurality of components for supporting execution of applications used in the wind power control system; And

And middleware for monitoring the failure of the components through communication with the components. The computer-readable recording medium containing a program for controlling the fault tolerance of the wind power generation control system.
The method of claim 1,

The plurality of components,

A first component that is not required to back up work data in order to hand over work that was being performed due to a failure to another component; And

In order to transfer the work being performed due to the failure to another component, at least one second component that is required to back up the data on the working environment; for the fault tolerance control of the wind power generation control system comprising a Computer-readable recording medium containing the program.
The method of claim 2,

The plurality of components,

At least one third component that is not currently performing the work; Computer-readable recording medium containing a program for the fault tolerance control of the wind power generation control system further comprising.
The method of claim 2,

The middleware,

Computer for storing the program for the fault tolerance control of the wind power generation control system, characterized in that for storing information about the application running in the at least one second component and the operation data for the at least one second component. Recordable media that can be read by
The method of claim 4, wherein

And a hypervisor for allocating and managing hardware resources used in the wind power generation control system to the plurality of components.

The middleware,

And a program for controlling the fault tolerance of the wind power generation control system, characterized by providing an interface between the plurality of components and the hypervisor.
The method of claim 5,

The job data,

And the at least one second component is data requested to the hypervisor. The computer-readable recording medium having a program for controlling the fault tolerance of the wind power generation control system.
The method of claim 1,

The middleware,

And a program for controlling the fault tolerance of the wind power generation control system, wherein one of the plurality of components is designated as the first component.
Communicating by the middleware with a plurality of components to support execution of applications used in the wind power control system; And

And monitoring the failure of the components by the middleware through the communication in the communication step.