Cloud desktop login method, apparatus and device, and computer readable storage medium

Abstract

The embodiment of the invention provides a cloud desktop login method and device, equipment and a computer readable storage medium, and relates to the technical field of cloud services. The method comprises the following steps: setting at least one configuration file template in a cloud server; and when receiving a login request of a user, the cloud server determines and obtains a target configuration file template from the at least one configuration file template, modifies the target configuration file template according to the user information to obtain a configuration file corresponding to the user information, and logs in the cloud desktop of the user by using the configuration file. According to the method and the device, part of contents in the configuration file template are modified in a manner of modifying on the basis of the pre-created configuration file template, the creation operation of the user configuration file does not need to be executed again, and the creation efficiency of the configuration file is improved. The problem of relatively long time consumption caused by re-creating a configuration file during first login can be avoided. By improving the creation efficiency of the configuration file, the login duration of the user who logs in the remote equipment for the first time is shortened.

Description

[0001] This application claims the priority of a Chinese patent application with the application number 202311658148.X and the application title "A Method and Device for Accelerating the Startup of a Cloud Desktop" filed with the National Intellectual Property Administration on December 1, 2023, the entire content of which is incorporated herein by reference. Technical Field

[0002] This application relates to the technical field of cloud services, and more specifically, to a method, device, equipment, and computer-readable storage medium for logging in to a cloud desktop. Background Art

[0003] In a cloud platform, a client connects to the cloud platform through a network to achieve remote display of a cloud desktop or remote access to a cloud server.

[0004] When the client logs in to the cloud desktop or the cloud server for the first time, the cloud server will perform a series of initialization operations to create a user profile. Since the user profile includes configuration files such as folders, files, registry, and configuration settings of the system environment, the creation process takes a long time. Therefore, when the client logs in to the cloud desktop or the cloud server for the first time, the login time is long. Summary of the Invention

[0005] This application provides a method, device, equipment, and computer-readable storage medium for logging in to a cloud desktop to reduce the login duration for the first login to the cloud desktop.

[0006] In a first aspect, an embodiment of this application provides a method for logging in to a cloud desktop. This method is executed by a cloud server in a cloud desktop system. At least one configuration file template of the cloud desktop is stored in the cloud server. The cloud desktop system further includes a client. The cloud server receives a login request sent by the client. In response to the login request, a target configuration file template is determined from at least one configuration file template. The login request includes user information of the user. The cloud server modifies the template configuration file based on the user information to obtain a configuration file corresponding to the user information. The cloud server uses the configuration file to log in to the user's cloud desktop. Wherein, the target configuration file template is used to indicate the user environment of the cloud desktop; the creation time of at least one configuration file template is earlier than the time when the login request is obtained.

[0007] Compared with the method of creating a configuration file when the user logs in, the embodiment of this application pre-creates a configuration file template. When receiving the user's login request, the configuration file template is adjusted according to the user information carried in the login request to obtain the user's configuration file. By adjusting based on the pre-created configuration file template, the creation efficiency of the configuration file is improved, and the problem of long time consumption caused by re-creating the configuration file during the first login can be avoided. By improving the creation efficiency of the configuration file, the login duration for the first login to the cloud desktop is shortened.

[0008] In a possible implementation, modifying the target configuration file template based on user information to obtain the user's configuration file is specifically implemented as follows: modifying the target configuration file template, the registry associated with the target configuration file template, and the access permission of the target configuration file template according to the user information to obtain the configuration file corresponding to the user information.

[0009] In this way, by modifying the target configuration file template, the registry associated with the target configuration file template, and the access permission of the target configuration file template, it is not necessary to re-execute the operation of creating the user configuration file, which improves the creation efficiency of the configuration file and can avoid the problem of long time consumption caused by re-creating the configuration file during the first login.

[0010] In a possible implementation, the user information includes the user name, security identifier (SID), and globally unique identifier (GUID). Modifying the target configuration file template, the registry associated with the target configuration file template, and the access permission of the target configuration file template according to the user information to obtain the configuration file corresponding to the user information is specifically implemented as follows: modifying the file name of the target configuration file template to the user name included in the user information. Modifying the call path of the target configuration file template in the registry according to the user name. Modifying the SID and GUID in the registry to the SID and GUID included in the user information. Modifying the access permission of the target configuration file template according to the user name to obtain the configuration file corresponding to the user information.

[0011] Based on this possible implementation, by modifying the file name of the target configuration file template, the registry associated with the target configuration file template, and the access permission of the target configuration file template, the target configuration file template of the simulated user is transferred to the user who requests to log in to the client. The rapid generation of the configuration file is realized, and the creation duration of the configuration file is shortened. Furthermore, the first login duration is shortened. And by ensuring the consistency between the file name of the target configuration file template, the registry associated with the target configuration file template, the access permission of the target configuration file template and the user information, the normal login of the cloud desktop is realized.

[0012] In a possible implementation, the user information includes configuration information. Modifying the target configuration file template based on the user information is specifically implemented as follows: modifying the configuration in the target configuration file template according to the configuration information included in the user information.

[0013] In this way, the configuration information modifies the configuration in the target configuration file template, ensuring the consistency between the configuration file corresponding to the user information and the configuration information in the user information, improving the adaptability between the configuration file and the user information, and further ensuring the accuracy of the configuration file.

[0014] In a possible implementation, the specific implementation is as follows: The user information further includes user permissions. When the cloud server determines the target configuration file template from at least one configuration file template, it obtains the target configuration file template that matches the user permissions from at least one configuration file template.

[0015] In this way, the adaptation degree between the target configuration file template and the user information is ensured through user permissions, the modification items of the target configuration file template are reduced, the rapid generation of the configuration file is realized, and the creation duration of the configuration file is shortened. Furthermore, the first login duration is shortened.

[0016] In a possible implementation, the specific implementation is as follows: The login request further includes the identifier of the target configuration file template. When the cloud server determines the target configuration file template from the at least one configuration file template, it obtains the target configuration file template indicated by the identifier from at least one configuration file template. Among them, the target configuration file template indicated by the identifier is obtained by the client through responding to the configuration file template operation.

[0017] Based on this possible implementation, the client obtains the identifier of the target configuration file template by responding to the configuration file template operation and sends the identifier of the target configuration file template to the cloud server. The cloud server obtains the target configuration file template from at least one configuration file template based on the identifier. In this way, a more adaptable target configuration file template is selected through the identifier, the modification items of the target configuration file template are reduced, the rapid generation of the configuration file is realized, and the creation duration of the configuration file is shortened. Furthermore, the first login duration is shortened.

[0018] In a possible implementation, the specific implementation is as follows: After logging in to the cloud desktop of the user using the configuration file, the cloud server sends the data of the cloud desktop to the client. Among them, the data of the cloud desktop enables the client to display the cloud desktop interface.

[0019] In this way, the display of the cloud desktop on the client is realized, which facilitates the client to call various functions of the cloud server through the function controls in the cloud desktop interface to complete the computing tasks.

[0020] In a possible implementation, the specific implementation of determining the target configuration file template from at least one configuration file template is as follows: In the case of determining that the user is logging in for the first time, the target configuration file template is determined from at least one configuration file template.

[0021] In this way, when the user logs in for the first time, the target configuration file template is determined from at least one configuration file template, and the configuration file is obtained by modifying the target configuration file template. It is possible to avoid the problem of long time consumption caused by re-creating the configuration file during the first login.

[0022] In a possible implementation, the specific implementation is as follows: after modifying the configuration file template based on the username to obtain the configuration file corresponding to the user information, the cloud server creates a new configuration file template.

[0023] After transferring the target configuration file template to the corresponding client user, the number of configuration file templates decreases. When the number of configuration file templates is insufficient, when a user logs in for the first time, they need to wait for the creation of the configuration file template or create a configuration file through an initialization operation. This will increase the first login duration. In this possible implementation, after modifying the configuration file template, a new configuration file template is created. In this way, it is ensured that the number of configuration file templates is sufficient, avoiding the problem of increased first login duration caused by insufficient configuration file templates.

[0024] In a possible implementation, the specific implementation is as follows: before receiving the login request sent by the client, the cloud server creates at least one simulated user, executes the login operations of each simulated user, and creates the configuration file templates of each simulated user.

[0025] Based on this possible implementation, the cloud server executes the login operations of each simulated user and creates the configuration file templates of each simulated user. In this way, by pre-creating the configuration file templates, reusable configuration file templates are provided for users who log in to the cloud desktop service for the first time, shortening the first login duration.

[0026] In a second aspect, an embodiment of the present application provides a cloud desktop login device. The cloud desktop login device can be a computing device cluster that executes the cloud desktop login method, or a chip or system-on-chip in the computing device cluster. The cloud desktop login device can implement the functional modules of the method in the first aspect or any possible implementation of the first aspect. The cloud desktop login device can implement the functions executed by the computing device in the first aspect or any possible implementation of the first aspect. The functional modules can be implemented by corresponding software executed by hardware. The hardware or software includes one or more modules corresponding to the above functions. For example: a communication module, a template acquisition module, a template modification module, and an operation module.

[0027] Among them, the communication module is used to receive the login request sent by the client. Among them, the login request includes user information.

[0028] The template acquisition module is used to determine, in response to the login request, a target configuration file template for indicating the user environment of the cloud desktop from at least one configuration file template. Among them, the creation time of the at least one configuration file template is earlier than the time of obtaining the login request.

[0029] The template modification module is used to modify the target configuration file template based on the user information to obtain the configuration file corresponding to the user information.

[0030] An operating module, configured to log in to the cloud desktop of the user by using a configuration file.

