WO2020135492A1 - Système de gestion hiérarchique de logiciel - Google Patents

Système de gestion hiérarchique de logiciel Download PDF

Info

Publication number
WO2020135492A1
WO2020135492A1 PCT/CN2019/128258 CN2019128258W WO2020135492A1 WO 2020135492 A1 WO2020135492 A1 WO 2020135492A1 CN 2019128258 W CN2019128258 W CN 2019128258W WO 2020135492 A1 WO2020135492 A1 WO 2020135492A1
Authority
WO
WIPO (PCT)
Prior art keywords
software
desktop
virtual desktop
virtual
operating system
Prior art date
Application number
PCT/CN2019/128258
Other languages
English (en)
Chinese (zh)
Inventor
李丽莉
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2020135492A1 publication Critical patent/WO2020135492A1/fr

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/451—Execution arrangements for user interfaces
    • G06F9/452—Remote windowing, e.g. X-Window System, desktop virtualisation
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/451—Execution arrangements for user interfaces
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533—Hypervisors; Virtual machine monitors
    • G06F9/45558—Hypervisor-specific management and integration aspects
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management

Definitions

  • This disclosure relates to, but is not limited to, the field of communications.
  • 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.
  • cloud-based virtual desktop technology has been widely used in scenarios such as operators, government enterprises, and schools, including private clouds built by us and operable public clouds.
  • VDI Virtual Desktop Infrastructure
  • 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.
  • 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.
  • a software layered management system 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.
  • FIG. 1 is a schematic structural diagram of a software layered management system according to an embodiment of the present disclosure
  • FIG. 2 is an architecture diagram of a software layered management system according to an embodiment of the present disclosure
  • FIG. 3 is an architecture diagram of a software layered management system according to an embodiment of the present disclosure
  • FIG. 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
  • FIG. 5 is a schematic structural diagram of a Docker container warehouse according to an embodiment of the present disclosure.
  • FIG. 6 is a flowchart 1 of loading an Android desktop according to an embodiment of the present disclosure
  • FIG. 7A is a flowchart 2 of loading an Android desktop according to an embodiment of the present disclosure.
  • FIG. 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.
  • FIG. 9A is a flowchart 4 of loading an Android desktop according to an embodiment of the present disclosure.
  • 9B is a flowchart 4 of loading an Android desktop according to an embodiment of the present disclosure.
  • FIG. 1 is a schematic structural diagram of a software layered management system according to an embodiment of the present disclosure.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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
  • 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.
  • 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.
  • 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.
  • 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.
  • 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 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.
  • 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.
  • 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.
  • the Android system 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.
  • the virtual desktop operating system 103 includes: a Docker startup processor and a Docker manager.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • FIG. 3 is an architectural diagram of an embodiment of a software layered management system according to an embodiment of the present disclosure.
  • 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.
  • 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
  • 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
  • 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
  • FIG. 4 is a schematic diagram of a system loading template access according to an embodiment of the present disclosure
  • FIG. 5 is a schematic diagram of a Docker warehouse server according to an embodiment of the present disclosure
  • 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.
  • the process includes: a. Install the Docker startup processor in advance in the system pre-installed application; b.
  • 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.
  • 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.
  • the Android system 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.
  • 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.
  • FIG. 6 is a flowchart 1 of loading an Android desktop according to an embodiment of the present disclosure.
  • 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.
  • step S601 the basic software management module installs the Android virtual desktop.
  • step S602 an Android virtual desktop is generated through the basic software management module and distributed to users.
  • step S603 log in and click to connect to the virtual desktop through the desktop client of the Android mobile terminal.
  • 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.
  • step S605 the Android desktop operating system starts the interceptor and determines that there is no common software in the common software management module.
  • step S606 the system normally scans the local system applications of the Android system and the applications installed in the basic software management module.
  • step S607 the system normally starts the default system program, and at the same time presents the scanned application APP icon to the user.
  • FIGS. 7A and 7B are a flowchart 2 of loading an Android desktop according to an embodiment of the present disclosure.
  • 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.
  • step S701 the basic software management module installs the basic software of the Android virtual desktop.
  • 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.
  • 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;
  • step S703 an Android desktop is generated through the basic software management module and distributed to users.
  • step S704 the user uses an ordinary Android mobile terminal and installs a desktop client, logs in and clicks to connect to the desktop.
  • 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.
  • 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.
  • 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.
  • step S708 the Docker manager loads the software list in the newly added Docker container.
  • 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.
  • 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.
  • FIGS. 8A and 8B are a flowchart 3 of loading an Android desktop according to an embodiment of the present disclosure.
  • 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.
  • step S801 the basic software management module installs the basic software of the Android virtual desktop.
  • 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.
  • 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;
  • step S803 an Android desktop is generated through the basic software management module and distributed to users.
  • step S804 the user uses an ordinary Android mobile terminal and installs a desktop client, logs in and clicks to connect to the desktop.
  • 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.
  • 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.
  • 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.
  • 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.
  • step S809 the Docker manager loads the software list in the newly added Docker container with permissions.
  • 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.
  • 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.
  • FIGS. 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 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.
  • step S901 the basic software management module installs the software of the Android virtual desktop.
  • 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.
  • 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.
  • 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.
  • step S903 an Android desktop is generated through the basic software management module and distributed to users.
  • step S904 through the Android mobile terminal and installed a desktop client, log in and click to connect to the desktop.
  • 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.
  • 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.
  • step S907 the system normally scans the system application local to the Android system and the APP application software installed in the basic template.
  • 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.
  • step S909 the Docker manager loads the software list in the newly added Docker container with permission.
  • 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.
  • 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.
  • 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.
  • Android software can be installed free of use You can start the operation directly, and you can set different people to use different software.
  • 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.
  • a terminal device in a software hierarchical management system 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.
  • 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.

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Human Computer Interaction (AREA)
  • Stored Programmes (AREA)

