Cloud desktop multi-connection method based on virtual device grouping

Abstract

The present application relates to the technical field of IT and software development. Disclosed are a cloud desktop multi-connection method based on virtual device grouping, which method aims to solve the problem of resource waste due to the fact that a resource utilization rate is very low and it is difficult to maximally use all CPUs and memory resources when same are used for office use only. The key points of the technical solution comprise: S1, increasing the number of virtual devices in a cloud desktop starting configuration file; S2, in a virtual machine starting stage, renaming a device DeviceType.DeviceID.GroupID and storing same; S3, a cloud desktop server updating device information of a corresponding group in a timely manner on the basis of the names of the devices; S4, when a user uses a cloud desktop client to connect a cloud desktop, the cloud desktop server verifying a connection request, a connection encryption certificate and a cloud desktop account password; and S5, after a plurality of cloud desktop users log in to the same cloud desktop, using different virtual device groups and sharing a CPU and memory resources of the cloud desktop. The effect of maximizing an energy resource utilization rate is achieved.

Description

A cloud desktop multi-connection method based on virtual device grouping

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to the Chinese patent application filed with the China Patent Office on December 13, 2023, with application number 202311712676.9 and invention name “A cloud desktop multi-connection method based on virtual device grouping”, the entire contents of which are incorporated by reference in this application. Technical Field

[0003] The present application relates to the field of IT and software development technology, and in particular to a cloud desktop multi-connection method based on virtual device grouping. Background Art

[0004] Currently in the field of cloud computing, virtualization technology can be used to abstract various physical resources of the original computer, such as CPU, memory, graphics card, disk, and various peripherals, through pure software or a combination of software and hardware. The corresponding functions are virtually realized, and virtual devices with corresponding functions are combined and provided to users. From the user's point of view, there is not much difference between the use of virtual computers and physical computers.

[0005] Currently, computer systems implemented through virtualization technology are called cloud desktops or cloud computers. In this application, they are collectively referred to as cloud desktops. Since cloud desktops are virtualized from servers in the cloud, users who want to operate cloud desktops locally must first connect to the server before they can see the cloud desktop screen through the local display and operate the cloud desktop with the mouse and keyboard. Only through the cloud desktop can they use local peripherals such as cameras, USB flash drives, printers, and scanners.

[0006] In fact, in addition to the CPU and memory, virtual devices related to user input and output, such as graphics cards and peripherals, in the cloud desktop all need to have real or logical channel connections with the user's local display and physical peripherals. For example, when a user plugs a USB flash drive into a local USB port, the cloud computer will see a USB flash drive plugged into the cloud computer. This is because we have established a unique correspondence between the local USB flash drive and the virtual USB flash drive in the cloud desktop. When operating the data in the USB flash drive in the cloud computer, it will be synchronized to our local physical USB flash drive in real time. Similar to physical machines, in the existing technology, cloud desktops are usually equipped with a variety of peripheral interfaces, allowing users to easily plug in the devices they need. In this way, a group of virtual devices need to establish a one-to-one connection relationship with local physical devices.

[0007] The above-mentioned existing technical solutions have the following defects: Currently, a cloud desktop is only used by one user to log in. Usually, the configuration of this cloud desktop can be a 4-core CPU, 8GB of memory, or an 8-core CPU, 16GB of memory. If the user only uses it for office use, the resource utilization rate is actually very low, and it is difficult to maximize the utilization of all CPU and memory resources, resulting in a waste of resources. Summary of the Invention

[0008] The purpose of this application is to provide a cloud desktop multi-connection method based on virtual device grouping, which enables different users to use completely different virtual devices when connecting to the same cloud desktop without interfering with each other.

[0009] To achieve the above objectives, this application provides the following technical solutions:

[0010] A cloud desktop multi-connection method based on virtual device grouping is as follows:

[0011] S1: Increase the number of virtual devices in the cloud desktop startup configuration file;

[0012] S2: During the virtual machine startup phase, the cloud desktop server renames the device to DeviceType.DeviceID.GroupID based on the type of each virtual device (DeviceType), device serial number (DeviceID), and group (GroupID), and stores it.

[0013] S3: When virtual devices are hot-swapped, added, or removed, the cloud desktop server promptly updates the device information of the corresponding group based on the device name;

[0014] S4: When a user uses a cloud desktop client to connect to a cloud desktop, the cloud desktop server verifies the connection encryption certificate and the cloud desktop account password for the connection request;

