WO2020135492A1

WO2020135492A1 - Software hierarchical management system

Info

Publication number: WO2020135492A1
Application number: PCT/CN2019/128258
Authority: WO
Inventors: 李丽莉
Original assignee: 中兴通讯股份有限公司
Priority date: 2018-12-26
Filing date: 2019-12-25
Publication date: 2020-07-02
Also published as: CN111367599B; CN111367599A

Abstract

Provided by the present disclosure is a software hierarchical management system, comprising: a terminal device used for selecting, by means of logging onto an installed client, a virtual machine from a list of virtual machines to be used, and connecting to a far-end virtual desktop on the basis of a desktop connection protocol according to the selected virtual machine; a virtual desktop resource management system used for managing a virtual desktop operating system and virtual machine resources so as to provide basic configuration and a plurality of pieces of commonly used software to a virtual desktop of the virtual desktop operating system, wherein image files of the plurality of pieces of commonly used software are distributed in a plurality of different containers; and a virtual desktop operating system which is installed on a physical hardware device and which is used for obtaining the basic configuration of the virtual desktop from the virtual desktop resource management system.

Description

Software layered management system

Technical field

This disclosure relates to, but is not limited to, the field of communications.

Background technique

Mobile phones and mobile terminals have been unable to leave people's lives, and the use from ordinary life scenarios has penetrated into work scenarios, such as the company's mobile phone mailbox, mobile office system, internal communication, etc., these data will be transferred in the mobile terminal, if Losing the phone will cause great security risks to these data.

With the rapid development of cloud computing services, cloud-based virtual desktop technology has been widely used in scenarios such as operators, government enterprises, and schools, including private clouds built by ourselves and operable public clouds.

Virtual Desktop Infrastructure (VDI), through server virtualization, realizes the abstraction of hardware, resource allocation, scheduling and management, the isolation of virtual desktops from the host operating system and multiple virtual desktops, and Through the agreement, the thin client side and the server side can display the cloud desktop image. Based on the virtualization technology, the virtual Windows system desktop and Linux system desktop are still the mainstream, and there is no virtual cloud desktop for the Android operating system to be used on mobile devices, and the software currently used on the Android system is based on personal Download APP(Application) software freely according to your preferences and use it after installation. You cannot directly use the software without installation, and the software cannot control the use rights of the software according to user attribute assignment rules. Therefore, when users use mobile devices, especially mobile phones, personal data and work data will be lost after the password is lost or stolen, and information security is greatly threatened.

Summary of the invention

According to an embodiment of the present disclosure, a software layered management system is provided, including: a terminal device, a virtual desktop resource management system, and a virtual desktop operating system installed on a physical hardware device; wherein, the terminal device is used to Log in to the installed client to select a virtual machine from the list of virtual machines to be used, and connect to the remote virtual desktop based on the desktop connection protocol according to the selected virtual machine; the virtual desktop resource management system is used to Desktop operating system and virtual machine resources are managed to provide basic configuration and multiple common software to the virtual desktop of the virtual desktop operating system, wherein the image files of multiple common software are distributed in multiple different containers; and The virtual desktop operating system is used to obtain the basic configuration of the virtual desktop from the virtual desktop resource management system.

BRIEF DESCRIPTION

FIG. 1 is a schematic structural diagram of a software layered management system according to an embodiment of the present disclosure;

2 is an architecture diagram of a software layered management system according to an embodiment of the present disclosure;

3 is an architecture diagram of a software layered management system according to an embodiment of the present disclosure;

4 is a schematic diagram of access to a loading template of a software layered management system according to an embodiment of the present disclosure;

5 is a schematic structural diagram of a Docker container warehouse according to an embodiment of the present disclosure;

6 is a flowchart 1 of loading an Android desktop according to an embodiment of the present disclosure;

7A is a flowchart 2 of loading an Android desktop according to an embodiment of the present disclosure;

7B is a flowchart 2 of loading an Android desktop according to an embodiment of the present disclosure;

8A is a flowchart 3 of loading an Android desktop according to an embodiment of the present disclosure;

8B is a flowchart 3 of loading an Android desktop according to an embodiment of the present disclosure;

9A is a flowchart 4 of loading an Android desktop according to an embodiment of the present disclosure; and

9B is a flowchart 4 of loading an Android desktop according to an embodiment of the present disclosure.

detailed description