[0031] Specifically, the related processing actions and beneficial effects of the communication module, the template acquisition module, the template modification module, and the operating module may refer to those in the first aspect or any possible implementation manner of the first aspect, and will not be elaborated herein.

[0032] In a third aspect, an embodiment of the present application provides a computing device cluster. The computing device cluster includes at least one computing device. Each computing device includes a processor and a memory. The processor of at least one computing device is configured to execute instructions stored in the memory of at least one computing device, so that the computing device cluster executes the method in the first aspect or any possible implementation manner of the first aspect as described above.

[0033] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, including computer program instructions. When the computer program instructions are executed by a computing device cluster, the computing device cluster executes the computer program instructions stored in the computer-readable storage medium to execute the method in the first aspect or any possible implementation manner of the first aspect as described above.

[0034] In a fifth aspect, an embodiment of the present application provides a computer program product. When the instructions are run by a computing device or a computing device cluster, the computing device cluster is caused to execute the method in the first aspect or any possible implementation manner of the first aspect as described above.

[0035] For the technical effects brought by any design manner in the second aspect to the fifth aspect, reference may be made to the technical effects brought by the first aspect to the first aspect or different design methods, which will not be elaborated herein.

[0036] Based on the implementation manners provided in the above aspects, the present application can be further combined to provide more implementation manners. BRIEF DESCRIPTION OF THE DRAWINGS

[0037] Figure 1 A schematic diagram of an application scenario of the cloud desktop login method provided by an embodiment of the present application;

[0038] Figure 2 A schematic diagram of a process for creating a configuration file template provided by an embodiment of the present application;

[0039] Figure 3 A schematic diagram of a process for the cloud desktop login method provided by an embodiment of the present application;

[0040] Figure 4 A schematic diagram of a process for modifying a configuration file template provided by an embodiment of the present application;

[0041] Figure 5Schematic diagram of the processing flow of the cloud desktop login method provided by the embodiment of the present application;

[0042] Figure 6 Schematic diagram of the client login interface provided by the embodiment of the present application;

[0043] Figure 7 Schematic diagram of the client selecting a configuration file template provided by the embodiment of the present application;

[0044] Figure 8 Schematic diagram of the client cloud desktop interface provided by the embodiment of the present application;

[0045] Figure 9 Schematic diagram of the structure of the cloud desktop login device provided by the embodiment of the present application;

[0046] Figure 10 Schematic diagram of the structure of the cloud desktop login system provided by the embodiment of the present application;

[0047] Figure 11 Schematic diagram of the structure of the computing device provided by the embodiment of the present application;

[0048] Figure 12 Schematic diagram of the structure of the computing device cluster provided by the embodiment of the present application;

[0049] Figure 13 Schematic diagram of the network connection between computing devices in the computing device cluster provided by the embodiment of the present application. Detailed implementation manners

[0050] First, the nouns involved in the embodiments of the present application are explained.

[0051] A cloud desktop, also known as a virtual desktop, is a desktop virtualization technology based on cloud computing technology. This technology stores the desktop environment and application programs on the servers in the data center and transmits them to the user devices through a remote display protocol.

[0052] Virtualization technology is a technology for running multiple independent virtual machines on a single server. By deploying an operating system on the virtual machines, the resources on these virtual machines are separated from the underlying physical hardware resources, enabling multiple independent virtual environments for multiple users to be provided on a shared server.

[0053] The remote display protocol is used to establish a connection between the client device and the remote virtual desktop environment and to achieve the interaction of the graphical interface and data.

[0054] The data center is used to provide servers and storage devices. For example, in the cloud desktop scenario, the data center provides the servers and storage devices required for deploying the virtual desktop application scenario.

[0055] Cloud applications are application programs built based on computing resources, storage resources, network resources, etc. provided by a cloud computing platform, and are remote applications centrally managed and published by a server. Cloud applications decouple the application programs used by users from the operating system, providing a virtual running environment for the application programs, so that users in different regions using different terminal devices can obtain an access experience similar to running local application programs. Cloud applications feature high security for applications and data. Optionally, in the cloud desktop scenario, cloud applications are deployed in the operating system where the cloud desktop is located.

[0056] When a user logs in to the cloud desktop for the first time or logs in to a cloud application for the first time, the operating system will perform an initialization operation to create a user configuration.

[0057] Among them, a user profile is a collection of user folders, files, registry, and configuration information that defines the user environment when the user logs in to the cloud desktop or cloud application. Among them, the user environment includes environment variables used by the user, shortcut key settings, command aliases, etc.

[0058] Among them, the user configuration can also be called a configuration file and is used to configure the user environment. For example, to configure the user environment of the cloud desktop or to configure the user environment of the cloud application.

[0059] For example, the environment configuration in the user configuration includes but is not limited to configuring environment variables, configuring the desktop display interface, configuring shortcuts, configuring the start menu, configuring the browser, and configuring application software that starts up when the computer boots.

[0060] Among them, environment variables are parameters used in the operating system to indicate the operating environment of the operating system. For example, the path variable (path), through which the operating system can find the application program to be run or the folder to be loaded.

[0061] The initialization operation is a configuration operation performed by the operating system when a user logs in to the cloud desktop for the first time or logs in to a cloud application for the first time. In one possible implementation, the initialization operation includes creating a user account and user folder, configuring the user registry, setting user groups, initializing the desktop environment, and setting permissions for the user folder, etc.

[0062] Among them, the registry is the registry created by the operating system. The registry is used to store the system configuration and settings of the user. For example, environment variables are stored in the registry.

[0063] User groups are used to determine user permissions. The operating system includes multiple user groups, and each user group has different access permissions to the system, network, software, and hardware. For example, the operating system includes, but is not limited to, the administrators user group, the users user group, and custom user groups.

[0064] Desktop environment initialization is used to set up the desktop environment. For example, setting the desktop wallpaper, the desktop lock screen interface, the desktop task bar, and system shortcut keys, etc.

[0065] As described in the background art, when a user logs in to a cloud desktop or a cloud application for the first time, the above series of initialization operations are executed to create a configuration file, resulting in an increase in the user's login duration.

[0066] Based on this, to reduce the login duration of users who log in to a cloud desktop or a cloud application for the first time, improve the login efficiency, and enhance the user experience. An embodiment of the present application provides a cloud desktop login method. Compared with the method of creating a configuration file when a user logs in, in the embodiment of the present application, a configuration file template is created in advance. When a login request of a user is received, the configuration file template is modified according to the user information carried in the login request to obtain the user's configuration file. By modifying based on the pre-created configuration file template, some contents in the configuration file template are modified, and there is no need to re-execute the operation of creating the user configuration file, thus improving the creation efficiency of the configuration file. It can avoid the problem of long time consumption caused by re-creating the configuration file when logging in for the first time. By improving the creation efficiency of the configuration file, the login duration of logging in to the cloud desktop for the first time is shortened. The login efficiency is improved, and the user experience is enhanced.

[0067] It should be noted that the cloud desktop login method provided by the embodiment of the present application can not only be applied to the cloud desktop or cloud application scenario to shorten the first login duration of the cloud desktop or cloud application. The cloud desktop login method provided by the embodiment of the present application can also be applied to the device remote control scenario to shorten the login duration of the user terminal remotely logging in to a physical device.

[0068] Understandably, when the method provided by the embodiment of the present application is applied to the cloud desktop scenario, the cloud server providing the cloud desktop service can be called a cloud desktop server. When the method provided by the embodiment of the present application is applied to the cloud application scenario, the cloud server providing the cloud application service can be called a cloud application server.

[0069] Taking the cloud desktop login method provided by the embodiment of the present application applied to the cloud desktop as an example, an application scenario of the cloud desktop login method is provided. As Figure 1 shown, Figure 1It is a schematic diagram of the application scenario of the cloud desktop method provided by the embodiments of the present application. The shown application scenario includes a cloud desktop system 100. The cloud desktop system 100 includes a cloud desktop server 10 and a client 20. The cloud desktop server 10 exchanges data with the client 20 through a network 30.

[0070] Among them, the cloud desktop server 10 is used to provide cloud desktop services to the client 20. The client 20 is used to request cloud desktop services from the cloud desktop server 10.

[0071] In the embodiments of the present application, the client 20 sends a login request to the cloud desktop server 10. The cloud desktop server 10 receives the login request and provides cloud desktop services to the client 20.

[0072] In a possible implementation manner, as Figure 1 shown, the cloud desktop server 10 includes a hardware resource layer 103, a virtual desktop layer 102, and an access layer 101.

[0073] Among them, the hardware resource layer 103 is used to provide hardware resources. For example, it provides computing resources, storage resources, and network resources.

[0074] The virtual desktop layer 102 is used to allocate a virtual desktop system and associate virtual resources based on the hardware resource layer 103, and load a configuration file to provide cloud desktop services to the client 20. Among them, the virtual resources include virtual computing resources, virtual storage resources, and virtual network resources.

[0075] The access layer 101 is used to receive the login request of the client 20 and allocate cloud desktops to the client 20, etc.

[0076] In an example, a cloud desktop management component 1012 and an access gateway 1011 are deployed in the access layer 101.

[0077] Among them, the access gateway 1011 is used to receive the login request of the client 20. The cloud desktop management component 1012 can be a virtual component. The cloud desktop management component 1012 is used to manage the cloud desktops provided by the cloud desktop server 10. For example, generating cloud desktops through the virtual desktop layer 102, and generating configuration files, etc.

[0078] In a possible implementation manner, the client 20 can be an application, such as a cloud computer application. Or the client 20 can be a web client. Or the client 20 can also be a terminal device, such as a cloud terminal, a mobile phone terminal, a tablet computer, a personal computer, or a notebook computer, etc.

[0079] In an example, when the client 20 is an application, the computing device runs the client 20 and sends a login request to the cloud desktop server 10.

