KR20230135233A - Session management device and its control method - Google Patents

Abstract

The present invention relates to a device and a control method for efficiently managing a session established between a client terminal and a server. More specifically, the present invention includes a wireless communication unit, a memory storing instructions, and a processor configured to execute the stored instructions, the processor configured to: a first session for connection with a client terminal and a connection with a first server; Control the wireless communication unit to maintain a second session for, control the wireless communication unit to perform relay between the client terminal and the first server through the first and second sessions, and prevent the first server from failing. It relates to a session management device that transfers the connection with the first server from the first server to the second server when an error occurs.

Description

Session management device and its control method {SESSION MANAGEMENT DEVICE AND ITS CONTROL METHOD}

The present invention relates to session management technology, and more specifically, to a session management device and its control method for monitoring whether a server failure occurs and effectively managing sessions in preparation for failure.

In order for a client terminal to connect to a server and receive a game or messenger service, a sustainable session connection must be maintained between the client terminal and the server. This sustainable session connection is different from a session connection where one-time data is exchanged, and because it is premised on continuous data exchange, the connection between the client terminal and the server is continuously maintained.

When a failure occurs in a server, the connection with that server is disconnected. The client terminal detects when the connection is lost and repeatedly reconnects to the failed server or another server. If the number of client terminals performing reconnection increases, there is a problem that the overload of reconnection traffic instantaneously flowing to other servers can spread to a full-scale failure.

Therefore, there is a need for technology to effectively manage problematic sessions when a server failure occurs.

The problem to be solved by the present invention is to provide a session management device that is located between the user and the service server and prevents the client terminal from recognizing network disconnection due to distribution or failure on the server side.

Another problem to be solved by the present invention is to provide a session management device that improves user usability by forwarding connections to other servers in normal service and blocks reconnection traffic to prevent it from spreading to a full-scale failure.

The technical problems to be achieved in the present invention are not limited to the technical problems mentioned above, and other technical problems not mentioned will be clearly understood by those skilled in the art from the description below. You will be able to.

According to one aspect of the present invention to solve the above or other problems, a wireless communication unit; Memory for storing instructions; and a processor configured to execute the stored instructions, wherein the processor: controls the wireless communication unit to maintain a first session for a connection with a client terminal and a second session for a connection with a first server, and The wireless communication unit is controlled to relay between the client terminal and the first server through first and second sessions, and when a failure occurs in the first server, the first server establishes a connection with the first server. 2 Provides a session management device that transfers to the server.

The first and second servers are servers provided to provide certain services,

In order to provide the predetermined service, login information may be requested from the client terminal.

If there are a plurality of client terminals to be relayed, and a failure occurs while a connection with the first server is maintained for each of the plurality of client terminals, the processor sequentially connects the plurality of client terminals to the first server. 2 Can be transferred to server.

When the processor transfers the connection with the first server, if the failure occurs, the processor establishes a third session with the second server and performs the transfer by replacing the second session with the third session. can do.

The processor may continuously perform the relay through the first and third sessions.

The memory further stores login information of the client terminal, and the processor automatically logs in to the second server using the stored login information when transferring the second session in establishing the third session. can be performed.

According to another aspect of the present invention to solve the above or other problems, controlling the wireless communication unit to maintain a first session for a connection with a client terminal and a second session for a connection with a first server; Controlling the wireless communication unit to perform relay between the client terminal and the first server through the first and second sessions; and transferring a connection with the first server from the first server to a second server when a failure occurs in the first server.

The first and second servers are servers equipped to provide a predetermined service, and may request login information from the client terminal to provide the predetermined service.

In the transferring step, if there are a plurality of relay target client terminals and a failure occurs while a connection with the first server is maintained for each of the plurality of client terminals, the processor connects the plurality of client terminals to the plurality of first servers. The connection can be sequentially transferred to the second server.

The transferring step may include establishing a third session with the second server when the failure occurs; and performing transfer by replacing the second session with the third session.

The relaying step may be performed continuously through the first and third sessions.

