An automatic connection management system and management method for VNC sessions

Abstract

The present invention discloses an automatic connection management system and management method for VNC sessions, including a client of the VNC session management system, which is responsible for providing a front-end interaction interface, communicating with the server of the VNC session management system, launching the VNC Client software, and generating corresponding configurations; the server of the VNC session management system, which is responsible for interacting with the device side, processing communications from the client of the VNC session management system, and maintaining a VNC session record table stored in the server of the VNC session management system. In the present invention, users can manage themselves in a single-user multi-VNC session environment, improving the security of the device-side server network, facilitating the establishment of VNC sessions, and achieving efficient VNC session management.

Description

Technical Field

[0001] The present invention relates to a management system and a management method, in particular to an automatic connection management system and method for VNC sessions, belonging to the field of communication technologies. Background Art

[0002] Virtual Network Computing (VNC), as a remote desktop control technology based on the RFB (Remote Frame Buffer) protocol, is widely used in fields such as server remote management and cloud computing resource access. Its core mechanism realizes cross-platform graphical interface transmission through incremental updates of the frame buffer, and it is an excellent remote control solution. VNC is divided into two parts: the Server side and the Client side. To use VNC software, it is necessary to first use VNC Server software to establish a session on a certain network port, and then use VNC Client software to connect to the network port where the session is located.

[0003] The process for establishing a VNC session without a preset port is as follows:

[0004] 1. The user manually establishes an SSH tunnel connection to the server to be logged in.

[0005] 2. The user uses VNC Server software to specify an unused VNC port and declare connection parameters to establish a VNC session.

[0006] 3. The user opens VNC Client software and uses the port of the VNC session just established and the corresponding server host IP address to establish a session configuration and connect to the session.

[0007] The process for establishing a VNC session with a preset port is as follows:

[0008] 1. The server administrator presets a VNC session and the corresponding port for each user.

[0009] 2. The user opens VNC Client software and uses the VNC port preset by the administrator to establish a session configuration and connect to the session.

[0010] The current technical system has the following technical defects:

[0011] In the process of establishing a VNC session without a preset port, the user needs to manually establish an SSH tunnel, specify a VNC port, and maintain connection parameters one by one (such as steps 3-5 of the typical implementation disclosed in CN110365718A). The steps are complex, there are many links, and the fault tolerance is poor. This problem is particularly significant in a distributed cluster environment. In addition, directly opening the SSH connection function of the server on the user side also brings security problems.

[0012] In the VNC session establishment process of the preset port, the user only needs to establish a session configuration according to the VNC port preset by the administrator. However, the administrator needs to maintain a huge user-server-VNC port correspondence table, which has poor flexibility. This problem is also significant in a distributed cluster environment.

[0013] In the prior art, Chinese Patent CN 117938828 A (Publication Date: January 18, 2024) realizes lightweight VNC connection. Compared with the traditional technology that requires software download, it avoids a lot of cumbersome configurations, but lacks the management function for a single-user multi-VNC session environment.

[0014] In the prior art, Chinese Patent CN 119011645 A (Publication Date: November 22, 2024) realizes the function of automatically allocating VNC hosts for users according to the virtual IP address used when connecting with the VNCClient software, which reduces the management burden, but cannot realize the function of a single-user multi-VNC session.

[0015] In the prior art, Chinese Patent CN 112689000 A (Publication Date: April 20, 2021) establishes a data transmission reverse tunnel (i.e., reverse proxy) through a data forwarding service, isolates the express cabinet host information from users, and improves network security, but cannot realize the function of allowing users to manage multi-VNC sessions by themselves.

[0016] In summary, the prior art mainly has the following defects:

[0017] 1. The problem that the traditional VNC session establishment steps without preset ports are complex, have many links, and poor fault tolerance;

[0018] 2. The problem that the traditional VNC session management with preset ports has high management difficulty and poor flexibility;

[0019] 3. It is difficult for ordinary users to manage multi-VNC session scenarios by themselves;

[0020] 4. The problem that the traditional VNC session establishment method cannot achieve load balancing;

[0021] 5. The problem that the traditional VNC session cannot isolate the user and the device-side network environment during use. Summary of the Invention

