KR102407334B1 - Gateway apparatus and operating method thereof - Google Patents

Abstract

A gateway device and a method of operating the same are disclosed. A gateway device and an operating method thereof according to an embodiment of the present invention include: an execution request processing module that receives execution request information for requesting execution of a specific function from a client, and converts the received execution request information into a message; and a message queue a processing server including a queue module for storing the message converted from the execution request processing module by using; and a database module storing API server information and client-related information, a request information generating module receiving the converted message from the queue module, and generating request information based on the converted message and the stored API server information, and the and a management server including a verification module for performing authentication for the client based on the generated request information and the stored client-related information, wherein the processing server is an API server that provides an API for performing the specific function. It further includes a routing module for sending the authenticated request information.

Description

Gateway device and its operation method {GATEWAY APPARATUS AND OPERATING METHOD THEREOF}

Embodiments of the present invention relate to a gateway device and an operating method thereof.

As the digital age changes, microservices are increasingly used to perform innovative services. Micro Service Architecture (MSA) refers to an architecture that can be executed independently and provides services by decomposing various functions into independent small units to be applied to large-scale software development.

In other words, there is an increasing demand for microservices that can be changed and combined by dividing API services that provide responses to requests from clients in the form of API (Application Programming Interface) into small units.

Accordingly, a gateway is being developed so that numerous API services can be smoothly operated and managed according to a client's request.

In order to provide a stable API service in such an MSA environment, the gateway needs to ensure data integrity and consistency even in the event of a system failure.

Republic of Korea Patent Publication No. 10-0568178 (2006.03.30.)

SUMMARY Embodiments of the present invention are to provide a gateway device and an operating method thereof for ensuring data integrity and consistency.

According to an exemplary embodiment of the present invention, the execution is performed using an execution request processing module that receives execution request information for requesting execution of a specific function from a client, and converts the received execution request information into a message, and a message queue a processing server including a queue module for storing messages converted from the request processing module; and a database module storing API (Application Programming Interface) server information and client-related information, request information for receiving the converted message from the queue module, and generating request information based on the converted message and the stored API server information A management server comprising a generation module, and a verification module for performing authentication for the client based on the generated request information and the stored client-related information, wherein the processing server provides an API for performing the specific function The gateway device further comprising a routing module for transmitting the authenticated request information to the API server is provided.

The execution request processing module monitors the status of the queue module, determines whether a failure has occurred in the queue module, and if it is determined that no failure has occurred in the queue module, converts the received execution request information into a message, It can be stored in the queue module.

When it is determined that a failure has occurred in the queue module, the execution request processing module may store the received execution request information in a file queue.

The execution request processing module may check whether the queue module is restored, and when it is determined that the queue module is restored, the execution request information may be converted into messages in the order in which the execution request information is stored in the file queue and stored in the queue module.

The request information generating module monitors the status of the database module, determines whether a failure has occurred in the database module, and if it is determined that the database module does not have a failure, the converted message transmitted from the queue module and the The request information may be generated based on the stored API server information.

When it is determined that a failure has occurred in the database module, the request information generation module may store the converted message received from the queue module in a file queue.

The request information generation module checks whether the database module is restored, and when it is determined that the database module is restored, confirms a request to perform a specific function of the client in the order in which the converted message is stored in the file queue, Request information for calling an API performing the specific function may be generated based on the stored API server information.

According to another exemplary embodiment of the present invention, the method comprising: receiving, in an execution request processing module, execution request information for requesting execution of a specific function from a client, and converting the received execution request information into a message; storing, in a queue module, the converted message using a message queue; receiving, in the request information generating module, the converted message, and generating request information based on the converted message and pre-stored API server information; performing, in the verification module, authentication on the client based on the generated request information and pre-stored client-related information; and transmitting, in the routing module, the authenticated request information to an API server that provides an API for performing the specific function, the method of operation of the gateway device is provided.

The converting into the message may include, in the execution request processing module, monitoring the status of the queue module, and determining whether a failure has occurred in the queue module; and converting the received execution request information into a message and storing the received execution request information in the queue module when the execution request processing module determines that a failure has not occurred in the queue module.

The converting into the message may further include, when the execution request processing module determines that a failure has occurred in the queue module, storing the received execution request information in a file queue.

