Cloud desktop management method, device, equipment, storage medium and program product

Abstract

The application discloses a cloud desktop management method, device, equipment, storage medium and program product. The method comprises the following steps: in the case that a resource access request of a cloud desktop is received, target identity information in the resource access request is acquired; in the case that the target identity information is verified, the resource access request is parsed to obtain identification information, the identification information is used for identifying a cloud desktop type corresponding to the resource access request; and the resource access request is sent to a third-party desktop management system corresponding to the cloud desktop type. According to the embodiment of the application, the resource management efficiency of multiple cloud desktops can be improved, and the resource management cost is reduced.

Description

Technical Field

[0001] This application belongs to the field of cloud platform technology, and in particular relates to a cloud desktop management method, device, equipment, storage medium and program product. Background Technology

[0002] With the rapid development and application of internet technology, various advanced information technologies have emerged, leading to a gradual increase in the level of IT application. In order to save costs, individuals and organizations are increasingly choosing to use cloud desktops instead of traditional physical machines, based on their specific needs.

[0003] Cloud desktops utilize virtualization technology to virtually realize the physical devices of computers, thereby effectively improving the utilization rate of physical resources and helping tenants save a lot of costs.

[0004] However, current cloud desktop application implementation solutions all use a single virtualization technology to build the cloud desktop management platform. The cloud desktop vendors provide their own virtualization technology stack, which cannot use the enterprise's existing virtualization environment. If an enterprise purchases cloud desktops from multiple cloud vendors, each vendor's cloud desktop has an independent virtualization technology stack, as well as an independent application and operation and maintenance interface. Therefore, it is impossible to manage the resources of multiple cloud desktops in a unified manner, which greatly increases the resource management cost. Summary of the Invention

[0005] This application provides a cloud desktop management method, apparatus, device, storage medium, and program product, which can solve the problem of high resource management costs in existing cloud desktops.

[0006] In a first aspect, embodiments of this application provide a cloud desktop management method, the method comprising:

[0007] Upon receiving a resource access request from the cloud desktop, obtain the target identity information from the resource access request;

[0008] If the target identity information is verified, the resource access request is parsed to obtain identification information, which is used to identify the cloud desktop type corresponding to the resource access request.

[0009] The resource access request is sent to the third-party desktop management system corresponding to the cloud desktop type.

[0010] In some embodiments, sending the resource access request to a third-party desktop management system corresponding to the cloud desktop type includes:

[0011] If the target identity information is verified, a verification token is added to the resource access request.

[0012] The resource access request with the added verification token is sent to the third-party desktop management system corresponding to the cloud desktop type.

[0013] In some embodiments, before parsing the resource access request to obtain the identification information after the target identity information has been verified, the method further includes:

[0014] Match the target identity information with a preset identity information database;

[0015] If an identity matching the target identity exists in the identity information database, the target identity is determined to have passed verification.

[0016] Secondly, embodiments of this application also provide a cloud desktop management method, the method comprising:

[0017] Receive resource access requests from a third-party desktop management system;

[0018] The resource access request is converted into target data, wherein the format of the target data conforms to the input parameter format required by the virtualization layer;

[0019] The target data is transmitted to the virtualization layer corresponding to the target data.

[0020] In some embodiments, converting the resource access request into target data includes:

[0021] Obtain the request header of the resource access request;

[0022] The request header is parsed to determine the request type of the resource access request;

[0023] The resource access request is converted into the target data according to the request type.

[0024] In some embodiments, after transmitting the target data to the virtualization layer corresponding to the target data, the method further includes:

[0025] Upon receiving feedback data of the target data, the feedback data is converted into standardized data, and the format of the standardized data conforms to the input parameter format required by the third-party desktop management system.

[0026] The standardized data is transmitted to the third-party desktop management system.

[0027] Thirdly, embodiments of this application provide a cloud desktop management device, the device comprising:

[0028] The acquisition module is used to acquire the target identity information in the resource access request when the cloud desktop is received;

[0029] The parsing module is used to parse the resource access request and obtain identification information when the target identity information is verified. The identification information is used to identify the cloud desktop type corresponding to the resource access request.