[0022] The technical problem to be solved by the present invention is to provide an automatic connection management system and management method for VNC sessions to realize the management of a single-user multi-VNC session scenario.

[0023] To solve the above technical problems, the technical solution adopted by the present invention is:

[0024] An automatic connection management system for VNC sessions, comprising

[0025] The VNC session management system client is responsible for providing a front-end interaction interface, communicating with the VNC session management system server, launching the VNC Client software, and generating corresponding configurations;

[0026] The VNC session management system server is responsible for interacting with the device side, processing communications from the VNC session management system client, and maintaining the VNC session record table stored in the VNC session management system server.

[0027] Furthermore, each VNC session record information in the VNC session record table includes the identification number of the VNC session, the username of the device side to which the VNC session belongs, the host IP address of the VNC session server side, the VNC session port number, and the VNC session process PID number.

[0028] A management method for an automatic connection management system of VNC sessions, comprising the following steps:

[0029] S1. First, log in to the VNC session management system client. After successful login, send a query request to the VNC session management system server through the VNC session management system client. After receiving the query request, the VNC session management system server searches for all VNC session records in the VNC session record table where the username of the device side to which the VNC session belongs matches the login username of the current user, and generates all the searched VNC session records into the VNC session record file of the current user.

[0030] S2. The VNC session management system server returns the VNC session record file of the current user to the VNC session management system client. After receiving the VNC session record file of the current user, the VNC session management system client displays all the VNC session information of the current user in the received VNC session record file of the current user to the user. The VNC session information of the current user displayed to the user includes the identification number of the VNC session, the host IP address of the VNC session server side, and the VNC session port number.

[0031] S3. The VNC session management system client initiates a session request to the VNC session management system server. The session request includes the identification number of the VNC session that the client hopes to connect to. After receiving the session request, the VNC session management system server searches the VNC session record table and finds the VNC session record information whose VNC session identification number matches the identification number of the VNC session that the client hopes to connect to. Then, based on the found VNC session record information, a proxy port is generated on the host of the VNC session management system server, and the proxy port number of this proxy port is returned to the VNC session management system client. After receiving the returned proxy port number, the VNC session management system client launches the VNC Client software. At the same time, the VNC session management system client generates a configuration file required for the VNC session that the client hopes to connect to in the VNC Client software.

[0032] Further, in step S1, after generating the VNC session record file of the current user, the VNC session management system server queries the VNC session process PID number of each VNC session record in the VNC session record file of the current user, and judges the survival status of the VNC session process in the host corresponding to each VNC session record. If the VNC session process in the host corresponding to a VNC session record has ended, then this VNC session record is deleted from the VNC session record file of the current user.

[0033] Further, in step S2, after receiving the VNC session record file of the current user, the VNC session management system client displays all the VNC session information of the current user in the received VNC session record file of the current user to the user in the form of a visual interface, and provides a connection button for each piece of VNC session information of the current user in the interface of the VNC session management system client.

[0034] Further, the VNC session management system client is provided with a button for creating a new VNC session. When the user selects the button for creating a new VNC session on the VNC session management system client and initiates a request for creating a new VNC session, the VNC session management system client first determines whether the current number of VNC sessions of the user has reached a preset upper limit value. If it has reached the limit, the user will be prompted that the upper limit of the VNC session number has been reached and the request for creating a new VNC session will be stopped. If it has not reached the limit, the request for creating a new VNC session will be sent to the VNC session management system server. After receiving the request for creating a new VNC session, the VNC session management system server first obtains the load conditions of the device-side server cluster, and then automatically selects the server with the minimum load according to the preset load balancing policy and selects an idle network port to create a new VNC session. After completing the creation of the new VNC session, the VNC session management system server adds the VNC session record information of the newly created VNC session to the VNC session record table. Then, the VNC session management system server searches in the VNC session record table for all VNC session records whose device-side user names to which the VNC sessions belong match the login user name of the current user according to the login user name of the current user, and generates all the searched VNC session records into a VNC session record file of the current user. The VNC session management system server returns the VNC session record file of the current user to the VNC session management system client. After receiving the VNC session record file of the current user, the VNC session management system client displays all the VNC session information of the current user in the received VNC session record file of the current user to the user, thus completing the process of creating a new VNC session.

