A cloud desktop system and method

Abstract

This invention relates to a method for handling cloud desktop client faults, comprising: determining on the terminal whether the fault originates from a first operating system or a second operating system; in response to the fault originating from the second operating system, closing the cloud desktop client in the first operating system; and in response to the fault originating from the first operating system, reporting the fault to the maintenance party responsible for the terminal. This method for handling cloud desktop client faults avoids wasting user terminal warranty resources and reduces the workload of cloud desktop administrators, thereby improving the promotion and user experience of cloud desktop systems.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of computer network, in particular to a cloud desktop system and method. BACKGROUND

[0002] With years of technology development, cloud desktop system has been relatively mature. The traditional cloud desktop system refers to that the desktop system of a user is stored on a server. Through a remote server, the unified management of the desktop system of the user is realized, and dynamic distribution and operation, flexible allocation and recovery are realized. For example, VDI (Virtual Desktop Infrastructure) is a typical cloud desktop system, all operations are performed on the server side, and the thin terminal only provides network connection and interaction function. However, the cloud desktop system based on VDI is severely dependent on the network, and it is very difficult to use offline. Moreover, the support of VDI for peripheral devices is also very limited. Therefore, the user experience is not good.

[0003] Under the background of increasing computing power of PC platform, Intel company proposed IDV (Intelligent Desktop Virtualization) mode of cloud desktop system. IDV adopts distributed operation, uses local computing resources, can also provide better bandwidth experience and compatibility of peripheral devices, and can support offline operation.

[0004] However, when the computer network with a large number of computers is converted to the cloud desktop system, since various models of computers exist in the existing computer network, the IDV needs to create corresponding images for each model of computer in the cloud, and the management and maintenance of the cloud desktop system become very complex. This makes the conversion of the existing computer network to the cloud desktop system become too high in cost, which affects the promotion and use of the cloud desktop system. Moreover, the fault maintenance work of the existing cloud desktop system is also very heavy, which is not conducive to the smooth operation of the entire cloud desktop system. SUMMARY

[0005] In view of the technical problems in the prior art, the present application provides a method for processing fault of cloud desktop client, comprising: determining whether the fault is from a first operating system or a second operating system on a terminal; in response to the fault being from the second operating system, closing the cloud desktop client in the first operating system; and in response to the fault being from the first operating system, reporting the fault to a maintenance party responsible for the terminal.

[0006] The method as described above further comprises: detecting the cloud desktop client in response to the fault being eliminated after the cloud desktop client is closed.

[0007] The method as described above further comprises: sending a detection request to the server, detecting the cloud desktop client of the terminal by the server, and displaying a detection result.

[0008] The method as described above further comprises: updating the cloud desktop client from the server in response to the detection result indicating that the cloud desktop client has a problem.

[0009] The method as described above further comprises: detecting an image containing the second operating system on the terminal in response to the detection result indicating that the cloud desktop client has no problem.

[0010] The method as described above further comprises: updating the image containing the second operating system from the server in response to the image containing the second operating system on the terminal having a problem.

[0011] The method as described above further comprises: restoring the second operating system on the terminal based on the image containing the second operating system on the terminal and incremental data of the specified location of the server.

[0012] The method as described above further comprises: closing the cloud desktop client in the first operating system; and determining that the fault originates from the first operating system in response to the fault still existing after the cloud desktop client is closed.

[0013] The method as described above further comprises: reporting the fault to a cloud desktop administrator, wherein the cloud desktop administrator is not the party responsible for the maintenance of the terminal.

[0014] The method as described above further comprises: recording a log of a troubleshooting process of the fault on the server in response to the fault originating from the second operating system.

[0015] The method for handling a cloud desktop client fault according to the present application can avoid waste of user terminal warranty resources, and can also reduce the work intensity of a cloud desktop administrator, thereby improving the promotion and use experience of a cloud desktop system. BRIEF DESCRIPTION OF DRAWINGS

[0016] Hereinafter, preferred embodiments of the present application will be described in further detail with reference to the accompanying drawings, in which:

