Automatic connection management system and management method for VNC session

Abstract

The invention discloses an automatic connection management system and management method for a VNC session, and the system comprises a VNC session management system client which is responsible for providing a front-end interaction interface, communicating with a VNC session management system server, pulling up VNC Client software, and generating corresponding configuration; and the VNC session management system server side is responsible for interacting with the equipment side, processing communication from the VNC session management system client side and maintaining a VNC session record table stored in the VNC session management system server side. According to the invention, the user can perform self-management in a single-user multi-VNC session environment, so that the security of the server network at the equipment end is improved, the VNC session is convenient to establish, and the VNC session management is efficient.

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 a management method for a VNC session, belonging to the technical field of communications. Background Art

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

[0003] The process of establishing a VNC session without a preset port is as follows: 1. The user manually establishes an SSH tunnel connection to the server that he wants to log in to.

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

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

[0006] The process of establishing a VNC session for the default port is as follows: 1. The server administrator presets VNC sessions and corresponding ports for each user.

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

[0008] The current technical system has the following technical defects: In the process of establishing a VNC session without a preset port, users need to manually establish SSH tunnels, specify VNC ports, and maintain connection parameters one by one (such as steps 3-5 of the typical implementation method disclosed in CN110365718A). The steps are complicated, there are many links, and the fault tolerance is poor. This problem is particularly prominent in a distributed cluster environment. In addition, directly opening the SSH connection function of the server on the user side also brings security issues.

[0009] In the process of establishing a VNC session with a preset port, users only need to establish a session configuration based on the VNC port preset by the administrator, but 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.

[0010] In the prior art, Chinese patent CN 117938828 A (publication date: 2024-01-18) realizes a lightweight VNC connection. Compared with the traditional technology that requires downloading software, it avoids a lot of cumbersome configurations, but lacks the management function of a single-user multi-VNC session environment.

[0011] In the prior art, Chinese patent CN 119011645 A (publication date: 2024-11-22) realizes the function of automatically allocating a VNC host to a user according to the virtual IP address used when the VNCClient software connects, which reduces the management burden, but cannot realize the function of multiple VNC sessions for a single user.

[0012] In the prior art, Chinese patent CN 112689000 A (publication date: 2021-04-20) establishes a reverse tunnel for data transmission (i.e., a reverse proxy) through a data forwarding service, isolates the express cabinet host information from the user, and improves network security, but cannot enable users to manage multiple VNC sessions by themselves.

[0013] In summary, the prior art mainly has the following defects: 1. The traditional VNC session establishment process without a preset port is complicated, involves many steps, and has poor fault tolerance. 2. The traditional VNC session management of preset ports is difficult and inflexible; 3. It is difficult for ordinary users to manage multiple VNC sessions by themselves; 4. The traditional VNC session establishment method cannot achieve load balancing; 5. Traditional VNC sessions cannot isolate the user from the device network environment. Summary of the invention

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

[0015] In order to solve the above technical problems, the technical solution adopted by the present invention is: An automatic connection management system for VNC sessions, comprising The VNC session management system client is responsible for providing a front-end interactive interface, communicating with the VNC session management system server, launching the VNC Client software, and generating corresponding configurations; 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.

[0016] Furthermore, each piece of VNC session record information in the VNC session record table includes an identification number of the VNC session, a user name of the device to which the VNC session belongs, an IP address of a host on the VNC session server side, a port number of the VNC session, and a PID number of a VNC session process.

[0017] A method for managing an automatic connection management system for a VNC session comprises the following steps: S1. First, log in to the VNC session management system client. After successful login, initiate 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 the VNC session record table for all VNC session records whose device user name to which the VNC session belongs matches 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 as the existing VNC session record files of the current user. S2, the VNC session management system server returns the existing VNC session record file of the current user to the VNC session management system client, and 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 of the current user in the received existing VNC session record file to the user, and the existing VNC session information of the current user displayed to the user includes the identification number of the VNC session, the IP address of the VNC session server host, and the port number of the VNC session; S3. The VNC session management system client initiates a session request to the VNC session management system server, where the session request includes an identification number of the VNC session to be connected. After receiving the session request, the VNC session management system server searches the VNC session record table for VNC session record information whose identification number of the VNC session matches the identification number of the VNC session to be connected, 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 the 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 to be connected in the VNC Client software.

[0018] Furthermore, in the step S1, after generating the existing 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 existing VNC session record file of the current user, and determines 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, the VNC session record is deleted from the existing VNC session record file of the current user.

[0019] Furthermore, in step S2, 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 of the current user in the received existing 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 existing VNC session information of the current user in the interface of the VNC session management system client.