Hereinafter, the present disclosure will be described in detail with reference to the accompanying drawings and in conjunction with the embodiments. It should be noted that the embodiments in the present application and the features in the embodiments can be combined with each other if there is no conflict.

It should be noted that the terms “first”, “second”, etc. in the specification and claims of the present disclosure and the above drawings are used to distinguish similar objects, and do not have to be used to describe a specific order or sequence.

An embodiment of the present disclosure provides a software layered management system. FIG. 1 is a schematic structural diagram of a software layered management system according to an embodiment of the present disclosure. As shown in FIG. 1, the system includes: a terminal device 101 and virtual desktop resource management The system 102 and the virtual desktop operating system 103 installed on the physical hardware device. The terminal device 101 is used to select a virtual machine from a list of virtual machines to be used by logging in the installed client, and connect to a remote virtual desktop based on the desktop connection protocol according to the selected virtual machine. The virtual desktop resource management system 102 is used to manage the virtual desktop operating system 103 and virtual machine resources to provide basic configuration and multiple common software to the virtual desktop of the virtual desktop operating system 103, where the image files of multiple common software are distributed In multiple different containers. The virtual desktop operating system 103 is used to obtain the basic configuration of the virtual desktop from the virtual desktop resource management system.

In an optional implementation manner of this embodiment, the virtual desktop resource management system 102 includes: a basic configuration module for managing basic configuration information required to run a virtual desktop; and a software management module for basic configuration information and common software Management of the life cycle of the software, and is used to create and manage basic configuration information and common software; allocation module, used to set permissions between common software and virtual desktop users; Docker container warehouse management module, used for software management module The software in provides an installation warehouse, where the installation warehouse includes multiple containers, and an image file of common software is downloaded and installed in each container.

In addition, in an optional implementation manner of this embodiment, the virtual desktop operating system 103 may further include: a Docker startup processor, used to obtain permissions between commonly used software and virtual desktop users, and manage from the Docker container warehouse according to the permissions Obtain the image file of the corresponding common software from the module and load it into the Docker manager; and the Docker manager to start the software in the Docker container warehouse management module locally on the virtual desktop of the virtual desktop operating system.

Install the common software to different warehouses through the above Docker container warehouse management module, and then use the software directly by obtaining the image file of the software, which realizes the free installation of the software. In addition, the common software is installed in different warehouses The hierarchical management of software is realized, and the permission relationship between commonly used software and virtual desktop users is set, so that different virtual desktop users have different software use permissions, which further realizes software management and improves security.

It should be noted that the basic configuration information involved in this embodiment includes: configuration information of the operating system and basic software and driver information of the operating system; commonly used software includes office software and/or personalized software. 2 is a schematic structural diagram of an implementation mode of a virtual desktop management system according to an embodiment of the present disclosure. As shown in FIG. 2, a physical hardware device 104 is used to virtualize the resources of one host server into multiple logical virtual Computer, and provide it to the terminal device 101 in the form of virtual desktop through the desktop protocol server and the desktop protocol.

Among them, in an optional implementation manner of this embodiment, the physical hardware device 104 includes: a computing, storage, and network virtualization module, configured to provide a virtualization capability for the physical hardware device and create a function of the virtual machine ; And the virtual desktop connection protocol server, used to obtain virtual desktops through virtual machines, and provide virtual desktops to terminal devices after the terminal device is connected to the desktop protocol client through the desktop protocol.

In an optional implementation manner of this embodiment, the virtual desktop resource management system 102 may further include: a desktop user management module, configured to maintain user information of the virtual desktop, and generate multiple virtual machines based on the basic configuration module of the virtual machine Desktop, and assign the virtual desktop to users in the system, where the user information includes at least: account number, password; and resource management module, used to manage and maintain the hardware physical equipment, network and storage management, and virtual Machine for resource management and life cycle management.

Further, in an optional implementation manner of this embodiment, the virtual desktop operating system 103 further includes: a desktop agent, configured to provide interaction between the virtual desktop and the virtual desktop resource management system and the terminal device.

In another optional implementation manner of this embodiment, the terminal device includes: a virtual desktop connection login client, which is used to provide an entry for a user to log in to the virtual desktop operating system to obtain a list of virtual desktops to be used; and a virtual desktop connection protocol The client is used to connect to and use the virtual desktop through the desktop protocol.

