KR20240074579A - Gateway device and method for routing management based on response information - Google Patents

Abstract

A gateway device and method for routing management based on response information are disclosed. A gateway device that mediates a communication connection between a plurality of client terminals and a plurality of target servers requests the target server for a task of the client terminal and includes a plurality of sub-threads that parse response information to the request. And it is connected to a plurality of sub-threads, and when response information parsed from the plurality of sub-threads is received, the error response rate of each target server is calculated using the received response information, and a routing policy is set based on the calculated error response rate. , includes a main thread that transfers the set routing policy to multiple subthreads.

Description

Gateway device and method for routing management based on response information}

The present invention relates to routing management technology, and more specifically, to a gateway device and method for managing routing based on response information that manages routing based on the error response rate for response information of a target server.

A multi-threaded gateway or proxy server sends requests to multiple designated target servers and receives responses corresponding to the requests.

Typically, a gateway or proxy server performs this process by selecting a target server in a round robin (RR) method or primary/backup method and transmitting TCP (Transmission) to the target server.　Control　Protocol) establishes a connection, sends a request, receives a response, and processes it.

However, the round robin method has a problem in that it cannot take into account even if there is a target server that has an error or problem during use, and the primary/backup method has a problem in that the resources of the backup server are wasted. There is also a problem that consideration of cases where a TCP connection is made to a specific server but the response to the HTTP request is not a normal response is not properly reflected.

Korean Patent Publication No. 10-1982578 (2019.05.21.)

The problem to be solved by the present invention is to provide a gateway device and method for routing management based on response information that provides smooth communication by preferentially selecting a target server with a low error response rate based on the error response rate for response information of the target server. is to provide.

In order to solve the above problem, a gateway device that mediates a communication connection between a plurality of client terminals and a plurality of target servers according to the present invention requests the target server for a task of the client terminal, and responds to the request. It is connected to a plurality of sub-threads that parse response information for the target server, and when the parsed response information is received from the plurality of sub-threads, an error of each target server is detected using the received response information. It includes a main thread that calculates a response rate, sets a routing policy based on the calculated error response rate, and transmits the set routing policy to the plurality of sub-threads.

In addition, the main thread is characterized in that it manages the code information included in the response information in the form of a hash map.

In addition, the main thread applies the error response rate when the number of response information of the target server is more than a preset standard and the error response rate of the target server reaches the preset standard, and a notification notifies that the error response rate is applied. It is characterized by controlling the message to be provided to the API manager device that manages the routing policy.

In addition, the main thread sets the routing policy to preferentially select and route the target server with the lowest error response rate.

Additionally, the main thread is characterized in that it sets the routing policy in a round robin method when there is a target server with the same error response rate.

Additionally, the main thread initializes the error response rate at each preset period and calculates a new error response rate.

Additionally, the main thread is connected to the plurality of sub-threads through a pipeline.

The routing method of a multi-threaded gateway device that mediates communication connections between a plurality of client terminals and a plurality of target servers according to the present invention includes a plurality of sub-threads of the gateway device to the target server for tasks of the client terminal. Requesting and parsing response information for the request, when the main thread of the gateway device receives the parsed response information from the plurality of sub-threads, uses the received response information to determine the error response rate of each target server. calculating, the main thread setting a routing policy based on the calculated error response rate, the main thread transmitting the set routing policy to the plurality of sub-threads, and the plurality of sub-threads receiving the It includes routing according to the established routing policy.

A routing system according to the present invention collects a plurality of gateway devices that mediate communication connections between a plurality of client terminals and a plurality of target servers and a routing policy for the communication connection from the plurality of gateway devices, and the collected routing policy Includes an API manager device that manages, wherein each of the plurality of gateway devices requests the target server for a task of the client terminal and a plurality of servers that parse response information to the request. It is connected to a thread and the plurality of sub-threads, and when the parsed response information is received from the plurality of sub-threads, the error response rate of each target server is calculated using the received response information, and based on the calculated error response rate. It includes a main thread that sets the routing policy and transfers the set routing policy to the plurality of sub-threads.

