JP6266502B2 - Remote desktop cooperation processing system and client state management server - Google Patents

Description

  The present invention relates to a remote desktop cooperation processing system and a client state management server.

  Conventionally, operating a desktop of a computer installed remotely from a user's operation terminal, such as a proprietary remote desktop or VNC (Virtual Network Computing) using RFB (Remote Frame Buffer) protocol of open source technology That is, there is a remote desktop system. Teleworkers sometimes work while using a remote desktop system from a local operating terminal. Here, a terminal on which a remote desktop system client operates is referred to as an “operation terminal”, and a computer to be operated is referred to as a “remote computer”. Real-time communication tool operation on a remote computer is not possible because VNC does not support voice media transfer. Other proprietary extensions include the use of camera and microphone resources on the operation terminal and the extension of a high-speed media transfer function using UDP (User Datagram Protocol).

"The RFB Protocol Tristan Richardson Real VNC Ltd (formerly of Olivetti Research Ltd / AT & T Labs Cambridge Version 3.8 Last updated 26 November 2010)", [online], [searched November 18, 2014], Internet <http: // www.realvnc.com/docs/rfbproto.pdf>

  When voice communication is performed using a real-time communication tool on a remote computer, the voice passes through a VPN (Virtual Private Network) server and various relay servers before reaching a personal computer (PC) in the seat. Therefore, there is a problem in that sound interruption or delay occurs in voice communication and sufficient call quality cannot be ensured. In order to solve such a problem, it is effective in terms of quality to operate a real-time communication tool on a personal computer, not on a remote computer, and perform voice communication without going through the remote computer. The user must suspend the operation of the remote computer from the personal computer and re-execute the procedure for operating the personal computer. That is, there is a problem that a user who is operating a remote computer from his / her desk PC needs a complicated operation to make a voice call with sufficient quality.

  Accordingly, an object of the present invention made in view of such a point is to perform a process in which the remote computer (control client) cannot be executed without complicated operations, or processing that lowers the quality when executed is performed on the operation terminal (controlled client). ). For example, one of the objects of the present invention is to make it possible to directly communicate a communication tool on an operation terminal from a remote desktop system.

  In order to solve the above problems, a remote desktop cooperation processing system according to the present invention includes a control client that is a remote desktop system server and a controlled client that is a remote desktop system client. A remote desktop cooperation processing system that cooperates with a client state management server and a subsystem server, wherein the authentication server is authenticated by the authentication function unit that authenticates the controlled client and the control client, and the authentication function unit. A session management unit that generates HTTP session information representing a session to the authentication server of each of the controlled client and the control client, and the control client performs control related to predetermined processing. Requesting the client state management server, the client state management server, the client state information indicating whether the control client and the controlled client are a control client or a controlled client, respectively, the HTTP session information, A client state management unit that associates and stores, and a subsystem management unit that delegates the predetermined process to the subsystem server when requested by the control client to execute the predetermined process. The subsystem server performs control for the controlled client to perform the predetermined process associated with the control client and stored in the client state management unit when the predetermined process is delegated. It has an original function part to perform.

  The client state management server according to the invention described in claim 6 is a client state management that cooperates with a plurality of remote desktop systems, each including a control client that is a remote desktop system server and a controlled client that is a remote desktop system client. Server status information indicating whether the controlled client and the controlled client are a controlled client or a controlled client, respectively, and an HTTP relating to an HTTP session to the controlled server and the authentication client of the controlled client A client status management unit that stores session information in association with each other, and when the control client requests control for executing a predetermined process, the client status information Serial based on the HTTP session information, and a sub-system management unit to delegate the sub-system server control for the controlled client executes the predetermined processing.

  According to the present invention, it is possible to cause an operation terminal (controlled client) to execute a process in which a remote computer (control client) cannot be executed without performing a complicated operation or the quality when it is executed is lowered.

