KR20240057224A - API Gateway System and Method of Performing API Service between Heterogeneous Networks - Google Patents

Abstract

The API gateway system between heterogeneous networks of the present invention includes a power generation company relay server and a data center relay server that perform KAFKA (distributed event streaming) communication to collect data messages about power generation operation; A power generation API gateway server that converts request information for the API service from an API message to a KAFKA (Distributed Event Streaming) message and converts result information for the API service from a KAFKA (Distributed Event Streaming) message to an API message; and a DataSensor API Gateway server that converts request information for the API service from a KAFKA (Distributed Event Streaming) message to an API message, and converts result information for the API service from an API message to a KAFKA (Distributed Event Streaming) message. You can.

Description

API Gateway System and Method of Performing API Service between Heterogeneous Networks}

The present invention relates to an API gateway system between heterogeneous networks with security restrictions and a method of performing an API service performed thereon.

The five power generation companies that operate standard coal-fired power plants in Korea (hereinafter referred to as the ‘Five Power Generation Companies’) each operate an independent business network, so it is impossible to link and share data between power generation companies, so failure cases, facility improvement, and fuel characteristics are not possible. It was not possible to jointly use important driving information such as

To solve this problem, KEPCO established the Intelligent Digital Power Plant (IDPP) integrated data center (hereinafter “IDPP Data Center”) in March 2022 and is collecting and managing the power generation operation information of five power generation companies.

Various data such as 'turbine cleaning cycle optimization', 'power generation facility early warning', and 'boiler damage monitoring' are derived by analyzing the data of the five power generation companies stored in the IDPP data center mentioned above and applying the results to each power generation facility to derive the optimal solution. Intelligent application SW (hereinafter referred to as ‘IDPP Intelligent App’) is continuously being researched, developed and operated.

If data such as operation know-how and failure cases of power generation companies are shared with each other through the IDPP intelligent app, it is expected to improve the operation efficiency of power generation facilities, reduce various maintenance costs, as well as reduce national greenhouse gases and improve power supply reliability.

However, there are strong security restrictions between the power generation company and the IDPP data center network, so general data communication between the operating system within the power generation company and the IDPP intelligent app installed in the IDPP data center is limited, and conventional technologies include World Wide Web (www) communication or Rest IDPP intelligent app service cannot be provided remotely using API.

Republic of Korea Registration Publication No. 10-1180375

The present invention seeks to provide an API gateway system between heterogeneous networks that enables remote API service provision between a system installed/operating in a power generation network with strong security restrictions and an intelligent application (App) system installed/operating in an integrated data center network. do.

An API gateway system between heterogeneous networks according to an aspect of the present invention includes a power generation company relay server and a data center relay server that perform KAFKA (distributed event streaming) communication to collect data messages about power generation operation; A power generation API gateway server that converts request information for the API service from an API message to a KAFKA (Distributed Event Streaming) message and converts result information for the API service from a KAFKA (Distributed Event Streaming) message to an API message; and a DataSensor API Gateway server that converts request information for the API service from a KAFKA (Distributed Event Streaming) message to an API message, and converts result information for the API service from an API message to a KAFKA (Distributed Event Streaming) message. You can.

Here, the KAFKA message includes a Topic consisting of type, power generation company name, and App ID; and Data may be included as request data or response result information required by the Topic.

Here, in the case of the KAFKA message converted from the API message, the power generation company API gateway and the data sensor API gateway may set the priority of the corresponding Topic (type) lower than that of other general KAFKA messages.

Here, the power generation company API gateway server includes an API Gateway that provides services such as authentication/authorization and routing to request/response to other modules on the network and a predetermined API service; And it may include a KAFKA-API message conversion module that converts the API service request/response signal into a KAFKA message to proceed with the subsequent process.

Here, the data sensor API gateway server includes an API Gateway that provides services such as authentication/authorization and routing so that other modules on the network can request/response to certain API services; And it may include a KAFKA-API message conversion module that converts the API service request/response signal into a KAFKA message to proceed with the subsequent process.

