Printer driver synchronization method and system, electronic equipment and storage medium

Abstract

The invention discloses a printer driver synchronization method and system, electronic equipment and a storage medium, and belongs to the technical field of computer networks. The method comprises the following steps: in response to a printer, connecting a cloud desktop of a first resource pool, and querying whether a drive file corresponding to the printer is installed in the cloud desktop through the cloud desktop; under the condition that the driver file is not installed, sending a driver acquisition request to the cloud management platform through the cloud desktop; executing a drive synchronization process through the cloud management platform according to the equipment information; wherein the drive acquisition request comprises equipment information of the printer, and the drive acquisition request is used for triggering the cloud management platform to execute a drive synchronization process; the drive synchronization process is used for the cloud desktop of the first resource pool to obtain the drive file and execute printing operation after installation. The problems that an existing printer drive synchronization method is large in workload and complex in process can be solved.

Description

Technical Field

[0001] This application belongs to the field of computer network technology, and specifically relates to a synchronization method, system, electronic device and storage medium for a printer driver. Background Technology

[0002] With the increasing popularity of cloud computing services, the ease of use, controllability, and reliability of printing on cloud desktops, a rigid requirement in office scenarios, urgently need improvement. Currently, printing in cloud desktop office scenarios suffers from problems such as cumbersome driver installation and difficulty in managing permissions.

[0003] Currently, the service cloud desktop has pre-installed printer drivers for some manufacturers. However, due to the large number of printer models, many printers still require maintenance and support personnel to manually perform operations such as remotely connecting to the service cloud desktop, copying driver files, and installing drivers in order to synchronize the printer drivers across different cloud desktops. This results in a large workload and complex processes. Summary of the Invention

[0004] The purpose of this application is to provide a printer driver synchronization method, system, electronic device, and storage medium that can solve the problems of large workload and complex process in existing printer driver synchronization methods.

[0005] In a first aspect, embodiments of this application provide a synchronization method for a printer driver, the method comprising: In response to the printer connecting to the cloud desktop of the first resource pool, the system queries whether the cloud desktop has the driver file corresponding to the printer installed. If the driver file is not installed, the system sends a driver acquisition request to the cloud management platform through the cloud desktop. The cloud management platform then executes a driver synchronization process based on the device information. The driver acquisition request includes the printer's device information and is used to trigger the cloud management platform to execute the driver synchronization process. The driver synchronization process is used for the cloud desktop of the first resource pool to acquire the driver file and perform a printing operation after installation.

[0006] Optionally, the step of executing the driver synchronization process through the cloud management platform based on the device information includes: The driver file information of each cloud desktop associated with the first resource pool is obtained through the cloud management platform; the driver file information includes at least the driver version, supported printer models, and storage status. If the driver file information matches the device information, the cloud management platform performs driver synchronization with the resource pool to synchronize the driver file within the first resource pool. If the driver file information does not match the device information, cross-resource pool driver synchronization is performed through the cloud management platform so that the driver file is synchronized from the second resource pool to the first resource pool.

[0007] Optionally, when the driver file information matches the device information, performing driver synchronization with the same resource pool through the cloud management platform to synchronize the driver file within the first resource pool includes: If the driver file information matches the device information, the target cloud desktop storing the driver file is determined through the cloud management platform; A first notification message is sent to the target cloud desktop through the cloud management platform; The cloud management platform sends a second notification message to the cloud desktops in the first resource pool that do not store the driver file. The first notification message is used to instruct the target cloud desktop to upload the driver file to the distributed storage of the first resource pool; the second notification message is used to instruct the cloud desktop that does not store the driver file to download the driver file from the distributed storage and install it.

[0008] Optionally, in the case that the driver file information does not match the device information, performing cross-resource pool driver synchronization through the cloud management platform to synchronize the driver file from the second resource pool to the first resource pool includes: If the driver file information does not match the device information, the target cloud desktop storing the driver file is determined through the cloud management platform; A third notification message is sent to the target cloud desktop through the cloud management platform; The driver file is copied from the distributed storage of the second resource pool to the distributed storage of the first resource pool through the cloud management platform. The cloud management platform sends a fourth notification message to the cloud desktops in the first resource pool that do not store the driver file. The third notification message is used to instruct the target cloud desktop to upload the driver file to the distributed storage of the second resource pool; the fourth notification message is used to instruct the cloud desktop that does not store the driver file to download the driver file from the distributed storage of the first resource pool and install it.

[0009] Optionally, the method further includes: The cloud desktop identifier and address information of the target cloud desktop are obtained through the cloud management platform; The cloud management platform generates either the first notification message or the second notification message based on the cloud desktop identifier and address information and a preset message format. The cloud management platform uses a timed message queue to send either the first notification message or the second notification message to the target cloud desktop.

[0010] Optionally, after executing the driver synchronization process based on the device information through the cloud management platform, the method further includes: The cloud management platform generates synchronization-related information, including driver file name, version, source resource pool, target resource pool, synchronization type, synchronization time, and installation result. The synchronization-related information is displayed in the client's interface.

[0011] Optionally, the display interface includes a new driver control, a batch operation control, and the method further includes at least one of the following: In response to a trigger operation on the newly added driver control, a new printer driver is added; In response to a trigger operation on the newly added driver control, manage prohibited drivers; In response to a trigger operation on the batch operation control, batch distribution, deletion, and other operations are performed on multiple drivers.