The application will be described in detail below in conjunction with the optional embodiment of this embodiment.

This embodiment provides a software hierarchical management system, which is used to implement the use of Android virtual desktops and the use of software hierarchies within the desktop, and the Android desktop software can be used directly without downloading installation packages and without installation, and can be used according to different users Attributes use different software effects.

In this embodiment, the software layered management system includes: a physical hardware device 104, a virtual desktop resource management system 102, a terminal device 101, and a virtual desktop operating system 103, where the terminal device 101 installs a virtual desktop connection login on the terminal device The client 312 and the virtual desktop connection protocol client 313. The type of terminal device that can be connected to the virtual desktop can be a Windows system PC, a Linux system thin terminal, a mobile Android, an iOS device, etc. The client 312 can be logged in through the virtual desktop connection to authenticate the user to obtain the user can use List of virtual desktop virtual machines, and then you can connect to the remote virtual desktop through the desktop connection protocol.

The physical hardware device 104 is installed with a virtualized host system, and virtualizes computing, storage, and network resources from one host server to multiple logical virtual machines for use. Install the virtual desktop connection protocol server 302 on the physical hardware device 104, the terminal device connects to the virtual desktop connection protocol server 302 through the virtual desktop connection protocol client 313, and then the terminal can connect to the virtual machine through the desktop protocol and use the virtual desktop mode Provide virtual desktops to users.

The virtual desktop resource management system 102 is used to manage, allocate, and maintain virtual machine resources such as computing, storage, and network resources, provide management and maintenance of desktop templates and software templates, provide user information maintenance for desktop users, and allocate desktop virtual machines, etc. . It can perform unified management on physical hardware devices, logical virtual machines, and virtual desktop users. In order to realize the software layering of the Android desktop, the virtual desktop resource management system 102 further includes: a basic configuration module 306, a software management module 309, an allocation module 310, and a Docker container warehouse management module 311.

The difference between the basic configuration module 306 and the software management module 309 is as follows: the basic configuration module 306 is used to install a standard operating system and basic used software, and a virtualized driver and an Android startup interceptor module. The software management module 309 is used to install actual working software and/or personalized software. After using the Android desktop created by the basic configuration module 306 in combination with the software management module 309, the user can directly use the software in the system without downloading the software installation package from the Android application store and then install it. use.

Virtual desktop operating system 103: Windows, Android, Linux and other operating systems can be installed in the virtual desktop. When the Android system is installed in the desktop virtual machine (that is, when the terminal device is the Android system), the Android desktop can be provided for use. In order to realize the layering function of the Android desktop software, the virtual desktop operating system 103 includes: a Docker startup processor and a Docker manager.

It should be noted that in order to achieve the same version of the same software, each software template can use the sandbox mechanism of the Docker container and the simultaneous operation mechanism of multiple Docker containers to install the personalized software in the software management module 309 in the Docker container. Each Docker container has downloaded and installed an image file of common software, and these Docker image files are uniformly deployed on the Docker warehouse server. After the software management module 309 is assigned to the user's Android desktop, the Android desktop is bound to the software management module 309 and an incremental Docker container image file download is performed, and when the Android system is started, the software management module 309 of this embodiment performs Start directly to run, which means that the Android desktop is bound to different software management modules and installed directly. At the same time, the user and application software use rights that can be configured in the desktop management platform give different users the right to use different software APP applications.

It should be noted that in the related technology, there are also software layering technologies in the Windows system environment, but the Windows system needs to include two parts of the registry and application files, and Docker technology cannot be used at the same time, so the writing driver will be used to intercept the files at the bottom. And processing, pointing the files used by the system to the directory of the application software, so it can only be controlled or not available for all software in the software management module, and cannot be used or not available for each user for each application.

The software hierarchical management system provided by this embodiment can provide users with convenient software, so that users who use the Android desktop do not need to download the installation package, which reduces the installation process and prevents different users from downloading the same software. The issue of version can be controlled by the software management module of the administrator whether there is the right to use the software and the version of the software. At the same time, the data used by the user is circulated in the virtualized data center, and will not be lost with the loss of the mobile phone. Maintaining personnel, enterprise data security, and users brings great convenience.

The case will be described in detail below in conjunction with the specific implementation of this embodiment and the drawings.

