WO2020077832A1

WO2020077832A1 - Cloud desktop access method, apparatus and device, and storage medium

Info

Publication number: WO2020077832A1
Application number: PCT/CN2018/123188
Authority: WO
Inventors: 穆骏
Original assignee: 平安科技（深圳）有限公司
Priority date: 2018-10-16
Filing date: 2018-12-24
Publication date: 2020-04-23
Also published as: CN109639749B; CN109639749A

Abstract

The present application relates to the technical field of cloud desktop accesses. Disclosed are a cloud desktop access method, apparatus and device, and a storage medium. The method comprises: receiving an access request of a cloud desktop triggered by a user by means of a web page browser, and extracting a page identification of the web page browser from the access request; searching for, according to the page identification, a TCP long connection required for the communication between the web page browser and the cloud desktop from a pre-constructed TCP connection pool; and sending the access request to a cloud computing platform by using the TCP long connection, and receiving response information made by the cloud computing platform to access the cloud desktop provided by the cloud computing platform.

Description

Cloud desktop access method, device, equipment and storage medium The

This application requires the priority of the Chinese patent application filed on October 16, 2018 in the Chinese Patent Office with the application number 201811201590.9 and the invention titled "Cloud Desktop Access Method, Device, Equipment, and Storage Media", the entire contents of which are cited Incorporated in the application.

Technical field

The present application relates to the field of cloud desktop access technology, and in particular, to a cloud desktop access method, device, equipment, and storage medium.

Background technique

CloudStack is an open source cloud computing platform with high availability and scalability, as well as an open source cloud computing solution. In addition, the platform also has a built-in user interface and programming interface to manage computing resources such as computing, networking, and storage. Therefore, using CloudStack as a foundation, data center operators can quickly and easily create cloud services through existing infrastructure.

Although, using CloudStack can accelerate the deployment, management and configuration of highly scalable public and private cloud environments. However, at present, access to the cloud desktop provided by CloudStack usually requires a separate application for accessing the cloud desktop to be installed on the user's machine, that is, in the implementation process, a proxy server to support the work of the application needs to be set, and the proxy server Assist the user machine to interact with the cloud desktop provided by CloudStack, which will undoubtedly increase the implementation cost. Moreover, due to the problem of the cloud desktop design mechanism, when the user machine accesses the cloud desktop, it is necessary to repeatedly execute the creation of a transmission control protocol (Transmission) between the user machine and CloudStack. Control Protocol (TCP) connection operation, and then the Hyper Text Transfer Protocol (Hyper Text Transfer Protocol) Protocol, HTTP) is transmitted from the user machine to CloudStack, which causes the HTTP request to occupy too much user machine resources, which in turn causes the user machine's operation interface to flash, freeze, etc.

Therefore, there is an urgent need to provide a cloud desktop access method that can reduce cloud desktop access costs and save user machine resources.

Summary of the invention

The main purpose of this application is to provide a cloud desktop access method, device, equipment and storage medium, aiming to solve the high access cost of cloud desktop in the prior art, and user machine resources are prone to appear during the process of accessing the cloud desktop Take up too many questions.

In order to achieve the above purpose, the present application provides a cloud desktop access method. The method includes the following steps:

Receiving a cloud desktop access request triggered by a user through a web browser, and extracting the page identifier of the web browser from the access request;

Searching for a long TCP connection required for communication between the web browser and the cloud desktop from a pre-built TCP connection pool according to the page identifier;

Using the long TCP connection, the access request is sent to the cloud computing platform, and the response information made by the cloud computing platform is received to achieve access to the cloud desktop provided by the cloud computing platform.

In addition, in order to achieve the above object, the present application also provides a cloud desktop access device, the device including:

A page identifier acquisition module, configured to receive a cloud desktop access request triggered by a user through a web browser, and extract the page identifier of the web browser from the access request;

A TCP long connection search module, configured to search for a TCP long connection required for communication between the web browser and the cloud desktop from a pre-built TCP connection pool according to the page identifier;

The cloud desktop access module is used to send the access request to the cloud computing platform using the long TCP connection, and receive the response information made by the cloud computing platform to implement access to the cloud desktop provided by the cloud computing platform .

In addition, in order to achieve the above object, the present application also proposes a cloud desktop access device, the device includes: a memory, a processor, and a cloud desktop accessible on the memory and capable of running on the processor. Read instructions, the cloud desktop access readable instructions are configured to implement the steps of the cloud desktop access method described above.

In addition, in order to achieve the above object, the present application also proposes a storage medium on which the cloud desktop access readable instructions are stored, and the cloud desktop access readable instructions are implemented by the processor as described above Steps of the cloud desktop access method.

The cloud desktop access method, device, device, and storage medium of this embodiment access the cloud desktop provided by the cloud platform by using web browsing, so that there is no need to separately install a cloud desktop access application on the user's machine, and therefore also in the implementation process There is no need to additionally set up a proxy server to support the work of accessing the cloud desktop application, thereby effectively reducing the access cost of the cloud desktop.

In addition, in the process of using a web browser to access the cloud desktop, the TCP length required for the web browser initiating the cloud desktop access request to communicate with the cloud desktop is found from the pre-built TCP connection pool according to the web browser's page identifier Connection, directly use the existing TCP long connection to exchange with the cloud desktop, to achieve access to the cloud desktop, in the process of accessing the cloud desktop, there is no need to repeatedly perform the operation of creating a TCP connection, just use it for reuse, so that Effectively reduce the occupation of user machine resources and solve the problem of flickering and jamming of user machine operation interface.