Further comprising the step of further storing the login information of the client terminal in the memory, and the step of establishing the third session includes automatically sending the information to the second server using the stored login information when transferring the second session. You can log in with .

The effects of the session management device according to the present invention will be described as follows.

According to at least one of the embodiments of the present invention, there is an advantage that the client terminal cannot recognize network disconnection due to distribution or failure on the server side.

In addition, according to at least one of the embodiments of the present invention, there is an advantage of improving user usability by forwarding the connection to another server in normal service and preventing reconnection traffic from causing a full-scale failure.

Further scope of applicability of the present invention will become apparent from the detailed description that follows. However, since various changes and modifications within the spirit and scope of the present invention may be clearly understood by those skilled in the art, the detailed description and specific embodiments such as preferred embodiments of the present invention should be understood as being given only as examples.

Figure 1 is a diagram illustrating a session connection when there is no session management device 100 according to an embodiment of the present invention.
FIG. 2 is a diagram illustrating a session connection when there is a session management device 100 according to an embodiment of the present invention.
Figure 3 shows a control flowchart for establishing a session between the first client terminal 110-1 and the first server 120-1 by the session management device 100 according to an embodiment of the present invention.
Figure 4 is a diagram showing the relationship between the first and second sessions 130-2 and sockets according to an embodiment of the present invention.
FIG. 5 shows a flowchart of data transmission and reception between a first client terminal 110-1 and a first server 120-1 connected by the session management device 100 according to an embodiment of the present invention.
Figure 6 shows a flow chart in which the session management device 100 monitors failures in existing connected servers and establishes new session connections with other servers according to an embodiment of the present invention.
Figure 7 is a diagram showing the relationship between the first to fourth sessions 130-1 to 130-4 and sockets according to an embodiment of the present invention.
Figure 8 shows the session management device 100 assigning the first and second client terminals 110-1 and 110-2 to the first and second servers 120-2, respectively, according to an embodiment of the present invention. Shows the state.
Figure 9 shows a conceptual diagram of redirecting a session according to an embodiment of the present invention.
FIG. 10 is a diagram illustrating the configuration of a session management device 100 according to an embodiment of the present invention.

Hereinafter, embodiments disclosed in the present specification will be described in detail with reference to the attached drawings. However, identical or similar components will be assigned the same reference numbers regardless of reference numerals, and duplicate descriptions thereof will be omitted. The suffixes “module” and “part” for components used in the following description are given or used interchangeably only for the ease of preparing the specification, and do not have distinct meanings or roles in themselves. Additionally, in describing the embodiments disclosed in this specification, if it is determined that detailed descriptions of related known technologies may obscure the gist of the embodiments disclosed in this specification, the detailed descriptions will be omitted. In addition, the attached drawings are only for easy understanding of the embodiments disclosed in this specification, and the technical idea disclosed in this specification is not limited by the attached drawings, and all changes included in the spirit and technical scope of the present invention are not limited. , should be understood to include equivalents or substitutes.

Terms containing ordinal numbers, such as first, second, etc., may be used to describe various components, but the components are not limited by the terms. The above terms are used only for the purpose of distinguishing one component from another.

When a component is said to be "connected" or "connected" to another component, it is understood that it may be directly connected to or connected to the other component, but that other components may exist in between. It should be. On the other hand, 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.

Singular expressions include plural expressions unless the context clearly dictates otherwise.

In this application, terms such as “comprise” or “have” are intended to designate the presence of features, numbers, steps, operations, components, parts, or combinations thereof described in the specification, but are not intended to indicate the presence of one or more other features. It should be understood that this does not exclude in advance the possibility of the existence or addition of elements, numbers, steps, operations, components, parts, or combinations thereof.

Figure 1 is a diagram illustrating a session connection when there is no session management device 100 according to an embodiment of the present invention.

Referring to the system 10 shown in FIG. 1, first to fourth servers 120-1 to 120-4 are provided to provide specific services, and a client terminal 110- to receive specific services. 1 to 110-4) are provided to connect to the first to fourth servers 120-1 to 120-4.