An intelligent power plant platform according to another aspect of the present invention includes a power generation company relay server that performs KAFKA communication to collect data messages about power generation operation; And it may include a power generation company API gateway server that converts request information for the API service from an API message to a KAFKA message and converts result information for the API service from a KAFKA message to an API message.

An IDPP integrated data center according to another aspect of the present invention includes a data center relay server that performs KAFKA communication to collect data messages about power generation operation; And it may include a data center API gateway server that converts request information for the API service from a KAFKA message to an API message, and converts result information for the API service from an API message to a KAFKA message.

A method of performing an API service between heterogeneous networks according to another aspect of the present invention includes the steps of requesting an API service from an API client to an API gateway of a power generation company; Converting the API service request into a KAFKA message at the power generation company API gateway; Transmitting the API service request converted into a KAFKA message from the power generation company relay server to the data center relay server; And a step where the data center API gateway server receives the API service request from the data center relay server, converts it from a KAFKA message to an API message, and transmits it to the API server of the corresponding API service.

Here, the data center API gateway receives an API service response to the API service request from the API server and converts it into a KAFKA message; Transmitting the API service response converted into a KAFKA message from the data center relay server to the power generation company relay server; And the power generation company API gateway may further include converting the API service response received from the power generation company relay server into an API message and transmitting it to the API client.

Here, the KAFKA message includes a Topic consisting of type, power generation company name, and App ID; and Data may be included as request data or response result information required by the Topic.

Here, in the step of converting the API service request into a KAFKA message, the priority of the topic can be set lower than that of other general KAFKA messages.

Here, in the step of receiving the API service response and converting it into a KAFKA message, the priority of the topic can be set lower than that of other general KAFKA messages.

When the API gateway system between heterogeneous networks according to the idea of the present invention of the above-described configuration is implemented, between a system installed/operating in a power generation network with strong security restrictions and an intelligent application (App) system installed/operating in an integrated data center network. It has the advantage of expanding the usability of intelligent apps by enabling the provision of remote API services.

The API gateway system between heterogeneous networks of the present invention utilizes a power generation operation data message collection communication method rather than a general API communication method, enabling the implementation of a remote API service with enhanced security between heterogeneous networks that is safe from DDoS, IP packet forgery, etc. There is an advantage.

1A and 1B are configuration diagrams of an API service system module between heterogeneous networks with security restrictions.
Figure 2 is a flowchart illustrating an embodiment of a method for performing an API service between heterogeneous networks.
Figure 3 is a message configuration diagram for a KAFKA message converted to an API service request/response signal applied during the process according to the above-described flowchart.
Figure 4 is a connection diagram of a power generation operation information integrated data center that builds an API gateway system between heterogeneous networks according to the idea of the present invention.

In describing the present invention, terms such as first and second may be used to describe various components, but the components may not be limited by the terms. Terms are intended only to distinguish one component from another. For example, a first component may be referred to as a second component, and similarly, the second component may be referred to as a first component without departing from the scope of the present invention.

When a component is mentioned as being connected or connected to another component, it can be understood that it may be directly connected to or connected to the other component, but other components may exist in between. .

The terms used in this specification are merely used to describe specific embodiments and are not intended to limit the invention. Singular expressions may include plural expressions, unless the context clearly indicates otherwise.

In this specification, terms such as include or have are intended to designate the presence of features, numbers, steps, operations, components, parts, or combinations thereof described in the specification, including one or more other features or numbers, It can be understood that the existence or addition possibility of steps, operations, components, parts, or combinations thereof is not excluded in advance.

Additionally, the shapes and sizes of elements in the drawings may be exaggerated for clearer explanation.

The present invention presents an API Gateway system and method for remote API service requests and responses between SW modules installed in heterogeneous networks with strict security restrictions. More specifically, a method was prepared to transmit and receive REST API packet data for application services through the KAFKA communication channel established for power plant management.

1A and 1B are configuration diagrams of an API service system module between heterogeneous networks with security restrictions.

In order to solve the above-mentioned problems, the present invention presents a system and method for IDPP intelligent App remote service on the KAFKA communication network, a heterogeneous network with strong security restrictions between power generation companies and KEPCO, as shown in Figures 1a and 1b.