BRIEF DESCRIPTION

FIG. 1 is a schematic structural diagram of a cloud desktop access device of a hardware operating environment according to an embodiment of the present application;

2 is a schematic flowchart of a first embodiment of a cloud desktop access method according to this application;

3 is a schematic flowchart of a second embodiment of a cloud desktop access method according to this application;

4 is a structural block diagram of a first embodiment of a cloud desktop access device of the present application.

The implementation, functional characteristics and advantages of the present application will be further described in conjunction with the embodiments and with reference to the drawings.

detailed description

It should be understood that the specific embodiments described herein are only used to explain the present application, and are not used to limit the present application.

Referring to FIG. 1, FIG. 1 is a schematic structural diagram of a cloud desktop access device of a hardware operating environment according to an embodiment of the present application.

As shown in FIG. 1, the cloud desktop access device may include: a processor 1001, such as a central processor (Central Processing Unit, CPU), communication bus 1002, user interface 1003, network interface 1004, memory 1005. Among them, the communication bus 1002 is used to implement connection communication between these components. The user interface 1003 may include a display screen (Display), an input unit such as a keyboard (Keyboard), and the optional user interface 1003 may also include a standard wired interface and a wireless interface. The network interface 1004 may optionally include a standard wired interface and a wireless interface (such as a wireless fidelity (WIreless-FIdelity, WI-FI) interface). The memory 1005 may be a high-speed random access memory (Random Access Memory (RAM) memory can also be a stable non-volatile memory (Non-Volatile Memory, NVM), such as disk storage. The memory 1005 may optionally be a storage device independent of the foregoing processor 1001.

Those skilled in the art may understand that the structure shown in FIG. 1 does not constitute a limitation on the cloud desktop access device, and may include more or less components than shown, or combine certain components, or arrange different components .

As shown in FIG. 1, the memory 1005 as a storage medium may include an operating system, a network communication module, a user interface module, and a cloud desktop access program (that is, cloud desktop access readable instructions).

In the cloud desktop access device shown in FIG. 1, the network interface 1004 is mainly used for data communication with the cloud computing platform; the user interface 1003 is mainly used for data interaction with the user; the processor in the cloud desktop access device of this application 1001. The storage 1005 may be provided in a cloud desktop access device. The cloud desktop access device calls the cloud desktop access readable instructions stored in the memory 1005 through the processor 1001, and executes the cloud desktop provided by the embodiment of the present application. Access method.

An embodiment of the present application provides a cloud desktop access method. Referring to FIG. 2, FIG. 2 is a schematic flowchart of a first embodiment of a cloud desktop access method of the present application.

In this embodiment, the cloud desktop access method includes the following steps:

Step S10: Receive a cloud desktop access request triggered by a user through a web browser, and extract a page identifier of the web browser from the access request.

Specifically, the execution subject in this embodiment is the user machine used by the user.

It should be understood that, in practical applications, the user machine may be any terminal device capable of accessing the network, such as a personal computer, a smart phone, a tablet computer, etc., which are not listed here one by one, and there is no limitation on this.

In addition, the aforementioned web browser, namely Web browser, referred to as Web browser, is a Hyper Text Markup language (Hyper Text Markup Language, HTML) developed to display the HTML file content of the web server or file system, and allow users to interact with these files, a software that usually comes on the user's machine, so in this case by using a web browser to trigger An access request to access the cloud desktop, that is, a remote desktop access protocol based on noVNC, which realizes the interactive operation between the user machine and the cloud desktop provided by the cloud computing platform (CloudStack).

It should be noted that the noVNC mentioned above is a remote desktop access protocol opposite to VNC. Among them, the use of the VNC remote desktop access protocol must install the corresponding application program on the user, that is, the method used by the existing user machine to access the cloud desktop; and noVNC does not need to install a separate application on the user machine to access the cloud desktop Program, so there is no need to additionally set a proxy server to support the work of accessing the cloud desktop application during the implementation process, which not only facilitates the convenience of creating cloud services based on CloudStack, but also effectively reduces the implementation cost.

In addition, the above-mentioned access request may be in any format, and in actual application, those skilled in the art may predefine it. Hypertext Transfer Protocol (HyperText Transfer Protocol, HTTP).

Correspondingly, the content carried in the access request may specifically be various information carried in the HTTP request, such as the request header and the request body.

In addition, it is worth mentioning that the purpose of extracting the page identifier of the web browser from the access request is to enable CloudStack to recognize the operating system, version, and CPU of the user machine The types, the version of the web browser, the rendering engine of the web browser, the language of the web browser, the plug-ins of the web browser, etc., are not listed here one by one, and there is no restriction on this.

In step S20, according to the page identifier, a long TCP connection required for communication between the web browser and the cloud desktop is searched from a pre-built TCP connection pool.

Specifically, the TCP mentioned here is Transmission Control Protocol (Transmission Control Protocol) Protocol, TCP), under normal circumstances, the connection based on TCP protocol, there are roughly TCP connection, TCP short connection and TCP long connection.

Among them, the TCP connection needs to complete three handshakes during the establishment process, and the release process needs to complete the four handshake. Therefore, the establishment of each TCP connection requires resource consumption and time consumption.