Additionally, the API manager device is characterized in that when at least one gateway device among the plurality of gateway devices requests the routing policy, the API manager device transmits the routing policy being managed to the corresponding gateway device.

According to an embodiment of the present invention, the error response rate of the target server is calculated using the response information of the target server, and a routing policy is set based on the calculated error response rate, thereby preferentially routing the target server with a low error response rate. It can provide smooth communication to users.

Additionally, by providing a routing policy to a gateway device newly added or created in the system, the time and cost for initial setup of the gateway device can be reduced.

1 is a configuration diagram for explaining a routing system according to an embodiment of the present invention.
Figure 2 is a block diagram for explaining a gateway device according to an embodiment of the present invention.
Figure 3 is a diagram for explaining the routing process according to an embodiment of the present invention.
Figure 4 is a flowchart for explaining a routing method of a gateway device according to an embodiment of the present invention.
Figure 5 is a flow chart to explain the information management method of the API manager device according to an embodiment of the present invention.
Figure 6 is a block diagram for explaining a computing device according to an embodiment of the present invention.

Below, with reference to the attached drawings, embodiments of the present invention will be described in detail so that those skilled in the art can easily implement the present invention. However, the present invention may be implemented in many different forms and is not limited to the embodiments described herein. In order to clearly explain the present invention in the drawings, parts unrelated to the description are omitted, and similar parts are given similar reference numerals throughout the specification.

In this specification and drawings (hereinafter referred to as “this specification”), duplicate descriptions of the same components are omitted.

Also, in this specification, when a component is mentioned as being 'connected' or 'connected' to another component, it may be directly connected or connected to the other component, but may be connected to the other component in the middle. It should be understood that may exist. On the other hand, in this specification, when it is mentioned that a component is 'directly connected' or 'directly connected' to another component, it should be understood that there are no other components in between.

Additionally, the terms used in this specification are merely used to describe specific embodiments and are not intended to limit the present invention.

Also, in this specification, singular expressions may include plural expressions, unless the context clearly dictates otherwise.

In addition, in this specification, terms such as 'include' or 'have' are only intended to designate the presence of features, numbers, steps, operations, components, parts, or combinations thereof described in the specification, and one or more It should be understood that this does not exclude in advance the presence or addition of other features, numbers, steps, operations, components, parts, or combinations thereof.

Also, in this specification, the term 'and/or' includes a combination of a plurality of listed items or any of the plurality of listed items. In this specification, 'A or B' may include 'A', 'B', or 'both A and B'.

Additionally, in this specification, detailed descriptions of well-known functions and configurations that may obscure the gist of the present invention will be omitted.

1 is a configuration diagram for explaining a routing system according to an embodiment of the present invention.

Referring to FIG. 1, the routing system 600 provides smooth communication by preferentially selecting a target server with a low error response rate based on the error response rate of response information of the target server. The routing system 600 may be a system in a cloud environment, but is not limited to this. The routing system 600 includes at least one gateway device 100, a plurality of client terminals 200, a plurality of target servers 300, an API manager device 400, and a user terminal 500.

The gateway device 100 mediates a communication connection between a plurality of client terminals 200 and a plurality of target servers 300. The gateway device 100 may include at least one device and may be configured on a multi-thread basis.

The gateway device 100 requests the target server 300 for a task of the client terminal 200 and parses response information to the request. Here, request refers to an HTTP (hypertext transfer protocol) request, and parsing refers to the process of analyzing code information included in response information. The gateway device 100 calculates the error response rate of each target server using the parsed response information. The gateway device 100 sets a routing policy based on the calculated error response rate. Here, the routing policy is a policy indicating a connection method with the target server 300. Basically, a rounding robin method can be set, but the target server with a low error response rate is preferentially selected. Additionally, the routing policy can be updated at preset intervals to reflect the latest error response error rate. The gateway device 100 supports communication between a plurality of client terminals 200 and a plurality of target servers 300 according to a set routing policy.