[0015] S5: Multiple cloud desktop users log in to the same cloud desktop, use different virtual device groups, and share the CPU and memory resources of the cloud desktop.

[0016] Optionally, the specific step of S1 is to assume that there are t types of virtual devices M1, M2..., Mt in the original cloud desktop, and each type of device has M1a, M2b..., Mtq, that is, a total of M1a+M2b+...+Mtq=M virtual devices.

[0017] Optionally, if the cloud desktop is allocated to N users in S1, the number of virtual devices is increased to M*N, which is equivalent to configuring N groups of identical virtual devices in the cloud desktop, and each cloud desktop can be connected to by N users at the same time.

[0018] Optionally, M in S1 is the number of cloud desktop virtual devices configured for each user, which is determined by actual usage requirements.

[0019] Optionally, N in S1 is the number of users that each desktop can serve simultaneously, which is determined by the cloud desktop specifications and the resources used by each user. N can be adjusted dynamically, that is, if the average resource requirements of each user increase, then N is reduced, and fewer users log in to the same desktop.

[0020] Optionally, if the average resource usage of each user in S1 is very low, then N is increased to allow more users to log in to one desktop at the same time.

[0021] Optionally, after the devices are renamed in S2, the devices in the same group are linked together, and the device information is stored in a database.

[0022] Optionally, the database is updated after the device information of the corresponding group is updated in S3.

[0023] Optionally, S4 adds a new verification of the validity of GroupID. If it is illegal, the cloud desktop client will be offline. If it is legal, the corresponding virtual device group will be found from the virtual device management relationship, such as from the database, and the connection channel corresponding to the virtual device group will be sent to the cloud desktop client.

[0024] Optionally, when the cloud desktop users in S5 use office suites, browse the web, use cameras, USB flash drives, printers and other peripherals for normal office work, they do not affect each other.

[0025] In summary, the beneficial technical effects of this application are:

[0026] 1. This application proposes a grouping concept called GroupID, which groups different types of devices into the same group. During use, devices can be searched and managed based on the group information proposed in this application. This also allows for searching by device type in existing technologies. This improves existing technologies that cannot distinguish between certain types of virtual devices or can only search by type. Furthermore, existing technologies cannot enable different users to use completely different virtual devices when connecting to the same cloud desktop without interfering with each other.

[0027] 2. This application adds a connection request to the existing connection process to identify the group number GroupID. The cloud desktop server can quickly find the group of devices that the user needs to connect to based on the GroupID, and send the corresponding channel information to the user. Specifically, the cloud desktop management system will assign a cloud desktop to each user. The allocation granularity is based on the desktop group number GroupID. When the user uses the cloud desktop client to connect, in addition to the existing desktop information, it will also provide the GroupID to the cloud desktop server. In addition to normal authentication of desktop information, the cloud desktop server will also verify whether the GroupID is legal. If it is legal, it will send the channel information corresponding to the corresponding virtual device group to the cloud desktop client. The cloud desktop client connects to the corresponding virtual device. Different users will not interfere with each other when logging in at the same time. Although different users are in the same cloud desktop, they do not know each other's existence because the images they see and the virtual devices they use are different. However, since they share the same CPU and memory resources, the CPU and memory resource usage of the entire cloud desktop will be maintained at a high level. Given that users are using it for office work and are simply typing and browsing the web, they will not place high demands on CPU and memory resources.

[0028] 3. This application solves the problem that in simple office scenarios using cloud desktops, the CPU and memory usage of cloud desktops are low, resulting in low overall utilization of cloud server resources. On the premise of sharing the same cloud desktop CPU and memory resources, multiple sets of virtual devices are configured in one cloud desktop, and the concept of groups is introduced to effectively manage these virtual devices. In addition, group verification and identification are added during the connection process of the cloud desktop client, so that different cloud desktop clients can connect to different device groups in the same cloud desktop. This solves the current situation in the prior art that a cloud desktop can only be used by one user, and ultimately enables multiple users to use one cloud desktop, thereby improving the resource utilization of the cloud desktop and correspondingly improving the resource utilization of the entire cloud server, maximizing the utilization of energy resources, and maximizing the utilization of cloud computing computing power. BRIEF DESCRIPTION OF THE DRAWINGS

[0029] FIG1 is a schematic diagram of the overall structure of the prior art;