Abstract

La présente invention concerne un système de gestion hiérarchique de logiciel, comprenant : un équipement terminal utilisé pour sélectionner, par connexion sur un client installé, une machine virtuelle dans une liste de machines virtuelles à utiliser, et se connecter à un bureau virtuel d'extrémité distante sur la base d'un protocole de connexion de bureau selon la machine virtuelle sélectionnée; un système de gestion de ressources de bureau virtuel utilisé pour gérer un système d'exploitation de bureau virtuel et des ressources de machine virtuelle de façon à fournir une configuration de base et une pluralité d'éléments de logiciel couramment utilisé à un bureau virtuel du système d'exploitation de bureau virtuel, des fichiers d'image de la pluralité d'éléments de logiciel couramment utilisé étant distribués dans une pluralité de contenants différents; et un système d'exploitation de bureau virtuel qui est installé sur un dispositif matériel physique et qui est utilisé pour obtenir la configuration de base du bureau virtuel à partir du système de gestion de ressources de bureau virtuel.
PCT/CN2019/128258 2018-12-26 2019-12-25 Système de gestion hiérarchique de logiciel WO2020135492A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201811605422.6A CN111367599B (zh) 2018-12-26 2018-12-26 一种软件分层管理系统
CN201811605422.6 2018-12-26

Publications (1)

Publication Number Publication Date
WO2020135492A1 true WO2020135492A1 (fr) 2020-07-02

Family

ID=71126369

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/128258 WO2020135492A1 (fr) 2018-12-26 2019-12-25 Système de gestion hiérarchique de logiciel

Country Status (2)