[0080] In a possible implementation, a configuration file template is set in the cloud desktop management component 1012. When a user logs in for the first time, the cloud desktop management component 1012 modifies the configuration file template to obtain a configuration file corresponding to the user.

[0081] In the embodiment of the present application, when the client 20 requests a cloud desktop service from the cloud desktop server 10, the client 20 establishes a connection with the access layer 101 of the cloud desktop server 10 through the network. The client 20 sends a login request to the access layer 101. The access gateway 1011 of the access layer 101 receives the login request. The cloud desktop management component 1012 of the access layer 101 executes the cloud desktop login method provided in the embodiment of the present application, creates a cloud desktop corresponding to the user through the virtual desktop layer 102, logs in to the user's cloud desktop, and sends a cloud desktop interface to the client. The client 20 displays the cloud desktop interface.

[0082] It should be noted that Figure 1 These are only exemplary drawings and do not constitute a limitation on the cloud desktop login method provided in the embodiment of the present application. Figure 1 The naming and grouping of the cloud desktop system 100 and the cloud desktop server 10 in the figure are schematic, and are only a logical function grouping. In actual implementation, there may be other grouping methods. For example, the cloud desktop server 10 can also be divided into a communication module, a template acquisition module, a template modification module, and an operation module. Specifically, another division example can be referred to in the Figure 9 corresponding example. And the cloud desktop server 10 can also be named a cloud desktop server or a cloud server. The cloud desktop server or the cloud server can include modules different from Figure 1 those shown.

[0083] Next, based on Figure 1 the provided application scenario, the cloud desktop login method provided in the embodiment of the present application will be introduced.

[0084] In the embodiment of the present application, after the deployment of the cloud desktop server is completed, the cloud desktop server creates a simulated user and creates a configuration file template for the simulated user. In subsequent cloud desktop logins, when the client corresponds to the user's first login, the cloud desktop server modifies the configuration file template of the simulated user to achieve fast cloud desktop login.

[0085] First, based on Figure 1 the provided application scenario, the creation process of the configuration file template will be described.

[0086] As Figure 2 shown, Figure 2It is a schematic flowchart of a method for creating a configuration file template provided by an embodiment of the present application. The method for creating the configuration file template includes steps S210 to S230.

[0087] Step S210, deploy a cloud desktop server.

[0088] In an embodiment of the present application, the cloud desktop server is a cloud server that provides cloud desktop services.

[0089] In an embodiment of the present application, a cloud platform is built based on the cloud server, and the cloud platform provides cloud desktop services. This is not described in detail in this embodiment of the present application.

[0090] Step S220, the cloud desktop server creates at least one simulated user.

[0091] In a first possible implementation manner, the cloud desktop server automatically creates simulated users.

[0092] In an example, the cloud desktop server randomly generates simulated users. For example, it creates simulated users by randomly generating user names.

[0093] In another example, the cloud desktop server generates simulated users through running script code. For example, when deploying the cloud desktop service, script code is deployed in the cloud server, and simulated users are generated by running the script code.

[0094] In a second possible implementation manner, the cloud desktop server creates simulated users in response to a simulated user creation instruction.

[0095] For example, an administrator of the cloud desktop server inputs a user creation instruction through the interface of the cloud desktop service.

[0096] In an embodiment of the present application, when the deployed cloud desktop server can receive two or more login requests at the same time, the cloud desktop server creates multiple simulated users. When the deployed cloud desktop service does not provide concurrent login services, the cloud desktop server creates one simulated user.

[0097] In a possible implementation manner, when the cloud desktop server creates multiple simulated users, each simulated user has a different user name. It can be understood that each simulated user belongs to the same user group. Or the user groups where each simulated user is located are not completely the same.

[0098] Step S230, the cloud desktop server performs the login operations of each simulated user and creates the configuration file templates of each simulated user.

[0099] In a possible implementation manner, for each simulated user, the cloud desktop server performs the above initialization operations to create the configuration file template of the simulated user.

[0100] As Figure 2 shown, the cloud desktop server sets the user permissions for each simulated user (step S231). The cloud desktop server sends a login instruction to the operating system where the cloud desktop server is located, and the operating system performs a login operation according to the user permissions of each simulated user to create a configuration file template for the simulated user (step S232).

[0101] In one example, the cloud desktop server sets the user permissions for each simulated user by setting the user group of each simulated user.

[0102] In one example, the cloud desktop server can send a login instruction to the operating system of the cloud desktop server through commands such as runas or psexec.

[0103] Based on Figure 2 the provided embodiments, after the cloud server runs the cloud desktop service, the cloud desktop server performs the login operations of each simulated user and creates a configuration file template for each simulated user. In this way, by pre-creating the configuration file template, a reusable configuration file template is provided for users who log in to the cloud desktop service for the first time, shortening the first login duration.

[0104] After the cloud desktop server completes the deployment and the creation of the configuration file template, it waits for the client to log in. When the cloud desktop server receives a login request sent by the client, it executes the cloud desktop login method, and the cloud desktop server starts the cloud desktop and provides the cloud desktop service to the client.

[0105] Next, the cloud desktop login method provided by the embodiments of the present application will be described.

[0106] In the embodiments of the present application, the configuration file template is used to indicate the user environment of the cloud desktop. For example, the system environment for running the cloud desktop, desktop wallpaper, shortcut settings, start menu settings, browser settings, and application software settings, etc.

[0107] As Figure 3 shown Figure 3 is a schematic flowchart of the cloud desktop login method provided by the embodiments of the present application. The shown cloud desktop login method includes steps S310 to S360.

[0108] Step S310, the client sends a login request to the cloud desktop server.

[0109] In the embodiments of the present application, the cloud desktop server provides cloud desktops with different desktop environments to multiple users, and the operating systems where different cloud desktops are located are isolated from each other through the user name. When the client logs in to the cloud desktop server, to ensure that the cloud desktop server provides reliable cloud services to the client, the login request sent by the client needs to carry user information.

[0110] In the first possible implementation, the user information includes the username.

[0111] The user can send a login request to the cloud desktop server by clicking on the login function control in the user interface of the client.

[0112] In an example, in response to a click operation on the login function control in the user interface, the client displays a cloud desktop login interface. The client sends a login request to the cloud desktop server based on the user information entered in the cloud desktop login interface.

[0113] For example, a username input box is set in the cloud desktop login interface. The user enters the user information by clicking on the username input box.

[0114] In the second possible implementation, the user information includes the username, the user login password, the user group, and the system parameters of the operating system where the requested cloud desktop is located. Among them, the system parameters include but are not limited to the device name of the computing device where the cloud desktop is located, the processor model, the running memory size, the operating system type, the system version number, etc. The operating system type includes Windows system, MAC system, or Linux operating system.

[0115] In an example, multiple cloud computer labels with different system parameters and corresponding selection controls are displayed in the cloud desktop login interface of the client. In response to the selection operation of the cloud computer label, the client obtains the system parameters of the operating system where the requested cloud desktop is located. A user information input interface is displayed. In the user information input interface, the system parameters of the operating system where the requested cloud desktop is located, a username input box, a login password input box, and a user group input box are displayed. The client sends a login request to the cloud desktop server based on the username, the user login password, the user group, and the system parameters of the operating system where the requested cloud desktop is located entered on the user information input page.

[0116] Step S320: The cloud desktop server receives and responds to the login request sent by the client.

[0117] After receiving the login request sent by the client, the cloud desktop server determines whether the user is logging in for the first time based on the user information carried in the login request. If it is determined that the user is logging in for the first time, the cloud desktop server executes the following steps S330 to S350 to log in to the cloud desktop. If the user is not logging in for the first time, the cloud desktop server executes the following step S360 to run the configuration file corresponding to the user information and log in to the cloud desktop.

[0118] In the first example, the cloud desktop server can query whether there is a configuration file corresponding to the user information based on the user information. In the case where there is no configuration file corresponding to the user information, it is determined that the user of the client logs in for the first time. In the case where there is a configuration file corresponding to the user information, it is determined that the user of the client is not logging in for the first time.

[0119] In the second example, the cloud desktop server can query whether there is a login record corresponding to the user information according to the user information. In the case where there is a login record corresponding to the user information, it is determined that the user of the client is not logging in for the first time. In the case where there is no login record corresponding to the user information, it is determined that the user of the client logs in for the first time.

[0120] Among them, the login record is used to indicate the number of logins of the client, the duration of each login, the network address where the client is located, and the username used.

[0121] For example, according to the username, query whether there is a login record including the username. In the case where there is a login record including the username, it is determined that there is a configuration file corresponding to the user information. In the case where there is no login record including the username, it is determined that there is no configuration file corresponding to the user information.

[0122] In the embodiments of the present application, the login log data includes the number of logins of the client, the duration of each login, the network address where the client is located, and the username used.

[0123] In the embodiments of the present application, in the case where it is determined that the user logs in for the first time, the above step S230 is executed, and the configuration file corresponding to the user information is obtained by modifying the configuration file template.

[0124] Step S330, in the case where the client corresponds to the user logging in for the first time, the cloud desktop server determines a target configuration file template from at least one configuration file template.

[0125] In the first possible implementation manner, in the case where there is one configuration file template, the cloud desktop server directly selects the target configuration file template.

[0126] In the second possible implementation manner, in the case where there are multiple configuration file templates, the cloud desktop server selects a target configuration file template that matches the user information from the multiple configuration file templates.

[0127] In the first example, the cloud desktop server can randomly select a configuration file template from the configuration file templates as the target configuration file template that matches the user information.

