Peripheral device processing method based on cloud desktop, electronic device and storage medium

Abstract

The present application discloses a peripheral device processing method, electronic device and storage medium based on a cloud desktop, the method comprising: receiving a user account from a cloud terminal; querying peripheral devices that have been registered under the user account, wherein the peripheral devices are connected to a first device; sending the queried peripheral devices to a cloud terminal; receiving a connection request from the cloud desktop, wherein the connection request is used to request a connection to a predetermined peripheral device; sending the connection request to the first device, wherein the first device is used to redirect the predetermined peripheral device to the cloud desktop using a peripheral redirection protocol. The present application solves the problem in the prior art that peripheral devices cannot be used in certain situations due to the binding of cloud desktop peripheral device redirection with the cloud desktop protocol, thereby enabling peripheral devices to be used in various cloud terminals, thereby improving the efficiency of using peripheral devices.

Description

Technical Field

[0001] The present application relates to the field of cloud computing, and more specifically, to a method for processing peripheral devices based on a cloud desktop, an electronic device, and a storage medium. Background Art

[0002] Cloud desktop uses virtual technology to virtualize various physical devices, thereby effectively improving resource utilization, saving costs and improving application quality. With the support of virtualization technology, the connection between network software and hardware devices will be more flexible, and the scalability will be greatly improved, so it is widely used. Cloud desktop uses virtualization technology to essentially store and manage various user information in a unified manner. Through a simple network access device, the user end can access the cloud desktop for centralized management and efficient resource sharing. In addition, users can also personalize the cloud desktop according to their own needs to meet diverse needs.

[0003] Cloud desktop, also known as desktop virtualization or cloud computer, is a new model to replace traditional computers. After adopting cloud desktop, users no longer need to buy computer hosts. The CPU, memory, hard disk and other components contained in the host are all virtualized in the back-end server. A single high-performance server can virtualize multiple virtual hosts of varying sizes. The mainstream front-end device is a thin client (or thin terminal, which is a type of cloud terminal) connected to a monitor and keyboard and mouse. After installing the client, the user accesses the virtual machine host on the back-end server through a unique communication protocol to achieve interactive operations and achieve the same experience as a computer. At the same time, cloud desktop not only supports the replacement of traditional computers, but also supports other smart devices such as mobile phones and tablets to access on the Internet. It is also the latest solution for mobile office.

[0004] When using a cloud desktop, you need to use peripheral devices such as printers, flash memory, mobile hard disks, digital cameras, and handwriting tablets. In the prior art, when a cloud desktop uses peripheral devices, it is generally connected to a thin terminal, and then the thin terminal is used to redirect the USB device. In this case, the cloud desktop peripheral device redirection is coupled with the cloud desktop protocol session, which makes it difficult for these cloud desktops to use computer office peripheral devices on the IOS system, mobile phone side, and web side. Summary of the invention

[0005] The embodiments of the present application provide a cloud desktop-based peripheral device processing method, an electronic device, and a storage medium to at least solve the problem in the prior art that peripheral devices cannot be used in certain situations due to the binding of cloud desktop peripheral device redirection with the cloud desktop protocol.

[0006] According to one aspect of the present application, a method for processing peripheral devices based on a cloud desktop is provided, comprising: receiving a user account from a cloud terminal, wherein the user account is an account used by the cloud terminal when logging into the cloud desktop; querying peripheral devices registered under the user account, wherein the peripheral device is connected to a first device, and the first device is used to register the connected peripheral device to the user account; sending the queried peripheral device to the cloud terminal; receiving a connection request from the cloud desktop, wherein the connection request is used to request connection to a predetermined peripheral device, and the predetermined peripheral device is at least one of the queried peripheral devices; sending the connection request to the first device, wherein the first device is used to redirect the predetermined peripheral device to the cloud desktop using a peripheral redirection protocol.

[0007] According to another aspect of the present application, a method for processing peripheral devices based on a cloud desktop is also provided, including: a first device sends a registration request to a peripheral service, wherein the registration request is used to register the peripheral device connected to the first device, and the peripheral service stores the registered peripheral devices; the first device receives a connection request sent by the peripheral service, wherein the peripheral service is used to provide a cloud terminal with registered peripheral devices that can be used by the cloud terminal, and the connection request is sent by the cloud terminal to the peripheral server, and the connection request is used to connect to a predetermined peripheral device, and the predetermined peripheral device is one of the registered peripheral devices that can be used by the cloud terminal; the first device redirects the predetermined peripheral device to the cloud desktop logged in by the cloud terminal using a peripheral redirection protocol.

[0008] According to another aspect of the present application, a method for processing peripheral devices based on a cloud desktop is also provided, including: a cloud terminal sends a query request to a peripheral service, wherein the query request is used to query the peripheral devices that the cloud terminal can use, and the peripheral service is used to register the peripheral devices connected to the first device; the cloud terminal receives the peripheral devices queried by the peripheral service; the cloud terminal sends a connection request to the peripheral service, wherein the connection request is used to request connection to a predetermined peripheral device, and the predetermined peripheral device is at least one of the queried peripheral devices; the cloud desktop logged in by the cloud terminal receives the predetermined peripheral device redirected to the cloud desktop by the first device through a peripheral redirection protocol.