[0035] Compared with the prior art, the present invention has the following advantages and effects:

[0036] 1. By reverse proxying the VNC ports of the device side to the network ports of one or more system server hosts, the VNC Client software on the client side only needs to connect to the proxy network port of the server to achieve the effect of accessing the VNC sessions of the device-side server, enabling the client network of the user to be completely isolated from the device-side server network, and significantly improving the security of the device-side server network.

[0037] 2. By providing a VNC session management system client with simple operation and clear interface, the user only needs to click the new button to complete the creation of a new VNC session. After establishing the VNC session, clicking the connect button can launch the VNC Client software to connect to the session, making it very easy to establish and connect to a VNC session.

[0038] 3. In the client of the present invention, since the user-level VNC session records are obtained from the server, users can manage themselves in a single-user multi-VNC session environment without the need to understand complex command operations. At the same time, since the server is responsible for recording all users' VNC session records, after the server visualizes these records, it becomes very easy and efficient for the system administrator to manage VNC sessions;

[0039] 4. By introducing a load balancing strategy in the server, the present VNC session management system has the ability of load balancing, which is very suitable for deployment in a large-scale server cluster environment to make full use of cluster resources;

[0040] 5. The VNC Server that runs in coordination with the system and the VNC Client can be arbitrarily replaced when they match each other, achieving the decoupling effect of the system software and the VNC software. BRIEF DESCRIPTION OF THE DRAWINGS

[0041] Figure 1 is a schematic diagram of an automatic connection management system for a VNC session of the present invention.

[0042] Figure 2 is a flowchart of the operation of the client of the VNC session management system of the present invention.

[0043] Figure 3 is a flowchart of the operation of the server of the VNC session management system of the present invention. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0044] In order to elaborate in detail the technical solutions adopted by the present invention to achieve the predetermined technical purposes, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, rather than all of the embodiments. And, without creative efforts, the technical means or technical features in the embodiments of the present invention can be replaced. The present invention will be described in detail below with reference to the drawings and in conjunction with the embodiments.

[0045] As Figure 1 shown, an automatic connection management system for a VNC session of the present invention includes

[0046] The client of the VNC session management system, which is responsible for providing a front-end interaction interface, communicating with the server of the VNC session management system, launching the VNC Client software, and generating corresponding configurations.

[0047] The server of the VNC session management system, which is responsible for interacting with the device side, processing the communication from the client of the VNC session management system, and maintaining the VNC session record table stored in the server of the VNC session management system.

[0048] Each piece of VNC session record information in the VNC session record table includes the identification number of the VNC session, the user name of the device end to which the VNC session belongs, the host IP address of the VNC session server end, the VNC session port number, and the VNC session process PID number.

[0049] A management method for an automatic connection management system of VNC sessions includes the following steps:

[0050] S1. As Figure 2 shown, first log in on the client side of the VNC session management system. After successful login, send a query request to the server side of the VNC session management system through the client side of the VNC session management system. After receiving the query request, the server side of the VNC session management system searches for all VNC session records in the VNC session record table whose device end user names belonging to the VNC sessions match the logged-in user name of the current user, and generates all the searched VNC session records into a VNC session record file of the current user.

[0051] After generating the VNC session record file of the current user, the server side of the VNC session management system queries the VNC session process PID number of each VNC session record in the VNC session record file of the current user, and judges the survival status of the VNC session process in the host corresponding to each VNC session record. If the VNC session process in the host corresponding to a VNC session record has ended, then delete that VNC session record from the VNC session record file of the current user. This action can ensure that the closed VNC sessions are deleted from the record, avoiding returning the closed VNC session records to the user.

[0052] S2. As Figure 3 shown, the server side of the VNC session management system returns the VNC session record file of the current user to the client side of the VNC session management system. After receiving the VNC session record file of the current user, the client side of the VNC session management system displays all the VNC session information of the current user in the received VNC session record file of the current user to the user. The VNC session information of the current user displayed to the user includes the identification number of the VNC session, the host IP address of the VNC session server end, and the VNC session port number.

