A scanner mapping method on a cloud desktop and its terminal

Abstract

The present invention discloses a method for mapping a scanner on a cloud desktop, which includes the following steps: S1. Construct a data source file that can be recognized by the TWAIN framework on the Windows system cloud desktop, and wake up the scanner through scanning software based on the TWAIN framework; S2. According to the workflow of the TWAIN framework, the TWAIN process component constructs a corresponding TWAIN request, converts the TWAIN request into a corresponding SANE request, and then sends the converted SANE request to the SANE framework on the local client to execute the corresponding scanning job; S3. After completing the scanning job, the SANE component on the local client receives the SANE request for completing the scanning job, and converts the SANE request into a corresponding TWAIN message again to notify the cloud desktop that the scanning job has been completed, and obtain the image through the TWAIN framework. Thus, users can use the physical scanner device on the local terminal on the cross-platform cloud desktop.

Description

Technical Field

[0001] The present invention relates to the technical field of cloud desktops, and particularly to a method for mapping a scanner on a cloud desktop and a terminal thereof. Background Art

[0002] A cloud desktop is an application of cloud computing technology in an operating system. That is, through virtualization technology, a virtualization software is installed in a server in a data center computer room, and then multiple desktop virtual machines are created by configuring the software. These virtual machines have relatively independent CPU and memory resources. By dividing an actual server into multiple virtual machines, it can be provided for multiple users to use independently. Different users use different virtual machines, which will neither preempt CPU and memory resources from each other nor conflict with each other due to operations on the same machine. This enables users to operate and work on the operating system on the desktop in various scenarios.

[0003] TWAIN (full name Technology without An Interesting Name) is a communication standard between software and image input devices such as digital cameras and scanners, and is also the most widely used printer communication standard on the Windows platform and the standard used on cloud desktops running the Windows system.

[0004] SANE (full name Scanner Access Now Easy) is an application programming interface (API) that provides standardized access to any raster image scanner hardware (including scanners and digital cameras). It is a general scanner protocol widely used on the Linux platform.

[0005] On domestic terminals running a domestic operating system based on the Linux system, when connected to a cloud desktop running the Windows system, users need a method to call the scanner on the local Linux system terminal to perform scanning tasks. On the Windows cloud desktop, TWAIN with mature applications is undoubtedly the best choice, but on the Linux local terminal, this is not the case. TWAIN cannot separate the user interface and the device driver, which means that most specific TWAIN programs adopt a specific GUI API, while SANE can separate the interface from the operation interface, enabling SANE to support the command-line driver interface on the Linux system. Summary of the Invention

[0006] The technical problem to be solved by the present invention is: to provide a scanner mapping method and its terminal on a cloud desktop. Based on the TWAIN protocol and the SANE protocol, on a cloud desktop running the Windows system, convert the TWAIN scan operation instructions made by the user into SANE instructions on the Linux system, so that the user can operate the scanner device connected to the local Linux system terminal on the cloud desktop of the Windows system.

[0007] To solve the above technical problem, a technical solution adopted by the present invention is:

[0008] A scanner mapping method on a cloud desktop, comprising the following steps:

[0009] S1. Construct a data source file for being recognized by the TWAIN framework on the cloud desktop of the Windows system, and wake up the scanner through a scanning software based on the TWAIN framework;

[0010] S2. According to the working process of the TWAIN framework, the TWAIN process component constructs a corresponding TWAIN request, converts the TWAIN request into a corresponding SANE request, and then sends the converted SANE request to the SANE framework on the local client to execute the corresponding scanning job;

[0011] S3. After completing the scanning job, the SANE component on the local client receives the SANE request for completing the scanning job, and converts the SANE request into a corresponding TWAIN message, notifies the cloud desktop that the scanning job has been completed, and performs image acquisition through the TWAIN framework.

[0012] To solve the above technical problem, another technical solution adopted by the present invention is:

[0013] A scanner mapping terminal on a cloud desktop, comprising a memory, a processor, and a computer program stored on the memory and executable on the processor. When the processor executes the computer program, it implements each step in the above-mentioned scanner mapping method on a cloud desktop.