[0009] According to another aspect of the present application, a cloud desktop-based peripheral device processing system is also provided, including: a peripheral service, a first device and a cloud terminal, wherein the peripheral service, the first device and the cloud terminal are respectively used for the above method.

[0010] According to another aspect of the present application, an electronic device is also provided, comprising a memory and a processor; wherein the memory is used to store one or more computer instructions, wherein the one or more computer instructions are executed by the processor to implement the above-mentioned method steps.

[0011] According to another aspect of the present application, a readable storage medium is provided, on which computer instructions are stored, wherein the computer instructions implement the above method steps when executed by a processor.

[0012] In the embodiment of the present application, a user account is received from a cloud terminal, wherein the user account is the account used by the cloud terminal when logging into the cloud desktop; the peripheral devices registered under the user account are queried, wherein the peripheral devices are connected to a first device, and the first device is used to register the peripheral devices connected to it to the user account; the queried peripheral devices are sent to the cloud terminal; a connection request is received from the cloud desktop, wherein the connection request is used to request a connection to a predetermined peripheral device, and the predetermined peripheral device is at least one of the queried peripheral devices; the connection request is sent to the first device, wherein the first device is used to redirect the predetermined peripheral device to the cloud desktop using a peripheral redirection protocol. This application solves the problem of peripheral devices being unusable in certain cases caused by the binding of cloud desktop peripheral device redirection and cloud desktop protocol in the prior art, thereby enabling peripheral devices to be used in various cloud terminals, thereby improving the efficiency of peripheral device use. BRIEF DESCRIPTION OF THE DRAWINGS

[0013] The drawings constituting a part of the present application are used to provide a further understanding of the present application. The illustrative embodiments and descriptions of the present application are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0014] Figure 1 The process of the peripheral device processing method based on the cloud desktop according to the embodiment of the present application is as follows Figure 1 ;

[0015] Figure 2 The process of the peripheral device processing method based on the cloud desktop according to the embodiment of the present application is as follows Figure 2 ;

[0016] Figure 3 The process of the peripheral device processing method based on the cloud desktop according to the embodiment of the present application is as follows Figure 3 ;as well as,

[0017] Figure 4 It is a flow chart of connecting a cloud desktop to peripheral devices according to an embodiment of the present application. DETAILED DESCRIPTION

[0018] It should be noted that, in the absence of conflict, the embodiments and features in the embodiments of the present application can be combined with each other. The present application will be described in detail below with reference to the accompanying drawings and in combination with the embodiments.

[0019] It should be noted that the steps shown in the flowcharts of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and that, although a logical order is shown in the flowcharts, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0020] In the following embodiments, the redirection of peripheral devices (referred to as peripherals for short) is involved, and the peripherals and redirection are first described below.

[0021] An external device is a device that can be connected to a thin terminal or a personal computer (referred to as PC) (hereinafter referred to as a thin terminal). In terms of interface, an external device can be connected to a thin terminal through a wired interface such as a Universal Serial Bus (USB), serial port, parallel port, or through a wireless interface such as wireless fidelity (WIFI) and Bluetooth (BT). In terms of function type, peripheral devices can include: USB flash drives, mobile hard drives, cameras, smart card readers, printers, scanners, high-definition cameras, input and output devices, etc.

[0022] In the related art, when using a cloud desktop, peripherals are generally connected to a local thin terminal or PC. The cloud desktop communicates with a server for providing a cloud virtual machine through a cloud desktop client installed on the thin terminal, so that the cloud desktop can be used on the thin terminal. In order to use peripheral devices connected to a thin terminal in a cloud desktop, it is necessary to redirect the peripheral devices connected to the thin terminal to the cloud desktop. Thin terminals generally connect peripheral devices through physical interfaces such as USB ports, serial ports, or parallel ports. When redirecting, the peripheral devices on these interfaces need to be redirected to the cloud desktop. The technical principles of redirection used by these interfaces are similar, and the USB interface is used as an example for explanation below.

[0023] In order to solve the compatibility problem of peripherals, the cloud desktop can adopt two working modes. The following first describes these two working modes separately.

[0024] The first working mode

[0025] This working mode is implemented through the USB driver layer. In this method, a low-level virtual driver needs to be implemented on the cloud desktop. The cloud desktop client intercepts the low-level device information on the thin terminal, and then transmits it to the cloud desktop through the cloud desktop protocol. The low-level driver of the cloud desktop then obtains the message for parsing. This method is called USB device redirection.

[0026] USB device redirection is implemented at the application layer. By creating a virtual USB device driver in the cloud desktop (for the operating system, a driver means a device), the application can obtain data. For the entire system, the USB device driver on the thin client is responsible for intercepting device information and then sending the intercepted device information to the virtual USB device driver in the cloud desktop. The USB driver on the thin client can send the intercepted device information to the virtual USB device driver in the cloud desktop through the cloud desktop protocol, and then maintain the data channel for sending device information.

[0027] Device redirection works at the driver layer of peripheral devices. Drivers need to be installed on thin terminals and cloud desktops. Drivers of peripheral devices on thin terminals compress and preprocess data, which is suitable for scenarios that are sensitive to latency or bandwidth, such as high-speed scanners, scanners, and cameras. Since drivers need to be installed on thin terminals, these peripheral devices provide drivers that can run on thin terminal operating systems.