[0017] Figure 1 is a structural schematic diagram of a cloud desktop system according to an embodiment of the present application;

[0018] Figure 2 is a structural schematic diagram of a terminal according to an embodiment of the present application;

[0019] Figure 3is a flowchart of a cloud desktop system client according to an embodiment of the present application;

[0020] Figure 4 is a flowchart of a server of a cloud desktop system according to an embodiment of the present application; and

[0021] Figure 5 is a flowchart of a cloud desktop client fault handling according to an embodiment of the present application. DETAILED DESCRIPTION

[0022] In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be described clearly and completely below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are some but not all of the embodiments of the present application. Based on the embodiments in the present application, all other embodiments obtained by a person of ordinary skill in the art without creative work fall within the protection scope of the present application.

[0023] In the following detailed description, reference can be made to the various drawings that form a part of the present disclosure and are illustrative of specific embodiments of the present application. In the drawings, like numerals describe substantially similar components throughout the several views. Various specific embodiments of the present application are described in sufficient detail below to enable a person of ordinary skill in the relevant art to practice the technical solutions of the present application. It should be understood that other embodiments or structural, logical or electrical changes to the embodiments of the present application can also be utilized.

[0024] The present application proposes a cloud desktop system based on IDV. A computer terminal obtains virtualization configuration from the cloud through a virtualization application running on a local operating system and simulates corresponding hardware. Secondary virtualization is performed based on the simulated hardware to distribute cloud desktops through an IDV framework, thereby realizing a full-network cloud desktop system. Since the number of virtualization configuration types is controllable, cloud desktop maintenance work on the cloud will be predictable. This will promote the arrangement and promotion of the cloud desktop system in existing computer networks.

[0025] Figure 1 is a structural diagram of a cloud desktop system according to an embodiment of the present application. As shown in the figure, the cloud desktop system 100 includes a server 101 and a plurality of terminals 102-107 connected thereto. The terminals 102 and 103 are in a first local area network, and the terminals 104 and 105 are in a second local area network; and the terminals 102 and 103 are not in the same local area network as the terminals 104 and 105. The terminals 106 and 107 are connected to the server 101 through VPNs, respectively.

