KR20190138355A - Method and system for automatic load balancing of server channels based on user movement - Google Patents

Abstract

According to an embodiment of the present invention, a load balancing method between servers realized by a computer may comprise the steps of: determining a remaining capacity of a server to which a channel is allocated according to communication with at least one server through a network, and searching for cleanup target servers; connecting a client connected to a termination-scheduled server to a transfer target server based on the termination-scheduled server selected on the cleanup target servers and the transfer target server; and updating information on the termination-scheduled server or the client connected to the termination-scheduled server to the transfer target server according to a connection state shared from the transfer target server to the termination-scheduled server.

Description

METHOOD AND SYSTEM FOR AUTOMATIC LOAD BALANCING OF SERVER CHANNELS BASED ON USER MOVEMENT}

The following description relates to a data communication technique in a distributed computing network having a client-server, and relates to a load balancing method of a server channel through user movement.

Load balancing is a type of computer network technology that divides work among two or more computer resources such as central processing units or storage devices. Through load balancing, device availability and response time can be optimized. Korean Patent Laid-Open Publication No. 10-2006-0069646 relates to a method for adjusting the load between subsystems in a communication network system of a bus-type network structure, and more particularly to one or more services existing in a process. In a bus network structure that connects a broker that handles message routing through a connector and interconnects all brokers in a full mesh form in a mesh, a load balance between each broker It proposes a method to properly adjust the balance.

However, the prior art must maintain the server assigned to the channel until the client connected to the server's channel moves to another channel or another server. Thus, even if only one client remains on the server's channel and remains there, the server must remain on, waiting for the client to terminate the connection and preventing new inflows from entering the server so that it can no longer enter the server. Wait until zero.

It is possible to provide a load balancing method for efficiently managing load balancing between servers by moving a client connected to one server to which a channel is allocated to a channel of another server.

A load balancing method between servers implemented by a computer may include: searching for cleanup target servers by determining a remaining capacity of a server to which a channel is allocated according to communication with at least one server through a network; Connecting a client connected to the scheduled termination server to the transfer target server based on the scheduled termination server selected for the searched clearance target servers and a transfer target server; And updating information on the scheduled termination server or a client connected to the scheduled termination server to the transfer target server according to a connection state shared from the transfer target server to the scheduled termination server.

The searching of the server to be cleaned up may include cleaning the servers including the target server or the scheduled server to be terminated based on the number of clients connected to the channel of each server and the remaining capacity of the other server other than the server. Searching may be included.

The searching of the server to be cleaned includes grouping the previous target server or the scheduled server to be determined as the server to be cleaned based on the number of clients connected to the channel of each server and the remaining capacity of the other server other than the server. It may include the step.

The searching of the server to be cleaned up may include listing the transfer target server or the scheduled server to be clustered with the server to be cleaned up.

The searching of the subject servers includes determining the number of clients connected to at least one or more channels of each server and the remaining capacity of the other server other than the server based on a predetermined criterion. The preset criterion may be any one of a time section, a period section, a day of the week, or a date set to search the server to be cleaned up.

The step of connecting the client connected to the scheduled server to be transferred to the transfer target server may include sharing address information of the transfer target server to the client connected to the scheduled server to be added to the scheduled server to be transferred and the target server to be transferred. And blocking the client requesting access.

The step of connecting the client connected to the scheduled server to be transferred to the transfer target server may be terminated as a request is made to access the transfer target server based on address information of the shared transfer target server from the client of the scheduled termination server. And connecting the client of the scheduled server to the transfer target server.

Clients of the server to be terminated may be multiplely connected to the server to be terminated and the transfer target server, and may transmit and receive information to and from the server to be terminated in the state of the multiple connection.

The updating of the transfer target server may include sharing a connection state with a client connected to the transfer target server from the transfer target server to the termination server as the client connected to the transfer target server is connected to the transfer target server. It may comprise the steps.