[0020] Furthermore, the VNC session management system client sets a new VNC session button. The user selects the new VNC session button in the VNC session management system client and initiates a new VNC session request. The VNC session management system client first determines whether the user's current VNC session number has reached a preset upper limit. If so, the user is prompted to reach the upper limit of the VNC session number and stop requesting a new VNC session. If not, the new VNC session request is sent to the VNC session management system server. After receiving the new VNC session request, the VNC session management system server first obtains the load status of the device-side server cluster, and then automatically selects the server with the smallest load and selects an idle network port to create a new VNC session according to a preset load balancing strategy. After completing the new VNC session, the VNC session management The system server adds VNC session record information of the newly created VNC session in the VNC session record table, and then the VNC session management system server searches for VNC session records whose device-side user names belonging to all VNC sessions match the current user's login user name in the VNC session record table according to the current user's login user name, and generates all searched VNC session records as the current user's existing VNC session record files, and the VNC session management system server returns the current user's existing VNC session record files to the VNC session management system client, and after receiving the current user's existing VNC session record files, 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 files to the user, completing the new VNC session process.

[0021] Compared with the prior art, the present invention has the following advantages and effects: 1. The present invention reversely proxies the VNC port of the device to the network port of one or more system server hosts. The VNC Client software of the client only needs to connect to the proxy network port of the server to achieve the effect of accessing the VNC session of the device server, so that the user client network can be completely isolated from the device server network, which significantly improves the security of the device server network; 2. The present invention provides a VNC session management system client with simple operation and clear interface. The user only needs to click a new button to complete the creation of a VNC session. After the VNC session is established, the user can click a connect button to start the VNCClient software connection session, which makes it very easy to establish and connect a VNC session. 3. The present invention, on the client side, has user-level VNC session records obtained from the server side, so that users can manage themselves in a single-user multi-VNC session environment without having to understand complex command operations. At the same time, since the server side is responsible for recording the VNC session records of all users, after the server side visualizes these records, it becomes very easy and efficient for the system administrator to manage the VNC session; 4. The present invention introduces a load balancing strategy on the server side, so that the VNC session management system has the ability of load balancing, which is very suitable for deployment in a large-scale server cluster environment and fully utilizes cluster resources; 5. The VNC Server and VNC Client that run in coordination with the system can be replaced at will if they match each other, thus achieving the effect of decoupling the system software from the VNC software. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0023] Figure 2 It is a workflow diagram of the VNC session management system client of the present invention.

[0024] Figure 3 It is a workflow diagram of the VNC session management system server of the present invention. DETAILED DESCRIPTION

[0025] In order to elaborate on the technical scheme adopted by the present invention to achieve the predetermined technical purpose, the technical scheme in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only partial embodiments of the present invention, rather than all embodiments, and the technical means or technical features in the embodiments of the present invention can be replaced without paying creative work. The present invention will be described in detail below with reference to the drawings and in conjunction with the embodiments.

[0026] like Figure 1 As shown, an automatic connection management system for VNC sessions of the present invention comprises The VNC session management system client is responsible for providing a front-end interactive interface, communicating with the VNC session management system server, launching the VNC Client software, and generating corresponding configurations.

[0027] 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.

[0028] Each VNC session record information in the VNC session record table includes the identification number of the VNC session, the device end user name 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.

[0029] A method for managing an automatic connection management system for a VNC session comprises the following steps: S1, such as Figure 2 As shown, first log in to the VNC session management system client. After the login is successful, a query request is initiated to the VNC session management system server through the VNC session management system client. After the VNC session management system server receives the query request, the VNC session management system server searches the VNC session record table for all VNC session records whose device user name to which the VNC session belongs matches 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 as the existing VNC session record files of the current user.

[0030] After generating the existing 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 existing VNC session record file of the current user, determines the survival status of the VNC session process in the host corresponding to each VNC session record, and if the VNC session process in the host corresponding to a VNC session record has ended, deletes the VNC session record from the existing VNC session record file of the current user. This action can ensure that the closed VNC session is deleted from the record, avoiding returning the closed VNC session record to the user.

[0031] S2, such as Figure 3As shown, 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. The current user's existing VNC session information displayed to the user includes the VNC session identification number, the VNC session server host IP address, and the VNC session port number.

[0032] 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 of the current user in the received existing VNC session record file to the user in the form of a visual interface, and provides a connection button for each existing VNC session information of the current user in the interface of the VNC session management system client.

[0033] 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 to be connected. After receiving the session request, the VNC session management system server finds the VNC session record information whose identification number matches the identification number of the VNC session to be connected in the VNC session record table, 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 the proxy port to the VNC session management system client. In this way, the client's VNC Client software only needs to connect to the proxy network port of the server to achieve the effect of accessing the VNC session of the device-side server, so that the user client network can 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, and at the same time, the VNC session management system client generates the configuration file required for the VNC session to be connected in the VNC Client software (such as the server-side host IP address, proxy port, and other information necessary for the VNC Client software).

[0034] S4. The VNC session management system client sets a new VNC session button. The user selects the new VNC session button in the VNC session management system client and initiates a new VNC session request. The VNC session management system client first determines whether the number of the user's current VNC sessions has reached a preset upper limit. If so, the user is prompted to reach the upper limit and stop requesting a new VNC session. If not, the new VNC session request is sent to the VNC session management system server. After receiving the new VNC session request, the VNC session management system server first obtains the load status of the device-side server cluster, and then automatically selects the server with the smallest load and selects an idle network port to create a new VNC session according to a preset load balancing strategy. After completing the new VNC session, the VNC session management system The system server adds the VNC session record information of the newly created VNC session in the VNC session record table, and then the VNC session management system server searches for VNC session records whose device-side user names belonging to all VNC sessions match the login user name of the current user in the VNC session record table according to the login user name of the current user, and generates all the searched VNC session records as the existing VNC session record files of the current user, and the VNC session management system server returns the existing VNC session record files of the current user to the VNC session management system client, and after receiving the existing VNC session record files of the current user, the VNC session management system client displays all the existing VNC session information of the current user in the received existing VNC session record files of the current user to the user, thereby completing the process of creating a new VNC session.