[0030] The sending module is used to send the resource access request to the third-party desktop management system corresponding to the cloud desktop type.

[0031] Fourthly, embodiments of this application provide a cloud desktop management device, the device including: a processor and a memory storing computer program instructions;

[0032] The processor implements the cloud desktop management method described above when executing computer program instructions.

[0033] Fifthly, embodiments of this application provide a computer storage medium storing computer program instructions, which, when executed by a processor, implement the cloud desktop management method described above.

[0034] Sixthly, embodiments of this application provide a computer program product, the computer program product including computer program instructions, which, when executed by a processor, implement the cloud desktop management method described above.

[0035] In this application, when the unified desktop management system receives a resource access request from a cloud desktop, it obtains the target identity information in the resource access request, verifies the target identity information, and if the target identity information is verified, it parses the resource access request to obtain the identification information that identifies the cloud desktop type, and then sends the resource access request to the third-party desktop management system corresponding to the cloud desktop type.

[0036] In this way, the unified desktop management system can uniformly verify resource access requests and allocate them to the corresponding third-party desktop management system. This means that the resources of multiple cloud desktops can be uniformly managed and allocated, ensuring that each tenant's resource access request can be quickly verified and allocated to the corresponding cloud desktop. This improves the efficiency of resource management across multiple cloud desktops and reduces resource management costs. Attached Figure Description

[0037] To more clearly illustrate the technical solutions of the embodiments of this application, the drawings used in the embodiments of this application will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0038] Figure 1 This is a flowchart illustrating a cloud desktop management method provided in an embodiment of this application;

[0039] Figure 2 This is a flowchart illustrating a cloud desktop management method provided in another embodiment of this application;

[0040] Figure 3 This is a flowchart illustrating a cloud desktop management method according to another embodiment of this application;

[0041] Figure 4 This is a schematic diagram of the structure of a cloud desktop management device provided in an embodiment of this application;

[0042] Figure 5 This is a schematic diagram of the hardware structure of a cloud desktop management device provided in an embodiment of this application;

[0043] Figure 6 This is a schematic diagram of the structure of a cloud desktop management device provided in an embodiment of this application. Detailed Implementation

[0044] The features and exemplary embodiments of various aspects of this application will be described in detail below. To make the objectives, technical solutions, and advantages of this application clearer, the application will be further described in detail below with reference to the accompanying drawings and specific embodiments. It should be understood that the specific embodiments described herein are only intended to explain this application and not to limit it. For those skilled in the art, this application can be implemented without some of these specific details. The following description of the embodiments is merely to provide a better understanding of this application by illustrating examples of this application.

[0045] It should be noted that, in this document, relational terms such as "first" and "second" are used merely to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising..." does not exclude the presence of additional identical elements in the process, method, article, or apparatus that includes the element.

[0046] It should be noted that, unless otherwise specified, the embodiments and features described in this application can be combined with each other. The embodiments will now be described in detail with reference to the accompanying drawings.

[0047] In existing technologies, the use of virtualization technology is relatively limited, which may lead to the following problems:

[0048] First, mainstream desktop cloud products on the market generally adopt a deployment and management approach that tightly couples various product components such as virtualization resource management, desktop management, and transmission protocols. Product deployment requires the construction of a dedicated Infrastructure as a Service (IaaS) layer resource pool to manage applications. The resource and network environment planning is relatively closed, making it impossible to achieve rapid deployment in a private cloud.

[0049] Secondly, based on the current division of labor among enterprise terminals and security management requirements, enterprises usually adopt cloud desktops from multiple cloud vendors. If an enterprise purchases cloud desktops from multiple cloud vendors, each vendor's cloud desktop has an independent virtualization technology stack, requiring the introduction of multiple sets of desktop cloud products for independent deployment and construction. Desktop resources cannot be managed uniformly, resulting in high management costs.

[0050] Secondly, the phased construction of desktop cloud and the independent deployment and decentralized management of products from different manufacturers result in inconsistent user experiences because desktop resources cannot be flexibly allocated across departments and scenarios. Furthermore, the network interconnection strategy for tenant desktop access applications is complex and requires separate implementation by desktop vendors, which cannot be automatically configured from the resource pool cloud management platform, leading to high operational complexity.

