Printing control method and device, system, equipment, storage medium and product

Abstract

The invention relates to the technical field of image forming devices, and particularly provides a printing control method and device, a system, equipment, a storage medium and a product. The method comprises the following steps: receiving a correction request, wherein the correction request is used for requesting to execute correction processing on a first task submitted to print; then, based on a hardware working state, determining a correctable range of the first task; therefore, based on the user operation information of the correctable range, generating a reconstruction queue of the first task; and further, on the basis of the reconstruction queue, continuing to execute the first task. In conclusion, according to the technical scheme provided by the invention, submitted but unprocessed tasks can be flexibly corrected, the implementation mode is simple and convenient, the efficiency is relatively high, and resource waste can be avoided.

Description

Technical Field

[0001] This application relates to the field of image forming apparatus technology, and in particular to a printing control method and apparatus, system, device, storage medium and product. Background Technology

[0002] In modern office and business printing scenarios, users often need to perform highly complex printing tasks (such as 100 pages x 100 copies of a meeting manual). In related technologies, once a print job is submitted, partial modifications are not possible. Users can only cancel the entire print job, correct the errors, and then resubmit it. For example, regarding deletion, if an error is discovered midway through printing (such as an error starting from page 51 of a document) and the erroneous pages need to be deleted, only complete job cancellation or continuing the erroneous output is supported; it's not possible to precisely delete specific pages within a specific number of copies (such as pages 51-100 of copies 51-100). Another example: if the original plan was to print 100 copies, and 30 copies have already been printed, and the plan is changed to 50 copies, the user can only wait for the current copy to finish printing, cancel the entire job, and then reprint the remaining 20 copies—a cumbersome and time-consuming process.

[0003] In summary, the existing technologies can only reset the entire job for submitted tasks, which is cumbersome, inflexible, and results in a significant waste of resources and time. Summary of the Invention This application is made in view of the above-mentioned problems. This application provides a printing control method and apparatus, system, device, storage medium, and product.

[0004] According to one aspect of this application, a printing control method is provided, comprising: Receive a correction request, the correction request being used to request correction processing to the first task that has been submitted for printing; Based on the hardware operating status, determine the correctable range of the first task; Based on the user operation information within the correctable range, a reconstruction queue for the first task is generated; Based on the reconstructed queue, continue executing the first task.

[0005] According to another aspect of this application, a printing control device is provided, comprising: A communication unit is configured to receive a correction request, the correction request being used to request correction processing of a first task that has been submitted for printing; The processing unit is used to determine the correctable range of the first task based on the hardware operating status. The processing unit is also configured to generate a reconstruction queue for the first task based on user operation information for the correctable range; The processing unit is also configured to continue executing the first task based on the reconstructed queue.

[0006] According to another aspect of this application, a printing control system is provided, comprising: The control layer is used to perform the methods described in any embodiment of this application; The hardware layer is used to perform printing tasks; The interaction layer is used to realize human-computer interaction between the control layer and the user.

[0007] According to another aspect of this application, an image forming apparatus is provided, comprising: main body; The printing control system as described in any embodiment of this application.

[0008] According to another aspect of this application, an electronic device is provided, including a memory, a processor, and a computer program stored in the memory, wherein the processor executes the computer program to implement the method described in any of the above embodiments.

[0009] According to another aspect of this application, a computer-readable storage medium is provided that stores a computer program / instructions thereon, which, when executed by a processor, implements the methods described in any of the above embodiments.

[0010] According to another aspect of this application, a computer program product is provided, including a computer program / instructions that, when executed by a processor, implement the methods described in any of the above embodiments.

[0011] As will be described in detail below, a printing control method, apparatus, system, device, storage medium, and product according to embodiments of this application are disclosed. This application allows a user to modify a submitted first task (e.g., a task in progress). Upon receiving a modification request, the modifiable range of the first task can be determined based on the hardware operating status. Through human-computer interaction, the user can precisely modify the unprocessed portion of the first task within the modifiable range. This application can generate a reconstruction queue based on user operation information and execute the reconstruction queue. In this process, the user can precisely modify the unprinted portion without canceling the entire job. Compared to a complete job reset solution, the technical solution provided by this application can flexibly modify submitted but unprocessed tasks, is simple and convenient to implement, highly efficient, and helps avoid resource waste.

[0012] It should be understood that both the foregoing general description and the following detailed description are exemplary and intended to provide further illustration of the claimed technology. Attached Figure Description

[0013] The above and other objects, features, and advantages of this application will become more apparent from the more detailed description of the embodiments of this application in conjunction with the accompanying drawings. The accompanying drawings are used to provide a further understanding of the embodiments of this application and form part of the specification. They are used together with the embodiments of this application to explain this application and do not constitute a limitation thereof. In the accompanying drawings, the same reference numerals generally represent the same components or steps.

[0014] Figure 1 This is a schematic diagram of the architecture of an image forming apparatus provided in an embodiment of this application.

[0015] Figure 2 This is a schematic diagram of the architecture of a printing control system provided in an embodiment of this application.

[0016] Figure 3 This is a flowchart illustrating a printing control method provided in an embodiment of this application.

[0017] Figure 4 This is a flowchart illustrating a deletion-based printing control method provided in an embodiment of this application.

[0018] Figure 5 This is a schematic diagram of a gradual shutdown provided in an embodiment of this application.

[0019] Figure 6 This is a flowchart illustrating another printing control method provided in an embodiment of this application.

[0020] Figure 7 This is a flowchart illustrating another printing control method provided in an embodiment of this application.

[0021] Figure 8 This is a structural block diagram of a printing control device provided in an embodiment of this application.

[0022] Figure 9 This is a hardware block diagram of an electronic device provided in an embodiment of this application.

[0023] Figure 10 This is a schematic diagram of a computer-readable storage medium provided in an embodiment of this application. Detailed Implementation

[0024] To make the objectives, technical solutions, and advantages of this application more apparent, exemplary embodiments according to this application will be described in detail below with reference to the accompanying drawings. Obviously, the described embodiments are merely some embodiments of this application, and not all embodiments of this application. It should be understood that this application is not limited to the exemplary embodiments described herein.

[0025] To address the issues of resource waste and cumbersome operation caused by the requirement to reset the entire submitted job in related technologies, this application provides a novel design concept: enabling users to modify submitted jobs. Through human-computer interaction, users can initiate modification requests for submitted jobs and fine-tune parts not processed at the hardware layer. Based on this, a reconstruction queue is generated and executed, achieving "surgical" local modification without resetting the entire job. This avoids resource waste, is simple and convenient to operate, and is highly efficient and flexible.

[0026] The following is a detailed explanation.

[0027] This application embodiment is applied to the scenario where an image forming apparatus performs a printing job. There is no limit to the printing volume. It can be a highly complex batch printing task or a simple printing task of a single document. This solution is applicable to both.

[0028] This application provides a printing control method, a printing control device, a printing control system, and an image forming apparatus. For ease of understanding, the relationship between them is briefly described first.

[0029] An image forming system generally includes an image forming apparatus and consumables. The image forming apparatus is the part of the image forming system that performs the image forming operation, while consumables are replaceable parts within the system. For example, when the image forming apparatus is an inkjet printer, laser printer, 3D printer, label printer, or dot matrix printer, the corresponding consumables are ink cartridges, toner cartridges, drum units, toner tubes, ribbon cartridges, etc. Furthermore, consumables can also be other easily damaged and replaceable components, parts, or units within the image forming apparatus (such as paper trays), which also fall under the technical solution corresponding to the consumables protected in this application.

[0030] Please refer to Figure 1 , Figure 1 This is a schematic diagram of the architecture of an image forming apparatus provided in an embodiment of this application. Figure 1 As shown, the image forming apparatus 100 includes a main body 110 and a print control system 120. The print control system 120 is used to implement print control of the image forming apparatus 100, that is, to execute the print control method in any of the embodiments provided later in this application.

[0031] Further, please refer to Figure 2 , Figure 2 This is a schematic diagram of the architecture of a printing control system provided in an embodiment of this application, as shown below. Figure 2 As shown, the printing control system 120 includes: The control layer 121 is used to execute the printing control method in any of the embodiments provided below in this application; Hardware layer 122 is used to perform printing tasks; The interaction layer 123 is used to realize human-computer interaction between the control layer 121 and the user.

[0032] Specifically, the interaction layer 123, also known as the user interface layer, is used to implement human-computer interaction. It can be any human-computer interaction device, including but not limited to one or more of the following: touch panels, physical buttons and / or virtual buttons, external touch control devices (e.g., mice, remote controls, voice control devices, etc.), user terminals (e.g., mobile phones, computers, etc.). This application does not exhaustively list these possibilities, nor does it impose any specific limitations. In one exemplary embodiment, the user can remotely control a printing task via a mobile phone, such as issuing a task, canceling a task, or modifying one or more of the following: the printing control method provided in this application. In this application, the interaction layer 123 can be used to receive correction requests initiated by the user, output the correctable range to the user, and obtain user operation information regarding the correctable range. These will be specifically described later in conjunction with the printing control method provided in this application.

[0033] Hardware layer 122, also known as the mechanical layer, is used to execute specific tasks. Hardware layer 122 is involved in the management and maintenance of various mechanical components. Hardware layer 122 can interact with control layer 121 to respond to control commands from control layer 121 (such as, but not limited to, suspend and resume commands, as described below) to control the operation or shutdown of various mechanical components. It can also exchange information with control layer 121, such as providing feedback on the hardware operating status. Therefore, control layer 121 can obtain the hardware operating status through interaction with hardware layer 122, thereby knowing which task is currently being executed and at which stage. It should be understood that the hardware operating status describes the current operating state of the hardware. For example, hardware layer 122 can record the working status of each paper feed sensor, including: paper out sensor, paper feed sensor, alignment sensor, jam sensor, and discharge sensor. The paper out sensor is installed inside the paper tray to detect whether there is paper in the tray. When there is no paper, it sends a signal to the main control board, triggering a "paper out" prompt and pausing printing. The paper feed sensor is located between the paper tray exit and the paper feed rollers, serving as the starting detection point for paper feeding. It detects whether the paper has been successfully picked up by the paper feed rollers and fed into the path, preventing idling or multiple pages from being fed. The alignment sensor is located at the front end of the secondary conveyor rollers and is a core positioning component. It detects the arrival time of the paper tip and synchronously triggers the printing engine to start printing, ensuring that the content is aligned with the paper edge. The discharge sensor is installed inside the paper exit, confirming that the paper has been completely discharged, providing a printing completion signal, and allowing the next page to be fed. In one exemplary embodiment, the hardware operating states involved in this application include at least the paper feed sensor state, which can be used to indicate the current passing position of the medium, thereby determining the correctable range of the job task, as explained below. In addition, other hardware operating states may exist, such as the print engine state, the fuser unit state, etc., which will not be exhaustive.