First, the framework of the system will be described with reference to FIG. 3, which is an architectural diagram of an embodiment of a software layered management system according to an embodiment of the present disclosure. As shown in FIG. 3, the system includes: physical hardware device 104, virtual A desktop operating system 103, a virtual desktop resource management system 102, and a terminal device 101. The physical hardware device 104 includes: a computing, storage, and network virtualization module 301, which is used to provide virtualization capabilities for the physical hardware device, and a function of creating a virtual machine; and a virtual desktop connection protocol server 302, which is used to provide conversion of the virtual machine into The virtual desktop is provided to the user after being connected through the virtual desktop connection protocol client 313.

The virtual desktop operating system 103 includes: a desktop agent 303, used to provide interaction between the virtual desktop and the virtual desktop resource management system 102, and the terminal device 101, for example, the use of an external device; the Docker startup processor 304, used to obtain The user software permissions between common software and virtual desktop users and the corresponding software image file obtained from the Docker warehouse server, and transferred to the Android desktop system and then loaded into the Docker manager; and Docker manager 305, used for local Android desktop Start the software in the Docker container.

The virtual desktop resource management system 102 includes: a basic configuration module 306 for managing basic configuration information required for running a virtual desktop; a desktop user management module 307 for maintaining user information of the virtual desktop, where the user information includes: Accounts, passwords, etc., and at the same time generate multiple virtual desktops based on the basic configuration module of the virtual machine, and assign the virtual desktops to the terminal devices in the system; the resource management module 308 is used to manage and maintain the hardware physical devices, and to the network , Storage management, and resource management and life cycle management of virtual machines; software management module 309, including a software management module composed of basic software management modules and common software management modules, that is, the software management module 309 can be used for basic software and The life cycle management of common software can create and manage the basic software management module of the desktop virtual machine, as well as the creation and management of the common software management module in the desktop; the allocation module 310 is used to allocate the user's authority to use the software. Through the allocation of permissions, to control different users to use different software; and Docker container warehouse management module 311, provides an installation warehouse for the software in the software management module 309, wherein the installation warehouse includes multiple containers, each container download And install an image file of commonly used software.

The terminal device 101 includes: a virtual desktop connection login client 312, which is used to provide an entrance for a user to log in to the virtual desktop operating system to obtain a list of virtual desktops to be used, wherein a corresponding client is to be installed on the terminal device, and the user is input when used The name and password can be obtained through the virtual desktop resource management system after authentication to obtain a list of available desktops; and virtual desktop connection protocol client 313, click to obtain the virtual desktop connection login client 312 desktop list, you can use the desktop protocol Connect to the desktop and use.

The present application will be further described in conjunction with the above frame diagram of FIG. 3 and the following FIGS. 4 to 9, FIG. 4 is a schematic diagram of a system loading template access according to an embodiment of the present disclosure, and FIG. 5 is a schematic diagram of a Docker warehouse server according to an embodiment of the present disclosure As shown in Figure 4 and Figure 5, the virtual machine Android desktop is created through the virtual machine system basic software management module. The Android desktop automatically comes with the APP software installed in the basic software management module, and the commonly used software management module is additional software for users. , And has been released to the Docker warehouse server in advance, and can be used in superposition with the software in the basic software management module.

When the basic software management module and common software management modules are superimposed on the same desktop virtual machine, the process includes: a. Install the Docker startup processor in advance in the system pre-installed application; b. When the Android desktop starts, the Docker startup processor acquires the user Software permissions, and obtain the corresponding Docker container image file from the Docker warehouse server and transfer it to the Android system, and load it into the Docker manager. The Docker manager is responsible for starting the software in the Docker container locally; c. When the Android desktop starts Scan the resources in the current system, such as system pre-installed application /system/app, system core component /system/priv-app, user installed application /data/app, etc. d. After the scan is completed, the Android system obtains complete information Compare with the system configuration file package.xml to determine the update of the files in these directories, and then automatically optimize the system. The process of system optimization is to update the related APP applications. After the update is complete, the Android system starts.

After that, a complete Android application interface felt by the user can use the APP software installed in the basic software management module or the APP software superimposed in the common software management module.

An example is described based on the above description in combination with the optional implementation manner of this embodiment;

Alternative Embodiment One

FIG. 6 is a flowchart 1 of loading an Android desktop according to an embodiment of the present disclosure. As shown in FIG. 6, the Android desktop is created by the basic software management module, that is, the process of loading the Android desktop when only the software of the basic software management module is owned. The method includes the following steps S601 to S607.