[0026] In some embodiments, the server 101 comprises one or more processors, memories, and communication interfaces. The processors can be coupled to the memories and the communication interfaces through a high-speed bus. The processors comprise one or more central processing units (CPUs), graphics processing units (GPUs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or combinations thereof. The processors can execute software or computer-readable instructions stored in the memories to perform the methods or operations described herein. The memories can store software, data, logs, or combinations thereof. The memories can be internal memories or external memories. Examples of the internal memories include disk memories, flash memories, non-volatile random access memories (NVRAMs), and the like. Examples of the external memories include memories residing on storage nodes, cloud servers, or storage servers. Examples of the communication interfaces include network interface cards, modems, and the like. The server 101 can connect to the first local area network and the second local area network using the communication interfaces, and communicate with the terminals 102-105 respectively residing therein. The server can also communicate with the terminals 106 and 107 residing in the external network using the communication interfaces through VPN protocols.

[0027] In some embodiments, any of the terminals 102-107 comprises a first processor, a first RAM, a first I / O device, a first display, and a first keyboard and a first mouse. The first I / O device can comprise a first hard disk and a second network interface card. All of the above devices are physical facilities of the respective terminals. As understood, the terminals 102-107 are configured to run a first operating system, i.e., a local operating system. The operating systems include, but are not limited to, Windows, Linux, Mac OS, IOS, or Android, or other operating systems based on these operating systems, such as Kylin, Red Flag Linux, AliOS (originally Yun OS), Harmony OS, and the like. Many of the terminals 102-107 already include the first operating system when purchased. In some cases, the maintenance services of the hardware of the terminals 102-107 and the first operating system, etc. can also be independently provided by brand service providers or other institutions of the terminals 102-107. Therefore, in some embodiments, the maintenance of the cloud desktop system does not necessarily include the maintenance work of the hardware of the terminals 102-107 and the first operating system.

[0028] In some embodiments, any of the terminals 102-107 further comprises a first virtualization layer, a second virtualization layer, and a cloud desktop. The first virtualization layer is generated by virtualization in the first operating system, which includes a plurality of virtual hardware: a second processor, a second RAM, a second I / O device, a second display, and a second keyboard and a second mouse; wherein the second I / O device can include a second hard disk and a second network interface card; it can be the same as the first processor, the first RAM, the first I / O device, the first display, and the first keyboard and the first mouse, or it can be different from them. The second virtualization layer is a virtualization software running on the virtual hardware of the first virtualization layer. Under the IDV framework, the virtualization software of the second virtualization layer is similar to the local virtualization software of the IDV, and provides support for the cloud desktop on it. The difference is that in the present application, the IDV virtualization software is running on each virtualization hardware of the first virtualization layer. The cloud desktop is the second operating system running on the terminal, which includes but is not limited to Windows, Linux, Mac OS, IOS or Android or other operating systems based on these operating systems, such as Kylin, Red Flag Linux, AliOS (formerly Yun OS), Harmony OS, etc.

[0029] The secondary virtualization of the terminal provides great flexibility for the cloud desktop system. Although it has undergone secondary virtualization, the loss of local computing performance is not great. Moreover, under the same framework, the performance of the local terminal can also be improved. In some embodiments, if the hardware of the terminal itself, such as the first processor, the first RAM, etc., does not support the virtualization software under the IDV framework, the first virtualization layer can improve the first processor, the first RAM, etc. through virtualization means and support the improvement of the client through the resources of the server 101. For example, the first processor of the terminal is an Intel i3 processor before 2016 and does not support Intel Broadwell, which cannot run the IDV framework. The first virtualization layer can set the virtual second processor to Intel i5-5675C through virtualization means, and achieve the required computing power through the computing resources of the server side. This not only enables the IDV framework to be easily installed and run on old terminals, but also substantially improves the user experience of the terminal.

[0030] The secondary virtualization of the terminal also relieves the burden of the maintenance of the cloud desktop system. Since the virtual hardware configuration is distributed by the server, the number of terminal images can be controlled from the server side. Therefore, the maintenance work of the cloud desktop system can be greatly reduced, and the actual operation cost of the cloud desktop system can be reduced.

[0031] The server runs cloud management platform software to provide management functions for the cloud desktop system. In some embodiments, the server includes an image library 110 and a cloud desktop management module 112; wherein the image library 110 stores one or more terminal-related images. In some embodiments, multiple terminals may correspond to one image. Reducing the number of images can alleviate the maintenance work required for the images. In other embodiments, the image library 110 includes a base image and multiple incremental images. The base image corresponds to a virtual hardware configuration. Different base images exist for different virtual hardware configurations. The incremental images correspond to terminals. Each terminal has an incremental image in the image library. The incremental images store personalized updates of the terminal based on the base image. A smaller number of base images reduces the maintenance workload and provides flexibility in terminal personalization settings.

[0032] The cloud desktop management module 112 provides management functions for the cloud desktop system. In some embodiments, the cloud desktop management module 112 provides management of images in the image library, including but not limited to: creating new images, binding images to terminals, updating and deleting images, etc. In some embodiments, the cloud desktop management module 112 provides management of terminals, including but not limited to: adding and deleting terminals, configuring networks, setting management policies, data backup and recovery, etc. These functions are similar to the management functions in the existing IDV framework, and will not be described in detail here.

[0033] Unlike existing IDV frameworks, the cloud desktop management module 112 also provides virtual configuration management functions. The cloud desktop management module receives virtual configuration requests from the terminal. The virtual configuration request includes at least the terminal's hardware configuration: a first processor, first RAM, a first I / O device, a first display, and a first keyboard and a first mouse, etc. The cloud desktop management module selects a suitable virtual configuration from a pool of existing virtual configurations and sends the virtual configuration to the terminal. As understood, the virtual configuration may have lower or higher computing and storage capabilities than the terminal's hardware configuration. To maximize the use of the terminal's local computing and storage resources while conserving cloud computing and storage resources, the computing and storage capabilities of the virtual configuration are generally lower than those of the terminal's hardware configuration.

[0034] In some embodiments, the server further includes a security authentication service module 114. The security authentication service module 114 provides access services between the terminal and the server; these include, but are not limited to, user services, login authentication services, transmission encryption services, and flow control services. These functions are similar to those in existing IDV frameworks and will not be described in detail here.

[0035] In some embodiments, the server further includes a cloud computing management module 116 and a cloud resource management module 118. When the computing or storage capabilities provided by the terminal's hardware are insufficient, a virtual second processor, second RAM, or second I / O, etc., utilizes the cloud computing and storage capabilities provided by the server to provide services to the terminal. Therefore, the server needs to provide corresponding resources according to the virtual configuration to support cloud computing and storage. Furthermore, the server itself also needs computing and storage resources to manage multiple terminals and provide corresponding cloud services. The cloud computing management module 116 and the cloud resource management module 118 provide and allocate the resources required for cloud computing and storage and manage the cloud computing.

[0036] Figure 2 This is a schematic diagram of the system architecture of a terminal according to an embodiment of the present invention. As shown in the figure, the terminal includes a five-layer structure: a basic hardware layer, a local operating system layer, a first virtualization layer, a second virtualization layer, and a cloud desktop layer. The basic hardware layer refers to the hardware possessed by the terminal, including a first processor, a first RAM, a first I / O device, a first display, a first keyboard, and a first mouse, etc. The local operating system layer (i.e., the first operating system) refers to the local operating system running on the basic hardware layer, which can be Windows, Linux, Mac OS, iOS, or Android, or other operating systems based on these operating systems, such as Kylin, Red Flag Linux, AliOS (formerly Yun OS), Harmony OS, etc.

[0037] In some embodiments, the terminal can run the client of the cloud desktop system of the present invention at the local operating system layer by installing software or an APP. As understood, the client of the present invention is provided in different forms depending on the local operating system. For example, an installation package for Windows, a dmg or pkg file for Mac OS, an apk file for Android, etc. The terminal can obtain the client of the cloud desktop system by downloading from a website or other means; and install it on the terminal's local operating system.

[0038] Through the cloud desktop system client, the terminal can communicate with the server and obtain virtual hardware settings allocated by the server, and virtualize the corresponding hardware on top of the terminal's local operating system. These virtual hardware components form the first virtualization layer, including: a second processor, a second RAM, a second I / O device, a second display, a second keyboard, and a second mouse, etc.

[0039] The terminal deploys the IDV framework on top of the virtual hardware of the first virtualization layer to remotely run cloud desktops. As is understood, a second virtualization layer, the hypervisor, is set up above the first virtualization layer. The hypervisor runs directly on the virtual hardware, providing the drivers required by the virtual hardware, or at least the CPU, interrupt (terminal), and RAM drivers, such as XEN. Because the hypervisor can run directly on the virtual hardware, although it is still virtualization, the performance loss is relatively small, ensuring operational reliability. The hypervisor manages the second operating system running on it. The second operating system can be Windows, Linux, Mac OS, iOS, or Android, or other operating systems based on these, such as Kylin, Red Flag Linux, AliOS (formerly Yun OS), Harmony OS, etc. The second virtualization layer and the second operating system layer are similar in technology to existing IDV frameworks, and will not be elaborated further here.

[0040] Figure 3 This is a schematic diagram of the operation flow of a cloud desktop system client according to an embodiment of the present invention. As shown in the figure, after the cloud desktop system client is installed on the local operating system of the terminal, the cloud desktop system client runs and executes the following steps: In step 310, the hardware configuration of the terminal is obtained, namely, a first processor, a first RAM, a first I / O device, a first display, a first keyboard, and a first mouse, etc. In step 320, the terminal hardware configuration is sent to the server. These hardware configurations include at least the first processor and the first RAM. In some embodiments, these configurations also include the first I / O device. As understood, the hardware configuration of the terminal sent to the server may also include other hardware, such as a display, a printer, a scanner, etc.

[0041] In step 330, a virtual hardware configuration is received from the server. The virtual hardware configuration includes at least a second processor and a second RAM. In some embodiments, the virtual hardware configuration also includes a second I / O device. As understood, the virtual hardware configuration sent to the terminal may also include other virtual hardware, such as a display, printer, scanner, etc. After receiving the hardware configuration from the terminal, the server first determines whether the terminal's hardware configuration can run the cloud desktop system and the performance of running the cloud desktop system. Therefore, the server determines whether the terminal's hardware configuration needs to be upgraded, i.e., whether it needs to utilize cloud computing resources to improve the terminal's operating experience. If computing power needs to be upgraded, the server determines the processor type and RAM quantity to be assigned to the terminal after the upgrade. Next, the server determines the virtual hardware configuration allocated to the terminal based on the terminal's hardware configuration and the processor type and RAM quantity specified if an upgrade is needed. A similar approach can be used for other types of terminal hardware that need upgrading, such as storage space.

[0042] In some embodiments, the server maintains a certain number of virtual hardware configurations. The server allocates one virtual hardware configuration to the terminal based on the terminal's hardware configuration and a specified processor type and amount of RAM. As understood, each virtual hardware configuration corresponds to a different image. This allows the server to maintain a controllable number of images.

[0043] In step 340, based on the virtual hardware configuration, the corresponding virtual hardware is simulated on the terminal. The cloud desktop system client has the ability to simulate hardware using software. This function of the cloud desktop system client is similar to that of VMware Workstation or VisualBox, i.e., generating virtual hardware through software. In some embodiments, when server computing resources are not required, communication for the virtual hardware is transferred to the local operating system and then executed by the local hardware. In other embodiments, when server computing resources are needed, communication for the virtual processor and RAM is sent to the server and the computation results are received from the server. When server storage resources are needed, communication for storage, such as read / write requests to the hard disk, is sent to the server and the read / write results are received from the server.

[0044] In step 350, the IDV framework client is configured based on the virtual hardware configuration. In some embodiments, a hypervisor, such as XEN, is installed on top of the virtual hardware. Then, the IDV cloud desktop client is installed on the terminal via the hypervisor. A suitable second operating system, i.e., the cloud desktop, is selected according to the needs of the terminal. This achieves two virtualizations on the terminal and the operation of the cloud desktop. In this step, the process is similar to existing IDV framework client setup methods and will not be described in detail here.

[0045] Figure 4 This is a flowchart illustrating the server process of a cloud desktop system according to an embodiment of the present invention. As shown, the server process of the cloud desktop system includes the following steps: In step 410, the server receives hardware configuration data from a terminal. As previously described, the terminal hardware configuration includes: a first processor, a first RAM, a first I / O device, a first display, a first keyboard, and a first mouse, etc. In step 420, the server determines whether the terminal's hardware configuration needs to be upgraded. In some embodiments, the server determines whether the terminal meets the conditions for running the IDV framework. If the terminal's computing power or processor type, etc., does not meet the conditions for installing the IDV framework client, the server will upgrade the terminal's computing power. In some embodiments, if the terminal's storage capacity is insufficient, for example, if the storage space is too small, the server will upgrade the terminal's storage capacity. In some embodiments, in step 430, the server determines whether the performance experience provided by the terminal meets the minimum standards. These performance experiences include, but are not limited to, the terminal's waiting time for performing some tasks, the terminal's graphics or video rendering capabilities, and the terminal's storage capacity, etc. If the server determines that the performance experience provided by the terminal does not meet the minimum standards, the server will upgrade the terminal's computing power and / or storage capacity.

[0046] In step 440, the server determines the computing power and / or storage capacity to be provided to the terminal. In some embodiments, if the computing power of the terminal is to be increased, the server determines the processor type and RAM size of the virtual terminal. For example, the server determines the processor type and RAM based on the minimum hardware requirements or minimum performance experience for running the IDV framework. If the storage capacity of the terminal is to be increased, the server determines the size of the cloud storage space to be provided. For example, cloud storage space is allocated to the terminal according to its needs.

[0047] In step 450, the server determines the virtual hardware configuration of the terminal. In some embodiments, the server's image library stores multiple images. Each image corresponds to multiple virtual hardware configurations. In other embodiments, the images in the image library include base images and incremental images. The base image corresponds to a virtual hardware configuration. Thus, the server includes multiple virtual hardware configurations. In some embodiments, the server compares the terminal's hardware configuration with the multiple virtual hardware configurations and assigns the virtual hardware configuration that is closest to the terminal's hardware configuration to the terminal. In some embodiments, the CPU processing power in the virtual hardware configuration is less than or equal to the CPU processing power in the terminal hardware. The RAM size in the virtual hardware configuration is equal to the RAM size in the terminal hardware. The disk space size in the virtual hardware configuration is equal to the disk space size in the terminal hardware. Of course, the virtual RAM and disk space sizes can also be slightly smaller than the terminal RAM and disk space sizes. Generally, the virtual CPU processing power, RAM, and disk space sizes will not exceed the terminal CPU processing power, RAM, and disk space sizes.

[0048] In some embodiments, the server replaces the terminal's corresponding hardware with enhanced computing and / or storage capabilities, and then compares it with multiple virtual hardware configurations to determine the virtual configuration allocated to the terminal. Since the terminal's computing and / or storage capabilities are enhanced, and these enhanced capabilities correspond to the computing and / or storage capabilities in the existing multiple virtual configurations, the corresponding virtual hardware configuration can be easily determined after the terminal's computing and / or storage capabilities are enhanced.

[0049] In some embodiments, if a suitable virtual hardware configuration for a terminal is not available on the server, a new virtual hardware configuration can be created on the server, and a corresponding image can be created in the image library. The newly created virtual hardware configuration is then assigned to the terminal. If the terminal's computing power and / or storage capacity exceeds the existing virtual hardware configuration on the server, a new virtual hardware configuration is created, thus ensuring that the terminal's computing power and / or storage capacity are not underutilized.

[0050] In step 460, an image associated with the terminal is specified. The server determines an image suitable for the terminal to run based on the terminal's computing power and / or storage capacity. In some embodiments, the server obtains the type of operating system required by the terminal and selects an image with the required operating system from the images suitable for the terminal. For example, if the terminal uses Windows XP, the server selects a Windows XP image or base image from the images corresponding to the terminal's virtual hardware configuration and specifies it to the terminal. The terminal then downloads the specified image and runs the Windows XP cloud desktop.

[0051] In some embodiments, the server manages the cloud desktop of a terminal remotely by managing a specified image. For example, the server can change the operating system used by the terminal by modifying the image assigned to the terminal. The server can add new software to the terminal's secondary operating system by installing new software from the image. The server can add new hardware to the secondary operating system by adding drivers for the terminal hardware from the image. The server can manage users using the terminal by configuring login information in the image. The server can manage the permissions of users using the terminal by configuring user permissions in the image. The server's management of each terminal's cloud desktop is similar to the management methods under the existing IDV framework, and will not be described in detail here.

[0052] This invention enables the distribution and management of cloud desktops by running the IDV framework on virtual hardware simulated on a computer terminal. In some embodiments of this invention, the number of images managed on the server can be effectively reduced, thereby alleviating the workload of cloud desktop maintenance and promoting the deployment and adoption of cloud desktop systems in existing computer networks. In some embodiments of this invention, the computing and / or storage capabilities provided by the server enhance the virtual hardware of the terminal, thereby ensuring the smooth operation of the cloud desktop system. This not only expands the applicability of cloud desktop systems but also improves the user experience.

[0053] However, malfunctions frequently occur when using cloud desktops on terminals. According to one embodiment of this application, a method for handling malfunctions when using a cloud desktop client is also proposed, which will be described in detail below.

[0054] Figure 5 This is a flowchart illustrating cloud desktop client fault handling according to an embodiment of the present invention. As shown, the cloud desktop client fault handling process includes the following steps: In step 510, it is determined on the terminal whether the fault originates from the first operating system or the second operating system. In the fault handling design of the present invention, the cloud desktop system administrator is only responsible for faults in the second operating system, while faults in the first operating system are the responsibility of the local user. For example, if it is a branded terminal, the corresponding brand warranty service can be used. If the warranty period has expired, the terminal's organization can centrally procure warranty services. This will greatly reduce the workload of the cloud desktop system administrator. When a cloud desktop client malfunctions, it is first necessary to determine whether the fault is in the first operating system or the second operating system on the terminal, that is, whether the fault occurs in the terminal's own first operating system and the virtual second operating system, so that the corresponding handling procedure can be determined according to the different operating system faults.

[0055] In step 520, the cloud desktop client is shut down in the first operating system. In some embodiments, the server can directly shut down the cloud desktop client in the first operating system. In some embodiments, the server can also instruct the terminal to shut down the cloud desktop client in the first operating system. This can determine whether the source of the fault is the second operating system, that is, whether the virtual second operating system is experiencing a problem. The cloud desktop client in the first operating system is shut down on the terminal, and the changes in the fault are observed. In some embodiments, when the source of the fault is determined to be the second operating system, the fault needs to be reported to the cloud desktop administrator. After receiving the fault report, the cloud desktop administrator can also perform subsequent fault handling.

[0056] In step 521, it is determined whether the fault still exists. In some embodiments, after closing the cloud desktop client, the presence or absence of the fault can be used to determine whether the first operating system or the second operating system is faulty. If the fault disappears after closing the cloud desktop client, it can be considered that the second operating system is faulty; if the fault still exists after closing the cloud desktop client, it can be considered that the fault originates from the first operating system.

[0057] In step 522, the cloud desktop client is detected. In some embodiments, if the fault disappears after the cloud desktop client is closed in step 521, it is considered that the second operating system is faulty. The location of the fault is then investigated, starting with automatically detecting whether the cloud desktop client itself has a problem. In some embodiments, the terminal can directly detect the cloud desktop client on it. In some embodiments, the terminal can also send a detection request to the server, which will then detect the terminal's cloud desktop client and display the detection results.

[0058] In step 523, it is determined whether the cloud desktop client itself has a problem. In some embodiments, the problem can be determined based on the detection results. If the detection results determine that the cloud desktop client has a problem, the fault can be considered to be caused by the cloud desktop client; if the detection results determine that the cloud desktop client does not have a problem, other parts need to be investigated further.

[0059] In step 524, the cloud desktop client is updated from the server. In some embodiments, if a problem is detected and determined in step 523, the cloud desktop client is automatically updated from the server (e.g., the latest version of the cloud desktop client is downloaded), thus completing the detection and handling of the fault, and proceeding to step 528.

[0060] In step 525, the image of the second operating system on the terminal is detected. In some embodiments, if the cloud desktop client is determined to have no problems in step 523, the troubleshooting continues, and the image of the second operating system on the terminal is automatically checked. In some embodiments, the terminal can directly detect the image of the second operating system on it. In some embodiments, the terminal can also send a detection request to the server, which will detect the image of the terminal's second operating system and display the detection results.

[0061] In step 526, it is determined whether the image of the second operating system on the terminal itself has a problem. In some embodiments, the problem of the image of the second operating system can be determined based on the detection in step 525. When the detection result determines that the image of the second operating system has a problem, it can be considered that the fault is caused by the image of the second operating system; and when the detection result determines that the image of the second operating system does not have a problem, it can be determined that the fault originates from the first operating system.

[0062] In step 527, the image of the second operating system is updated from the server. In some embodiments, if the detection result in step 526 determines that there is a problem with the image of the second operating system on the terminal, the image of the second operating system is automatically updated from the server, thus completing the detection and handling of the fault, and then proceeding to step 528.

[0063] In some embodiments, when a problem is detected with the image of the second operating system on the terminal, the second operating system of the terminal can also be restored. In some embodiments, the restoration of the second operating system of the terminal can be based on the image of the second operating system on the terminal and specified incremental data. In some embodiments, the incremental data is user behavior data of the user using the second operating system or cloud desktop client, which may be stored on a server or on the terminal. By specifying the incremental data, the second operating system can be restored to a specified stage, allowing the user to continue using the second operating system without affecting the user's usage records before the failure.

[0064] In step 528, the troubleshooting process is logged on the server. In some embodiments, when the fault originates from a second operating system, and after the fault is detected and handled, relevant records are archived on the server. In some embodiments, the troubleshooting process may also be reported to the cloud desktop administrator.

[0065] In step 530, the fault is reported to the maintenance party responsible for the terminal. In some embodiments, when the fault originates from the first operating system, it is considered that the terminal itself has a problem or fault (e.g., hardware damage to the terminal or a problem with the operating system), and the fault is reported to the maintenance party responsible for the terminal. In some embodiments, the maintenance party responsible for the terminal is not the cloud desktop administrator. In some embodiments, the maintenance party responsible for the terminal can be the terminal's maintenance service provider (e.g., the terminal brand service provider or other organization).

[0066] The cloud desktop client fault handling method of this application can determine the source of the fault when a user encounters a fault while using the cloud desktop client, and take corresponding actions based on the determined source of the fault. In this way, when the primary operating system of the terminal fails, it can be handled using the warranty provided by the terminal maintenance service provider, avoiding waste of resources; and when the secondary operating system of the terminal fails, it can be reported to the cloud desktop administrator for corresponding handling. Thus, the cloud desktop administrator only needs to handle the relevant issues of the secondary operating system failure, greatly reducing the workload of the cloud desktop administrator.

[0067] The above embodiments are for illustrative purposes only and are not intended to limit the invention. Those skilled in the art can make various changes and modifications without departing from the scope of the invention. Therefore, all equivalent technical solutions should also fall within the scope of the invention.

Claims

1. A method for cloud desktop client failure handling, wherein the cloud desktop client comprises a base hardware layer of a terminal; a first operating system layer configured to run on the terminal; a first virtualization layer comprising a plurality of virtual hardware emulated on the first operating system layer. a second virtualization layer including a hypervisor on the plurality of virtual hardware bases; and a cloud desktop including a second operating system managed by the hypervisor; the method comprising: determining on the terminal whether the fault originates from the first operating system or the second operating system; in response to the fault originating from the second operating system, closing the cloud desktop client in the first operating system; and in response to the fault originating from the first operating system, reporting the fault to a maintenance party responsible for the terminal.

2. The method of claim 1, further comprising: detecting the cloud desktop client in response to the fault being eliminated after the cloud desktop client is closed.

3. The method of claim 2, further comprising: sending a detection request to a server to detect the cloud desktop client on the terminal through the server and displaying a detection result.

4. The method of claim 3, further comprising: in response to the detection result being that there is a problem with the cloud desktop client, updating the cloud desktop client from the server.

5. The method of claim 4, further comprising: in response to the detection result being that there is no problem with the cloud desktop client, detecting an image including the second operating system on the terminal.

6. The method of claim 5, further comprising: in response to the image including the second operating system on the terminal having a problem, updating the image including the second operating system from the server.

7. The method of claim 5, further comprising: restoring the second operating system on the terminal based on the image including the second operating system on the terminal and incremental data of a specified location of the server.

8. The method of claim 1, further comprising: closing the cloud desktop client in the first operating system; in response to the fault still existing after the cloud desktop client is closed, determining that the fault originates from the first operating system.

9. The method of claim 1, further comprising: reporting the fault to a cloud desktop administrator, wherein the cloud desktop administrator is not the maintenance party responsible for the terminal.

10. The method of claim 1, further comprising: in response to the fault originating from the second operating system, recording a log of a troubleshooting process of the fault on a server.

Images