[0028] The second working mode

[0029] This working mode is implemented at the application layer and is called USB port redirection. In USB port redirection, a mapping from a thin terminal to a cloud desktop is provided for peripheral devices, and a dedicated channel for business data transmission is provided for them.

[0030] The data of the USB device plugged into the thin client is submitted to the virtual USB device driver in the cloud desktop through the USB bus of the thin client. The virtual USB device driver is responsible for bidirectional data transmission between the thin client bus and the USB client, and transmits all the details of the USB hardware truthfully. For the virtual machine, it is equivalent to plugging a USB hardware into the virtual USB bus.

[0031] In essence, port mapping is equivalent to lengthening the section between the USB device driver and the USB bus driver in the USB workflow on the PC. By adding several agents in the middle, the details of the USB peripherals on the thin client are finally presented to the USB application on the virtual machine. It just conceals the fact that the device is actually on the remote thin client. In this way, the application cannot perceive the difference from using local peripherals, and it is the same as running on the PC. Therefore, USB port redirection has good device compatibility.

[0032] In port mapping, you can imagine that the USB cable is extended, and the USB device is connected to the cloud desktop from the thin client through the network. Therefore, there is no need to install the driver of the peripheral on the thin terminal, and the corresponding device driver can be installed on the cloud desktop. Since the driver does not need to be installed on the thin terminal, the compatibility is relatively good.

[0033] Port redirection also has certain limitations. Since the data is not compressed and pre-processed at the device driver layer, it may cause problems such as excessive bandwidth and network delay sensitivity for some image applications such as scanners and cameras.

[0034] Whether to use port redirection or device redirection for a specific peripheral depends on the thin terminal type, peripheral category, performance requirements, etc., and can be flexibly selected according to actual conditions.

[0035] Regardless of the above redirection methods, redirection is performed between the thin terminal and the cloud desktop, and the peripheral devices need to be connected to the thin terminal. However, with the development of technology, the types of cloud terminals are not limited to thin clients, but can also be PC soft terminals, Web clients, and zero terminals. The Web client logs in to the cloud desktop through a browser, the soft terminal logs in to the cloud desktop through software, and the zero terminal is a network computer with no CPU, no memory, and no hard disk. These cloud terminals can run in various terminal devices, such as mobile phones, and these terminal devices are of different types. Some terminal devices cannot connect to peripheral devices, and the operating systems on these terminal devices cannot support the redirection of peripheral devices, resulting in the inability to use peripheral devices when using these cloud terminals, which brings inconvenience to users.

[0036] In order to solve this problem, in the following embodiments, another device is introduced to separately connect and maintain peripheral devices. For the convenience of description, the newly introduced device is referred to as an external cloud box in the following embodiments (that is, the first device described below. The newly introduced device can connect to external devices and provide the connected external devices to the cloud terminal, so it is called an external cloud box. All devices with the above functions can be called external cloud boxes).

[0037] In this embodiment, a method for processing peripheral devices based on a cloud desktop is provided. Figure 1 The process of the peripheral device processing method based on the cloud desktop according to the embodiment of the present application is as follows Figure 1 , the following Figure 1 The steps involved in the method are described.

[0038] Step S102: The first device sends a registration request to a peripheral device service, wherein the registration request is used to register a peripheral device connected to the first device, and the peripheral device service stores the registered peripheral devices;

[0039] Step S104, the first device receives a connection request sent by the peripheral service, wherein the peripheral service is used to provide the cloud terminal with a registered peripheral device that can be used by the cloud terminal, the connection request is sent by the cloud terminal to the peripheral server, and the connection request is used to connect to a predetermined peripheral device, and the predetermined peripheral device is one of the registered peripheral devices that can be used by the cloud terminal;

[0040] Step S106: the first device redirects the predetermined peripheral device to the cloud desktop logged in by the cloud terminal using a peripheral redirection protocol.

[0041] In the above steps, cloud terminals, first devices and peripheral services are involved, wherein cloud terminals may include all forms of cloud terminals such as thin terminals, soft terminals, Web clients and zero terminals. In the above steps, a first device is introduced, and the first device has a network module, a processor and an interface connected to a peripheral device. Compared with the prior art in which the peripheral device is directly connected to the cloud terminal, the following embodiment connects the peripheral device to the first device. After the cloud terminal logs in to the cloud desktop, it can access the first device and use the peripheral device through the first device. The first device can connect to the peripheral device through different interfaces (including wired interfaces and wireless interfaces). For example, the peripheral device can be connected through wired interfaces such as USB interfaces, parallel ports, serial ports, etc., or it can be connected through wireless interfaces such as WIFI and Bluetooth.

[0042] Since the first device is connected to multiple peripheral devices, and the first device itself can also be multiple, in order to facilitate management, a service for managing the first device is also introduced in this embodiment. The service is called a peripheral service (the service can also be called a peripheral registration / hosting service). The peripheral service can run on a server and can be connected to a cloud terminal and the first device.