[0053] After the VNC session management system client receives the VNC session record file of the current user, it displays all the VNC session information of the current user in the received VNC session record file of the current user to the user in the form of a visual interface, and provides a connection button for each piece of VNC session information of the current user in the interface of the VNC session management system client.

[0054] S3. The VNC session management system client sends a session request to the VNC session management system server. The session request includes the identification number of the VNC session that the user hopes to connect to. After receiving the session request, the VNC session management system server searches for the VNC session record information in the VNC session record table whose identification number of the VNC session matches the identification number of the VNC session that the user hopes to connect to, and generates a proxy port on the host of the VNC session management system server according to the found VNC session record information, and returns the proxy port number of this proxy port to the VNC session management system client. In this way, the VNC Client software on the client only needs to connect to this proxy network port on the server to achieve the effect of accessing the VNC session of the device-side server, enabling the user client network to be completely isolated from the device-side server network. After receiving the returned proxy port number, the VNC session management system client launches the VNC Client software. At the same time, the VNC session management system client generates the configuration file required for the VNC session that the user hopes to connect to (such as the IP address of the server host, the proxy port, and other necessary information for the VNC Client software) in the VNC Client software.

[0055] S4. The VNC session management system client sets a new VNC session button. The user selects the new VNC session button on the VNC session management system client and initiates a new VNC session request. The VNC session management system client first determines whether the current number of VNC sessions of the user reaches the preset upper limit value. If it reaches, it prompts the user that the VNC session number reaches the upper limit value and stops the new VNC session request. If it does not reach, it sends the new VNC session request to the VNC session management system server. After receiving the new VNC session request, the VNC session management system server first obtains the load condition of the device-side server cluster, then automatically selects the server with the smallest load according to the preset load balancing strategy and selects an idle network port to create a new VNC session. After completing the creation of the new VNC session, the VNC session management system server adds the VNC session record information of the new VNC session to the VNC session record table. Then, the VNC session management system server searches all VNC session records in the VNC session record table whose device-side user names of the VNC sessions belong to the current user's login user name and match the current user's login user name, and generates all the searched VNC session records into the current user's existing VNC session record file. The VNC session management system server returns the current user's existing VNC session record file to the VNC session management system client. After receiving the current user's existing VNC session record file, the VNC session management system client displays all the current user's existing VNC session information in the received current user's existing VNC session record file to the user, completing the new VNC session process.

[0056] In the present invention, by reverse proxying the VNC port of the device side to the network ports of one or more system server hosts, the VNC Client software on the client side only needs to connect to the proxy network port of the server side to achieve the effect of accessing the VNC session of the device side server, enabling the user client network to be completely isolated from the device side server network and significantly improving the security of the device side server network; by providing a VNC session management system client with simple operation and clear interface, the user only needs to click the new button to complete the creation of a VNC session. After the VNC session is established, clicking the connect button can launch the VNC Client software to connect to the session, making it very easy to create and connect to a VNC session; on the client side of the present invention, since there is a user-level VNC session record obtained from the server side, the user can manage it by himself in a single-user multi-VNC session environment without the need to understand complex command operations. At the same time, since the server side is responsible for recording all users' VNC session records and visualizing these records, it is also very easy and efficient for the system administrator to manage the VNC sessions; by introducing a load balancing strategy on the server side, the present VNC session management system has the ability of load balancing, which is very suitable for deployment in a large-scale server cluster environment and makes full use of cluster resources; the VNC Server and VNC Client that operate in coordination with the system can be arbitrarily replaced when they match each other, achieving the decoupling effect of the system software and the VNC software.

[0057] The above are only the preferred embodiments of the present invention and do not impose any form of limitation on the present invention. Although the present invention has been disclosed above with the preferred embodiments, it is not intended to limit the present invention. Any person skilled in the art can make some changes or modifications to the above-disclosed technical content to obtain equivalent embodiments with equivalent changes within the scope of the technical solution of the present invention. However, as long as it does not depart from the technical solution content of the present invention and is based on the technical essence of the present invention, any simple modification, equivalent replacement, and improvement made to the above embodiments still fall within the protection scope of the technical solution of the present invention.

Claims