[0128] In the second example, the cloud desktop server uses the configuration file template that matches the user group in the user information among multiple configuration file templates as the target configuration file template that matches the user information. In this way, the user permissions of the configuration file template that matches the user information match the user permissions included in the user information.

[0129] Exemplarily, the matching can be that the user group in the configuration file template is the same as the user group in the user information.

[0130] For example, taking the user group in the user information as the administrators user group as an example, when the user group of configuration file template A is the users user group, the user group of configuration file template B is the administrators user group, and the user group of configuration file template C is the users user group, configuration file template B is used as the target configuration file template that matches the user information.

[0131] Exemplarily, the matching can be that the user permissions corresponding to the user group in the configuration file template are greater than the user permissions corresponding to the user group in the user information.

[0132] For example, taking the user group in the user information as the custom user group as an example, when the user group of configuration file template A is the users user group, the user group of configuration file template B is the administrators user group, and the user group of configuration file C is the users user group, since the user permissions of the administrators user group are greater than the user permissions of the custom user group, configuration file template B is used as the target configuration file template that matches the user information.

[0133] In the third example, the login request further includes the identifier of the target configuration file template. The cloud desktop server obtains the target configuration file template indicated by the identifier from multiple configuration file templates. Among them, the target configuration file template indicated by the identifier is obtained by the client in response to the configuration file template operation.

[0134] Among them, the identifier can be the username of the simulated user corresponding to the configuration file template.

[0135] For example, the usernames of multiple simulated users provided by the cloud desktop server are displayed on the cloud desktop login interface of the client. The client determines the username of the selected simulated user in response to the selection operation. The client sends a login request to the cloud desktop server, and the login request includes user information and the username of the selected simulated user. The cloud desktop server obtains the username of the simulated user selected by the client from the login request, and uses the configuration file template whose username is the same as the username of the simulated user selected by the client among multiple configuration file templates as the target configuration file template that matches the user information.

[0136] Step S340: Modify the target configuration file template based on the user information to obtain the configuration file corresponding to the user information.

[0137] Since the operating system where the cloud desktop server is located sets the file name of the user folder through the user name of the logged-in user. When the user name of the logged-in user is inconsistent with the file name of the user folder, the operating system will start with errors and the cloud desktop login cannot be achieved.

[0138] Based on this, in the embodiment of the present application, modifying the target configuration file template based on the user information includes: modifying the file name of the target configuration file template according to the user information. In this way, by ensuring that the user name logged in to the cloud desktop is consistent with the file name of the configuration file, the normal login of the cloud desktop is achieved.

[0139] In a possible implementation, since the registry and the access rights of the configuration file template are also involved in the startup of the operating system, and the access rights of the registry and the configuration file template are both associated with the user name of the logged-in user. When the user name of the logged-in user is inconsistent with the user name corresponding to the configuration file template, only modifying the file name of the configuration file template will also cause errors in the startup of the operating system and the cloud desktop login cannot be achieved. Therefore, modifying the target configuration file template based on the user information includes: modifying the file name of the target configuration file template, the registry associated with the target configuration file template, and the access rights of the target configuration file template according to the user information. In this way, by ensuring the consistency between the file name, the registry, and the access rights of the configuration file template and the user name of the logged-in user, the normal login of the cloud desktop is achieved.

[0140] Since the user configurations of different users are different. For example, the desktop display interfaces, shortcut methods, and start menu settings of different users are different. Therefore, in order to provide a cloud desktop that is more adapted to the user, in the embodiment of the present application, in addition to modifying the file name of the target configuration file template, the configuration in the target configuration file template can also be modified based on the user information.

[0141] In an example, the user information further includes configuration information. The cloud desktop server modifies the configuration in the target configuration file template according to the configuration information.

[0142] Among them, the configuration information includes one or more of desktop display information, shortcut methods, and start menu setting information.

[0143] For example, taking the configuration information as the desktop display information as an example, the desktop display information includes at least one of the cloud desktop interface color, the cloud desktop wallpaper, and the cloud desktop display font. The cloud desktop server modifies at least one of the cloud desktop interface color, the cloud desktop wallpaper, and the cloud desktop display font in the target configuration file template according to the configuration information in the user information.

[0144] Step S350: The cloud desktop server logs in to the user's cloud desktop using the configuration file.

[0145] In the embodiment of the present application, the cloud desktop server logs in to the user's cloud desktop using the configuration file, including: the cloud desktop server copies the configuration file to the running memory, loads the configuration file, creates and loads the user environment of the user's cloud desktop, and sends the data of the cloud desktop to the client.

[0146] For example, Figure 1 Taking the provided cloud desktop platform as an example, the desktop management component in the access layer 101 loads the configuration file through the virtual desktop system provided in the virtual desktop layer 102, and creates and loads the user environment of the user's cloud desktop.

[0147] In the first possible implementation manner, after obtaining the configuration file corresponding to the user information, the cloud desktop server automatically creates and loads the user environment of the user's cloud desktop, and sends the data of the cloud desktop to the client.

[0148] In the second possible implementation manner, after obtaining the configuration file corresponding to the user information, the cloud desktop server sends the login account and login password to the client. The client sends a cloud desktop start request to the cloud desktop server according to the login account and login password. The cloud desktop server receives the cloud desktop start request sent by the client and logs in to the user's cloud desktop using the configuration file.

[0149] Step S360: In the case where the client is the user's non-first login, the cloud desktop server loads the configuration file corresponding to the user information and logs in to the user's cloud desktop.

[0150] In the embodiment of the present application, cloud applications are deployed in the operating system where the cloud desktop is located, and the icons of the cloud applications are displayed in the cloud desktop interface. The user can click the icon of the cloud application in the cloud desktop interface displayed on the client, and the client responds to the click operation of the icon of the cloud application and sends an application start request to the cloud desktop server. The cloud desktop server receives the application start request, obtains the start interface data of the cloud application corresponding to the application start request, and sends the start interface data of the cloud application to the client. The client displays the start interface of the cloud application based on the received start interface data.

[0151] In a possible implementation manner, when the cloud application corresponding to the application start request requires the user to log in, in the case where the user logs in to the cloud application for the first time, the cloud desktop server needs to create and execute user registration operations, create user accounts, login passwords, and application settings, etc., and generate user login files, which will increase the login duration of the cloud application.

[0152] Based on this, to reduce the first login duration of the cloud application, for the cloud application that needs to log in, the cloud desktop serverFigure 2 The provided configuration file template is created to create a user login file template for cloud applications. When the cloud desktop server determines that a user logs in to a cloud application for the first time, it modifies the user login file template according to the user information carried in the user login request to obtain a user login file corresponding to the user information. The cloud desktop server realizes the fast login of the cloud application by running the user login file corresponding to the user information and provides the cloud application service to the cloud desktop server.

[0153] Based on Figure 3 In the provided embodiments, compared with the method of creating a configuration file when a user logs in, the embodiments of the present application pre-create a configuration file template. When receiving a user's login request, in the case of the user's first login, the target configuration file template is adjusted according to the user information carried in the login request to obtain the user's configuration file. By adjusting based on the pre-created target configuration file template, some content in the target configuration file template is modified, and there is no need to re-execute the operation of creating a user configuration file, which improves the creation efficiency of the configuration file and can avoid the problem of long time consumption caused by re-creating the configuration file during the first login. By improving the creation efficiency of the configuration file, the login duration of the first login is shortened.

[0154] To better illustrate the cloud desktop login method provided by the embodiments of the present application, next, taking the modification of the file name of the target configuration file template, the registry associated with the target configuration file template, and the access permission of the target configuration file template according to user information as an example, the modification method of the target configuration file template in the above step S340 will be described.

[0155] As Figure 4 shown, Figure 4 is a schematic flowchart of modifying the target configuration file template provided by the embodiments of the present application. The shown process of modifying the target configuration file template includes steps S341 to S344.

[0156] Step S341, rename the target configuration file template. Modify the file name of the target configuration file template to the user name included in the user information.

[0157] In a possible implementation manner, the file name of the target configuration file template is modified by renaming.

[0158] In an example, the file name of the target configuration file template can be modified by modifying the file address.

[0159] The cloud desktop server obtains the file address of the target configuration file template according to the file name of the target configuration file template. The cloud desktop server modifies the file name of the target configuration file template by modifying the folder name in the file address of the target configuration file template.

[0160] For example, taking the target configuration file template X1 as an example, assume that the file name of the target configuration file template X1 is "MN1", and the target configuration file template X1 is located in the User directory under the C drive of the cloud desktop server, that is, the file address of the target configuration file template X1 is C:\Users\MN1. When the user name in the user information is "yh1", change the file name "MN1" of the target configuration file template X1 to "yh1", and change the file address C:\Users\MN1 of the target configuration file template X1 to C:\Users\yh1.

[0161] Step S342, registry modification. Modify the call path of the target configuration file template in the registry according to the user name, and modify the security identifier SID and the global security symbol GUID in the registry to the SID and GUID included in the user information.

[0162] In a possible implementation, the registry includes the call path of the target configuration file, and the call path is used to obtain the configuration file. In this way, when the cloud desktop is started, the cloud server obtains the configuration file through the call path of the configuration file in the registry, and copies the configuration file to the user configuration (Profile) file directory. The processor of the cloud server loads the configuration file in the Profile file directory and starts the cloud desktop. After the file name of the target configuration file template is renamed, the cloud desktop server replaces the call path of the target configuration file template in the registry according to the user name included in the user information.

[0163] Among them, the Profile file directory is used to set the environment variables and startup programs of the operating system.

[0164] In an example, the cloud desktop server forms a new call path according to the user name. The cloud desktop server obtains the call path of the target configuration file template from the registry by querying the index. Replace the call path of the target configuration file template with the new call path.