[0043] After the introduction of the peripheral service and the first device, the cloud terminal itself no longer needs to be directly connected to the peripheral device, and thus the driver of the peripheral device does not need to be installed on the cloud terminal. Therefore, the form of the cloud terminal is no longer important. Since the cloud terminal logs in to the cloud desktop through the network, that is, the cloud terminal must support network functions. As long as it supports network functions, the cloud terminal can access the first device and the peripheral service through the network, thereby using the peripheral device connected to the first device. Figure 1The steps shown in the above solve the problem in the prior art that peripheral devices cannot be used in certain situations due to the binding of cloud desktop peripheral device redirection with cloud desktop protocol, thereby enabling peripheral devices to be used in various cloud terminals, thereby improving the efficiency of peripheral device use.

[0044] exist Figure 1 In step S106 shown in the figure, the first device redirects the preset peripheral device to the cloud desktop logged in by the cloud terminal by using the peripheral redirection protocol. The peripheral redirection protocol can be the USB device redirection method introduced above. Unlike USB device redirection, the first device redirects the external device to the cloud desktop logged in by the cloud terminal through the network. There are many ways to implement this redirection. Two optional implementations are described below.

[0045] Optional implementation method 1

[0046] This optional implementation is implemented by connecting the peripheral device driver layer on the first device. In this way, it is necessary to install a virtual peripheral device driver at the bottom layer of the peripheral device on the cloud desktop (the peripheral device driver is installed in the cloud desktop, but the peripheral device is not directly connected in the cloud desktop, so the driver is called a virtual peripheral device driver), and at the same time, the driver of the peripheral device also needs to be installed on the first device. When the peripheral device is needed, the first device intercepts the device data from the driver layer of the peripheral device, and then establishes a network connection between the cloud desktop and the first device through the network, and sends the device data intercepted in the driver layer of the first device to the cloud desktop through the network connection. After receiving the device data, the cloud desktop obtains the device data and parses it by the underlying virtual driver installed by the cloud desktop. Similarly, for the command and / or data sent by the cloud desktop to the peripheral device, the command and / or data is intercepted by the underlying virtual driver of the cloud desktop, and then the command and / or data is sent to the first device through the network connection with the first device, and the first device uses the driver of the peripheral device to receive the command and / or data, and parses the command and / or data. In this way, the interaction of peripheral devices between the cloud terminal and the first device can be completed. For the convenience of description, this method is referred to as peripheral device redirection (or simply device redirection) in the following description. It should be noted that when the cloud desktop and the first device interact with each other through a network connection, the protocol format agreed upon by both parties can be used. The protocol used by both parties is referred to as the peripheral redirection protocol in the following implementation.

[0047] Peripheral device redirection enables cloud applications in the cloud desktop to obtain device data by creating a virtual peripheral device driver in the cloud desktop (for the operating system, a driver means a device). For the workflow, the peripheral device driver on the first device is responsible for intercepting device data and then sending the intercepted device data to the virtual peripheral device driver in the cloud desktop, that is, the peripheral device driver on the first device can send the intercepted device data to the virtual peripheral device driver in the cloud desktop through the cloud desktop, and then maintain the data channel for sending device data.

[0048] Device redirection works at the driver layer of peripheral devices. Drivers need to be installed on both the first device and the cloud desktop. The driver of the peripheral device on the first device compresses and pre-processes the device data, which is suitable for scenarios that are sensitive to latency or bandwidth, such as high-definition cameras, scanners, and cameras.

[0049] Optional implementation method 2

[0050] In this optional implementation, it is not necessary to install a driver on the first device. Instead, the first device directly obtains device data from the port connected to the peripheral device and the first device. The device data is not processed by the driver. Instead, the obtained device data is directly sent to the cloud application in the cloud desktop through the network connection with the cloud desktop. The driver of the virtual peripheral device installed in the cloud desktop processes the received device data.

[0051] For example, assuming that the peripheral device is connected to the first device via a USB interface, the first device directly obtains the device data through its USB bus, that is, the USB device data plugged into the first device is submitted to the virtual USB device driver in the cloud desktop through the USB bus on the first device. The virtual USB device driver is responsible for bidirectional data transmission between the first device and the cloud desktop. The data transmits all the details of the USB hardware truthfully. For the cloud desktop, it is equivalent to plugging a USB hardware into the virtual USB bus.

[0052] For another example, assuming that the peripheral device is connected to the first device via a Bluetooth interface, the first device obtains the device data of the peripheral device through the Bluetooth channel, and then the first device sends the device data of the Bluetooth peripheral device to the virtual Bluetooth device driver of the cloud desktop through the network connection. The virtual Bluetooth device driver is responsible for two-way data transmission between the first device and the cloud desktop. For the cloud desktop, it is equivalent to connecting the Bluetooth device directly to the cloud desktop.

[0053] For the convenience of description, the mapping in this implementation may be referred to as port mapping. In port redirection, the first device provides a mapping from the first device to the cloud desktop for the peripheral device, and provides a dedicated channel for business data transmission. Port mapping is equivalent to presenting the details of the peripheral device on the first device to the cloud application in the cloud desktop, but concealing the fact that the peripheral device is actually on the first device, so that the cloud application cannot perceive the difference from using the local peripheral device at all. Therefore, port redirection has good device compatibility.