[0012] Secondly, embodiments of this application provide a synchronization device for a printer driver, the device comprising: The driver query module is used to respond to the cloud desktop where the printer is connected to the first resource pool and query whether the cloud desktop has the driver file corresponding to the printer installed. The driver acquisition module is used to send a driver acquisition request to the cloud management platform through the cloud desktop when the driver file is not installed. The driver synchronization module is used to execute the driver synchronization process based on the device information through the cloud management platform; The driver acquisition request includes the printer's device information, and the driver acquisition request is used to trigger the cloud management platform to execute the driver synchronization process; the driver synchronization process is used for the cloud desktop of the first resource pool to acquire the driver file and perform a printing operation after installation.

[0013] Thirdly, embodiments of this application provide an electronic device including a processor, a memory, and a program or instructions stored in the memory and executable on the processor, wherein the program or instructions, when executed by the processor, implement the steps of the printer driver synchronization method as described in the first aspect.

[0014] Fourthly, embodiments of this application provide a readable storage medium storing a program or instructions that, when executed by a processor, implement the steps of the printer driver synchronization method as described in the first aspect.

[0015] In this embodiment, in response to the printer connecting to the cloud desktop of the first resource pool, the system automatically queries whether the cloud desktop stores driver files. If no driver files are stored, the system automatically obtains and installs the driver files, thus automating the upload and download process and significantly improving the efficiency of driver management. Furthermore, the cloud management platform executes a driver synchronization process based on device information, enabling the cloud desktop of the first resource pool to obtain and install driver files. Through the unified scheduling of the cloud management platform, the upload and download operations of drivers are simplified, management efficiency is improved, and manual intervention is reduced. Attached Figure Description

[0016] Figure 1 This is a flowchart of a printer driver synchronization method provided in an embodiment of this application.

[0017] Figure 2 This is a flowchart illustrating the specific steps of a printer driver synchronization method provided in an embodiment of this application.

[0018] Figure 3 This is a schematic diagram of a driver synchronization method for the same resource pool provided in an embodiment of this application.

[0019] Figure 4 This is a schematic diagram of a cross-resource pool driver synchronization method provided in an embodiment of this application.

[0020] Figure 5 This is a schematic diagram of a client display interface provided in an embodiment of this application.

[0021] Figure 6 This is a schematic diagram of another client display interface provided in an embodiment of this application.

[0022] Figure 7 This is a schematic diagram of another client display interface provided in an embodiment of this application.

[0023] Figure 8 This is a schematic diagram of a printer driver synchronization system provided in an embodiment of this application.

[0024] Figure 9 This is a block diagram of a printer driver synchronization device provided in an embodiment of this application.

[0025] Figure 10 This is a block diagram of an electronic device provided in an embodiment of this application.

[0026] Figure 11 This is a block diagram of another electronic device provided in the embodiments of this application. Detailed Implementation

[0027] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0028] The terms "first," "second," etc., used in the specification and claims of this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such use of data can be interchanged where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein. Furthermore, in the specification and claims, "and / or" indicates at least one of the connected objects, and the character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0029] A printer driver file is a dedicated software program that enables communication between a computer or cloud desktop and the printer. It converts printing instructions sent by the computer, such as print content, format, and paper size, into a language that the printer can understand. At the same time, it feeds back the printer's status, such as out of paper, paper jam, or printing completed, to the computer.

[0030] Cloud desktops are virtual desktop services based on cloud computing technology. They store a computer's operating system, software, and data on a cloud server, allowing users to remotely access and use the virtual computer in the cloud using their local devices, without needing to install complex operating systems or store large amounts of data on their local devices. Because cloud desktops are virtualized environments, drivers cannot be directly installed locally like on physical machines. Driver resources must be managed centrally through the cloud desktop service; driver files must be parsed and uploaded to cloud storage via the cloud desktop. The version and compatibility of driver files directly affect the stability of the printing service.

[0031] Although the service cloud desktop comes pre-installed with printer drivers from some manufacturers, there are numerous printer models, and many printers still require maintenance and support personnel to manually connect remotely to the service cloud desktop, copy driver files, and install drivers. This results in a large amount of repetitive work related to driver recording, updating, and alignment, primarily in three scenarios: 1. Several service cloud desktops exist within the same resource pool, all requiring manual installation. 2. Driver file resources are not shared between resource pools; if drivers from other resource pools are not used, manual operation is still required. 3. In different virtual cloud desktop environments within a resource pool, the consistency of printer functionality and performance cannot be guaranteed, leading to compatibility and operational issues due to inconsistent driver versions.

[0032] To address the aforementioned issues, this application provides a printer driver synchronization method, system, electronic device, and storage medium. The printer driver synchronization method provided in this application will be described in detail below with reference to the accompanying drawings and specific embodiments and application scenarios.

[0033] Figure 1 This is a flowchart of a printer driver synchronization method provided in an embodiment of this application. See also... Figure 1 The method includes the following steps.

[0034] Step 101: In response to the printer connecting to the cloud desktop of the first resource pool, query the cloud desktop to see if the corresponding driver file for the printer is installed.

[0035] In some embodiments, the connection between the printer and the cloud desktop of the first resource pool can be via Universal Serial Bus (USB), Transmission Control Protocol (TCP) connection, etc.

[0036] In some embodiments, cloud desktops are categorized into ordinary cloud desktops and service cloud desktops based on their function, type, and form. Both ordinary cloud desktops and service cloud desktops are virtualized instances on physical servers. Ordinary cloud desktops are cloud desktop clients, while service cloud desktops are cloud desktop drivers. Ordinary cloud desktops interact with service cloud desktops.