The updating of the transfer target server may include terminating the operation of the server to be terminated when the connection of the server to be terminated from the client is terminated.

The updating of the transfer target server may include transmitting the client's information to the transfer target server in a connection relationship between the transfer target server and the termination server while disconnecting the termination server from the client. It may include the step.

The load balancing server for performing load balancing between servers implemented as a computer is a search unit for determining the remaining capacity of the server to which the channel is allocated as the communication with the at least one or more servers through the network to search the server to be cleaned up. ; A connection unit configured to connect a client connected to the scheduled server to be terminated to the transfer target server based on the scheduled termination server selected for the searched cleanup target servers and a transfer target server; And an updater configured to update information on the scheduled termination server or the client connected to the scheduled termination server to the transfer target server according to a connection state shared from the transfer target server to the scheduled termination server.

Servers can be managed more efficiently by performing server-to-server load balancing that moves clients connected to the server's channel to another server based on the number of clients connected to the server's channel and the remaining capacity of the other server. This can solve the problem of not maintaining the server assigned to the channel until the client existing in the channel moves.

In addition, since the client is moved to the transfer target server through the dual connection between the transfer target server and the scheduled server to be terminated, the service can be naturally used without disconnection of the server.

1 is a diagram illustrating an example of a network environment according to an embodiment.
2 is a block diagram illustrating an internal configuration of a client and a server according to an exemplary embodiment.
3 is a block diagram illustrating an example of components that may be included in a processor of a load balancing server according to an embodiment.
4 is a flowchart illustrating a server-to-server load balancing method performed by a load balancing server according to an embodiment.
5 is a flowchart illustrating a method of searching for cleanup target servers in a load balancing server according to an exemplary embodiment.
6 is a flowchart illustrating a method of connecting a client to a transfer target server in a load balancing server according to an embodiment.
7 is a flowchart illustrating a method of updating a client's information to a transfer target server in a load balancing server according to an embodiment.
8 is a diagram illustrating an operation of a transfer target server and a server to be terminated according to an exemplary embodiment.

Hereinafter, exemplary embodiments will be described in detail with reference to the accompanying drawings.

1 is a diagram illustrating an example of a network environment according to an embodiment.

The network environment of FIG. 1 illustrates an example including a plurality of electronic devices 110, 120, 130, and 140, a plurality of servers 150 and 160, and a network 170. 1 is an example for describing the present invention, and the number of electronic devices or the number of servers is not limited as shown in FIG. 1.

The plurality of electronic devices 110, 120, 130, and 140 may be fixed terminals or mobile terminals implemented as computer devices. Examples of the plurality of electronic devices 110, 120, 130, and 140 include a smart phone, a mobile phone, a navigation device, a computer, a notebook computer, a digital broadcasting terminal, a personal digital assistant (PDA), and a portable multimedia player (PMP). Tablet PC). For example, the electronic device 1 110 may communicate with other electronic devices 120, 130, 140 and / or the server 150, 160 through a network 170 using a wireless or wired communication scheme. In an embodiment, the electronic device may be a client.

The communication method is not limited and may include not only a communication method using a communication network (for example, a mobile communication network, a wired internet, a wireless internet, and a broadcasting network) that the network 170 may include, but also a short range wireless communication between devices. For example, the network 170 may include a personal area network (PAN), a local area network (LAN), a campus area network (CAN), a metropolitan area network (MAN), a wide area network (WAN), and a broadband network (BBN). And one or more of networks such as the Internet. The network 170 may also include any one or more of network topologies, including bus networks, star networks, ring networks, mesh networks, star-bus networks, trees, or hierarchical networks, but It is not limited.

Each of the servers 150 and 160 communicates with the plurality of electronic devices 110, 120, 130, and 140 through the network 170 to provide a command, code, file, content, service, or the like. It may be implemented in devices.