During the establishment of the TCP short connection, only one handshake is required to complete the read and write operation, but after the completion of a read and write operation, a close operation must be performed to disconnect the TCP short link, that is, using TCP For short link communication, the operations of creating and closing need to be repeated, which will occupy too much user machine resources, resulting in problems such as stuck or flickering on the user machine's operation interface.

After the TCP long connection is established, even if the communication parties (user machine and cloud desktop) complete a read and write operation, the TCP long connection will not be automatically closed, so subsequent read and write operations can continue to take the TCP long connection In this way, there is no need to repeatedly perform the creation operation during the entire process of the user machine accessing the cloud desktop, so it can effectively reduce the occupation of the user machine resources.

From the above description, it is not difficult to find that because long TCP connections are not automatically closed after being created and can be reused directly, in order to ensure that cloud desktop access operations can proceed smoothly, a TCP connection pool for storing these long TCP connections can be constructed in advance , So that after receiving the access request triggered by the user through the web browser, directly find the TCP long connection required for the communication between the web browser and the cloud desktop from the TCP connection pool according to the web page identifier extracted from the access request That's it.

Regarding the operation of searching the TCP long connection required for communication between the web browser and the cloud desktop from the TCP connection pool, the specific operation can be implemented as follows:

(1) Using the page identification as an index item, look up the identification number of the TCP long connection corresponding to the page identification from a pre-recorded TCP long connection record table.

It should be understood that in practical applications, in order to facilitate retrieval, when creating a TCP long-connection record table, a key-value pair will be used, and the unique page identifier will be stored in the record table as the key information required for retrieval. key area, and then store the identification number of the TCP long connection corresponding to each page ID into the value area corresponding to the key where each page ID is stored. Therefore, when searching for the TCP long connection required for communication between the web browser and the cloud desktop, first use the page identifier to search for the TCP long connection corresponding to the page identifier from a pre-recorded TCP long connection record table Identify and then carry out subsequent search operations, which is not only convenient to search, but also easy to expand and manage.

(2) If the identification number of the TCP long connection corresponding to the page identifier is found, the TCP long connection corresponding to the identification number is found from the pre-built TCP connection pool according to the identification number, and the found The long TCP connection serves as a long TCP connection required for communication between the web browser and the cloud desktop.

It should be understood that each TCP long connection will have its own identification number, so according to the found identification number, the TCP long corresponding to the identification number can be quickly and accurately found from the pre-built TCP connection pool connection.

In addition, it is worth mentioning that in practical applications, in order to save the user machine resources, the number of long TCP connections added in the pre-built TCP connection pool is limited, so there may be found TCP long connection is currently in use. Therefore, before using the found TCP long connection as the TCP long connection required for the web browser to communicate with the cloud desktop, you can also first determine whether the found TCP long connection is idle. If it is in idle state, it is directly used for multiplexing; otherwise, a long TCP connection is recreated.

(3) If the identification number of the TCP long connection corresponding to the page identifier is not found, a TCP long connection is created as the TCP long connection required for the web browser to communicate with the cloud desktop, and the created TCP The identification number of the long connection is updated to the TCP long connection record table.

Specifically, the operation of creating a long TCP connection is roughly as follows:

First, send a handshake request to access the cloud desktop to the cloud computing platform to negotiate the parameters required to establish a long TCP connection.

It should be noted that the parameters required for the TCP long connection mentioned above are specifically parameters common to both parties.

Then, receiving the first parameter information of the handshake response and feedback made by the cloud computing platform.

Specifically, after receiving the handshake request sent by the user machine, the cloud computing platform makes a handshake response so that the user machine determines that the cloud computing platform has successfully received the handshake request.

In addition, the first parameter information fed back is specifically the parameter types and specific formats that the cloud computing platform can support, such as the digital types (integer, floating point, currency) that support various system versions (32-bit or 64-bit) Etc.), date type (format: XX year-XX month-XX day), string type, no longer list one by one here, nor limit this.

Next, obtain the second parameter information of the machine.

It should be understood that the second parameter information mentioned here is the type of parameters that the user machine can support, the specific format, etc. It can also be a digital type (integer, float) that supports various system versions (32-bit or 64-bit) Point type, currency type, etc.), date type (format: XX year-XX month-XX day), string type, no longer list them one by one, and do not limit them.

Next, perform intersection processing on the first parameter information and the second parameter information to obtain a candidate parameter set.

Specifically, since the process of accessing the cloud desktop is an interaction process between the user machine and the cloud computing platform, the selected parameters need to be supported by both, such as a string type parameter that takes up 10 bytes of storage space. Therefore, by performing intersection processing on the first parameter information and the second parameter information here, the parameters in the candidate parameter set obtained are parameters supported by both parties.

Next, any one of the parameters from the candidate parameter set is selected as a parameter required for establishing a long TCP connection to complete the handshake operation.

Since the parameters supported by both sides are obtained when the parameters in the alternative parameter set are obtained, any one parameter from the alternative parameter set can be used as the parameter required for establishing a long TCP connection to complete the handshake operation.