The client terminal 200 is a terminal used by a client and may include a plurality of terminals 200a, 200b, 200c, and 200d. Each client terminal 200 makes a request for a task, receives a response to the request, and outputs it. At this time, the client terminal 200 may communicate with the target server 300 through the gateway device 100. Preferably, the client terminal 200 may be a computing system including a smartphone, desktop, laptop, tablet PC, handheld PC, etc.

The target server 300 is a server that provides various contents and may include a plurality of servers 300a, 300b, 300c, and 300d. At this time, the target server 300 may be a server that decentralizes data for one site, but is not limited to this. Each target server 300 has a unique IP (internet protocol) address, so a TCP connection is possible through the IP address. When the target server 300 establishes a TCP connection and receives a task-related request, it provides response information for the request. At this time, the target server 300 may transmit response information to the gateway device 100. Preferably, the target server 300 may be a computing system including a server computer, a cluster computer, etc.

The API (application programming interface) manager device 400 receives a routing policy from at least one gateway device 100 and manages the received routing policy. When there are multiple gateway devices 100, the API manager device 400 may receive routing policies from each gateway device 100 and manage the received routing policies by merging them. That is, the API manager device 400 averages the error response rates of each target server 300a, 300b, 300c, and 300d included in the plurality of received routing policies to derive a routing policy for the entire system. The API manager device 400 stores and manages the derived routing policy, and can update the routing policy being managed by receiving the latest routing policy from a plurality of gateway devices 100 at preset intervals. Meanwhile, when at least one gateway device among a plurality of gateway devices requests a routing policy, the API manager device 400 transmits the routing policy being managed to the corresponding gateway device and allows the gateway to route based on the transmitted routing policy. You can. Here, the gateway device requesting the routing policy may be a device newly created or added to the routing system 600.

The user terminal 500 is a terminal used by a user (system administrator) and communicates with the API manager device 400. The user terminal 500 receives the latest routing policy from the API manager device 400 and outputs the received routing policy. At this time, the user terminal 500 may separately display and output the target server with a high error response rate. Through this, the user can intuitively recognize that there is a problem with the TCP connection with the target server. Preferably, the user terminal 500 may be a computing system including a smartphone, desktop, laptop, tablet PC, handheld PC, etc.

FIG. 2 is a block diagram for explaining a gateway device according to an embodiment of the present invention, and FIG. 3 is a diagram for explaining a routing process according to an embodiment of the present invention.

1 to 3, the gateway device 100 includes a communication unit 10, a control unit 30, and a storage unit 50.

The communication unit 10 may communicate with the client terminal 200 and the target server 300, and further communicate with the API manager device 400. The communication unit 10 receives a task-related request from the client terminal 200 and transmits response information corresponding to the request to the client terminal 200. The communication unit 10 transmits a request related to the task to the target server 300 and receives response information corresponding to the request from the target server 300. The communication unit 10 transmits a routing policy indicating a routing method to the API manager device 400.

The control unit 30 performs overall control of the gateway device 100. The control unit 300 is composed of a plurality of threads and controls routing through the plurality of threads. The control unit 30 includes a main thread 41 and a plurality of sub-threads 42, 43, and 44. Here, the main thread 41 is connected to a plurality of sub-threads 42, 43, and 44 through a pipeline.

The main thread 41 controls routing of the gateway device 100. To this end, the main thread 41 does not process requests related to the task, but sets a routing policy based on the response information of the target server.

In detail, when the main thread 41 receives response information parsed from a plurality of sub-threads 42, 43, and 44, it manages the received response information. At this time, the main thread 41 can manage the code information included in the response information in the form of a hash map. The main thread 41 can manage data more smoothly by mapping keys to values through a hash map. The main thread 41 uses the response information to calculate the error response rate of each target server. The main thread 41 can apply the error response rate when the number of response information of the target server is more than a preset standard and the error response rate of the target server reaches the preset standard. Preferably, the error response rate is 30%. It can be applied to the error response rate starting from 40% or more, but is not limited to this. That is, if the number of response information is less than the standard value, the main thread 41 may not determine that the error response rate is the error response rate of the target server even if the error response rate is high because the reliability of the data is low. In addition, the main thread 41 may calculate the error response rate as 0% by determining that it does not significantly affect the TCP connection if the error response rate is 30% to 40% or less even if the number of response information is more than the standard value.