It is a function block diagram of the remote desktop system cooperation process which concerns on embodiment. It is a conceptual diagram showing the key value store of the connection management part shown in FIG. It is a conceptual diagram showing the key value store of the client state management part shown in FIG. It is a function block diagram of the signaling server which concerns on embodiment. It is a conceptual diagram showing the key value store of the call state management part shown in FIG. It is a conceptual diagram showing the key value store of the routing table part shown in FIG. It is a processing sequence figure concerning login of this embodiment. It is a processing sequence figure concerning a client status report of this embodiment. It is a processing sequence figure concerning the telephone call of this embodiment.

  Embodiments of the present invention will be described below with reference to the drawings.

<< Functional configuration of remote desktop linkage processing system linkage processing >>
First, the functional configuration of the remote desktop cooperation processing system 1 of this embodiment will be described with reference to FIG.

  The remote desktop cooperation processing system 1 is a system for making a call between a plurality of users who respectively use the remote desktop system 2, and includes a controlled client 10 and a control client 20 as shown in FIG. A desktop system 2, an authentication server 30, a client state management server 40, a subsystem server 50, and a load balancer 60 are provided. Hereinafter, the controlled client 10 and the control client 20 are collectively referred to as “client”.

  The authentication server 30, the client state management server 40, and the subsystem server 50 are connected to the communication network, and transmit / receive information to / from the control client 20 and the controlled client 10 via the load balancer 60.

<Functional configuration of controlled client>
The controlled client 10 is an operation terminal, for example, and operates the desktop of the control client 20 by a remote desktop function. That is, the controlled client 10 operates as a remote desktop system client in the remote desktop system 2. The controlled client 10 receives user information including the user ID input by the user, and transmits the received user information to the authentication server 30 via the load balancer 60. In addition, the controlled client 10 transmits local client status information indicating that it is a “controlled client” to the client status management server 40.

  Further, the controlled client 10 transmits session description information to the subsystem server 50 via the load balancer 60 based on a request from the subsystem server 50. The session description information is information for starting a multimedia session that requires session announcement or session invitation, and is described using, for example, SDP (Session Description Protocol).

  When a call session is established under the control of the subsystem server 50, the first controlled client 10A (hereinafter simply referred to as “controlled client 10A”) among the plurality of controlled clients 10 and the second The controlled client 10B (hereinafter simply referred to as “controlled client 10B”) performs processing related to the call. Thereby, users of these controlled clients 10 can talk over the communication network.

<Functional configuration of control client>
The control client 20 is a remote computer, for example, and the desktop is operated by the controlled client 10 using the remote desktop function. That is, the control client 20 operates as a remote desktop system server in the remote desktop system 2.

  The control client 20 receives user information input by the user and transmits the received user information to the authentication server 30. Further, the control client 20 requests the client state management server 40 for predetermined processing. Specifically, the control client 20 transmits message connection request information representing a message connection request realized by Web Socket or the like to the client state management server 40. In addition, message connection response information representing a message connection response realized by Web Socket or the like transmitted from the client state management server 40 is received. Further, the control client 20 transmits remote client status information indicating that it is a “control client” to the client status management server 40.

  Also, a first control client 20A (hereinafter simply referred to as “control client 20A”) among the plurality of control clients 20 is connected to a second control client 20B (hereinafter simply referred to as “control client 20B”). Call session establishment request information indicating that the establishment of a call is requested (calling) is transmitted to the client state management server 40. When the call session establishment response information by the control client 20B is transmitted from the client state management server 40, the transmitted call session establishment response information is received. The call session establishment response information is information indicating that the control client 20B that has received the call session establishment request information responds to the establishment of the call session.

  When control session 20A receives call session disconnection request information requesting disconnection of the call session with control client 20B from client state management unit 42, control client 20A disconnects the call session related to the call session disconnection request information. The session disconnection response information is information indicating that the control client 20A that has received the session disconnection request information responds to the disconnection of the call session.