[0165] Among them, the query index can be "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList\", and the environment variables are stored in ProfileList. For example, the call path of the target configuration file template is stored in ProfileList.

[0166] For example, taking the file address of the target configuration file template X1 as C:\Users\MN1, the target configuration file template X1 is obtained according to the call path (profileimagepath) "C:\Users\MN1" in the registry. When the file address of the target configuration file template is modified to "C:\Users\yh1", the call path (profileimagepath) "C:\Users\MN1" in the registry is modified to "C:\Users\yh1". The target configuration file template X1 is obtained according to the call path (profileimagepath) "C:\Users\yh1" in the registry.

[0167] In the embodiment of the present application, the registry also includes the SID and GUID of the logged-in user.

[0168] Among them, SID is an identifier used to uniquely identify a security principal (such as a user, group, computer, etc.). Each logged-in user is assigned a unique SID in the operating system for authentication and access control.

[0169] GUID is a set of text strings used to identify the logged-in user.

[0170] Since the SID and GUID of different logged-in users are different in the operating system. Therefore, when modifying the registry, in addition to replacing the call path of the target configuration file template in the registry, it is also necessary to modify the SID and GUID of the impersonated user in the registry.

[0171] For example, the SID and GUID in the target configuration file template are also stored in ProfileList. The cloud desktop server obtains the SID and GUID in the target configuration file template from the registry through the above query index, and modifies the SID and GUID in the target configuration file template to the SID and GUID included in the user information.

[0172] In a possible implementation manner, when the cloud desktop server determines that the user logs in for the first time, it generates the SID and GUID corresponding to the user information through the identifier generation algorithm deployed in the operating system. The cloud desktop server modifies the SID of the impersonated user corresponding to the target configuration file template under the registry query index to the SID corresponding to the user information, and modifies the GUID of the impersonated user corresponding to the target configuration file template in the registry to the GUID corresponding to the user information.

[0173] Step S343, modify file permissions. Modify the access permissions of the modified target configuration file template according to the user name.

[0174] In a possible implementation, after modifying the file name of the target configuration file template and the registry, to ensure the normal access to the configuration file and data security, and to prevent other users from modifying the configuration file, it is necessary to modify the access rights of the target configuration file template according to the user name in the user information.

[0175] In one example, the cloud desktop server associates the access rights of the target configuration file template with the user name. And disconnects the association between the access rights of the simulated user corresponding to the target configuration file template and the target configuration file template. In this way, the access rights of the target configuration file template are modified from the simulated user to the user who requests to log in to the client.

[0176] In another example, the cloud desktop server can obtain the access rights list of the target configuration file template, write the user name in the user information into the access rights list. And delete the user name of the simulated user corresponding to the target configuration file template from the access rights list.

[0177] For example, replace the user name of the simulated user corresponding to the target configuration file template in the access rights list with the user name in the user information.

[0178] Step S344, user permission setting.

[0179] In the first possible implementation, the cloud desktop server can set the user permissions by setting the user group corresponding to the user who requests to log in to the client.

[0180] For example, the cloud desktop server sets the user group corresponding to the user who requests to log in to the client as "administrators" or "users".

[0181] In the second possible implementation, the cloud desktop server can set the user permissions through the user group included in the user information.

[0182] For example, when the user group included in the user information is "administrators", the cloud desktop server sets the user permissions as administrator permissions.

[0183] Based on Figure 4 The provided embodiments, the cloud desktop server transfers the target configuration file template of the simulated user to the user who requests to log in to the client by modifying the file name of the target configuration file template, the registry associated with the target configuration file template, and the access rights of the target configuration file template. It realizes the rapid generation of the configuration file, shortens the creation duration of the configuration file. And further shortens the first login duration.

[0184] In the embodiments of the present application, after transferring the target configuration file template to the corresponding client user, the number of configuration file templates decreases. When the number of configuration file templates is insufficient, when the user logs in for the first time, they need to wait for the creation of the configuration file template or create a configuration file through an initialization operation. This will increase the first login duration. Based on this, after modifying the configuration file template, the cloud desktop server executes the above Figure 2 provided embodiment to create a new configuration file template for the simulated user. In this way, it is ensured that the number of configuration file templates is sufficient, avoiding the problem of increased first login duration caused by insufficient configuration file templates.

[0185] As Figure 5 shown, the cloud desktop server executes the creation of the configuration file template (step S1). Receives the login request of user A (step S2). The cloud desktop server determines whether user A logs in for the first time (step S3). When it is determined that the user logs in for the first time, the cloud desktop server modifies the configuration file template of the simulated user B based on the user information of user A (step S4), transfers the configuration file template of the simulated user B to the currently logged-in user A. And re-executes the login operation of the simulated user B to create a new configuration file template for the simulated user B (step S5). When it is determined that the user does not log in for the first time, the cloud desktop server loads the configuration file corresponding to user A (step S6).

[0186] Wherein, user A is the user name carried in the login request sent by the client.

[0187] It should be noted that in the Figure 5 shown cloud desktop login process, the cloud desktop server can execute the above steps S210 - S230 to create a configuration file template for the simulated user (step S1), and can execute the above step S340, or Figure 4 the provided embodiment to transfer the configuration file template of the simulated user B to the currently logged-in user A. The embodiments of the present application will not be elaborated here.

[0188] In the first possible implementation manner, after modifying the access permission of the modified configuration file template, the cloud desktop server executes the above Figure 2 provided embodiment to create a new configuration file template for the simulated user.

[0189] In the second possible implementation manner, after obtaining the configuration file corresponding to the user information, the cloud desktop server executes the above Figure 2 provided embodiment to create a new configuration file template for the simulated user.

[0190] In the third possible implementation manner, after logging in to the cloud desktop server, the cloud desktop server executes the above Figure 2 provided embodiment to create a new configuration file template for the simulated user.

[0191] It should be noted that the above implementation manner of the reconfigured file template is only for exemplary illustration and does not constitute a limitation on the cloud desktop login method provided by the embodiments of the present application. In actual applications, the cloud desktop server may adopt other implementation manners according to the actual application scenarios.

[0192] For example, in the case where the cloud desktop server provides a configuration file template, after modifying the configuration file template, the cloud desktop server creates a new configuration file template for the simulated user according to any of the above possible implementation manners.

[0193] Again, for example, in the case where the cloud desktop server provides multiple configuration file templates, after modifying the configuration file templates, the cloud desktop server queries the remaining quantity of the configuration file templates. When the remaining quantity of the configuration file templates is greater than the preset quantity threshold, the cloud desktop server does not perform the operation of regenerating the configuration file template. When the remaining quantity of the configuration file templates is less than or equal to the preset quantity threshold, the cloud desktop server executes the above Figure 2 provided embodiments to create a new configuration file template for the simulated user.

[0194] In the embodiments of the present application, to avoid the re-creation of the configuration file template, after obtaining the target configuration file template corresponding to the user information, the cloud desktop server creates an image file of the target configuration file template. The cloud desktop server modifies the image file of the target configuration file template according to the above Figure 4 provided embodiments to obtain the configuration file corresponding to the user information. In this way, after directly modifying the target configuration file template, it is not necessary to re-execute the operation of creating the configuration file template.

[0195] The above mainly introduces the cloud desktop login method provided by the embodiments of the present application from the perspective of the interaction between the cloud desktop server and the client. To better illustrate the cloud desktop login method provided by the embodiments of the present application, taking the client as a mobile terminal as an example, the embodiments of the present application also provide an interaction interface embodiment between clients.

[0196] In a possible implementation manner, the client sends a login request to the cloud desktop server based on the user information input through the cloud desktop interface.

[0197] As Figure 6 shown, Figure 6 is a schematic diagram of the client cloud desktop login interface provided by the embodiments of the present application. Figure 6 In the (a) figure in Figure 6The cloud desktop login interface shown in Figure (b). In the cloud desktop login page interface, a parameter box for cloud computer 1, a parameter box for cloud computer 2, and a parameter box for cloud computer 3 are displayed, as well as a "More" control. Among them, the corresponding system parameters and selection controls are respectively displayed in the parameter box for cloud computer 1, the parameter box for cloud computer 2, and the parameter box for cloud computer 3. When the user clicks the selection control for cloud computer 1, the client obtains the system parameters of cloud computer 1 and displays as shown in Figure 6 The user information input interface shown in Figure (c). In the user information input interface, the device name XXXCOXX1 of cloud computer 1, the processor model Intel(R) Core(TM) i5-10400 CPU @ 2.90GHz 2.90GHz, the running memory size 8.00GB, and the operating system type Windows 10 Professional Edition and other system parameters are displayed. And a user name input box, a login password input box, and a user group input box are displayed in the user information input interface. When the user clicks the user name input box to evoke the soft keyboard, enters the user name through the soft keyboard, clicks the login password input box to enter the user login password, and enters the user group, it is displayed as shown in Figure 6 The interface shown in Figure (d). In Figure 6 The interface shown in Figure (d), the user name XXX1, the login password, and the user group administrators are displayed. When the user clicks Figure 6 The "Log in immediately" control displayed in Figure (d), the client sends a login request to the cloud desktop server.

[0198] In a possible implementation, the client sends a login request to the cloud desktop server based on the user information input in the cloud desktop interface and the target configuration file template selected by the user.

[0199] As shown in Figure 7 In the cloud desktop login interface shown in Figure (a), a selection control for the configuration file template is displayed. When the user clicks the selection control to input the operation of selecting the configuration file template. The client responds to the operation of selecting the configuration file template and displays as shown in Figure 7 The configuration file template display interface shown in Figure (b). In the configuration file template display interface, the identifier of the configuration file template provided by the cloud desktop server is displayed. Among them, the identifier of the configuration file template can be the user name of the simulated user. As shown in Figure 7 In Figure (b), the identifiers of the configuration file templates displayed in the configuration file template display interface include User 1, User 2, User 3, User 4, User 5, User 6, and User 7. When the user clicks the selection control for User 3 in the configuration file template display interface and clicks Figure 7 The "Confirm" control displayed in Figure (b), the client determines the target configuration file template selected by the user. Figure 7 In Figure (b), the client determines the target configuration file template selected by the user.