[0054] For port redirection, there is no need to install the driver of the peripheral device on the thin terminal. You only need to install the corresponding peripheral device driver on the cloud desktop. Since the driver does not need to be installed on the thin terminal, the compatibility is relatively good. Port redirection also has certain limitations. Since the data is not compressed and preprocessed at the device driver layer, it may cause network delays and other problems for some image applications such as scanners and cameras.

[0055] In the above two optional implementations, considering that the driver needs to be installed on the cloud desktop, the driver programs of the peripheral devices applicable to various operating systems can also be saved in advance in the first device or the peripheral service. After the peripheral service provides the cloud desktop with a list of peripheral devices that it can use, and the cloud desktop selects the predetermined peripheral device to be used from the peripheral device list, if the driver program of the peripheral device is not installed in the cloud desktop, the cloud desktop can send a driver acquisition request to the first device or the peripheral service, and the request carries the model of the operating system of the cloud desktop and the identification information of the predetermined peripheral device; after the first device or the peripheral service receives the driver acquisition request, it sends the driver program corresponding to the model of the operating system of the predetermined peripheral device to the cloud desktop, or sends the download address of the driver program corresponding to the model of the operating system of the predetermined peripheral device to the cloud desktop, so that the cloud desktop can obtain the driver program. After the cloud desktop installs the driver program, the peripheral device on the first device can be used.

[0056] In the above two methods, device redirection requires the installation of a driver on the first device, while port redirection does not require the installation of a driver on the first device. In another optional implementation, when a new peripheral device is connected to the first device, the first device can obtain the device information of the new peripheral device, and search for the driver of the new peripheral device in the peripheral service or network public channel according to the device information. If the corresponding driver is found and the driver of the new peripheral device is successfully installed on the first device, device redirection is used when interacting with the cloud desktop; if the driver is not found or the driver installation fails, port redirection is used when interacting with the cloud desktop.

[0057] In the above implementation, in order to facilitate the management of the first device and the peripheral devices connected to the first device, a peripheral service is introduced. As an optional implementation, the peripheral service can associate the user account used by the cloud terminal to log in to the cloud desktop with the first device, that is, the first device can be registered under the user account, so that the cloud desktop can obtain the peripheral devices under the first device and use them when needed. There are two ways to register the first device to the user account, one is to register the first device itself, and the other is to register the peripheral device connected to the first device. In order to distinguish these two registrations, the registration request is divided into a first registration request and a second registration request in the following, that is, the step of the first device sending a registration request to the peripheral service can include: the first device sends a first registration request to the peripheral service, wherein the first registration request is used to request that the first registered device be registered under a user account, and the user account is the user account used by the cloud terminal to log in to the cloud desktop; and / or, when the first device determines that the peripheral device is connected to the first device, it sends a second registration request, wherein the second registration request carries the device information of the peripheral device connected to the first device, and the second registration request is used to register the peripheral device connected to the first device under the user account.

[0058] It should be noted that the first device and the user account can be matched one-to-one, that is, one first device can only be registered under one user account; or one first device can also be registered under multiple user accounts, and the multiple user accounts can all use the peripheral devices in the first device. When the peripheral device is being used by one of the user accounts, if another user account also wants to use the device, the other user account is prompted that the peripheral device is busy, or the use request of the other user account is queued for processing; of course, multiple first devices can be registered under one user account, so that the number of peripheral devices that can be used by the user account is relatively large.

[0059] As another optional implementation, the first device or peripheral device that has been registered to the user account can also be changed, deleted or deregistered. That is, in an optional implementation, when the first device determines that the peripheral device is disconnected from the first device, it sends a deregistration request, wherein the deregistration request carries the device information of the peripheral device that is disconnected from the first device; the deregistration request is used to delete the disconnected peripheral device from the user account; and / or, the first device sends a change request, wherein the change request is used to deregister the first device from the user account or transfer the first device from the user account to another user account. This change, deletion or deregistration can better manage peripheral devices.

[0060] The above is described from the perspective of the first device. Figure 2 The process of the peripheral device processing method based on the cloud desktop according to the embodiment of the present application is as follows Figure 2 , the following combination Figure 2 Describes the steps performed by the peripheral service.

[0061] Step S202, receiving a user account from a cloud terminal, wherein the user account is an account used by the cloud terminal to log in to a cloud desktop;

[0062] Step S204, querying the peripheral device that has been registered under the user account, wherein the peripheral device is connected to a first device, and the first device is used to register the connected peripheral device to the user account;

[0063] Step S206, sending the queried peripheral devices to the cloud terminal;

[0064] Step S208, receiving a connection request from the cloud desktop, wherein the connection request is used to request connection to a predetermined peripheral device, and the predetermined peripheral device is at least one of the queried peripheral devices;

[0065] Step S210: sending the connection request to the first device, wherein the first device is used to redirect the predetermined peripheral device to the cloud desktop using a peripheral redirection protocol.