<Functional configuration of authentication server>
The authentication server 30 authenticates the user based on the user information transmitted from the controlled client 10 and the control client 20, and manages the HTTP session information related to the HTTP session related to the transmission. The authentication server 30 includes a user information storage unit 31, an authentication function unit 32, and a session management unit 33.

  The user information storage unit 31 stores user information including a user ID for identifying the user and a password.

  The authentication function unit 32 receives user information input from the user and transmitted from the controlled client 10 and the control client 20 via the load balancer 60. Further, the authentication function unit 32 performs user authentication using the user ID and password included in the received user information. Specifically, in the authentication function unit 32, the password stored in the user information storage unit 31 in association with the user ID included in the received user information is the same as the password included in the received user information. It is determined whether or not.

  The session management unit 33 generates HTTP session information representing a session to the authentication server 30 of each of the controlled client 10 and the control client 20 authenticated by the authentication function unit 32. Specifically, the session management unit 33 performs a message defined by the HTTP protocol when an HTTP session from the controlled client 10 and the control client 20 to the authentication server 30 is normally performed in the authentication by the authentication function unit 32. “200 OK” is transmitted. In addition, the session management unit 33 generates a session ID that uniquely identifies the HTTP session.

<Functional configuration of client status management server>
The client state management server 40 manages the client states of the controlled client 10 and the control client 20, and delegates control of processing related to the call session to the subsystem server 50.

  As shown in FIG. 1, the client state management server 40 includes a connection management unit 41, a client state management unit 42, a call state management unit 43, and a subsystem management unit 44.

  The connection management unit 41 includes a key / value store, and stores user IDs and session IDs of the controlled client 10 and the control client 20 in association with each other as illustrated in FIG. Specifically, the connection management unit 41 receives message connection request information representing a message connection request from the controlled client 10 via the load balancer 60. When the connection management unit 41 receives message connection request information, the connection management unit 41 requests HTTP session information from the authentication server 30. Further, the connection management unit 41 receives HTTP session information as a response from the authentication server 30, and associates the session ID included in the HTTP session information with the user ID of the controlled client 10 that transmitted the message connection request information. And stored in the key value store as connection information.

  The client status management unit 42 includes a key / value store and manages client status information of the controlled client 10 and the control client 20. The client status information is information indicating whether the client is the controlled client 10 or the control client 20. Of the client status information, information indicating that the client is the control client 20 is referred to as remote client status information, and information indicating that the client is the controlled client 10 is referred to as local client status information.

  Specifically, when the client state management unit 42 receives remote client state information from the control client 20, the user ID and the session ID included in the connection information stored in the connection management unit 41 as shown in FIG. The key value store stores that the client state is “control client”. When the local client status information is received from the controlled client 10, the client status is “controlled” in association with the user ID and session ID included in the connection information stored in the connection management unit 41 as shown in FIG. It is memorized that it is a “control client”.

  In addition, when the client state management unit 42 stores the client state information and the connection information in association with each other, the client state management unit 42 notifies the control client 20 that it is possible to request establishment of a call session (callable).

  The call state management unit 43 controls the call session based on the call session establishment request information (Offer) indicating that the session establishment is requested and the session disconnection request information (Bye) indicating that the session is requested to be disconnected. Is delegated to the subsystem server 50.

  Specifically, when receiving the call session establishment request information (Offer), the call state management unit 43 transmits the call session establishment request information to the control client 20B. Similarly, when the control client 20B receives call session establishment response information (Answer) indicating that the control client 20B responds to the call session establishment request information, the call state management unit 43 transmits the call session establishment response information to the control client 20A. .

  When the call state management unit 43 receives session disconnection request information (Bye) indicating that a session disconnection is requested from the controlled client 10B, the call state management unit 43 transmits the session disconnection request information to the control client 20A, and the subsystem server Call termination information indicating that the call session is to be disconnected is transmitted to 50.

  Further, the call state management unit 43 transmits the call session establishment request information transmitted by the control client 20A to the control client 20B, or transmits the call session establishment response information transmitted by the control client 20B to the control client 20A. To do. The call state management unit 43 includes a key / value store, and updates the call state indicating that the control client 20A and the control client 20B are processing for session establishment or session establishment. Specifically, as shown in FIG. 5, the call state management unit 43 displays call state information that associates the user ID of the control client 20A and the user ID of the control client 20B included in the call session establishment request information. Store in the key value store.

  The subsystem management unit 44 delegates control related to a predetermined process requested from the control client 10 to the subsystem server 50 based on the client state information and the HTTP session information. In the present embodiment, the predetermined process is a call in a call session, and the control is establishment and disconnection of the call session. Specifically, the subsystem management unit 44 transmits session information of the controlled client 10A corresponding to the control client 20A and session information of the controlled client 10B corresponding to the control client 20B, and establishes a call session. This is notified to the subsystem server 50.

  Here, a method in which the subsystem management unit 44 extracts session information including the session ID of the controlled client 10A corresponding to the control client 20A will be described with reference to FIG. The subsystem management unit 44 extracts the user ID stored in the client state management unit 42 in association with the session ID of the control client 20A. Then, the subsystem management unit 44 extracts the session ID of the controlled client 10A stored in association with the extracted user ID. The session ID of the controlled client 10A extracted in this way is the session ID of the controlled client 10A corresponding to the control client 20A. The same applies to the session ID of the controlled client 10B corresponding to the control client 20B.

