A cloud application system based on WEB communication interaction technology and a method thereof

Abstract

The application provides a cloud application system based on WEB communication interaction technology and a method thereof. The cloud application system based on WEB communication interaction technology comprises a webpage front end, a scheduling server and a cloud virtual machine. The webpage front end is used for receiving user operation instructions, providing interfaces and interactive components for users. The cloud virtual machine is used for running application instances and receiving instructions for execution. The scheduling server is used for information transfer, helping the front end and the cloud virtual machine to establish a handshake connection, and monitoring the running state of the webpage front end. The technical scheme of the application relies on remote desktop technology, has a simple overall structure, does not change the application program logic, and has low development cost. Meanwhile, the system adopts an efficient data transmission format, optimizes network delay, and has good network adaptability. Moreover, the technology itself supports a non-GPU running mode, effectively reducing the cost.

Description

Technical Field

[0001] This invention relates to the fields of cloud application architecture and web technology, and in particular to a system and method for cloud applications based on web communication and interaction technology. Background Technology

[0002] With the rapid development and widespread adoption of information technologies such as cloud computing, the cloudification of software applications has become a growing trend. For large-scale software applications, the traditional local model requires users to install and manage version updates themselves, and the user experience is limited by the performance of the local computer, placing high demands on computer configuration. Furthermore, the local model struggles to meet the needs of multi-user collaborative work scenarios, resulting in inefficient file management.

[0003] A common implementation of cloud-based application models is the pure web application. This solution uses the web as a carrier, providing users with a convenient environment. However, due to limitations in web page performance and user hardware, pure web applications cannot guarantee smooth visual performance for large-scale applications. Furthermore, when operations involving uploading and downloading are involved, this solution requires significant data transfer, failing to provide users with a good file operation experience.

[0004] Another implementation relies on streaming cloud technology. This approach typically requires deep modifications to the application, including underlying file operation logic, resulting in high development costs and few successful cases in the market. Moreover, for large-scale, graphically rich, and interactive applications, this approach usually requires graphics card support and has high network performance requirements, thus leading to high operating costs. Summary of the Invention

[0005] To overcome the aforementioned technical deficiencies, the first aspect of the present invention provides a cloud-based application system based on web communication and interaction technology, comprising:

[0006] The webpage front-end is used for user login; it is also used to send instructions to the scheduling server to request the start of an application instance; it is also used to establish a handshake connection between the scheduling server and the cloud virtual machine; it is also used to receive cloud remote desktop streams and text information streams directly sent by the cloud virtual machine, present the application window interface to the user, and receive the user's application operation instructions; it is also used to send the received user-inputted application operation instructions directly to the application instance on the cloud virtual machine through the remote desktop interface; and it is also used to display the execution results generated by the application instance on the cloud virtual machine and the updated interface information to the user.

[0007] The scheduling server is used to forward instructions requesting the launch of an application instance to the cloud virtual machine; it is also used to assist in establishing a handshake connection between the cloud virtual machine and the web frontend; and it is also used to continuously monitor the status of the web frontend and the cloud virtual machine.

[0008] The cloud virtual machine is used to receive and start application instances from requests forwarded by the scheduling server; it is also used to establish a handshake connection between the scheduling server and the web frontend; it is also used to directly transmit cloud remote desktop streams and text information streams to the web frontend, and embed the application window interface into the web frontend through the remote desktop interface to present it to the user; it is also used to execute application operation instructions and generate execution results and updated interface information; and it is also used to directly send the execution results and updated cloud remote desktop information to the web frontend.

[0009] For example, the cloud virtual machine in this application can use a high-performance chip server located abroad to provide remote cloud application services to Chinese customers.

[0010] Furthermore, the web frontend is used to send a request to start the application instance to the scheduling server via HTTPS; the scheduling server is used to forward the request to start the application instance to the cloud virtual machine via the WebSocket network protocol and start the application instance on the cloud virtual machine. After the application instance starts, it establishes a WebSocket connection with the scheduling server, and the scheduling server informs the web frontend of the instance's startup status, thus binding the web frontend and the instance.