For example, the server 160 may provide a file for installing an application to the electronic device 1 110 connected through the network 170. In this case, the electronic device 1110 may install an application using a file provided from the server 160. In addition, a service provided by the server 150 by accessing the server 150 under the control of an operating system (OS) included in the electronic device 1 110 and at least one program (for example, a browser or the installed application). I can be provided with content. For example, when the electronic device 1 110 transmits a service request message to the server 150 through the network 170 under the control of the application, the server 150 transmits a code corresponding to the service request message to the electronic device 1. The electronic device 1 110 may provide content to a user by configuring and displaying a screen according to a code under the control of an application.

In the following embodiment, the transfer target server and the scheduled end server are clustered and classified as the cleanup target server based on the total number of users connected to the channel of the server and the remaining capacity on the other server. A method of performing load balancing by controlling a client connected to a scheduled termination server to be moved to a previous target server will be described. In this case, each server may be controlled through a separate load balancing server (load balancer) for load balancing, and load balancing may be performed by each server in which a program or an application for load balancing is installed. In addition, each server may be operated based on a platform for load balancing.

2 is a block diagram illustrating an internal configuration of an electronic device and a server according to an exemplary embodiment.

In FIG. 2, an internal configuration of the electronic device 1 110 as an example of one electronic device and the server 150 as an example of one server will be described. The same or similar internal components may be applied to other electronic devices 120, 130, 140 or server 160 as well as other electronic devices or other servers that may be included in the network environment described with reference to FIG. 1. For example, the electronic device 1 110 may refer to a transaction web server that provides a client and a server 150 to provide a transaction of data related to a good.

The electronic device 1 110 and the server 150 may include memories 211 and 221, processors 212 and 222, communication modules 213 and 223, and input / output interfaces 214 and 224. The memories 211 and 221 are computer-readable recording media, and may include non-volatile permanent storage devices such as random access memory (RAM), read only memory (ROM), and disk drives. In addition, the memory 211 and 221 may store an operating system and at least one program code (for example, a code installed for the browser or the above-described application or the like installed in the electronic device 1110). These software components may be loaded from a computer readable recording medium separate from the memories 211 and 221 using a drive mechanism. Such a separate computer-readable recording medium may include a computer-readable recording medium such as a floppy drive, a disk, a tape, a DVD / CD-ROM drive, a memory card, and the like. In other embodiments, software components may be loaded into the memory 211, 221 through the communication module 213, 223 rather than a computer readable recording medium. For example, the at least one program is a program installed by files provided by the file distribution system (for example, the server 160 described above) through the network 170 for distributing installation files of developers or applications (for example, It can be loaded into the memory (211, 221) based on the above-described application).

Processors 212 and 222 may be configured to process instructions of a computer program by performing basic arithmetic, logic, and input / output operations. Instructions may be provided to the processors 212, 222 by the memory 211, 221 or the communication modules 213, 223. For example, the processors 212 and 222 may be configured to execute a command received according to a program code stored in a recording device such as the memory 211 and 221.