[0034] For example, the hardware involved in the image forming apparatus that can perform the job task (taking a printing engine as an example) may include, but is not limited to, a developing assembly, a photosensitive drum assembly, a transfer assembly, a fixing assembly, and an ejection assembly. Specifically, the paper to be printed moves in the paper feeding direction via a paper feed sensor, passing sequentially through the photosensitive drum assembly, the developing assembly, the transfer assembly, the fixing assembly, and the ejection assembly to complete the printing. The photosensitive drum assembly is used to generate an electrostatic latent image. Specifically, when the printer receives a print signal, the photosensitive drum assembly starts first. The charging roller evenly applies a negative charge to the surface of the photosensitive drum, making the entire drum surface covered with electrostatic charge of the same potential. Then, the laser beam precisely scans the surface of the photosensitive drum according to the digital signal of the print content. The area irradiated by the laser loses its charge, while the unirradiated area retains the negative charge, ultimately forming an invisible electrostatic latent image on the photosensitive drum that is completely consistent with the print content. The developing assembly is in close contact with the photosensitive drum assembly. Its internal developing roller carries pre-charged toner. Due to the electrostatic attraction between the toner and the unexposed areas of the electrostatic latent image on the photosensitive drum, the developing roller precisely adsorbs the toner onto the latent image of the photosensitive drum. Like positioning, the originally invisible electrostatic latent image is filled with toner and transformed into a visible toner image. When the paper is fed between the photosensitive drum and the transfer roller, the transfer assembly begins to work. The transfer roller releases a positive charge, and the attraction of the positive charge is greater than the electrostatic attraction of the photosensitive drum to the toner, pulling the toner image off the drum surface. At the same time, the transfer roller and the photosensitive drum squeeze each other, tightly clamping the paper in the middle, ensuring that the toner image is transferred completely and without deviation to the paper surface. Then, the paper with the loose toner image is fed into the fixing assembly. The upper and lower rollers of the fixing assembly provide high temperature and high pressure, respectively. The high temperature melts the resin component in the toner, making it viscous, while the high pressure compacts the molten toner, allowing it to penetrate into the fiber gaps of the paper. After the paper passes through the fixing roller, the temperature cools rapidly, the molten resin solidifies, and the toner is permanently fixed on the paper, ultimately forming a clear and durable printed product. Then, the paper is ejected from the printer by the ejection assembly. Further details are omitted here.

[0035] The control layer 121, also known as the core control layer, engine layer, control engine, etc., is used to realize the overall control of the image forming apparatus, and may include, but is not limited to, the printing control method provided in any of the embodiments described below. It should be understood that, in addition to the printing control method provided in this application, the control layer 121 may also have other control and management capabilities, which are not particularly limited and will not be described in detail.

[0036] In this application, the control layer 121 can communicate with the interaction layer 123 and the hardware layer 122 to achieve information interaction. For example, in this embodiment, the control layer 121 can be used to receive correction requests transmitted by the interaction layer 123, and can also transmit the correctable range to the interaction layer 123 to be displayed to the user or to obtain user operation information. The control layer 121 can also be used to query the hardware working status from the hardware layer 122, and can also issue job instructions or reconstruct queues to the hardware layer 122, as will be described in detail later.

[0037] This application provides a printing control method.

[0038] Please refer to Figure 3 , Figure 3 This is a flowchart illustrating a printing control method provided in an embodiment of this application. Figure 3 As shown, the method includes: S302, Receive a correction request, which is used to request correction processing for the first task that has been submitted for printing.

[0039] The first task can be any task that has been submitted for printing. This application does not restrict its current processing status. The first task can be a task that is currently being processed for printing, or a task that has been submitted to the printing queue and is currently being queued in the printing queue but has not yet started execution.

[0040] Furthermore, this application does not impose mandatory restrictions on the triggering method of the correction request. For example, users can initiate a correction request directly on the printer's touch panel, or they can initiate a correction request remotely via wireless communication through devices such as mobile phones, laptops, and computers, which will not be elaborated further.

[0041] In this embodiment, a correction request can also be called a modification request. The correction processing (or correction processing method, modification method) involved in the correction request can include, but is not limited to, one or more of the following: deletion, insertion (or addition), and editing. For example, in one embodiment of this application, a user can be allowed to perform deletion processing on the unprocessed part of a submitted job task, such as deleting pages that have not been printed, or deleting excess copies that have not been printed. In another possible embodiment, a user can also be allowed to perform processing on the unprocessed part of a submitted job task other than deletion, such as inserting pages, editing page content, or one or more other processing methods. This will be explained in detail later. It should be understood that deletion processing is more common in real-world scenarios. For example, as described in the background art, a user may need to delete some pages or some copies of a submitted print job.

[0042] S304 determines the correctable range of the first task based on the hardware operating status.

[0043] In this embodiment of the application, the hardware working state is at least used to indicate the current execution state of the first task. For example, it indicates whether the first task has started execution, and if it has started execution, it indicates which page it is currently executing on.

[0044] In this embodiment, the correctable range is the portion of the first task that has not yet been printed. If the first task is in progress, the correctable range for the first task is the area after the current page that enters the paper feed sensor (excluding the current page). As mentioned earlier, the paper entering the paper feed sensor means the paper has left the paper tray. Therefore, all pages before that page (including the current page) have been processed, and modifications to the printed pages by the user are meaningless. However, pages after that page (excluding the current page) have not yet been printed. This unprinted portion is the correctable range provided to the user in this application, allowing the user to correct the unprinted portion. If the first task has not yet started processing, the entire range of the first task is the correctable range, allowing the user to make fine-tuning adjustments within the entire range of the first task.

[0045] For example, the correctable range involved in the embodiments of this application may include, but is not limited to, at least one of the following: page number range and number of copies range. The page number range may be one page or more pages, and the number of copies range may be one or more copies; the correctable range is related to the current execution state of the first task and changes with the current execution state. This application allows users to dynamically correct the unprocessed portion of the first task at the page number level and / or the number of copies level. Page number level correction and number of copies level correction may be used independently or in combination.

[0046] In some embodiments, only page-level corrections are allowed, meaning the correction scope covers all pages after the currently processed page (excluding the current page). In this case, page-level corrections can apply only to the current document, or by default to all unprocessed documents, depending on a custom preset or determined based on user operation information.

[0047] In some embodiments, users may be allowed to make corrections only at the copy level, meaning the scope of correction includes all copies after the current copy being processed (excluding the current copy). In this case, users cannot correct the document currently being printed that year; they can only delete, add, or edit all unprocessed copies after the current copy, and cannot make page-level corrections.

[0048] Some embodiments also allow users to perform page-level and copy-level corrections, which is more flexible and better meets users' personalized needs. For example, if the first task is a printing task of N copies of M pages, and this task is in progress, the current processing level can be determined at least by the paper feed sensor status, up to page m of the nth copy. Therefore, the correctable range for this first task is: page (m+1) of the nth copy to page M, and the entire page number range from the (n+1)th copy to the Nth copy. Where n is less than N, m is less than M, and M, N, m, and n are all integers.

[0049] S306, Based on user operation information within the correctable range, generate a reconstruction queue for the first task.

[0050] User operation information can be obtained through the interaction layer 123, and can be specifically used to indicate the user's correction intentions. In an exemplary embodiment, the user operation information can be used to indicate the following: correction object information and correction method. The correction object information indicates which task objects (pages and / or copies) the user intends to delete, insert, or edit in the first task, and the correction method indicates how the user intends to implement the correction; for example, the correction method can be batch processing or single processing, etc. This will be explained in detail later. It is understood that based on the correction object information and the correction method, the user's intention can be specifically determined.

[0051] Based on the user's operation information, the task queue corresponding to the correctable range of the first task no longer matches the task queue after the user's intended correction. Therefore, this application also reconstructs the task queue of the first task to generate a reconstructed queue. The reconstructed queue is adapted to the corrected first task.

[0052] The task queue reconstruction method is related to user operation information. Based on the user operation information, the corrected task objects (e.g., pages, copies) are determined, and these corrected task objects are rearranged to form a new task queue, thus obtaining the reconstruction queue for the first task. For example, if the user operation information includes correction object information and correction method, then during this step, the reconstruction queue for the first task can be generated based on the correctable correction object information and correction method. The correction object information and correction method can then be used to indicate the corrected task objects.

[0053] Specifically, the task objects (pages, copies) in the refactoring queue and the task queue corresponding to the correctable range of the first task differ at least partially. For example, if the first task is a 50-copy print job, and 20 copies have already been processed, and the user corrects the remaining 30 copies to 10, then the task queue corresponding to the correctable range of the first task contains 30 task objects, while the refactoring queue only contains 10 task objects; they are not entirely the same. As another example, if the first task is a 100-page print job, and page 50 has already been processed, and the user corrects the unprocessed pages from 51 to 100, inserting one page after page 71, then the task objects in the task queue corresponding to the correctable range of the first task are the original pages 51 to 100, while the task objects in the refactoring queue are: the original pages 51 to 71, the inserted page, and pages 72 to 100. Of course, in some possible embodiments, the user's correction method may also be to delete the entire correctable range. In this case, there is no need to generate a reconstruction queue. Alternatively, it can be understood as reconstructing the task queue corresponding to the correctable range of the first task to be empty, which no longer contains any task objects.

[0054] In this embodiment of the application, generating the reconstruction queue of the first task is actually generating the reconstruction queue of the task queue corresponding to the correctable range of the first task. That is, the reconstruction queue is regenerated for the task queue corresponding to the correctable range of the first task.

[0055] Furthermore, it should be noted that if the first task is a partial task in the image forming apparatus, then the task queue in the image forming apparatus (referred to as the overall task queue for ease of distinction) includes not only the partial task queue corresponding to the first task, but also partial task queues of other tasks. In this case, the partial task queue in the overall task queue corresponding to the correctable range of the first task can be reconstructed. In this case, the reconstructed queue is the partial task queue in the overall task queue corresponding to the correctable range of the first task. Alternatively, in other embodiments, the entire overall task queue can also be reconstructed, which will not be elaborated further.

