A cloud printing data processing method and system based on mobile terminal local processing
Patent Information
- Application Number
- CN202610924086.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-06-25
- Publication Date
- 2026-08-18
AI Technical Summary
[0005]本发明针对背景技术中存在服务器负载压力极大、打印效率偏低以及交互体验差的问题,提出一种基于移动端本地处理的云打印数据处理方法及系统
[0033] First, regarding the problem of extremely high server load, this invention migrates all high-computing operations such as file conversion, parameter adaptation, and rendering preview to the mobile terminal. The server only undertakes lightweight forwarding and scheduling work, and the CPU and memory usage rate is reduced by more than 85%. High-concurrency printing tasks can be supported without high-configuration hardware, and the costs of hardware procurement, subsequent expansion and maintenance are greatly reduced.
Smart Images

Figure CN122593723A_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of cloud printing data processing technology, and in particular to a cloud printing data processing method and system based on local processing on a mobile device. Background Technology
[0002] The current mainstream cloud printing architecture adopts a server-centralized data processing mode: users upload files to be printed in PDF, DOC, XLS, PPT and other formats to the cloud printing server through APP, WeChat mini program and other means. The server completes the processing such as file parsing, format conversion and printing instruction generation to generate printing data that the printer can recognize, and then sends the final printing data to the terminal printer to execute the printing task.
[0003] For the current mainstream cloud printing architecture: First, the server load is extremely high. In high-concurrency printing scenarios, the server needs to handle the format conversion and computing power of massive files simultaneously, which can easily lead to high CPU / memory usage, response latency, and downtime risks, resulting in high maintenance costs and hardware investment. Second, printing efficiency is low. The file upload and server conversion process takes a long time, especially when processing large files or complex layout documents. The long cycle of printing data delivery results in significant user waiting time, affecting the user experience. Third, the interactive experience is poor. If users are not satisfied with the preview effect and need to modify the configuration parameters, they must re-upload the parameters to the server and wait for the server to reprocess and send back the preview image. This repeated operation is extremely time-consuming and cannot meet the user experience requirements of instant adjustment and fast preview.
[0004] In recent years, the computing power of smartphone hardware has improved significantly. Multi-core CPUs and large-capacity memory have become standard features of smartphones, and mobile processors are powerful enough to efficiently complete routine document parsing and format conversion tasks. Meanwhile, the widespread coverage of 4G / 5G networks in China has significantly improved uplink speeds and enhanced transmission stability, providing reliable network support for uploading converted data from mobile devices. Against this backdrop, the industry's technological bias that only servers can handle print data conversion has been challenged, creating an urgent need for a cloud-based printing data processing solution that can leverage the computing power of mobile terminals and reduce the burden on servers. Summary of the Invention
[0005] This invention addresses the problems of extremely high server load, low printing efficiency, and poor user experience in the background technology by proposing a cloud printing data processing method and system based on local processing on mobile devices.
[0006] To achieve the above objectives, the present invention provides the following technical solution: a cloud printing data processing method based on local processing on a mobile device, comprising the following steps:
[0007] Users select the file to be printed via a mobile app, which automatically identifies the file format type.
[0008] The mobile app uses its built-in hardware computing power to parse documents of recognized format types and renders a print preview screen based on the printing device's capabilities and user-set parameters, allowing the user to confirm whether to print.
[0009] After clicking to confirm printing, the mobile app performs a format conversion locally based on the document content with adapted parameters, converting the general office document into special printing instruction data that the target printing device can directly recognize and execute. The special printing instruction data is the second data format.
[0010] The mobile app compresses and encrypts the generated print instruction data, packages it, and transmits it to the cloud printing server over the network.
[0011] The cloud printing server performs integrity verification, print queue scheduling, and route matching on the received print instruction data packets. It does not perform any format conversion or document parsing operations, and directly sends the verified print instruction data packets to the corresponding target printing device.
[0012] The target printing device receives the instruction and executes the printing directly.
[0013] Preferably, the file to be printed is in a first data format;
[0014] The first data format is a common document format, including PDF, DOC, DOCX, XLS, XLSX, PPT, PPTX, TXT, JPG, and PNG formats;
[0015] The mobile app has multiple built-in document parsing engines that can process PDF, DOC, DOCX, XLS, XLSX, PPT, PPTX, TXT, JPG, and PNG documents.
[0016] The mobile app supports local parameter configuration, layout preview, and document conversion in offline environments. Users can complete the entire configuration and conversion process offline, and then directly upload the print command data to the server once the device is connected to the network.
[0017] Preferably, the step of user confirmation for printing includes: the user instantly views the print preview on the APP; if the user is not satisfied with the preview, they can directly modify the configuration parameters; the APP re-renders and refreshes the preview locally within seconds; if the user is satisfied with the preview, they click to confirm printing.
[0018] Preferably, the print instruction data packet includes a print task ID, a target print device ID, a user identity ID, a user level, an emergency flag, a timestamp of the task being generated by the mobile terminal, the byte length of the print instruction payload, a checksum of the payload data, a data packet protocol version number, an encryption algorithm identifier, a compression algorithm identifier, and encrypted payload data.
[0019] Preferably, the execution process of compressing and encrypting the generated print instruction data and then transmitting it to the cloud print server via the network includes: based on the device capability information of the printer selected by the user, the APP locally converts the original document into a corresponding print instruction binary stream; calculates the check value of the print instruction binary stream; compresses the print instruction binary stream; encrypts the compressed data; assembles the packet header by filling in the print task ID, target print device ID, user identity ID, user level, emergency flag, timestamp of task generation on the mobile terminal, byte length of the print instruction payload, check value of the payload data, data packet protocol version number, encryption algorithm identifier, and compression algorithm identifier; and merges the packet header and the encrypted payload into a complete data packet, which is then uploaded to the cloud print server via HTTPS or other protocols.
[0020] Preferably, the integrity verification includes the following steps:
[0021] The server parses the metadata fields and extracts the byte length of the print command payload, the checksum of the payload data, the encrypted payload data, and the encryption algorithm identifier.
[0022] Compare the actual received data length with the payload byte length declared in the data packet header to see if they are consistent;
[0023] Using a pre-defined algorithm agreed upon with the mobile app, the payload content is not parsed; instead, it is calculated as a binary data stream. The received binary data stream is used to calculate a checksum, which is then compared with the checksum carried in the uploaded data packet.
[0024] Check whether the data packet structure is consistent with the protocol format agreed upon by the server and the APP in advance. The check includes the field order, required fields, and field types.
[0025] If all three items are consistent, the data integrity verification is successful and the data enters the print queue scheduling stage. If any item is inconsistent, the verification fails, and the server immediately returns a retransmission instruction to the mobile APP, carrying the failed task ID. Upon receiving the instruction, the APP automatically re-compresses and encrypts the data and uploads the print instruction data packet.
[0026] To achieve the above objectives, the present invention provides the following technical solution: a cloud printing data processing system based on local processing on a mobile device, comprising a file format recognition module, a print preview module, a print instruction generation module, a print instruction packaging and transmission module, and a lightweight server forwarding module;
[0027] The file format recognition module automatically identifies the format type of the file to be printed selected by the user through the mobile APP;
[0028] The instant print preview module parses the document with the identified format type based on the built-in hardware computing power, and renders and generates a print preview screen based on the device capability information of the printing device and the parameters set by the user, and sends a print option for the user to confirm.
[0029] After the user clicks to confirm printing, the print instruction generation module performs format conversion locally based on the document content with adapted parameters, converting the general office document into special print instruction data that can be directly recognized and executed by the target printing device;
[0030] The print instruction packaging and transmission module compresses and encrypts the generated print instruction data, packages it, and transmits it to the cloud print server via the network.
[0031] The lightweight forwarding module of the server uses the cloud printing server to perform integrity verification, print queue scheduling and route matching on the received print instruction data packets. It does not perform any format conversion or document parsing operations, and directly sends the verified print instruction data packets to the corresponding target printing device to execute the printing task.
[0032] Compared with the prior art, the present invention includes at least one of the following beneficial technical effects:
[0033] First, regarding the problem of extremely high server load, this invention migrates all high-computing operations such as file conversion, parameter adaptation, and rendering preview to the mobile terminal. The server only undertakes lightweight forwarding and scheduling work, and the CPU and memory usage rate is reduced by more than 85%. High-concurrency printing tasks can be supported without high-configuration hardware, and the costs of hardware procurement, subsequent expansion and maintenance are greatly reduced.
[0034] Secondly, regarding the issue of low printing efficiency, this invention simplifies redundant steps such as file upload, server processing, and preview return. The entire process from user configuration to generating print commands is completed locally, avoiding server queuing time and shortening the overall printing task cycle by more than 50%, resulting in faster printing response speed.
[0035] Third, regarding the issue of poor interactive experience, this invention allows users to set parameters such as resolution, layout, and watermark on the APP and then directly render and preview locally without uploading to the server or waiting for a return. The preview effect is presented in seconds, and the system refreshes instantly after parameter adjustments. This completely eliminates the two-way transmission of preview data between the server and the APP, solving the problem of preview lag and failure under weak network conditions, and greatly improving the user interactive experience. Attached Figure Description
[0036] Figure 1 A flowchart illustrating the steps of a cloud printing data processing method based on local processing on a mobile device;
[0037] Figure 2 This is a module connection diagram for a cloud printing data processing system based on local processing on a mobile device. Detailed Implementation
[0038] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.
[0039] like Figure 1 As shown, this embodiment provides a cloud printing data processing method based on local processing on a mobile device, including the following steps:
[0040] Users select the file to be printed via a mobile app, which automatically identifies the file format type.
[0041] The mobile app uses its built-in hardware computing power to parse documents of recognized format types and renders a print preview screen based on the printing device's capabilities and user-set parameters, allowing the user to confirm whether to print.
[0042] After clicking to confirm printing, the mobile app performs a format conversion locally based on the document content with adapted parameters, converting the general office document into special printing instruction data that the target printing device can directly recognize and execute. The special printing instruction data is the second data format.
[0043] The mobile app compresses and encrypts the generated print instruction data, packages it, and transmits it to the cloud printing server over the network.
[0044] The cloud printing server performs integrity verification, print queue scheduling, and route matching on the received print instruction data packets. It does not perform any format conversion or document parsing operations, and directly sends the verified print instruction data packets to the corresponding target printing device.
[0045] The target printing device receives the instruction and executes the printing directly.
[0046] Furthermore, the file to be printed is in a first data format;
[0047] The first data format is a common document format, including PDF, DOC, DOCX, XLS, XLSX, PPT, PPTX, TXT, JPG, and PNG formats;
[0048] The mobile app has multiple built-in document parsing engines that can process PDF, DOC, DOCX, XLS, XLSX, PPT, PPTX, TXT, JPG, and PNG documents.
[0049] The mobile app supports local parameter configuration, layout preview, and document conversion in offline environments. Users can complete the entire configuration and conversion process offline, and then directly upload the print command data to the server once the device is connected to the network.
[0050] In this embodiment, it should be specifically noted that the mobile terminal includes, but is not limited to, mobile devices such as mobile phones, tablets, and portable smart terminals.
[0051] In this embodiment, it should be specifically noted that the device capability information of the printing device includes, but is not limited to, the supported page description language type (e.g., the instruction format that the printer can recognize, such as PCL, PostScript, etc.), resolution (the maximum or default printing resolution supported by the printer, such as 600dpi, 1200dpi), and paper size (the paper specifications supported by the printer, such as A4, A3, Letter, etc.).
[0052] In this embodiment, it should be specifically noted that the parameters set by the user include, but are not limited to, resolution (such as print clarity), paper size (such as A4, B5, etc.), layout splicing (such as merging multiple pages, scaling, multi-page imposition, etc.), and watermark (adding text or image watermarks).
[0053] Furthermore, the user confirmation for printing includes: the user viewing the print preview in real time on the APP; if the user is not satisfied with the preview, they can directly modify the configuration parameters; the APP re-renders and refreshes the preview locally within seconds; if the user is satisfied with the preview, they can click to confirm printing.
[0054] Furthermore, the print instruction data packet includes a print task ID, a target print device ID, a user identity ID, a user level, an emergency flag, a timestamp indicating that the task was generated by the mobile terminal, the byte length of the print instruction payload, a checksum of the payload data, a data packet protocol version number, an encryption algorithm identifier, a compression algorithm identifier, and the encrypted payload data.
[0055] Furthermore, the execution process of compressing and encrypting the generated print instruction data before transmitting it to the cloud print server over the network includes: based on the device capability information of the printer selected by the user, the APP locally converts the original document into a corresponding print instruction binary stream; calculates the checksum of the print instruction binary stream; compresses the print instruction binary stream; encrypts the compressed data; assembles the packet header by filling in the print task ID, target print device ID, user identity ID, user level, emergency flag, timestamp of task generation on the mobile terminal, byte length of the print instruction payload, checksum of the payload data, data packet protocol version number, encryption algorithm identifier, and compression algorithm identifier; and merges the packet header and the encrypted payload into a complete data packet, which is then uploaded to the cloud print server via HTTPS or other protocols.
[0056] Furthermore, the integrity verification includes the following steps:
[0057] The server parses the metadata fields and extracts the byte length of the print command payload, the checksum of the payload data, the encrypted payload data, and the encryption algorithm identifier.
[0058] Compare the actual received data length with the payload byte length declared in the data packet header to see if they are consistent;
[0059] Using a pre-defined algorithm agreed upon with the mobile app, the payload content is not parsed; instead, it is calculated as a binary data stream. The received binary data stream is used to calculate a checksum, which is then compared with the checksum carried in the uploaded data packet.
[0060] Check whether the data packet structure is consistent with the protocol format agreed upon by the server and the APP in advance. The check includes the field order, required fields, and field types.
[0061] If all three items are consistent, the data integrity verification is successful and the data enters the print queue scheduling stage. If any item is inconsistent, the verification fails, and the server immediately returns a retransmission instruction to the mobile APP, carrying the failed task ID. Upon receiving the instruction, the APP automatically re-compresses and encrypts the data and uploads the print instruction data packet.
[0062] In this embodiment, it should be specifically noted that the printing queue scheduling includes the following steps:
[0063] After the integrity verification is passed, the server extracts the scheduling-related fields, including the print task ID, user level (normal, VIP, and enterprise administrator), emergency flag (0=normal, 1=emergency), timestamp of the task generated by the mobile device, and target printing device ID.
[0064] Priority is determined based on user level and task urgency. If the urgency flag is 1, the priority is increased by 1. If the user level is VIP, the priority is increased by 2. If the user level is enterprise administrator, the priority is increased by 1. If the user level is ordinary, the priority is increased by 0. The original priority is 1 by default. After the priority is added, the priority is increased.
[0065] The task is inserted into the device-specific queue corresponding to the target printing device ID. The print tasks are arranged in descending order of priority within the queue. If the priority is the same, the print tasks are arranged in descending order of the timestamp of the task generated by the mobile device.
[0066] For each target printing device, the server runs an independent queue scheduler that continuously retrieves the highest priority task from the head of the queue. If the printer is idle or the number of tasks does not exceed the device's buffer capacity, the routing matching and forwarding process begins immediately. If the printer is busy, the task continues to wait in the queue.
[0067] In this embodiment, it should be specifically noted that the route matching includes the following steps:
[0068] Read the target printing device ID from the data packet that has passed the checksum and scheduling;
[0069] The system queries the device registry. If the device is online, it proceeds to the forwarding stage. If the device is offline or faulty, the server returns an error status to the app. After the user confirms and waits, the task is temporarily stored. It will be retried after the device comes online. After the user confirms and stops, the task is deleted.
[0070] Based on the protocol type of the target printing device, the encrypted payload data is encapsulated into the corresponding network data packet format, and the printing command is sent to the target printing device through the established network connection.
[0071] like Figure 2 As shown, this embodiment provides a cloud printing data processing system based on local processing on a mobile device, including a file format recognition module, a real-time print preview module, a print instruction generation module, a print instruction packaging and transmission module, and a lightweight server forwarding module;
[0072] The file format recognition module automatically identifies the format type of the file to be printed selected by the user through the mobile APP;
[0073] The instant print preview module parses the document with the identified format type based on the built-in hardware computing power, and renders and generates a print preview screen based on the device capability information of the printing device and the parameters set by the user, and sends a print option for the user to confirm.
[0074] After the user clicks to confirm printing, the print instruction generation module performs format conversion locally based on the document content with adapted parameters, converting the general office document into special print instruction data that can be directly recognized and executed by the target printing device;
[0075] The print instruction packaging and transmission module compresses and encrypts the generated print instruction data, packages it, and transmits it to the cloud print server via the network.
[0076] The lightweight forwarding module of the server uses the cloud printing server to perform integrity verification, print queue scheduling and route matching on the received print instruction data packets. It does not perform any format conversion or document parsing operations, and directly sends the verified print instruction data packets to the corresponding target printing device to execute the printing task.
[0077] In this embodiment, it should be specifically noted that a cloud printing data processing system based on local processing on a mobile device also includes a database, which is used to store data information of all modules in the system. For a cloud printing data processing system based on local processing on a mobile device, the file format recognition module, the real-time print preview module, the print instruction generation module, the print instruction packaging and transmission module, and the server lightweight forwarding module are connected sequentially, and all modules in the system are connected to the database.
[0078] In conclusion, the above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the protection scope of the present invention.
Claims
1. A cloud printing data processing method based on local processing on a mobile device, characterized in that, Includes the following steps: Users select the file to be printed via a mobile app, which automatically identifies the file format type. The mobile app uses its built-in hardware computing power to parse documents of recognized format types and renders a print preview screen based on the printing device's capabilities and user-set parameters, allowing the user to confirm whether to print. After clicking to confirm printing, the mobile app performs a format conversion locally based on the document content with adapted parameters, converting the general office document into special printing instruction data that the target printing device can directly recognize and execute. The special printing instruction data is the second data format. The mobile app compresses and encrypts the generated print instruction data, packages it, and transmits it to the cloud printing server over the network. The cloud printing server performs integrity verification, print queue scheduling, and route matching on the received print instruction data packets. It does not perform any format conversion or document parsing operations, and directly sends the verified print instruction data packets to the corresponding target printing device. The target printing device receives the instruction and executes the printing directly.
2. The cloud printing data processing method based on local processing on a mobile device according to claim 1, characterized in that, The file to be printed is in the first data format; The first data format is a common document format, including PDF, DOC, DOCX, XLS, XLSX, PPT, PPTX, TXT, JPG, and PNG formats; The mobile app has multiple built-in document parsing engines that can process PDF, DOC, DOCX, XLS, XLSX, PPT, PPTX, TXT, JPG, and PNG documents. The mobile app supports local parameter configuration, layout preview, and document conversion in offline environments. Users can complete the entire configuration and conversion process offline, and then directly upload the print command data to the server once the device is connected to the network.
3. The cloud printing data processing method based on local processing on a mobile device according to claim 1, characterized in that, The process of having the user confirm whether to print includes: the user can view the print preview in real time on the APP; if the user is not satisfied with the preview, they can directly modify the configuration parameters; the APP will re-render and refresh the preview locally within seconds; if the user is satisfied with the preview, they can click to confirm printing.
4. The cloud printing data processing method based on local processing on a mobile device according to claim 1, characterized in that, The print instruction data packet includes a print task ID, a target print device ID, a user identity ID, a user level, an emergency flag, a timestamp indicating that the task was generated by the mobile device, the byte length of the print instruction payload, a checksum of the payload data, a data packet protocol version number, an encryption algorithm identifier, a compression algorithm identifier, and the encrypted payload data.
5. The cloud printing data processing method based on local processing on a mobile device according to claim 1, characterized in that, The process of compressing and encrypting the generated print instruction data before transmitting it to the cloud print server over the network includes: based on the device capability information of the printer selected by the user, the APP locally converts the original document into a corresponding print instruction binary stream; calculates the checksum of the print instruction binary stream; compresses the print instruction binary stream; encrypts the compressed data; assembles the packet header by filling in the print task ID, target print device ID, user ID, user level, emergency flag, timestamp of task generation on the mobile device, byte length of the print instruction payload, checksum of the payload data, data packet protocol version number, encryption algorithm identifier, and compression algorithm identifier; and merges the packet header and the encrypted payload into a complete data packet, which is then uploaded to the cloud print server via HTTPS or other protocols.
6. The cloud printing data processing method based on local processing on a mobile device according to claim 1, characterized in that, The integrity verification includes the following steps: The server parses the metadata fields and extracts the byte length of the print command payload, the checksum of the payload data, the encrypted payload data, and the encryption algorithm identifier. Compare the actual received data length with the payload byte length declared in the data packet header to see if they are consistent; Using a pre-defined algorithm agreed upon with the mobile app, the payload content is not parsed; instead, it is calculated as a binary data stream. The received binary data stream is used to calculate a checksum, which is then compared with the checksum carried in the uploaded data packet. Check whether the data packet structure is consistent with the protocol format agreed upon by the server and the APP in advance. The check includes the field order, required fields, and field types. If all three items are consistent, the data integrity verification is successful and the data enters the print queue scheduling stage. If any item is inconsistent, the verification fails, and the server immediately returns a retransmission instruction to the mobile APP, carrying the failed task ID. Upon receiving the instruction, the APP automatically re-compresses and encrypts the data and uploads the print instruction data packet.
7. A cloud printing data processing system based on local processing on a mobile device, employing the cloud printing data processing method based on local processing on a mobile device as described in any one of claims 1-6, characterized in that, It includes a file format recognition module, a print preview module, a print command generation module, a print command packaging and transmission module, and a lightweight server forwarding module; The file format recognition module automatically identifies the format type of the file to be printed selected by the user through the mobile APP; The instant print preview module parses the document with the identified format type based on the built-in hardware computing power, and renders and generates a print preview screen based on the device capability information of the printing device and the parameters set by the user, and sends a print option for the user to confirm. After the user clicks to confirm printing, the print instruction generation module performs format conversion locally based on the document content with adapted parameters, converting the general office document into special print instruction data that can be directly recognized and executed by the target printing device; The print instruction packaging and transmission module compresses and encrypts the generated print instruction data, packages it, and transmits it to the cloud print server via the network. The lightweight forwarding module of the server uses the cloud printing server to perform integrity verification, print queue scheduling and route matching on the received print instruction data packets. It does not perform any format conversion or document parsing operations, and directly sends the verified print instruction data packets to the corresponding target printing device to execute the printing task.