Finally, send the first hypertext transfer protocol (Hyper Text Transfer Protocol) bound to the machine by TCP long connection to the cloud computing platform Protocol (HTTP) server address and the first Internet protocol (Internet Protocol, IP, also known as: Internet Protocol) port, and receives the second Hyper Text Transfer Protocol (Hyper Text Transfer) bound by the cloud desktop delivered by the cloud computing platform Protocol (HTTP) server address and the second Internet Protocol (Internet Protocol, IP, also known as: Internet Protocol) port to complete the establishment of long TCP connections.

Specifically, when the user machine completes the handshake operation with the cloud computing platform and starts to access the cloud desktop, it initiates an HTTP request to the cloud computing platform through the pre-bound HTTP server address or IP port, and the cloud computing platform responds to the HTTP request The user machine returns the HTML file of the cloud desktop, and then the user machine executes the JS (that is, javascrip, a scripting language belonging to the network) script in the HTML file to complete the creation of the TCP long connection.

In addition, it should be understood that the TCP long connection existing in the above TCP connection pool may be specifically created when the user machine first receives the access request, and when the TCP long connection is idle, the The TCP long connection periodically sends heartbeat packets to ensure that the TCP long connection can always be in a connected state during use.

Step S30: Use the TCP long connection to send the access request to the cloud computing platform, and receive the response information made by the cloud computing platform to implement access to the cloud desktop provided by the cloud computing platform.

Specifically, the implementation of the access operation to the cloud desktop provided by the cloud computing platform is roughly as follows:

After using the TCP long connection to send the access request to the cloud computing platform and receive the response information made by the cloud computing platform, the communication channel between the web browser and the cloud desktop is connected and connected Next, the cloud computing platform will push the cloud desktop related data to the user machine through the TCP long connection. After receiving the pushed data, the user machine can render the cloud desktop by triggering a callback mechanism to perform the rendering operation on the data In the web browser, the user can operate the cloud service virtual device (hereinafter referred to as a virtual machine) built on CloudStack through the cloud desktop presented in the web browser.

The operations used to perform operations on the virtual machine through the cloud desktop presented in the web browser are roughly as follows:

For example, after detecting the user's operation in the web browser, the user machine encapsulates the data generated during the operation of the cloud desktop into the agreed data format according to the pre-agreed data format, and then communicates through the TCP long connection The channel is sent to the cloud computing platform. The cloud computing platform interprets the data sent by the user machine according to the agreed data packet protocol, and then executes the data packet to control the virtual machine.

It should be noted that the above is only a rough access process to the cloud desktop, and does not constitute a limitation on the technical solution of the present application. In a specific implementation, a person skilled in the art can agree on the data format as needed, and will not do it here limit.

It is not difficult to find from the above description that the cloud desktop access method provided by this embodiment uses web browsing to access the cloud desktop provided by the cloud platform, so that there is no need to separately install an application to access the cloud desktop on the user machine. There is no need to additionally set up a proxy server that supports the work of accessing the cloud desktop application, thereby effectively reducing the access cost of the cloud desktop.

Referring to FIG. 3, FIG. 3 is a schematic flowchart of a second embodiment of a cloud desktop access method according to this application.

Based on the foregoing first embodiment, before the step S30, the cloud desktop access method of this embodiment further includes:

Step S00: Determine whether the access request meets the preset requirements.

For example, whether the access request meets the preset requirement is determined according to the preset access request rule.

It should be noted that the above-mentioned access request rules may specifically include the standard format of the access request, the fields required to be carried, and the adopted protocol, which are not listed here one by one, nor are they limited.

Correspondingly, after passing the above judgment operation, if it is determined that the access request meets the preset requirements, step S30 is entered to perform the operation of sending the access request to the cloud computing platform using the TCP long connection, so as to ensure that After receiving the access request, the cloud computing platform can make a correct response to ensure that the cloud desktop access can proceed smoothly.

In addition, it should be understood that in actual applications, users who initiate access to the cloud desktop using a web browser in the user's machine are often unfamiliar with related technologies, so in order to be able to notify relevant management personnel in time when an exception occurs, so that the management personnel can resolve The problem that leads to the access request not meeting the preset requirements and ensuring the user's experience, after step S00, may also include:

Step S40: Obtain the abnormal log file corresponding to the access request, and send the access request and the abnormal log file to the terminal device of the administrator.

It should be understood that the management personnel mentioned in this embodiment may specifically be workers who create cloud services based on CloudStack.

Correspondingly, the terminal device of the management personnel may specifically be a development device used by the management personnel, such as a personal computer, a server, etc., which will not be listed here one by one, and there is no limitation on this.

Further, before sending the acquired exception log file and the access request that does not currently meet the preset requirements to the terminal device of the management personnel, the exception log file and the pre-stored Compare the normal log files and mark the inconsistent content to obtain the marked version of the abnormal log file; then send the access request and the marked version of the abnormal log file to the terminal device of the administrator, so that the The management personnel can locate the reason that the access request does not meet the preset requirements based on the access request and the abnormal log file of the marked version.

In addition, in practical applications, when the access request and the marked version of the abnormal log file are sent to the terminal device of the manager, the local parameters of the user machine can also be sent to the terminal device of the manager together, so that The management personnel use the same user machine and the same version of the web browser to trigger the access request to access the cloud desktop, reproduce the problem encountered by the user, and thus can better solve the problem.