[0030] Figure 2 is a schematic diagram of the overall structure of this application;

[0031] Figure 3 is a schematic diagram of the cloud desktop configuration and connection process for this application. DETAILED DESCRIPTION

[0032] The present application method is further described in detail below with reference to the accompanying drawings.

[0033] Example 1

[0034] Referring to FIG2 , a cloud desktop multi-connection method based on virtual device grouping is as follows:

[0035] S1: Increase the number of virtual devices in the cloud desktop startup configuration file. Assume that there are t types of virtual devices in the original cloud desktop, M1, M2, ..., Mt, and each type of device has M1a, M2b, ..., Mtq, that is, M1a+M2b+...+Mtq=M virtual devices in total. If this cloud desktop is allocated to N users, then the number of virtual devices is increased to M*N, which is equivalent to configuring N groups of identical virtual devices in the cloud desktop. Each cloud desktop can be connected to N users simultaneously. M is the number of cloud desktop virtual devices configured for each user, which is determined by actual usage requirements. N is the number of users that can be served simultaneously by each desktop, which is determined by the cloud desktop specifications and the resources used by each user. N can be adjusted dynamically. That is, if the average resource requirement of each user increases, then N is reduced, and fewer users log in to the same desktop. If the average resource usage of each user is very low, then N is increased, allowing more users to log in to the same desktop simultaneously.

[0036] S2: During the virtual machine startup phase, the cloud desktop server renames the device to DeviceType.DeviceID.GroupID based on the type of each virtual device (DeviceType), device serial number (DeviceID), and group (GroupID), and stores the information. After the device is renamed, the devices in the same group are linked and the device information is stored in the database.

[0037] S3: When virtual devices are hot-swapped, added, or removed, the cloud desktop server promptly updates the device information of the corresponding group based on the device name, and then updates the database after updating the device information of the corresponding group;

[0038] Referring to Figure 3, S4: When the user uses the cloud desktop client to connect to the cloud desktop, the cloud desktop server verifies the connection encryption certificate and the cloud desktop account password for the connection request, and adds a new verification of the legitimacy of the GroupID. If it is not legal, the cloud desktop client is offline. If it is legal, the corresponding virtual device group is found from the virtual device management relationship, such as from the database, and the connection channel corresponding to the virtual device group is sent to the cloud desktop client;

[0039] S5: Multiple cloud desktop users log in to the same cloud desktop, use different virtual device groups, and share the cloud desktop's CPU and memory resources. When each cloud desktop user uses the office suite, browses the web, and uses peripherals such as cameras, USB flash drives, and printers to perform normal office work, they do not affect each other.

[0040] Example 2

[0041] This application is applicable to simple office scenarios on cloud desktops, when a single user does not have high CPU and memory usage on the cloud desktop. In order to improve the resource utilization efficiency of the cloud desktop, the number of virtual devices is increased in a cloud desktop. The original cloud desktop has M virtual devices, including M1, M2..., Mt, a total of t types of virtual devices, and each type of device has M1a, M2b..., Mtq, that is, a total of M1a+M2b+...+Mtq=M virtual devices. Now, if we want to allocate this cloud desktop to N users, we need to increase the number of virtual devices to M*N. This is equivalent to configuring N groups of identical virtual devices in the cloud desktop. Each cloud desktop can be connected to by N users at the same time, and they each use different M virtual devices in the cloud desktop. The structural diagram is shown in Figure 2, where Y is the number of cloud desktops that the cloud server can provide, which is determined by the specifications of the cloud server. M is the number of cloud desktop virtual devices configured for each user, which is determined by actual usage needs. N is the number of users that each desktop can serve simultaneously, which is determined by the cloud desktop specifications and the resources used by each user. N can be adjusted dynamically. That is, if the average resource requirements of each user increase, then reduce N, and fewer users will log in to the same desktop. On the contrary, if the average resource usage of each user is very low, then increase N to allow more users to log in to the same desktop at the same time.

[0042] When a cloud desktop user uses a cloud desktop client to connect to a cloud desktop, the cloud desktop server, in addition to normal authentication of desktop information, adds a judgment on the GroupID to verify whether the GroupID is legal. If it is legal, the channel information corresponding to the corresponding virtual device group will be sent to the cloud desktop client, and the cloud desktop client will connect to the corresponding virtual device. The cloud desktop configuration and connection process is shown in Figure 3;