The client terminals (110-1 to 110-4) establish a session connection with the servers (120-1 to 120-4) to receive a specific service. In this case, the connected session will not be a one-time connection, but will be a session that allows continuous data transmission and reception. For example, real-time streaming services, game services, or real-time messaging services can be provided through such sessions.

In order to enable continuous data transmission and reception, a socket-based session may be established, but embodiments of the present invention are not necessarily limited thereto. A socket-based session refers to a session in which a socket is created for each subject performing data transmission and reception, and a connection is maintained between the created sockets to exchange data in real time.

Hereinafter, the session used in the present invention refers to a session capable of continuous data transmission and reception as described above.

If the session management device 100 is not present, the client terminals 110-1 to 110-4 are directly connected to the servers 120-1 to 120-4. That is, the connection of the sessions 130-1 to 130-4 is created between the client terminals 110-1 to 110-4 and the servers 120-1 to 120-4.

When the client terminals 110-1 to 110-4 transmit login information to the servers 120-1 to 120-4, the servers 120-1 to 120-4 check whether the login information is correct. If the login information is correct, the server (120-1 to 120-4) can establish a session connection with the corresponding client terminal (110-1 to 110-4). For example, in the illustrated example, when the first client terminal 110-1 wants to connect a session with the first server 120-1, token T1, which is an example of login information, is sent to the first server 120-1. ), and the first server 120-1 can establish the first session 130-1 after checking whether the token T1 is correct.

In the drawing, the first and second client terminals 110-1 and 110-2 are connected to the first server 120-1. That is, the first session 130-1 is established between the first client terminal 110-1 and the first server 120-1, and the second client terminal 110-2 and the first server 120-1 1) A second session (130-2) is established.

If a failure occurs in the first server 120-1, the first and second client terminals 110-1 and 110-2 detect the failure. And, the first and second client terminals 110-1 and 110-2 will continuously attempt to reconnect to continue the service. Reconnection attempted in this way can be attempted not only with the failed first server 120-1 but also with the properly operating second server 120-2.

If the number of client terminals currently connected to the first server 120-1 is large, the number of reconnection attempts will inevitably increase. At this time, if reconnection attempts to the second server 120-2 rapidly increase, the risk of failure of the second server 120-2, which was operating properly, also increases. This is because, if the existing cause of failure of the first server (120-1) was due to the large number of client terminals being connected, all of the large number of client terminals may attempt to reconnect to the second server (120-2). Because. In other words, if a situation like this occurs, there is a risk that it will spread to a full-scale failure, with even servers that were operating normally experiencing failures.

In order to solve this problem, in one embodiment of the present invention, a separate session management device 100 is provided to relay the client's continuous reconnection problem in the middle, and a full reconnection attempt is made through the session management device 100. This is a suggestion to minimize the spreading phenomenon.

FIG. 2 is a diagram illustrating a session connection when there is a session management device 100 according to an embodiment of the present invention.

Likewise, referring to the system 10' shown in FIG. 2, first to fourth servers 120-1 to 120-4 are provided to provide a specific service, and a client terminal to receive the specific service. (110-1 to 110-4) are provided to connect to the first to fourth servers (120-1 to 120-4). However, at least one session management device 100 may be provided between the client terminals 110-1 to 110-4 and the servers 120-1 to 120-4.

The session management devices 100-1 and 100-2 are devices for relaying sessions between client terminals 110-1 to 110-4 and servers 120-1 to 120-4.

The connection between the first client terminal 110-1 and the first server 120-1 is established between the first client terminal 110-1 and the first session management device 100-1 ( 130-1) and a second session 130-2 established between the first session management device 100-1 and the first server 120-1.

Referring to Figure 3, the session establishment process will be described.

Figure 3 shows a control flowchart for establishing a session between the first client terminal 110-1 and the first server 120-1 by the session management device 100 according to an embodiment of the present invention.