[0066] Through the above steps, after the peripheral service and the first device are introduced, the cloud terminal itself no longer needs to be directly connected to the peripheral device, so there is no need to install the driver of the peripheral device on the cloud terminal. Therefore, the form of the cloud terminal is no longer important. Since the cloud terminal logs in to the cloud desktop through the network, that is, the cloud terminal must support network functions. As long as it supports network functions, the cloud terminal can access the first device and the peripheral service through the network, thereby using the peripheral device connected to the first device. Figure 2 The steps shown in the above solve the problem in the prior art that peripheral devices cannot be used in certain situations due to the binding of cloud desktop peripheral device redirection with cloud desktop protocol, thereby enabling peripheral devices to be used in various cloud terminals, thereby improving the use efficiency of peripheral devices.

[0067] Similar to the registration request described above, as an optional implementation, the registration request may be a first registration request and a second registration request (the first and second are only used to distinguish the two registration requests and have no other practical meaning), that is, before receiving the user account from the cloud terminal, the method further includes: receiving a first registration request from the first device, wherein the first registration request is used to request that the first device be registered under the user account; registering the first device under the user account according to the first registration request, wherein one or more first devices are registered under the user account. After registering the first device under the user account, the method may further include: receiving a second registration request from the first device, wherein the second registration request carries device information of a peripheral device connected to the first device; and registering the peripheral device connected to the first device under the user account according to the device information of the peripheral device.

[0068] As another optional implementation, the first device or peripheral device that has been registered under the user account can also be changed, deleted or deregistered. That is, in an optional implementation, the peripheral service can receive a change request, wherein the change request is used to deregister the first device from the user account or transfer the first device from the user account to another user account; deregister the first device from the user account or transfer the first device from the user account to another user account according to the change request. Alternatively, the peripheral service can also receive a deregistration request from the first user device, wherein the deregistration request carries device information of a peripheral device that is to be removed from the first device; and delete the removed peripheral device from the user account according to the device information of the removed peripheral device.

[0069] After the first device and the peripheral service are introduced, the cloud terminal can interact with the first device and the peripheral service. Figure 3 The process of the peripheral device processing method based on the cloud desktop according to the embodiment of the present application is as follows Figure 3 , the following Figure 3 The method steps involved are described in detail.

[0070] Step S302, the cloud terminal sends a query request to the peripheral service, wherein the query request is used to query the peripheral devices that the cloud terminal can use, and the peripheral service is used to register the peripheral device connected to the first device;

[0071] In this step, the user account used by the cloud terminal to log in to the cloud desktop can be associated with the first device and the peripheral device connected to the first device, that is, the query request can carry the user account used by the cloud terminal to log in to the cloud desktop, and the peripheral service saves the first device registered under the user account and the peripheral device connected to the first device.

[0072] Step S304, the cloud terminal receives the peripheral device queried by the peripheral service;

[0073] Step S306, the cloud terminal sends a connection request to the peripheral service, wherein the connection request is used to request connection to a predetermined peripheral device, and the predetermined peripheral device is at least one of the queried peripheral devices;

[0074] Step S308: The cloud desktop logged in by the cloud terminal receives the predetermined peripheral device redirected to the cloud desktop by the first device through a peripheral redirection protocol.

[0075] Through the above steps, the cloud terminal no longer needs to connect the peripheral device to the cloud terminal, but uses the peripheral device provided by the first device, so that the cloud terminal does not need to install the driver of the peripheral device, so the form of the cloud terminal is no longer important, as long as it supports the network function, the cloud terminal can access the first device and the peripheral service through the network, so as to use the peripheral device connected to the first device. Therefore, the problem of the peripheral device being unable to be used in some cases caused by the cloud desktop peripheral device redirection and the cloud desktop protocol binding in the prior art is solved, so that the peripheral device can be used in various cloud terminals, and the use efficiency of the peripheral device is improved.

[0076] Above Figure 1 , Figure 2 and Figure 3 The first device, peripheral service and cloud terminal are described respectively. In one embodiment, a peripheral device processing system based on a cloud desktop can also be provided, which includes the first device, peripheral service and cloud terminal described in the above embodiment. The overall process of connecting a cloud desktop to a peripheral device is described below in conjunction with an optional embodiment. Figure 4 is a schematic diagram of a process of connecting a cloud desktop to a peripheral device according to an embodiment of the present application. Figure 4In the process, the peripheral cloud box (i.e., the first device) will be registered under a certain account of the cloud user after it is started. When a peripheral device is linked to the peripheral cloud box, the peripheral cloud box registers the device with the peripheral hosting service (i.e., the peripheral service). After receiving the registration information, the peripheral hosting service writes the device information of the peripheral device into the device list corresponding to the user account. When the cloud terminal needs to use the cloud desktop, it queries the device list under the account through the peripheral hosting service. After the cloud terminal is connected to the cloud desktop, when it needs to connect to the device, it sends a device connection command to the peripheral cloud box through the peripheral hosting service. After receiving the connection command, the peripheral cloud box links to the corresponding cloud application through the peripheral redirection protocol. Through Figure 4 The cloud-based peripheral hosting service decouples cloud desktops from peripheral devices, thereby supporting various types of cloud terminals and achieving full-end system support.

[0077] In this embodiment, an electronic device is provided, including a memory and a processor. The memory stores a computer program, and the processor is configured to run the computer program to execute the method in the above embodiment.