[0051] To address the aforementioned issues, this application proposes a cloud desktop management method. Through an adaptation layer module and a unified data model compatible with multiple virtualization platforms, it achieves unified adaptation and compatibility across multiple virtualization cloud platforms. Combined with a unified desktop management platform, it ultimately realizes integrated management of cloud desktop resources.

[0052] Specifically, in order to address the problems of the prior art, embodiments of this application provide a cloud desktop management method, apparatus, device, storage medium, and program product. The cloud desktop management method provided in this application embodiment will be described first below.

[0053] Figure 1 A flowchart illustrating a cloud desktop management method according to an embodiment of this application is shown. The method is applied to a unified desktop management system and includes the following steps:

[0054] S110, upon receiving a resource access request from the cloud desktop, obtain the target identity information from the resource access request.

[0055] In this embodiment, a unified desktop management system can be set up between users and third-party desktop management systems from various vendors. This serves two purposes: firstly, it shields the differences in resource request, management, and operation between different vendors' third-party desktop management systems; secondly, it decouples cloud desktop deployment management from the virtualization cloud platform, so that cloud desktop deployment management no longer depends on the functionality of the virtualization cloud platform. This decoupling reduces the complexity of cloud desktop deployment management, separates the responsibilities of cloud desktop deployment management and the virtualization cloud platform, and improves the system's reliability and maintainability.

[0056] Specifically, when a user wants to access resources on the cloud desktop, they send a resource access request to the unified desktop management system. This request requests access to resources that the cloud desktop can run. These resources can include applications, storage files, and data that the cloud desktop can run.

[0057] Furthermore, the resource access request includes the user's target identity information. The unified desktop management system can obtain the user's target identity information from the resource access request and verify the user's target identity information. Only when the user's target identity information is verified will the resource access request be responded to, allowing the user to access the resource; otherwise, the resource access request can be shelved.

[0058] S120, if the target identity information is verified, the resource access request is parsed to obtain identification information, which is used to identify the cloud desktop type corresponding to the resource access request.

[0059] In this embodiment, the unified desktop management system does not replace the third-party management systems of various vendors. Instead, it performs unified verification of resource access requests before the third-party management systems, and sends the resource access requests to the corresponding third-party desktop management system after successful verification.

[0060] Specifically, different resource access requests correspond to resources on different cloud desktops, and the resource access requests include identification information. This identification information identifies the type of cloud desktop corresponding to the resource requested for access. The identification information can be composed of strings, with different strings corresponding to different cloud desktop types.

[0061] S130, the resource access request is sent to the third-party desktop management system corresponding to the cloud desktop type.

[0062] In this embodiment, since the third-party desktop management system can only transmit resource access requests with matching types to the next level, after the third-party desktop management system parses the resource access request to obtain the identification information, it can determine the type of cloud desktop that the resource access request wants to access through the identification information, and send the resource access request to the third-party desktop management system corresponding to the cloud desktop type, and then the third-party desktop management system transmits the resource access request to the virtualization layer.

[0063] It is worth noting that third-party desktop management systems are management systems configured by each vendor. This application does not require any changes to the original third-party desktop management system. It only needs to set up a unified desktop management system at the user interface layer for user target identity information verification and resource access request allocation to achieve unified management of cloud desktops from different vendors.

[0064] This application obtains the target identity information in the resource access request when the unified desktop management system receives the resource access request from the cloud desktop, verifies the target identity information, and if the target identity information is verified, parses the resource access request to obtain the identification information that identifies the cloud desktop type, and sends the resource access request to the third-party desktop management system corresponding to the cloud desktop type.

[0065] In this way, the unified desktop management system can uniformly verify resource access requests and allocate them to the corresponding third-party desktop management system. This means that the resources of multiple cloud desktops can be uniformly managed and allocated, ensuring that each tenant's resource access request can be quickly verified and allocated to the corresponding cloud desktop. This improves the efficiency of resource management across multiple cloud desktops and reduces resource management costs.

[0066] As an optional embodiment, sending the resource access request to the third-party desktop management system corresponding to the cloud desktop type includes:

[0067] If the target identity information is verified, a verification token is added to the resource access request.