1. A management method for an automatic connection management system of VNC sessions, characterized in that It includes the following steps: S1. First, log in to the VNC session management system client. After successful login, send a query request to the VNC session management system server through the VNC session management system client. After receiving the query request, the VNC session management system server searches for all VNC session records in the VNC session record table where the device-side username of the VNC session matches the logged-in username of the current user based on the logged-in username of the current user, and generates a VNC session record file for the current user's existing VNC sessions from all the searched VNC session records; S2. The VNC session management system server returns the VNC session record file for the current user's existing VNC sessions to the VNC session management system client. After receiving the VNC session record file for the current user's existing VNC sessions, the VNC session management system client displays all the VNC session information for the current user's existing VNC sessions in the received file to the user. The VNC session information for the current user's existing VNC sessions displayed to the user includes the identification number of the VNC session, the host IP address of the VNC session server, and the VNC session port number; S3. The VNC session management system client sends a session request to the VNC session management system server. The session request includes the identification number of the VNC session that the user hopes to connect to. After receiving the session request, the VNC session management system server finds the VNC session record information in the VNC session record table where the identification number of the VNC session matches the identification number of the VNC session that the user hopes to connect to, and generates a proxy port on the host of the VNC session management system server based on the found VNC session record information and returns the proxy port number of this proxy port to the VNC session management system client. After receiving the returned proxy port number, the VNC session management system client launches the VNC Client software, and at the same time, the VNC session management system client generates a configuration file required for the VNC session that the user hopes to connect to in the VNC Client software.

2. The management method according to claim 1, wherein: In step S1, after generating the VNC session record file for the current user's existing VNC sessions, the VNC session management system server queries the VNC session process PID number of each VNC session record in the VNC session record file for the current user's existing VNC sessions, and judges the survival status of the VNC session process in the host corresponding to each VNC session record. If the VNC session process in the host corresponding to a VNC session record has ended, then delete this VNC session record from the VNC session record file for the current user's existing VNC sessions.

3. The management method according to claim 1, characterized in that: In step S2, after receiving the VNC session record file for the current user's existing VNC sessions, the VNC session management system client displays all the VNC session information for the current user's existing VNC sessions in the received file to the user in the form of a visual interface, and provides a connection button for each piece of VNC session information for the current user's existing VNC sessions in the interface of the VNC session management system client.

4. The management method according to claim 1, characterized in that: The VNC session management system client sets a new VNC session button. When the user selects the new VNC session button on the VNC session management system client and initiates a new VNC session request, the VNC session management system client first determines whether the current number of VNC sessions of the user has reached the preset upper limit value. If it has reached, it prompts the user that the VNC session number has reached the upper limit and stops the new VNC session request. If it has not reached, it sends the new VNC session request to the VNC session management system server. After receiving the new VNC session request, the VNC session management system server first obtains the load situation of the device-side server cluster, then automatically selects the server with the least load according to the preset load balancing strategy and selects an idle network port to create a new VNC session. After completing the creation of the new VNC session, the VNC session management system server adds the VNC session record information of the new VNC session to the VNC session record table. Then, the VNC session management system server searches all VNC session records in the VNC session record table whose device-side user names belonging to the VNC session match the logged-in user name of the current user according to the logged-in user name of the current user, and generates all the searched VNC session records into the existing VNC session record file of the current user. The VNC session management system server returns the existing VNC session record file of the current user to the VNC session management system client. After receiving the existing VNC session record file of the current user, the VNC session management system client displays all the existing VNC session information in the received existing VNC session record file of the current user to the user, completing the process of creating a new VNC session.

5. An automatic connection management system for a VNC session implementing the management method according to any one of claims 1-4, characterized in that: Include The VNC session management system client is responsible for providing the front-end interaction interface, communicating with the VNC session management system server, launching the VNC Client software, and generating the corresponding configuration. The VNC session management system server is responsible for interacting with the device side, processing the communication from the VNC session management system client, and maintaining the VNC session record table stored in the VNC session management system server.

6. The automatic connection management system for a VNC session according to claim 5, characterized in that: Each piece of VNC session record information in the VNC session record table includes the identification number of the VNC session, the device-side user name to which the VNC session belongs, the host IP address of the VNC session server side, the VNC session port number, and the VNC session process PID number.

Images