[0011] Furthermore, the scheduling server forwards the handshake request of the cloud virtual machine application instance to the web frontend; the web frontend responds to the handshake request, and the scheduling server also forwards the response information to the cloud virtual machine via the WebSocket network protocol; the cloud virtual machine generates handshake confirmation information, and the scheduling server also forwards the handshake confirmation information to the web frontend and enters the established connection state; the web frontend receives the handshake confirmation information and enters the established state, thus completing the establishment of the handshake connection, enabling direct information interaction between the web frontend and the cloud virtual machine.

[0012] Furthermore, the webpage front-end has a rendering component that supports user interaction; the cloud virtual machine is used to embed the application window interface into the rendering component of the webpage front-end through the remote desktop interface to present it to the user: the cloud remote desktop stream information transmitted by the cloud virtual machine is carried on TCP, converted into RFB protocol data carried on Websocket by the Websockify proxy, decoded by the noVNC client, and transmitted to the rendering component of the front-end; the text information stream uses the Protobuf data format, serializes the data structure into a byte stream for transmission, is encoded by the Protobuf compiler at the cloud virtual machine, transmitted to the webpage front-end, and then decoded by the Protobuf compiler of the webpage front-end, and the corresponding display is completed by the rendering component.

[0013] Furthermore, both application operation command information and execution result information adopt the Protobuf data format. The web page front-end is used to encode the application operation command information and execution result information, while the cloud virtual machine is used to decode the application operation command information and execution result information. The cloud virtual machine is also used to embed the updated cloud remote desktop information into the rendering component of the web page front-end through the remote desktop interface to present it to the user.

[0014] A second aspect of the present invention provides a cloud application method for a cloud application system employing the above-described cloud application system based on web communication and interaction technology, comprising:

[0015] Step S1: The user logs into the web frontend and sends a request to start the application instance to the scheduling server. The scheduling server forwards the request to start the application instance to the cloud virtual machine, and the cloud virtual machine starts the application instance on it.

[0016] Step S2: The cloud virtual machine establishes a handshake connection with the web page front-end through the scheduling server, thereby enabling direct information exchange between the web page front-end and the cloud virtual machine;

[0017] Step S3: The cloud virtual machine directly transmits the cloud remote desktop stream and text information stream to the web page front end, embeds the application window interface into the web page front end through the remote desktop interface to present it to the user, and then the web page front end receives the user's application operation instructions.

[0018] Step S4: The web page front-end sends the received user input application operation instructions directly to the application instance on the cloud virtual machine through the remote desktop interface. The application instance on the cloud virtual machine executes the application operation instructions and generates the execution results and updated interface information.

[0019] Step S5: The cloud virtual machine sends the execution results and the updated cloud remote desktop information directly to the web page front-end and displays them to the user;

[0020] In steps S1-S5, the scheduling server continuously monitors the status of the web page frontend and the cloud virtual machine.

[0021] For example, the cloud virtual machine in this application can use a high-performance chip server located abroad to provide remote cloud application services to Chinese customers.

[0022] Furthermore, in step S1, the web page frontend sends a request to start the application instance to the scheduling server via HTTPS. The scheduling server forwards the request to start the application instance to the cloud virtual machine via the WebSocket network protocol and starts the application instance on the cloud virtual machine. After the application instance starts, it establishes a WebSocket connection with the scheduling server. The scheduling server informs the web page frontend of the instance's startup status, thus binding the web page frontend and the instance.