[0068] The resource access request with the added verification token is sent to the third-party desktop management system corresponding to the cloud desktop type.

[0069] In this embodiment, a verification token is a data structure used to represent identity and access permissions, typically used for authentication and authorization between users and the management system. The format and content of the verification token are usually defined by the management system and can be any string or an encrypted digital signature to prevent tampering. The validity period of a verification token is usually limited to ensure security.

[0070] As an optional implementation, the verification token can be a Token. During the login process, the user first submits target identity information to the unified desktop management system. This target identity information can be a username and password. The unified desktop management system authenticates the target identity information. If the authentication is successful, the server generates a Token, attaches it to the resource access request, and sends it back to the client. The Token attached to the resource access request proves that the request has been authenticated.

[0071] Next, the client will send the resource access request with the added token to the third-party desktop management system corresponding to the identification information. The third-party desktop management system does not need to verify the resource access request again. Once it is determined that the resource access request contains a token, it can be determined which resource the client is allowed to access.

[0072] The above method enables single sign-on, meaning that once a user's identity information is successfully verified, they can log in again within a certain period without needing to re-enter the authentication information. This verification method helps reduce the number of login attempts required by users, improves user experience, and protects user authentication information.

[0073] As an optional embodiment, before parsing the resource access request to obtain the identification information after the target identity information has been verified, the method further includes:

[0074] Match the target identity information with a preset identity information database;

[0075] If an identity matching the target identity exists in the identity information database, the target identity is determined to have passed verification.

[0076] In this embodiment, the target identity information can be a user's account. A unified account system can be established in the unified desktop management system to manage users. User management can include account management, tenant management, permission management, and single sign-on authentication.

[0077] Specifically, account management refers to the unified desktop management system providing users with a standard desktop account opening process interface. This interface can adapt to differences in application data from different cloud desktop vendors' business systems, ensuring the normal activation of desktop resources from each vendor. For applicant tenants, it masks the differences in account opening between different cloud desktop vendors, simplifies the tenant's operation process, and enables flexible allocation of desktop resources across departments and vendors.

[0078] When a user successfully registers in the unified desktop management system, the registered target identity information is stored in the identity information database. Therefore, during the subsequent login process, if the target identity information entered by the user matches the information in the identity information database, the user can be considered a pre-registered tenant, and thus the verification of the target identity information can be confirmed.

[0079] Furthermore, the unified cloud desktop management portal connects to cloud desktop management systems from different vendors through a unified standard application programming interface (API), ensuring compatibility with various vendors' cloud desktop management functions and providing centralized management and visual monitoring of resources such as desktops, peripherals, images, and policies. Unified operation and management is achieved through resource synchronization and resource interface integration, as detailed below:

[0080] Resource synchronization: The unified desktop management system calls the resource query interface of the third-party desktop management system in real time to obtain resource data such as desktop, peripherals, images, and policies, and performs audit management.

[0081] Resource Interface Integration: Based on resources, a unified display interface is designed according to the attribute characteristics of the corresponding resources. Information from cloud desktops from different vendors is integrated and differentiated through the technology stack. Complex management operations of cloud desktops from different vendors can be accessed through the corresponding cloud desktop management system, achieving both integration and relative independence.

[0082] With unified operation and management, desktop operation and management personnel can view and control all cloud desktop resources from all vendors on a single interface. This one-point access and one-point view of desktop resources improves the management capabilities and operation and maintenance efficiency of desktop resources.

[0083] As an optional embodiment, such as Figure 2 As shown, users can enter their identity information through the client's browser to request login to the unified desktop management system (hereinafter referred to as "unified desktop management"). The unified desktop management uses the authentication center of identity information to authenticate the user's identity information. If the authentication is successful, the unified desktop management issues a token to the user. The user can then send resource access requests carrying the token directly to the third-party desktop management system. The third-party desktop management system only needs to verify whether the token is valid. If the token is valid, it can directly respond to the resource access request.

[0084] Figure 3 A flowchart illustrating a cloud desktop management method according to an embodiment of this application is shown. The method is applied to a resource adaptation module and includes the following steps:

[0085] S310 receives resource access requests from third-party desktop management systems;