<Functional configuration of subsystem server>
The subsystem server 50 is a server that executes one or more arbitrary functions. As an example, the subsystem server 50 is a signaling server 52 that performs call control in this embodiment. As shown in FIG. 1, the subsystem server 50 includes a unique function unit 51. When the predetermined process is delegated to the subsystem server 50, the unique function unit 51 controls the predetermined process by the controlled client based on the client status information and the HTTP session information.

  As an example, the unique function unit 51 performs control for establishing or disconnecting the call session of the controlled client 10 associated with the control client 20 based on the client status information and the HTTP session information. 53 and a message transfer function unit 54. That is, as shown in FIG. 4, the signaling server 52 includes a routing table unit 53 and a message transfer function unit 54.

  The routing table unit 53 includes a key / value store, and stores network routines between the plurality of controlled clients 10. Specifically, the routing table unit 53 receives call session establishment request information from the control client 20A. When the routing table unit 53 receives the call session establishment response information from the control client 20B, the routing table unit 53 stores the session ID of the controlled client 10A stored in association with the control client 20A and the control client 20B as shown in FIG. The session ID of the controlled client 10B stored in association is stored in the key-value store.

  When the routing table unit 53 receives from the client state management server 40 call termination information indicating that the call session established between the controlled client 10A and the controlled client 10B is to be disconnected, the routing table unit 53 receives the controlled client 10A. And the session ID of the controlled client 10B are deleted from the routing table.

  The message transfer function unit 54 transmits session description request information for requesting session description information to the controlled client 10A. In addition, the message transfer function unit 54 transmits the session description information received from the controlled client 10A to the controlled client 10B, and transmits the session description information received from the controlled client 10B to the controlled client 10A.

<Functional configuration of load balancer>
The load distribution device 60 distributes the load applied to each of the authentication server 30, the client state management server 40, and the subsystem server 50. As shown in FIG. 1, the load balancer 60 includes a reverse proxy 61 and a load balancer 62.

  The reverse proxy 61 receives information transmitted to these servers as a proxy for the authentication server 30, the client state management server 40, and the subsystem server 50, and transmits the information to each server.

  When the remote desktop cooperation processing system 1 includes a plurality of authentication servers 30, for example, the load balancer 62 distributes information transmitted from the controlled client 10 and the control client 20 to the plurality of authentication servers 30. Thereby, it is possible to suppress the load per unit in the plurality of authentication servers 30. The load balancer 62 also has the same function when the remote desktop cooperation processing system 1 includes a plurality of client state management servers 40 and a plurality of subsystem servers 50.