[0200] In one example, after the client displays the "Log in immediately" control shown in (d) of Figure 6 upon the user's click, the client displays the interface as shown in (a) of Figure 7 . After the client determines the target profile template selected by the user, the client sends a log-in request to the cloud desktop server based on the identifier of the target profile template selected by the user and the user information. Figure 6 After the user clicks the "Log in immediately" control shown in (d) of Figure 6 , the client displays the interface as shown in (a) of Figure 7 . After the client determines the target profile template selected by the user, the client sends a log-in request to the cloud desktop server based on the identifier of the target profile template selected by the user and the user information. Figure 7 After the client determines the target profile template selected by the user, the client sends a log-in request to the cloud desktop server based on the identifier of the target profile template selected by the user and the user information.

[0201] In another example, when the user clicks the "Log in" control shown in (a) of Figure 6 , the cloud desktop log-in interface as shown in (a) of Figure 7 is displayed. After the user clicks the identifier of the profile template in the profile template display interface and clicks the "Confirm" control shown in (b) of Figure 7 , the client displays the cloud desktop log-in interface as shown in (b) of Figure 6 . Figure 6 When the user clicks the "Log in" control shown in (a) of Figure 6 , the cloud desktop log-in interface as shown in (a) of Figure 7 is displayed. After the user clicks the identifier of the profile template in the profile template display interface and clicks the "Confirm" control shown in (b) of Figure 7 , the client displays the cloud desktop log-in interface as shown in (b) of Figure 6 . Figure 7 After the user clicks the identifier of the profile template in the profile template display interface and clicks the "Confirm" control shown in (b) of Figure 7 , the client displays the cloud desktop log-in interface as shown in (b) of Figure 6 . Figure 7 After the user clicks the identifier of the profile template in the profile template display interface and clicks the "Confirm" control shown in (b) of Figure 7 , the client displays the cloud desktop log-in interface as shown in (b) of Figure 6 . Figure 6 After the user clicks the identifier of the profile template in the profile template display interface and clicks the "Confirm" control shown in (b) of Figure 7 , the client displays the cloud desktop log-in interface as shown in (b) of Figure 6 .

[0202] In the embodiments of the present application, the client receives the data of the cloud desktop sent by the cloud server and displays the cloud desktop interface as shown in Figure 8 . The icons of cloud applications are displayed in the cloud desktop interface. Figure 8 In the embodiments of the present application, the client receives the data of the cloud desktop sent by the cloud server and displays the cloud desktop interface as shown in Figure 8 . The icons of cloud applications are displayed in the cloud desktop interface.

[0203] It should be noted that the above mainly takes the cloud desktop log-in scenario as an example and introduces the method provided by the embodiments of the present application from the perspective of the interaction between the cloud desktop server and the client. It can be understood that the method provided by the embodiments of the present application can also be applied to the cloud application log-in scenario. In the cloud application log-in scenario, the client interacts with the cloud application server. When the client logs in to the cloud application server for the first time, the cloud application server executes the embodiments provided above to achieve the fast log-in of cloud applications. Figure 3 When the client logs in to the cloud application server for the first time, the cloud application server executes the embodiments provided above to achieve the fast log-in of cloud applications.

[0204] The above mainly introduces the method provided by the embodiments of the present application from the perspective of the interaction between the cloud desktop server and the client. It can be understood that the cloud desktop server includes the corresponding hardware structure and / or software module for executing each function. Those skilled in the art can easily realize that, in combination with the algorithm steps of each example described in the embodiments disclosed in the present application, the present application can be implemented in the form of hardware or the combination of hardware and computer software. Whether a certain function is executed in the way of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Professional technicians can use different methods to implement the described function for each specific application, but such implementation should not be considered to exceed the scope of the present application.

[0205] In the embodiments of the present application, the function modules of the cloud desktop server can be grouped according to the above method examples. For example, each function module can correspond to each function group, or two or more functions can be integrated into one processing module. The above integrated module can be implemented in the form of hardware or in the form of a software function module. It should be noted that the naming and grouping of the modules in the embodiments of the present application are illustrative, only a logical function grouping, and there can be other grouping methods in actual implementation.

[0206] For example, the cloud desktop server can also be named as a cloud desktop login device. As Figure 9 shown, Figure 9 FIG. 12 is a schematic structural diagram of a cloud desktop login device 12 provided by an embodiment of the present application. The shown cloud desktop login device 12 includes:

[0207] A communication module 121, configured to receive a login request sent by a client. Among them, the login request includes user information. For example, the communication module 121 is configured to execute Figure 3 step S320 in

[0208] A template acquisition module 122, configured to determine a target configuration file template from at least one configuration file template in response to the login request. Among them, the target configuration file template is used to indicate the user environment of the cloud desktop. The creation time of at least one configuration file template is earlier than the time of obtaining the login request. For example, the template acquisition module 122 is configured to execute Figure 3 step S330 in the above

[0209] A template modification module 123, configured to modify the target configuration file template based on the user information to obtain a configuration file corresponding to the user information. For example, the template modification module is configured to execute Figure 3 step S340 in the above

[0210] An operation module 124, configured to log in to the user's cloud desktop by using the configuration file. For example, the operation module 124 is configured to execute Figure 3 step S350 in the above

[0211] Among them, the communication module 121, the template acquisition module 122, the template modification module 123, and the operation module 124 can all be implemented by software or by hardware. Exemplarily, next, taking the communication module 121 as an example, the implementation manner of the communication module 121 is introduced. Similarly, the template acquisition module 122, the template modification module 123, and the operation module 124 can refer to the implementation manner of the communication module 121.

[0212] As an example of a software functional unit, the communication module 121 may include code running on a computing instance. The computing instance may include at least one of a physical host (computing device), a virtual machine, and a container. Further, the above computing instance may be one or more. For example, the communication module 121 may include code running on multiple hosts / virtual machines / containers. It should be noted that the multiple hosts / virtual machines / containers for running the code may be distributed in the same region or in different regions. Further, the multiple hosts / virtual machines / containers for running the code may be distributed in the same availability zone (AZ) or in different AZs. Each AZ includes one data center or multiple geographically proximate data centers. Usually, one region may include multiple AZs.

[0213] Similarly, the multiple hosts / virtual machines / containers for running the code may be distributed in the same virtual private cloud (VPC) or in multiple VPCs. Usually, one VPC is set within one region. For cross-region communication between two VPCs within the same region and between VPCs in different regions, a communication gateway needs to be set in each VPC, and the interconnection between VPCs is achieved through the communication gateway.

[0214] As an example of a hardware functional unit, the communication module 121 may include at least one computing device, such as a server, etc. Or, the communication module 121 may also be a device implemented by an application-specific integrated circuit (ASIC) or a programmable logic device (PLD). Among them, the above PLD may be implemented by a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL), or any combination thereof.

[0215] The multiple computing devices included in the communication module 121 can be distributed in the same region or in different regions. The multiple computing devices included in the communication module 121 can be distributed in the same AZ or in different AZs. Similarly, the multiple computing devices included in the communication module 121 can be distributed in the same VPC or in multiple VPCs. Among them, the multiple computing devices can be any combination of computing devices such as servers, ASICs, PLDs, CPLDs, FPGAs, and GALs.

[0216] It should be noted that, in other embodiments, the communication module 121 can be used to execute any step in the cloud desktop login method. The template acquisition module 122 can be used to execute any step in the cloud desktop login method. The template modification module 123 can be used to execute any step in the cloud desktop login method. The operation module 124 can be used to execute any step in the cloud desktop login method. The steps to be implemented by the communication module 121, the template acquisition module 122, the template modification module 123, and the operation module 124 can be specified as needed. The cloud desktop login device 12 realizes all its functions by implementing different steps in the cloud desktop login method through the communication module 121, the template acquisition module 122, the template modification module 123, and the operation module 124 respectively.

[0217] The embodiment of the present application provides a cloud desktop login system 13 provided with Figure 9 the cloud desktop login device 12 provided. As Figure 10 shown, Figure 10 is a schematic structural diagram of the cloud desktop login system 13 provided by the embodiment of the present application. The shown cloud desktop login system 13 includes:

[0218] A client 20, configured to send a login request to the cloud desktop login device 12 and display a cloud desktop interface based on the data of the cloud desktop sent by the cloud desktop login device 12. Among them, the login request carries user information. For example, the client 20 executes Figure 3 the step S310 in

[0219] The cloud desktop login device 12 is configured to receive the login request sent by the client 20; in response to the login request, determine a target configuration file template from at least one configuration file template. Modify the target configuration file template based on the user information to obtain a configuration file corresponding to the user information. Use the configuration file to log in to the user's cloud desktop. Send the data of the cloud desktop to the client 20. Among them, the target configuration file template is used to indicate the desktop environment of the cloud desktop, and the creation time of at least one configuration file template is earlier than the time when the login request is obtained. For example, the cloud desktop login device executes Figure 3 the steps S320 to S350 in

[0220] Among them, both the cloud desktop login device 12 and the client 20 can be implemented by software or by hardware. Exemplarily, the implementation manner of the cloud desktop login device 12 will be introduced next. Similarly, the implementation manner of the client 20 can refer to the implementation manner of the cloud desktop login device 12.