IP address normal response Error response error response rate 1.1.1.1 6 4 40% 2.2.2.2 20 5 0% 3.3.3.3 4 4 0%

For example, the main thread 41 can calculate the error response rate as shown in [Table 1]. Here, the target server includes a target server (300a) with an IP address of 1.1.1.1, a target server (300b) with an IP address of 2.2.2.2, and a target server (300c) with an IP address of 3.3.3.3, and the minimum total response information for calculating the error response rate. The number is 10, and the starting error response rate to which the error response rate is applied is assumed to be 30%. The main thread 41 receives response information of the target server 300a from a plurality of sub-threads 42, 43, and 44. At this time, if the total number of response information is 10, of which 6 are normal responses and 4 are error responses, the main thread 41 calculates the error response rate as 40%, and sends the calculated error response rate to the target server 300a. Applies to error response rate. Additionally, the main thread 41 receives response information of the target server 300b from a plurality of sub-threads 42, 43, and 44. At this time, if the total number of response information is 25, of which 20 are normal responses and 5 are error responses, the main thread 41 can calculate the error response rate as 20%, but the calculated error response rate is the starting error response rate. Since it does not exceed 30%, the calculated error response rate is not applied as the error response rate of the target server 300b. Additionally, the main thread 41 receives response information of the target server 300c from a plurality of sub-threads 42, 43, and 44. At this time, if the total number of response information is 9, of which 4 are normal responses and 4 are error responses, the main thread 41 can calculate the error response rate as 50%, but the total number of response information is at least the total response. Since it is lower than the number of information, the calculated error response rate is not applied as the error response rate of the target server 300c.

Here, the main thread 41 can control a notification message indicating that the error response rate is applied to be provided to the API manager device 400. Through this, the API manager device 400 can provide the corresponding notification message to the user terminal 500.

The main thread 41 sets a routing policy based on the calculated error response rate. The main thread 41 sets a routing policy to preferentially select and route target servers with low error response rates. Here, the main thread 41 can set the routing policy in a round-robin method when there are target servers with the same error response rate. For example, when the error response rate is as shown in [Table 1], the main thread 41 selects the target server 300b and target server 300c in a round-robin method, and then selects the target server 300a in the following order. Alternatively, the target server 300b and the target server 300c can be selected in a round-robin manner, excluding the target server 300a. Additionally, the main thread 41 can initialize the error response rate at each preset cycle, calculate a new error response rate, and set the latest routing policy. That is, the main thread 41 can set the latest routing policy at preset intervals in order to quickly respond to cases where a target server where an error occurred is restored or an error occurs at a target server where an error did not occur, etc.

The main thread 41 transfers the set routing policy to the plurality of sub-threads 42, 43, and 44 and controls routing to be performed through the plurality of sub-threads 42, 43, and 44. Additionally, the main thread 41 can transmit the set routing policy to the API manager device 400 so that the API manager device 400 can manage routing for the entire system.

A plurality of sub-threads 42, 43, and 44 are connected to the main thread 41 and process tasks of the client terminal 200. That is, the plurality of sub-threads 42, 43, and 44 request the target server 300 for a task, receive response information for the request, and parse it. At this time, the plurality of sub-threads 42, 43, and 44 may parse the code information included in the response information. A plurality of sub-threads 42, 43, and 44 transmit the parsed response information to the main thread 41. The plurality of sub-threads 42, 43, and 44 each receive a routing policy set based on response information from the main thread 41 and perform routing according to the received routing policy.