The converting into the message may include, in the execution request processing module, checking whether the queue module is restored; and when the execution request processing module determines that the queue module is restored, converting the messages into messages in the order in which the execution request information is stored in the file queue and storing the messages in the queue module.

The generating of the request information may include, in the request information generating module, monitoring a status of a database module, and determining whether a failure has occurred in the database module; and generating the request information based on the converted message received from the queue module and the stored API server information when it is determined in the request information generating module that no failure has occurred in the database module have.

The generating of the request information may further include, in the request information generating module, if it is determined that a failure has occurred in the database module, storing the converted message received from the queue module in a file queue have.

The generating of the request information may include, in the request information generating module, checking whether the database module is restored; confirming, in the request information generating module, a request to perform a specific function of the client in the order in which the converted message is stored in the file queue, when it is determined that the database module is restored; and generating, in the request information generating module, request information for calling an API performing the specific function based on the stored API server information.

According to embodiments of the present invention, when a system failure occurs in the gateway device (in particular, the queue module and the database module), the execution request processing module and the request information generating module store input data in a file queue, and when the system is restored By processing the input data in the order stored in the file queue, data integrity and consistency can be guaranteed even in the event of a system failure.

1 is a schematic diagram illustrating a microservices architecture including a gateway device according to an embodiment of the present invention;
2 is a block diagram illustrating a gateway device according to an embodiment of the present invention;
3 is a flowchart illustrating a method of operating a gateway device according to an embodiment of the present invention;
4 is a flowchart illustrating a method of operating a gateway device according to another embodiment of the present invention;
5 is a block diagram illustrating and describing a computing environment including a computing device suitable for use in example embodiments;

Hereinafter, specific embodiments of the present invention will be described with reference to the drawings. The following detailed description is provided to provide a comprehensive understanding of the methods, devices, and/or systems described herein. However, this is merely an example, and the present invention is not limited thereto.

In describing the embodiments of the present invention, if it is determined that the detailed description of the known technology related to the present invention may unnecessarily obscure the gist of the present invention, the detailed description thereof will be omitted. And, the terms to be described later are terms defined in consideration of functions in the present invention, which may vary according to intentions or customs of users and operators. Therefore, the definition should be made based on the content throughout this specification. The terminology used in the detailed description is for the purpose of describing embodiments of the present invention only, and should in no way be limiting. Unless explicitly used otherwise, expressions in the singular include the meaning of the plural. In this description, expressions such as “comprising” or “comprising” are intended to indicate certain features, numbers, steps, acts, elements, some or a combination thereof, one or more other than those described. It should not be construed to exclude the presence or possibility of other features, numbers, steps, acts, elements, or any part or combination thereof.

Also, terms such as first and second may be used to describe various components, but the components should not be limited by the terms. The above terms may be used for the purpose of distinguishing one component from another component. For example, without departing from the scope of the present invention, a first component may be referred to as a second component, and similarly, a second component may also be referred to as a first component.

In the following description, the terms "transmission", "communication", "transmission", "reception" and other similar meanings of a signal or information are not only directly transmitted from one component to another component, but also a signal or information This includes passing through other components. In particular, to “transmit” or “transmit” a signal or information to a component indicates the final destination of the signal or information and does not imply a direct destination. The same is true for "reception" of signals or information. In addition, in this specification, when two or more data or information are "related", it means that when one data (or information) is acquired, at least a part of other data (or information) can be acquired based thereon.

1 is a schematic diagram illustrating a microservices architecture including a gateway device 200 according to an embodiment of the present invention.

As shown in FIG. 1 , a microservice architecture including a gateway device 200 according to an embodiment of the present invention may include a client 100 , a gateway device 200 , and a plurality of API servers 300 . have.

The client 100 may transmit an execution request (performance request information) for a specific function to the gateway device 200 . Also, the client 100 may receive response information according to a request to perform a specific function from the gateway device 200 . For example, the client 100 is a mobile station (MS), a user terminal (UT), a subscriber station (SS), a wireless device, a wireless modem, a handheld device, and an AT ( Access Terminal), a mobile communication terminal, a smart phone, etc., but is not limited thereto.