[0023] Furthermore, in step S2, the cloud virtual machine instance first has its handshake request forwarded by the scheduling server to the web frontend; the web frontend responds to the handshake request, and this response information is forwarded to the cloud virtual machine via the WebSocket network protocol through the scheduling server; after the cloud virtual machine generates handshake confirmation information, it is forwarded by the scheduling service to the web frontend and enters the established connection state; after the web frontend receives the handshake confirmation information, it also enters the established state, thus completing the establishment of the handshake connection, thereby enabling direct information interaction between the web frontend and the cloud virtual machine.

[0024] Furthermore, in step S3, the webpage front-end has a rendering component that supports user interaction. The cloud virtual machine embeds the application window interface into the rendering component of the webpage front-end through the remote desktop interface to present it to the user. The cloud remote desktop stream information transmitted by the cloud virtual machine is carried on TCP, converted into RFB protocol data carried on Websocket by the Websockify proxy, decoded by the noVNC client, and transmitted to the rendering component of the front-end. The text information stream uses the Protobuf data format, serializes the data structure into a byte stream for transmission, is encoded by the Protobuf compiler at the cloud virtual machine, transmitted to the webpage front-end, and then decoded by the Protobuf compiler of the webpage front-end, and the corresponding display is completed by the rendering component.

[0025] Furthermore, in step S4, the application operation instruction information adopts the Protobuf data format and is encoded and decoded by the Protobuf compiler at the web front-end and the cloud virtual machine, respectively; in step S5, the execution result information adopts the Protobuf data format and is encoded and decoded by the Protobuf compiler at the web front-end and the cloud virtual machine, respectively; the cloud virtual machine embeds the updated cloud remote desktop information into the rendering component of the web front-end through the remote desktop interface to present it to the user.

[0026] This application provides a cloud-based application system based on web communication and interaction technology, comprising a web front-end, a scheduling server, and a cloud virtual machine. The web front-end receives user operation commands and provides the user with an interface and interactive components. The cloud virtual machine runs application instances and receives commands to execute. The scheduling server acts as an intermediary, assisting the front-end in establishing a handshake connection with the cloud virtual machine and monitoring the running status of the web front-end. Compared with existing technologies, the above technical solution offers the following advantages:

[0027] 1. Good network adaptability: The technical solution of this invention adopts a high-efficiency data transmission format, optimizes network latency, and has good network adaptability; the web page front-end does not require users to use high-performance machines, and users can access it smoothly even using tablets and other devices.

[0028] 2. Cost reduction: The technical solution of this invention relies on remote desktop technology, with a simple overall architecture that does not change the application logic and has low development costs; at the same time, the cloud virtual machine adopts a low-power, high-efficiency ARM Linux system, resulting in low procurement costs; furthermore, the technical solution of this application supports a graphics card-less operation mode, effectively reducing hardware costs by approximately 90%.

[0029] 3. Remote cloud application services can be provided: The cloud virtual machine in the technical solution of this application can use a high-end chip server located abroad to provide remote cloud application services to domestic customers. Attached Figure Description

[0030] Figure 1 This is a schematic diagram of the system structure of a cloud application based on WEB communication and interaction technology in one embodiment of this application. The scheduling server in the figure is used for information relay, and its information communication is represented by dashed lines to distinguish it from the direct information channel between the web page front-end and the cloud virtual machine.

[0031] Figure 2 This is an interaction sequence diagram of a cloud application method based on WEB communication and interaction technology in one embodiment of this application.

[0032] Figure 3 A flowchart of a cloud application method based on WEB communication and interaction technology in one embodiment of this application;

[0033] Figure 4 This is an interaction sequence diagram of step S1 in a cloud application method based on WEB communication and interaction technology according to an embodiment of this application.

[0034] Figure 5 This is an interaction sequence diagram of step S2 in a cloud application method based on WEB communication and interaction technology according to an embodiment of this application;

[0035] Figure 6This is an interaction sequence diagram of step S3 in a cloud application method based on WEB communication and interaction technology in one embodiment of this application.

[0036] Figure 7 This is a schematic diagram of the web page front-end interface in one embodiment of this application when the cloud application is a 3D design software.