[0037] For example, a regular cloud desktop refers to virtual desktop infrastructure. That is, a regular cloud desktop is a virtual desktop accessed by the user, providing a basic desktop environment and print client application where the user can start printing documents. Regular cloud desktops are also used to query available service cloud desktops with printer drivers and initiate print jobs. Service cloud desktops, on the other hand, have driver management and print job processing capabilities. They are dedicated virtual desktops that provide environmental support for printing services, or report information such as driver file versions, paths, and supported printer models to the cloud management platform.

[0038] In some embodiments, step 101 may include: in response to the printer connecting to the ordinary cloud desktop of the first resource pool, querying whether the driver file corresponding to the printer is stored locally through the ordinary cloud desktop.

[0039] Step 102: If no driver files are installed, send a driver acquisition request to the cloud management platform via the cloud desktop.

[0040] In this embodiment, the driver acquisition request includes printer device information, and the driver acquisition request is used to trigger the cloud management platform to execute the driver synchronization process.

[0041] In some embodiments, the printer's device information includes the printer's model number.

[0042] In some embodiments, the cloud management platform is also referred to as the "business management platform". The cloud management platform is used to drive file information management, respond to printer availability queries, and drive file synchronization triggering and scheduling. In other words, the cloud management platform is a central management system, a management platform running in containerized form on a cloud server.

[0043] In some embodiments, a regular cloud desktop initiates a query request to the business management platform through an Application Programming Interface (API) or interface call to check the available service cloud desktops for the currently connected printer. The available service cloud desktops are those with the corresponding driver files for the printer installed.

[0044] For example, the printer model is printer Model. A regular cloud desktop requests the available service cloud desktop of printer Model from the meta management platform via HTTPS.

[0045] Step 103: Execute the driver synchronization process through the cloud management platform based on the device information.

[0046] In this embodiment of the application, the driver synchronization process is used for the cloud desktop of the first resource pool to obtain the driver file and perform a printing operation after installation.

[0047] In some embodiments, the service cloud desktop reports information such as driver file version, path, and supported printer models to the cloud management platform via API or interface calls.

[0048] In some embodiments, the cloud management platform determines whether printer driver files exist for some service cloud desktops in the current resource pool. If yes, it triggers a driver synchronization operation within the same resource pool; if not, it determines whether printer driver files exist in other resource pools. If they exist, it triggers cross-resource pool driver synchronization.

[0049] In some embodiments, the cloud management platform includes a high-performance distributed object storage system (MinIO) based on open-source technology and a relational database management system (MySQL) database, wherein MinIO is used to store driver files and the MySQL database is used to store cloud desktop information, driver file records, etc.

[0050] This allows for efficient management of large numbers of drive files and supports fast file transfers using high-performance object storage compatible with Amazon S3. Traditional solutions typically rely on local storage, resulting in poor flexibility and scalability. However, by adopting MinIO, the storage system possesses significantly improved cross-resource pool data transfer capabilities.

[0051] In some embodiments, after the cloud desktop obtains and installs the driver file, the user selects the target printer in the cloud desktop application, sets the printing parameters, and submits a request; the application passes the print content to the printing service of the cloud desktop operating system; the printing service calls the installed driver file to convert general printing data into printer-specific instructions; the driver file transmits the converted instructions to the printer through the previously established connection.

[0052] In some embodiments, step 103 may include: querying whether the cloud desktop associated with the first resource pool stores driver files based on device information through the cloud management platform, and obtaining the query result; and executing the driver synchronization process based on the query result through the cloud management platform.

[0053] In this embodiment, the driver synchronization process is used for the cloud desktops of the first resource pool to obtain driver files and install them.

[0054] In some embodiments, the driver synchronization process includes synchronization with the same resource pool driver or synchronization across resource pool drivers. A resource pool is a shared pool that integrates the computing power, storage resources, and network bandwidth of multiple physical servers, storage devices, and network devices. This resource pool is then allocated on demand to virtual instances such as cloud desktops and virtual machines through a cloud management platform.

[0055] In some embodiments, the cloud management platform notifies the service cloud desktop containing the driver to upload the driver file, and simultaneously notifies the service cloud desktop without the driver to download the required driver file, so that all service cloud desktops under the user resource pool can provide services for the user's print jobs.

[0056] In some embodiments, after step 103, the above-mentioned printer driver synchronization method may further include: sending the installation result to the cloud management platform via a cloud desktop.

[0057] In summary, in this embodiment, in response to the printer connecting to the cloud desktop of the first resource pool, the system automatically queries whether the cloud desktop stores driver files. If no driver files are stored, the system automatically obtains and installs the driver files, thus automating the upload and download process and significantly improving the efficiency of driver management. Furthermore, the cloud management platform executes a query based on device information to determine whether the cloud desktop associated with the first resource pool stores driver files, and executes a driver synchronization process based on the query results. This enables the cloud desktop of the first resource pool to obtain and install the driver files. Through the unified scheduling of the cloud management platform, the upload and download operations of drivers are simplified, management efficiency is improved, and manual intervention is reduced.

[0058] Figure 2 This is a flowchart illustrating the specific steps of a printer driver synchronization method provided in an embodiment of this application. See also... Figure 2 The method includes the following steps.

[0059] Step 201: In response to the printer connecting to the cloud desktop of the first resource pool, query the cloud desktop to see if the corresponding driver file for the printer is stored locally.

[0060] The method for this step has been explained in step 101 above, and will not be repeated here.

[0061] Step 202: If the driver file is not stored, send the first acquisition request to the cloud management platform via the cloud desktop.

[0062] The method for this step has been explained in step 102 above, and will not be repeated here.

[0063] Step 203: Obtain the driver file information for each cloud desktop associated with the first resource pool through the cloud management platform.