The storage unit 50 stores a program or algorithm for driving the gateway device 100. The storage unit 50 stores task-related information (request, response). The storage unit 50 stores the error response rate and routing policy. The storage unit 50 includes a flash memory type, hard disk type, multimedia card micro type, card type memory (for example, SD or XD memory, etc.), Random Access Memory (RAM), Static Random Access Memory (SRAM), Read-Only Memory (ROM), Electrically Erasable Programmable Read-Only Memory (EEPROM), Programmable Read-Only Memory (PROM), magnetic memory, It may include at least one storage medium of a magnetic disk and an optical disk.

Figure 4 is a flowchart for explaining a routing method of a gateway device according to an embodiment of the present invention.

Referring to Figures 1 and 4, the routing method of the gateway device 100 uses response information of the target server 300 to calculate the error response rate of the target server and sets a routing policy based on the calculated error response rate. do. Through this, the routing method can provide smooth communication to users by preferentially routing target servers with low error response rates.

In step S110, the gateway device 100 receives response information from the target server 300. The gateway device 100 receives response information corresponding to the task request. The gateway device 100 may parse the received response information and manage the parsed response information in the form of a hash map.

In step S120, the gateway device 100 calculates the error response rate for each target server. The gateway device 100 calculates the error response rate by dividing the number of error response information by the total number of response information for each target server and calculating it as a percentage. At this time, the gateway device 100 may apply the corresponding error response rate when the number of response information of the target server is greater than the preset standard and the error response rate of the target server reaches the preset standard. At this time, the gateway device 100 may transmit a notification message indicating that the error response rate is applied to the API manager device 400.

In step S130, the gateway device 100 sets a routing policy. The gateway device 100 sets a routing policy based on the calculated error response rate. The gateway device 100 may set a routing policy to preferentially select and route a target server with a low error response rate. At this time, if there are target servers with the same error response rate, the gateway device 100 may set the routing policy in a round-robin method.

In step S140, the gateway device 100 performs routing. The gateway device 100 performs routing according to a set routing policy.

Figure 5 is a flowchart for explaining the information management method of the API manager device according to an embodiment of the present invention.

Referring to Figures 1 and 5, the information management method of the API manager device 400 provides a routing policy to a gateway device newly added or created in the system, thereby reducing the time and cost for initial setup of the corresponding gateway device. .

In step S210, the API manager device 400 collects routing policies. The API manager device 400 collects routing policies from each gateway device 100. At this time, there may be some differences in the routing policy for each gateway device.

In step S220, the API manager device 400 merges the collected routing policies into one integrated routing policy. The API manager device 400 generates one integrated routing policy by averaging the error response rate for each target server 300 included in the routing policy.

In step S230, the API manager device 400 determines whether there is a gateway device that has requested a routing policy. The API manager device 400 performs step S240 if there is a gateway device that has requested a routing policy, and performs step S250 if there is no gateway device that has requested a routing policy.

In step S240, the API manager device 400 transmits a routing policy to the corresponding gateway device. The API manager device 400 transmits the routing policy being managed to the gateway device that requested the routing policy.

In step S250, the API manager device 400 determines whether a preset period has been reached. The API manager device 400 performs step S210 when the preset period reaches, and performs step S230 when the preset period does not reach.

Figure 6 is a block diagram for explaining a computing device according to an embodiment of the present invention.

Referring to FIG. 6, the computing device TN100 may be a device described in this specification (eg, a gateway device, a client terminal, a target server, an API manager device, a user terminal, etc.).

The computing device TN100 may include at least one processor TN110, a transceiver device TN120, and a memory TN130. Additionally, the computing device TN100 may further include a storage device TN140, an input interface device TN150, an output interface device TN160, etc. Components included in the computing device TN100 may be connected by a bus TN170 and communicate with each other.

The processor TN110 may execute a program command stored in at least one of the memory TN130 and the storage device TN140. The processor TN110 may refer to a central processing unit (CPU), a graphics processing unit (GPU), or a dedicated processor on which methods according to embodiments of the present invention are performed. Processor TN110 may be configured to implement procedures, functions, and methods described in connection with embodiments of the present invention. The processor TN110 may control each component of the computing device TN100.