[0221] As an example of a software functional unit, the cloud desktop login device 12 may include code running on a computing instance. Among them, the computing instance may be at least one of computing devices such as a physical host (computing device), a virtual machine, a container, etc. Further, the above computing devices may be one or more. For example, the cloud desktop login device 12 may include code running on multiple hosts / virtual machines / containers. It should be noted that the multiple hosts / virtual machines / containers for running the application may be distributed in the same region or in different regions. The multiple hosts / virtual machines / containers for running the code may be distributed in the same AZ or in different AZs, and each AZ includes one data center or multiple geographically proximate data centers. Among them, generally one region may include multiple AZs.

[0222] Similarly, the multiple hosts / virtual machines / containers for running the code may be distributed in the same VPC or in multiple VPCs. Among them, generally one VPC is set within one region. For cross-region communication between two VPCs within the same region and between VPCs in different regions, a communication gateway needs to be set in each VPC, and the interconnection between VPCs is achieved through the communication gateway.

[0223] As an example of a hardware functional unit, the cloud desktop login device 12 may include at least one computing device, such as a server, etc. Or, the cloud desktop login device 12 may also be a device implemented by ASIC or PLD, etc. Among them, the above PLD may be implemented by CPLD, FPGA, GAL or any combination thereof.

[0224] The multiple computing devices included in the cloud desktop login device 12 may be distributed in the same region or in different regions. The multiple computing devices included in the cloud desktop login device 12 may be distributed in the same AZ or in different AZs. Similarly, the multiple computing devices included in the cloud desktop login device 12 may be distributed in the same VPC or in multiple VPCs. Among them, the multiple computing devices may be any combination of computing devices such as servers, ASICs, PLDs, CPLDs, FPGAs, and GALs.

[0225] The embodiment of the present application further provides a computing device 14 for executing the above cloud desktop login method.

[0226] In one example, the computing device 14 may include a cloud desktop login device 12 as shown in Figure 9 FIG. The cloud desktop login device 12 includes a communication module 121, a template acquisition module 122, a template modification module 123, and an operation module 124.

[0227] In another example, the computing device 14 may include a cloud desktop login system 13 as shown in Figure 10 FIG. The cloud desktop login system 13 includes a cloud desktop login device 12 and a client 20.

[0228] In yet another example, as shown in Figure 11 FIG., the computing device 14 includes: a bus 142, a processor 144, a memory 146, and a communication interface 148. The processor 144, the memory 146, and the communication interface 148 communicate with each other through the bus 142. The computing device 14 may be a server or a terminal device. It should be understood that the present application does not limit the number of processors 144 and memories 146 in the computing device 14.

[0229] The bus 142 may be a peripheral component interconnect (PCI) bus, an extended industry standard architecture (EISA) bus, or the like. The bus may be divided into an address bus, a data bus, a control bus, etc. For the sake of simplicity of representation, Figure 11 only one line is shown in FIG., but it does not mean that there is only one bus or one type of bus. The bus 142 may include a path for transmitting information between various components of the computing device 14 (for example, the memory 146, the processor 144, the communication interface 148).

[0230] The processor 144 may include any one or more of a central processing unit (CPU), a graphics processing unit (GPU), a microprocessor (MP), or a digital signal processor (DSP).

[0231] In the present application, the processor 144 executes the method shown in Figure 3 FIG. For example, receiving a login request sent by a client. In response to the login request, determining a target configuration file template from at least one configuration file template. Modifying the target configuration file template based on user information to obtain a configuration file corresponding to the user information. Using the configuration file to log in to the cloud desktop server.

[0232] In an embodiment of the present application, the processor 144 executes the above Figure 2 shown method. For example, at least one simulated user is created, the login operations of each simulated user are executed, and a configuration file template for each simulated user is created.

[0233] The memory 146 may include volatile memory, such as random access memory (RAM). The processor 144 may also include non-volatile memory, such as read-only memory (ROM), flash memory, hard disk drive (HDD), or solid state drive (SSD).

[0234] The memory 146 stores executable program code, and the processor 144 executes the executable program code to respectively implement the functions of the foregoing communication module 121, template acquisition module 122, and template modification module 123, thereby implementing the cloud desktop login method. That is, the memory 146 stores instructions for executing the cloud desktop login method.

[0235] In an embodiment of the present application, the memory 146 stores a configuration file template for a simulated user.

[0236] The communication interface 148 uses a transceiver module such as, but not limited to, a network interface card or a transceiver to implement communication between the computing device 14 and other devices or communication networks.

[0237] The cloud desktop login method disclosed in the above method embodiment can be applied to or implemented by the processor 144. The processor 144 may be an integrated circuit chip with signal processing capabilities.

[0238] In the implementation process, each step of the above method can be completed by the integrated logic circuit of the hardware in the processor 144 or the instructions in the form of software. The above-mentioned processor 144 can be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it can also be a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, discrete electron tubes or transistor logic devices, discrete hardware components. It can implement or execute the various methods, steps and logic block diagrams disclosed in the embodiments of the present application. The general-purpose processor can be a microprocessor or the processor can also be any conventional processor, etc. The steps of the method disclosed in combination with the embodiments of the present application can be directly embodied as being executed and completed by the hardware decoding processor, or executed and completed by a combination of the hardware and software modules in the decoding processor. The software module can be located in a mature storage medium in the art such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, etc. This storage medium is located in the memory 146, and the processor 144 reads the information in the memory 146 and combines its hardware to complete the steps of the above method.

[0239] In a possible implementation manner, the processor 144 can also be used to execute the cloud desktop login method. For the specific implementation, reference can be made to the embodiments provided in the above cloud desktop login method, and the embodiments of the present application will not be elaborated herein.

[0240] In the embodiments of the present application, the chip system can be composed of chips or can also include chips and other discrete devices.

[0241] The embodiments of the present application also provide a computing device cluster 15 for executing the above cloud desktop login method.

[0242] In one example, the computing device cluster 15 may include, as Figure 9 shown, the cloud desktop login device 12. The cloud desktop login device 12 includes a communication module 121, a template acquisition module 122, and a template modification module 123.

[0243] In another example, as Figure 12 shown, the computing device cluster 15 includes at least one computing device 14 as Figure 11 shown. The computing device 14 includes: a bus 142, a processor 144, a memory 146, and a communication interface 148. The processor 144, the memory 146, and the communication interface 148 communicate with each other through the bus 142. The computing device 14 can be a server or a terminal device.

[0244] In a possible implementation, one or more computing devices in a computing device cluster can be connected via a network. Among them, the network can be a wide area network or a local area network, etc. Figure 13 A possible implementation is shown. As Figure 13 shown, two computing devices 14A and 14B are connected via a network. Specifically, they are connected to the network through the communication interfaces in each computing device. In this type of possible implementation, the memory 146 in computing device 14A stores instructions for executing the functions of the communication module 121 and the running module 124. At the same time, the memory 146 in computing device 14B stores instructions for executing the functions of the template acquisition module 122 and the template modification module 123.

[0245] Figure 13 The connection method between the computing device clusters shown can be considered in view of the cloud desktop login method provided in this application. It is necessary to store configuration file templates of multiple simulated users and configuration files of different users, which requires a large amount of data storage, and running the cloud desktop requires computing resources. Therefore, it is considered that the functions implemented by the template acquisition module 122 and the template modification module 123 are executed by computing device 14B. The functions implemented by the communication module 121 and the running module 124 are executed by computing device 14A.

[0246] It should be understood that Figure 13 the functions of computing device 14A shown can also be completed by multiple computing devices 14. Similarly, the functions of computing device 14B can also be completed by multiple computing devices 14.

[0247] The embodiments of this application also provide a computer program product containing instructions. The computer program product can be software or a program product containing instructions that can run on a computing device or be stored in any available medium. When the computer program product runs on at least one computing device, it causes at least one computing device to execute the above-mentioned cloud desktop login method.

[0248] For example, when the computer program product runs on at least one computing device, it causes at least one computing device to execute Figure 3 the cloud desktop login method shown.

[0249] The embodiments of the present application also provide a computer-readable storage medium. All or part of the processes in the above method embodiments can be completed by a computer program instructing relevant hardware. This program can be stored in the above computer-readable storage medium. When this program is executed, it can include the processes of the above method embodiments. The computer-readable storage medium can be the terminal in any of the foregoing embodiments, such as an internal storage unit including a data transmission end and / or a data reception end, for example, the hard disk or memory of the terminal. The above computer-readable storage medium can also be an external storage device of the above terminal, such as a plug-in hard disk, a smart media card (SMC), a secure digital (SD) card, a flash card, etc. equipped on the above terminal. Further, the above computer-readable storage medium can also include both the internal storage unit and the external storage device of the above terminal. The above computer-readable storage medium is used to store the above computer program and other programs and data required by the above terminal. The above computer-readable storage medium can also be used to temporarily store the data that has been output or will be output.

[0250] It should be understood that in the technical solution of the present application, the collection, storage, use, processing, transmission, provision, and disclosure of the user's personal information and other processes all comply with relevant laws and regulations and do not violate public order and good customs. For example, in the technical solution of the present application, the processing of the user's personal information is carried out under the authorization of the user. The same is explained here and will not be repeated below.

[0251] It should be noted that the terms "first" and "second" in the specification, claims, and drawings of the present application are used to distinguish different objects, rather than to describe a specific order. In addition, the terms "include" and "have" and any variations thereof are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or device that includes a series of steps or units is not limited to the listed steps or units, but optionally further includes steps or units that are not listed, or optionally further includes other steps or units inherent to these processes, methods, products, or devices.