[0037] Figure 8 This is an interaction sequence diagram of step S4 in a cloud application method based on WEB communication and interaction technology according to an embodiment of this application.

[0038] Figure 9 This is an interaction sequence diagram of step S5 in a cloud application method based on WEB communication and interaction technology according to an embodiment of this application. Detailed Implementation

[0039] The advantages of the present invention are further illustrated below with reference to the accompanying drawings and specific embodiments. Those skilled in the art should understand that the following detailed description is illustrative rather than restrictive and should not be construed as limiting the scope of protection of the present invention.

[0040] like Figure 1 As shown, this embodiment provides a cloud application system based on WEB communication and interaction technology, which includes: a web page front-end, a scheduling server, and a cloud virtual machine.

[0041] The web page frontend is used for user login; it is also used to send instructions to start application instances to the scheduling server; it is also used to establish a handshake connection between the scheduling server and the cloud virtual machine; it is also used to receive cloud remote desktop streams and text information streams directly sent by the cloud virtual machine, present the application window interface to the user, and receive the user's application operation instructions; it is also used to send the received user-inputted application operation instructions directly to the application instance on the cloud virtual machine through the remote desktop interface; and it is also used to display the execution results generated by the application instance on the cloud virtual machine and the updated interface information to the user.

[0042] The scheduling server is used to forward instructions requesting the launch of application instances to the cloud virtual machine; it is also used to assist in establishing a handshake connection between the cloud virtual machine and the web frontend; and it is used to continuously monitor the status of the web frontend and the cloud virtual machine.

[0043] The cloud virtual machine is used to receive and start application instances from requests forwarded by the scheduling server; it is also used to establish a handshake connection between the scheduling server and the web frontend; it is also used to directly transmit cloud remote desktop streams and text information streams to the web frontend, and to embed the application window interface into the web frontend through the remote desktop interface to present it to the user; it is also used to execute application operation instructions and generate execution results and updated interface information; and it is also used to directly send the execution results and updated cloud remote desktop information to the web frontend.

[0044] like Figure 2 and Figure 3 As shown, the method for implementing cloud-based applications using the cloud-based application system based on the above-mentioned WEB communication and interaction technology includes the following steps S1-S5:

[0045] Step S1: The user logs into the web frontend and sends a request to start the application instance to the scheduling server. The scheduling server forwards the request to start the application instance to the cloud virtual machine, and the cloud virtual machine starts the application instance on it.

[0046] like Figure 4 As shown, in the initial stages of deploying cloud applications, cloud virtual machines need to complete service registration through a proxy at the scheduling server. After the user logs in, the web frontend sends a request to start the instance to the scheduling server via HTTPS. The scheduling server starts the cloud virtual machine instance via the WebSocket network protocol, and the instance establishes a WebSocket connection with the scheduling server after startup. The scheduling server further informs the web frontend of the instance's startup status, thus binding the web frontend and the instance. After successful binding, the frontend and the instance can communicate one-to-one through the scheduling service.

[0047] Step S2: The cloud virtual machine establishes a handshake connection with the web frontend through the scheduling server, enabling direct information exchange between the web frontend and the cloud virtual machine.

[0048] like Figure 5 As shown, after establishing one-to-one communication, the cloud virtual machine instance first forwards a handshake request from the scheduling server to the web frontend. The web frontend responds to the handshake request, and this response information is forwarded to the cloud virtual machine via the WebSocket network protocol through the scheduling server. After the cloud virtual machine generates a handshake confirmation message, it is forwarded by the scheduling service to the web frontend, and enters the established connection state. After receiving the handshake confirmation message, the web frontend also enters the established state. At this point, both the web frontend and the cloud virtual machine confirm their respective sending and receiving capabilities, and the handshake connection is established, enabling direct information exchange between the web frontend and the cloud virtual machine.