[0056] S308, based on the reconstructed queue, continues to execute the first task.

[0057] As described above, the reconstruction queue represents the unexecuted portion of the first task. After generating the reconstruction queue, executing the queue directly allows the first task to continue, i.e., continuing with the corrected version of the first task. Specifically, the control layer 121 can send the reconstruction queue (or, the reconstruction queue along with indication information / instructions) to the hardware layer 122, instructing the hardware layer 122 to execute subsequent tasks based on the reconstruction queue. Furthermore, if the reconstruction queue is empty, the control layer 121 can still send the reconstruction queue to the hardware layer 122. Upon receiving an empty task queue, the hardware layer 122 need not continue execution; it can simply halt or continue executing the next task.

[0058] In summary, this application allows users to modify a submitted first task (e.g., a task in progress). Upon receiving a modification request, the modifiable range of the first task can be determined based on the hardware's operating status. Through human-computer interaction, users can precisely modify the unprocessed portion of the first task within this modifiable range. This application can generate and execute a reconstruction queue based on user operation information. During this process, users can precisely modify the unprinted portion without canceling the entire job. Compared to a complete job reset, the technical solution provided by this application allows for flexible modification of submitted but unprocessed tasks. It is simple, convenient, and efficient, helping to avoid resource waste.

[0059] In addition, in one exemplary embodiment of this application, after receiving a correction request, the method further includes: verifying the legality of the correction request; the legality includes at least one of the following: the requester's identity is legal, and the first task matches; if the correction request is illegal, a prompt message is output.

[0060] The correction request must include at least the task identifier (JobID) of the first task. Based on this task identifier, the controller can determine whether the task indicated by the correction request is a valid task. In a further embodiment, the task identifier can also be used to verify whether the task is a correctable task (for example, if the task has already completed printing, it would be a case of task mismatch).

[0061] In another embodiment, the correction request may also carry a requester's identity identifier. Based on this identifier, the control layer 121 can verify its validity. In some embodiments, only the initiator of the first task has the authority to correct the task; therefore, if the identifier matches the initiator's identifier, the requester's identity is valid; otherwise, if they do not match, the identity is invalid. Alternatively, in some embodiments, user correction permissions can be preset. For example, some users may have correction permissions for all tasks. In this case, the requester's identity identifier needs to be compared with a preset set of user identifiers with task correction permissions. If the requester's identity identifier is any one of the identifiers in this set, the requester's identity is valid; otherwise, it is invalid. The above identity verification schemes can be used independently or in combination, and will not be elaborated further.

[0062] It should be understood that if the correction request is valid, the correction process can be performed according to the printing control method of any embodiment provided in this application. Specifically, if the correction request is valid, the control layer 121 can also generate a correction session identifier (i.e., correction session ID), record the operation log, interrupt the current job queue processing thread of the first task, and then enter the ready state to execute the correction method.

[0063] Furthermore, this application does not impose any special restrictions on the output message in the event of verification failure. This message is specifically used to inform the requesting party that verification has failed. For example, the message could be an error code, such as 401 / 404. Alternatively, the message could be text content such as: "The verification request failed; please check and resubmit (this is just an example), and will not be elaborated further."

[0064] As mentioned above, this application allows users to precisely correct unprocessed parts of submitted jobs. Correction methods may include, but are not limited to, deletion, insertion, editing, or one or more other methods. In specific implementation, the correctable range can be output through the interaction layer 123, allowing users to perform corrections within that range.

[0065] In one exemplary embodiment, prior to S306, the method may further include: outputting a correctable range and obtaining user operation information for the correctable range. This part of the processing can be implemented through the interaction layer 123.

[0066] Specifically, there are several ways to output the correctable range. For example, the correctable page number range and / or correctable copy number range of the first task can be directly output, and further, a selection control that can be operated by the user can be output. The user can perform one or more operations such as selection and editing on the selection control. In this way, the interaction layer 123 can obtain the user's operation information regarding the correctable range.

[0067] It should be understood that the function and number of selection controls can be customized and are generally related to the correction methods and content provided by the print control system. For example, a selection control may include a page number range box, where the user can select the start and end pages to determine the page number positions to be corrected, allowing for batch deletion, insertion, editing, or other correction operations within these page ranges. Another example is a page number slider list, where the user can slide to select the page number positions to be corrected, facilitating deletion, insertion, editing, or other correction operations at those page positions. Yet another example is a batch range box, used to select the range of copies to be corrected in batches; a single copy input box, specifically used to select the specific number of copies to be modified. Furthermore, a correction method selection box, used to select the correction method, such as deletion, insertion, or editing. Additionally, a batch correction selection box (e.g., batch deletion, batch insertion, batch editing, etc.) allows the user to choose whether batch corrections are needed. It should be understood that the aforementioned selection controls are merely illustrative examples. In actual scenarios, one or more of the above selection controls can be used, as well as more or fewer selection controls, without any mandatory restrictions.

[0068] As described above, the user operation information involved in the embodiments of this application can be used to indicate, but is not limited to, at least one of the following: correction object information and correction method. The correction object information may include, but is not limited to, at least one of the following: object to be deleted (and / or object to be retained), object to be inserted, and object to be edited. The correction method may include, but is not limited to, at least one of the following: deletion method, insertion method, and editing method. Within the correctable scope output by this application, the user can customize the deletion, insertion, or editing. The following is a detailed description.

[0069] Among them, the deletion method, the objects to be deleted, and the objects to be retained are all related to the deletion process.

[0070] Specifically, deletion methods (or correction methods for deletion processing) can include, but are not limited to: batch deletion, single-part deletion, or total deletion. Batch deletion refers to deleting multiple sets of data within the correctable range in batches, i.e., deleting one or more pages of data from multiple sets of data. Single-part deletion refers to deleting a portion of the pages (one or more pages) from a single set within the correctable range. Total deletion refers to deleting all data within the correctable range; total deletion is a special form of batch deletion.

[0071] The specific deletion processing modification object information may include: objects to be deleted and / or objects to be retained. Objects to be deleted (i.e., objects the user intends to delete) may include, but are not limited to, one or more of the following: page numbers to be deleted, number of copies to be deleted. That is, objects to be deleted can be page numbers and / or the number of copies. In practical scenarios, a single data entry may include one or more page numbers, with no limitation thereto. Objects to be retained (i.e., objects the user intends to retain) may include, but are not limited to, one or more of the following: page numbers to be retained, number of copies to be retained. Objects to be retained refer to objects that remain unchanged within the scope of modification. It should be understood that objects outside the scope of objects to be retained within the scope of modification are objects to be deleted. In some embodiments, this application also provides users with an operation path for selecting objects to be retained. Users only need to determine which page numbers and / or the number of copies they want to retain, which also achieves the effect of deleting some objects. In other words, objects to be deleted and objects to be retained can be used as two object selection methods for deletion processing. The two methods can be used individually or in combination. For example, when there are many objects to be deleted, users can select the objects to keep to simplify the operation; when there are few objects to be deleted, users can directly select the objects to be deleted. It should be understood that this is only an example of an application scenario and is not intended to limit the scope of user operations.

[0072] It should be understood that in real-world scenarios, the aforementioned user operation information can be used in combination or individually. For example, if the user operation information indicates deletion of all items, there is no need to specify the items to be deleted and the items to be retained. Alternatively, instead of providing the user with deletion method options, the system can directly determine which pages and / or copies to delete based on the user's selected items (e.g., page numbers, number of copies to delete), and perform single or batch deletion according to preset or default deletion methods. This is not an exhaustive list.

[0073] In one exemplary embodiment, if the correction request is used to request deletion of a first submitted print job, the correction object information indicated by the user operation information includes: the page number to be deleted, and / or, the number of copies to be deleted; or, the correction object information indicated by the user operation information includes: the page number to be retained, and / or, the number of copies to be retained. If the correction request is used to request deletion of a first submitted print job, the correction method indicated by the user operation information includes: batch deletion, single copy deletion, or all deletion. Further details are omitted.

[0074] The insertion method is related to the object to be inserted and the insertion process.

[0075] Specifically, the insertion method (or the correction method for insertion processing) can include, but is not limited to: batch insertion and single insertion. Specifically, batch insertion refers to performing batch insertion processing on multiple sets of data within the modifiable range, that is, inserting one or more pages of data into multiple sets of data; single insertion refers to inserting one or more pages of data into a single set of data within the modifiable range.

[0076] The object to be inserted (or the correction object information for insertion processing) may include, but is not limited to, one or more of the following: the page number range to be inserted, and the document to be inserted. The page number range to be inserted is used to indicate the positions at which the new object (or the object to be inserted, or the document to be inserted) will be inserted. The page number range to be inserted can be indicated by two adjacent page numbers, or by a page number and indication information, wherein the indication information is used to indicate whether the insertion will occur before or after the page number. For example, a first indicator can be used to indicate insertion before the page number, and a second indicator can be used to indicate insertion after the page number. For example, the page number range to be inserted can be 39-40, meaning that the insertion will occur after page 39 and before page 40; or, the page number range to be inserted can be indicated by 39 and a second indicator, which also indicates that the insertion will occur after page 39 and before page 40. This application does not limit the indication method of the indication information, such as text, custom symbols, numbers, letters, patterns, etc., which will not be elaborated further. Furthermore, the page number range to be inserted can be one or more locations, and one or more pages of data can be inserted at any one location. The file to be inserted is used to indicate which objects to insert, and its name is not used to specifically restrict the object type. The file to be inserted can be one or more of the following, including but not limited to: documents (supporting Word, PDF, Excel, Txt, etc., but not limited to these), charts, data, text, icons, symbols, images, etc., and so on.

[0077] It should be understood that in real-world scenarios, the two types of user operation information mentioned above can be used in combination or individually. For example, if the user operation information indicates a file to be inserted, without specifying the insertion method, the file can be inserted at the current position (before the correctable range), or after the correctable range, or the page number range to be inserted can be automatically determined based on one or more methods such as semantic matching, text matching, or association recognition, and then inserted. As another example, in some scenarios, one or more files to be inserted can be preset. Therefore, when applying this solution, the user only needs to specify one or more of the page number range to be inserted, the insertion method, etc., to achieve automatic insertion of the preset files. Further examples are omitted.