[0086] S320, the resource access request is converted into target data, wherein the format of the target data conforms to the input parameter format required by the virtualization layer;

[0087] S330, the target data is transmitted to the virtualization layer corresponding to the target data.

[0088] In this embodiment, because the input parameter format of the resource access request does not conform to the requirements of the virtualization layer, the virtualization layer cannot directly respond to the resource access request. Therefore, a resource adaptation module can be set up between the user interface layer and the virtualization layer. The resource adaptation module includes a first interface, a second interface, and a data converter. This resource adaptation module can realize the conversion of data parameter formats through a unified data converter, shielding the interface and data differences between different virtualization cloud platforms, and realizing the decoupling of cloud desktop deployment management from the virtualization cloud platform and unified docking for multi-cloud adaptation.

[0089] Specifically, the first interface connects to the third-party desktop management system, and the second interface connects to the virtualization layer. Both the first and second interfaces are connected to a data converter. The data converter can receive resource access requests from the third-party desktop management system through the first interface and convert the resource access requests into target data. The input parameter format of the target data is a customized format that the virtualization layer can respond to. After format conversion, the target data can be transmitted to the virtualization layer through the second interface, enabling the virtualization layer to respond to the target data.

[0090] As an optional embodiment, converting the resource access request into target data includes:

[0091] Obtain the request header of the resource access request;

[0092] The request header is parsed to determine the request type of the resource access request;

[0093] The resource access request is converted into the target data according to the request type.

[0094] In this embodiment, the virtualization layer includes multiple different open-source cloud computing management platforms, such as standard OpenStack and non-standard OpenStack, as well as other virtualization platforms. Each cloud computing management platform can respond with data input parameter formats that are different.

[0095] Therefore, in order to convert resource access requests into the correct input parameter format, it is necessary to determine the corresponding cloud computing management platform based on the request type of the resource access request, and then convert the resource access request into target data in a format that the cloud computing management platform can respond to. The request type can be obtained by parsing the request header of the resource access request.

[0096] As an optional embodiment, after transmitting the target data to the virtualization layer corresponding to the target data, the method further includes:

[0097] Upon receiving feedback data of the target data, the feedback data is converted into standardized data, and the format of the standardized data conforms to the input parameter format required by the third-party desktop management system.

[0098] The standardized data is transmitted to the third-party desktop management system.

[0099] In this embodiment, when the virtualization layer receives the target data converted from the resource access request, it can respond to the target data, obtain the resource requested by the resource access request, and encapsulate the resource into feedback data and send it to the resource adaptation module.

[0100] Since the feedback data generated by the virtualization layer does not conform to the input parameter format required by the third-party desktop management system, the feedback data also needs to be converted in the data converter to standardized data that conforms to the input parameter format required by the third-party desktop management system. The data converter then transmits the standardized data to the third-party desktop management system through the first interface.

[0101] As an optional embodiment, the overall technical architecture includes a unified desktop management system and a resource adaptation module, as follows: Figure 4 As shown, a unified desktop management system has been added to the existing cloud desktops and virtualization layers of various vendors for unified management of cloud desktops from multiple vendors. A resource adaptation module has also been added to convert data formats, shielding the data differences between the cloud desktop management system and the virtualization layer, thereby decoupling cloud desktop deployment management from the virtualization cloud platform and achieving unified multi-cloud adaptation and connection.

[0102] Based on the cloud desktop management method provided in the above embodiments, this application also provides specific implementations of a cloud desktop management device. Please refer to the following embodiments.

[0103] First see Figure 5 The cloud desktop management device 500 provided in this application embodiment includes the following modules:

[0104] The acquisition module 501 is used to acquire the target identity information in the resource access request when the cloud desktop is received;

[0105] The parsing module 502 is used to parse the resource access request and obtain identification information when the target identity information is verified. The identification information is used to identify the cloud desktop type corresponding to the resource access request.

[0106] The sending module 503 is used to send the resource access request to the third-party desktop management system corresponding to the cloud desktop type.

[0107] When a device receives a resource access request from a cloud desktop in the unified desktop management system, it can obtain the target identity information in the resource access request, verify the target identity information, and if the target identity information is verified, parse the resource access request to obtain the identification information that identifies the type of cloud desktop, and then send the resource access request to the third-party desktop management system corresponding to the type of cloud desktop.