[0252] It should be understood that in this application, "at least one (item)" means one or more, "a plurality" means two or more, "at least two (items)" means two or three or more, and "and / or" is used to describe the association relationship of associated objects, indicating that three relationships can exist. For example, "A and / or B" can mean: only A exists, only B exists, and both A and B exist at the same time. Here, A and B can be singular or plural. The character " / " generally indicates that the associated objects before and after are in an "or" relationship. "At least one (item) of the following" or its similar expressions refer to any combination of these items, including any combination of single item (item) or plural items (items). For example, at least one (item) of a, b, or c can mean: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, c can be single or multiple.

[0253] It should be understood that in the embodiments of this application, "B corresponding to A" means that B is associated with A. For example, B can be determined according to A. It should also be understood that determining B according to A does not mean determining B only according to A, and B can also be determined according to A and / or other information. In addition, the "connection" that appears in the embodiments of this application refers to various connection methods such as direct connection or indirect connection to achieve communication between devices, and this application does not make any limitations on this.

[0254] Unless otherwise specified, the "transmission" (transmit / transmission) that appears in the embodiments of this application refers to two-way transmission, including the actions of sending and / or receiving. Specifically, the "transmission" in the embodiments of this application includes the sending of data, the receiving of data, or the sending and receiving of data. Or rather, the data transmission here includes uplink and / or downlink data transmission. Data can include channels and / or signals. Uplink data transmission is the transmission of uplink channels and / or uplink signals, and downlink data transmission is the transmission of downlink channels and / or downlink signals. The "network" and "system" that appear in the embodiments of this application express the same concept, and an all-optical network is an all-optical system.

[0255] Through the description of the above embodiments, those skilled in the art can clearly understand that for the convenience and simplicity of description, only the grouping of the above functional modules is used as an example. In actual applications, the above functions can be allocated to different functional modules according to needs, that is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above.

[0256] In several embodiments provided by the present application, it should be understood that the disclosed cloud desktop login device and method can be implemented in other ways. For example, the cloud desktop login device embodiments described above are merely illustrative. For example, the grouping of modules or units is only a logical function grouping. In actual implementation, there may be other grouping methods. For example, multiple units or components can be combined or integrated into another device, or some features can be ignored or not executed. Another point is that the displayed or discussed couplings or direct couplings or communication connections to each other can be through some interfaces. The indirect couplings or communication connections of devices or units can be in electrical, mechanical or other forms.

[0257] The units described as separate components may or may not be physically separated. The components displayed as units may be one physical unit or multiple physical units, that is, they can be located in one place, or they can be distributed to multiple different places. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0258] In addition, in each embodiment of the present application, each functional unit can be integrated in a processing unit, or each unit can exist physically alone, or two or more units can be integrated in one unit. The above-mentioned integrated units can be implemented in the form of hardware or in the form of software functional units.

[0259] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium. Based on such an understanding, the technical solution of the embodiments of the present application, in essence, or the part that contributes to the prior art, or all or part of this technical solution, can be embodied in the form of a software product. This software product is stored in a storage medium and includes several instructions to enable a device, such as a single-chip microcomputer, a chip, etc., or a processor to execute all or part of the steps of the methods in the various embodiments of the present application. The foregoing storage medium includes various media for storing program codes, such as USB flash drives, mobile hard disks, ROM, RAM, magnetic disks or optical discs.

[0260] The above is only the specific implementation manner of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art can easily think of changes or substitutions within the technical scope disclosed by the present application, and all should be covered by the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims

1. A cloud desktop login method, characterized in that: The cloud desktop system includes a cloud server and a client, wherein the cloud server stores at least one configuration file template of the cloud desktop; The method is performed by the cloud server, and the method includes: receiving a login request sent by the client; the login request includes user information of the user; In response to the login request, determining a target configuration file template from the at least one configuration file template; the target configuration file template is used to indicate a user environment of the cloud desktop; the creation time of the at least one configuration file template is earlier than the time when the login request is obtained; Modify the target configuration file template based on the user information to obtain a configuration file corresponding to the user information; The configuration file is used to log in to the user's cloud desktop.

2. The method according to claim 1, characterized in that The step of modifying the target configuration file template based on the user information to obtain a configuration file corresponding to the user information includes: The target configuration file template, a registration table associated with the target configuration file template, and access rights of the target configuration file template are modified according to the user information to obtain a configuration file corresponding to the user information.

3. The method according to claim 2, characterized in that The user information includes a user name, a security identifier SID and a global security identifier GUID; The step of modifying the target configuration file template, a registry associated with the target configuration file template, and access rights of the target configuration file template according to the user information to obtain a configuration file corresponding to the user information includes: Modify the file name of the target configuration file template to the user name included in the user information; Modify the calling path of the target configuration file template in the registration table according to the user name; Modify the SID and GUID in the registry to the SID and GUID included in the user information; The access permission of the target configuration file template is modified according to the user name to obtain a configuration file corresponding to the user information.

4. The method according to any one of claims 1 to 3, characterized in that The user information includes configuration information; The modifying the target configuration file template based on the user information includes: The configuration in the target configuration file template is modified according to the configuration information included in the user information.

5. The method according to any one of claims 1 to 4, characterized in that The user information also includes user authority; and determining a target configuration file template from the at least one configuration file template includes: The target configuration file template matching the user authority is obtained from the at least one configuration file template.

6. The method according to any one of claims 1 to 4, characterized in that The login request also includes an identification of a target configuration file template; The determining a target configuration file template from the at least one configuration file template comprises: The target configuration file template indicated by the identifier is acquired from the at least one configuration file template; the target configuration file template indicated by the identifier is obtained by the client through a response configuration file template operation.

7. The method according to any one of claims 1 to 6, characterized in that After logging into the user's cloud desktop using the configuration file, the method further includes: The data of the cloud desktop is sent to the client, and the data of the cloud desktop is used for the client to display a cloud desktop interface.

8. The method according to any one of claims 1 to 7, characterized in that: The determining a target configuration file template from the at least one configuration file template comprises: When it is determined that the user logs in for the first time, a target configuration file template is determined from the at least one configuration file template.

9. The method according to any one of claims 1 to 7, characterized in that: After modifying the configuration file template based on the user name to obtain the configuration file corresponding to the user information, the method further includes: Create a new configuration file template.

10. The method according to any one of claims 1 to 8, characterized in that: Before receiving the login request sent by the client, the method further includes: At least one simulated user is created, a login operation of each simulated user is performed, and a configuration file template of each simulated user is created.

11. A cloud desktop login device, characterized in that: The cloud desktop login device comprises: A communication module, used to receive a login request sent by a client; the login request includes user information; A template acquisition module, used to determine a target configuration file template from at least one configuration file template in response to the login request; the target configuration file template is used to indicate a user environment of the cloud desktop; the creation time of the at least one configuration file template is earlier than the time when the login request is acquired; A template modification module, used to modify the target configuration file template based on the user information to obtain a configuration file corresponding to the user information; The running module is used to log in to the cloud desktop of the user using the configuration file.

12. The device according to claim 11, characterized in that The template modification module is used to modify the target configuration file template, the registration table associated with the target configuration file template, and the access rights of the target configuration file template according to the user information to obtain the configuration file corresponding to the user information.

13. The device according to claim 12, characterized in that The user information includes a user name, a security identifier SID and a global security identifier GUID; the template modification module is used to modify the file name of the target configuration file template to the user name included in the user information; modify the calling path of the target configuration file template in the registry according to the user name; modify the SID and GUID in the registry to the SID and GUID included in the user information; modify the access rights of the target configuration file template according to the user name, and obtain the configuration file corresponding to the user information.

14. The device according to any one of claims 11 to 13, characterized in that The user information includes configuration information; the template modification module is further used to modify the configuration in the target configuration file template according to the configuration information included in the user information.

15. The device according to any one of claims 11 to 14, characterized in that The user information also includes user rights, and the template acquisition module is used to acquire the target configuration file template that matches the user rights from the at least one configuration file template.

16. The device according to any one of claims 11 to 14, characterized in that The login request received by the communication module also includes an identifier of a configuration file template; the identifier of the configuration file template is used to indicate the configuration file template selected by the client in response to the configuration file template selection operation; The template acquisition module is used to acquire a target configuration file template that matches the identifier of the configuration file template from the at least one configuration file template.

17. The device according to any one of claims 11 to 16, characterized in that After the operation module uses the configuration file to log in to the user's cloud desktop, the communication module is further used to send the data of the cloud desktop to the client, and the data of the cloud desktop is used for the client to display the cloud desktop interface.

18. The device according to any one of claims 11 to 17, characterized in that The template acquisition module is further configured to determine a target configuration file template from the at least one configuration file template when it is determined that the user is logging in for the first time.

19. The device according to any one of claims 11 to 18, characterized in that The template modification module modifies the configuration file template based on the user name. After obtaining the configuration file corresponding to the user information, the device is further used to create a new configuration file template.

20. The device according to any one of claims 11 to 19, characterized in that Before the communication module receives the login request sent by the client, the device is further used to create at least one simulated user, execute a login operation for each simulated user, and create a configuration file template for each simulated user.

21. A computing device cluster, characterized in that: comprising at least one computing device, each computing device comprising a processor and a memory; The processor of the at least one computing device is configured to execute instructions stored in the memory of the at least one computing device, so that the computing device cluster executes the method according to any one of claims 1 to 10.

22. A computer program product comprising instructions, characterized in that When the instruction is executed by a computing device cluster, the computing device cluster executes the method as claimed in any one of claims 1 to 10; or when the instruction is executed by a computing device, the computing device executes the method as claimed in any one of claims 1 to 10.

23. A computer-readable storage medium, characterized in that: The method comprises computer program instructions, and when the computer program instructions are executed by a computing device cluster, the computing device cluster performs the method according to any one of claims 1 to 10.

Images