<< Operation of Remote Desktop Cooperation Processing System >>
<Operations related to login processing>
Next, with reference to FIG. 7, the operation | movement which concerns on the login process of the remote desktop cooperation processing system 1 which concerns on this embodiment is demonstrated.

  As shown in FIG. 7, first, the controlled client 10 receives user information including a user ID and a password input by the user, and transmits the received user information to the authentication server 30 (step S11). . When the authentication server 30 receives the user information transmitted in step S11, the session management unit 33 of the authentication server 30 generates HTTP session information including the session ID, and transmits an HTTP protocol message “200 OK” (step). S12).

  Subsequently, the controlled client 10 transmits message connection request information indicating that a message connection is requested to the client state management server 40 using a protocol such as Web Socket (step S13). When the message connection request information is transmitted in step S13, the connection management unit 41 of the client state management server 40 receives the message connection request information, and sends the HTTP session information generated by the session management unit 33 to the authentication server 30. A request is made (step S14).

  When HTTP session information is requested by the connection management unit 41 in step S14, the session management unit 33 transmits HTTP session information in response to the request (step S15). Then, the connection management unit 41 of the client state management server 40 stores the HTTP session information transmitted by the session management unit 33 in association with the session information of the message connection request (step S16). Further, the connection management unit 41 transmits message connection response information such as Web Socket indicating response to the message connection request to the controlled client 10 (step S17).

  Through the above processing, the message connection between the controlled client 10 and the client state management server 40 is established. Similarly, the process from step S11 to step S17 is performed for the control client 20 as well.

<Operation related to client status report processing>
Next, with reference to FIG. 8, the operation | movement which concerns on the client status notification process of the remote desktop cooperation processing system 1 which concerns on this embodiment is demonstrated. As shown in FIG. 8, first, the control client 20 transmits remote client status information to the client status management server 40 (step S21). When the remote client status information is transmitted in step S21, the client status management unit 42 receives the remote client status information and associates the remote client status information with the user ID and session ID stored in the connection management unit 41. Is stored as shown in FIG. 3 (step S22).

  Then, the client status management unit 42 transmits status change success information indicating that the remote client status information is stored to the control client 20 (step S23). When the status change success information is transmitted, the control client 20 receives the status change success information and changes the screen to operate as a remote client (remote desktop system server) (step S24).

  Similarly, the controlled client 10 transmits local client status information to the client status management server 40 (step S25). When the local client status information is transmitted in step S25, the client status management unit 42 receives the local client status information, and associates the local client status information with the user ID and session ID stored in the connection management unit 41. Is stored (step S26).

  Then, the client status management unit 42 transmits status change success information indicating that the local client status information is stored to the control client 10 (step S27). When the status change success information is transmitted, the control client 20 receives the status change success information and changes the screen to operate as a local client (remote desktop system client) (step S28).

  When the client state management unit 42 associates and stores the client state information and the session information for the control client 20 and the controlled client 10 in steps S22 and S26, respectively, it is possible to request establishment of a call session (callable) ) Is notified to the control client 20 (step S29).