[0108] In this way, the unified desktop management system can uniformly verify resource access requests and allocate them to the corresponding third-party desktop management system. This means that the resources of multiple cloud desktops can be uniformly managed and allocated, ensuring that each tenant's resource access request can be quickly verified and allocated to the corresponding cloud desktop. This improves the efficiency of resource management across multiple cloud desktops and reduces resource management costs.

[0109] As one implementation of this application, the above-mentioned acquisition module 503 may further include:

[0110] An adding unit is used to add a verification token to the resource access request if the target identity information is verified successfully.

[0111] The sending unit is used to send the resource access request with the added verification token to the third-party desktop management system corresponding to the cloud desktop type.

[0112] As one implementation of this application, the parsing module 502 may further include:

[0113] The matching unit is used to match the target identity information with a preset identity information database;

[0114] The verification unit is used to determine that the target identity information passes verification when there is identity information in the identity information database that matches the target identity information.

[0115] As one implementation of this application, the cloud desktop management device 500 may further include:

[0116] The receiving module is used to receive resource access requests from third-party desktop management systems.

[0117] A conversion module is used to convert the resource access request into target data, wherein the format of the target data conforms to the input parameter format required by the virtualization layer;

[0118] A transmission module is used to transmit the target data to the virtualization layer corresponding to the target data.

[0119] As one implementation of this application, the above conversion module can also be used for:

[0120] Obtain the request header of the resource access request;

[0121] The request header is parsed to determine the request type of the resource access request;

[0122] The resource access request is converted into the target data according to the request type.

[0123] As one implementation of this application, the above conversion module can also be used for:

[0124] Upon receiving feedback data of the target data, the feedback data is converted into standardized data, and the format of the standardized data conforms to the input parameter format required by the third-party desktop management system.

[0125] The standardized data is transmitted to the third-party desktop management system.

[0126] The cloud desktop management device provided in this embodiment of the invention can implement the steps in the above method embodiments, and will not be repeated here to avoid repetition.

[0127] Figure 6 A schematic diagram of the hardware structure of the cloud desktop management device provided in an embodiment of this application is shown.

[0128] The management device for the cloud desktop may include a processor 601 and a memory 602 storing computer program instructions.

[0129] Specifically, the processor 601 may include a central processing unit (CPU), an application-specific integrated circuit (ASIC), or one or more integrated circuits that can be configured to implement the embodiments of this application.

[0130] Memory 602 may include mass storage for data or instructions. For example, and not limitingly, memory 602 may include a hard disk drive (HDD), floppy disk drive, flash memory, optical disk, magneto-optical disk, magnetic tape, or Universal Serial Bus (USB) drive, or a combination of two or more of these. Where appropriate, memory 602 may include removable or non-removable (or fixed) media. Where appropriate, memory 602 may be internal or external to the integrated gateway disaster recovery device. In a particular embodiment, memory 602 is non-volatile solid-state memory.

[0131] Memory may include read-only memory (ROM), random access memory (RAM), disk storage media devices, optical storage media devices, flash memory devices, and electrical, optical, or other physical / tangible memory storage devices. Therefore, typically, memory includes one or more tangible (non-transitory) computer-readable storage media (e.g., memory devices) encoded with software including computer-executable instructions, and when the software is executed (e.g., by one or more processors), it is operable to perform the operations described with reference to the methods according to one aspect of this disclosure.

[0132] The processor 601 reads and executes computer program instructions stored in the memory 602 to implement any of the cloud desktop management methods in the above embodiments.

[0133] In one example, the cloud desktop management device may also include a communication interface 603 and a bus 610. Wherein, as Figure 6 As shown, the processor 601, memory 602, and communication interface 603 are connected through bus 610 and complete communication with each other.

[0134] The communication interface 603 is mainly used to realize communication between various modules, devices, units and / or equipment in the embodiments of this application.