Taking the user phone as the user's mobile phone as an example, the local parameters of the user machine are various parameter information recorded under the "About this machine" function option in the setting interface of the phone, such as the network connected to the mobile phone, the total capacity, Available capacity, version, operator, model, serial number, wireless LAN address, etc., are not listed here, nor are there any restrictions.

It should be understood that, after determining that the access request does not meet the preset requirements, the operation may be performed automatically by the user machine, or after determining that the access request does not meet the preset requirements, first An abnormal prompt pops up on the operation interface of the user machine, reminds the user that the current access request is illegal, and reminds the user to re-initiate the access request, while allowing the user machine to perform the operation in step S40.

It should be noted that the above is only an example, and does not constitute a limitation on the technical solution of the present application. In a specific implementation, a person skilled in the art may set it as needed, and there is no limitation here.

Further, in order to improve the efficiency of the administrator to solve the problem, after sending the above exception information (access request, exception log file, local parameter information, etc.) to the terminal device of the administrator, the method may further include the following operations: The first system time of the machine, reporting the first system time to the assessment system for evaluating the manager; receiving the abnormal release notification sent by the manager's terminal device, and triggering a test access request through the web browser Operation to obtain a test access request; determine the test access request according to a preset judgment rule, and determine that the test access request meets the preset requirements; obtain the second system time of the machine, and set the second system time The time is reported to the assessment system for assessing the management personnel, so that the assessment system determines the time taken by the management personnel to resolve the abnormality according to the first system time and the second system time, and will resolve the abnormality The time used serves as a reference factor for the performance evaluation of the managers.

From the above description, it is not difficult to find that the above operations can effectively improve the problem-solving efficiency of managers.

In addition, it is worth mentioning that, in order to facilitate the management personnel to solve the problems that may exist in the created cloud service, the update of each function module in the cloud service has been iterated. In the specific implementation, the cloud service created based on CloudStack can be component-developed according to the function and independently deployed, which can facilitate the later modification of any function, and after the modification, there is no need to update the entire service, greatly reducing the cloud The degree of coupling of the various functional modules in the service improves convenience for subsequent horizontal expansion.

It should be understood that the above is only an example, and does not constitute a limitation on the technical solution of the present application. In a specific implementation, those skilled in the art may set it as needed, without limitation here.

It is not difficult to find from the above description that the cloud desktop access method provided in this example, before using the found TCP long connection to send the access request to the cloud computing platform, by judging the access request, before determining that the Only when the requirements are set, will the access request be sent to the cloud computing platform, so as to ensure that the cloud computing platform can make a correct response after receiving the access request, and ensure that the cloud desktop access can proceed smoothly; When the preset requirements are not met, by sending the access request and the exception log file corresponding to the access request to the terminal device of the management personnel, the management personnel can be enabled according to the access request and the exception log file To locate the cause of the access request that does not meet the preset requirements, quickly resolve the abnormal phenomenon, and then ensure the user experience.

It should be noted that those of ordinary skill in the art may understand that all or part of the steps to implement the above-mentioned embodiments may be completed by hardware, or may be controlled by computer-readable instructions to control related hardware. The computer-readable instructions may be stored in In a non-volatile computer-readable storage medium, the aforementioned non-volatile readable storage medium may be a read-only memory, a magnetic disk, or an optical disk.

Referring to FIG. 4, FIG. 4 is a structural block diagram of a first embodiment of a cloud desktop access device of the present application.

As shown in FIG. 4, the cloud desktop access device provided in the embodiment of the present application includes: a page identifier acquisition module 4001, a TCP long connection search module 4002, and a cloud desktop access module 4003. Among them, the page identifier acquisition module 4001 is used to receive a cloud desktop access request triggered by a user through a web browser, and extract the page identifier of the web browser from the access request; the TCP long connection search module 4002 is used to The page identifier, from a pre-constructed TCP connection pool, to find a long TCP connection required for communication between the web browser and the cloud desktop; a cloud desktop access module 4003 is used to use the long TCP connection to transfer the The access request is sent to the cloud computing platform, and the response information made by the cloud computing platform is received to implement access to the cloud desktop provided by the cloud computing platform.

It should be understood that, in practical applications, in order to facilitate maintenance and management, the operations performed by the TCP long connection search module 4002 may be specifically divided, and the refined operations are allocated to different functional modules.

For example, in practical applications, the TCP long connection search module 4002 may be divided into: an identification number search sub-module, a TCP long connection search sub-module, and a TCP long connection creation sub-module.

Specifically, the identification number searching submodule is used to search for the identification number of the TCP long connection corresponding to the page identification from a pre-recorded TCP long connection record table using the page identification as an index item; the TCP long The connection search submodule is used to search for the TCP long connection corresponding to the identification number from the pre-built TCP connection pool according to the identification number when the identification number of the TCP long connection corresponding to the page identification is found, and Use the found TCP long connection as the TCP long connection required for the web browser to communicate with the cloud desktop; the TCP long connection creation sub-module is used to find the TCP corresponding to the page identifier when the page identifier is not found When the identification number of the long connection is created, create a TCP long connection as the TCP long connection required for the web browser to communicate with the cloud desktop, and update the identification number of the created TCP long connection to the TCP long connection record table in.