[0014] The beneficial effects of the present invention are as follows: A scanner mapping method and its terminal on a cloud desktop are provided. By creating a virtual SANE protocol scanner device in the virtual machine of the cloud desktop, users can call the scanner device under the local SANE protocol through the scanning software based on the TWAIN protocol on the cloud desktop. When the user scans a file on the created virtual scanner device, the scanning task will be packaged and sent to the physical scanner driver of the local terminal, and the physical scanner on the local terminal can scan the file that the user wants to scan and send it to the cloud desktop for the user to use. That is, users can use the physical scanner device on the local terminal on the cross-platform cloud desktop. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] Figure 1 It is a flowchart of a scanner mapping method on a cloud desktop according to an embodiment of the present invention;

[0016] Figure 2 It is a TWAIN status flowchart of a scanner mapping method on a cloud desktop according to an embodiment of the present invention;

[0017] Figure 3 It is a SANE management program interface diagram of a scanner mapping method on a cloud desktop according to an embodiment of the present invention;

[0018] Figure 4 It is a selection device operation diagram of a scanner mapping method on a cloud desktop according to an embodiment of the present invention;

[0019] Figure 5 It is a target source schematic diagram of a scanner mapping method on a cloud desktop according to an embodiment of the present invention;

[0020] Figure 6 It is an operation diagram for obtaining a scanning device of a scanner mapping method on a cloud desktop according to an embodiment of the present invention;

[0021] Figure 7 It is an architecture diagram of a scanner mapping terminal on a cloud desktop according to an embodiment of the present invention. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0022] To describe in detail the technical content, the achieved objectives and the effects of the present invention, the following is described in conjunction with the embodiments and with reference to the accompanying drawings.

[0023] A scanner mapping method on a cloud desktop includes the following steps:

[0024] S1. Construct a data source file that can be recognized by the TWAIN framework on the Windows system cloud desktop, and wake up the scanner through the scanning software based on the TWAIN framework;

[0025] S2. According to the working process of the TWAIN framework, the TWAIN process component constructs a corresponding TWAIN request, converts the TWAIN request into a corresponding SANE request, and then sends the converted SANE request to the SANE framework on the local client to execute the corresponding scanning job;

[0026] S3. After completing the scanning job, the SANE component on the local client receives the SANE request for completing the scanning job, converts the SANE request into a corresponding TWAIN message, notifies the cloud desktop that the scanning job has been completed, and retrieves the image through the TWAIN framework.

[0027] As can be seen from the above description, the beneficial effect of the present invention is to provide a method for mapping a scanner on a cloud desktop. By creating a virtual SANE protocol scanner device in the virtual machine of the cloud desktop, users can call the scanner device under the local SANE protocol based on the scanning software of the TWAIN protocol on the cloud desktop. When the user scans a file on the created virtual scanner device, the scanning task will be packaged and sent to the physical scanner driver on the local terminal. The physical scanner on the local terminal can then scan the file that the user wants to scan and send it to the cloud desktop for the user to use. That is, users can use the physical scanner device on the local terminal on the cross-platform cloud desktop.

[0028] Further, the TWAIN framework in step S1 consists of three parts: application software, device resource manager, and device driver resource; communication between the three parts is achieved through an entry function;

[0029] The application software includes a device selection entry and a scanning entry;

[0030] The device resource manager is used to select the device type;

[0031] The device driver resource is used to control the underlying driver of the image device according to the TWAIN specification.

[0032] As can be seen from the above description, TWAIN defines a software protocol standard and application programming interface for information exchange between application software and image device resources.

[0033] Further, the specific method of waking up the scanner through the scanning software based on the TWAIN framework in step S1 is as follows: the program of the application software sends an open device message to the TWAIN protocol; the program of the application software selects the virtual device source to wake up the mapped local SANE scanner; the virtual device source is mapped from the SANE protocol scanner on the local Linux operating system to the cloud desktop of the Windows system.

[0034] From the above description, it can be seen that the application software program is a window management software developed based on Qt, which is used to call the SANE scanner interface.

