WO2015062217A1 - 虚拟桌面***中外设的接入处理方法及装置 - Google Patents
虚拟桌面***中外设的接入处理方法及装置 Download PDFInfo
- Publication number
- WO2015062217A1 WO2015062217A1 PCT/CN2014/075608 CN2014075608W WO2015062217A1 WO 2015062217 A1 WO2015062217 A1 WO 2015062217A1 CN 2014075608 W CN2014075608 W CN 2014075608W WO 2015062217 A1 WO2015062217 A1 WO 2015062217A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- driver
- peripheral
- management server
- virtual machine
- terminal
- Prior art date
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
- G06F13/10—Program control for peripheral devices
- G06F13/102—Program control for peripheral devices where the programme performs an interfacing function, e.g. device driver
-
- 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
- G06F2009/45579—I/O management, e.g. providing access to device drivers or storage
-
- 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/4401—Bootstrapping
- G06F9/4411—Configuring for operating with peripheral devices; Loading of device drivers
Definitions
- the present invention relates to the field of cloud computing, and in particular to a method and device for accessing peripherals in a virtual desktop system.
- Cloud computing is the development and commercial implementation of concepts such as distributed processing, parallel computing and grid computing. Its technical essence is the virtualization of IT hardware and software resources such as computing, storage, servers, and application software. Cloud computing is in virtualization and data storage. , data management, programming mode and other aspects have their own unique technology.
- Desktop virtual machine, server virtualization is an important cornerstone of cloud computing infrastructure.
- Cloud computing virtual desktops create and leverage a new cloud-based web application development and publishing platform while leveraging and highlighting the benefits of the desktop.
- the virtual desktop, the web desktop runs on the browser and can integrate web applications, web services, client ⁇ server applications, C ⁇ S application servers, and local client applications into a desktop environment.
- Cloud computing virtual desktops create and leverage a new cloud-based web application development and publishing platform while leveraging and highlighting the benefits of the desktop.
- peripherals there are numerous sub-categories of peripherals, and the interface can be divided into a Universal Serial Bus (USB) interface, a serial port, a parallel port, and the like.
- the slave device type can be divided into a printer, a USB flash drive, a scanner, a password input device, an evaluator, a dongle, and the like.
- each type of peripheral is divided into different manufacturers and different models. If a variety of peripherals are connected to the virtual desktop system, the conventional means is to install the corresponding peripheral driver and debug on each thin terminal and each desktop virtual machine separately. The work is cumbersome and huge, and a lot of repetitive work is still done.
- the thin terminal is a device that uses a virtual desktop, and is generally a device embedded with a separate embedded operating system, which can be connected to a desktop running on the server through various protocols.
- the current peripheral redirection management has the following problems: The same peripheral driver needs to be manually re-installed and commissioned in each terminal and desktop virtual machine, and the resource investment is high. In view of the above problems in the related art, an effective solution has not yet been proposed. SUMMARY OF THE INVENTION The present invention provides a method and an apparatus for accessing a peripheral device in a virtual desktop system to solve at least the above problems.
- a method for accessing peripherals in a virtual desktop system including: acquiring, when accessing a peripheral device of a terminal where the virtual machine is located, obtaining from a peripheral drive management server of the virtual desktop system The driver of the peripheral; the above driver is sent to the above virtual machine for installation.
- the obtaining the driver of the peripheral device from the peripheral drive management server of the virtual desktop system comprises: receiving a notification message from the virtual machine, wherein the notification message carries type information of the peripheral device; the notification message And the following information is used to notify the peripheral drive management server: the peripheral device has accessed the terminal; and the driver corresponding to the type information is obtained from the peripheral drive management server.
- the obtaining the driver corresponding to the type information from the peripheral drive management server includes: searching for a driver corresponding to the type information from a driver stored in advance by the peripheral drive management server.
- the method before acquiring the driver corresponding to the type information from the peripheral drive management server, the method includes: receiving, by the peripheral drive management server, the driver that is uploaded by the virtual machine, where the driver is stored in the terminal in.
- the method before the foregoing peripheral drive management server receives the driver uploaded by the virtual machine, the method includes: determining that the driver is not pre-stored in the peripheral drive management server.
- the method includes: acquiring configuration information of the virtual machine and the terminal; determining, according to the configuration information, whether to send the driver, where determining the configuration information When the above driver is adapted, it is determined that the above driver is issued.
- an access processing apparatus for a peripheral device in a virtual desktop system including: a detecting module, configured to detect whether a terminal where the virtual machine is located is connected to a peripheral device; and an acquiring module, configured to be inspected When the terminal where the virtual machine is located is connected to the peripheral device, the driver of the peripheral device is obtained from the peripheral drive management server of the virtual desktop system; and the sending module is configured to deliver the driver to the virtual machine for installation.
- the obtaining module includes: a receiving unit, configured to receive a notification message from the virtual machine, where the notification message carries type information of the peripheral device; and the notification message is used to notify the peripheral driving management server Information:
- the above peripheral device has accessed the terminal; the obtaining unit is configured to acquire a driver corresponding to the type information from the peripheral drive management server.
- the acquisition unit is configured to search for a driver corresponding to the type information from a driver stored in advance by the peripheral drive management server.
- the receiving unit is configured to receive, by the peripheral driving management server, the driver that is uploaded by the virtual machine, wherein the driver is stored in the terminal.
- the embodiment of the present invention solves the related art by acquiring a driver from a peripheral drive management server of a virtual desktop system and delivering the driver to the virtual machine for installation when detecting that the terminal of the virtual machine is connected to the peripheral device.
- the peripheral driver In the case of the peripheral driver, the problem of wasted resources caused by manual re-installation is increased, thereby improving the debugging efficiency of peripheral access.
- FIG. 1 is a flow chart of a method for access processing of a peripheral device in a virtual desktop system according to an embodiment of the present invention
- FIG. 2 is a block diagram showing a structure of an access processing device for a peripheral device in a virtual desktop system according to an embodiment of the present invention
- FIG. 3 is another structural block diagram of an access processing device for a peripheral device in a virtual desktop system according to an embodiment of the present invention
- FIG. 4 is a schematic diagram of a method for debugging a manually deployed peripheral redirection driver in the related art
- FIG. The user pre-deployment of the driver package version of the embodiment of the invention solves the seamless access of the peripheral device
- FIG. 6 is a schematic diagram of the user seamlessly accessing the peripheral without the pre-deployment of the driver package version according to the embodiment of the invention.
- Step S102 When detecting that the terminal where the virtual machine is located accesses the peripheral device, obtain the driver of the peripheral device from the peripheral drive management server of the virtual desktop system.
- the processing step may be implemented by: receiving a notification message from the virtual machine, where the notification message carries type information of a peripheral; the notification message is used to notify the peripheral driver management server of the following information: Accessing the terminal; acquiring a driver corresponding to the type information from the peripheral drive management server.
- Accessing the terminal acquiring a driver corresponding to the type information from the peripheral drive management server.
- the meaning of "access” here is the physical connection on the hardware.
- the first processing method pre-stores the drivers of various peripherals on the peripheral drive management server, that is, searches from the driver pre-stored by the peripheral drive management server. A driver corresponding to the above type information.
- the second processing method is to obtain the peripheral driver management server from the terminal where the virtual machine is located, and then deliver the obtained driver to the virtual machine.
- the above-mentioned driver uploaded by the virtual machine is received by the peripheral drive management server, wherein the driver is stored in the terminal.
- the first processing method can be used in combination with the second processing method.
- the second processing method is adopted. Get the above driver.
- the driver is delivered to the virtual machine for installation. Before the driver is sent to the virtual machine for installation, the configuration information of the virtual machine and the terminal may be acquired; Determining whether to issue the driver according to the configuration information, wherein when determining that the configuration information is adapted to the driver, it is determined that the driver is delivered.
- the maintenance personnel can pre-deploy the driver package of various peripherals in the desktop background system (that is, in the peripheral drive management).
- the driver is pre-stored in the server, and the peripheral configuration information is entered.
- the system automatically deploys the driver corresponding to the peripheral on the thin terminal, and automatically executes the driver. Install and deploy the corresponding peripheral driver in the connected desktop VM.
- the system automatically deploys the peripheral driver, it will automatically determine the operating system type and hard disk space of the thin terminal, the operating system type of the virtual machine, and the hard disk space. If the required conditions are not met, the automatic deployment operation is not performed.
- the desktop background system does not pre-deploy the peripheral driver package in the desktop system according to the description of the first processing method as above, when the client is inserting in the thin terminal.
- the system will prompt the client to enter the peripheral installation package placed locally by the thin terminal into the background system, and prompt the customer to confirm the corresponding device information according to the currently inserted device, and the background system confirms according to the customer.
- the action record drives the configuration information corresponding to the package.
- the entered driver package serves as the basis for subsequent automatic deployment of other terminals.
- the system When the system automatically deploys the peripheral driver, it will automatically determine the operating system type and hard disk space of the thin terminal, the operating system type of the virtual machine, and the hard disk space. If the required conditions are not met, the automatic deployment operation is not performed.
- an access processing device based on a peripheral device in a virtual desktop system is also provided, which is used to implement the foregoing embodiments and preferred embodiments, and has not been described again.
- the module is explained.
- the term "module" may implement a combination of software and/or hardware of a predetermined function.
- the device includes: a detecting module 20, connected to the obtaining module 22, configured to detect whether a terminal where the virtual machine is located is connected to the peripheral device; and an obtaining module 22 connected to the sending module 24, configured to detect the virtual machine
- the driver of the peripheral device is obtained from the peripheral drive management server of the virtual desktop system; and the sending module 24 is configured to deliver the driver to the virtual machine for installation.
- the sending module 24 is configured to deliver the driver to the virtual machine for installation.
- the obtaining module 22 may include the following processing unit:
- the receiving unit 220 is configured to receive a notification message from the virtual machine, where the notification message carries type information of the peripheral device, and the notification message is used to notify the peripheral driving management server of the following information:
- the foregoing terminal the obtaining unit 222 is connected to the receiving unit 220, and is configured to acquire a driver corresponding to the type information from the peripheral driving management server.
- the obtaining unit 222 may be further configured to search for a driver corresponding to the type information from a driver stored in advance by the peripheral drive management server.
- the receiving unit 220 may further be configured to receive, by the peripheral driving management server, the driver that is uploaded by the virtual machine, wherein the driver is stored in the terminal.
- FIG. 4 shows a debugging method of the existing manual deployment peripheral redirection driver.
- the method may include the following processing steps: Step S402: Connect a printer to the thin terminal.
- Step S404 the user manually installs the driver package of the printer on the thin terminal.
- Step S406 the user manually installs a printer driver package on the virtual machine connected to the thin terminal to complete peripheral access.
- the first processing manner is as shown in FIG. 5, and the processing manner includes: Step S502: Connect a printer to the thin terminal.
- Step S504 pre-deploying the printer driver installation package on the peripheral drive management server.
- the peripheral drive management server first turns on the write protection of the thin terminal, and then actively according to the type of the peripheral accessed on the thin terminal.
- the printer driver package is delivered to the thin terminal, and the peripheral driver package is automatically installed and deployed.
- the peripheral drive management server queries the cloud management server for the virtual machine information connected by the thin terminal.
- the peripheral drive management server actively delivers the printer driver package to the virtual machine connected to the thin terminal, and automatically installs and deploys the peripheral driver package on the virtual machine to complete the peripheral driver package deployment.
- the seamless peripheral access scheme described above mainly deploys the driver package on the peripheral drive management server in advance.
- the agent on the thin terminal When a peripheral device is connected to the thin terminal, the agent on the thin terminal will be like the peripheral drive management server.
- the report server automatically delivers the driver package to the thin terminal according to the reported message type. If the virtual machine connected to the thin terminal does not have the corresponding driver package installed, the peripheral driver package management server will automatically install and install the peripheral driver package in the corresponding virtual machine. No human intervention is required throughout the process. It greatly simplifies the operation process and improves the efficiency of peripheral driver access commissioning.
- the second processing mode is as shown in FIG. 6.
- the processing manner includes the following processing steps: Step S602: On the thin terminal, access a printer, that is, peripheral access. Step S604, there is no driver installation package of the printer on the peripheral drive management server (corresponding to the drive package 5 in FIG. 6).
- the user When the printer is connected to the thin terminal, the user first deploys the driver version of the printer on the thin terminal. .
- the agent on the thin terminal automatically uploads the peripheral driver package not on the peripheral management server.
- the peripheral drive management server may first query the virtual machine information connected by the thin terminal, and then actively deliver the printer driver package to the virtual machine connected to the thin terminal, and automatically install and deploy the peripheral driver package on the virtual machine, completing the external Set up the driver package deployment.
- the technical solution in the foregoing embodiment may implement a scheme in which a peripheral drive management server pushes a peripheral drive package to a specific thin terminal or a virtual machine.
- the embodiments of the present invention achieve the following beneficial effects: reduce the workload of maintenance personnel, and reduce the possibility of manual error, and at the same time, the existing network implementation scheme is less modified, and has strong practicability. It also reduces the complexity of peripheral access debugging and improves the efficiency of peripheral access debugging.
- software is also provided for performing the technical solutions described in the above embodiments and preferred embodiments.
- a storage medium is provided, the software being stored, including but not limited to: an optical disk, a floppy disk, a hard disk, a rewritable memory, and the like.
- modules or steps of the present invention can be implemented by a general-purpose computing device, which can be concentrated on a single computing device or distributed over a network composed of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device, such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein.
- the steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps are fabricated as a single integrated circuit module.
- the invention is not limited to any specific combination of hardware and software.
- the above are only the preferred embodiments of the present invention, and are not intended to limit the present invention, and various modifications and changes can be made to the present invention.
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
本发明提供了一种虚拟桌面***中外设的接入处理方法及装置,其中,该方法包括:在检测到虚拟机所在终端接入外设时,从虚拟桌面***的外设驱动管理服务器中获取该外设的驱动程序;将所述驱动程序下发至所述虚拟机进行安装。采用本发明提供的上述技术方案,解决了相关技术中对于外设的驱动程序需要人工重复安装而导致的浪费资源等问题,从而提高了外设接入的调试效率。
Description
虚拟桌面***中外设的接入处理方法及装置 技术领域 本发明涉及云计算领域, 具体而言, 涉及一种虚拟桌面***中外设的接入处理方 法及装置。 背景技术 随着 IT技术的演进, 基础架构方面也在推陈出新, 伴随虚拟化技术的不断成熟, 云计算也发展到了新的阶段。 云计算是分布式处理、 并行计算和网格计算等概念的发 展和商业实现, 其技术实质是计算、 存储、 服务器、 应用软件等 IT软硬件资源的虚拟 化, 云计算在虚拟化、 数据存储、 数据管理、 编程模式等方面具有自身独特的技术。 桌面虚拟机, 即服务器虚拟化是云计算底层架构的重要基石。在服务器虚拟化中, 虚拟化软件需要实现对硬件的抽象, 资源的分配、 调度和管理, 虚拟机与宿主操作系 统及多个虚拟机间的隔离等功能, 目前典型的实现(基本成为事实标准)有 Citrix Xeiu VMware ESX Server和 Microsoft Hype-V等。 云计算的虚拟桌面是利用和突出桌面优点的同时创建一种新的基于云计算的 Web 应用开发和发布平台。 虚拟桌面即 Web桌面, 运行在浏览器上, 能整合 Web应用、 Web服务、 客户端 (Client) \服务器 (Server) 应用、 C\S应用服务器以及本地客户端 应用到一个桌面环境上。 云计算的虚拟桌面是利用和突出桌面优点的同时创建一种新 的基于云计算的 Web应用开发和发布平台。 目前在虚拟桌面应用过程中, 分门别类的外设数不胜数, 从接口可分为通用串行 总线 (Universal Serial Bus, 简称为 USB ) 接口、 串口、 并口等。 从设备类型可分为打 印机、 USB闪存驱动器、 扫描仪、 密码输入器、 评价器、 加密狗等。 而且每种外设还 分为不同的厂家和不同的型号。 如果在虚拟桌面***中接入各种外设, 常规的手段是 需要在每个瘦终端和每个桌面虚拟机上分别安装相应的外设驱动并且调试, 工作繁琐 且巨大, 大量重复的工作还会出现传错安装包、 空间不够等因素导致外设驱动安装不 正常, 对问题排查也有很大难度。 其中, 瘦终端是使用虚拟桌面的设备, 一般是一个 内嵌了独立的嵌入式操作***, 可以通过各种协议连接到运行在服务器上的桌面的设 备。
当前外设重定向管理存在以下问题: 同样的外设驱动需要在每个终端和桌面虚拟 机中人工重复安装和调测, 资源投入高。 针对相关技术中的上述问题, 目前尚未提出有效的解决方案。 发明内容 针对相关技术中, 对于外设的驱动程序需要人工重复安装而导致的浪费资源等问 题, 本发明实施例提供了一种虚拟桌面***中外设的接入处理方法及装置, 以至少解 决上述问题。 根据本发明的一个实施例, 提供了一种虚拟桌面***中外设的接入处理方法, 包 括: 在检测到虚拟机所在终端接入外设时, 从虚拟桌面***的外设驱动管理服务器中 获取该外设的驱动程序; 将上述驱动程序下发至上述虚拟机进行安装。 优选地, 从虚拟桌面***的外设驱动管理服务器中获取该外设的驱动程序,包括: 接收来自上述虚拟机的通知消息, 其中, 上述通知消息携带有上述外设的类型信息; 上述通知消息用于通知上述外设驱动管理服务器以下信息: 上述外设已经接入上述终 端; 从上述外设驱动管理服务器中获取与上述类型信息对应的驱动程序。 优选地, 从上述外设驱动管理服务器中获取与上述类型信息对应的驱动程序, 包 括: 从上述外设驱动管理服务器预先存储的驱动程序中查找与上述类型信息对应的驱 动程序。 优选地,从上述外设驱动管理服务器中获取与上述类型信息对应的驱动程序之前, 包括: 通过上述外设驱动管理服务器接收上述虚拟机上传的上述驱动程序, 其中, 上 述驱动程序存储于上述终端中。 优选地,通过上述外设驱动管理服务器接收上述虚拟机上传的上述驱动程序之前, 包括: 确定上述外设驱动管理服务器中未预先存储上述驱动程序。 优选地, 将上述驱动程序下发至上述虚拟机进行安装之前, 包括: 获取上述虚拟 机和上述终端的配置信息; 根据上述配置信息判断是否下发上述驱动程序, 其中, 在 确定上述配置信息与上述驱动程序相适配时, 确定下发上述驱动程序。 根据本发明的另一个实施例,还提供了一种虚拟桌面***中外设的接入处理装置, 包括: 检测模块, 设置为检测虚拟机所在终端是否接入外设; 获取模块, 设置为在检
测到虚拟机所在终端接入外设时, 从虚拟桌面***的外设驱动管理服务器中获取该外 设的驱动程序; 发送模块, 设置为将上述驱动程序下发至上述虚拟机进行安装。 优选地, 上述获取模块, 包括: 接收单元, 设置为接收来自上述虚拟机的通知消 息, 其中, 上述通知消息携带有上述外设的类型信息; 上述通知消息用于通知上述外 设驱动管理服务器以下信息: 上述外设已经接入上述终端; 获取单元, 设置为从上述 外设驱动管理服务器中获取与上述类型信息对应的驱动程序。 优选地, 上述获取单元, 设置为从上述外设驱动管理服务器预先存储的驱动程序 中查找与上述类型信息对应的驱动程序。 优选地, 上述接收单元, 设置为通过上述外设驱动管理服务器接收上述虚拟机上 传的上述驱动程序, 其中, 上述驱动程序存储于上述终端中。 通过本发明实施例, 采用在检测到虚拟机所在终端接入外设时, 从虚拟桌面*** 的外设驱动管理服务器中获取驱动程序并下发至虚拟机进行安装的技术手段, 解决了 相关技术中, 对于外设的驱动程序需要人工重复安装而导致的浪费资源等问题, 从而 提高了外设接入的调试效率。 附图说明 此处所说明的附图用来提供对本发明的进一步理解, 构成本申请的一部分, 本发 明的示意性实施例及其说明用于解释本发明, 并不构成对本发明的不当限定。 在附图 中- 图 1为根据本发明实施例的虚拟桌面***中外设的接入处理方法的流程图; 图 2为根据本发明实施例的虚拟桌面***中外设的接入处理装置的结构框图; 图 3 为根据本发明实施例的虚拟桌面***中外设的接入处理装置的另一结构框 图; 图 4为相关技术中手工部署外设重定向驱动的调测方法示意图; 图 5为根据本发明实施例的用户预先部署驱动包版本解决外设无缝接入示意图; 以及 图 6为根据本发明实施例的用户没有预先部署驱动包版本解决外设无缝接入示意 图。
具体实施方式 下文中将参考附图并结合实施例来详细说明本发明。 需要说明的是, 在不冲突的 情况下, 本申请中的实施例及实施例中的特征可以相互组合。 以下实施例可以应用到计算机中, 例如应用到 PC 中。 也可以应用到目前采用了 智能操作***中的移动终端中, 还可以应用到云计算的虚拟机所在瘦终端中, 并不限 于此。 对于计算机或移动终端的操作***并没有特殊要求。 例如, 以下实施例可以应 用到 Windows操作***中。 图 1为根据本发明实施例的虚拟桌面***中外设的接入处理方法的流程图。 如图 1所示, 该方法包括以下处理步骤: 步骤 S102,在检测到虚拟机所在终端接入外设时,从虚拟桌面***的外设驱动管 理服务器中获取该外设的驱动程序。 该处理步骤可以通过以下处理过程实现: 接收来自上述虚拟机的通知消息,其中, 该通知消息携带有外设的类型信息; 上述通知消息用于通知外设驱动管理服务器以下 信息: 上述外设已经接入上述终端; 从外设驱动管理服务器中获取与上述类型信息对 应的驱动程序。 需要说明的是, 此处 "接入"的含义为硬件上的物理连接。 更具体地, 可以通过以下两种方式获取上述驱动程序: 第一种处理方式 在外设驱动管理服务器上预先存储各种外设的驱动程序, 即从外设驱动管理服务 器预先存储的驱动程序中查找与上述类型信息对应的驱动程序。 第二种处理方式 外设驱动管理服务器先从虚拟机所在终端获取, 然后再将获取的驱动程序下发至 虚拟机。 具体地, 通过外设驱动管理服务器接收上述虚拟机上传的上述驱动程序, 其 中, 上述驱动程序存储于上述终端中。 需要说明的是, 第一种处理方式可以和第二种处理方式结合使用, 例如, 可以优 先选用第一种处理方式, 在外设驱动管理服务器中未预先存储驱动程序时, 采用第二 种处理方式获取上述驱动程序。 步骤 S104,将上述驱动程序下发至上述虚拟机进行安装。在将上述驱动程序下发 至上述虚拟机进行安装之前, 还可以获取上述虚拟机和上述终端的配置信息; 根据上
述配置信息判断是否下发上述驱动程序, 其中, 在确定上述配置信息与上述驱动程序 相适配时, 确定下发上述驱动程序。 对于上述两种处理方式, 在具体实施时可以表现为以下两种实现过程: 对于第一种处理方式, 维护人员可预先在桌面后台***中部署各种外设的驱动包 (即在外设驱动管理服务器中预先存储驱动程序),并录入外设配置信息, 当桌面*** 中有该种类型的外设接入时, ***自动在瘦终端上部署安装该外设对应的驱动, 并且 自动在该外设已经连接的桌面虚拟机中安装部署相应的外设驱动。 ***自动部署的外 设驱动的时候, 会自动判断瘦终端的操作***类型和硬盘空间、 虚拟机的操作***类 型和硬盘空间等信息。 如果不满足需要条件, 不进行自动部署操作。 对于第二种处理方式, 客户需要使用一种全新的外设类型, 桌面后台***中没有 按照如上第一种处理方式的描述预先在桌面***中部署外设驱动包, 当客户在瘦终端 在***新的外设的时候, ***将提示客户端是否把瘦终端本地放置的外设安装包录入 到后台***中, 并根据当前已经***的设备提示客户确认相应的设备信息, 后台*** 根据客户的确认动作记录驱动包对应的配置信息。 该录入的驱动包作为后续其他终端 自动部署的依据。 ***自动部署的外设驱动的时候, 会自动判断瘦终端的操作***类 型和硬盘空间、 虚拟机的操作***类型和硬盘空间等信息。 如果不满足需要条件, 不 进行自动部署操作。 在本实施例中还提供了一种基于虚拟桌面***中外设的接入处理装置, 用于实现 上述实施例及优选实施方式, 已经进行过说明的不再赘述, 下面对该装置中涉及到的 模块进行说明。 如以下所使用的, 术语 "模块"可以实现预定功能的软件和 /或硬件的 组合。 尽管以下实施例所描述的装置较佳地以软件来实现, 但是硬件, 或者软件和硬 件的组合的实现也是可能并被构想的。 图 2为根据本发明实施例的虚拟桌面***中外 设的接入处理装置的结构框图。 如图 2所示, 该装置包括: 检测模块 20, 连接至获取模块 22, 设置为检测虚拟机所在终端是否接入外设; 获取模块 22, 连接至发送模块 24, 设置为在检测到虚拟机所在终端接入外设时, 从虚拟桌面***的外设驱动管理服务器中获取该外设的驱动程序; 发送模块 24, 设置为将上述驱动程序下发至上述虚拟机进行安装。 可选地, 如图 3所示, 获取模块 22, 可以包括以下处理单元:
接收单元 220, 设置为接收来自上述虚拟机的通知消息, 其中, 上述通知消息携 带有上述外设的类型信息;上述通知消息用于通知上述外设驱动管理服务器以下信息: 上述外设已经接入上述终端; 获取单元 222, 连接至接收单元 220, 设置为从上述外设驱动管理服务器中获取 与上述类型信息对应的驱动程序。 在本实施例中, 获取单元 222, 还可以设置为从上述外设驱动管理服务器预先存 储的驱动程序中查找与上述类型信息对应的驱动程序。 在本实施例中, 接收单元 220, 还可以设置为通过上述外设驱动管理服务器接收 上述虚拟机上传的上述驱动程序, 其中, 上述驱动程序存储于上述终端中。 为了更好地理解上述实施例, 以下以打印机为例进行说明。 图 4示出了现有手工部署外设重定向驱动的调测方法, 如图 4所示, 该方法可以 包括以下处理步骤: 步骤 S402, 在瘦终端上, 接入一个打印机。 步骤 S404, 用户手工在瘦终端上安装打印机的驱动包。 步骤 S406,用户手工在此瘦终端连接的虚拟机上安装打印机驱动包,完成外设接 入。 显然, 上述处理过程都需要手工安装部署驱动包, 整个过程复杂, 浪费很多人力 成本。 为解决上述问题, 以下提供了两种处理方式: 第一种处理方式 如图 5所示, 该处理方式包括: 步骤 S502, 在瘦终端上, 接入一个打印机。 步骤 S504,在外设驱动管理服务器上预先部署打印机驱动安装包, 当瘦终端上接 入打印机时, 外设驱动管理服务器首先打开瘦终端的写保护, 然后根据瘦终端上接入 的外设类型主动下发打印机驱动包到瘦终端上, 并自动安装部署外设驱动包。
步骤 S506, 外设驱动管理服务器在云管理服务器上查询瘦终端连接的虚拟机信 息。 步骤 S508, 外设驱动管理服务器对瘦终端上连接的虚拟机主动下发打印机驱动 包, 并自动在虚拟机上安装部署外设驱动包, 完成外设驱动包部署。 上面所述的无缝外设接入方案, 主要是通过预先在外设驱动管理服务器上部署驱 动包, 当有外设在瘦终端上接入时, 瘦终端上的代理会像外设驱动管理服务器上报消 息, 管理服务器根据上报的消息类型自动下发驱动包到瘦终端上安装。 如果该瘦终端 连接的虚拟机也没有安装相应的驱动包, 外设驱动包管理服务器也会自动在相应的虚 拟机上下发安装外设驱动包。 整个过程无需人工干预。 大大简化了操作流程, 提高了 外设驱动接入调测的效率。 第二种处理方式 如图 6所示, 该处理方式包括以下处理步骤: 步骤 S602, 在瘦终端上, 接入一个打印机, 即外设接入。 步骤 S604, 在外设驱动管理服务器上无此打印机的驱动安装包 (对应图 6中的 驱动包 5), 当瘦终端上接入打印机时, 用户会在首先在瘦终端上部署该打印机的驱动 版本。 步骤 S606, 瘦终端上的代理会自动上传外设管理服务器上没有的外设驱动包。 步骤 S608,外设驱动管理服务器可以先查询瘦终端连接的虚拟机信息,然后对瘦 终端上连接的虚拟机主动下发打印机驱动包,并自动在虚拟机上安装部署外设驱动包, 完成外设驱动包部署。 上述实施例中的技术方案可以实现在外设驱动管理服务器对某些特定瘦终端或者 虚拟机推送下发外设驱动包等方案。 综上所述, 本发明实施例实现了以下有益效果: 减少了维护人员工作量, 并相应减少人工出错的可能性, 同时对现有的网络实施 方案改造较小, 具有极强的实用性, 还降低外设接入调试复杂性, 提高外设接入调试 效率。
在另外一个实施例中, 还提供了一种软件, 该软件用于执行上述实施例及优选实 施方式中描述的技术方案。 在另外一个实施例中, 还提供了一种存储介质, 该存储介质中存储有上述软件, 该存储介质包括但不限于: 光盘、 软盘、 硬盘、 可擦写存储器等。 显然, 本领域的技术人员应该明白, 上述的本发明的各模块或各步骤可以用通用 的计算装置来实现, 它们可以集中在单个的计算装置上, 或者分布在多个计算装置所 组成的网络上, 可选地, 它们可以用计算装置可执行的程序代码来实现, 从而, 可以 将它们存储在存储装置中由计算装置来执行, 并且在某些情况下, 可以以不同于此处 的顺序执行所示出或描述的步骤, 或者将它们分别制作成各个集成电路模块, 或者将 它们中的多个模块或步骤制作成单个集成电路模块来实现。 这样, 本发明不限制于任 何特定的硬件和软件结合。 以上仅为本发明的优选实施例而已, 并不用于限制本发明, 对于本领域的技术人 员来说, 本发明可以有各种更改和变化。 凡在本发明的精神和原则之内, 所作的任何 修改、 等同替换、 改进等, 均应包含在本发明的保护范围之内。 工业实用性 采用本发明提供的上述技术方案, 可以应用于虚拟桌面***中外设的接入处理过 程中, 采用在检测到虚拟机所在终端接入外设时, 从虚拟桌面***的外设驱动管理服 务器中获取驱动程序并下发至虚拟机进行安装的技术手段, 解决了相关技术中, 对于 外设的驱动程序需要人工重复安装而导致的浪费资源等问题, 从而提高了外设接入的 调试效率。
Claims
1. 一种虚拟桌面***中外设的接入处理方法, 包括:
在检测到虚拟机所在终端接入外设时, 从虚拟桌面***的外设驱动管理服 务器中获取该外设的驱动程序;
将所述驱动程序下发至所述虚拟机进行安装。
2. 根据权利要求 1所述的方法, 其中, 从虚拟桌面***的外设驱动管理服务器中 获取该外设的驱动程序, 包括:
接收来自所述虚拟机的通知消息, 其中, 所述通知消息携带有所述外设的 类型信息; 所述通知消息用于通知所述外设驱动管理服务器以下信息: 所述外 设已经接入所述终端;
从所述外设驱动管理服务器中获取与所述类型信息对应的驱动程序。
3. 根据权利要求 2所述的方法, 其中, 从所述外设驱动管理服务器中获取与所述 类型信息对应的驱动程序, 包括:
从所述外设驱动管理服务器预先存储的驱动程序中查找与所述类型信息对 应的驱动程序。
4. 根据权利要求 2所述的方法, 其中, 从所述外设驱动管理服务器中获取与所述 类型信息对应的驱动程序之前, 包括:
通过所述外设驱动管理服务器接收所述虚拟机上传的所述驱动程序,其中, 所述驱动程序存储于所述终端中。
5. 根据权利要求 4所述的方法, 其中, 通过所述外设驱动管理服务器接收所述虚 拟机上传的所述驱动程序之前, 包括:
确定所述外设驱动管理服务器中未预先存储所述驱动程序。
6. 根据权利要求 1至 5中任一项所述的方法, 其中, 将所述驱动程序下发至所述 虚拟机进行安装之前, 包括:
获取所述虚拟机和所述终端的配置信息; 根据所述配置信息判断是否下发所述驱动程序, 其中, 在确定所述配置信 息与所述驱动程序相适配时, 确定下发所述驱动程序。
一种虚拟桌面***中外设的接入处理装置, 包括: 检测模块, 设置为检测虚拟机所在终端是否接入外设;
获取模块, 设置为在检测到虚拟机所在终端接入外设时, 从虚拟桌面*** 的外设驱动管理服务器中获取该外设的驱动程序;
发送模块, 设置为将所述驱动程序下发至所述虚拟机进行安装。 根据权利要求 7所述的装置, 其中, 所述获取模块, 包括: 接收单元, 设置为接收来自所述虚拟机的通知消息, 其中, 所述通知消息 携带有所述外设的类型信息; 所述通知消息用于通知所述外设驱动管理服务器 以下信息: 所述外设已经接入所述终端;
获取单元, 设置为从所述外设驱动管理服务器中获取与所述类型信息对应 的驱动程序。 根据权利要求 8所述的装置, 其中, 所述获取单元, 设置为从所述外设驱动管 理服务器预先存储的驱动程序中查找与所述类型信息对应的驱动程序。 根据权利要求 8所述的装置, 其中, 所述接收单元, 设置为通过所述外设驱动 管理服务器接收所述虚拟机上传的所述驱动程序, 其中, 所述驱动程序存储于 所述终端中。
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201310531033.4 | 2013-10-31 | ||
CN201310531033.4A CN104601617A (zh) | 2013-10-31 | 2013-10-31 | 虚拟桌面***中外设的接入处理方法及装置 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2015062217A1 true WO2015062217A1 (zh) | 2015-05-07 |
Family
ID=53003238
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2014/075608 WO2015062217A1 (zh) | 2013-10-31 | 2014-04-17 | 虚拟桌面***中外设的接入处理方法及装置 |
Country Status (2)
Country | Link |
---|---|
CN (1) | CN104601617A (zh) |
WO (1) | WO2015062217A1 (zh) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11453131B2 (en) | 2019-12-30 | 2022-09-27 | UiPath, Inc. | Method and apparatus for remote native automation decoupling |
Families Citing this family (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2017027385A (ja) * | 2015-07-23 | 2017-02-02 | 富士ゼロックス株式会社 | 情報処理システム、端末装置及びプログラム |
CN107957900A (zh) * | 2016-10-17 | 2018-04-24 | 中兴通讯股份有限公司 | 一种虚拟环境下对远程iso进行管控的方法及相关装置 |
CN108170505A (zh) * | 2016-12-07 | 2018-06-15 | 华为技术有限公司 | 一种驱动管理方法及宿主机 |
JP7027809B2 (ja) * | 2017-10-31 | 2022-03-02 | 京セラドキュメントソリューションズ株式会社 | アップデートシステム |
CN108153579A (zh) * | 2017-12-29 | 2018-06-12 | 佛山市幻云科技有限公司 | 桌面云外设接入*** |
CN109857465A (zh) * | 2018-11-23 | 2019-06-07 | 广东微云科技股份有限公司 | 一种云桌面usb驱动的自动安装方法和*** |
CN113448672A (zh) * | 2021-06-30 | 2021-09-28 | 深信服科技股份有限公司 | 设备控制方法、目标终端、云端、虚拟桌面服务器及介质 |
CN114327504A (zh) * | 2021-12-01 | 2022-04-12 | 阿里巴巴(中国)有限公司 | 通信方法及*** |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101008903A (zh) * | 2006-01-23 | 2007-08-01 | 联想(北京)有限公司 | 一种虚拟机***及其设备访问方法 |
CN102023960A (zh) * | 2009-09-14 | 2011-04-20 | 联想(北京)有限公司 | 计算机网络***、计算机及其硬件设备远程管理的方法 |
CN102402446A (zh) * | 2011-11-22 | 2012-04-04 | 成都市华为赛门铁克科技有限公司 | 应用软件的安装方法和应用软件的安装装置 |
CN103246544A (zh) * | 2013-04-09 | 2013-08-14 | 何钦淋 | 虚拟硬件驱动终端及驱动方法 |
Family Cites Families (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8312471B2 (en) * | 2010-04-26 | 2012-11-13 | Vmware, Inc. | File system independent content aware cache |
CN102270186B (zh) * | 2011-07-21 | 2013-03-20 | 华中科技大学 | 一种虚拟桌面外部设备支持*** |
CN102385523A (zh) * | 2011-10-12 | 2012-03-21 | 中山爱科数字科技有限公司 | 一种云操作***的驱动安装和管理方法 |
CN202268914U (zh) * | 2011-10-19 | 2012-06-06 | 深圳市京华科讯科技有限公司 | 一种应用虚拟化外设结构 |
-
2013
- 2013-10-31 CN CN201310531033.4A patent/CN104601617A/zh active Pending
-
2014
- 2014-04-17 WO PCT/CN2014/075608 patent/WO2015062217A1/zh active Application Filing
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101008903A (zh) * | 2006-01-23 | 2007-08-01 | 联想(北京)有限公司 | 一种虚拟机***及其设备访问方法 |
CN102023960A (zh) * | 2009-09-14 | 2011-04-20 | 联想(北京)有限公司 | 计算机网络***、计算机及其硬件设备远程管理的方法 |
CN102402446A (zh) * | 2011-11-22 | 2012-04-04 | 成都市华为赛门铁克科技有限公司 | 应用软件的安装方法和应用软件的安装装置 |
CN103246544A (zh) * | 2013-04-09 | 2013-08-14 | 何钦淋 | 虚拟硬件驱动终端及驱动方法 |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11453131B2 (en) | 2019-12-30 | 2022-09-27 | UiPath, Inc. | Method and apparatus for remote native automation decoupling |
Also Published As
Publication number | Publication date |
---|---|
CN104601617A (zh) | 2015-05-06 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2015062217A1 (zh) | 虚拟桌面***中外设的接入处理方法及装置 | |
US9588794B2 (en) | Method, system and device for managing software on virtual machine in cloud environment | |
US20220179682A1 (en) | Task processing method, apparatus, and system based on distributed system | |
US9612814B2 (en) | Network topology-aware recovery automation | |
US8997090B2 (en) | Installing an operating system in a host system | |
CN102932408B (zh) | 一种服务器集群的管理方法和平台 | |
EP3575975B1 (en) | Method and apparatus for operating smart network interface card | |
US9317268B2 (en) | Recovery automation in heterogeneous environments | |
CN106873970B (zh) | 一种操作***的安装方法和装置 | |
CN111459403B (zh) | 一种存储硬件管理方法及装置 | |
CN106209445B (zh) | 一种通过网络部署的虚拟化数据中心 | |
CN111694604A (zh) | 一种驱动批量安装方法、装置、设备及机器可读存储介质 | |
CN107659621B (zh) | 一种raid控制卡配置方法及装置 | |
CN110688130A (zh) | 物理机部署方法、装置、可读存储介质及电子设备 | |
CN110618884A (zh) | 故障监控方法、虚拟化的网络功能模块管理器和存储介质 | |
CN114443295A (zh) | 一种异构云资源管理调度方法、装置及*** | |
CN103617077A (zh) | 智能型云端化移转的方法与*** | |
TWI554876B (zh) | 節點置換處理方法與使用其之伺服器系統 | |
CN105608034A (zh) | 一种clump自动热插拔的方法 | |
CN111338926A (zh) | 补丁的测试方法、装置及电子设备 | |
CN116820686B (zh) | 物理机的部署方法、虚拟机和容器统一监控的方法及装置 | |
US20220334863A1 (en) | Storage system, installation method, and recording medium | |
CN108319500B (zh) | 一种云计算***的操作方法、装置及电子设备 | |
CN117376341A (zh) | 一种将文件上传至虚拟机的方法、装置、设备及介质 | |
CN111897577A (zh) | 一种cpu的主从辨别方法及其装置、计算机终端设备 |
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: 14858667 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 14858667 Country of ref document: EP Kind code of ref document: A1 |