The operation of the TCP long connection creation submodule to create a TCP long connection can be roughly as follows: send a handshake request to the cloud computing platform to access the cloud desktop, negotiate the parameters required to establish a TCP long connection; receive the cloud computing platform The first parameter information of the handshake response and feedback made; obtaining the second parameter information of the local machine; performing an intersection processing on the first parameter information and the second parameter information to obtain a candidate parameter set; from the backup Select any one of the parameter sets as the parameter required to establish a long TCP connection to complete the handshake operation; send the first hypertext transfer protocol server address and the first Internet protocol port bound to the TCP long connection to the cloud computing platform And receive the second hypertext transfer protocol server address and the second Internet protocol port bound to the cloud desktop delivered by the cloud computing platform to complete the creation of a long TCP connection.

In addition, it should be understood that in practical applications, in order to save the user machine resources, the number of long TCP connections added to the pre-built TCP connection pool is limited, so there may be TCP found The long connection is currently in use. Therefore, in order to ensure the smooth operation of the cloud desktop access operation, the cloud desktop access device provided in this embodiment may further include a state detection module.

Wherein, the state detection module is configured to determine whether the found TCP long connection is used as the TCP long connection required for communication between the web browser and the cloud desktop as the TCP long connection found Idle.

Correspondingly, if it is determined that the long TCP connection found is in an idle state, the long TCP connection found is used as the long TCP connection required for communication between the web browser and the cloud desktop.

It is not difficult to find from the above description that the cloud desktop access device provided in this embodiment accesses the cloud desktop provided by the cloud platform by using web browsing, so that there is no need to install a separate application for accessing the cloud desktop on the user machine. There is no need to additionally set up a proxy server that supports the work of accessing the cloud desktop application, thereby effectively reducing the access cost of the cloud desktop.

Based on the first embodiment of the cloud desktop access device described above, a second embodiment of the cloud desktop access device of the present application is proposed.

In this embodiment, the cloud desktop access device further includes an access request detection module.

Wherein, the access request detection module is used to determine whether the access request meets the preset requirements.

Correspondingly, if the access request meets the preset requirements, the cloud desktop access module is triggered to perform the operation of “using the TCP long connection to send the access request to the cloud computing platform”.

In addition, it should be understood that, in practical applications, in order to solve the problem that the access request does not meet the preset requirements as soon as possible, the cloud desktop access device provided in this embodiment may further include a log acquisition module and an exception information sending module.

Wherein, the log obtaining module is used to obtain an exception log file corresponding to the access request when the access request detection module determines that the access request does not meet the preset requirements by judging the access request; the exception information is sent A module for sending the access request and the abnormal log file to the terminal device of the manager, so that the manager can locate the access request and the abnormal log file according to the access request and the abnormal log file Reasons for meeting preset requirements.

Further, in order to facilitate the management personnel to handle, the reason that the access request does not meet the preset requirements can be quickly located. Before sending the access request and the abnormal log file to the terminal device of the management personnel, Mark the contents of the exception log file. Therefore, the cloud desktop access device provided in this embodiment may further include an abnormality marking module.

Wherein, the abnormality marking module is used to compare the abnormality log file with the normality log file pre-stored when the access request is initiated, and mark the inconsistent content to obtain a marked version of the abnormality log file.

Correspondingly, when sending abnormal information such as the access request and the abnormal log file corresponding to the access request, the abnormal information sending module specifically sends the access request and the marked version of the abnormal log file to the management The terminal device of the personnel, so that the management personnel can locate the reason that the access request does not meet the preset requirements according to the access request and the abnormal log file of the marked version.

From the above description, it is not difficult to find that the cloud desktop access device provided in this example, before using the found TCP long connection to send the access request to the cloud computing platform, by judging the access request, it is determined that the Only when the requirements are set, will the access request be sent to the cloud computing platform, so as to ensure that the cloud computing platform can make a correct response after receiving the access request, and ensure that the cloud desktop access can proceed smoothly; When the preset requirements are not met, by sending the access request and the exception log file corresponding to the access request to the terminal device of the management personnel, the management personnel can be enabled according to the access request and the exception log file To locate the cause of the access request that does not meet the preset requirements, quickly resolve the abnormal phenomenon, and then ensure the user experience.

In addition, it should be noted that in this article, the terms "include", "include" or any other variant thereof are intended to cover non-exclusive inclusion, so that a process, method, article or system that includes a series of elements includes not only those Elements, but also include other elements that are not explicitly listed, or include elements inherent to this process, method, article, or system. Without more restrictions, the element defined by the sentence "include one ..." does not exclude that there are other identical elements in the process, method, article or system that includes the element.

The sequence numbers of the above embodiments of the present application are for description only, and do not represent the advantages and disadvantages of the embodiments.

Through the description of the above embodiments, those skilled in the art can clearly understand the above The method of the embodiment can be implemented by means of software plus the necessary general hardware platform, and of course it can also be implemented by hardware, but in many cases the former is the better implementation. Based on this understanding, the The technical solution can be embodied in the form of a software product in essence or part of the contribution to the existing technology. The computer software product is stored in a storage medium (such as read-only memory (Read Only) Memory, ROM) / RAM, disk, optical Disk), including several instructions to enable a terminal device (which may be a mobile phone, a computer, a server, or a network device, etc.) to execute the method described in each embodiment of the present application.

The above are only the preferred embodiments of the present application, and do not limit the patent scope of the present application. Any equivalent structure or equivalent process transformation made by the description and drawings of this application, or directly or indirectly used in other related technical fields , The same reason is included in the scope of patent protection of this application.