[0078] The above program can be run in the processor, or it can be stored in the memory (or computer-readable medium), which includes permanent and non-permanent, removable and non-removable media. Information storage can be achieved by any method or technology. Information can be computer-readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, read-only compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, tape disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined in this article, computer-readable media does not include temporary computer-readable media (transitory media), such as modulated data signals and carrier waves.

[0079] These computer programs can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, so that the instructions executed on the computer or other programmable device provide instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps of the functions specified in one or more blocks can be implemented by different modules corresponding to different steps.

[0080] This embodiment provides such a device. The device is used to implement the functions of the method in the above embodiment. Each module in the system or device corresponds to each step in the method, which has been explained in the method and will not be repeated here.

[0081] Corresponds to Figure 2 In this embodiment, a peripheral device processing device based on a cloud desktop is provided, and the device includes: a first receiving module, used to receive a user account from a cloud terminal, wherein the user account is an account used by the cloud terminal when logging into the cloud desktop; a query module, used to query the peripheral devices registered under the user account, wherein the peripheral device is connected to a first device, and the first device is used to register the connected peripheral device to the user account; a first sending module, used to send the queried peripheral device to the cloud terminal; a second receiving module, used to receive a connection request from the cloud desktop, wherein the connection request is used to request connection to a predetermined peripheral device, and the predetermined peripheral device is at least one of the queried peripheral devices; a second sending module, used to send the connection request to the first device, wherein the first device is used to redirect the predetermined peripheral device to the cloud desktop using a peripheral redirection protocol.

[0082] Optionally, before receiving the user account from the cloud terminal, the device also includes: a registration module, used to receive a first registration request from the first device, wherein the first registration request is used to request that the first device be registered under the user account; register the first device under the user account according to the first registration request, wherein one or more first devices are registered under the user account.

[0083] Optionally, after registering the first device to the user account, the above-mentioned registration module is also used to: receive a change request, wherein the change request is used to deregister the first device from the user account or transfer the first device from the user account to another user account; deregister the first device from the user account or transfer the first device from the user account to another user account according to the change request.

[0084] Optionally, after registering the first device under the user account, the above-mentioned registration module is also used to: receive a second registration request from the first device, wherein the second registration request carries device information of a peripheral device connected to the first device; and register the peripheral device connected to the first device under the user account according to the device information of the peripheral device.

[0085] Optionally, the registration module is also used to: receive a logout request from the first user device, wherein the logout request carries device information of a peripheral device removed from the first device; and delete the removed peripheral device from the user account according to the device information of the removed peripheral device.

[0086] Corresponds to Figure 1 In this embodiment, a peripheral device processing device based on a cloud desktop is also provided, which is located in the first device and includes: a third sending module, used to send a registration request to a peripheral service, wherein the registration request is used to register the peripheral device connected to the first device, and the peripheral service stores the registered peripheral devices; a third receiving module, used to receive a connection request sent by the peripheral service, wherein the peripheral service is used to provide the cloud terminal with the registered peripheral devices that can be used by the cloud terminal, and the connection request is sent by the cloud terminal to the peripheral server, and the connection request is used to connect to a predetermined peripheral device, and the predetermined peripheral device is one of the registered peripheral devices that can be used by the cloud terminal; a redirection module, used to redirect the predetermined peripheral device to the cloud desktop logged in by the cloud terminal using a peripheral redirection protocol.

[0087] Optionally, the third sending module is used to send a first registration request to the peripheral service, wherein the first registration request is used to request that the first registered device be registered under a user account, and the user account is a user account used by the cloud terminal to log in to the cloud desktop; and / or, when it is determined that a peripheral device is connected to the first device, a second registration request is sent, wherein the second registration request carries device information of the peripheral device connected to the first device, and the second registration request is used to register the peripheral device connected to the first device under the user account.

[0088] Optionally, the third sending module is also used to: send a logout request when it is determined that the peripheral device is disconnected from the first device, wherein the logout request carries device information of the peripheral device disconnected from the first device; the logout request is used to delete the disconnected peripheral device from the user account; and / or send a change request, wherein the change request is used to log out the first device from the user account or transfer the first device from the user account to another user account.

[0089] Corresponds to Figure 3In this embodiment, a peripheral device processing device based on a cloud desktop is also provided, which is located in a cloud terminal and includes: a fourth sending module, used to send a query request to a peripheral service, wherein the query request is used to query the peripheral devices that can be used by the cloud terminal, and the peripheral service is used to register the peripheral devices connected to the first device; a fourth receiving module, used to receive the peripheral devices queried by the peripheral service; a fifth sending module, used to send a connection request to the peripheral service, wherein the connection request is used to request a connection to a predetermined peripheral device, and the predetermined peripheral device is at least one of the queried peripheral devices; a fifth receiving module, used to receive the predetermined peripheral device redirected by the first device to the cloud desktop through a peripheral redirection protocol.

[0090] Optionally, the query request carries a user account used by the cloud terminal to log in to the cloud desktop, and the peripheral service stores the first device registered under the user account and the peripheral devices connected to the first device.

[0091] The above implementation solves the problem in the prior art that peripheral devices cannot be used in certain situations due to the binding of cloud desktop peripheral device redirection and cloud desktop protocol, thereby enabling peripheral devices to be used in various cloud terminals, thereby improving the use efficiency of peripheral devices.