[0078] In one exemplary embodiment, if the correction request is used to request insertion processing on a first submitted print job, the correction object information indicated by the user operation information includes: the page number range to be inserted and the file to be inserted. If the correction request is used to request insertion processing on a first submitted print job, the correction method indicated by the user operation information includes: batch insertion or single-copy insertion. Further details are omitted.

[0079] Among them, the editing method and the object to be edited are related to the editing process.

[0080] Specifically, editing methods (or editing correction methods) can include, but are not limited to: batch editing and individual editing. Batch editing means that one piece of content is edited in multiple editing locations, which is more efficient; individual editing means that the content and / or editing location is edited one by one, which is more suitable for personalized editing scenarios.

[0081] The object to be edited may include, but is not limited to, one or more of the following: page number to be edited, and content to be edited. Specifically, the page number to be edited indicates where to edit; the editing location can be one or more locations, which will not be elaborated further. The content to be edited indicates the user's edits to the correctable range, which may include, but is not limited to, one or more of the following: text modification, image processing, content replacement, etc., and will not be exhaustive.

[0082] In practical scenarios, the range of correction methods corresponding to the correction request can be preset or defaulted to. For example, in some possible embodiments, the correction method of the correction request may only include one of the above correction methods, such as deletion. In this case, the user only needs to select the object to be deleted and / or retained (page number and / or number of copies) within the correctable range, without needing to specify the correction method, making it simpler and faster. In addition, in some possible embodiments, multiple correction methods can be provided to the user simultaneously. The user can first select a correction method and then further select the specific processing method such as the object and location corresponding to the correction method. Furthermore, in some embodiments, multiple correction methods and their specific processing details can be displayed on the same page. The user can directly select the specific processing method based on their own needs and obtain all user operation information for the correctable range through a single interaction.

[0083] In summary, this application grants users a wide range of granular correction permissions, allowing them to finely modify submitted but unprinted portions (i.e., portions within the correction range) based on their actual needs. Furthermore, this application supports both batch processing (e.g., batch deletion, batch insertion, batch editing) and individual processing, offering a high degree of flexibility.

[0084] Taking deletion as an example, this section briefly explains the interaction process between the print control system (mainly involving interaction layer 123) and the user. First, after entering the operation interface, the user initiates a correction request. The print control system checks the hardware operating status and detects whether the print engine is suspended. If the print engine is suspended, the correction range is displayed through interaction layer 123, showing the number of copies and / or page numbers that the user can correct. The range of correctable copies and page numbers can be displayed through interaction layer 123. The user can then operate on the operation interface, selecting single-copy or batch operation. If a single-copy operation is selected, the user needs to further input the copy number identifier of the copies to be deleted and then select the page numbers to be deleted for that number of copies (the selection method is not limited; sliding and / or input are both acceptable, and the page numbers to be deleted can be one or more pages). Based on this, the print control system can determine the deletion targets based on the user's operation information. Alternatively, if the user selects batch operation, they also need to further input the copy range and the page number range. Based on this, the print control system can determine the deletion targets based on the user's operation information. The print control system can generate a reconstruction queue based on deleted objects and resume printing.

[0085] This application does not impose mandatory restrictions on the user interface. Users can operate on the user interface to perform actions such as triggering correction requests, canceling correction requests, selecting and / or entering a range of copies, selecting and / or entering a range of page numbers, and confirming correction content. The interaction layer 123 of this application may have one or more of the following interactive elements: an engine status indicator area, a correctable copy counter, a copy operation area, a page number sliding list, a page number range box, and a warning prompt box. In actual scenarios, the interaction layer 123 may also have more or fewer interface elements.

[0086] The engine status indicator area can be a specific indicator light or a similar interface element in the user interface, using different colors to represent different states of the printing engine. For example, green indicates the printing engine is suspended and can be corrected, red indicates the printing engine is not suspended, and yellow indicates the printing engine is suspended. There are no color restrictions; this is just an example. The correctable copy counter indicates the number of operable copies. The copy operation area can include one or more of the following: a single copy input box, a batch input box, and a copy number input box. The single copy input box is used to input a single copy number identifier (also called a copy number); the batch input box is used to input at least two copy number identifiers, and the range between two adjacent copy number identifiers is the range of copies to be corrected selected by the user; the copy number input box can be used to input one or more copy number identifiers and / or copy number ranges. The page number sliding list is used to display the correctable page number range, such as pages 1 to 100, by sliding vertically or horizontally. The user can click to select a page number in this area, and the selected page number will be highlighted (e.g., highlighted). The page number range box is used to input at least two page number identifiers, and the range between two adjacent page number identifiers is the range of pages to be corrected selected by the user. Warning dialog boxes are used to output prompts to inform users of abnormal situations. For example, warning dialog boxes can be used to output prompts such as "Engine hang failed, operation unavailable!" or "Repair request invalid, operation unavailable!", etc., without exhaustive list.

[0087] Furthermore, this application embodiment does not impose any particular restrictions on the specific form and storage method of user operation information. For example, in one embodiment, the interaction layer 123 can cache the user operation information, and the control layer 121 can directly read the user operation information from the cache. In another embodiment, the interaction layer 123 can also directly send the user operation information to the control layer 121 via real-time communication. In yet another embodiment, the interaction layer 123 can store the user operation information as a map container and submit the map container to the control layer 121. This is not an exhaustive list.

[0088] Based on user operation information, the details of the correction process can be obtained. Based on this, the temporal relationship between the user-corrected task object and each task object can be determined, and the queue reconstruction of the first task can be realized accordingly.

[0089] Based on the user operation information described in any of the foregoing embodiments, the generation of the reconstruction queue for the first task in this application can be implemented as follows: based on the user operation information, determine the correction object information and the correction method; based on the correction object information and the correction method, perform deletion, insertion, or replacement processing of task objects in the task queue corresponding to the correctable range of the first task; rearrange the task queue corresponding to the correctable range of the first task after the processing to obtain the reconstruction queue corresponding to the correctable range of the first task.

[0090] Taking deletion as an example, based on user operation information for the correctable range, a reconstruction queue for the first task is generated, which may include the following processes: determining the object to be deleted and the deletion method based on the user operation information; deleting the object to be deleted individually or in batches in the task queue corresponding to the correctable range of the first task according to the deletion method instruction; and rearranging the remaining objects in the task queue corresponding to the correctable range of the first task to obtain the reconstruction queue corresponding to the correctable range of the first task.

[0091] In practice, the object to be deleted can be determined by comparing the user operation information with the task queue corresponding to the correctable range of the first task. The object to be deleted can be one or more page numbers and / or copies. Specifically, if the correction object information indicated by the user operation information includes the page number to be deleted and / or the number of copies to be deleted, then the object to be deleted can be directly determined accordingly. In practice, the task queue corresponding to the correctable range of the first task can be directly compared with the page number to be deleted and / or the number of copies to be deleted, and the object belonging to the task queue corresponding to the correctable range of the first task and belonging to the page number to be deleted and / or the number of copies to be deleted is determined as the object to be deleted. Alternatively, if the user operation information indicates that the object to be corrected includes the page number to be retained and / or the number of copies to be retained, then the other page numbers and / or copies within the correctable range, excluding the objects to be retained, are the objects to be deleted. In practice, the queue corresponding to the correctable range of the first task can be compared with the page numbers and / or the number of copies to be retained. Objects belonging to the task queue corresponding to the correctable range of the first task but not to the page numbers and / or the number of copies to be retained are identified as objects to be deleted. In real-world scenarios, the user operation information only needs to indicate either the objects to be retained or the objects to be deleted to achieve this solution; redundant indication is unnecessary.

[0092] Furthermore, as mentioned above, this application can support users to make page-level corrections and / or copy-level corrections within the correctable range. In practical scenarios, the number of copies to be deleted and / or the page numbers to be deleted can be determined based on the user's operation information and the task queue corresponding to the correctable range of the first task.

[0093] Please refer to Figure 4 , Figure 4 This is a flowchart illustrating a deletion-based printing control method provided in an embodiment of this application. Figure 4 As shown, the control layer 121 can receive and parse the map container data (user operation information) to obtain the number of copies and / or page numbers that the user intends to retain. Furthermore, the control layer 121 can also obtain the remaining number of copies and page numbers in the task queue corresponding to the correctable range of the first task.

[0094] Then the number of copies can be compared. The control layer 121 can compare the number of remaining copies in the task queue corresponding to the correctable range of the first task with the number of copies to be retained. For any remaining copy (the i-th copy) in the task queue corresponding to the correctable range of the first task, if the copy belongs to the number of copies to be retained, then the copy is retained; otherwise, the copy is removed from the task queue corresponding to the correctable range of the first task.

[0095] Then, page number comparison is performed. The control layer 121 can compare the remaining page numbers corresponding to the number of copies in the task queue corresponding to the correctable range of the first task with the page numbers to be retained. For any remaining page number (page j) of that number of copies, if the page number belongs to the page number to be retained, then the page number is retained; otherwise, the page number is removed from the task queue corresponding to the correctable range of the first task.

[0096] Repeat the above steps until all copies and page numbers in the task queue corresponding to the correctable range of the first task have been compared. This completes the deletion of all objects to be deleted. Next, the remaining objects in the task queue corresponding to the correctable range of the first task are reconstructed. Specifically, the remaining copies and page numbers in the task queue corresponding to the correctable range of the first task can be rearranged (e.g., renamed) to construct a new print queue. This yields the reconstructed queue corresponding to the correctable range of the first task, which is then submitted to the printing engine for execution.

[0097] In this embodiment, if the user performs both page-level and copy-level deletion simultaneously, the number of copies to be deleted can be determined first, followed by the page number to be deleted, to simplify the processing logic and avoid redundant operations. Conversely, determining the page number to be deleted first, followed by the number of copies to be deleted, also does not affect the implementation of this solution.

[0098] Furthermore, real-world scenarios also involve the execution of duplex printing tasks. In duplex printing mode, based on preset duplex printing page number mapping rules, two pages printed on the same medium constitute a duplex printing combination. If a user discovers an error in a page number of the first submitted print job and needs to delete that page number, deleting only the print job node corresponding to that single page number in the job queue will cause all subsequent page numbers in the reconstructed job queue (i.e., the reconstructed queue) to automatically shift forward one position. In this case, if the user subsequently corrects the page number and prints it separately, the printed file cannot be accurately inserted into the already printed file set, or the back of the paper may be blank after insertion, thus compromising the physical integrity of the file set.