In step S601, the basic software management module installs the Android virtual desktop.

In step S602, an Android virtual desktop is generated through the basic software management module and distributed to users.

In step S603, log in and click to connect to the virtual desktop through the desktop client of the Android mobile terminal.

In step S604, the Android virtual desktop in the remote virtualization server center is connected through the desktop protocol, and the Android desktop startup process is presented to the terminal device through the protocol.

In step S605, the Android desktop operating system starts the interceptor and determines that there is no common software in the common software management module.

In step S606, the system normally scans the local system applications of the Android system and the applications installed in the basic software management module.

In step S607, the system normally starts the default system program, and at the same time presents the scanned application APP icon to the user.

Optional embodiment two

FIGS. 7A and 7B are a flowchart 2 of loading an Android desktop according to an embodiment of the present disclosure. As shown in FIGS. 7A and 7B, the Android desktop is created by the basic software management module. The software of the commonly used software management module, the Android desktop of the end user has the basic software management module and the software APP of the commonly used software management module, and the method of this process includes the following steps S701 to S710.

In step S701, the basic software management module installs the basic software of the Android virtual desktop.

In step S702, the software is installed in a Docker container and deployed in a Docker warehouse server, and converted into software in a common software management module, which is distributed to users for use.

For example, the basic software management module can install only the most basic software APP that all users will use, and the software APP used by some people is made into the software in the common software management module and allocated to the corresponding part of the personnel;

In step S703, an Android desktop is generated through the basic software management module and distributed to users.

In step S704, the user uses an ordinary Android mobile terminal and installs a desktop client, logs in and clicks to connect to the desktop.

In step S705, the Android virtual desktop in the remote virtualization server center is connected through the desktop protocol, and the Android desktop startup process is presented to the terminal device through the protocol.

In step S706, the Android desktop operating system starts the interceptor, obtains software with common software management modules, obtains a list of software available to users, and obtains the corresponding Docker container image file from the Docker warehouse server and passes it to the Android system.

In step S707, the system normally scans the system application local to the Android system and the APP application software installed in the basic software management module.

In step S708, the Docker manager loads the software list in the newly added Docker container.

In step S709, when the user clicks on the icon of the newly added Docker container, the APP application software starts to run independently in the Docker container.

In step S710, the Android system starts to scan the resources in the current system, obtain complete information and compare it with the system configuration file package.xml, determine the new software APP in the added Docker manager, optimize the system, and load these new additions Software APP, the system finishes starting.

What the Android system shows to the user at the same time is the collection of the application APP in the basic software management module and the software application APP in the common software management module.

Optional embodiment three

8A and 8B are a flowchart 3 of loading an Android desktop according to an embodiment of the present disclosure. As shown in FIGS. 8A and 8B, the Android desktop is created by software in the basic software management module, while having the software of the basic software management module. , The software in the common software management module is superimposed, but it can be filtered according to the user software permissions set by the user. The end user’s Android desktop has the basic software management module and the authorized software APP in the common software management module, and the APP application without authorization Not displayed. The method includes the following steps S801 to S811.

In step S801, the basic software management module installs the basic software of the Android virtual desktop.

In step S802, the software is installed in a Docker container and deployed in a Docker warehouse server, and converted into software in a common software management module.

Among them, different users in the software template allocate different software to use, and decentralize the use according to the characteristics of the users. For example, if the sales staff does not use the financial software of the financial staff, then the financial staff can only be assigned the corresponding software permissions, and the sales staff does not have the permissions, although the software APPs are in a software template on the final financial staff’s Android desktop. Corresponding financial software can be used, and the sales staff will not display this part of the software APP;

In step S803, an Android desktop is generated through the basic software management module and distributed to users.

In step S804, the user uses an ordinary Android mobile terminal and installs a desktop client, logs in and clicks to connect to the desktop.

In step S805, the Android virtual desktop in the remote virtualization server center is connected through the desktop protocol, and the Android desktop startup process is presented to the terminal device through the protocol.

In step S806, the Android desktop operating system starts the interceptor, obtains the software in the software management module, obtains the software list available to the user, and obtains the corresponding Docker container image file from the Docker warehouse server and passes it to the Android system.

In step S807, the system normally scans the system application local to the Android system and the APP application software installed in the basic software management module.