[0135] Bus 610 includes hardware, software, or both, that couples components of a cloud desktop management device together. For example, and not limitingly, the bus may include an Accelerated Graphics Port (AGP) or other graphics bus, an Enhanced Industry Standard Architecture (EISA) bus, a Front Side Bus (FSB), HyperTransport (HT) interconnect, an Industry Standard Architecture (ISA) bus, an Infinite Bandwidth Interconnect, a Low Pin Count (LPC) bus, a memory bus, a Microchannel Architecture (MCA) bus, a Peripheral Component Interconnect (PCI) bus, a PCI-Express (PCI-X) bus, a Serial Advanced Technology Attachment (SATA) bus, a Video Electronics Standards Association Local (VLB) bus, or other suitable buses, or combinations of two or more of these. Where appropriate, bus 610 may include one or more buses. Although specific buses are described and illustrated in embodiments of this application, any suitable bus or interconnect is contemplated herein.

[0136] The cloud desktop management device can be based on the above embodiments to realize the cloud desktop management method and apparatus described above.

[0137] Furthermore, in conjunction with the cloud desktop management methods in the above embodiments, this application embodiment can provide a computer storage medium for implementation. This computer storage medium stores computer program instructions; when these computer program instructions are executed by a processor, they implement any of the cloud desktop management methods in the above embodiments and achieve the same technical effect. To avoid repetition, further details are omitted here. The aforementioned computer-readable storage medium may include non-transitory computer-readable storage media, such as read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks, etc., and is not limited thereto.

[0138] In addition, this application also provides a computer program product, including computer program instructions, which, when executed by a processor, can implement the steps and corresponding content of the aforementioned method embodiments.

[0139] It should be clarified that this application is not limited to the specific configurations and processes described above and shown in the figures. For the sake of brevity, detailed descriptions of known methods are omitted here. In the above embodiments, several specific steps are described and shown as examples. However, the method process of this application is not limited to the specific steps described and shown. Those skilled in the art can make various changes, modifications, and additions, or change the order of steps, after understanding the spirit of this application.

[0140] The functional blocks shown in the above block diagram can be implemented as hardware, software, firmware, or a combination thereof. When implemented in hardware, they can be, for example, electronic circuits, application-specific integrated circuits (ASICs), appropriate firmware, plug-ins, function cards, etc. When implemented in software, the elements of this application are programs or code segments used to perform the required tasks. Programs or code segments can be stored on a machine-readable medium or transmitted over a transmission medium or communication link via data signals carried on a carrier wave. "Machine-readable medium" can include any medium capable of storing or transmitting information. Examples of machine-readable media include electronic circuits, semiconductor memory devices, ROM, flash memory, erasable ROM (EROM), floppy disks, CD-ROMs, optical disks, hard disks, fiber optic media, radio frequency (RF) links, etc. Code segments can be downloaded via computer networks such as the Internet, intranets, etc.

[0141] It should also be noted that the exemplary embodiments mentioned in this application describe methods or systems based on a series of steps or apparatus. However, this application is not limited to the order of the above steps; that is, the steps can be performed in the order mentioned in the embodiments, or in a different order, or several steps can be performed simultaneously.

[0142] The aspects of this disclosure have been described above with reference to flowchart illustrations and / or block diagrams of methods, apparatus, and computer program products according to embodiments of this disclosure. It should be understood that each block in the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus to produce a machine such that these instructions, executable via the processor of the computer or other programmable data processing apparatus, enable the implementation of the functions / actions specified in one or more blocks of the flowchart illustrations and / or block diagrams. Such a processor can be, but is not limited to, a general-purpose processor, a special-purpose processor, a special application processor, or a field-programmable logic circuit. It is also understood that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can also be implemented by special-purpose hardware performing the specified functions or actions, or can be implemented by a combination of special-purpose hardware and computer instructions.

[0143] The above are merely specific embodiments of this application. Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, modules, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here. It should be understood that the protection scope of this application is not limited thereto. Any person skilled in the art can easily conceive of various equivalent modifications or substitutions within the technical scope disclosed in this application, and these modifications or substitutions should all be covered within the protection scope of this application.

Claims