[0064] In this embodiment of the application, the driver file information includes at least the driver version, supported printer models, and storage status.

[0065] For example, the driver file information is as follows: infPath; / / Path to the driver's inf file version; / / Driver INF file version manufacturer; driverName; / / Driver Name deviceId; / / Unique identifier for printer model device printerName; / / Printer name fileStatus; / / Driver file status 0: Invalid 1: Valid printCount; / / Number of prints using the driver file printSucCount; / / Prints the number of successful attempts using the driver file. infoReportStatus; / / Driver information reporting status: 0: Initialized; 1: Reported fileReportStatus; / / Driver file upload status 0: Initialized 1: Uploaded In some embodiments, prior to step 201, the printer driver synchronization method may further include: each cloud desktop periodically uploading its own driver file information to the cloud management platform. This significantly improves the efficiency of driver management through automated upload and download processes. Traditional methods require administrators to manually install drivers, increasing labor costs and the possibility of errors. The automated synchronization mechanism of this application greatly improves the reliability and efficiency of the operation.

[0066] In some embodiments, the driver file information for the cloud desktop is stored in the driver management database of the cloud management platform.

[0067] For example, the INF file path is C:\Windows\System32\... The INF file is a Windows driver installation configuration file that records the driver's installation logic, dependencies, and other information. The driver version number is 11.0.0.0, used to distinguish driver iterations. The corresponding device manufacturers include BROTHER, KYOCERA, CANON, etc. The driver name is Brother HL-L2340D series, the printer model device unique identifier is BrotherHL-L2340D_SER6305, the printer name is yocera FS-1125MFP, and the file status value of 1 indicates validity.

[0068] Step 204: If the driver file information matches the device information, perform driver synchronization with the resource pool through the cloud management platform so that the driver file is synchronized within the first resource pool.

[0069] For example, if the cloud management platform's driver management database stores a unique identifier for the printer model, the cloud management platform can determine that the service cloud desktop in the first resource pool stores the driver files. The above technical solution enables efficient sharing of driver files within the same resource pool and across different resource pools, avoiding duplicate installations and ensuring that all cloud desktops can access the latest driver files. Existing technologies are typically limited to a single resource pool and cannot flexibly address driver requirements in multi-resource pool environments, thus reducing the effective utilization of resources.

[0070] In some embodiments, step 204 may include: Sub-step 2041: If the driver file information matches the device information, determine the target cloud desktop that stores the driver file through the cloud management platform; Sub-step 2042: Send the first notification message to the target cloud desktop through the cloud management platform; Sub-step 2043: Send a second notification message to the cloud desktops in the first resource pool that do not store driver files through the cloud management platform.

[0071] The first notification message instructs the target cloud desktop to upload the driver file to the distributed storage of the first resource pool; the second notification message instructs the cloud desktop that does not store the driver file to download the driver file from the distributed storage and install it; the first notification message and the second notification message are timed message queues (Kafka).

[0072] In some embodiments, prior to sub-step 2042, the above-described printer driver synchronization method may further include: Sub-step S1: Obtain the cloud desktop identifier and address information of the target cloud desktop through the cloud management platform; Sub-step S2 involves generating a first notification message through the cloud management platform based on the cloud desktop identifier and address information and a preset message format. Sub-step S3 involves sending the first notification message to the target cloud desktop via a timed message queue through the cloud management platform.

[0073] For example, resource pool B stores a service cloud desktop (B-Service-005) driven by "CanonLBP214dw". The cloud management platform queries the driver file information of each cloud desktop associated with resource pool B, filters out records with deviceId=Canon_LBP214dw and fileStatus=1 (valid), and obtains the cloud desktop identifier of the service cloud desktop: desktopId="B-Service-005" (unique ID), resourcePoolId="PoolB" (to which resource pool belongs), and address information: ip="192.168.2.105" (the local area network IP of the cloud desktop), kafkaPartition=3 (pre-allocated Kafka message partition). Based on the above identifier and address information, the cloud management platform generates a first notification message in a preset JSON format; using Kafka's timed delivery mechanism, the first notification message is sent to the target cloud desktop.

[0074] It should be noted that the steps for the cloud management platform to generate the second, third, and fourth notification messages are similar to those for the first notification message, and will not be repeated here.

[0075] In some embodiments, the first notification message is an upload group, and the second notification message is a download group.

[0076] For example, create a topic driver-upload-topic to notify the service cloud desktop to upload driver files; create a topic driver-download-topic to notify the service cloud desktop to download and install driver files.

[0077] In some embodiments, the target cloud desktop, in response to a first notification message, uploads the driver file to the distributed storage of the first resource pool. For example, resource pool A serves cloud desktop 1 by uploading the driver file (driverFile) to MinIO of resource pool A via HTTPS communication.

[0078] In some embodiments, a cloud desktop that has not stored a driver file responds to a second notification message, downloads the driver file from distributed storage, and installs it; after installation, it reports the installation result to the cloud management platform. For example, cloud desktop 2, which serves resource pool A, downloads the driver file driverFile from resource pool A MinIO via HTTPS communication; resource pool A serves cloud desktop 2 to perform automated installation and reports the installation result to the cloud management platform.

[0079] In this embodiment of the application, the cloud desktop is actually a virtualized instance on a physical server, and the driver files are stored in the memory area allocated to the cloud desktop in the memory of the physical server.

[0080] For example, Figure 3 This is a schematic diagram illustrating a driver synchronization method for the same resource pool provided in an embodiment of this application. See also... Figure 3 The driver synchronization method for the same resource pool can include the following steps.

[0081] (1) The resource pool service cloud desktop realizes the automatic parsing, registration and updating of driver file information, and reports information such as driver file version, path and supported printer model to the business management platform.