[0099] Considering this situation, this application further provides users with an optional processing solution for duplex printing scenarios, specifically including: First, receiving a deletion / correction request for a first task that has been submitted for printing, parsing the user operation information in the correction request, and extracting the correction object information and correction method; wherein, the correction object information only contains a single page number to be deleted, and the correction method is deletion processing; Second, determining whether the first task is a duplex printing task, specifically detecting whether the printing configuration parameters of the first task contain a duplex printing execution instruction; Third, if it is determined to be a duplex printing task, determining the single page number to be deleted based on a preset duplex printing page number mapping rule. The system first identifies a double-sided printing combination and designates it as the object to be deleted. A double-sided printing combination refers to a set of pages on the physical medium (e.g., paper) that carries a single page number to be deleted, consisting of two corresponding pages on the front and back sides. Fourth, based on the deletion correction method, the print task node corresponding to the double-sided printing combination is deleted from the task queue corresponding to the correctable range of the first task. Finally, after the user completes the correction operation for the single page number to be deleted and reprints it, the print file corresponding to the double-sided printing combination is inserted into the file set corresponding to the first task in page number order, thus perfectly balancing the flexibility of print task correction with the integrity of the file set.

[0100] In practical scenarios, this processing method can also output prompts to inform the user of the method and / or result of the current correction. Furthermore, in some possible embodiments, the prompts may include operation controls, allowing the user to choose whether to accept the method; for example, the operation controls include confirm and cancel. If the user clicks confirm, the object is deleted according to the double-sided printing method; if the user clicks cancel, the object is deleted according to the method described above. Further details are omitted.

[0101] The above example uses deletion to illustrate how to generate a reconstruction queue. The process is similar for insertion and editing, and is briefly explained below: For insertion processing, the range to be inserted and the file to be inserted can be determined based on the user operation information. Then, based on the single insertion or batch insertion method indicated by the insertion method, the file to be inserted is inserted into the range to be inserted in the task queue corresponding to the correctable range of the first task (i.e., single insertion or batch insertion). The queue can be reorganized to generate a reconstructed queue.

[0102] For editing, the page numbers and content to be edited in the task queue corresponding to the correctable range of the first task can be determined based on the user operation information. Then, the page numbers to be edited in the task queue corresponding to the correctable range of the first task are edited according to the content to be edited. Based on the editing method instruction, the page numbers to be edited in the task queue corresponding to the correctable range of the first task (one or more batches) are replaced with the edited page numbers in the manner of editing one by one or batch editing. The queue is then rearranged to generate a reconstructed queue, which will not be elaborated further.

[0103] Furthermore, this application can determine the correctable range of the first task based on the hardware operating status, specifically including the following processing: querying the hardware operating status, wherein the hardware operating status includes at least the paper feed sensor status, which indicates the current passing position of the medium. Based on this, unprocessed objects after the current passing position of the medium can be filtered in the first task to obtain the correctable range.

[0104] The medium, or printing medium, can include, but is not limited to, paper. The working principle of the paper feed sensor has already been explained. Located between the paper tray exit and the paper feed rollers, the paper feed sensor detects whether the paper has been successfully picked up and fed into the path. Thus, the paper feed sensor status indicates the position of the portion of the paper that has been picked up and fed into the paper path within the paper, i.e., the current position of the medium. For example, if the paper has completely left the paper tray and entered the paper path, the current position of the medium is at the page gap; if 50% of the paper has left the paper tray and entered the paper path, the current position of the medium is at the middle of the page. In practical scenarios, the paper feed sensor status can be further refined to represent the middle position of the page, such as specifying the proportion or number of rows of the portion currently in the paper path. This application does not impose any particular limitations on this.

[0105] Since the paper feed sensor status clearly indicates the current position of the medium, in this step, the control layer 121 needs to query the paper feed sensor status to determine the current position of the medium and thus determine the correctable range. Specifically, if the paper feed sensor status indicates that the current position of the medium is in the middle of the page (before reaching the page gap), the correctable range is all unprocessed pages starting from the page following the current page (i.e., the current page). If the paper feed sensor status indicates that the current position of the medium is at the page gap, then the paper (page) currently in the paper feed sensor has been processed, and the next page has not yet started processing. In this case, the next page after the current position of the medium is still taken as the starting page of the correctable range, and all pages after the starting page are the correctable range.

[0106] Specifically, the control layer 121 can query the hardware operating status through information interaction with the hardware layer 122. Specifically, the control layer 121 can send a query request to the hardware layer 122, and the hardware layer 122 can return the hardware operating status to the control layer 121 based on the query request. Thus, the control layer 121 receives the hardware operating status from the hardware layer 122.

[0107] Based on this, the hardware operating status queried by the control layer 121 and / or fed back by the hardware layer 122 may include more information. For example, the hardware operating status may include, but is not limited to, one or more of the following: print engine status (generally a laser engine, also called laser engine status), fuser unit status, other paper feed sensor status, etc., without exhaustive list. For example, the laser engine status can be used to indicate one or more of the following information: whether the laser engine position is legal, whether the laser engine is abnormal; the fuser unit status can be used to indicate one or more of the following information: fuser unit temperature (only involving temperature, which is determined by the control layer 121 to be whether it is overheating abnormal), fuser unit temperature overheating (abnormal information).

[0108] In one exemplary embodiment, in addition to responding to a query request and feeding back the hardware operating status to the control layer 121, the hardware layer 122 may also include the following processing: querying (or obtaining) the operating status of each piece of printer hardware and detecting whether each piece of printer hardware is abnormal. Therefore, if a printer hardware malfunctions, exception handling is performed; if none of the printer hardware is abnormal, the hardware layer 122 feeds back the hardware operating status to the control layer 121. The hardware operating status fed back can be all or part of the operating status of each piece of hardware queried by the hardware layer 122, without limitation.

[0109] This application does not impose any particular restrictions on the type of printer hardware or its fault handling methods. For example, printer hardware faults may include, but are not limited to, one or more of the following: sensor timeout, queue verification failure, hardware suspension failure, invalid laser engine position, overheating of the fuser unit, etc., without exhaustive list. Further, for example, if a sensor timeout occurs, one or more (e.g., three) retries can be performed. If the fault persists after retries, the sensor hardware is confirmed to be faulty, and the operation is interrupted. As another example, if a queue verification failure occurs, data loss or other data anomalies may occur. In this case, the task queue corresponding to the correctable range of the first task can be rolled back, and a notification can be output to the user through the interaction layer 123. As yet another example, if a hardware suspension failure occurs, an emergency stop can be initiated, and an error code can be output through the interaction layer 123 for the user to handle. It should be understood that any of the above faults can be reported to the user through the interaction layer 123, so that the user is aware of the hardware situation and can handle it promptly.

[0110] Furthermore, the aforementioned hardware anomaly query and detection can be performed continuously or periodically at the hardware layer 122. Alternatively, in another possible embodiment, execution can be triggered in response to receiving a query request. For example, after receiving a query request, the hardware layer 122 can collect the operating status of each hardware component and determine whether there is a hardware anomaly. If none of the hardware components are abnormal, it sends the hardware operating status, including at least the paper feed sensor status, to the control layer 121.

[0111] In one embodiment of this application, after querying the hardware operating status, the following processing may be included: isolating the unprocessed object from the processed object based on the current transit position of the medium. Specifically, this isolation process is intended to distinguish between unprocessed and processed objects so that subsequent correction processing is performed only on the unprocessed object.

[0112] In this context, the processed object can also be referred to as a "dirty page." This application defines a page that has already passed the paper feed sensor as a dirty page; at this point, the paper has left the paper tray, and this operation is generally irreversible. In practical scenarios, the paper feed sensor may include a paper feed sensor, an alignment sensor, and an eject sensor, in addition to the paper feed sensor. The alignment sensor is located after the paper feed sensor and before the printing engine. If the paper has passed the alignment sensor, logically, the page has passed the photosensitive drum and must be printed. If the paper passes the paper feed sensor but not the alignment sensor, and if it can be fed into the waste paper bin via a control program (if supported by hardware and software), then a dirty page can be defined as a page that has passed the alignment sensor. However, in general scenarios, if the paper passes the paper feed sensor but not the alignment sensor, printing continues to avoid adversely affecting pages already in the printing path. Therefore, in another possible embodiment of this application, if paper that has passed the paper feed sensor but not the alignment sensor is allowed to be revoked (i.e., allowed to return to the paper tray or undergo other operations, such as feeding into the waste paper bin, without entering the alignment sensor), then in this embodiment, a dirty page can also be a page that has passed the alignment sensor.

[0113] In a real-world scenario, the hardware layer 122 can report the boundary information of the current dirty page to the control layer 121. This information could include, but is not limited to, the page number of the last dirty page and / or a custom unique identifier. The control layer 121 can then isolate the dirty page based on this information. It should be understood that the boundary information of the dirty page corresponds to the correctable range, which includes all objects in the first task other than the dirty page, i.e., unprocessed objects. The hardware layer 122 can send the boundary information of the dirty page as part of the hardware operating status (e.g., the paper feed sensor status) along with the hardware operating status; or it can send it independently.

[0114] Dirty page isolation can be implemented through one or more methods, such as physical isolation and adding markers. Physical isolation means locking processed objects (i.e., dirty page data), thus making them read-only. Users cannot perform any processing on processed objects other than read-only, achieving both dirty page isolation and preventing accidental deletion of processed objects. Adding markers means adding custom identifiers to processed and / or unprocessed objects. These custom identifiers can include processed and / or unprocessed identifiers. Subsequent processing then only targets objects without a processed identifier and / or objects with an unprocessed identifier, thus distinguishing dirty pages through the custom identifiers corresponding to each object.

[0115] In one possible embodiment of this application, before generating the reconstruction queue of the first task, the method may further include: storing job data of the task queue corresponding to the correctable range of the first task.

[0116] Furthermore, this application supports multiple rounds of correction processing for the same first task, allowing users to submit correction requests multiple times based on actual scenario requirements. Therefore, for any round of correction processing, if no correction processing has been performed before this round, the task queue corresponding to the correctable range of the first task can be the initial task queue generated when the user first submits the first task; or, if the first task has been modified before this round of correction processing, the task queue corresponding to the correctable range of the first task is the reconstructed queue generated during the previous round of correction processing, with no restrictions on this.