<Operation related to establishment and disconnection of call session>
Next, with reference to FIG. 9, operations related to establishment and disconnection of a call session of the remote desktop cooperation processing system 1 according to the present embodiment will be described. As shown in FIG. 9, first, the control client 20A transmits call session establishment request information (Offer) to the client state management server 40 (step S41). When the call session establishment request information transmitted in step S41 is transmitted, the call state management unit 43 of the client state management server 40 receives the call session establishment request information, and sends the call session establishment request information to the control client 20B. Transmit (step S42).

  Based on the call session establishment request information transmitted in step S42, when the user inputs that the request is accepted (step S43), the control client 20B stores the call session establishment response information (Answer) in the client state management. It transmits to the server 40 (step S44). Further, the control client 20B changes the screen (step S45).

  When the call session establishment response information is transmitted in step S44, the call state management unit 43 stores the call state information of the control client 20A and the control client 20B as shown in FIG. 5 (step S46).

  Subsequently, the subsystem management unit 44 performs processing for establishing a call session between the controlled client 10A corresponding to the control client 20A and the controlled client 10B corresponding to the control client 20B as a signaling that is the subsystem server 50. Delegate to server 52. Specifically, the subsystem management unit 44 extracts the session ID of the controlled client 10A stored in the key value store of the client state management unit 42 shown in FIG. 3 in association with the session ID of the control client 20A. To do. Similarly, the subsystem management unit 44 extracts the session ID of the controlled client 10A stored in association with the session ID of the control client 20A. Then, the subsystem management unit 44 transmits session information including the extracted session ID, and notifies the signaling server 52 of the start of a call session between the controlled client 10A and the controlled client 10B (step S47).

  Then, the routing table unit 53 of the signaling server 52 notified of the start of the call session adds a routing for the controlled client 10A and the controlled client 10A to establish a call session as shown in FIG. Step S48).

  Further, when the call session establishment response information is transmitted from the control client 20B in step S44, the call state management unit 43 receives the transmitted call session establishment response information and transmits it to the control client 20A (step S49). . When the call session establishment response information is transmitted, the control client 20A receives the call session establishment response information, and transitions to a screen used for the call session (step S50).

  In step S47, when the call state management unit 43 notifies the signaling server 52 of the start of the call session between the controlled client 10A and the controlled client 10B, the message transfer function unit 35 of the signaling server 52 The client 10A is requested for session description information (step S51). When the session description information is requested in step S51, the controlled client 10A transmits the session description information to the signaling server 52 in response to the request (step S52). Then, the message transfer function unit 35 of the signaling server 52 transmits the session description information received from the controlled client 10A to the controlled client 10B (step S53).

  Then, the controlled client 10B transmits session description response information indicating that it responds to the received session description information to the signaling server 52 (step S54), and the message transfer function unit 35 of the signaling server 52 receives the session description response. Information is transmitted to the controlled client 20A (step S55). Through the above processing, a call session (media) between the controlled client 10A and the controlled client 10B is established.

  When an instruction to end the call session is input by the user to the control client 20B, the control client 20B transmits call session disconnection request information (bye) to the client state management server 40 (step S60), and is used for the call session. The screen is changed so as to close the screen that has been closed (step S61). When the client state management server 40 receives the call session disconnection request information transmitted in step S60, the call state management unit 43 updates (deletes) the call state updated in step S46 (step 62).

  Then, the call state management unit 43 transmits the call session disconnection request information transmitted from the control client 20B in step S60 to the control client 20A (step S63). When the call session disconnection request information is transmitted in step S63, the control client 20A changes the screen so as to close the screen used for the call session (step S64).

  In step S63, when the call state management unit 43 transmits the call session disconnection request information to the control client 20A, the subsystem management unit 44 performs processing for disconnecting the call session between the controlled client 10A and the controlled client 10A. Is delegated to the subsystem server 50. Specifically, the subsystem management unit 44 notifies the signaling server 52 of disconnection of the call session between the controlled client 10A and the controlled client 10B (step S65).

  In step S65, when the call state management unit 43 notifies the signaling server 52 of the termination of the call session between the controlled client 10A and the controlled client 10B, the message transfer function unit 35 of the signaling server 52 will control the controlled client 10A. Is requested to disconnect the call session (step S66), and the controlled client 10B is requested to disconnect the call session (step S67).

  In step S65, when the signaling server 52 is notified of disconnection of the call session between the controlled client 10A and the controlled client 10B, the routing table unit 53 of the signaling server 52 causes the controlled client 10A and the controlled client 10A. Is deleted from the routing table (step S68).

  As described above, when the user of the remote desktop system 2 requests establishment of a call session from the control client 20 as the remote desktop system server, the remote desktop cooperation processing system 1 described in the present embodiment controls the user. A call session is established directly between the controlled clients 10 as remote desktop system clients without going through the client 20. Therefore, the user can avoid problems such as sound interruption and voice delay due to a call session established via a control client as a remote desktop system server. In addition, the client state management server 40 performs control for establishing a call session between the controlled clients 10 by using the association between the controlled client 20 and the controlled client 10 stored in the client state management unit 42. Therefore, the user does not need to perform complicated operations.

  That is, a system that realizes a high-quality call can be realized by linking the establishment of a call session and a call function. Even if the remote desktop system 2 uses a communication path that is not suitable for media transfer, the controlled client 10A communicates directly with the controlled client 10B, so that a high-quality call can be realized. Further, when performing real-time communication using a remote desktop system, the operation terminal (controlled client 10) communicates without going through the remote desktop, so that a high-quality call can be realized.

  In the remote desktop cooperation processing system 1 described in the present embodiment, a call session is directly established between the controlled clients 10. However, based on conditions such as functions, performance, and specifications regarding the control client 20 </ b> A, The client state management unit 42 may determine whether to establish a call session directly between the control clients 10 or to establish a call session via the control client 20. Specifically, the client state management unit 42 determines whether or not the control client 20 has a call function. When it is determined that the control clients 20 have a call function, the control clients 20 perform processing for establishing a call session. If it is determined that the control client 20 does not have a call function, the subsystem management unit 44 notifies the signaling server 52 of the session information of the controlled client 10.

  When the connection management unit 41 receives a message connection request from a user, the connection management unit 41 requests session information from the session management unit 33. Therefore, the user controls any terminal by performing authentication processing using a user ID. It can be a client or a controlled client. On the other hand, since the session management unit 33 stores information related to user authentication, when the user uses the same controlled client in subsequent operations, there is no need to perform authentication processing again.

  In addition, when the operation terminal used by the user does not have a microphone or a camera necessary for realizing the call function, the user may operate another operation terminal as a controlled client. That is, the operation terminal used by the user is not fixed, and any operation terminal equipped with hardware necessary for realizing the call function may be used as the controlled client.

  Further, in the remote desktop cooperation processing system 1 described in the present embodiment, when image information, video information, text information, and the like are transmitted and received during establishment of a call session, the controlled clients 10 directly transmit and receive each other. Instead, it can be transmitted and received via the control client 20.

  In the remote desktop cooperation processing system 1 described in the present embodiment, the control client 20B that is different from the control client 20A that transmitted the call session establishment request information transmits a call session disconnection request. A call session disconnection request may be transmitted.

  Moreover, in the remote desktop cooperation processing system 1 described in the present embodiment, sufficient call quality is realized when the control client 20A does not have a function related to a call or the call quality by the control client 20A is not sufficient. Although the call session is established using the controlled client 10A having a call function that can perform the above function, the above-described configuration may be applied to functions other than the call. That is, when the control client 20A does not have a predetermined function other than a call or its performance is not sufficient, the process related to the function is performed in the unique function unit 51 in the same manner as the method described in the above embodiment. The control client 10A may be controlled to perform the predetermined process.

  Further, in the remote desktop cooperation processing system 1 described in the present embodiment, the user information transmitted from the controlled client 10 and the control client 20 is associated with the terminal information for the session management unit 33 to uniquely identify the terminal. May be stored. In this way, if the user uses the same terminal, the authentication server 30 can identify the user without performing authentication at the subsequent login. The user can also log in to the remote desktop cooperation processing system 1 by using another terminal as the controlled client 10A through authentication. For example, when a terminal that is desired to be used as the controlled client 10A does not include a microphone or a camera, the user can use another terminal.

  Moreover, in the remote desktop cooperation processing system 1 described in the present embodiment, in the processing related to login, the controlled client 10 and the control client 10 store and store user information including a user ID in advance. A dongle that transmits user information to the authentication server 30 may be used. By doing in this way, it becomes possible to reduce the load of the operation | work which a user inputs user information or transmits. In particular, for example, when the control client 10 is installed in a company and the controlled client 20 is used at home, complicated setting information or software prohibited from being taken out from the company must be used by a dongle. The person can easily operate.

  In the remote desktop cooperation processing system 1 described in the present embodiment, the connection management unit 41, the client status management unit 42, the subsystem management unit 44, and the routing table unit 53 store each information in the key value store. To do. As a result, a highly scalable design can be realized. However, the connection management unit 41, the client state management unit 42, the subsystem management unit 44, and the routing table unit 53 may store each information in a storage unit of an arbitrary format such as a relational database.

  Although the above embodiment has been described as a representative example, it will be apparent to those skilled in the art that many changes and substitutions can be made within the spirit and scope of the invention. Therefore, the present invention should not be construed as being limited by the above-described embodiments, and various modifications and changes can be made without departing from the scope of the claims. For example, a plurality of constituent blocks described in the embodiments can be combined into one, or one constituent block can be divided.