The gateway device 200 receives an execution request (performance request information) for a specific function from the client 100 , and generates request information for calling an API for performing a specific function corresponding to each API server 300 . can do. Also, the gateway device 200 may receive response information from each of the plurality of API servers 300 . That is, the gateway device 200 may route the request of the client 100 to each microservice (API server 300 ). The gateway device 200 may be implemented in the form of a proxy server or the like, and one or more of various software that allows a network load balancing mechanism, or a service device to operate on the Internet or other networks may be installed, through which It can also be implemented as a computerized system.

The plurality of application programming interface (API) servers 300 may provide application programming interface (API) services, respectively. The plurality of API servers 300 may receive request information from the gateway device 200 and may generate response information for API services provided by each API server 300 in response to the received request information. Also, the plurality of API servers 300 may transmit the generated response information to the gateway device 200 .

As described above, in the microservice architecture including the gateway device 200 according to an embodiment of the present invention, microservices can be provided to the client 100 through the above configuration. Hereinafter, the gateway device 200 for realizing this The configuration of will be described in more detail.

2 is a configuration diagram for explaining a gateway device 200 according to an embodiment of the present invention.

As shown in FIG. 2 , the gateway device 200 according to an embodiment of the present invention may include a processing server 210 and a management server 220 .

The processing (gateway) server 210 may include a performance request processing module 211 , a queue module 212 , and a routing module 213 .

The execution request processing module 211 may receive an execution request (execution request information) for a specific function from the client 100 . Here, the specific function may mean, for example, an independent function that can be performed by the API server 300 . Also, the execution request processing module 211 may convert the received execution request information into a message, and transmit the converted message to the queue module 212 . Specifically, the execution request processing module 211 may convert a request to perform a specific function into a message in order to process a large number of execution requests from the client 100 . That is, by converting the execution request information received from the client 100 into a message and storing it in the queue module 212 , the actual message flow can be implemented in an asynchronous structure using a queue.

In an exemplary embodiment, the execution request processing module 211 may monitor the status of the queue module 212 .

Specifically, the execution request processing module 211 monitors the status of the queue module 212 and causes the queue module 212 to fail (eg, locking-up, hanging, crashing). etc.) has occurred, it is possible to store the received execution request information in a file queue without converting it into a message. Here, the file queue may mean a queue for storing contents in a file. That is, when the queue module 212 fails in the execution request processing module 211, there is a risk that the data stored in the memory is volatilized. can be saved. Also, when it is determined that the queue module 212 is restored, the execution request processing module 211 may convert the execution request information into a message in the order in which the execution request information is stored in the file queue. That is, when a failure occurs in the queue module 212, the execution request processing module 211 stops the message conversion operation and stores the execution request information in the file queue, and when the queue module 212 is restored, the execution stored in the file queue By resuming the message conversion operation in the order in which the request information is stored, data loss can be prevented even when a failure occurs in the queue module 212 .

The queue module 212 may store the message converted from the execution request processing module 211 using a message queue. The queue module 212 may be implemented as an in-memory database to store messages in a memory queue.

The routing module 213 may obtain response information for the API by calling the API based on the request information. Specifically, the routing module 213 may generate call information for the API by using the information on the API included in the request information, and call the API by using the call information on the API.

The admin server 220 may include a request information generation module 221 , a database module 222 , and a confirmation module 223 .

The request information generation module 221 may generate request information based on the converted message and pre-stored API server information. Specifically, the request information generation module 221 receives the converted message from the queue module 212, checks the execution request of the client 100, and calls an API that performs a specific function based on pre-stored API server information. You can create request information for

In an exemplary embodiment, the request information generation module 221 may monitor the status of the database module 222 .

Specifically, the request information generation module 221 monitors the status of the database module 222 and causes the database module 222 to fail (eg, locking-up, hanging, crashing). etc.) has occurred, the converted message received from the queue module 212 may be stored in a file queue. That is, the request information generating module 221 has a risk of volatilization of data stored in the memory when a failure occurs in the database module 222. In order to safely store the data, the contents are stored in the file until the database module 222 is restored. can be saved. In addition, when it is determined that the database module 222 has been restored, the request information generation module 221 checks the request to perform a specific function of the client 100 in the order in which the converted messages are stored in the file queue, and a pre-stored API Request information for calling an API that performs a specific function can be generated based on server information. That is, when a failure occurs in the database module 222, the request information generation module 221 stops the request information generation operation and stores the converted message in a file queue, and when the database module 222 is restored, it is stored in the file queue By resuming the operation of generating the requested information in the order in which the converted messages are stored, data loss can be prevented even when a failure occurs in the database module 222 .