[0035] Furthermore, step S2 specifically includes: after the TWAIN process component obtains the device opening message, calling out a local management interface for managing the SANE scanner.

[0036] It can be seen from the above description that the SANE management program interface is used to interact with the user, and the SANE protocol interface is used to implement the operation of the local physical scanner.

[0037] Furthermore, the management interface is printer management software running locally, and the management interface is created through a sub-window of the cloud desktop window.

[0038] From the above description, it can be seen that the program runs on the local client. By establishing a parent-child relationship between the program window and the cloud desktop window and tightly coupling them, the sense of disconnection when switching back and forth between the user's desktop and the local client can be reduced.

[0039] Furthermore, when the management interface appears, a callback message is generated to notify the TWAIN protocol device on the cloud desktop that it is ready, and TWAIN receives the ready message and waits for the transmission of image data.

[0040] From the above description, it can be seen that when the SANE management program is called up, the local SANE protocol scanner is turned on. For the TWAIN protocol on the cloud desktop, it also enters the "Source Open" state. TWAIN will receive a MSG_ENABLEDS message and start waiting for the transmission of image data.

[0041] Furthermore, the request for obtaining the image in step S3 is completed locally in a SANE manner, and then the result of the scanning operation is submitted from the local SANE framework to the TWAIN framework on the cloud desktop.

[0042] From the above description, it can be seen that the user can operate the scanning software based on the TWAIN framework on the desktop, call and complete the scanning job of the local SANE framework, that is, the function of calling the local Linux domestic system on the Windows cloud desktop can be realized.

[0043] Furthermore, if the user chooses continuous scanning, after the data of the current page is scanned, the TWAIN on the cloud desktop is in a transmission state. When the data of the next page is scanned, a transmission preparation message is sent to notify TWAIN that a new image can be obtained, and then the acquisition information is continued to be sent to obtain image data.

[0044] As can be seen from the above description, the present invention can achieve single-page scanning or continuous scanning.

[0045] A scanner mapping terminal on a cloud desktop includes a memory, a processor, and a computer program stored on the memory and executable on the processor. When the processor executes the computer program, each step in the above-mentioned scanner mapping method on a cloud desktop is implemented.

[0046] As can be seen from the above description, the beneficial effect of the present invention is to provide a scanner mapping terminal on a cloud desktop. By creating a virtual SANE protocol scanner device in the virtual machine of the cloud desktop, users can call the scanner device under the local SANE protocol through the scanning software based on the TWAIN protocol on the cloud desktop. When the user scans a file on the created virtual scanner device, the scanning task will be packaged and sent to the physical scanner driver on the local terminal, and the physical scanner on the local terminal can scan out the file that the user wants to scan and send it to the cloud desktop for the user to use. That is, users can use the physical scanner device on the local terminal on the cross-platform cloud desktop.

[0047] For the above-mentioned scanner mapping method and terminal on a cloud desktop of the present invention, users can call the scanner device under the local SANE protocol through the scanning software based on the TWAIN protocol on the cloud desktop, which will be described in detail through the following specific embodiments:

[0048] Embodiment 1

[0049] An embodiment of the present invention provides a scanner mapping method on a cloud desktop. First, a DataSource file for being recognized by the TWAIN framework on the Windows system cloud desktop needs to be constructed, and this TWAIN to SANE framework is disguised as a data source that can be recognized by TWAIN. When the user opens the data source on the Windows cloud desktop, the TwainProcess component on the desktop constructs a corresponding request according to the working process of the TWAIN framework and sends it to the local client. And it is converted into a corresponding SANE request, and then the converted SANE request is sent to the SANE framework on the local client to perform the corresponding scanning work. After the corresponding scanning work is completed, a completed SANE request is notified to the SANE component on the local client, and it is converted into a corresponding TWAIN message again to notify that the scanning job on the desktop has been completed, and let the TWAIN framework on the desktop fetch the image. Of course, the request for fetching the image will also be completed locally in the SANE manner, and then the result of the scanning job is submitted from the local SANE framework to the TWAIN framework on the desktop. In this way, the user can operate the scanning software based on the TWAIN framework on the desktop, call and complete the scanning job of the local SANE framework. In this way, the function of calling the local Linux domestic system on the Windows cloud desktop is realized.