[0049] Step S3: The cloud virtual machine directly transmits the cloud remote desktop stream and text information stream to the web page front end, embeds the application window interface into the web page front end through the remote desktop interface to present it to the user, and then the web page front end receives the user's application operation instructions.

[0050] like Figure 6 As shown, based on the established handshake connection channel, the cloud virtual machine can directly transmit cloud desktop streams and text information streams to the web page front-end. The application interface is embedded into the front-end rendering component through the remote desktop interface and presented to the user. The application interface is a cropped desktop image from the cloud virtual machine; only the application image area is transmitted. The remote desktop interface is implemented using the noVNC service and the Websockify proxy tool. Specifically, the cloud desktop stream information transmitted by the cloud virtual machine is carried over TCP, converted into RFB protocol data carried over WebSocket by the Websockify proxy, decoded by the noVNC client, and transmitted to the front-end rendering component.

[0051] The text information stream uses the Protobuf data format, which serializes the data structure into a byte stream for transmission. The Protobuf compiler at the cloud virtual machine encodes the data, transmits it to the web page front-end, and then decodes it through the compiler. The corresponding display is then completed by the rendering component.

[0052] The webpage front-end also incorporates additionally developed rendering components (including but not limited to icons, left and right-click menus, pop-ups, fixed panels, and editors) to support user interaction. These front-end rendering components can be implemented using the Vue application framework (but are not limited to this framework). For example, Figure 7 The cloud application corresponding to the webpage's front-end interface is 3D design software. Figure 7 In the webpage front-end interface, A is the webpage front-end toolbar, B is the webpage front-end graphic area, C is the webpage front-end editor, D is the webpage front-end fixed panel, E is the webpage front-end left / right-click menu, and F is the webpage front-end pop-up window.

[0053] Step S4: The web page front-end sends the received user input application operation instructions directly to the application instance on the cloud virtual machine through the remote desktop interface. The application instance on the cloud virtual machine executes the application operation instructions and generates the execution results and updated interface information.

[0054] like Figure 8As shown, users can interact with components through the interface. Specifically, users can select and click on objects, change views, and perform other operations on the interface. The icon component integrates operation commands into an icon set, allowing users to perform quick operations. The left-click menu component recommends operation functions based on the user's selected object. The right-click menu component presents the supported functions as a text list. The pop-up component implements data input and displays prompt messages and error messages. The fixed panel component displays the file frame and the property information of objects within the application. The editor component supports code text editing for secondary development.

[0055] The operation command information uses the Protobuf data format, which is encoded and decoded by the Protobuf compiler at the web front-end and the cloud virtual machine, respectively.

[0056] Step S5: The cloud virtual machine sends the execution results and the updated cloud remote desktop information directly to the web page front-end and displays them to the user.

[0057] like Figure 9 As shown, the execution results, updated interface, and data information are returned through the channel between the cloud virtual machine and the web frontend, and displayed to the user on the web frontend. The transmission of the application interface is consistent with the remote desktop interface scheme in step 3. The data information also uses the Protobuf data format, and is encoded and decoded by the Protobuf compiler at the cloud virtual machine and the web frontend, respectively.

[0058] In steps S1-S5, the scheduling server continuously monitors the status of the web frontend and the cloud virtual machine. Even after the web frontend and the cloud virtual machine establish a connection, the scheduling server continues to provide status monitoring support, which is one of the innovations of this application. The scheduling server uses the WebSocket network protocol to request the web frontend and the cloud virtual machine to send heartbeat detection information to the scheduling server periodically (e.g., every 20 seconds) for monitoring purposes. If the scheduling server detects that the frontend is connected but the cloud virtual machine is disconnected, it sends a command to request the restart of the cloud virtual machine to facilitate rapid restoration of the communication connection. If the scheduling server detects that the frontend is disconnected and there is no reconnection request within a certain period, it sends a shutdown command to the cloud virtual machine, requesting the shutdown of the application instance and the release of computing resources. The heartbeat monitoring information, the restart request command for the cloud virtual machine, and the shutdown request command for the cloud virtual machine can all use Protobuf data format.