[0082] (2) The resource pool ordinary cloud desktop queries the business management platform for available service cloud desktops for the currently connected printer.

[0083] (3) The business management platform determines that some services in the resource pool have driver files for cloud desktops, and triggers driver synchronization with the resource pool. (4) The business management platform generates upload and download groups, notifies the cloud desktops containing drivers to upload driver files, and notifies the cloud desktops without driver files to download and install them.

[0084] (5) Resource pool service cloud desktop 1 uploads driver files to resource pool A MinIO.

[0085] (6) The resource pool service downloads the driver file for Cloud Desktop 2, performs automated installation, and reports the installation results to the business management platform.

[0086] It should be noted that, Figure 3 The business management platform in this application is the cloud management platform in the embodiment of this application, and resource pool A is the first resource pool.

[0087] The above technical solutions, using the Kafka messaging mechanism for notifications, enable more efficient automation. Message queues handle file uploads and downloads, reducing system latency and communication costs. HTTPS transmission and the use of MinIO ensure data transmission security and efficiency, significantly improving communication and data transmission efficiency across resource pools.

[0088] Step 205: If the driver file information does not match the device information, perform cross-resource pool driver synchronization through the cloud management platform so that the driver file is synchronized from the second resource pool to the first resource pool.

[0089] The above technical solutions, including the driving synchronization technology for both same and cross resource pools, not only improve resource utilization efficiency and system flexibility, but also reduce management and maintenance costs, and enhance user experience and service quality.

[0090] In some embodiments, step 205 may include: Sub-step 2051: If the driver file information does not match the device information, determine the target cloud desktop that stores the driver file through the cloud management platform; Sub-step 2052: Send a third notification message to the target cloud desktop through the cloud management platform; Sub-step 2053: Copy the driver file from the distributed storage of the second resource pool to the distributed storage of the first resource pool through the cloud management platform; Sub-step 2054: Send a fourth notification message to the cloud desktops in the first resource pool that do not store driver files through the cloud management platform.

[0091] The third notification message is used to instruct the target cloud desktop to upload the driver file to the distributed storage of the second resource pool; the fourth notification message is used to instruct the cloud desktop that has not stored the driver file to download the driver file from the distributed storage of the first resource pool and install it; the third notification message and the fourth notification message are timed message queues.

[0092] In some embodiments, the target cloud desktop, in response to a third notification message, uploads the driver file to the distributed storage of the first resource pool. For example, resource pool B serves cloud desktop 1 by uploading the driver file (driverFile) to MinIO of resource pool B via HTTPS communication.

[0093] In some embodiments, the driverFile file is copied from MinIO in resource pool B to MinIO in resource pool A via MinIO-Client in the cloud management platform.

[0094] In some embodiments, a cloud desktop that has not stored a driver file responds to a fourth notification message, downloads the driver file from distributed storage, and installs it; after installation, it reports the installation result to the cloud management platform. For example, cloud desktop 2, which serves resource pool A, downloads the driver file driverFile from resource pool A MinIO via HTTPS communication; resource pool A serves cloud desktop 2 to perform automated installation and reports the installation result to the cloud management platform.

[0095] For example, Figure 4 This is a schematic diagram illustrating a cross-resource pool driver synchronization method provided in an embodiment of this application. See also... Figure 4 The cross-resource pool driver synchronization method may include the following steps.

[0096] (1) Resource Pool B service cloud desktop realizes automatic parsing, registration and updating of driver file information, and reports information such as driver file version, path and supported printer model to the business management platform.

[0097] (2) The ordinary cloud desktop of resource pool A queries the business management platform for the available cloud desktops of resource pool A for the currently connected printer.

[0098] (3) The business management platform determines that none of the service cloud desktops in the resource pool have the driver file for the printer, but other resource pools do. This triggers cross-resource pool driver synchronization. The business management platform generates an upload group and a download group, notifies the service cloud desktops containing the driver to upload the driver file, and notifies the service desktops without the driver file to download and install it.

[0099] (4) Upload driver files from the cloud desktop of resource pool B to resource pool B MinIO.

[0100] (5) Copy the driver file from resource pool B minio to resource pool A MinIO.

[0101] (6) Download driver files for the cloud desktop of resource pool A, perform automated installation, and report the installation results to the business management platform.

[0102] It should be noted that, Figure 4 The business management platform in this application is the cloud management platform in the embodiments of this application.

[0103] In some embodiments, after step 205, the synchronization of the printer driver may further include sub-steps 206 to 207.

[0104] Sub-step 206: Generate relevant synchronization information through the cloud management platform.

[0105] In this embodiment, the synchronization-related information includes driver file name, version, source resource pool, target resource pool, synchronization type, synchronization time, and installation result.

[0106] For example, the driver file name indicates the driver file identifier for synchronization; the supported printer indicates the printer model that the driver is compatible with; the operation type includes automatic synchronization, and the synchronization type includes local resource pool synchronization or cross-resource pool synchronization; the source desktop / target desktop shell driver synchronization initiator (source) and receiver (target) cloud desktop IDs; the synchronization time indicates the execution time of the driver synchronization; the installation result includes installation in progress.

[0107] Sub-step 207: Display synchronization-related information in the client's display interface.

[0108] In this embodiment of the application, the client's display interface can be the driver synchronization management interface of the cloud management platform, which is displayed in the designated client so that operation and maintenance personnel can use this interface to manage the drivers of various cloud desktops.

[0109] For example, see Figure 5 The client's display interface shows synchronization-related information, including driver file name, version, source resource pool, target resource pool, synchronization type, synchronization time, and installation results.