[0050] On the cloud desktop, the user can use this virtual scanning device for any scanning. When the scanner is awakened, the window that pops up is the printer management software running locally. This makes the scanner configuration information it obtains come from the physical scanner on the local terminal. Therefore, the user's experience when operating the virtual scanner is the same as that of operating a physical scanner locally. This management window will be created as a child window of the cloud desktop window. Therefore, when the user operates the software on this local terminal on the cloud desktop, there will be no sense of fragmentation, just like operating a software running on the cloud desktop. Therefore, the part of the scanning job process completed on the local terminal will not be perceived by the user, and the user can obtain a scanning experience as if the entire process is completed on the cloud desktop, thus realizing the function of operating the scanner on the local Linux domestic system when using the Windows cloud desktop.

[0051] Specifically, it includes the following steps:

[0052] S1. Construct a data source file for being recognized by the TWAIN framework on the Windows system cloud desktop, and wake up the scanner through the scanning software based on the TWAIN framework;

[0053] Among them, TWAIN consists of three parts: application software, device resource manager, and device driver resource:

[0054] The application software includes a device selection menu item and a scan acquisition menu item. Software developers must modify the application according to the TWAIN specification.

[0055] The device resource manager is used to select the device type and coordinate the information exchange and communication management between the application software and the underlying driver of the device resources, named TWAIN.DLL.

[0056] The device driver resource is used to control the underlying driver of the image device according to the TWAIN specification. It is named *.DS.

[0057] In addition, the source management software provides the "Select Source" dialog box that appears when the user selects the "Select Device" menu; the source software provides the scanner user interface that the user sees when using the scanner.

[0058] Then, the communication between the three parts is achieved through the entry functions DSM_Entry() and DS_Entry(). The ultimate goal of the Application is to obtain data from the Source, but the Application cannot directly contact the Source. All data acquisition, attribute information, error information, etc. must be passed through the Source Manager. TWAIN defines approximately 140 operations. The application program must pass these operation requests to the Source Manager through the DSM_Entry() function. After receiving these requests, if the Source Manager finds that the target of these operations is the Source, it calls the DS_Entry() function to send the requests to the Source.

[0059] Specifically, in the TWAIN structure, local scanners are managed in the form of DataSource (hereinafter referred to as DS). Each connected scanner will have a corresponding DataSource, and the corresponding scanner is operated through the corresponding DataSource. Above these DataSources, there is a DataSource Manager (hereinafter referred to as DSM), which manages these DSs as the manager of DS. Therefore, when the user operates the scanning application software, a DSM needs to be created first, and a MSG_OPENDSM message will be sent during this creation process. When the Twain component on the desktop receives this message, a DS named Sane, which is generated by mapping the local scanner, will appear in the source list of DSM for selection. Of course, this source is a scanner driver mapped through the SANE protocol when the local physical scanner is connected to the terminal Linux system. However, in order to be operated by the TWAIN framework on the desktop, the scanner under the SANE protocol will be mapped to a scanner source supported by the TWAIN protocol. At this time, the user can select this source through the above-mentioned "Select Device" menu item (SelectSource) to perform the next operation.

[0060] Waking up the scanner through the scanning software based on the TWAIN framework is specifically as follows: The program of the application software sends a MSG_OPENDS message to the TWAIN protocol; the program of the application software selects the virtual device source to wake up the mapped local SANE scanner; the virtual device source is mapped from the SANE protocol scanner on the local domestic Linux operating system to the Windows desktop.

[0061] S2. According to the working process of the TWAIN framework, the TWAIN process component constructs a corresponding TWAIN request, converts the TWAIN request into a corresponding SANE request, and then sends the converted SANE request to the SANE framework on the local client to execute the corresponding scanning job;