[0059] It should be noted that the embodiments of the present invention have better implementability and are not intended to limit the present invention in any way. Any person skilled in the art may use the above-disclosed technical content to change or modify it into equivalent effective embodiments. However, any modifications or equivalent changes and modifications made to the above embodiments based on the technical essence of the present invention without departing from the content of the technical solution of the present invention shall still fall within the scope of the technical solution of the present invention.

Claims

1. A cloud-based application system based on web communication and interaction technology, characterized in that, include: The web page front-end is used for user login and also for sending instructions to the scheduling server to request the start of an application instance. It is also used to establish a handshake connection between the scheduling server and the cloud virtual machine; it is also used to receive the cloud remote desktop stream and text information stream directly sent by the cloud virtual machine, present the application window interface to the user, and receive the user's application operation instructions; it is also used to send the received user-inputted application operation instructions directly to the application instance on the cloud virtual machine through the remote desktop interface; it is also used to display the execution results generated by the application instance on the cloud virtual machine and the updated interface information to the user. The scheduling server is used to forward instructions requesting the launch of an application instance to the cloud virtual machine; it is also used to assist in establishing a handshake connection between the cloud virtual machine and the web frontend; and it is also used to continuously monitor the status of the web frontend and the cloud virtual machine. The cloud virtual machine is used to receive the instruction to start the application instance forwarded by the scheduling server and start the application instance; it is also used to establish a handshake connection between the scheduling server and the web page front-end; it is also used to directly transmit the cloud remote desktop stream and text information stream to the web page front-end, and embed the application window interface into the web page front-end through the remote desktop interface to present it to the user; it is also used to execute application operation instructions and generate execution results and updated interface information. It is also used to send the execution results and updated cloud remote desktop information directly to the web page front-end.

2. The cloud-based application system based on WEB communication and interaction technology as described in claim 1, characterized in that, The web frontend sends a request to start an application instance to the scheduling server via HTTPS. The scheduling server forwards the request to start the application instance to the cloud virtual machine via the WebSocket network protocol and starts the application instance on the cloud virtual machine. After the application instance starts, it establishes a WebSocket connection with the scheduling server. The scheduling server informs the web frontend of the instance's startup status, thus binding the web frontend and the instance.

3. The cloud-based application system based on WEB communication and interaction technology as described in claim 1, characterized in that, The scheduling server forwards handshake requests from cloud virtual machine application instances to the web frontend. The web frontend responds to the handshake requests, and the scheduling server also forwards the response information to the cloud virtual machine via the WebSocket network protocol. The cloud virtual machine generates handshake confirmation information, which the scheduling server forwards to the web frontend, and the web frontend enters the established connection state. The web frontend receives the handshake confirmation information and enters the established state, thus completing the handshake connection and enabling direct information exchange between the web frontend and the cloud virtual machine.

4. The cloud-based application system based on WEB communication and interaction technology as described in claim 1, characterized in that, The webpage front-end has a rendering component that supports user interaction. The cloud virtual machine is used to embed the application window interface into the rendering component of the webpage front-end through a remote desktop interface to present it to the user. The cloud remote desktop stream information transmitted by the cloud virtual machine is carried on TCP, converted into RFB protocol data carried on WebSocket by the Websockify proxy, decoded by the noVNC client, and transmitted to the rendering component of the front-end. The text information stream uses the Protobuf data format, serializes the data structure into a byte stream for transmission, is encoded by the Protobuf compiler at the cloud virtual machine, transmitted to the webpage front-end, and then decoded by the Protobuf compiler of the webpage front-end, and displayed accordingly by the rendering component.