[0043] The specific situation is:

[0044] Increase the number of virtual devices in the cloud desktop startup configuration file. Assume that the original cloud desktop has t types of virtual devices, M1, M2, ..., Mt, and each type of device has M1a, M2b, ..., Mtq, respectively. That is, M1a + M2b + ... + Mtq = M virtual devices in total. Assume M = 10. These virtual devices can be used for peripherals such as cameras, USB flash drives, printers, and five-in-one devices. Now each cloud desktop needs to provide services for N users. Assume N = 3. Therefore, the cloud desktop now needs to be configured with 10 * 3 = 30 virtual devices, which is three sets of virtual device configurations identical to the original cloud desktop.

[0045] During the virtual machine startup phase, the cloud desktop server renames the device to DeviceType.DeviceID.GroupID based on the type of each virtual device, the device serial number, and the group, and establishes a connection between devices in the same group. The device information can be stored in a database, but is not limited to the database.

[0046] When a virtual device is hot-swapped, added, or removed, the cloud desktop server will promptly update the device information of the corresponding group based on the device name, including but not limited to updating the database;

[0047] When a user uses a cloud desktop client to connect to a cloud desktop, the cloud desktop server verifies the connection encryption certificate, cloud desktop account password, and adds a new verification of the legitimacy of the GroupID. If it is not legal, the cloud desktop client will be offline. If it is legal, the corresponding virtual device group will be found from the virtual device management relationship, such as from the database, and the connection channel corresponding to the virtual device group will be sent to the cloud desktop client.

[0048] Multiple cloud desktop users log in to the same cloud desktop, use different virtual device groups, and share the cloud desktop's CPU and memory resources. When using office suites, browsing the web, using cameras, USB flash drives, printers and other peripherals, and performing normal office work, each cloud desktop user does not affect each other;

[0049] The key technical point of this application is a cloud desktop multi-connection method based on virtual device grouping. Compared with the existing technology, each cloud desktop can only have one user connection. This improves the CPU, memory and other resource utilization of this cloud desktop in ordinary office scenarios, and overall improves the computing power utilization of cloud computing servers.

[0050] The key technical point is that N groups of identical virtual devices are configured in the same cloud desktop. Each group of virtual devices has t types of virtual devices, M1, M2, ..., Mt, and each type of device has M1a, M2b, ..., Mtq, i.e., a total of M1a+M2b+...+Mtq=M virtual devices. This can meet the needs of different types of devices such as cameras, USB flash drives, and printers. Therefore, a cloud desktop is equipped with N*M virtual devices, which is beneficial for multiple users to use different virtual devices without interfering with each other.

[0051] The specific technical points are that the cloud desktop server renames N*M virtual devices, including but not limited to according to device type, device serial number, and group information, and establishes connections between these virtual devices according to groups, including but not limited to using a database to store this information to facilitate management tasks such as query, addition, and reduction;

[0052] The number of users ultimately assigned to each cloud desktop is determined by the cloud desktop specifications and the resources used by each user. N can be adjusted dynamically. For example, if the average resource requirements per user increase, N can be reduced, allowing fewer users to log into the same desktop. Conversely, if the average resource usage per user is low, N can be increased, allowing more users to log into the same desktop simultaneously.

[0053] The specific technical point is that when connecting to the cloud desktop, in addition to the normal connection authentication process, a group verification process is added. Only after the verification is passed will the cloud desktop client be allowed to connect, and the corresponding virtual device group will be notified to the cloud desktop client for connection and use.

[0054] It is important to note that the construction and arrangement of the present application shown in a number of different exemplary embodiments are merely illustrative. Although only a few embodiments are described in detail in this disclosure, it should be readily understood by those reading this disclosure that many modifications are possible (e.g., the size, scale, structure, shape and proportion of various elements, as well as parameter values ​​(e.g., temperature, pressure, etc.), mounting arrangements, use of materials, color, changes in orientation, etc.) without materially departing from the novel teachings and advantages of the subject matter described in this application. For example, elements shown as integrally formed may be composed of multiple parts or elements, the positions of elements may be inverted or otherwise changed, and the nature or number or position of discrete elements may be altered or changed, and therefore, all such modifications are intended to be included within the scope of this application. The order or sequence of any process or method steps may be changed or reordered according to alternative embodiments. In the claims, any "means plus function" clause is intended to cover the structures described herein that perform the function, and not only structural equivalence but also equivalent structures. Without departing from the scope of the present application, other substitutions, modifications, changes and omissions may be made in the design, operating conditions and arrangement of the exemplary embodiments. Therefore, the present application is not limited to a specific embodiment, but extends to various modifications that still fall within the scope of the appended claims.