DESCRIPTION OF SYMBOLS 1 Remote desktop cooperation processing system 10 Controlled client 20 Control client 30 Authentication server 31 User information storage part 32 Authentication function part 33 Session management part 40 Client state management server 41 Connection management part 42 Client state management part 43 Call state management part 44 Subsystem management unit 50 Subsystem server 51 Unique function unit 52 Signaling server 53 Routing table unit 54 Message transfer function unit 60 Load balancer 61 Reverse proxy 62 Load balancer

Claims (6)

A remote desktop cooperative processing system in which a plurality of remote desktop systems, each including a control client that is a remote desktop system server and a controlled client that is a remote desktop system client, cooperate with an authentication server, a client state management server, and a subsystem server. There,
The authentication server is
An authentication function unit for authenticating the controlled client and the control client;
A session management unit that generates HTTP session information representing a session to the authentication server of each of the controlled client and the control client authenticated by the authentication function unit;
The control client is
Requesting control related to a predetermined process from the client state management server, the client state management server,
A client state management unit for storing the client state information indicating whether the control client and the controlled client are a control client or a controlled client, respectively, and the HTTP session information;
A subsystem management unit that delegates the predetermined process to the subsystem server when control for executing the predetermined process is requested by the control client;
When the predetermined process is delegated, the subsystem server performs control for the controlled client associated with the control client and stored in the client state management unit to perform the predetermined process. Remote desktop cooperation processing system with functional units. In the remote desktop cooperation processing system according to claim 1,
The control related to the predetermined process is to establish or disconnect a call session;
The unique function unit establishes or disconnects a call session of the controlled client associated with the control client based on the client status information and the HTTP session information. In the remote desktop cooperation processing system according to claim 2,
The subsystem management unit transmits the HTTP session information and the client state information stored in the client state management unit to the unique function unit,
The unique function unit is
A routing table unit that stores a session ID of the controlled client based on the client status information and the HTTP session information;
A message transfer function unit that transmits and receives session description information to and from a controlled client associated with a session ID stored in the routing table unit,
Remote desktop linkage processing system. In the remote desktop cooperation processing system according to claim 2 or 3,
A first control client of the plurality of control clients transmits call session establishment request information for establishing the call session with a second control client to the client state management server,
The second control client transmits call session establishment response information to the client state management server based on the call session establishment request information,
The client state management server
When receiving the call session establishment response information, a call state management unit that stores call state information that associates a user ID related to the first control client and a user ID related to the second control client;
Remote desktop linkage processing system. In the remote desktop cooperation processing system according to claim 4,
The call state management unit deletes the call state information when call session disconnection request information is transmitted from any one of the first control client and the second control client. Remote desktop linkage processing system. A client state management server that cooperates with a plurality of remote desktop systems, each including a control client that is a remote desktop system server and a controlled client that is a remote desktop system client,
Associating client status information indicating whether the controlled client and the controlled client are each a controlled client or a controlled client, and HTTP session information related to an HTTP session to the controlled client and the authentication client of the controlled client A client state management unit for storing
When control for executing a predetermined process is requested by the control client, the control client performs sub-control for executing the predetermined process based on the client status information and the HTTP session information. A subsystem management unit that delegates to the system server;
A client state management server.

Images