[0062] Among them, after the TwainProcess component obtains the MSG_OPENDS message, it brings up the local management interface for managing SANE scanners. Specifically, the application sends a MSG_OPENDS message to the TWAIN protocol. When our TWAIN protocol component obtains this message, the local management interface for managing SANE scanners will be launched. This is a windowed management software developed based on Qt for invoking the SANE scanner interface. Although this program runs on the local client, by establishing a parent-child relationship between the program window and the cloud desktop window and tightly coupling them together, users will not feel that this is a program on the client, but think that they are still operating a program on the cloud desktop. In this way, users will not have the sense of disconnection from switching back and forth between the desktop and the local client.

[0063] Among them, the management interface is a printer management software running locally, and the management interface is created through a child window of the cloud desktop window.

[0064] Among them, after the management interface appears, a callback message is generated to notify that the TWAIN protocol device on the desktop is ready, and the TWAIN receives the MSG_ENABLEDS message and waits for the transmission of image data. Specifically, when the SANE management program is launched, the local SANE protocol scanner has actually been opened. For the TWAIN protocol on the cloud desktop, it also enters the state of the fourth stage, that is, "Source Open". When the management program interface appears, a callback message will be generated to notify that the TWAIN protocol device on the desktop is ready. In this way, the TWAIN will receive a MSG_ENABLEDS message. Next, the TWAIN starts to wait for the transmission of image data.

[0065] In this embodiment, the operations on the local physical scanner are implemented through the interface of the SANE protocol, and these operations are all interacted with the user through the above-mentioned SANE management program interface. Specifically, this embodiment provides the operations in the case of single-page scanning. First, after the user invokes the SANE management software, the software will obtain the list of locally connected scanners through the sane_get_devices interface. The list will appear in the device selection window, and the user can select the corresponding device for operation. When the user selects a device, the corresponding device will be opened through the sane_open interface. Then, the sane_get_option_descriptor interface is called to obtain the detailed parameters of the device, including the resolution, color, etc. of the scanner. These parameters will be presented in the form of a list in the interface, allowing the user to select the corresponding parameters, such as setting the resolution, setting color or black-and-white scanning, etc. When the user has set the parameters, the set parameter information will be set into the selected scanner driver through the sane_control_option interface. After the user has set the parameters, the file can be scanned. The SANE management software will continuously scan the data through the sane_read interface until a whole image is read and a message named MSG_TRANSFERREADY is sent to the TWAIN protocol on the desktop. TWAIN will then send a MSG_GET message to the client to obtain the image data. When the whole page of data is scanned, the TWAIN on the desktop will receive a MSG_ENDXFER message, notifying that the scanning is completed, and the SANE management program will be closed to complete the entire scanning job.

[0066] S3. After completing the scanning job, the SANE component on the local client receives the SANE request for completing the scanning job, and converts the SANE request into a corresponding TWAIN message, notifying the cloud desktop that the scanning job has been completed, and fetching the image through the TWAIN framework.

[0067] Among them, the request for fetching the image is completed locally in the SANE manner, and then the result of the scanning job is submitted from the local SANE framework to the TWAIN framework on the desktop.

[0068] Embodiment 2

[0069] The difference between this embodiment and the first embodiment is that if the user selects continuous scanning, after the data on the current page is scanned, the TWAIN on the desktop is set to the Transferring state. When the data on the next page is scanned, a MSG_TRANSFERREADY message is sent to notify TWAIN that it can acquire a new picture, and then MSG_GET is continuously sent to obtain image data. Specifically, when a full page of data is scanned, the TWAIN protocol on the cloud desktop is not immediately notified that the scanning has ended. Instead, the TWAIN on the desktop remains in state 7 (Transferring). When a new page of data is scanned, a MSG_TRANSFERREADY message is sent to notify TWAIN that it can acquire a new picture, and then MSG_GET is continuously sent to obtain image data. This process loops continuously until all images are scanned. The local SANE management software will send an end command to notify the client to send a MSG_ENDXFER message to the TWAIN protocol on the desktop to end the transfer process. Subsequently, the SANE management software is closed. After receiving all the image data, the TWAIN on the desktop will send a MSG_CLOSEDS message to close the SANE scanner virtual source of the mapped client on the desktop. After closing DS, a MSG_CLOSEDSM message will be sent to notify the closure of DSM, completing the entire scanning process.

[0070] Embodiment Three