1. A method for managing cloud desktops, characterized in that, The method is applied to a unified desktop management system, and the method includes: Upon receiving a resource access request from the cloud desktop, obtain the target identity information from the resource access request; If the target identity information is verified, the resource access request is parsed to obtain identification information, which is used to identify the cloud desktop type corresponding to the resource access request. The resource access request is sent to the third-party desktop management system corresponding to the cloud desktop type. The third-party desktop management system then transmits the resource access request to the resource adaptation module. The resource adaptation module converts the resource access request into target data and transmits the target data to the virtualization layer corresponding to the target data. The format of the target data conforms to the input parameter format required by the virtualization layer. The third-party desktop management system is a management system for cloud desktops from different vendors. The unified desktop management system is set at the user interface layer, located between the user and the third-party desktop management system, and connects to the third-party desktop management systems of different vendors through a unified standard application programming interface.

2. The cloud desktop management method according to claim 1, characterized in that, Sending the resource access request to the third-party desktop management system corresponding to the cloud desktop type includes: If the target identity information is verified, a verification token is added to the resource access request. The resource access request with the added verification token is sent to the third-party desktop management system corresponding to the cloud desktop type.

3. The cloud desktop management method according to claim 1, characterized in that, Before parsing the resource access request to obtain the identification information after the target identity information has been verified, the method further includes: Match the target identity information with a preset identity information database; If an identity matching the target identity exists in the identity information database, the target identity is determined to have passed verification.

4. A method for managing cloud desktops, characterized in that, The method is applied to the resource adaptation module, and the method includes: The system receives a resource access request from a third-party desktop management system. The resource access request originates from the unified desktop management system. Upon receiving the resource access request from the cloud desktop, the unified desktop management system obtains the target identity information from the resource access request. If the target identity information is verified, the system parses the resource access request to obtain identification information, which is used to identify the cloud desktop type corresponding to the resource access request. Finally, the system sends the resource access request to the third-party desktop management system corresponding to the cloud desktop type. The resource access request is converted into target data, wherein the format of the target data conforms to the input parameter format required by the virtualization layer; The target data is transmitted to the virtualization layer corresponding to the target data. The third-party desktop management system is a management system for cloud desktops from different vendors. The unified desktop management system is set at the user interface layer, located between the user and the third-party desktop management system, and connects to the third-party desktop management systems of different vendors through a unified standard application programming interface.

5. The cloud desktop management method according to claim 4, characterized in that, The step of converting the resource access request into target data includes: Obtain the request header of the resource access request; The request header is parsed to determine the request type of the resource access request; The resource access request is converted into the target data according to the request type.

6. The cloud desktop management method according to claim 4, characterized in that, After transmitting the target data to the virtualization layer corresponding to the target data, the method further includes: Upon receiving feedback data of the target data, the feedback data is converted into standardized data, and the format of the standardized data conforms to the input parameter format required by the third-party desktop management system. The standardized data is transmitted to the third-party desktop management system.

7. A cloud desktop management device, characterized in that, The device, used in a unified desktop management system, includes: The acquisition module is used to acquire the target identity information in the resource access request when the cloud desktop is received; The parsing module is used to parse the resource access request and obtain identification information when the target identity information is verified. The identification information is used to identify the cloud desktop type corresponding to the resource access request. The sending module is used to send the resource access request to the third-party desktop management system corresponding to the cloud desktop type. The third-party desktop management system then transmits the resource access request to the resource adaptation module. The resource adaptation module converts the resource access request into target data and transmits the target data to the virtualization layer corresponding to the target data. The format of the target data conforms to the input parameter format required by the virtualization layer. The third-party desktop management system is a management system for cloud desktops from different vendors. The unified desktop management system is set at the user interface layer, located between the user and the third-party desktop management system, and connects to the third-party desktop management systems of different vendors through a unified standard application programming interface.

8. A cloud desktop management device, characterized in that, The management device for the cloud desktop includes: a processor and a memory storing computer program instructions; When the processor executes the computer program instructions, it implements the cloud desktop management method as described in any one of claims 1-6.

9. A computer storage medium, characterized in that, The computer storage medium stores computer program instructions, which, when executed by a processor, implement the cloud desktop management method as described in any one of claims 1-6.

10. A computer program product, characterized in that, The computer program product includes computer program instructions, which, when executed by a processor, implement the cloud desktop management method according to any one of claims 1-6.

Images