[0117] The job data of the task queue corresponding to the correctable range of the first task includes at least the complete queue structure of the task queue corresponding to the correctable range of the first task. The complete queue structure of the task queue corresponding to the correctable range of the first task refers to all task objects in the task queue corresponding to the correctable range of the first task and the queue relationships between each task object. In addition, the job data may also include, but is not limited to, one or more of the following: page rendering data in RAM, current copy counting data of the recorder, sensor status data (e.g., the current passing position of the medium), consumable data (ink / paper), etc., which are not exhaustive and will not be elaborated upon.

[0118] This application does not limit the storage method of job data. For example, job data can be stored in the form of job snapshots (i.e., creating dynamic memory snapshots), or the task queue corresponding to the correctable range of the first task can be copied and its complete data stored directly. Alternatively, feature vectors or other forms of custom data can be generated based on the task queue corresponding to the correctable range of the first task and stored. This application also does not limit the storage location of job data. Job data can be stored in dynamic memory, locally on the printer, or in the cloud or third-party storage, which will not be elaborated further.

[0119] By pre-storing the data of the task queue corresponding to the correctable range of the first task, if an anomaly occurs in the reconstruction queue, causing the queue verification to fail, the first task can be rolled back from the reconstruction queue to the pre-stored previous queue (i.e., the task queue corresponding to the correctable range of the first task) through data rollback, thereby avoiding data anomalies. The first task can be executed according to the task queue that the user last submitted or modified, ensuring the smooth execution of the first task.

[0120] Furthermore, in a preferred embodiment, the data storage for the task queue corresponding to the correctable range of the first task needs to be completed before generating the reconstructed queue. In a practical scenario, a dynamic memory snapshot can be created before the hardware layer 122 is frozen, for example, after the control layer 121 receives the hardware operating status feedback from the hardware layer 122 (at which point the mechanical status check of the hardware layer 122 is correct). This snapshot saves the complete queue structure corresponding to the correctable range of the first task, protecting the data and providing room for data rollback after the hardware layer 122 is unfrozen, thus providing data support for the hardware layer 122 to return to a safe state.

[0121] In this application, after querying the hardware operating status, the following processing may also be included: based on the hardware operating status, controlling the relevant hardware to shut down.

[0122] The control of related hardware shutdown, also known as hardware freeze, refers to temporarily stopping the operation of related hardware (shutdown) to prevent continuous operation from causing dynamic changes in the correctable range and affecting the normal progress of print correction processing. Different hardware requires different shutdown methods. The related hardware involved in this embodiment may include, but is not limited to, the print engine and the paper feed sensor. Shutting down the print engine means suspending the print engine and stopping the printing operation, for example, by turning off laser scanning. The paper feed sensor is related to paper feeding; stopping and freezing the paper feed sensor means stopping paper feeding; in specific implementations, this can be achieved by turning off the drive motor of the paper feed sensor. Furthermore, in some possible embodiments, the temperature of the fixing unit can be kept constant to avoid cold start delays.

[0123] Specifically, in this embodiment, the control layer 121 can determine when to control the hardware to stop based on the hardware operating state (at least including the paper feed sensor state). Specifically, for any printing task, the printing engine is only allowed to be suspended if the current passing position of the medium is at a page gap (also known as a page interval) to avoid printing half a page (in some embodiments, the printing engine can be suspended only at the copy separation to avoid printing half a copy, or a combination of both). Based on this, if the paper feed sensor state indicates that the current passing position of the medium is at a page gap, it means that the current passing position of the medium is at a page edge, and the printing engine can be suspended; conversely, if the paper feed sensor state indicates that the current passing position of the medium does not have a page gap, it means that the current passing position of the medium is in the middle of the page. In this case, the control layer 121 can wait until the paper feed sensor state indicates that the current passing position of the medium is at a page gap before controlling the printing engine to be suspended; or, the control layer 121 can instruct the hardware layer 122 to gradually stop the printing. In other words, in this embodiment, the relevant hardware (at least the print engine) will only stop and freeze when the paper feed sensor status indicates that the current passing position of the medium is at the page interval.

[0124] In one exemplary embodiment, if the paper feed sensor status indicates that the current passing position of the medium is at a page gap, the control layer 121 can send a suspend command to the hardware layer 122 to instruct the hardware layer 122 to implement a hardware shutdown freeze based on a stop command. The stop command is at least used to instruct the relevant hardware of the hardware layer 122 to stop immediately. In this embodiment, the control layer 121 can interact with the hardware layer 122 in real time to obtain the paper feed sensor status and determine whether the current passing position of the medium is at a page gap. If the current passing position of the medium is at a page gap, the control layer 121 controls the hardware layer 122 to stop immediately to avoid half-page printing.

[0125] In another embodiment, without much intervention from the control layer 121, the control layer 121 can directly instruct the hardware layer 122 to perform a gradual shutdown, so that the relevant hardware performs a shutdown freeze when the current passing position of the medium indicated by the paper feed sensor is at the page interval.

[0126] Specifically, in this embodiment, before determining the correctable range of the first task based on the hardware operating state, the method further includes: the control layer 121 sending a suspension command to the hardware layer 122; wherein the suspension command is used to instruct the hardware layer 122 to gradually stop. The gradual stop is at least used to instruct the printing engine to continue operating until the current passing position of the media is at the page interval; wherein the current passing position of the media is indicated by the paper feed sensor status.

[0127] It should be understood that the content indicated by the suspend instruction (also known as freeze instruction, pause instruction, etc., name is not limited) in this embodiment is slightly different from that in the foregoing embodiments. The two can be the same instruction but carrying different instruction information, or they can be different instructions, and there is no limitation in this regard. For example, in other possible embodiments, the suspend instruction may not be used to indicate the shutdown method. Whether a gradual shutdown or other method is adopted can be determined by the hardware layer 122 or set by default, and there is no limitation in this regard.

[0128] In this embodiment, gradual shutdown means that after receiving the instruction, hardware layer 122 will not immediately stop the operation of all related hardware, but will gradually shut down in a step-by-step and / or phased manner. The shutdown node is when the current passing position of the medium is at the page interval, and a certain amount of time is required from receiving the shutdown instruction to the actual shutdown. Furthermore, gradual shutdown can be applied to all related hardware, or it can be applied only to some of the hardware. For example, the paper feed motor can be gradually shut down, controlling it to gradually decelerate until its speed reaches 0 within a preset time. Alternatively, some related hardware can be stopped in stages, and then other hardware can be gradually stopped. Or, all related hardware can be controlled to gradually decelerate or reduce the scanning frequency, etc., until it stops completely.

[0129] Furthermore, in any of the foregoing embodiments, the control layer 121 can send an ENGINE_SUSPEND command (i.e., a suspension command) to the hardware layer 122 (i.e., the HAL layer). Upon receiving this command, the hardware layer 122 can shut down laser scanning, stop the paper feed sensor motor, and maintain the temperature of the fuser assembly. Additionally, the hardware layer 122 can also send a stop confirmation command, such as a SUSPEND_ACK signal, to the control layer 121. Based on this stop confirmation command, the control layer 121 can enter a correction mode to correct any unprocessed tasks.

[0130] In one exemplary embodiment, reference can be made to Figure 5 , Figure 5 This is a schematic diagram illustrating a gradual shutdown as provided in an embodiment of this application. Figure 5As shown, hardware layer 122 can receive suspend commands, such as the SUSPEND command. In response to this suspend command, hardware layer 122 can initiate a three-stage deceleration program. In the first stage, the paper feed motor speed is reduced; for example, it can be linearly reduced from normal speed to 0 within 100ms; or, for example, the paper feed roller speed can be reduced by 50% initially. While the paper feed motor is decelerating, the status of the paper feed sensor is continuously monitored to determine if the next stable position has been reached (e.g., the page gap position, and / or the position before the alignment roller). If the paper feed sensor status indicates that the current passing position of the medium is at the page gap, the second stage begins, controlling the printing engine to stop scanning, for example, controlling the laser engine to stop emitting laser light. Furthermore, in this stage, the fuser assembly can be kept at a constant temperature to avoid delays caused by reheating. In the third stage, the main motor is slowly stopped and mechanical operation is locked. This completes the gradual shutdown of hardware layer 122, which can also send a shutdown confirmation command, such as the SUSPEND_ACK signal, to control layer 121.

[0131] By implementing a gradual shutdown, it is possible to ensure that all relevant devices in the hardware layer 122 reach a safe and stable position when the system actually stops. For example, a gradual shutdown of the paper feed motor can ensure that the paper currently being transported can safely reach the next stable position (such as the page spacing or alignment position), avoiding abnormal situations such as paper jams, which helps to ensure the stability and safety of the printing system.

[0132] In a real-world scenario, once all the relevant hardware in hardware layer 122 has completely stopped working, it enters a low-power standby state (in some embodiments, the fixing temperature can also be maintained in this state), waiting for a recovery command (also known as a defrost command, power-on command, etc., with no limitation on the name) from control layer 121. The recovery command is at least used to instruct hardware layer 122 to restart.

[0133] Specifically, after receiving the recovery signal, the hardware layer 122 can unfreeze and restart the relevant hardware. Specifically, after receiving the recovery signal, the hardware layer 122 can restart the paper feed motor and start working according to the task queue corresponding to the correctable range of the first task or the new print queue (i.e., the reconstruction queue) sent by the control layer 121.

[0134] Specifically, the printing engine resets the print queue based on the reconstruction queue sent by the control layer 121, so that printing tasks can continue based on the reconstructed queue. Furthermore, the mechanical position of the drive motor reverts to the nearest safe point, and the rendering pointer is restored from the corresponding page of the modified queue. In practical scenarios, users can operate within the correctable range or choose not to make any corrections; this application does not impose any particular restrictions on this. Therefore, for the hardware layer 122, if the user does not make any corrections, after the hardware layer 122 restores, it can continue processing directly according to the existing print queue without resetting it; alternatively, it can reset the print queue based on the original queue (e.g., queue data in a dynamic memory snapshot) (generally, this process is unnecessary).