Claims

A cloud desktop access method, characterized in that the method includes:

Receiving a cloud desktop access request triggered by a user through a web browser, and extracting the page identifier of the web browser from the access request;

Searching for a long TCP connection required for communication between the web browser and the cloud desktop from a pre-built TCP connection pool according to the page identifier;

Using the long TCP connection, the access request is sent to the cloud computing platform, and the response information made by the cloud computing platform is received to achieve access to the cloud desktop provided by the cloud computing platform.
The method according to claim 1, wherein the step of searching for a long TCP connection required for communication between the web browser and the cloud desktop from a pre-built TCP connection pool according to the page identifier, include:

Using the page identifier as an index item, look up the identification number of the TCP long connection corresponding to the page identifier from a pre-recorded TCP long connection record table;

If the identification number of the TCP long connection corresponding to the page identification is found, then the TCP long connection corresponding to the identification number is found from the pre-built TCP connection pool according to the identification number, and the found TCP The long connection serves as a long TCP connection required for communication between the web browser and the cloud desktop;

If the identification number of the TCP long connection corresponding to the page identifier is not found, a TCP long connection is created as the TCP long connection required for communication between the web browser and the cloud desktop, and the created TCP long connection The identification number is updated into the TCP long connection record table.
The method according to claim 2, wherein before the step of using the found TCP long connection as the TCP long connection required for communication between the web browser and the cloud desktop, the method further include:

Determine whether the long TCP connection found is in an idle state;

Wherein, using the found TCP long connection as the TCP long connection required for communication between the web browser and the cloud desktop includes:

If the long TCP connection found is in an idle state, the long TCP connection found is used as the long TCP connection required for communication between the web browser and the cloud desktop.
The method of claim 2, wherein the step of creating a long TCP connection includes:

Send a handshake request to the cloud computing platform to access the cloud desktop to negotiate the parameters required to establish a long TCP connection;

Receiving the first parameter information of the handshake response and feedback made by the cloud computing platform;

Obtain the second parameter information of this machine;

Performing intersection processing on the first parameter information and the second parameter information to obtain a candidate parameter set;

Select any one of the candidate parameter sets as the parameter required to establish a long TCP connection to complete the handshake operation;

Send the first hypertext transfer protocol server address and the first Internet protocol port bound to the cloud computing platform to the cloud computing platform, and receive the second hypertext transfer protocol bound to the cloud desktop issued by the cloud computing platform The server address and the second Internet protocol port complete the creation of a long TCP connection.
The method of claim 1, wherein before the step of using the TCP long connection to send the access request to a cloud computing platform, the method further comprises:

Determine whether the access request meets the preset requirements;

Wherein, using the TCP long connection to send the access request to the cloud computing platform includes:

If the access request meets the preset requirements, the TCP long connection is used to send the access request to the cloud computing platform.
The method according to claim 5, wherein after the step of determining whether the access request meets a preset requirement, the method further comprises:

If the access request does not meet the preset requirements, obtain an exception log file corresponding to the access request;

Sending the access request and the abnormal log file to the terminal device of the manager, so that the manager can locate the access request that does not meet the preset requirements based on the access request and the abnormal log file s reason.
The method according to claim 6, wherein before the step of sending the access request and the exception log file to a terminal device of a manager, the method further comprises:

Comparing the abnormal log file with the pre-stored normal log file generated when the access request is initiated, and marking the inconsistent content to obtain a marked version of the abnormal log file;

Wherein, the sending of the access request and the abnormal log file to the terminal device of the management personnel includes:

Sending the access request and the marked version of the abnormal log file to the terminal device of the administrator, so that the manager can locate the access cause The reason why the request does not meet the preset requirements.
A cloud desktop access device, characterized in that the device includes:

A page identifier acquisition module, configured to receive a cloud desktop access request triggered by a user through a web browser, and extract the page identifier of the web browser from the access request;

A TCP long connection search module, configured to search for a TCP long connection required for communication between the web browser and the cloud desktop from a pre-built TCP connection pool according to the page identifier;

The cloud desktop access module is used to send the access request to the cloud computing platform using the long TCP connection, and receive the response information made by the cloud computing platform to implement access to the cloud desktop provided by the cloud computing platform .
A cloud desktop access device, characterized in that the device includes: a memory, a processor, and a cloud desktop access readable instruction stored on the memory and operable on the processor, the cloud desktop The access readable instructions are configured to implement the following steps:

Receiving a cloud desktop access request triggered by a user through a web browser, and extracting the page identifier of the web browser from the access request;

Searching for a long TCP connection required for communication between the web browser and the cloud desktop from a pre-built TCP connection pool according to the page identifier;

Using the long TCP connection, the access request is sent to the cloud computing platform, and the response information made by the cloud computing platform is received to achieve access to the cloud desktop provided by the cloud computing platform.
The cloud desktop access device according to claim 9, wherein the TCP length required for communication between the web browser and the cloud desktop is searched from a pre-built TCP connection pool according to the page identifier The connection steps include:

Using the page identifier as an index item, look up the identification number of the TCP long connection corresponding to the page identifier from a pre-recorded TCP long connection record table;

If the identification number of the TCP long connection corresponding to the page identification is found, then the TCP long connection corresponding to the identification number is found from the pre-built TCP connection pool according to the identification number, and the found TCP The long connection serves as a long TCP connection required for communication between the web browser and the cloud desktop;