In step S808, the software permission filter is based on the list of available application software APPs configured on the server side of the logged-on Android desktop user, and after filtering, the Docker manager is allowed to load only the software list with permissions.

In step S809, the Docker manager loads the software list in the newly added Docker container with permissions.

In step S810; when the user clicks on the icon of the newly added Docker container, the APP application software starts to run independently in the Docker container.

In step S811, the Android system starts to scan the resources in the current system, obtain complete information and compare it with the system configuration file package.xml, determine the newly added software APP in the added Docker manager, optimize the system, and load these new additions Software APP, the system finishes starting.

Among them, what the Android system shows to the user at the same time is a collection of application APPs in the basic software management module and application software APPs that the user has permission to use in the common software management module.

Optional embodiment four

9A and 9B are a flowchart 4 of loading an Android desktop according to an embodiment of the present disclosure; as shown in FIGS. 9A and 9B, this alternative implementation is similar to alternative implementation three, but in this alternative implementation , The system supports linear expansion, supports the stacking of software in multiple common software management modules, and supports multiple Docker warehouse servers that store software to meet the increasing software needs of users. The Android desktop is created by the basic software management module. While having the software of the basic software management module, the software in multiple common software management modules is superimposed. At the same time, all newly added software can still be filtered according to the usage rights set by the user. The end user The Android desktop has a basic software management module and software apps with permissions in all common software management modules. Apps without permissions are not displayed. The method includes the following steps S901 to S911.

In step S901, the basic software management module installs the software of the Android virtual desktop.

In step S902, the system administrator installs the software in the Docker container in advance and deploys it in the Docker warehouse server, and supports multiple Docker warehouse servers at the same time.

In other words, it can be stored in different warehouse servers according to different software attributes, which is easy to distinguish and manage. Among them, the Docker container where the software is installed is converted into a software template, in which different users in the software template are assigned different software to use, and decentralized use is based on the characteristics of the users. For example, different software templates can be assigned according to different attributes of users. If they are sales-oriented, production-oriented, or under management leadership, the software used will be different. The software used by these roles can be made into public software Templates, different software features are made into different software templates, and different software permissions can also be assigned according to different personnel levels.

In step S903, an Android desktop is generated through the basic software management module and distributed to users.

In step S904, through the Android mobile terminal and installed a desktop client, log in and click to connect to the desktop.

In step S905, the Android virtual desktop in the remote virtualization server center is connected through the desktop protocol, and the Android desktop startup process is presented to the terminal device through the protocol.

In step S906, the Android desktop operating system starts the interceptor, obtains a software template, obtains a list of software permissions that can be used by the user, and obtains corresponding Docker container image files from multiple Docker warehouse servers and passes it to the Android system.

In step S907, the system normally scans the system application local to the Android system and the APP application software installed in the basic template.

In step S908, the software permission filter is based on the list of available application software APPs configured on the server side of the logged-on Android desktop user, and after filtering, the Docker manager is allowed to load only the software list with permissions.

In step S909, the Docker manager loads the software list in the newly added Docker container with permission.

In step S910, when the user clicks the icon of the newly added Docker container, the APP application software starts to run independently in the Docker container.

In step S911, the Android system starts to scan the resources in the current system, obtain complete information and compare it with the system configuration file package.xml, determine the new software APP in the added Docker manager, optimize the system, and load these new additions Software APP, the system finishes starting.

Through this embodiment, users can use Android virtual desktops on mobile devices or in the Windows operating system, and can control the Android software used in different layers according to different users. At the same time, Android software can be installed free of use You can start the operation directly, and you can set different people to use different software. When users use the Android virtual desktop, each software is saved before downloading the installation package and carrying out cumbersome installation before use, reducing the learning cost of using the Android system, and all the data will be in the server and storage of the computing center Circulation, there is no usage data on the terminal, and it cannot be transferred to the terminal. This embodiment implements the software-free installation process on the basis of the Android virtualized desktop, and controls the software use rights according to different user rights, which improves the user's ease of use and guarantees user data security.