[0135] Furthermore, in some possible embodiments, the recovery instruction can also be used to instruct the hardware layer 122 to restart in a gradual manner. In one exemplary embodiment, continuing to execute the first task based on the reconstruction queue includes: sending a recovery instruction and the reconstruction queue to the hardware layer 122, so that the restarted hardware layer 122 continues to execute the first task based on the reconstruction queue; wherein the recovery instruction is used to instruct the hardware layer 122 to start gradually.

[0136] As previously stated, the recovery command is at least used to instruct hardware layer 122 to unfreeze and restart. In this embodiment, the recovery command is further used to instruct hardware layer 122 to use a gradual startup method. It should be understood that in other possible embodiments, the recovery command may not be used to instruct the startup method; whether to use a gradual startup, an immediate startup, or another method can be determined by hardware layer 122 itself or set by default, and there are no restrictions on this.

[0137] Progressive startup means that hardware layer 122 gradually starts up in a step-by-step and / or phased manner. A certain amount of time is required from receiving the recovery command to the actual unfreezing and restart. There are several methods of progressive startup. For example, the paper feed motor gradually increases its speed from 0 or a preset starting value until it reaches normal speed. Another example is the laser engine gradually increasing its scanning frequency from 0 or a preset scanning frequency until it reaches normal scanning frequency. Yet another example is the fixing temperature of the fixing unit gradually increasing until it reaches its operating temperature. Similar to progressive shutdown, progressive startup can also be applied to all or part of the relevant hardware, which will not be elaborated further.

[0138] After receiving the recovery command, the hardware layer 122 can restart the paper feed motor at a low starting speed, and then gradually accelerate to the normal speed (within a preset time interval) and start the printing engine to continue printing. This also enables the gradual start of the hardware layer 122.

[0139] You can refer to this. Figure 6 , Figure 6This is a flowchart illustrating another printing control method provided in an embodiment of this application. Figure 6 As shown, the control layer 121 implements the printing control scheme through interaction with the user and the hardware layer 122. The control layer 121 can receive correction requests triggered by the user and send query requests and stop commands to the hardware layer 122. In this embodiment, the query request can be sent together with the stop command, or they can be sent independently. Figure 6 As shown, after receiving the query request and stop command, the hardware layer 122 queries the hardware operating status of relevant hardware, such as the paper feed sensor status, and generates a dirty page mapping table accordingly. Then, it performs a stop / freeze of the relevant hardware, such as a gradual stop, and feeds back the hardware operating status to the control layer 121. Upon receiving the hardware operating status, the control layer 121 determines the correctable range and obtains user operation information for that range, generating a reconstruction queue for the first task. The control layer 121 can then send the reconstruction queue and a recovery command to the hardware layer 122. These can be sent independently or together, as detailed below. Upon receiving the recovery command and reconstruction queue, the hardware layer 122 restarts the relevant hardware and resets the print queue for the first task based on the reconstruction queue, continuing to execute the task according to the reset print queue.

[0140] During this process, if users need to correct a submitted print job, they do not need to cancel the entire job, thus avoiding a waste of resources and time.

[0141] For example, in a large-scale printing scenario, a user needs to print 100 copies of a 100-page manual (i.e., the first task). When printing the 40th copy (page 50), the user realizes that the remaining 50 pages (pages 51-100) are not needed. Therefore, the requirement has changed, and the subsequent unprocessed print jobs urgently need to be corrected.

[0142] In this situation, the relevant technology only supports users canceling the entire job and then re-initiating a new one for printing. If a user cancels the current job, modifies the document, and then reissues the print job, this process will waste 2000 pages and take approximately 65 minutes longer. Alternatively, the user can choose not to cancel the job and continue the current task, in which case the manual will be printed as planned, but this will waste 2500 pages and take approximately 80 minutes longer.

[0143] In response, the proposed solution allows users to initiate a correction request for the print job. For example, by clicking "Correct" on the printer panel or mobile control panel, the printer will display the current correctable range: page 51 of the 40th copy to page 100 of the 100th copy. Users can freely correct within this range. In this scenario, the user simply needs to select pages 51-100 of the 51st to 100th copies for deletion. After the user's action, the printer generates a reconstruction queue and restores the hardware layer 122 job. During this process, the application wastes at most one page (i.e., the 50th page of the 40th copy is partially exposed and has already been fed), and the entire process, including hardware freezing, user selection, and queue updating, can be completed in 5 minutes. Furthermore, this application is device-independent and can be directly controlled via the printer panel, PC, or one or more other devices, making it convenient and fast. In other words, this application achieves "page-level surgical" correction, precisely extending the user's operable time point from after clicking to start printing to before paper feed, greatly improving user operation error tolerance, efficiency, and saving significant time costs, giving the printer "undo capability" for the first time.

[0144] For ease of understanding, the following is combined with Figure 7 Explain the specific interaction process and implementation of this printing control method, in which, Figure 7 This is a flowchart illustrating another printing control method provided in an embodiment of this application, which specifically shows the interaction process between the control layer 121, the hardware layer 122, and the interaction layer 123 in the printing control system.

[0145] like Figure 7 As shown, the user can trigger a correction request through the interaction layer 123. Upon receiving this request, the control layer 121 responds by sending a query request to the hardware layer 122 to check the hardware's operating status. The hardware layer 122 checks the hardware status, suspends the print engine, freezes and shuts down related hardware, isolates dirty pages, and then reports the hardware operating status back to the control layer 121 (including at least the paper feed sensor status; in real-world scenarios, it can also carry other sensor data, consumable status, paper position, etc.). Based on the data from the hardware layer 122, the control layer 121 determines the unprocessed portion (non-dirty page portion) of the first print job as the correctable range and reports this range to the user through the interaction layer 123. The user can then perform operations within this correctable range to complete specific corrections; for example, the user can select a range to delete. The interaction layer 123 reports this user operation information back to the control layer 121. The control layer 121 then recalculates resources to generate a reconstruction queue for the first print job, sends the reconstruction queue to the hardware layer 122, and instructs the hardware layer 122 to update the print job. In this way, hardware layer 122 can continue printing based on the updated print job, thereby completing the printing process of the entire first job.

[0146] In summary, the printing control method provided in this application can accurately modify the unprinted portion of a submitted print job without resetting the entire job. It is simple, convenient, and efficient, and helps to avoid wasting resources and time.

[0147] This application also provides a printing control device. Figure 8 A structural block diagram of a printing control device provided in an embodiment of this application is shown below. Figure 8 As shown, the printing control device 800 can specifically be the control layer 121 described above, which may specifically include: The communication unit 810 is used to receive a correction request, which is used to request correction processing to be performed on the first task that has been submitted for printing. Processing unit 820 is used to determine the correctable range of the first task based on the hardware operating status; The processing unit 820 is also used to generate a reconstruction queue for the first task based on user operation information for the correctable range; Processing unit 820 is also used to continue executing the first task based on the reconstructed queue.

[0148] In one exemplary embodiment, the correctable range includes at least one of the following: page number range and number of copies range.

[0149] In one exemplary embodiment, the correction process includes one or more of the following: deletion, insertion, and editing.

[0150] In one exemplary embodiment, the user operation information is used to indicate: correction object information and correction method; in this case, the processing unit 820 is specifically used to: Based on the correction object information and correction method for the correctable range, a reconstruction queue for the first task is generated.

[0151] In one exemplary embodiment, if the correction request is used to request deletion processing of the first task that has been submitted for printing, the correction object information indicated by the user operation information includes: the page number to be deleted, and / or, the number of copies to be deleted; or, the correction object information indicated by the user operation information includes: the page number to be retained, and / or, the number of copies to be retained; the correction method indicated by the user operation information includes: batch deletion, single copy deletion, or all deletion.

[0152] In one exemplary embodiment, if the correction request is used to request insertion processing on a first task that has been submitted for printing, the correction object information indicated by the user operation information includes: the page number range to be inserted and the file to be inserted; the correction method indicated by the user operation information includes: batch insertion or single insertion.

[0153] In one exemplary embodiment, if the correction request is used to request editing processing of the first task that has been submitted for printing, the correction object information indicated by the user operation information includes: the page number to be edited and the content to be edited; the correction method indicated by the user operation information includes: batch editing or editing one by one.

[0154] In one exemplary embodiment, the processing unit 820 is specifically used for: Based on the user operation information, the correction object information and the correction method are determined; Based on the correction object information and the correction method, the task object is deleted, inserted, or replaced after editing in the task queue corresponding to the correctable range of the first task; The task queue corresponding to the correctable range of the first task after rearrangement is obtained to form the reconstructed queue corresponding to the correctable range of the first task.

[0155] In one exemplary embodiment, the processing unit 820 is specifically used for: If the correction request is used to request the deletion of the first task that has been submitted for printing, and the correction object information indicated by the user operation information includes a single page number to be deleted, when the first task is a duplex printing task, the duplex printing group containing the single page number to be deleted is determined as the object to be deleted. Based on the correction method, the double-sided printing combination is deleted from the task queue corresponding to the correctable range of the first task.

[0156] In one exemplary embodiment, the processing unit 820 is specifically used for: Query the hardware operating status, which includes at least the paper feed sensor status, which indicates the current position of the medium. In the first task, filter the unprocessed objects after the current passing position of the medium to obtain the correctable range.

[0157] In one exemplary embodiment, the communication unit 810 is specifically used for: Send a query request to hardware layer 122; Receive the hardware operating status from hardware layer 122.

[0158] In one exemplary embodiment, the processing unit 820 is further configured to: Based on the current transit position of the medium, isolate unprocessed objects from processed objects.

[0159] In one exemplary embodiment, before generating the reconstruction queue for the first task, the processing unit 820 is further configured to: Store the job data of the task queue corresponding to the correctable range of the first task.

[0160] In one exemplary embodiment, after receiving the correction request, the processing unit 820 is further configured to: Verify the validity of the correction request; validity includes at least one of the following: the requester's identity is valid, and the first task matches; If the correction request is invalid, a prompt message will be displayed.

[0161] In one exemplary embodiment, before determining the correctable range of the first task based on the hardware operating state, the processing unit 820 is further configured to: A suspend command is sent to hardware layer 122; wherein the suspend command is used to instruct hardware layer 122 to perform a gradual shutdown; wherein instructing hardware layer 122 to perform a gradual shutdown includes instructing the printing engine to continue operating until the current passing position of the media is at the page interval and then stopping; wherein the current passing position of the media is indicated by the status of the paper feed sensor.