[0071] Please refer to Figure 7 , a scanner mapping terminal on a cloud desktop, including a memory, a processor, and a computer program stored on the memory and executable on the processor, characterized in that when the processor executes the computer program, it implements the steps of a scanner mapping method on a cloud desktop in any one of the above-mentioned Embodiments One to Two.

[0072] In summary, a scanner mapping method and terminal provided by the present invention create a virtual SANE protocol scanner device in the virtual machine of the cloud desktop, and package the scanning task and send it to the TWAIN protocol scanning software on the cloud desktop, so that users can use the physical scanner device on the local terminal on a cross-platform cloud desktop.

[0073] It should be noted that, for the foregoing method embodiments, for the sake of simplicity of description, they are all expressed as a series of action combinations. However, those skilled in the art should know that the present invention is not limited by the described action sequence, because according to the present invention, some steps can be performed in other sequences or simultaneously. Secondly, those skilled in the art should also know that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily essential to the present invention.

[0074] In the above embodiments, the descriptions of the respective embodiments have their own emphases. For parts not detailed in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0075] The above are only the embodiments of the present invention, and do not limit the patent scope of the present invention accordingly. Any equivalent structure or equivalent process transformation made by using the content of the specification and drawings of the present invention, or directly or indirectly applied in other related technical fields, shall be equally included in the patent protection scope of the present invention.

Claims

1. A scanner mapping method on a cloud desktop, characterized in that, it includes the following steps: S1. Construct a data source file recognized by the TWAIN framework on the Windows system cloud desktop, and wake up the scanner through scanning software based on the TWAIN framework. Specifically: the program of the application software sends an open device message to the TWAIN protocol; S2. According to the working process of the TWAIN framework, the TWAIN process component constructs a corresponding TWAIN request, converts the TWAIN request into a corresponding SANE request, and then sends the converted SANE request to the SANE framework on the local client to execute the corresponding scanning job. Specifically: When the TWAIN process component obtains the open device message, it calls out the local management interface for managing the SANE scanner. The management interface is a printer management software running locally and created through a sub-window of the cloud desktop window; When the management interface appears, a callback message is generated to notify that the TWAIN protocol device on the cloud desktop is ready. The TWAIN framework receives the ready message and waits for the transmission of image data; S3. After completing the scanning job, the SANE component on the local client receives the SANE request for completing the scanning job, and converts the SANE request into a corresponding TWAIN message to notify the cloud desktop that the scanning job has been completed, and retrieves the image through the TWAIN framework.

2. A scanner mapping method on a cloud desktop according to claim 1, characterized in that, in step S1, the TWAIN framework consists of three parts: application software, device resource manager, and device driver resource; communication between the three parts is realized through an entry function; the application software includes a device selection entry and a scanning entry; the device resource manager is used to select the device type; the device driver resource is used to control the underlying driver of the image device according to the TWAIN specification.

3. A scanner mapping method on a cloud desktop according to claim 2, characterized in that, in step S1, waking up the scanner through scanning software based on the TWAIN framework is specifically: the program of the application software sends an open device message to the TWAIN protocol; the program of the application software selects the virtual device source and wakes up the mapped local SANE scanner; the virtual device source is mapped from the SANE protocol scanner on the local Linux operating system to the Windows system cloud desktop.

4. A scanner mapping method on a cloud desktop according to claim 1, characterized in that, in step S3, the request for retrieving the image is completed locally in the SANE manner, and then the result of the scanning job is submitted from the local SANE framework to the TWAIN framework on the cloud desktop.

5. A scanner mapping method on a cloud desktop according to claim 1, characterized in that, If the user selects continuous scanning, after the data on the current page is scanned, the TWAIN on the cloud desktop is put into the transmission state. When the data on the next page is scanned, a transmission preparation message is sent to notify TWAIN that it can obtain a new picture, and then the acquisition information is continuously sent to obtain the image data.

6. A scanner mapping terminal on a cloud desktop, comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, characterized in that, when the processor executes the computer program, each step in a scanner mapping method on a cloud desktop according to any one of claims 1 to 5 is implemented.

Images