[0035] The present invention reversely proxies the VNC port of the device end to the network port of one or more system server hosts, and the VNC Client software of the client only needs to connect to the proxy network port of the server end to achieve the effect of accessing the VNC session of the device end server, so that the user client network can be completely isolated from the device end server network, and the security of the device end server network is significantly improved; the present invention provides a VNC session management system client with simple operation and clear interface, and the user only needs to click a new button to complete the creation of a VNC session. After the VNC session is established, the VNC Client software connection session can be pulled up by clicking a connection button, which makes it very easy to establish and connect a VNC session; at the client end of the present invention, because there are user-level VNC session records obtained from the server end, the user can manage by himself in a single-user multi-VNC session environment without having to understand complex command operations. At the same time, since the server is responsible for recording the VNC session records of all users, after the server visualizes these records, it becomes very easy and efficient for the system administrator to manage the VNC session; the present invention introduces a load balancing strategy on the server side, so that the VNC session management system has the ability of load balancing, which is very suitable for deployment in a large-scale server cluster environment and fully utilizes cluster resources; the VNC Server and VNC Client that work in coordination with the system can be replaced arbitrarily under the condition of matching each other, achieving the effect of decoupling the system software and the VNC software.

[0036] The above is only a preferred embodiment of the present invention and does not limit the present invention in any form. Although the present invention has been disclosed as a preferred embodiment as above, it is not used to limit the present invention. Any technician familiar with this profession can make some changes or modify the technical contents disclosed above into equivalent embodiments without departing from the scope of the technical solution of the present invention. However, any simple modification, equivalent replacement and improvement made to the above embodiments without departing from the content of the technical solution of the present invention, based on the technical essence of the present invention, within the spirit and principles of the present invention, still fall within the protection scope of the technical solution of the present invention.

Claims

1. An automatic connection management system for VNC sessions, characterized in that: Include The VNC session management system client is responsible for providing a front-end interactive interface, communicating with the VNC session management system server, launching the VNC Client software, and generating corresponding configurations; 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.

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

3. A method for managing an automatic connection management system for a VNC session according to any one of claims 1 to 2, characterized in that The following steps are involved: S1. First, log in to the VNC session management system client. After successful login, initiate 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 the VNC session record table for all VNC session records whose device user name to which the VNC session belongs matches 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 as the existing VNC session record files of the current user. S2, the VNC session management system server returns the existing VNC session record file of the current user to the VNC session management system client, and 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 of the current user in the received existing VNC session record file to the user, and the existing VNC session information of the current user displayed to the user includes the identification number of the VNC session, the IP address of the VNC session server host, and the port number of the VNC session; S3. The VNC session management system client initiates a session request to the VNC session management system server, where the session request includes an identification number of the VNC session to be connected. After receiving the session request, the VNC session management system server searches the VNC session record table for VNC session record information whose identification number of the VNC session matches the identification number of the VNC session to be connected, 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 the 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 to be connected in the VNC Client software.

4. The management method according to claim 3, characterized in that: In the step S1, after the existing VNC session record file of the current user is generated, the VNC session management system server queries the VNC session process PID number of each VNC session record in the existing VNC session record file of the current user, determines the survival status of the VNC session process in the host corresponding to each VNC session record, and if the VNC session process in the host corresponding to a VNC session record has ended, deletes the VNC session record from the existing VNC session record file of the current user.

5. The management method according to claim 3, characterized in that: In step S2, 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 of the current user in the received existing 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 existing VNC session information of the current user in the interface of the VNC session management system client.

6. The management method according to claim 3, characterized in that: The VNC session management system client sets a new VNC session button. The user selects the new VNC session button in the VNC session management system client and initiates a new VNC session request. The VNC session management system client first determines whether the user's current VNC session number has reached the preset upper limit. If so, it prompts the user that the upper limit of the VNC session number has been reached and stops the new VNC session request. If not, 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 status of the device-side server cluster, and 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 new VNC session, the VNC session management system The server adds VNC session record information of the newly created VNC session in the VNC session record table, and then the VNC session management system server searches the VNC session record table for all VNC session records whose device-side user names to which the VNC sessions belong match the current user's login user name according to the current user's login user name, and generates all searched VNC session records as existing VNC session record files for the current user. The VNC session management system server returns the existing VNC session record file for the current user to the VNC session management system client. After receiving the existing VNC session record file for the current user, the VNC session management system client displays all the existing VNC session information of the current user in the received existing VNC session record file for the current user to the user, thereby completing the process of creating a new VNC session.

Images