The first client terminal 110-1 requests session establishment to the first management socket of the first session management device 100-1 through the first user socket (S301). The session establishment request may include login information (eg, token T1) of the first client terminal 110-1. The first session management device 100-1 transmits the received session establishment request to the first server 120-1 (S302). At this time, the session establishment request transmitted may also be transmitted along with the login information of the first client terminal 110-1.

The first server 120-1 that has received the session establishment request performs authentication based on the login information and registers the session (S303). At this time, the registered session includes the first session 130-1 formed between the first client terminal 110-1 and the first session management device 100-1, and the first session management device 100-1. It may be a second session 130-2 formed between the first server 120-1.

In another embodiment of the present invention, the session registered in step S303 may be the second session 130-2 formed between the first session management device 100-1 and the first server 120-1. . Also, the first session 130-1 formed between the first client terminal 110-1 and the first session management device 100-1 may be registered in step S305, which will be described later.

Embodiments of the present invention will not be limited by the registration subject or order of the first and second sessions 130-2.

Figure 4 is a diagram showing the relationship between the first and second sessions 130-2 and sockets according to an embodiment of the present invention.

The first session 130-1 is between the first user socket 401-1 of the first client terminal 110-1 and the first manager socket 402-1 of the first session management device 100-1. is established. And the second session 130-2 may be established between the first manager socket 402-1 and the first server socket 403-1 of the first server 120-1.

Returning to FIG. 3, the first server 120-1 may return the session establishment result to the first session management device 100-1 (S304).

The first session management device 100-1 registers a session map based on the session establishment result received. A session map refers to data stored by matching socket information, which is information about a socket for establishing a session, and login information used to establish a session. In other words, the session map may be data needed for the session management device 100 to manage a session. As shown in FIG. 4, the session map is divided into the first and second sessions 130 by the first user socket 401-1, the first manager socket 402-1, and the first server socket 403-1. -2) Information that has been established can be stored.

Table 1 below shows the session map in the example of Figures 3 and 4.

client side session server side session Authentication information (token) 1st session (130-1) 2nd session (130-2) T1(110-1)

The first session management device 100-1 may deliver the session establishment result to the first client terminal 110-1 (S306).

Hereinafter, with reference to FIG. 5, the connection between the first client terminal 110-1 and the first server 120-1 will be described in more detail.

FIG. 5 shows a flowchart of data transmission and reception between a first client terminal 110-1 and a first server 120-1 connected by the session management device 100 according to an embodiment of the present invention.

If the first client terminal 110-1 wants to send a request to the first server 120-1, the request may be sent sequentially through the first and second sessions 130-2.

First, when a predetermined request is transmitted to the first session management device 100-1 through the first session 130-1 (S501), the first session management device 100-1 sends the received predetermined request to the second session. It can be delivered (S502) to the first server (120-1) through (130-2).

The first server 120-1, which has received the predetermined request, performs an operation corresponding to the predetermined request (S503) and generates a response. The response generated by the first server 120-1 may also be transmitted in the opposite direction. When a response is transmitted to the first session management device 100-1 by the second session 130-2 (S504), the first session management device 100-1 sends the response to the first client terminal 110-1. It can be delivered to 1) (S505).

Figure 6 shows a flow chart in which the session management device 100 monitors failures in existing connected servers and establishes new session connections with other servers according to an embodiment of the present invention.

The first session management device 100-1 monitors the occurrence of a failure in the previously connected first server 120-1 in step S601. If a failure of the first server 120-1 is detected, the first session management device 100-1 deletes the second session 130-2 being established with the first server 120-1 (S602) And, another new second server 120-2 is searched (S603).

When the second server 120-2 is found as a new server, the first session management device 100-1 transmits a request for establishing a new session to the second server 120-2 (S604). At this time, the request for establishing a new session will include pre-stored login information (token T1 described above).

The second server 120-2 that has received the request may perform authentication based on the login information included in the request and then register a new session (S605). Additionally, the second server 120-2 may register a session and then return the registration result to the first session management device 100-1 (S606). The session established with the second server in this way is called the third session (130-3).