Country Link
CN (1) CN111367599B (fr)
WO (1) WO2020135492A1 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112084007A (zh) * 2020-09-10 2020-12-15 星辰天合（北京）数据科技有限公司 基于虚拟机技术的nas存储升级方法和装置
CN115826995A (zh) * 2022-10-31 2023-03-21 北京凯思昊鹏软件工程技术有限公司 一种分布式镜像构建系统
CN116483505A (zh) * 2023-05-08 2023-07-25 江苏云之遥信息科技有限公司 一种智能化的多功能云桌面系统

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112579143A (zh) * 2020-12-24 2021-03-30 江苏杰瑞信息科技有限公司 一种设计软件信息安全的管理平台系统
CN112667365B (zh) * 2021-01-22 2022-11-15 山东浪潮科学研究院有限公司 一种基于云边协同的桌面应用下发的系统、方法及设备
CN113191729A (zh) * 2021-04-26 2021-07-30 西安雷风电子科技有限公司 云桌面管理方法及系统
CN114546667A (zh) * 2022-04-25 2022-05-27 杭州筋斗腾云科技有限公司 即时办公空间的管理方法、系统及计算机设备

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8683466B2 (en) * 2011-05-24 2014-03-25 Vmware, Inc. System and method for generating a virtual desktop
CN106199696A (zh) * 2016-06-29 2016-12-07 中国石油天然气股份有限公司 地震数据处理系统和方法
CN107577937A (zh) * 2017-09-01 2018-01-12 深信服科技股份有限公司 一种应用程序保护方法及系统
CN108021425A (zh) * 2017-12-28 2018-05-11 南开大学 一种集成多个应用图形窗口的虚拟桌面系统及运行方法
CN108694065A (zh) * 2017-04-10 2018-10-23 鸿富锦精密电子(天津)有限公司 虚拟桌面系统及虚拟桌面控制方法

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106959882A (zh) * 2016-01-12 2017-07-18 深圳市深信服电子科技有限公司 虚拟桌面实现方法及装置

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8683466B2 (en) * 2011-05-24 2014-03-25 Vmware, Inc. System and method for generating a virtual desktop
CN106199696A (zh) * 2016-06-29 2016-12-07 中国石油天然气股份有限公司 地震数据处理系统和方法
CN108694065A (zh) * 2017-04-10 2018-10-23 鸿富锦精密电子(天津)有限公司 虚拟桌面系统及虚拟桌面控制方法
CN107577937A (zh) * 2017-09-01 2018-01-12 深信服科技股份有限公司 一种应用程序保护方法及系统
CN108021425A (zh) * 2017-12-28 2018-05-11 南开大学 一种集成多个应用图形窗口的虚拟桌面系统及运行方法

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112084007A (zh) * 2020-09-10 2020-12-15 星辰天合（北京）数据科技有限公司 基于虚拟机技术的nas存储升级方法和装置
CN115826995A (zh) * 2022-10-31 2023-03-21 北京凯思昊鹏软件工程技术有限公司 一种分布式镜像构建系统
CN115826995B (zh) * 2022-10-31 2023-07-14 北京凯思昊鹏软件工程技术有限公司 一种分布式镜像构建系统
CN116483505A (zh) * 2023-05-08 2023-07-25 江苏云之遥信息科技有限公司 一种智能化的多功能云桌面系统
CN116483505B (zh) * 2023-05-08 2024-03-19 江苏云之遥信息科技有限公司 一种智能化的多功能云桌面系统

Also Published As

Publication number Publication date
CN111367599A (zh) 2020-07-03
CN111367599B (zh) 2023-03-24

Similar Documents

Publication Publication Date Title
WO2020135492A1 (fr) Système de gestion hiérarchique de logiciel
JP6718530B2 (ja) 画像分析および管理
EP3588356B1 (fr) Gestion d'identité et d'accès entre des applications
CN107004095B (zh) 基于上下文的云安全保障系统
US9244671B2 (en) System and method for deploying preconfigured software
US10558407B2 (en) Availability of devices based on location
US10133525B2 (en) Autonomous secure printing
CN108604187B (zh) 托管的虚拟机部署
US10331599B2 (en) Employing session level restrictions to limit access to a redirected interface of a composite device
US9985949B2 (en) Secure assertion attribute for a federated log in
CN105378768A (zh) 企业系统中的接近度和环境感知的移动工作空间
US20180004585A1 (en) Application Programming Interface (API) Hub
CN105247531A (zh) 提供受管浏览器
US20200042578A1 (en) Document Object Model (DOM) Element Location Platform
US20140096208A1 (en) Automated system and method for provisioning and managing cloud desktop services
WO2020140264A1 (fr) Publication d'application dans un environnement virtualisé
EP4260181A1 (fr) Intégration d'applications natives pour un agrément amélioré de bureau à distance
US20130238673A1 (en) Information processing apparatus, image file creation method, and storage medium
EP2750350B1 (fr) Système et procédé de déploiement de logiciel préconfiguré
US11385946B2 (en) Real-time file system event mapping to cloud events
KR102436673B1 (ko) 클라우드 인프라 기반으로 구축된 가상환경의 파일 및 폴더의 백업 암호화 시스템
Preston et al. Using Chef Provisioning to Provision Machines
CN113906392A (zh) 用于提供不同版本的虚拟应用的系统和方法

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 19902654

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 16.11.2021)

122 Ep: pct application non-entry in european phase

Ref document number: 19902654

Country of ref document: EP

Kind code of ref document: A1