5. The cloud-based application system based on WEB communication and interaction technology as described in claim 1, characterized in that, Application operation command information and execution result information both adopt the Protobuf data format. The web front-end is used to encode the application operation command information and execution result information, while the cloud virtual machine is used to decode the application operation command information and execution result information. The cloud virtual machine is also used to embed the updated cloud remote desktop information into the rendering component of the web front-end through the remote desktop interface to present it to the user.

6. A cloud application method for a cloud application system based on WEB communication and interaction technology as described in any one of claims 1 to 5, characterized in that, include: Step S1: The user logs into the web frontend and sends a request to start the application instance to the scheduling server. The scheduling server forwards the request to start the application instance to the cloud virtual machine, and the cloud virtual machine starts the application instance on it. Step S2: The cloud virtual machine establishes a handshake connection with the web page front-end through the scheduling server, thereby enabling direct information exchange between the web page front-end and the cloud virtual machine; Step S3: The cloud virtual machine directly transmits the cloud remote desktop stream and text information stream to the web page front end, embeds the application window interface into the web page front end through the remote desktop interface to present it to the user, and then the web page front end receives the user's application operation instructions. Step S4: The web page front-end sends the received user input application operation instructions directly to the application instance on the cloud virtual machine through the remote desktop interface. The application instance on the cloud virtual machine executes the application operation instructions and generates the execution results and updated interface information. Step S5: The cloud virtual machine sends the execution results and the updated cloud remote desktop information directly to the web page front-end and displays them to the user; In steps S1-S5, the scheduling server continuously monitors the status of the web page frontend and the cloud virtual machine.

7. The cloud application method as described in claim 6, characterized in that, In step S1, the web page frontend sends a request to start the application instance to the scheduling server via HTTPS. The scheduling server forwards the request to start the application instance to the cloud virtual machine via the WebSocket network protocol and starts the application instance on the cloud virtual machine. After the application instance starts, it establishes a WebSocket connection with the scheduling server. The scheduling server informs the web page frontend of the instance's startup status, thus binding the web page frontend and the instance.

8. The cloud application method as described in claim 6, characterized in that, In step S2, the cloud virtual machine instance first has its handshake request forwarded by the scheduling server to the web frontend; the web frontend responds to the handshake request, and this response information is forwarded to the cloud virtual machine via the WebSocket network protocol through the scheduling server; after the cloud virtual machine generates handshake confirmation information, it is forwarded by the scheduling service to the web frontend and enters the established connection state; after the web frontend receives the handshake confirmation information, it also enters the established state, thus completing the establishment of the handshake connection, enabling the web frontend and the cloud virtual machine to directly interact with each other.

9. The cloud application method as described in claim 6, characterized in that, In step S3, the webpage front-end has a rendering component that supports user interaction. The cloud virtual machine embeds the application window interface into the rendering component of the webpage front-end through the remote desktop interface to present it to the user, including the following steps: the cloud remote desktop stream information transmitted by the cloud virtual machine is carried on TCP, converted into RFB protocol data carried on Websocket by the Websockify proxy, decoded by the noVNC client, and transmitted to the rendering component of the front-end; the text information stream uses the Protobuf data format, serializes the data structure into a byte stream for transmission, is encoded by the Protobuf compiler at the cloud virtual machine, transmitted to the webpage front-end, and then decoded by the Protobuf compiler of the webpage front-end, and the corresponding display is completed by the rendering component.

10. The cloud application method as described in claim 6, characterized in that, In step S4, the application operation instruction information adopts the Protobuf data format, which is encoded and decoded by the Protobuf compiler at the web front-end and the cloud virtual machine, respectively. In step S5, the execution result information adopts the Protobuf data format, which is encoded and decoded by the Protobuf compiler at the web front-end and the cloud virtual machine, respectively. The cloud virtual machine embeds the updated cloud remote desktop information into the rendering component of the web page front end through the remote desktop interface to present it to the user.

Images