Each of the memory TN130 and the storage device TN140 can store various information related to the operation of the processor TN110. Each of the memory TN130 and the storage device TN140 may be comprised of at least one of a volatile storage medium and a non-volatile storage medium. For example, the memory TN130 may be comprised of at least one of read only memory (ROM) and random access memory (RAM).

The transceiving device TN120 can transmit or receive wired signals or wireless signals. The transmitting and receiving device (TN120) can be connected to a network and perform communication.

Meanwhile, the embodiments of the present invention are not only implemented through the apparatus and/or method described so far, but may also be implemented through a program that realizes the function corresponding to the configuration of the embodiment of the present invention or a recording medium on which the program is recorded. This implementation can be easily implemented by anyone skilled in the art from the description of the above-described embodiments.

Although the embodiments of the present invention have been described in detail above, the scope of the present invention is not limited thereto, and various modifications and improvements made by those skilled in the art using the basic concept of the present invention defined in the following claims are also possible. It falls within the scope of invention rights.

10: Department of Communications
30: control unit
41: main thread
42: first sub-thread
43: second sub-thread
44: nth subthread
100: gateway device
200: client terminal
300: Target server
400: API manager device
500: user terminal
600: Routing system

Claims (10)

In the gateway device that mediates communication connections between a plurality of client terminals and a plurality of target servers,
a plurality of sub-threads that request a task of the client terminal from the target server and parse response information to the request; and
It is connected to the plurality of sub-threads, and when the parsed response information is received from the plurality of sub-threads, the error response rate of each target server is calculated using the received response information, and routing is performed based on the calculated error response rate. a main thread that sets a policy and transfers the set routing policy to the plurality of sub-threads;
A gateway device containing a. According to clause 1,
The main thread is,
A gateway device characterized in that it is managed in the form of a hash map based on the code information included in the response information. According to clause 1,
The main thread is,
If the number of response information of the target server is more than the preset standard and the error response rate of the target server reaches the preset standard, the error response rate is applied, and a notification message notifying that the error response rate is applied is sent to the routing policy. A gateway device characterized in that it is controlled to be provided to a managed API manager device. According to clause 1,
The main thread is,
A gateway device characterized in that the routing policy is set so that the target server with the lowest error response rate is preferentially selected and routed. According to clause 1,
The main thread is,
A gateway device characterized in that, when there is a target server with the same error response rate, the routing policy is set in a round robin method. According to clause 1,
The main thread is,
A gateway device characterized in that the error response rate is initialized at each preset period and a new error response rate is calculated. According to clause 1,
The main thread is,
A gateway device characterized in that it is connected to the plurality of sub-threads and a pipeline. In the routing method of a multi-threaded gateway device that mediates communication connections between a plurality of client terminals and a plurality of target servers,
A plurality of sub-threads of the gateway device requesting the target server for a task of the client terminal and parsing response information to the request;
When the main thread of the gateway device receives the parsed response information from the plurality of sub-threads, calculating an error response rate of each target server using the received response information;
setting, by the main thread, a routing policy based on the calculated error response rate;
transmitting, by the main thread, the set routing policy to the plurality of sub-threads; and
routing by the plurality of sub-threads according to the received routing policy;
Routing method containing . A plurality of gateway devices that mediate communication connections between a plurality of client terminals and a plurality of target servers; and
Including an API manager device that collects routing policies for the communication connection from the plurality of gateway devices and manages the collected routing policies,
Each of the plurality of gateway devices,
a plurality of sub-threads that request the target server for a task of the client terminal and parse response information to the request; and
It is connected to the plurality of sub-threads, and when the parsed response information is received from the plurality of sub-threads, the error response rate of each target server is calculated using the received response information, and the error response rate of each target server is calculated based on the calculated error response rate. a main thread that sets a routing policy and transfers the set routing policy to the plurality of sub-threads;
A routing system that includes. According to clause 9,
The API manager device is,
A routing system, wherein when at least one gateway device among the plurality of gateway devices requests the routing policy, the routing policy being managed is transmitted to the corresponding gateway device.

Images