The illustrated API gateway system between heterogeneous networks includes a power generation company relay server 300 and a data center relay server 600 that perform KAFKA (distributed event streaming) communication to collect data messages about power generation operation; A power generation API gateway server 200 that converts request information for the API service from an API message to a KAFKA (Distributed Event Streaming) message and converts result information for the API service from a KAFKA (Distributed Event Streaming) message to an API message; and a data sensor API gateway server 700 that converts request information for the API service from a KAFKA (Distributed Event Streaming) message to an API message, and converts result information for the API service from an API message to a KAFKA (Distributed Event Streaming) message. may include.

The API Gateway (G/W) (220, 720) provided in the power generation company API gateway server 200 and the data sensor API gateway server 700, respectively, connects to different networks on the SW module (endpoint) such as the web or App. It is a middleware that provides services such as authentication/authorization and routing so that API services such as data or calculation processing can be requested/responsed by SW modules. It is an essential service for joint use by power generation companies of the IDPP intelligent app installed and operated in the IDPP data center. /It is a facility.

However, according to the results of the security review by the host organization, the IDPP data center network and the power generation company network of the intelligent power plant platform used by each power generation company are composed of the relay server 300 and the firewall 500 as shown in Figure 1a, and the message Data communication through methods and protocols other than middleware (KAFKA) 620 is not possible, and API G/W service execution is impossible using conventional methods. There is a need for a system configuration and implementation plan for API services to remotely provide IDPP intelligent app services between heterogeneous networks with severe security restrictions.

The 'KAFKA-API message conversion module' (240, 740) is a module that converts the API service request/response signal into a KAFKA message and proceeds with the subsequent process. It 'converts the API request signal into a KAFKA message' and 'KAFKA response It is configured to perform the function of ‘converting a message into an API response signal.’

The API service requester (App or Web SW module) 100 of the power generation company network transmits an API service request signal (REST API) to the API G/W server 200 of the IDPP platform, which is transmitted to the API G/W server 200. It is converted into a KAFKA message including Topic ('API') information defined through the 'KAFKA-API message conversion module 240. This message is delivered in the form of a Producer to the Relay Server (300) within the power generation company, which in turn is delivered to the Relay Server (600) Consumer of the IDPP data center. The API G/W server 700 of the IDPP data center receives the message in the form of a Consumer for the defined Topic (‘API’) and converts it back into an API request signal. The converted API request signal is transmitted to the API service provider (IDPP intelligent app module) 800 through the API G/W service module 720.

The API service provider 800 transmits a response signal to the API G/W server 700 for the result of app execution in response to the request, which sends the API response signal to the API requester 100 within the power generation company through the reverse order of the steps described above. delivered in the form

Through the system and method of the present invention as illustrated in Figures 1a and 1b, the operating system within each power generation company can use the API service of the IDPP intelligent app installed and operated in the IDPP data center in the form of the same REST API as the existing method. do.

Here, the KAFKA message includes a Topic consisting of type, power generation company name, and App ID; and Data as request data or response result information required by the Topic. Specific examples of this will be described later.

Since the general KAFKA message is related to power plant operation/control/monitoring, it may be urgent in power plant operation, while the KAFKA message converted from the API message according to the idea of the present invention is a kind of application service for the API service, so it is a general It may have less urgency than the KAFKA message.

Considering the above-mentioned circumstances, the power generation company API gateway server 200 and the data sensor API gateway server 700, in the case of a KAFKA message converted from the API message, determine the priority of the corresponding Topic (more specifically, type). can be set lower than other general KAFKA messages.

Meanwhile, as shown in FIG. 1A, the intelligent power plant platform includes a power generation company relay server 300 that performs KAFKA (distributed event streaming) communication to collect data messages about power generation operation; and a power generation API gateway server 200 that converts request information for the API service from an API message to a KAFKA (Distributed Event Streaming) message and converts result information for the API service from a KAFKA (Distributed Event Streaming) message to an API message. It can be defined as including.

Likewise, the IDPP integrated data center shown in Figure 1b includes a data center relay server 600 that performs KAFKA (distributed event streaming) communication to collect data messages about power generation operation; and a data center API gateway server 700 that converts request information for the API service from a KAFKA (Distributed Event Streaming) message to an API message, and converts result information for the API service from an API message to a KAFKA (Distributed Event Streaming) message. It can be defined as including.