[0110] In some embodiments, the display interface includes a new driver control, a batch operation control, and a batch operation control.

[0111] In some embodiments, the above-described printer driver synchronization method further includes at least one of the following: Sub-step 208: In response to a trigger operation for a newly added driver control, add a new printer driver; Sub-step 209, in response to a trigger operation for a newly added driver control, manages the prohibited drivers; Sub-step 210, in response to a trigger operation on the batch operation control, performs batch distribution, deletion, and other operations on multiple drivers.

[0112] For example, see Figure 6 "Add Driver" is used to add new printer drivers; "Blacklist" is used to manage prohibited drivers; "Driver Synchronization Record" is used to query the synchronization history of drivers between cloud desktops; "Batch Operation" is used to perform batch distribution, deletion, and other operations on multiple drivers. Search criteria include: drivers can be filtered by "Supported Printer Models" and "Driver File Name" to quickly locate the target driver.

[0113] In one possible implementation, in response to a trigger operation for adding a new driver control, an information input control and an installation package upload control are displayed on the client's interface; wherein, the information input control is used to input the printer model to be added as a driver; and the installation package upload control is used to upload the driver's installation file.

[0114] See Figure 7 When you click "Add Driver," a configuration window will pop up, where you can enter key information about the new driver. "Supported Printer Models" is for entering compatible printer models (multiple models separated by commas), with a maximum of 200 characters. "Upload Installation Package" is for uploading the driver's installation file (zip format only), which is the core file source for driver installation. The "OK" button completes the addition, and the "Cancel" button cancels the operation.

[0115] The above technical solution enables a driver synchronization management interface for the business management platform, featuring functions such as manually adding driver files, a driver file blacklist, and driver synchronization records. It can monitor driver file usage in real time and quickly provide feedback on installation results, improving problem-solving speed. Traditional methods lack real-time capabilities, making it difficult to promptly identify problems. This mechanism effectively improves system operation and maintenance response capabilities.

[0116] In summary, this application embodiment firstly achieves efficient sharing of driver files within the same resource pool and across resource pools, avoiding duplicate installations and ensuring that all cloud desktops can access the latest driver files. Existing technologies are typically limited to a single resource pool and cannot flexibly address driver requirements in multi-resource pool environments, thus reducing the effective utilization of resources. Secondly, it ensures that the driver file versions on each cloud desktop are consistent, thereby avoiding compatibility issues during printing. Traditional methods often lead to inconsistent driver versions, affecting the success rate of printing tasks, while this invention improves the reliability of the printing process through a real-time monitoring and update mechanism. Finally, through the intelligent judgment and collaborative processing of the cloud management platform, it facilitates the sharing of print drivers, thereby improving the user experience for end users and reducing manual maintenance costs and system high availability.

[0117] Figure 8 This is a schematic diagram of a printer driver synchronization system provided in an embodiment of this application. See also... Figure 8 The printer-driven synchronization system includes multiple cloud management platforms, at least two resource pools, and cloud desktops. In some embodiments, the printer-driven synchronization system can be deployed on a cloud server.

[0118] In this embodiment, the cloud management platform is the control center of the entire process, responsible for receiving configurations, issuing instructions, and coordinating the synchronization between resource pools.

[0119] In this embodiment, the resource pool includes a local resource pool (resource pool A) and other resource pools (resource pool B). Distributed object storage is deployed in the resource pools to store driver files, supporting efficient file transfer methods such as streaming direct transfer.

[0120] In this embodiment, the cloud desktop includes a service cloud desktop and a regular cloud desktop. The service cloud desktop is responsible for reporting driver configurations and uploading / downloading driver files; the regular cloud desktop requests available service cloud desktops.

[0121] In summary, this embodiment improves the efficiency of printer driver management in a virtual desktop environment, preventing poor user experience and print job failures caused by missing or inconsistent drivers. It also enables driver sharing among multiple resource pools, reducing manual driver maintenance costs.

[0122] Figure 9 This is a block diagram of a printer driver synchronization device provided in an embodiment of this application, such as... Figure 9 As shown, the printer driver synchronization device 400 includes the following modules.

[0123] The driver query module 401 is used to respond to the cloud desktop that the printer connects to the first resource pool and query whether the cloud desktop has the corresponding driver file for the printer installed. The driver acquisition module 402 is used to send a driver acquisition request to the cloud management platform via the cloud desktop when no driver file is installed. The drive synchronization module 403 is used to execute the drive synchronization process based on device information through the cloud management platform; The driver acquisition request includes the printer's device information and is used to trigger the cloud management platform to execute the driver synchronization process. The driver synchronization process is used by the cloud desktop in the first resource pool to acquire the driver file and perform the printing operation after installation.

[0124] Optional, driver installation module 403 includes: The driver information acquisition submodule is used to obtain driver file information for each cloud desktop associated with the first resource pool through the cloud management platform; the driver file information includes at least the driver version, supported printer models, and storage status; The same resource pool synchronization submodule is used to perform same resource pool driver synchronization through the cloud management platform when the driver file information matches the device information, so that the driver file is synchronized in the first resource pool. The cross-resource pool synchronization submodule is used to perform cross-resource pool driver synchronization through the cloud management platform when the driver file information and device information do not match, so that the driver file can be synchronized from the second resource pool to the first resource pool.