Through the present invention, a terminal device in a software hierarchical management system is provided for selecting a virtual machine from a list of virtual machines to be used by logging in to an installed client, and based on the selected virtual machine based on a desktop connection protocol Connected to a remote virtual desktop; a virtual desktop resource management system is used to manage the virtual desktop operating system and virtual machine resources to provide basic configuration and multiple common software to the virtual desktop of the virtual desktop operating system. The image files of common software are distributed in multiple different containers; the virtual desktop operating system is used to obtain the basic configuration of the virtual desktop from the virtual desktop resource management system. The invention solves the problems that the APP in the virtual desktop based on the Android system in the related art needs to be downloaded before it can be used without installation and without layered management of the software, and the effect of providing a user experience is achieved.

Obviously, those skilled in the art should understand that the above-mentioned modules or steps of the present disclosure can be implemented by a general-purpose computing device, they can be concentrated on a single computing device, or distributed in a network composed of multiple computing devices Above, in an embodiment, they can be implemented with program code executable by the computing device, so that they can be stored in the storage device to be executed by the computing device, and in some cases, may be different from here The steps shown or described are performed in the order of, or they are made into individual integrated circuit modules respectively, or multiple modules or steps among them are made into a single integrated circuit module to achieve. In this way, the present disclosure is not limited to any specific combination of hardware and software.

The above are only preferred embodiments of the present disclosure, and are not intended to limit the present disclosure. For those skilled in the art, the present disclosure may have various modifications and changes. Any modification, equivalent replacement, improvement, etc. made within the principles of this disclosure shall be included in the protection scope of this disclosure.

Claims

A software hierarchical management system includes: a terminal device, a virtual desktop resource management system, and a virtual desktop operating system installed on a physical hardware device, where,

The terminal device is used to select a virtual machine from a list of virtual machines to be used by logging in the installed client, and connect to a remote virtual desktop based on the desktop connection protocol according to the selected virtual machine;

The virtual desktop resource management system is used to manage the virtual desktop operating system and virtual machine resources to provide basic configuration and multiple common software to the virtual desktop of the virtual desktop operating system, wherein the multiple common The software image files are distributed in multiple different containers; and

The virtual desktop operating system is used to obtain the basic configuration of the virtual desktop from the virtual desktop resource management system.
The system of claim 1, wherein the virtual desktop resource management system includes:

A basic configuration module, used to manage basic configuration information required for running the virtual desktop;

The software management module is used to manage the basic configuration information and the life cycle of the common software, and is used to create and manage the basic configuration information and the common software;

An allocation module for setting permissions between the commonly used software and virtual desktop users; and

A Docker container warehouse management module is used to provide an installation warehouse for the software in the software management module, wherein the installation warehouse includes multiple containers, and an image file of common software is downloaded and installed in each container.
The system of claim 2, wherein the virtual desktop operating system includes:

The Docker startup processor is used to obtain the permission between the common software and the virtual desktop user, and obtain the image file corresponding to the common software from the Docker container warehouse management module according to the permission, and load it into the Docker manager ;as well as

The Docker manager is used to start the software in the Docker container warehouse management module locally on the virtual desktop of the virtual desktop operating system.
The system of claim 1, wherein:

The physical hardware device is used to virtualize the resources of one host server into multiple logical virtual machines, and provide them to the terminal device in a virtual desktop manner through a virtual desktop connection protocol server and a desktop protocol.
The system according to claim 4, wherein the virtual desktop resource management system further comprises:

The desktop user management module is used to maintain user information of the virtual desktop, generate multiple virtual desktops based on the basic configuration module of the virtual machine, and distribute the virtual desktops to users in the system, wherein the user The information includes at least: account number and password.
The system according to claim 5, wherein the virtual desktop operating system further comprises:

The desktop agent is used to provide interaction between the virtual desktop and the virtual desktop resource management system and the terminal device.
The system according to claim 2, wherein the terminal device comprises:

The virtual desktop connection login client is used to provide an entry for users to log in to the virtual desktop operating system to obtain a list of virtual desktops to be used; and

The virtual desktop connection protocol client is used to connect to and use the virtual desktop through the desktop protocol.
The system according to claim 4, wherein the physical hardware device comprises:

A computing, storage, and network virtualization module, used to provide virtualization capabilities for the physical hardware device and create functions of the virtual machine; and

The virtual desktop connection protocol server is used to obtain the virtual desktop through the virtual machine, and provide the virtual desktop to the terminal device after the terminal device is connected to the desktop protocol client through the desktop protocol.
The system according to claim 2, wherein the basic configuration information includes configuration information of an operating system and basic software and driver information for running the operating system, and the commonly used software includes office software and/or personalized software.