Figure 2 is a flowchart illustrating an embodiment of a method for performing an API service between heterogeneous networks. The illustrated flow chart represents the flow of calling an API service request, converting a message, and receiving a result.

The illustrated method of performing an API service between heterogeneous networks includes the steps of requesting an API service from the API client 100 to the power generation company API gateway server 200 (S10); Converting the API service request into a KAFKA message at the power generation company API gateway server 200 (S20); Transmitting the API service request converted into a KAFKA message from the power generation company relay server 300 to the data center relay server 600 (S30); The data center API gateway server 700 receives the API service request from the data center relay server 600 (S40), converts it from a KAFKA (distributed event streaming) message to an API message, and converts it into an API message for the corresponding API service. Transferring to (800) (S50); The data center API gateway server 700 receives an API service response to the API service request from the API server 800 (S60) and converts it into a KAFKA message (S70); Transmitting the API service response converted into a KAFKA message from the data center relay server 600 to the power generation company relay server 300 (S80); And the power generation company API gateway server 200 may include converting the API service response received from the power generation company relay server 300 (S90) into an API message and transmitting it to the API client 100 (S95). there is.

We will explain each process of the proposed API service request - conversion - delivery - result reception, which is implemented according to the illustrated procedure.

In the illustrated step S10, the API service requester 100 requests an API service for the IDPP intelligent app through the power generation company API G/W server 200 in the power generation company intelligent power plant (IDPP) platform.

In the illustrated step S20, the power generation company API G/W server 200 converts the received API service request signal into a KAFKA message including defined Topic information (described later in FIG. 3) and sends it to the power generation company relay server (KAFKA) 300. Send it in the form of Producer.

In the illustrated step S30, the power generation company relay server 300 transmits the corresponding KAFKA message to the IDPP data center relay server 600.

In the illustrated step S40, the IDPP data center API G/W server 700 receives a message in the form of a consumer from the relay server 600.

In the illustrated step S50, the IDPP data center API G/W server 700 converts the KAFKA message into an API request signal and requests a service from the IDPP intelligent App API service provider 800.

In step S60, the API service provider 800 provides a service response to the API G/W server 700 of the IDPP data center.

In the illustrated step S70, the IDPP data center API G/W server 700 converts the received API response signal into a KAFKA message including defined topic information and transmits it to the IDPP data center relay server 600 in the form of a producer. .

In the illustrated step S80, the IDPP data center relay server 600 transmits a message about the service response to the power generation company relay server 300.

In the illustrated step S90, the power generation API G/W server 200 receives a message in the form of a consumer from the relay server 300.

In the illustrated step S95, the power generation company API G/W server 200 converts the KAFKA message into an API response signal and returns it to the API service requester 100.

Figure 3 is a message configuration diagram for a KAFKA message converted to an API service request/response signal applied during the process according to the above-described flowchart.

KAFKA messages are composed of Topic and Data. Topic consists of type, generator name, and App ID, and data is request data or response result information required by the topic.

The KAFKA-API message conversion module of the API G/W server can generate a message including type, power generation company name, App ID, and data information according to API information for API service request and response signals. An example of a KAFKA message generated in this way is shown in Table 1 below.

When performing the method of performing the API service between heterogeneous networks in FIG. 2 according to the KAFKA message configuration in FIG. 3, in the step of converting the API service request into a KAFKA message (S20), the priority of the topic is set over other general KAFKA messages. It can be set low.

Likewise, in the step (S70) of receiving the API service response shown in FIG. 2 and converting it into a KAFKA message, the priority of the topic can be set lower than that of other general KAFKA messages.

Figure 4 is a connection diagram of a power generation operation information integrated data center that builds an API gateway system between heterogeneous networks according to the idea of the present invention.

The connection configuration shown is centered around a data center that installs and demonstrates the “intelligent digital power plant platform” at five power generation companies and can store and manage large-scale power generation operation information based on the data platform that constitutes the intelligent digital power plant platform.