[0125] Optional, the same resource pool synchronization submodule includes: The first determining unit is used to determine the target cloud desktop containing the driver file through the cloud management platform when the driver file information matches the device information. The first sending unit is used to send a first notification message to the target cloud desktop through the cloud management platform; The second sending unit is used to send a second notification message to the cloud desktop in the first resource pool that does not store driver files through the cloud management platform; The first notification message instructs the target cloud desktop to upload the driver file to the distributed storage of the first resource pool; the second notification message instructs the cloud desktop that has not stored the driver file to download the driver file from the distributed storage and install it.

[0126] Optional cross-resource pool synchronization submodules include: The second determining unit is used to determine the target cloud desktop containing the driver file through the cloud management platform when the driver file information and device information do not match. The third sending unit is used to send a third notification message to the target cloud desktop through the cloud management platform; The fourth sending unit is used to copy the driver file from the distributed storage of the second resource pool to the distributed storage of the first resource pool through the cloud management platform; Send a fourth notification message to cloud desktops in the first resource pool that do not store driver files through the cloud management platform; The third notification message is used to instruct the target cloud desktop to upload the driver file to the distributed storage of the second resource pool; the fourth notification message is used to instruct the cloud desktop that has not stored the driver file to download the driver file from the distributed storage of the first resource pool and install it.

[0127] Optionally, the printer driver synchronization device 400 also includes: The cloud desktop acquisition module is used to obtain the cloud desktop identifier and address information of the target cloud desktop through the cloud management platform; The message generation module is used to generate a first notification message or a second notification message through the cloud management platform based on the cloud desktop identifier and address information and a preset message format; The message sending module is used to send the first or second notification message to the target cloud desktop via a timed message queue through the cloud management platform.

[0128] Optionally, the printer driver synchronization device 400 also includes: The generation module is used to generate synchronization-related information through the cloud management platform. The synchronization-related information includes driver file name, version, source resource pool, target resource pool, synchronization type, synchronization time, and installation result. The display module is used to show synchronization-related information in the client's display interface.

[0129] Optionally, the display interface includes a new driver control, a batch operation control, and the printer driver synchronization device 400 further includes at least one of the following: The driver addition module is used to add new printer drivers in response to trigger operations for newly added driver controls; The driver management module is used to manage prohibited drivers in response to triggering operations for newly added driver controls. The driver operation module is used to respond to trigger operations on batch operation controls and perform batch distribution, deletion, and other operations on multiple drivers.

[0130] As the device embodiment is basically similar to the method embodiment, the description is relatively simple, and relevant parts can be found in the description of the method embodiment.

[0131] Optionally, such as Figure 10As shown, this application embodiment also provides an electronic device 500, including a processor 501 and a memory 502. The memory 502 stores a program or instructions that can run on the processor 501. When the program or instructions are executed by the processor 501, they implement the various steps of the above-described printer driver synchronization method embodiment and can achieve the same technical effect. To avoid repetition, they will not be described again here.

[0132] It should be noted that the electronic devices in the embodiments of this application include the mobile electronic devices and non-mobile electronic devices described above.

[0133] Figure 11 A schematic diagram of the hardware structure of an electronic device to implement an embodiment of this application.

[0134] The electronic device 600 includes, but is not limited to, components such as: radio frequency unit 601, network module 602, audio output unit 603, input unit 604, sensor 605, display unit 606, user input unit 607, interface unit 608, memory 609, and processor 610.

[0135] Those skilled in the art will understand that the electronic device 600 may also include a power supply (such as a battery) for supplying power to various components. The power supply may be logically connected to the processor 610 through a power management system, thereby enabling functions such as managing charging, discharging, and power consumption through the power management system. Figure 11 The electronic device structure shown does not constitute a limitation on the electronic device. The electronic device may include more or fewer components than shown, or combine certain components, or have different component arrangements, which will not be elaborated here.

[0136] The processor 610 is used to implement the above-mentioned printer driver synchronization method.

[0137] It should be understood that, in this embodiment, the input unit 604 may include a graphics processing unit (GPU) 6041 and a microphone 6042. The GPU 6041 processes image data of still images or videos obtained by an image capture device (such as a camera) in video capture mode or image capture mode. The display unit 606 may include a display panel 6061, which may be configured in the form of a liquid crystal display, an organic light-emitting diode, or the like. The user input unit 607 includes at least one of a touch panel 6071 and other input devices 6072. The touch panel 6071 is also called a touch screen. The touch panel 6071 may include a touch detection device and a touch controller. Other input devices 6072 may include, but are not limited to, physical keyboards, function keys (such as volume control buttons, power buttons, etc.), trackballs, mice, and joysticks, which will not be described in detail here.

[0138] The memory 609 can be used to store software programs and various data. The memory 609 may primarily include a first storage area for storing programs or instructions and a second storage area for storing data. The first storage area may store the operating system, application programs, or instructions required for functions (such as sound playback functions, image playback functions, etc.). Furthermore, the memory 609 may include volatile memory or non-volatile memory, or it may include both volatile and non-volatile memory. The non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM), static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous linked dynamic random access memory (Synchlink DRAM, SLDRAM), and direct memory bus RAM (DRRAM). The memory 609 in this embodiment includes, but is not limited to, these and any other suitable types of memory.

[0139] Processor 610 may include one or more processing units; optionally, processor 610 integrates an application processor and a modem processor, wherein the application processor mainly handles operations involving the operating system, user interface, and applications, and the modem processor mainly handles wireless communication signals, such as a baseband processor. It is understood that the aforementioned modem processor may also not be integrated into processor 610.

[0140] This application also provides a readable storage medium storing a program or instructions. When the program or instructions are executed by a processor, they implement the various processes of the above-described printer driver synchronization method embodiments and achieve the same technical effect. To avoid repetition, they will not be described again here.