Figure 7 is a diagram showing the relationship between the first to fourth sessions 130-1 to 130-4 and sockets according to an embodiment of the present invention.

The second session 130-2 established between the first manager socket 402-1 and the first server socket 403-1 of the first server 120-1 is connected to the first server 120-1. It is no longer maintained due to a disability. Accordingly, the first session management device 100-1 may remove the second session 130-2 by deleting the first manager socket 402-1.

Furthermore, in order to establish the third session 130-3, the first session management device 100-1 creates a second manager socket 402-2, and the second server of the second server 120-2 A socket 403-2 and a third session 130-3 can be established. In addition, the second manager socket 402-2 receives the first session 130-1 maintained by the existing first manager socket 402-1 and establishes a first session with the first user socket 401-1. (130-1) can be continued.

To summarize the relationship in FIG. 7, the first session 130-1 is maintained between the first user socket 401-1 and the second manager socket 402-2, and the third session 130-3 is maintained between the first user socket 401-1 and the second manager socket 402-2. It may be established between the second manager socket 402-2 and the second server socket 403-2 of the second server 120-2.

Returning to FIG. 6, the first session management device 100-1, which has received a reply of the third session 130-3 establishment result, registers the established third session 130-3 in the session map (S607). You can. In step S607, the session map is registered by registering the first and third sessions 130-3 through the first user socket 401-1, the first manager socket 402-1, and the first server socket 403-1. ) can be stored.

Table 2 below shows the session map in the example of Figures 6 and 7.

client side session server side session Authentication information (token) 1st session (130-1) 3rd session (130-3) T1(110-1)

In the procedures shown in FIGS. 6 and 7, the second session is deleted (S602), a new server is searched (S603), and a new session is established (S604 to 507) by the client terminals 110-1 to 110-4. ) will not be notified. That is, since the client terminals 110-1 to 110-4 are not directly connected to the server but are connected to the first session management device 100-1, they are maintained with the first session management device 100-1. As long as there is no problem in the first session 130-1, the failure of the servers 120-1 to 120-4 cannot be known.

It will be apparent that through the newly established third session 130-3, the request delivery process (S501, S502) and the response delivery process (S504, S505) described above with reference to FIG. 5 can be performed.

Meanwhile, as the types of multimedia devices have recently become more diverse, there are many cases where a single user uses multiple multimedia devices simultaneously. For example, a smartphone that is relatively small in size and can be carried by a user in a pocket or hand, and a tablet PC that is relatively large in size and can be carried in a bag, etc.

In this situation, if the smartphone and tablet PC are connected to different servers, it is not efficient because communication between servers is also required for data exchanged between the smartphone and tablet PC. In other words, there is a cost for data communication between servers. Therefore, it would be desirable for the same user to be connected to the same server.

To this end, the present invention proposes to manage sessions for a single user by concentrating them on one server using a session management device. An embodiment for this will be described with reference to FIGS. 8 and 9.

Figure 8 shows the session management device 100 assigning the first and second client terminals 110-1 and 110-2 to the first and second servers 120-2, respectively, according to an embodiment of the present invention. Shows the state.

Referring to the drawing, the first client terminal 110-1 is connected to the first server 120-1 through the first and second sessions 130-1 and 130-2. Additionally, the second client terminal 110-2 is connected to the second server 120-2 through the third and fourth sessions 130-3 and 130-4.

In establishing a connection, when the first client terminal 110-1 transmits a session connection request to the session management device 100, it may also transmit first login information (for example, token T1), which is its own login information. there is. Likewise, when the second client terminal 110-2 transmits a session connection request to the session management device 100, it may also transmit second login information (eg, token T2).

When the first server 120-1 receives a session connection request from the session management device 100, it performs authentication based on the first login information included and then registers the session (first and second sessions) ) You will be able to do it.

Likewise, when the second server 120-2 receives a session connection request from the session management device 100, it performs authentication based on the second login information included and then registers the session (third and fourth session). Furthermore, the second server 120-2 may check whether there is a session of a user identical to the second login information when performing authentication. That is, the second server 120-2 will be able to check whether there is another session established using the same user's token based on token T2.