The communication modules 213 and 223 may provide a function for the electronic device 1 110 and the server 150 to communicate with each other through the network 170, and another electronic device (for example, the electronic device 2 120). Alternatively, it may provide a function for communicating with another server (eg, server 160). For example, a request (eg, a streaming service request for content) generated by the processor 212 of the electronic device 1 110 according to a program code stored in a recording device such as the memory 211 is controlled by the communication module 213. In accordance with the network 170 may be delivered to the server 150. Conversely, control signals, commands, contents, files, and the like provided according to the control of the processor 222 of the server 150 are transmitted to the communication module of the electronic device 1 110 via the communication module 223 and the network 170 ( It may be received by the electronic device 1110 through 213. For example, a control signal or a command of the server 150 received through the communication module 213 may be transmitted to the processor 212 or the memory 211, and the content or the file may be transmitted by the electronic device 1110. It may be stored as a storage medium that may further include.

The input / output interfaces 214 and 224 may be means for interfacing with the input / output device 215. For example, the input device may include a device such as a keyboard or mouse, and the output device may include a device such as a display for displaying a communication session of an application. As another example, the input / output interface 214 may be a means for interfacing with a device in which functions for input and output are integrated into one, such as a touch screen. As a more specific example, the processor 212 of the electronic device 1110 is configured using data provided by the server 150 or the electronic device 2 120 in processing a command of a computer program loaded in the memory 211. The service screen or the content may be displayed on the display through the input / output interface 214.

Also, in other embodiments, the electronic device 1 110 and the server 150 may include more components than those of FIG. 2. However, it is not necessary to clearly show most of the prior art components. For example, the electronic device 1 110 may be implemented to include at least some of the above-described input / output devices 215 or other components such as a transceiver, a global positioning system (GPS) module, a camera, various sensors, a database, and the like. It may further include elements.

3 is a block diagram illustrating an example of a component that a processor of a load balancing server may include, and FIG. 4 illustrates a server-to-server load balancing method performed by a load balancing server according to an embodiment. It is a flowchart for doing this.

The processor 222 of the load balancing server may include a searcher 310, a connector 320, and an updater 330. The components of the processor 222 may be representations of different functions performed by the processor 222 according to a control command provided by program code stored in the load balancing server. The processor 222 and the components of the processor 222 may control the load balancing server to perform the steps 410 to 430 included in the inter-server load balancing method of FIG. 4. In this case, the processor 222 and the components of the processor 222 may be implemented to execute instructions according to code of an operating system included in a memory and code of at least one program.

The processor 222 may load the program code stored in the file of the program for the server-to-server load balancing method to the memory. For example, when a program is executed in the load balancing server, the processor may control the load balancing server to load the program code from the file of the program into the memory under the control of the operating system. In this case, each of the processor 310, the searcher 310, the connector 320, and the updater 330 included in the processor 222 executes a command of a corresponding part of the program code loaded in the memory to perform subsequent steps. Different functional representations of the processor 222 for executing 410-430.

In operation 410, the search unit 310 may search for the cleanup target servers by determining the remaining capacity of the server to which the channel is allocated as the communication with the at least one server is performed through the network. Referring to FIG. 5, a flowchart for describing a method of searching for cleanup target servers in a load balancing server. In operation 510, the search unit 310 may organize the target servers including the previous target server or the scheduled server to be terminated based on the number of clients connected to the channel allocated to each server and the remaining capacity of the other server other than the server. You can navigate. The search unit 310 may calculate the remaining capacity of the remaining servers that do not know the number of clients connected to the channel allocated to each server and the number of clients based on each server existing in the specific service. In this case, the search unit 310 may bundle the A server and the B server as a cleanup target server when the remaining available capacity of the A server is larger than the number of clients of the B server. In this case, the server A may be selected as the transfer target server and the server B as the server to be terminated. For example, the search unit 310 may search for cleanup target servers for load balancing of servers existing in a specific service. If a specific service is a game, there may be a plurality of servers for providing a smooth game service. In this case, the client may be connected to at least one channel allocated to the server. In general, it is common to assign a 1: 1 channel to a physical server, but it is not limited thereto. It is assumed that at least one channel may be allocated to a server. Here, since a common room is allocated 1: 1 to a physical server through the concept of a waiting room and a channel, the following channel will be used as a concept of one physical server. For example, the search unit 310 may select a specific server as a server to be terminated as monitoring load balancing of a plurality of servers existing in the game service. The search unit 310 may select an end server to be terminated among a plurality of servers existing in the game service, and determine the number of clients of the end server. In this case, the search unit 310 may check the remaining capacity of the remaining servers other than the scheduled server based on the number of clients connected to the scheduled server. The search unit 310 may select the remaining server having the remaining capacity larger than the number of clients connected to the scheduled server as the transfer target server. Alternatively, the search unit 310 may set the number of clients connected to at least one channel of each server present in a specific service and the remaining capacity of the remaining servers (for example, time, duration, day of the week, date, etc.). Can also be determined based on Alternatively, the search unit 310 may periodically or aperiodically determine the number of clients connected to at least one channel of each server present in a specific service and the remaining capacity of the remaining servers. For example, the search unit 310 may determine the remaining capacity of the servers for a specific service every preset time period. In detail, the search unit 310 may search for the previous target server and the scheduled server to be finished by determining the remaining capacity of the server at the 6 o'clock to 12 o'clock and 18 o'clock periods. In operation 520, the search unit 310 may cluster the previous target server or the server to be terminated into the grooming target server. In operation 510, the search unit 310 may list a previous target server or a scheduled server to be clustered into the target servers to be cleaned up. For example, the search unit 310 may classify and classify the cleanup target servers into (previous target server, scheduled server). For example, the search unit 310 may classify the transfer target server and the scheduled end server, respectively, and list the classified transfer target server and the scheduled end server in the order of priority for load balancing. For example, the search unit 310 may cluster the previous target server and the scheduled end server to perform load balancing by calculating the optimal efficiency in clustering each transfer target server and the scheduled end server, and create a list by clustering the previous target server and the scheduled end server. . Alternatively, the search unit 310 may list the transfer target servers that are transferable based on the server to be terminated.

In operation 420, the connection unit 320 may connect the client connected to the scheduled server to be terminated based on the scheduled termination server and the target server selected for the searched cleaning target servers to the target server. Referring to FIG. 6, a flowchart illustrating a method of connecting a client to a transfer target server in a load balancing server. In step 610, the connection unit 320 may share the address information of the transfer target server to the client connected to the server to be terminated. For example, the connection unit 320 may share the IP address of the transfer target server to the client connected to the server to be terminated. The connection unit 320 may block a client requesting additional connection to the server to be terminated and the transfer target server. In operation 620, the connection unit 320 may connect the client of the scheduled server to the target server as the connection is requested to the previous target server based on the address information of the target server shared from the client of the scheduled server. . At this time, the client connected to the server to be scheduled for termination is multiplely connected to the server to be scheduled for termination and the transfer target server, and the information is transmitted and received with the server to be scheduled in the multiple connection state.

In operation 430, the updater 330 may update the information on the client scheduled to be connected to the server to be terminated or the server to be terminated according to the connection state shared from the server to the server to be migrated to the server. Referring to FIG. 7, a flowchart illustrating a method of updating information of a client from a load balancing server to a transfer target server. In operation 710, the updater 330 may share a connection state with a client connected to the transfer target server from the transfer target server to the server to be terminated. At this time, if all of the clients connected to the server to be finally terminated succeed, the client may disconnect from the server to be terminated and update the information of the previous target server. In operation 720, the updater 330 may terminate the operation of the server to be terminated as the connection of the server to be terminated from the client is terminated. As a result, the server to be terminated is terminated and the physical server corresponding to the server to be terminated is returned. The updater 330 may deliver the client's information to the transfer target server in a connection relationship between the transfer target server and the transfer target server while disconnecting the server to be terminated from the client. For example, the updater 330 connected to the client may terminate the connection of the server to be terminated and update the information of the previous target server. At the same time, it is possible to update the information of the transfer target server to the client, as well as update the client information (for example, user status information, user identification information, etc.) or information of the server to be terminated. In this case, the updating method may be different for each server, service, and / or content. In one example, it can be updated by connecting a link of a service to a database.

8 is a diagram illustrating an operation of a transfer target server and a server to be terminated according to an exemplary embodiment.

In one example, there may be servers that provide services (eg, content, games, etc.). The load balancing server 150 may provide server load balancing. The load balancing server 150 may determine the remaining capacity of the server to which the channel is allocated and search for the cleanup target servers. For example, the load balancing server may search for cleanup target servers including a previous target server or a server to be terminated based on the number of clients connected to a channel allocated to each server and the remaining capacity of the remaining servers. At this time, since the capacity of the channel allocated to the server is determined, the maximum value can be measured, and thus the remaining capacity can be defined as excluding the number of clients currently connected to the channel of the server from the maximum value. The load balancing server 150 may cluster the previous target server or the server to be terminated as the cleanup target server. For example, assume that the server A 820 and the server B 810 are selected as the organization target servers. At this time, the load balancing server 150 is the server A 820 is the transfer target server, server B 810 is to be terminated server, server 820 of the server 810 IP address of the server A 820 Can share. In this case, the A server 820 and the B server 810 may block the entrance of the client to additionally access each server. The user side 830 of the client 840 may request access to the A server 820 based on the IP address of the A server. For example, the user side 830 may have a connector 850 provided at the channel and lobby server side. In this way, the client 840 connected to the server B 810 may be connected to the server A 820 through the connector. The load balancing server 150 may connect the client 840 to the A server 820. Accordingly, the server A 820 may share the connection state of the client with the server B 810. Finally, if the client 840 successfully connects to the server A 820, the client may terminate the connection of the server B 810. The server A 820 may update the client's information. Alternatively, the information of the server A may be updated in the client 840. For example, the client 840 may be provided with the same environment of a particular service.

For example, it may be applied to a cloud environment. Server-to-server load balancing may be performed in a cloud server that provides a cloud service. In using the cloud service, you have to pay a service fee based on the period of use and the capacity used. Accordingly, the cost can be minimized and the server can be optimized by minimizing the use of unnecessary servers through server-to-server load balancing.

As described above, the load balancing server may perform load balancing between servers through the load balancing server, and load balancing between servers may be automatically performed by transmitting and receiving information through communication between servers for a specific service. have. The load is automatically measured at each server to determine a server to which load balancing should be performed. For example, when detecting that the load of the B server 810 is loaded, the previous target server for load balancing of the B server 810 may be searched for. In this case, the number of clients connected to the channel allocated to each server and the remaining capacity of each server are automatically calculated through communication with each server and counterpart servers existing in or adjacent to each server. Server groups can be classified. In this process, in order to reduce the load of the server B 810, the server A 820 may be selected as a transfer target server. Alternatively, the transfer target server may be listed as load balancing is requested in the server B 810. The B server 810 may select at least one transfer target server from the list of transfer target servers. As the server A 820 and the server B 810 are classified as the server group to be arranged, the client 840 connected to the channel allocated to the server B may be moved to the server A 820. In detail, the IP address of the server A 820 may be shared with the client 840 of the server B 810. In this case, the client 840 may be moved while the entrance of the client who wants to further access the A server 820 and the B server 810 is blocked. The user side 830 of the client 840 may request access to the A server 820 based on the IP address of the A server. For example, the user side 830 may have a connector 850 provided at the channel and lobby server side. Such a role of connecting the client 840 connected to the server B 810 to the server A 820 through the connector may be performed. Client 840 may connect to server A 820. Accordingly, the server A 820 may share the connection state of the client with the server B 810. If the client 840 successfully connects to the server A 820, the client 840 may terminate the connection of the server B 810. The server A 820 may update the information of the client, or the information of the server A may be updated to the client 840.

Since the load balancing method according to an embodiment allows a client to have a dual connection structure between the transfer target server and the scheduled termination server, information may be transmitted and received with the scheduled termination server even during the dual connection. In addition, as the double connection of the client is completed, the user's information may be transferred in a connection relationship between the scheduled termination server and the transfer target server while the connection with the scheduled termination server is terminated. Clients transferred to the transfer target server may in turn terminate the connection with the scheduled server, that is, the existing server. At this time, the process is not performed simultaneously, but serially. As you progress through the process, you work in sequence to prevent bottlenecks from occurring. As such, by double-connecting the transfer target server of the client and the scheduled server to be terminated, the client or the user of the client does not feel that the service is disconnected or a problem occurs, and can naturally use the service continuously.

The apparatus described above may be implemented as a hardware component, a software component, and / or a combination of hardware components and software components. For example, the devices and components described in the embodiments are, for example, processors, controllers, arithmetic logic units (ALUs), digital signal processors, microcomputers, field programmable gate arrays (FPGAs). Can be implemented using one or more general purpose or special purpose computers, such as a programmable logic unit (PLU), a microprocessor, or any other device capable of executing and responding to instructions. The processing device may execute an operating system (OS) and one or more software applications running on the operating system. The processing device may also access, store, manipulate, process, and generate data in response to the execution of the software. For convenience of explanation, one processing device may be described as being used, but one of ordinary skill in the art will appreciate that the processing device includes a plurality of processing elements and / or a plurality of types of processing elements. It can be seen that it may include. For example, the processing device may include a plurality of processors or one processor and one controller. In addition, other processing configurations are possible, such as parallel processors.

The software may include a computer program, code, instructions, or a combination of one or more of the above, and configure the processing device to operate as desired, or process independently or collectively. You can command the device. Software and / or data may be any type of machine, component, physical device, virtual equipment, computer storage medium or device in order to be interpreted by or to provide instructions or data to the processing device. It can be embodied in. The software may be distributed over networked computer systems so that they may be stored or executed in a distributed manner. Software and data may be stored on one or more computer readable recording media.

The method according to the embodiment may be embodied in the form of program instructions that can be executed by various computer means and recorded in a computer readable medium. The computer readable medium may include program instructions, data files, data structures, etc. alone or in combination. Program instructions recorded on the media may be those specially designed and constructed for the purposes of the embodiments, or they may be of the kind well-known and available to those having skill in the computer software arts. Examples of computer readable recording media include magnetic media such as hard disks, floppy disks and magnetic tape, optical media such as CD-ROMs, DVDs, and magnetic disks such as floppy disks. Magneto-optical media, and hardware devices specifically configured to store and execute program instructions, such as ROM, RAM, flash memory, and the like. Examples of program instructions include machine code, such as produced by a compiler, as well as high-level language code that can be executed by a computer using an interpreter or the like.

Although the embodiments have been described by the limited embodiments and the drawings as described above, various modifications and variations are possible to those skilled in the art from the above description. For example, the described techniques may be performed in a different order than the described method, and / or components of the described systems, structures, devices, circuits, etc. may be combined or combined in a different form than the described method, or other components. Or even if replaced or substituted by equivalents, an appropriate result can be achieved.

Therefore, other implementations, other embodiments, and equivalents to the claims are within the scope of the claims that follow.

Claims (20)

In the load balancing method between the server implemented as a computer,
Determining the remaining capacity of the server to which the channel is allocated as the communication through the network with the at least one server is performed, and searching the server to be cleaned up;
Connecting a client connected to the scheduled termination server to the transfer target server based on the scheduled termination server selected for the searched clearance target servers and a transfer target server; And
Updating information on the scheduled termination server or a client connected to the scheduled termination server to the transfer target server according to a connection state shared from the transfer target server to the scheduled termination server;
Load balancing method between servers comprising a. The method of claim 1,
Searching for the cleanup target server,
Searching for cleanup target servers including the transfer target server or the scheduled termination server based on the number of clients connected to the channel of each server and the remaining capacity of the counterpart server other than the server;
Load balancing method between servers comprising a. The method of claim 2,
Searching for the cleanup target server,
Clustering a previous target server or a scheduled termination server based on the number of clients connected to the channel of each server and the remaining capacity of the other server other than the server to the cleaning target server;
Load balancing method between servers comprising a. The method of claim 3,
Searching for the cleanup target server,
Listing the transfer target server clustered with the cleanup target servers or the scheduled server to be terminated;
Load balancing method between servers comprising a. The method of claim 3,
Searching for the cleanup target server,
Determining the number of clients connected to at least one channel of each server and the remaining capacity of a counterpart server other than the server based on a predetermined criterion;
Including,
The preset criterion is any one of a time section, a period section, a day of the week, or a date set to search the server to be cleaned up. The method of claim 1,
The step of connecting the client connected to the server to be finalized with the transfer target server,
Sharing the address information of the transfer target server to the client connected to the scheduled termination server, and blocking the scheduled termination server and the client additionally requested to access the transfer target server
Load balancing method between servers comprising a. The method of claim 6,
The step of connecting the client connected to the server to be finalized with the transfer target server,
Connecting a client of the scheduled termination server to the transfer target server when a connection to the transfer target server is requested from the client of the scheduled termination server based on address information of the shared transfer target server;
Load balancing method between servers comprising a. The method of claim 6,
The client of the scheduled server to end,
And multiple accesses to the server to be terminated and the target server to be transferred, and to transmit and receive information to and from the server to be terminated in the state of the multiple access. The method of claim 1,
Updating to the transfer target server,
Sharing a connection state with a client connected to the transfer target server from the transfer target server to the end target server as the client connected to the transfer target server is connected to the transfer target server;
Load balancing method between servers comprising a. The method of claim 9,
Updating to the transfer target server,
Terminating the operation of the server to be terminated when the connection of the server to be terminated from the client is terminated;
Load balancing method between servers comprising a. The method of claim 9,
Updating to the transfer target server,
Transmitting the client's information to the transfer target server in a connection relationship between the transfer target server and the termination server while disconnecting the termination server from the client;
Load balancing method between servers comprising a. A load balancing server for performing load balancing between servers implemented by a computer,
A search unit for searching the server to be arranged by determining the remaining capacity of the server to which the channel is allocated as the communication through the network with the at least one server;
A connection unit which connects a client connected to the scheduled server to be terminated to the transfer target server based on the scheduled termination server selected by the searched grooming target servers and a transfer target server; And
An update unit for updating information about a client to be connected to the server to be terminated or the server to be terminated according to a connection state shared from the server to which the server is to be migrated to the server to be transferred to the server;
Load balancing server comprising a. The method of claim 12,
The search unit,
Searching for cleanup target servers including the transfer target server or the scheduled termination server based on the number of clients connected to the channel of each server and the remaining capacity of the counterpart server other than the server;
Load balancing server, characterized in that. The method of claim 13,
The search unit,
The previous target server or the scheduled end server, which is determined based on the number of clients connected to the channel of each server and the remaining capacity of the other server other than the server, is clustered into the grooming target server and clustered into the grooming target servers. To list the target server or the server to be transferred
Load balancing server, characterized in that. The method of claim 13,
The search unit,
Determining the number of clients connected to at least one channel of each server and the remaining capacity of a counterpart server other than the server based on a predetermined criterion;
The preset criterion is any one of a time interval, a period interval, a day of the week, or a date set for searching the server to be cleaned up. The method of claim 11,
The connecting portion,
Sharing the address information of the transfer target server to the client connected to the scheduled termination server, and blocking the additional termination request server and the client requested to access the transfer target server
Load balancing server, characterized in that. The method of claim 16,
The connecting portion,
Connecting the client of the scheduled server to the target server as a connection is requested from the client of the scheduled server to the target server based on the address information of the shared target server.
Load balancing server, characterized in that. The method of claim 16,
And a client of the scheduled server to be multiplexed to the scheduled server and the transfer target server, and to transmit and receive information to and from the scheduled server in the multiple access state. The method of claim 11,
The update unit,
As the client connected to the server to be terminated is connected to the server to be transferred, the connection state with the client connected to the server to be transferred from the server to the server is shared.
Load balancing server, characterized in that. The method of claim 9,
Updating to the transfer target server,
The connection between the transfer target server and the server to be terminated is terminated while the operation of the server to be terminated is terminated as the connection of the server to be terminated from the client is terminated and the server to be terminated is disconnected from the client. Transferring the client's information to the transfer target server in a relationship
Load balancing server, characterized in that.

Images