[0141] The processor is the processor in the electronic device described in the above embodiments. The readable storage medium includes computer-readable storage media, such as computer read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk.

[0142] This application also provides a chip, which includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is used to run programs or instructions to implement the various processes of the above-described printer driver synchronization method embodiments and achieve the same technical effect. To avoid repetition, it will not be described again here.

[0143] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0144] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. Furthermore, it should be noted that the scope of the methods and apparatuses in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may also include performing functions substantially simultaneously or in the reverse order, depending on the functions involved. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

[0145] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal (which may be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0146] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other forms under the guidance of this application without departing from the spirit and scope of the claims, and all of these forms are within the protection scope of this application.

Claims

1. A synchronization method for a printer driver, characterized in that, Applied to a cloud server, wherein multiple cloud desktops, a first resource pool, and a cloud management platform are deployed in the cloud server, and the multiple cloud desktops interact with the first resource pool, the method includes: In response to the printer connecting to the cloud desktop of the first resource pool, query the cloud desktop to see if the cloud desktop has the driver file corresponding to the printer installed; If the driver file is not installed, a driver acquisition request is sent to the cloud management platform via the cloud desktop; The cloud management platform executes the driver synchronization process based on the device information. The driver acquisition request includes the printer's device information, and the driver acquisition request is used to trigger the cloud management platform to execute the driver synchronization process; the driver synchronization process is used for the cloud desktop of the first resource pool to acquire the driver file and perform a printing operation after installation.

2. The method according to claim 1, characterized in that, The cloud server also deploys a second resource pool. The process of executing the driver synchronization procedure through the cloud management platform based on the device information includes: The driver file information of each cloud desktop associated with the first resource pool is obtained through the cloud management platform; the driver file information includes at least the driver version, supported printer models, and storage status. If the driver file information matches the device information, the cloud management platform performs driver synchronization with the resource pool to synchronize the driver file within the first resource pool. If the driver file information does not match the device information, cross-resource pool driver synchronization is performed through the cloud management platform so that the driver file is synchronized from the second resource pool to the first resource pool.

3. The method according to claim 2, characterized in that, When the driver file information matches the device information, the cloud management platform performs driver synchronization with the resource pool to synchronize the driver file within the first resource pool, including: If the driver file information matches the device information, the target cloud desktop storing the driver file is determined through the cloud management platform; A first notification message is sent to the target cloud desktop through the cloud management platform; The cloud management platform sends a second notification message to the cloud desktops in the first resource pool that do not store the driver file. The first notification message is used to instruct the target cloud desktop to upload the driver file to the distributed storage of the first resource pool; the second notification message is used to instruct the cloud desktop that does not store the driver file to download the driver file from the distributed storage and install it.

4. The method according to claim 2, characterized in that, In the event that the driver file information does not match the device information, cross-resource pool driver synchronization is performed through the cloud management platform to synchronize the driver file from the second resource pool to the first resource pool, including: If the driver file information does not match the device information, the target cloud desktop storing the driver file is determined through the cloud management platform; A third notification message is sent to the target cloud desktop through the cloud management platform; The driver file is copied from the distributed storage of the second resource pool to the distributed storage of the first resource pool through the cloud management platform. The cloud management platform sends a fourth notification message to the cloud desktops in the first resource pool that do not store the driver file. The third notification message is used to instruct the target cloud desktop to upload the driver file to the distributed storage of the second resource pool; the fourth notification message is used to instruct the cloud desktop that does not store the driver file to download the driver file from the distributed storage of the first resource pool and install it.

5. The method according to claim 3 or 4, characterized in that, The method further includes: The cloud desktop identifier and address information of the target cloud desktop are obtained through the cloud management platform; The cloud management platform generates either the first notification message or the second notification message based on the cloud desktop identifier and address information and a preset message format. The cloud management platform uses a timed message queue to send either the first notification message or the second notification message to the target cloud desktop.

6. The method according to claim 1, characterized in that, After executing the driver synchronization process based on the device information through the cloud management platform, the method further includes: The cloud management platform generates synchronization-related information, including driver file name, version, source resource pool, target resource pool, synchronization type, synchronization time, and installation result. The synchronization-related information is displayed in the client's interface.

7. The method according to claim 6, characterized in that, The display interface includes a new driver control, a new driver control, and a batch operation control; the method further includes at least one of the following: In response to a trigger operation on the newly added driver control, a new printer driver is added; In response to a trigger operation on the newly added driver control, manage prohibited drivers; In response to a trigger operation on the batch operation control, batch distribution, deletion, and other operations are performed on multiple drivers.

8. A synchronization device for a printer driver, characterized in that, The device includes: The driver query module is used to respond to the cloud desktop where the printer is connected to the first resource pool and query whether the cloud desktop has the driver file corresponding to the printer installed. The driver acquisition module is used to send a driver acquisition request to the cloud management platform through the cloud desktop when the driver file is not installed. The driver synchronization module is used to execute the driver synchronization process based on the device information through the cloud management platform; The driver acquisition request includes the printer's device information, and the driver acquisition request is used to trigger the cloud management platform to execute the driver synchronization process; the driver synchronization process is used for the cloud desktop of the first resource pool to acquire the driver file and perform a printing operation after installation.

9. An electronic device, characterized in that, It includes a processor, a memory, and a program or instructions stored in the memory and executable on the processor, wherein the program or instructions, when executed by the processor, implement the steps of the synchronization method for a printer driver as described in any one of claims 1-7.

10. A readable storage medium, characterized in that, The readable storage medium stores a program or instructions that, when executed by a processor, implement the steps of the synchronization method for a printer driver as described in any one of claims 1-7.

Images