If the first and second client terminals 110-1 and 110-2 are terminals used by a single user, it is not desirable for them to be connected to different servers as shown.

Accordingly, if it is confirmed that there is another session established using the same user's token, the second server 120-2 redirects the session to the server where the session was established.

Figure 9 shows a conceptual diagram of redirecting a session according to an embodiment of the present invention.

When a redirecting command is received from the second server 120-2, the session management device 100 removes the second manager socket 402-2 and the established fourth session 130-4. And the session management device 100 creates a third manager socket 402-3. The third manager socket 402-3 receives the third session 130-3 maintained by the existing second manager socket 402-2 and establishes a third session 130 with the second user socket 401-1. -3) continues. And, the session management device 100 establishes a fifth session 130-5 connecting the third manager socket 402-3 and the first server socket 403-1, and creates the third and fifth sessions ( 130-3, 130-5) are connected.

Table 3 below shows the registered session map in the example of FIG. 9.

client side session server side session Authentication information (token) 1st session (130-1) 3rd session (130-3) T1(110-1) 3rd session (130-3) Session 5 (130-5) T2(110-2)

In this way, when the fourth session (130-4) connected to the second server (120-2) is removed and redirected to the first server (120-1) through the fifth session (130-5) , it will be possible to minimize unnecessary costs incurred due to data communication between servers.

FIG. 10 is a diagram illustrating a flowchart of how the session management device 100 redirects a session of the same user according to an embodiment of the present invention.

As described above, the first client terminal 110-1 is connected to the first server 120-1 through the first and second sessions 130-1 and 130-2. First, an operation (S1001 to S1005) in which the first client terminal 110-1 establishes a session with the first server 120-1 through the session management device 100 will be described.

The first client terminal 110-1 transmits a session establishment request (S1001) to the session management device 100. In establishing a connection, when the first client terminal 110-1 transmits a session connection request to the session management device 100 (S1001), the first login information (for example, token T1), which is its own login information, is sent to the session management device 100. can be transmitted together.

Next, the session management device 100 transmits a session establishment request to the first server 120-1 (S1002). When the first server 120-1 receives a session connection request from the session management device 100, the first server 120-1 performs authentication based on the first login information included, and then registers the session (step S1003) (first and register for the second session).

After registering the session, the first server 120-1 returns a session establishment result to the session management device 100 (S1004). As described above, a session map can be registered based on the returned result. Subsequently, the session management device 100 may deliver the response result to the first client terminal 110-1 (S1005).

Next, the procedure (S1006 to S1010) in which the second client terminal 110-2 attempts to connect to the second server 120-2 will be described. At this time, it is assumed that the first and second client terminals 110-1 and 110-2 are terminals used by the same user, and the case of redirecting will be described.

The second client terminal 110-2 transmits a session establishment request to the session management device 100 (S1006).

Likewise, when the second client terminal 110-2 transmits a session connection request to the session management device 100, it may also transmit second login information (eg, token T2).

The session management device 100, which has received the session establishment request, transmits the session establishment request to the second server 120-2 (S1007).

The second server 120-2, which has received the session establishment request, checks the second login information to determine whether there is another session established for the same user (S1008). That is, in the illustrated example, it is determined whether there are first and second sessions 130-1 and 130-2 connecting the first client terminal 110-1 and the first server 120-1.

If there is another session established for the same user, the second server 120-2 redirects the session to the first server 120-1 (S1009) and sends a session redirection request to session management. A reply is sent to the device 100 (S1010).

The session management device 100, which has received a response to the session redirection request, transmits the session redirection request to the first server 120-1 (S1011). And the first server 120-1 may perform authentication based on the second login information (token T2) and then register a session (step S1012).

The first server 120-1 may reply to the session management device 100 with a result of session registration through redirection.

Subsequently, when the session management device 100 receives a session redirection result reply, it may register a session map based on this (S1014) and deliver the session establishment result to the second client terminal 110-2 (S1015). .