[0055] Additionally, in order to provide a concise description of example embodiments, all features of an actual embodiment (ie, those features not relevant to the best mode presently contemplated for carrying out the application or those not relevant to implementing the application) may not be described.

[0056] It will be appreciated that in the development of any actual implementation, as in any engineering or design project, numerous implementation-specific decisions may be made. Such a development effort may be complex and time-consuming, but will be a routine task of design, fabrication, and production for those of ordinary skill having the benefit of this disclosure without undue experimentation.

[0057] It should be noted that the above embodiments are only used to illustrate the technical solutions of the present application and are not intended to limit the present application. Although the present application has been described in detail with reference to the preferred embodiments, those skilled in the art should understand that the technical solutions of the present application may be modified or replaced by equivalents without departing from the spirit and scope of the technical solutions of the present application, and all of these should be included in the scope of the claims of the present application.

Claims

1. A cloud desktop multi-connection method based on virtual device grouping, characterized in that: The method is as follows: S1: Increase the number of virtual devices in the cloud desktop startup configuration file; S2: During the virtual machine startup phase, the cloud desktop server renames the device to DeviceType.DeviceID.GroupID according to the type DeviceType, device serial number DeviceID, and group GroupID of each virtual device, and stores it; S3: When a virtual device is hot-swapped, added, or reduced, the cloud desktop server will update the device information of the corresponding group in a timely manner based on the device name; S4: When the user uses the cloud desktop client to connect to the cloud desktop, the cloud desktop server verifies the connection encryption certificate and the cloud desktop account password for the connection request; S5: After multiple cloud desktop users log in to the same cloud desktop, they use different virtual device groups and share the CPU and memory resources of the cloud desktop.

2. The cloud desktop multi-connection method based on virtual device grouping according to claim 1, characterized in that: The specific steps of S1 are as follows: assuming that there are t types of virtual devices, M1, M2, ..., Mt, in the original cloud desktop, and each type of device has M1a, M2b, ..., Mtq, that is, M1a+M2b+...+Mtq=M virtual devices in total.

3. The cloud desktop multi-connection method based on virtual device grouping according to claim 2 is characterized in that: In S1, the cloud desktop is allocated to N users, and the number of virtual devices is increased to M*N, which is equivalent to configuring N groups of identical virtual devices in the cloud desktop, and each cloud desktop can be connected to by N users at the same time.

4. The cloud desktop multi-connection method based on virtual device grouping according to claim 3 is characterized in that: The number of cloud desktop virtual devices configured by M for each user in S1 is determined by actual usage requirements.

5. The cloud desktop multi-connection method based on virtual device grouping according to claim 4 is characterized in that: In S1, N is the number of users that each desktop can serve simultaneously, which is determined by the cloud desktop specifications and the resources used by each user. N can be adjusted dynamically, that is, if the average resource requirements of each user increase, then N is reduced, and fewer users log in to the same desktop.

6. The cloud desktop multi-connection method based on virtual device grouping according to claim 4 is characterized in that: If the average resource usage of each user in S1 is very low, then N is increased to allow more users to log in to one desktop at the same time.

7. The cloud desktop multi-connection method based on virtual device grouping according to claim 6 is characterized in that: After the devices in S2 are renamed, the devices in the same group are linked and the device information is stored in a database.

8. The cloud desktop multi-connection method based on virtual device grouping according to claim 7 is characterized in that: In the S3, the database is updated after the device information of the corresponding group is updated.

9. The cloud desktop multi-connection method based on virtual device grouping according to claim 8, characterized in that: The S4 adds a new verification of the legitimacy of the GroupID. If it is illegal, the cloud desktop client is offline. If it is legal, the corresponding virtual device group is found from the virtual device management relationship, such as from the database, and the connection channel corresponding to the virtual device group is sent to the cloud desktop client.

10. The cloud desktop multi-connection method based on virtual device grouping according to claim 9, characterized in that: In the S5, each cloud desktop user does not affect each other when using office suites, browsing web pages, using cameras, USB flash drives, printers and other peripherals for ordinary office work.

Images