The database module 222 may store API server information, client-related information, and log information. Here, the API server information may include information on a function required for the API server 300 to perform a function, an address of the API server, a resource of the API server, and the like. In addition, the client-related information may include a unique identification number for identifying the client, such as a client ID. In addition, the log information may include an API call log according to the execution request information received from the client.

The verification module 223 may perform authentication for the client 100 . Specifically, the verification module 223 may compare the request information generated by the request information generation module 221 with pre-stored client-related information to confirm authentication and access authority for the client 100 . That is, the verification module 223 may call the API only in response to a request from the client 100 having authentication and access authority to protect access to the API server 300 .

Meanwhile, the order of calling APIs described in the present invention is only an example, and may be set differently according to embodiments.

Therefore, according to embodiments of the present invention, when a system failure occurs in the gateway device 200 (in particular, the queue module 212 and the database module 222), each module (in particular, the execution request processing module 211) and the request information generating module 221) stores the input data in the file queue, and when the system is restored, the data is processed in the order stored in the file queue, thereby ensuring the integrity and consistency of the data even in the event of a system failure. have.

3 is a flowchart illustrating an operation method of the gateway device 200 according to an embodiment of the present invention. The method illustrated in FIG. 3 may be performed, for example, by the aforementioned gateway device 200 . In the illustrated flowchart, the method is described by dividing the method into a plurality of steps, but at least some of the steps are performed in a different order, are performed in combination with other steps, are omitted, are performed in separate steps, or are not shown. One or more steps may be added and performed.

First, the gateway device 200 receives an execution request (execution request information) for a specific function from the client 100 ( S301 ). Here, the specific function may mean, for example, an independent function that can be performed by the API server 300 .

Next, the gateway device 200 monitors the status of the queue module 212 (S302), and determines whether a failure has occurred in the queue module 212 (S303).

Next, if it is determined that a failure has not occurred in the queue module 212, the gateway device 200 converts the received execution request information into a message (S304), and stores the converted message in the queue module 212 ( S305).

At this time, if it is determined that a failure has occurred in the queue module 212, the gateway device 200 stores the received execution request information as a file queue without converting it into a message (S306). Here, the file queue may mean a queue for storing contents in a file. Next, the gateway device 200 checks whether the queue module 212 is restored while storing the execution request information in the file queue (S307), and when it is determined that the queue module 212 is restored, in the order stored in the file queue The execution request information is converted into a message (S308).

Next, the gateway device 200 generates request information based on the converted message and pre-stored API server information (S309). Specifically, the gateway device 200 checks the execution request of the client 100 based on the converted message, and generates request information for calling an API that performs a specific function based on pre-stored API server information. have.

Next, the gateway device 200 authenticates the client 100 ( S310 ). Specifically, the gateway device 200 may compare the request information with information related to the client 100 to confirm authentication and access rights for the client 100 .

Finally, the gateway device 200 calls the API based on the request information (S311). Specifically, the gateway device 200 may generate call information for the API by using information on the API included in the request information, and call the API by using the call information on the API.

4 is a flowchart illustrating an operation method of the gateway device 200 according to another embodiment of the present invention. The method illustrated in FIG. 4 may be performed, for example, by the aforementioned gateway device 200 . In the illustrated flowchart, the method is described by dividing the method into a plurality of steps, but at least some of the steps are performed in a different order, are performed in combination with other steps, are omitted, are performed in separate steps, or are not shown. One or more steps may be added and performed.

First, the gateway device 200 receives an execution request (performance request information) for a specific function from the client 100 (S401). Here, the specific function may mean, for example, an independent function that can be performed by the API server 300 .

Next, the gateway device 200 converts the received execution request information into a message (S402). At this time, the gateway device 200 monitors the status of the queue module 212 and causes a failure in the queue module 212 (eg, locking-up, hanging, crashing, etc.) If it is determined that this has occurred, the received execution request information may be stored in a file queue without converting it into a message. Here, the file queue may mean a queue for storing contents in a file. Also, when it is determined that the queue module 212 is restored, the gateway device 200 may convert the execution request information into a message in the order stored in the file queue.

Next, the gateway device 200 stores the converted message in the queue module 212 (S403).