[0162] In one exemplary embodiment, the processing unit 820 is specifically used for: A recovery command and a reconstruction queue are sent to hardware layer 122 so that the rebooted hardware layer 122 can continue to execute the first task based on the reconstruction queue; wherein, the recovery command is used to instruct hardware layer 122 to start gradually.

[0163] For details not covered, please refer to the preceding text; further explanation is not required here.

[0164] Figure 9 This is a hardware block diagram of an electronic device provided in an embodiment of this application. The electronic device 900 according to an embodiment of this application includes at least a memory, a processor, and a computer program stored in the memory. The processor executes the computer program to implement the printing control method described in any of the above embodiments.

[0165] Figure 9 The illustrated electronic device 900 specifically includes a central processing unit (CPU) 901, a graphics processing unit (GPU) 902, and a memory 903. These units are interconnected via a bus 904. The CPU 901 and / or GPU 902 can function as the aforementioned processor, and the memory 903 can function as the aforementioned memory storing computer-readable instructions. Furthermore, the electronic device 900 may also include a communication unit 905, a storage unit 906, an output unit 907, an input unit 908, and an external device 909, all of which are also connected to the bus 904.

[0166] Figure 10This is a schematic diagram of a computer-readable storage medium provided in an embodiment of this application. The computer-readable storage medium according to an embodiment of this application stores computer programs / instructions (including but not limited to computer-readable instructions). Specifically, as shown... Figure 10 As shown, a computer-readable storage medium 1000 stores computer-readable instructions 1001. When executed by a processor, this computer program / instruction implements the printing control method described in any of the preceding embodiments of this application. The computer-readable storage medium includes, but is not limited to, volatile memory and / or non-volatile memory. Volatile memory may include, for example, random access memory (RAM) and / or cache memory. Non-volatile memory may include, for example, read-only memory (ROM), hard disk, flash memory, optical disk, magnetic disk, etc.

[0167] This application further provides a computer program product, including a computer program / instructions that, when executed by a processor, implement the printing control method described in any of the preceding embodiments of this application.

[0168] The basic principles of this application have been described above with reference to specific embodiments. However, it should be noted that the advantages, benefits, and effects mentioned in this application are merely examples and not limitations, and should not be considered as essential features of each embodiment of this application. Furthermore, the specific details disclosed above are for illustrative and facilitative purposes only, and are not limitations. These details do not limit the application to the necessity of employing the aforementioned specific details for implementation.

[0169] The block diagrams of devices, apparatuses, devices, and systems involved in this application are merely illustrative examples and are not intended to require or imply that they must be connected, arranged, or configured in the manner shown in the block diagrams. As those skilled in the art will recognize, these devices, apparatuses, devices, and systems can be connected, arranged, and configured in any manner. Words such as “comprising,” “including,” “having,” etc., are open-ended terms meaning “including but not limited to,” and are used interchangeably with them. The terms “or” and “and” as used herein refer to the terms “and / or,” and are used interchangeably with them unless the context clearly indicates otherwise. The term “such as” as used herein refers to the phrase “such as but not limited to,” and is used interchangeably with it.

[0170] Additionally, as used herein, the "or" used in a list of items beginning with "at least one" indicates a separate list, such that a list of, for example, "at least one of A, B, or C" means A or B or C, or AB or AC or BC, or ABC (i.e., A and B and C). Furthermore, the word "exemplary" does not imply that the described example is preferred or better than other examples.

[0171] It should also be noted that in the system and method of this application, the components or steps can be decomposed and / or recombined. These decompositions and / or recombinations should be considered as equivalent solutions of this application.

[0172] Various changes, substitutions, and modifications can be made to the technology described herein without departing from the teachings defined by the appended claims. Furthermore, the scope of the claims is not limited to the specific aspects of the processes, machines, manufactures, events, means, methods, and actions described above. Currently existing or later-developed processes, machines, manufactures, events, means, methods, or actions that perform substantially the same function or achieve substantially the same result as the corresponding aspects described herein can be utilized. Therefore, the appended claims include such processes, machines, manufactures, events, means, methods, or actions within their scope.

[0173] The above description of the disclosed aspects is provided to enable any person skilled in the art to make or use this application. Various modifications to these aspects will be readily apparent to those skilled in the art, and the general principles defined herein can be applied to other aspects without departing from the scope of this application. Therefore, this application is not intended to be limited to the aspects shown herein, but rather to be accorded the widest scope consistent with the principles and novel features disclosed herein.

[0174] The above description has been given for purposes of illustration and description. Furthermore, this description is not intended to limit the embodiments of this application to the forms disclosed herein. Although numerous exemplary aspects and embodiments have been discussed above, those skilled in the art will recognize certain variations, modifications, alterations, additions, and sub-combinations thereof.

Claims

1. A printing control method, characterized in that, include: Receive a correction request, the correction request being used to request correction processing to the first task that has been submitted for printing; Based on the hardware operating status, determine the correctable range of the first task; Based on user operation information for the correctable range, a reconstruction queue for the first task is generated; Based on the reconstructed queue, continue executing the first task.

2. The method according to claim 1, characterized in that, The correctable range includes at least one of the following: page number range and number of copies range.

3. The method according to claim 1, characterized in that, The correction process includes one or more of the following: deletion, insertion, and editing.

4. The method according to claim 1, characterized in that, The user operation information is used to indicate, including: the object to be corrected and the correction method; The process of generating the reconstruction queue for the first task based on the user operation information within the correctable range includes: Based on the information on the correctable object and the corrective method within the correctable range, a reconstruction queue for the first task is generated.

5. The method according to claim 4, characterized in that, If the correction request is used to request deletion of the first task that has been submitted for printing, then the correction object information indicated by the user operation information includes: the page number to be deleted, and / or, the number of copies to be deleted; or, the correction object information indicated by the user operation information includes: the page number to be retained, and / or, the number of copies to be retained; the correction method indicated by the user operation information includes: batch deletion, single copy deletion, or all deletion. If the correction request is used to request insertion processing on the first task that has been submitted for printing, then the correction object information indicated by the user operation information includes: the page number range to be inserted and the file to be inserted; the correction method indicated by the user operation information includes: batch insertion or single insertion. If the correction request is used to request editing of the first task that has been submitted for printing, the correction object information indicated by the user operation information includes: the page number to be edited and the content to be edited; the correction method indicated by the user operation information includes: batch editing or editing one by one.

6. The method according to claim 4, characterized in that, The process of generating a reconstruction queue for the first task based on the user operation information within the correctable range includes: Based on the user operation information, the correction object information and the correction method are determined; Based on the correction object information and the correction method, the task object is deleted, inserted, or replaced after editing in the task queue corresponding to the correctable range of the first task; The task queue corresponding to the correctable range of the first task after rearranging the processed task queue is obtained as the reconstructed queue corresponding to the correctable range of the first task.

7. The method according to claim 6, characterized in that, The step of deleting, inserting, or replacing task objects in the task queue corresponding to the correctable range of the first task, based on the correction object information and the correction method, includes: If the correction request is used to request the deletion of the first task that has been submitted for printing, and the correction object information indicated by the user operation information includes a single page number to be deleted, when the first task is a duplex printing task, the duplex printing combination to which the single page number to be deleted belongs is determined as the object to be deleted. Based on the correction method, the double-sided printing combination is deleted from the task queue corresponding to the correctable range of the first task.

8. The method according to any one of claims 1-7, characterized in that, Determining the correctable range of the first task based on the hardware operating status includes: Query the hardware operating status, wherein the hardware operating status includes at least the paper feed sensor status, which is used to indicate the current passing position of the medium; Based on the current transit position of the medium, unprocessed objects are filtered out in the first task, and a correctable range is determined based on the unprocessed objects.

9. The method according to claim 8, characterized in that, The query of hardware operating status includes: Send a query request to the hardware layer; Receive the hardware operating status from the hardware layer.

10. The method according to claim 8, characterized in that, The method further includes: Based on the current transit position of the medium, the unprocessed object is isolated from the processed object.

11. The method according to any one of claims 1-7, characterized in that, Before generating the reconstruction queue for the first task, the method further includes: Store the job data of the task queue corresponding to the correctable range of the first task.

12. The method according to any one of claims 1-7, characterized in that, After receiving the correction request, the method further includes: Verify the legality of the correction request; the legality includes at least one of the following: the requester's identity is legitimate, and the first task matches; If the correction request is invalid, a prompt message will be output.

13. The method according to any one of claims 1-7, characterized in that, Before determining the correctable range of the first task based on the hardware operating status, the method further includes: Send a suspend instruction to the hardware layer; wherein the suspend instruction is used to instruct the hardware layer to perform a gradual shutdown; The instruction to the hardware layer to perform a gradual shutdown includes instructing the printing engine to continue operating until the current passing position of the medium is at the page interval before stopping; wherein the current passing position of the medium is indicated by the status of the paper feed sensor.

14. The method according to any one of claims 1-7, characterized in that, The step of continuing to execute the first task based on the reconstructed queue includes: A recovery command and the refactoring queue are sent to the hardware layer so that the restarted hardware layer continues to execute the first task based on the refactoring queue; wherein the recovery command is used to instruct the hardware layer to start gradually.

15. A printing control device, characterized in that, include: A communication unit is configured to receive a correction request, the correction request being used to request correction processing of a first task that has been submitted for printing; The processing unit is used to determine the correctable range of the first task based on the hardware operating status. The processing unit is also configured to generate a reconstruction queue for the first task based on user operation information for the correctable range; The processing unit is also configured to continue executing the first task based on the reconstructed queue.

16. A printing control system, characterized in that, include: A control layer for performing the method as described in any one of claims 1-14; The hardware layer is used to perform printing tasks; The interaction layer is used to realize human-computer interaction between the control layer and the user.

17. An image forming apparatus, characterized in that, include: main body; The printing control system as described in claim 16.

18. An electronic device comprising a memory, a processor, and a computer program stored in the memory, characterized in that, The processor executes the computer program to implement the method according to any one of claims 1-14.

19. A computer-readable storage medium having a computer program / instructions stored thereon, characterized in that, When the computer program / instructions are executed by the processor, they implement the method described in any one of claims 1-14.

20. A computer program product comprising a computer program / instructions, characterized in that, When the computer program / instructions are executed by the processor, they implement the method described in any one of claims 1-14.

Images