If the identification number of the TCP long connection corresponding to the page identifier is not found, a TCP long connection is created as the TCP long connection required for communication between the web browser and the cloud desktop, and the created TCP long connection The identification number is updated into the TCP long connection record table.
The cloud desktop access device according to claim 10, wherein before the step of using the found TCP long connection as the TCP long connection required for communication between the web browser and the cloud desktop, The method also includes:

Determine whether the long TCP connection found is in an idle state;

Wherein, using the found TCP long connection as the TCP long connection required for communication between the web browser and the cloud desktop includes:

If the long TCP connection found is in an idle state, the long TCP connection found is used as the long TCP connection required for communication between the web browser and the cloud desktop.
The cloud desktop access device according to claim 10, wherein the step of creating a long TCP connection includes:

Send a handshake request to the cloud computing platform to access the cloud desktop to negotiate the parameters required to establish a long TCP connection;

Receiving the first parameter information of the handshake response and feedback made by the cloud computing platform;

Obtain the second parameter information of this machine;

Performing intersection processing on the first parameter information and the second parameter information to obtain a candidate parameter set;

Select any one of the candidate parameter sets as the parameter required to establish a long TCP connection to complete the handshake operation;

Send the first hypertext transfer protocol server address and the first Internet protocol port bound to the cloud computing platform to the cloud computing platform, and receive the second hypertext transfer protocol bound to the cloud desktop issued by the cloud computing platform The server address and the second Internet protocol port complete the creation of a long TCP connection.
The cloud desktop access device according to claim 9, wherein before the step of using the TCP long connection to send the access request to a cloud computing platform, the method further includes:

Determine whether the access request meets the preset requirements;

Wherein, using the TCP long connection to send the access request to the cloud computing platform includes:

If the access request meets the preset requirements, the TCP long connection is used to send the access request to the cloud computing platform.
The cloud desktop access device according to claim 13, wherein after the step of determining whether the access request meets a preset requirement, the method further includes:

If the access request does not meet the preset requirements, obtain an exception log file corresponding to the access request;

Sending the access request and the abnormal log file to the terminal device of the manager, so that the manager can locate the access request that does not meet the preset requirements based on the access request and the abnormal log file s reason.
The cloud desktop access device according to claim 14, wherein before the step of sending the access request and the exception log file to a terminal device of a manager, the method further includes:

Comparing the abnormal log file with the pre-stored normal log file generated when the access request is initiated, and marking the inconsistent content to obtain a marked version of the abnormal log file;

Wherein, the sending of the access request and the abnormal log file to the terminal device of the management personnel includes:

Sending the access request and the marked version of the abnormal log file to the terminal device of the manager, so that the manager can locate the access caused by the access request and the marked version of the abnormal log file The reason why the request does not meet the preset requirements.
A storage medium is characterized in that cloud desktop access readable instructions are stored on the storage medium, and the cloud desktop access readable instructions implement the following steps when executed by a processor:

Receiving a cloud desktop access request triggered by a user through a web browser, and extracting the page identifier of the web browser from the access request;

Searching for a long TCP connection required for communication between the web browser and the cloud desktop from a pre-built TCP connection pool according to the page identifier;

Using the long TCP connection, the access request is sent to the cloud computing platform, and the response information made by the cloud computing platform is received to achieve access to the cloud desktop provided by the cloud computing platform.
The storage medium according to claim 16, wherein the step of searching for a long TCP connection required for communication between the web browser and the cloud desktop from a pre-built TCP connection pool according to the page identifier ,include:

Using the page identifier as an index item, look up the identification number of the TCP long connection corresponding to the page identifier from a pre-recorded TCP long connection record table;

If the identification number of the TCP long connection corresponding to the page identification is found, then the TCP long connection corresponding to the identification number is found from the pre-built TCP connection pool according to the identification number, and the found TCP The long connection serves as a long TCP connection required for communication between the web browser and the cloud desktop;

If the identification number of the TCP long connection corresponding to the page identifier is not found, a TCP long connection is created as the TCP long connection required for communication between the web browser and the cloud desktop, and the created TCP long connection The identification number is updated into the TCP long connection record table.
The storage medium according to claim 17, wherein before the step of using the found TCP long connection as a TCP long connection required for communication between the web browser and the cloud desktop, the method Also includes:

Determine whether the long TCP connection found is in an idle state;

Wherein, using the found TCP long connection as the TCP long connection required for communication between the web browser and the cloud desktop includes:

If the long TCP connection found is in an idle state, the long TCP connection found is used as the long TCP connection required for communication between the web browser and the cloud desktop.
The storage medium according to claim 16, wherein before the step of using the TCP long connection to send the access request to a cloud computing platform, the method further includes:

Determine whether the access request meets the preset requirements;

Wherein, using the TCP long connection to send the access request to the cloud computing platform includes:

If the access request meets the preset requirements, the TCP long connection is used to send the access request to the cloud computing platform.
The storage medium according to claim 19, wherein after the step of determining whether the access request meets a preset requirement, the method further includes:

If the access request does not meet the preset requirements, obtain an exception log file corresponding to the access request;

Sending the access request and the abnormal log file to the terminal device of the manager, so that the manager can locate the access request that does not meet the preset requirements based on the access request and the abnormal log file s reason. The