Next, the gateway device 200 monitors the state of the database module 222 (S404), and determines whether a failure has occurred in the database module 222 (S405).

Next, when it is determined that a failure has not occurred in the database module 222, the gateway device 200 generates request information based on the converted message and pre-stored API server information (S406).

At this time, when it is determined that a failure has occurred in the database module 222, the gateway device 200 stores the converted message in a file queue (S407). Next, the gateway device 200 checks whether the database module 222 is restored while storing the converted message in the file queue, and when it is determined that the database module 222 is restored (S408), the converted message in the file queue Checks a request to perform a specific function of the client 100 in the stored order, and generates request information for calling an API that performs a specific function based on pre-stored API server information (S409).

Then, the gateway device 200 performs authentication for the client 100 (S410). Specifically, the gateway device 200 may compare the request information with information related to the client 100 to confirm authentication and access rights for the client 100 .

Finally, the gateway device 200 calls the API based on the request information (S411). Specifically, the gateway device 200 may generate call information for the API by using information on the API included in the request information, and call the API by using the call information on the API.

5 is a block diagram illustrating and describing a computing environment including a computing device suitable for use in example embodiments. In the illustrated embodiment, each component may have different functions and capabilities other than those described below, and may include additional components in addition to those described below.

The illustrated computing environment 10 includes a computing device 12 . In one embodiment, computing device 12 may be client 100 . Computing device 12 may also be gateway device 200 . Also, the computing device 12 may be the API server 300 .

Computing device 12 includes at least one processor 14 , computer readable storage medium 16 , and communication bus 18 . The processor 14 may cause the computing device 12 to operate in accordance with the exemplary embodiments discussed above. For example, the processor 14 may execute one or more programs stored in the computer-readable storage medium 16 . The one or more programs may include one or more computer-executable instructions that, when executed by the processor 14, configure the computing device 12 to perform operations in accordance with the exemplary embodiment. can be

Computer-readable storage medium 16 is configured to store computer-executable instructions or program code, program data, and/or other suitable form of information. The program 20 stored in the computer readable storage medium 16 includes a set of instructions executable by the processor 14 . In one embodiment, computer-readable storage medium 16 includes memory (volatile memory, such as random access memory, non-volatile memory, or a suitable combination thereof), one or more magnetic disk storage devices, optical disk storage devices, flash It may be memory devices, other forms of storage medium accessed by computing device 12 and capable of storing desired information, or a suitable combination thereof.

Communication bus 18 interconnects various other components of computing device 12 , including processor 14 and computer readable storage medium 16 .

Computing device 12 may also include one or more input/output interfaces 22 and one or more network communication interfaces 26 that provide interfaces for one or more input/output devices 24 . The input/output interface 22 and the network communication interface 26 are coupled to the communication bus 18 . Input/output device 24 may be coupled to other components of computing device 12 via input/output interface 22 . Exemplary input/output device 24 may include a pointing device (such as a mouse or trackpad), a keyboard, a touch input device (such as a touchpad or touchscreen), a voice or sound input device, various types of sensor devices, and/or imaging devices. input devices and/or output devices such as display devices, printers, speakers and/or network cards. The exemplary input/output device 24 may be included in the computing device 12 as a component constituting the computing device 12 , and may be connected to the computing device 12 as a separate device distinct from the computing device 12 . may be

Although representative embodiments of the present invention have been described in detail above, those of ordinary skill in the art to which the present invention pertains will understand that various modifications are possible without departing from the scope of the present invention with respect to the above-described embodiments. . Therefore, the scope of the present invention should not be limited to the described embodiments, but should be defined by the claims described below as well as the claims and equivalents.

100 : client
200: gateway device
210: processing server
211: execution request processing module
212: queue module
213: routing module
220: management server
221: request information generation module
222: database module
223: verification module
300: multiple API servers

Claims (14)