[0092] The above are only embodiments of the present application and are not intended to limit the present application. For those skilled in the art, the present application may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included within the scope of the claims of the present application.

Claims

1. A method for processing peripheral devices based on a cloud desktop, comprising: Receiving a user account from a cloud terminal, wherein the user account is an account used by the cloud terminal to log in to a cloud desktop; Querying the peripheral devices registered under the user account, wherein the peripheral device is connected to a first device, and the first device is used to register the connected peripheral device to the user account; Send the queried peripheral devices to the cloud terminal; Receiving a connection request from the cloud terminal, wherein the connection request is used to request connection to a predetermined peripheral device, and the predetermined peripheral device is at least one of the queried peripheral devices; The connection request is sent to the first device, wherein the first device is used to redirect the predetermined peripheral device to the cloud desktop using a peripheral redirection protocol.

2. The method according to claim 1, wherein: Before receiving the user account from the cloud terminal, the method further includes: receiving a first registration request from the first device, wherein the first registration request is used to request to register the first device under the user account; The first device is registered under the user account according to the first registration request, wherein one or more first devices are registered under the user account.

3. The method according to claim 2, after registering the first device to the user account, the method further comprises: receiving a change request, wherein the change request is used to deregister the first device from the user account or transfer the first device from the user account to another user account; The first device is deregistered from the user account or the first device is transferred from the user account to another user account according to the change request.

4. The method according to claim 2, wherein: After registering the first device under the user account, the method further includes: receiving a second registration request from the first device, wherein the second registration request carries device information of a peripheral device connected to the first device; The peripheral device connected to the first device is registered under the user account according to the device information of the peripheral device.

5. The method according to claim 3, wherein: Also includes: receiving a deregistration request from the first device, wherein the deregistration request carries device information of a peripheral device to be removed from the first device; The disconnected peripheral device is deleted from the user account according to the device information of the disconnected peripheral device.

6. A method for processing peripheral devices based on a cloud desktop, comprising: The first device sends a registration request to the peripheral device service, wherein the registration request is used to register the peripheral device connected to the first device, and the peripheral device service stores device information of the registered peripheral device; The first device receives a connection request sent by the peripheral service, wherein the peripheral service is used to provide the cloud terminal with a registered peripheral device that can be used by the cloud terminal, the connection request is sent by the cloud terminal to the peripheral service, and the connection request is used to connect to a predetermined peripheral device, and the predetermined peripheral device is one of the registered peripheral devices that can be used by the cloud terminal; The first device redirects the predetermined peripheral device to the cloud desktop logged in by the cloud terminal using a peripheral redirection protocol.

7. The method according to claim 6, wherein: The first device sending a registration request to the peripheral service includes: The first device sends a first registration request to the peripheral service, wherein the first registration request is used to request that the first device be registered under a user account, and the user account is a user account used by the cloud terminal to log in to the cloud desktop.

8. The method according to claim 7, wherein: The first device sending a registration request to the peripheral service includes: When the first device determines that a peripheral device is connected to the first device, it sends a second registration request, wherein the second registration request carries device information of the peripheral device connected to the first device, and the second registration request is used to register the peripheral device connected to the first device under the user account.

9. The method according to claim 8, wherein: Also includes: When the first device determines that the peripheral device is disconnected from the first device, the first device sends a logout request, wherein the logout request carries device information of the peripheral device disconnected from the first device; the logout request is used to delete the disconnected peripheral device from the user account; and / or, The first device sends a change request, where the change request is used to deregister the first device from the user account or transfer the first device from the user account to another user account.

10. A method for processing peripheral devices based on a cloud desktop, comprising: The cloud terminal sends a query request to the peripheral service, wherein the query request is used to query the peripheral devices that can be used by the cloud terminal, and the peripheral service is used to register the peripheral device connected to the first device; The cloud terminal receives the peripheral device queried by the peripheral service; The cloud terminal sends a connection request to the peripheral service, wherein the connection request is used to request connection to a predetermined peripheral device, and the predetermined peripheral device is at least one of the queried peripheral devices; The cloud desktop logged in by the cloud terminal receives the predetermined peripheral device redirected to the cloud desktop by the first device through the peripheral redirection protocol.

11. The method according to claim 10, wherein: The query request carries a user account used by the cloud terminal to log in to the cloud desktop, and the peripheral service stores the first device registered under the user account and the peripheral devices connected to the first device.

12. A peripheral device processing system based on a cloud desktop, comprising: A peripheral service, a first device and a cloud terminal, wherein the peripheral service is used to execute the method described in any one of claims 1 to 5, the first device is used to execute the method described in any one of claims 6 to 9, and the cloud terminal is used to execute the method described in claim 10 or 11.

13. An electronic device comprising a memory and a processor; wherein: The memory is used to store one or more computer instructions, wherein the one or more computer instructions are executed by the processor to implement the method steps described in any one of claims 6 to 9.

14. A readable storage medium having computer instructions stored thereon, wherein: When the computer instruction is executed by a processor, the method steps described in any one of claims 1 to 5 are implemented; or, when the computer instruction is executed by a processor, the method steps described in any one of claims 10 to 11 are implemented.

Images