In the case of the API gateway system between heterogeneous networks according to the connection configuration of FIG. 4, an example of an API service to which the present invention can be applied and implemented according to the idea is a notification service for the remaining life of power generation equipment of each power plant and fuel in the case of a coal-fired power plant. One example is a service that provides optimization algorithms based on mixing ratio (i.e., mixing ratio for each type of coal).

Those skilled in the art to which the present invention pertains should understand that the present invention can be implemented in other specific forms without changing its technical idea or essential features, and that the embodiments described above are illustrative in all respects and not restrictive. Just do it. The scope of the present invention is indicated by the claims described later rather than the detailed description, and all changes or modified forms derived from the meaning and scope of the claims and their equivalent concepts should be construed as being included in the scope of the present invention. .

200: Power generation company API gateway server
300: Power generation relay server
500: firewall
600: Data center relay server
700: API gateway server

Claims (12)

A power generation company relay server and a data center relay server that perform KAFKA communication to collect data messages about power generation operation;
A power generation company API gateway server that converts request information for the API service from an API message to a KAFKA message and converts result information for the API service from a KAFKA message to an API message; and
A data sensor API gateway server that converts request information for API services from KAFKA messages to API messages, and converts result information for API services from API messages to KAFKA messages.
API gateway system between heterogeneous networks including.
According to paragraph 1,
The KAFKA message is,
Topic consisting of type, power company name, and App ID; and
Data as request data or response result information required in the above topic
API gateway system between heterogeneous networks including.
According to paragraph 2,
The power generation company API gateway and the data sensor API gateway,
In the case of a KAFKA message converted from the above API message, an API gateway system between heterogeneous networks sets the priority of the topic lower than that of other general KAFKA messages.
According to paragraph 1,
The power generation company API gateway server,
API Gateway, which provides services such as authentication/authorization and routing so that other modules on the network can request/response to certain API services; and
KAFKA-API message conversion module that converts API service request/response signals into KAFKA messages for subsequent processing
API gateway system between heterogeneous networks including.
According to paragraph 1,
The data sensor API gateway server,
API Gateway, which provides services such as authentication/authorization and routing so that other modules on the network can request/response to certain API services; and
KAFKA-API message conversion module that converts API service request/response signals into KAFKA messages for subsequent processing
API gateway system between heterogeneous networks including.
A power generation company relay server that performs KAFKA communication to collect data messages about power generation operation; and
Power generation company API gateway server that converts request information for API service from API message to KAFKA message and converts result information for API service from KAFKA message to API message
Intelligent power plant platform including.
A data center relay server that performs KAFKA communication to collect data messages about power generation operation; and
A data center API gateway server that converts request information for API services from KAFKA messages to API messages, and converts result information for API services from API messages to KAFKA messages.
IDPP integrated data center including.
Requesting an API service from the API client to the power generation company's API gateway;
Converting the API service request into a KAFKA message at the power generation company API gateway;
Transmitting the API service request converted into a KAFKA message from the power generation company relay server to the data center relay server; and
A step where the data center API gateway server receives the API service request from the data center relay server, converts it from a KAFKA message to an API message, and delivers it to the API server of the corresponding API service.
A method of performing API services between heterogeneous networks including.
According to clause 8,
The data center API gateway receiving an API service response to the API service request from the API server and converting it into a KAFKA message;
Transmitting the API service response converted into a KAFKA message from the data center relay server to the power generation company relay server; and
Converting the API service response received from the power generation company relay server into an API message at the power generation company API gateway and delivering it to the API client.
A method of performing an API service between heterogeneous networks, further comprising:
According to clause 9,
The KAFKA message is,
Topic consisting of type, power company name, and App ID; and
Data as request data or response result information required in the above topic
A method of performing API services between heterogeneous networks including.
According to clause 10,
In the step of converting the API service request into a KAFKA message,
A method of performing API services between heterogeneous networks that sets the priority of the topic lower than other general KAFKA messages.
According to clause 10,
In the step of receiving the API service response and converting it into a KAFKA message,
A method of performing API services between heterogeneous networks that sets the priority of the topic lower than other general KAFKA messages.