Receives execution request information for requesting execution of a specific function from a client, an execution request processing module that converts the received execution request information into a message, and a message queue to store the converted message from the execution request processing module a processing server including a queue module; and
Request information generation for receiving the converted message from a database module storing API (Application Programming Interface) server information and client-related information, and the queue module, and generating request information based on the converted message and the stored API server information A management server comprising a module, and a verification module that performs authentication for the client based on the generated request information and the stored client-related information,
The processing server further comprises a routing module for transmitting the authenticated request information to an API server that provides an API for performing the specific function,
The execution request processing module,
monitoring the status of the queue module, determining whether a failure has occurred in the queue module , gateway device.
delete The method according to claim 1,
The execution request processing module,
When it is determined that a failure has occurred in the queue module, the gateway device for storing the received execution request information in a file queue.
4. The method according to claim 3,
The execution request processing module,
Checking whether the queue module has been restored, and if it is determined that the queue module is restored, converts the messages into messages in the order in which the execution request information is stored in the file queue and stores the messages in the queue module.
Receives execution request information for requesting execution of a specific function from a client, an execution request processing module that converts the received execution request information into a message, and a message queue to store the converted message from the execution request processing module a processing server including a queue module; and
Request information generation for receiving the converted message from a database module storing API (Application Programming Interface) server information and client-related information, and the queue module, and generating request information based on the converted message and the stored API server information A management server comprising a module, and a verification module that performs authentication for the client based on the generated request information and the stored client-related information,
The processing server further comprises a routing module for transmitting the authenticated request information to an API server that provides an API for performing the specific function,
The request information generation module,
Monitors the status of the database module, determines whether a failure has occurred in the database module, and when it is determined that the database module does not have a failure, based on the converted message transmitted from the queue module and the stored API server information To generate the request information, the gateway device.
6. The method of claim 5,
The request information generation module,
When it is determined that a failure has occurred in the database module, the gateway device for storing the converted message transmitted from the queue module in a file queue.
7. The method of claim 6,
The request information generation module,
Check whether the database module is restored, and if it is determined that the database module is restored, confirm the request to perform the specific function of the client in the order in which the converted message is stored in the file queue, and retrieve the stored API server information A gateway device that generates request information for calling an API that performs the specific function based on it.
receiving, in the execution request processing module, execution request information for requesting execution of a specific function from a client, and converting the received execution request information into a message;
storing, in a queue module, the converted message using a message queue;
receiving, in the request information generating module, the converted message, and generating request information based on the converted message and pre-stored API server information;
performing, in the verification module, authentication on the client based on the generated request information and pre-stored client-related information; and
In the routing module, comprising the step of transmitting the authenticated request information to an API server that provides an API that performs the specific function,
The step of converting the message into the
monitoring, in the execution request processing module, the status of the queue module, and determining whether a failure has occurred in the queue module; and
When the execution request processing module determines that there is no failure in the queue module, converting the received execution request information into a message and storing the message in the queue module, the method of operating a gateway device.
delete 9. The method of claim 8,
The step of converting the message into
When the execution request processing module determines that a failure has occurred in the queue module, the method further comprising the step of storing the received execution request information in a file queue.
11. The method of claim 10,
The step of converting the message into
checking, in the execution request processing module, whether the queue module is restored; and
When the execution request processing module determines that the queue module is restored, converting the execution request information into messages in the order in which the execution request information is stored in the file queue and storing the converted messages in the queue module, the method of operating a gateway device further comprising: .
receiving, in the execution request processing module, execution request information for requesting execution of a specific function from a client, and converting the received execution request information into a message;
storing, in a queue module, the converted message using a message queue;
receiving, in the request information generating module, the converted message, and generating request information based on the converted message and pre-stored API server information;
performing, in the verification module, authentication on the client based on the generated request information and pre-stored client-related information; and
In the routing module, comprising the step of transmitting the authenticated request information to an API server that provides an API that performs the specific function,
The step of generating the request information includes:
monitoring, in the request information generating module, the status of the database module, and determining whether a failure has occurred in the database module; and
In the request information generating module, if it is determined that there is no failure in the database module, generating the request information based on the converted message received from the queue module and the stored API server information, the gateway further comprising How the device works.
13. The method of claim 12,
The step of generating the request information includes:
In the request information generating module, if it is determined that a failure has occurred in the database module, further comprising the step of storing the converted message transmitted from the queue module in a file queue (file queue), the operation method of the gateway device.
14. The method of claim 13,
The step of generating the request information includes:
checking, in the request information generating module, whether the database module is restored;
confirming, in the request information generating module, a request to perform a specific function of the client in the order in which the converted message is stored in the file queue, when it is determined that the database module is restored; and
The method of operating a gateway device, further comprising, in the request information generating module, generating request information for calling an API performing the specific function based on the stored API server information.

Images