According to the above-described embodiment, there is an advantage that data communication costs between servers can be minimized by concentrating client terminals belonging to the same user to one server.

FIG. 11 is a diagram illustrating the configuration of a session management device 100 according to an embodiment of the present invention.

Referring to FIG. 11, the session management device 100 includes a processor 1101 and a memory 1102.

Memory 1102 stores one or more instructions executable by processor 1101.

Processor 1101 executes one or more instructions stored in memory 1102. Processor 1101 may perform one or more operations described above with respect to FIGS. 1-9 by executing instructions.

The wireless communication unit 1103 exchanges data between at least one client terminal (110-1 to 110-4) and the server (120-1 to 120-4).

Although the embodiment of the session management device and its control method according to the present invention has been described above, this is explained as at least one embodiment, and the technical idea, structure, and operation of the present invention are not limited thereby. , the scope of the technical idea of the present invention is not limited/limited by the drawings or the description referring to the drawings. In addition, the concept and embodiments of the invention presented in the present invention can be used by those skilled in the art as a basis for modifying or designing other structures to achieve the same purpose of the present invention. , Equivalent structures modified or changed by those skilled in the art to which the present invention pertains are bound to the technical scope of the present invention described in the claims, and do not depart from the spirit or scope of the invention described in the claims. Various changes, substitutions, and changes are possible within limits.

Claims (13)

Department of Wireless Communications;
Memory for storing instructions; and
a processor configured to execute the stored instructions, the processor configured to:
Controlling the wireless communication unit to maintain a first session for connection with a client terminal and a second session for connection with a first server,
Controlling the wireless communication unit to perform relay between the client terminal and the first server through the first and second sessions,
Transferring the connection with the first server to the second server when a failure occurs in the first server,
Session management device.
The method of claim 1, wherein the first and second servers:
It is a server equipped to provide certain services,
Requesting login information from the client terminal to provide the predetermined service,
Session management device.
According to claim 1,
If there are a plurality of client terminals to be relayed, and a failure occurs while a connection with the first server is maintained for each of the plurality of client terminals, the processor sequentially connects the plurality of client terminals to the first server. 2 Transfer to server,
Session management device.
The method of claim 1, wherein when the processor transfers a connection with the first server,
Establishing a third session with the second server,
Performing the transfer by replacing the second session with the third session,
Session management device.
The method of claim 4, wherein the processor continuously performs the relaying through the first and third sessions.
Session management device.
According to claim 5,
The memory is,
Further storing the login information of the client terminal,
In establishing the third session, the processor automatically logs in to the second server using the stored login information when transferring the second session.
Session management device.
Controlling the wireless communication unit to maintain a first session for a connection with a client terminal and a second session for a connection with a first server;
Controlling the wireless communication unit to perform relay between the client terminal and the first server through the first and second sessions; and
Comprising the step of transferring the second session from the first server to the second server when a failure occurs in the first server,
Control method of session management device.
The method of claim 7, wherein the first and second servers:
It is a server equipped to provide certain services,
Requesting login information from the client terminal to provide the predetermined service,
Control method of session management device.
The method of claim 7, wherein the transferring step includes:
If there are a plurality of client terminals to be relayed, and a failure occurs while a connection with the first server is maintained for each of the plurality of client terminals, the processor sequentially connects the plurality of client terminals to the first server. 2 Transfer to server,
Control method of session management device.
The method of claim 7, wherein the transferring step includes:
establishing a third session with the second server; and
Comprising performing a transfer by replacing the second session with the third session,
Control method of session management device.
The method of claim 10, wherein the relaying step continuously performs the relaying through the first and third sessions.
Control method of session management device.
According to claim 11,
Further comprising the step of storing login information of the client terminal in the memory,
The step of establishing the third session includes automatically logging in to the second server using the saved login information when transferring the second session.
Control method of session management device.
A computer program combined with hardware and stored on a medium to execute the method of any one of claims 7 to 12.