CN111124321B

CN111124321B - Debugging method and system of laser printer

Info

Publication number: CN111124321B
Application number: CN201911067265.2A
Authority: CN
Inventors: 王伟聪; 张怿; 黄智�; 吴泽民; 龙安川; 唐忞旻
Original assignee: Shenzhen Castle Security Tech Co ltd
Current assignee: Shenzhen Castle Security Tech Co ltd
Priority date: 2019-11-04
Filing date: 2019-11-04
Publication date: 2020-09-08
Anticipated expiration: 2039-11-04
Also published as: CN111124321A

Abstract

The invention relates to the technical field of intelligent printing processing systems, in particular to a debugging method and a debugging system of a laser printer. The method comprises the steps of utilizing the laser printer to send application scene information to an operation server in the working process, obtaining corresponding debugging updating data from the operation server, then updating chip parameters of an SOC chip and system data in a printing safety chip according to the debugging updating data, sending updating completion information to the operation server after updating is completed each time, obtaining debugging tracking historical information with a current time node as a reference from the laser printer by tracking the operation server, and generating a debugging strategy aiming at the laser printer by a debugging terminal according to the debugging tracking historical information. The invention enables the laser printer to achieve better system adaptation effect in various application scenes, thereby enhancing the printing experience of the laser printer in any scene and improving the debugging effect.

Description

Debugging method and system of laser printer

Technical Field

The application relates to the technical field of intelligent printing processing systems, in particular to a debugging method and a debugging system of a laser printer.

Background

Laser printers are print output devices that combine laser scanning technology with electrophotographic technology. The basic working principle is that the binary data information transmitted from computer is converted into video signal by video controller, then the video signal is converted into laser driving signal by video interface/control system, then the laser scanning system generates laser beam with character information, finally the electronic photographic system makes the laser beam image and transfer it onto paper. Compared with other printing equipment, the laser printer has the advantages of high printing speed, high imaging quality and the like, but the use cost is relatively high.

However, the SOC chip parameters and system data of the laser printer in the market are usually fixed after the laser printer leaves the factory for use, and even if the conditions of the external scene change, the SOC chip parameters and the system data in the printing security chip cannot be adjusted accordingly, so that a better system adaptation effect cannot be achieved in many scenes, and especially for the shared laser printers arranged in different areas on the market, the user experience is seriously affected.

Disclosure of Invention

In order to overcome at least the above deficiencies in the prior art, an object of the present application is to provide a method and a system for debugging a laser printer, which can perform adaptive dynamic debugging and updating on chip parameters of an SOC chip and system data in a print security chip according to an actual application scenario, so that the laser printer can achieve a better system adaptation effect in various application scenarios, further enhance the printing experience of the laser printer in any scenario, further track the debugging situation in each debugging and updating, implement debugging in a long time sequence range, and further improve the debugging effect.

In a first aspect, the present application provides a method for debugging a laser printer, which is characterized in that the method is applied to a debugging system of the laser printer, the debugging system of the laser printer includes the laser printer, a debugging terminal and an operation server in communication connection with the laser printer and the debugging terminal, printer usage information of different laser printers is stored in the operation server, and the method includes:

the laser printer sends application scene information to the operation server in the working process, wherein the application scene information comprises one or more combinations of scene service type information, printer information or printing processing type information;

the operation server acquires application scene information of the laser printer, acquires corresponding debugging updating data according to the application scene information, and sends the corresponding debugging updating data to the laser printer, wherein the debugging updating data comprises chip debugging updating parameters of an SOC chip of the laser printer and debugging updating system data in a printing safety chip electrically connected with the SOC chip;

the laser printer updates the chip parameters of the SOC chip and the system data in the printing safety chip according to the debugging updating data, and sends updating completion information to the operation server after each updating is completed;

the operation server acquires debugging trace historical information which takes a current time node as a reference from the laser printer according to the updating completion information trace;

and the debugging terminal generates a debugging strategy aiming at the laser printer according to the debugging tracking history information.

In a second aspect, a debugging system of a laser printer in an embodiment of the present application is characterized in that the debugging system of the laser printer includes a laser printer, a debugging terminal, and an operation server in communication connection with the laser printer and the debugging terminal, and printer usage information of different laser printers is stored in the operation server;

the laser printer is used for sending the application scene information to the operation server in the working process, wherein the application scene information comprises one or more combinations of scene service type information, printer information or printing processing type information;

the operation server is used for acquiring application scene information of the laser printer, acquiring corresponding debugging updating data according to the application scene information, and sending the corresponding debugging updating data to the laser printer, wherein the debugging updating data comprises chip debugging updating parameters of an SOC chip of the laser printer and debugging updating system data in a printing safety chip electrically connected with the SOC chip;

the laser printer is used for updating the chip parameters of the SOC chip and the system data in the printing safety chip according to the debugging updating data and sending updating completion information to the operation server after each updating is completed;

the operation server is used for acquiring debugging trace historical information which takes a current time node as a reference from the laser printer according to the updating completion information trace;

and the debugging terminal is used for generating a debugging strategy aiming at the laser printer according to the debugging tracking history information.

In a third aspect, an embodiment of the present application provides an electronic device, which includes a processor, a memory, and a network interface. The memory and the network interface processor can be connected through a bus system. The network interface is configured to receive a message, the memory is configured to store a program, an instruction, or a code, and the processor is configured to execute the program, the instruction, or the code in the memory to perform the operations performed in the first aspect.

In a fourth aspect, embodiments of the present application provide a computer-readable storage medium having stored therein instructions that, when detected on a computer, cause the computer to perform the method of the first aspect.

Based on any one of the above aspects, in the embodiment of the application, in the working process of the laser printer, the application scene information is sent to the operation server, so that corresponding debugging update data is obtained from the operation server, then, the chip parameters of the SOC chip and the system data in the printing security chip are updated according to the debugging update data, and update completion information is sent to the operation server after each update is completed, the operation server tracks debugging trace history information obtained from the laser printer and based on the current time node, and the debugging terminal generates a debugging strategy for the laser printer according to the debugging trace history information. Therefore, adaptive dynamic debugging and updating can be carried out on chip parameters of the SOC chip and system data in the printing safety chip according to actual application scenes, so that the laser printer can achieve a better system adaptation effect under various application scenes, the printing experience of the laser printer under any scene is further enhanced, the debugging situation is further tracked at each debugging and updating so as to realize debugging in a long time sequence range, and the debugging effect is further improved.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are required to be used in the embodiments will be briefly described below, it should be understood that the following drawings only illustrate some embodiments of the present application and therefore should not be considered as limiting the scope, and for those skilled in the art, other related drawings can be obtained from the drawings without inventive effort.

Fig. 1 is an interactive schematic view of a debugging system of a laser printer according to an embodiment of the present application;

fig. 2 is a schematic flowchart of a debugging method of a laser printer according to an embodiment of the present application;

FIG. 3 is a flow chart illustrating various sub-steps included in step S140 in one possible implementation shown in FIG. 2;

FIG. 4 is a flow chart illustrating various sub-steps included in step S130 in one possible implementation shown in FIG. 2;

FIG. 5 is a flow chart illustrating various sub-steps included in step S150 in one possible implementation shown in FIG. 2;

fig. 6 is a block diagram schematically illustrating a structure of an electronic device for implementing the operation server, the laser printer, and the debugging terminal shown in fig. 1 according to an embodiment of the present disclosure.

Detailed Description

The present application will now be described in detail with reference to the drawings, and the specific operations in the method embodiments may also be applied to the apparatus embodiments or the system embodiments. In the description of the present application, "at least one" includes one or more unless otherwise specified. "plurality" means two or more. For example, at least one of A, B and C, comprising: a alone, B alone, a and B in combination, a and C in combination, B and C in combination, and A, B and C in combination. In this application, "/" means "or, for example, A/B may mean A or B; "and/or" herein is merely an association describing an associated object, and means that there may be three relationships, e.g., a and/or B, which may mean: a exists alone, A and B exist simultaneously, and B exists alone.

Fig. 1 is an interactive schematic diagram of a debugging system 10 of a laser printer according to an embodiment of the present application. For example, the commissioning system 10 for a laser printer may be an online commissioning platform for a laser printer, for example. The debugging system 10 of the laser printer may include an operation server 100, a laser printer 200, and a debugging terminal 300, and a processor for executing an instruction operation may be included in the operation server 100. The commissioning system 10 of the laser printer shown in fig. 1 is only one possible example, and in other possible embodiments, the commissioning system 10 of the laser printer may also include only a part of the components shown in fig. 1 or may also include other components.

In some embodiments, the operation server 100 may be a single operation server or a group of operation servers. The operation server group may be centralized or distributed (for example, the operation server 100 may be a distributed system). In some embodiments, the operation server 100 may be local or remote with respect to the terminal. For example, the operation server 100 may access information stored in the laser printer 200, the debug terminal 300, and the database, or any combination thereof, via a network. As another example, the operation server 100 may be directly connected to at least one of the laser printer 200, the debugging terminal 300, and a database to access information and/or data stored therein. In some embodiments, the operations server 100 may be implemented on a cloud platform; by way of example only, the cloud platform may include a private cloud, a public cloud, a hybrid cloud, a community cloud (community cloud), a distributed cloud, an inter-cloud, a multi-cloud, and the like, or any combination thereof. In some embodiments, the operation server 100, the laser printer 200, and the debugging terminal 300 may be implemented on the electronic device 200 having one or more components shown in fig. 2 in the embodiment of the present application.

In some embodiments, operations server 100 may include a processor. The processor may process information and/or data related to the service request to perform one or more of the functions described herein. For example, in a shared printing service, the processor may determine a target laser printer based on a print reservation request obtained from a commissioning terminal. A processor may include one or more processing cores (e.g., a single-core processor (S) or a multi-core processor (S)). Merely by way of example, a Processor may include a Central Processing Unit (CPU), an Application Specific Integrated Circuit (ASIC), an Application Specific Instruction Set Processor (ASIP), a Graphics Processing Unit (GPU), a Physical Processing Unit (PPU), a Digital Signal Processor (DSP), a Field Programmable Gate Array (FPGA), a Programmable Logic Device (PLD), a controller, a microcontroller Unit, a reduced Instruction Set computer (reduced Instruction Set computer), a microprocessor, or the like, or any combination thereof.

The network may be used for the exchange of information and/or data. In some embodiments, one or more components in the commissioning system 10 of the laser printer (e.g., the operations server 100, the laser printer 200, the commissioning terminal 300, and the database) may send information and/or data to other components. For example, the operation server 100 may acquire a print request to the laser printer 200 via a network. In some embodiments, the network may be any type of wired or wireless network, or combination thereof. Merely by way of example, Network 130 may include a wired Network, a Wireless Network, a fiber optic Network, a telecommunications Network, an intranet, the internet, a Local Area Network (LAN), a Wide Area Network (WAN), a Wireless Local Area Network (WLAN), a WLAN, a Metropolitan Area Network (MAN), a Wide Area Network (WAN), a Public Switched Telephone Network (PSTN), a bluetooth Network, a ZigBee Network, a Near Field Communication (NFC) Network, or the like, or any combination thereof. In some embodiments, the network may include one or more network access points. For example, the network may include wired or wireless network access points, such as base stations and/or network switching nodes, through which one or more components of the debugging system 10 of the laser printer may connect to the network to exchange data and/or information.

The aforementioned database may store data and/or instructions. In some embodiments, the database may store data obtained from laser printer 200 and/or commissioning terminal 300. In some embodiments, the database may store data and/or instructions for the exemplary methods described herein. In some embodiments, the database may include mass storage, removable storage, volatile Read-write Memory, or Read-Only Memory (ROM), among others, or any combination thereof. By way of example, mass storage may include magnetic disks, optical disks, solid state drives, and the like; removable memory may include flash drives, floppy disks, optical disks, memory cards, zip disks, tapes, and the like; volatile read-write Memory may include Random Access Memory (RAM); the RAM may include Dynamic RAM (DRAM), Double data Rate Synchronous Dynamic RAM (DDR SDRAM); static RAM (SRAM), Thyristor-Based Random Access Memory (T-RAM), Zero-capacitor RAM (Zero-RAM), and the like. By way of example, ROMs may include Mask Read-Only memories (MROMs), Programmable ROMs (PROMs), Erasable Programmable ROMs (PERROMs), Electrically Erasable Programmable ROMs (EEPROMs), compact disk ROMs (CD-ROMs), digital versatile disks (ROMs), and the like. In some embodiments, the database may be implemented on a cloud platform. By way of example only, the cloud platform may include a private cloud, a public cloud, a hybrid cloud, a community cloud, a distributed cloud, across clouds, multiple clouds, or the like, or any combination thereof.

In some embodiments, the database may be connected to a network to communicate with one or more components in the commissioning system 10 of the laser printer (e.g., the operations server 100, the laser printer 200, the commissioning terminal 300, etc.). One or more components in the commissioning system 10 of the laser printer may access data or instructions stored in a database via a network. In some embodiments, the database may be directly connected to one or more components in the commissioning system 10 of the laser printer (e.g., the operations server 100, the laser printer 200, the commissioning terminal 300, etc.); alternatively, in some embodiments, the database may also be part of the operations server 100.

Fig. 2 is a schematic flowchart of a debugging method of a laser printer according to an embodiment of the present application, where the debugging method of a laser printer according to the present application can be executed by the debugging system 10 of a laser printer shown in fig. 1, and the debugging method of a laser printer is described in detail below.

And step S110, the laser printer sends the information of the application scene to the operation server in the working process.

Step S120, the operation server obtains the application scene information of the laser printer, obtains corresponding debugging update data according to the application scene information, and sends the corresponding debugging update data to the laser printer.

And step S130, the laser printer updates the chip parameters of the SOC chip and the system data in the printing safety chip according to the debugging updating data, and sends updating completion information to the operation server after each updating is completed.

In step S140, the operation server acquires the debugging trace history information based on the current time node from the laser printer according to the update completion information trace.

And step S150, the debugging terminal generates a debugging strategy aiming at the laser printer according to the debugging trace history information.

In this embodiment, the laser printer may send the information of the application scenario to the operation server in real time or at regular intervals in any status process that can perform communication and data collection, such as a printing process or a power-on status process. The application scenario information may be selected according to actual requirements, for example, the application scenario information may include one or more combinations of scenario service type information, printer information, or print processing type information. The scene service type information may refer to a geographical location scene (e.g., a company, a home, a public place, etc.) where the laser printer is used, the printer information may refer to attribute information, ID information, storage information, etc. of the laser printer itself, and the print processing type information may refer to a print processing type currently used by the laser printer, such as color printing, black-and-white printing, ultra-long space printing, etc.

In order to solve the technical problem in the foregoing background art, the present embodiment may obtain corresponding debugging update data through the laser server operation server, where the debugging update data may include chip debugging update parameters of an SOC chip of the laser printer and debugging update system data in a printing security chip electrically connected to the SOC chip, for example. The chip debugging and updating parameters may be parameters required by various control instructions of the SOC chip during specific use, and the debugging and updating system data may be system software service data adopted by the printing security chip during a specific printing process.

On the basis, chip parameters of the SOC chip and system data in the printing safety chip are updated according to the debugging updating data, updating completion information is sent to the operation server after updating is completed every time, the operation server tracks and acquires debugging tracking history information with the current time node as the reference from the laser printer, and the debugging terminal can generate a debugging strategy for the laser printer according to the debugging tracking history information.

Therefore, the laser printer can achieve a better system adaptation effect in various application scenes, the printing experience of the laser printer in any scene is further enhanced, the debugging situation is further tracked in order to achieve debugging in a long time sequence range in each debugging updating, and the debugging effect is further improved.

In some possible designs, for step S140, in the prior art, for each debugging process, it is necessary to repeatedly rewrite all programs of the debugging process, and then perform the debugging process; therefore, the workload generated in the debugging processing process is large, and the processing efficiency is low.

Based on this, in order to solve or improve the above problem, please refer to fig. 3 in combination, step S140 can be implemented by the following sub-steps:

substep S141, obtaining printing process information and data to be debugged from the laser printer according to the updated information trace

And a substep S142, acquiring a debugging processing link file corresponding to the debugging processing type from the laser printer according to the debugging processing type.

And a substep S143, determining a target debug processing sublink file corresponding to the current time node according to the debug processing link file corresponding to the debug processing type.

And a substep S144 of acquiring debugging trace history information with the current time node as a reference from the laser printer according to the target debugging processing sub-link.

In this embodiment, the printing process information may be used to indicate debugging processing types, each debugging processing link file includes a plurality of debugging processing sub-link files, each debugging processing sub-link file in each debugging processing link file has an order relationship associated with the debugging processing type, each debugging processing sub-link file corresponds to a debugging processing mode, and each debugging processing sub-link file is used to perform a debugging processing process indicated by the debugging processing mode corresponding to the debugging processing sub-link file on the chip parameter of the SOC chip and the system data in the printing security chip.

Therefore, in the embodiment, the plurality of debugging processing sub-link files form the debugging processing link file in the chain combination form, and each debugging processing sub-link file can be called to be processed each time of debugging processing, so that a large number of programs of debugging processing procedures are not required to be written in each debugging process, the workload of debugging processing is reduced, and the debugging processing efficiency is improved. Meanwhile, the labor cost is reduced, and the debugging cost is further reduced. Moreover, after each debugging processing sub-link file in the debugging processing link file is adopted for debugging, as the debugging processing sub-link files have the sequence relation associated with the debugging processing type, debugging tracking history information taking the current time node as the reference can be conveniently acquired from the laser printer by taking any time node as the reference, and the progress in the debugging tracking process is greatly accelerated.

In some possible designs, based on the above description, regarding step S130, please refer to fig. 4, which may be implemented by the following sub-steps:

and a substep S131, acquiring a parameter combination to be updated and a system data combination to be updated corresponding to each debugging processing sublink file.

And a substep S132, inputting the parameter combination to be updated and the system data combination to be updated into each debugging processing sublink file so as to update the chip parameters of the SOC chip and the system data in the printing security chip.

In this embodiment, the parameter combination to be updated may include at least one chip debug parameter, and the system data combination to be updated may include at least one system data to be updated.

On this basis, for the substep S132, specifically, the update parameter of each update file library in the chip parameters of the SOC chip and the update data of each update database in the system data in the print security chip may be determined from each debug process sublink file according to the parameter combination to be updated and the system data combination to be updated.

And then, updating the chip parameters of the SOC chip and the system data in the printing security chip according to the updating parameters of each updating file library and the updating data of each updating database in the system data in the printing security chip.

Optionally, the parameter combination to be updated may include directory information of a key file of the update file library corresponding to the print processing type, an update authority identifier, an update range coefficient, and an update upper limit coefficient of the update file library corresponding to the print processing type.

Based on this, according to the parameter combination to be updated and the system data combination to be updated, the update parameter of each update file library in the chip parameters of the SOC chip and the update data of each update database in the system data in the print security chip are determined from each debug processing child link file, and specifically, the update parameters may be:

firstly, determining an update size coefficient of a parameter combination to be updated according to an update range coefficient of the parameter combination to be updated, then determining directory information of each key update file, and calculating a difference value between each key update file and each key file according to the directory information of each key update file, the directory information of the key files of an update file library corresponding to the printing processing type and the update authority identification of the update file library corresponding to the printing processing type.

And then, determining a first intermediate parameter of each key update file according to the update authority identifier of the update file library corresponding to the printing processing type and the difference value of each key update file, wherein the first intermediate parameter is the product of 1 minus the update authority identifier and the difference value.

And then, determining a second intermediate parameter of each key update file according to the first intermediate parameter, the update upper limit coefficient and the update size coefficient of each key update file, wherein the second intermediate parameter is the product of the first intermediate parameter minus the update upper limit coefficient and the update size coefficient.

And then, determining the update size coefficient of each key update file according to the preset initial update size coefficient of the parameter combination to be updated and the second intermediate parameter of each key update file.

And then, determining an updating strategy of each key updating file according to the updating size coefficient of each key updating file, wherein the updating strategy and the updating size coefficient have a one-to-one correspondence relationship.

Therefore, the chip parameters of the SOC chip can be correspondingly updated according to the updating strategy of a key updating file. Through the steps, different updating strategies can be determined for different key updating files in the parameter updating process, and the adaptability effect of parameter updating can be improved.

In some possible designs, aiming at step S150, the inventor finds, in a further research process, that the existing debugging scheme is difficult to automatically optimize the fuzzy and inaccurate debugging history information, requires a large amount of manual involvement, thus greatly increasing the manual processing burden, and also difficult to ensure the accuracy of the debugging strategy.

Based on this, in order to solve or improve the above problem, please refer to fig. 5, step S150 can be implemented by the following sub-steps:

and a substep S151, aiming at the debugged debugging history information in the debugging trace history information, identifying and processing the debugging processing information of the debugging history information with the same debugging processing type to obtain a closed feedback data flow graph.

And a substep S152, performing multi-classification processing on the debugging processing flows of different time nodes contained in the closed feedback data flow graph.

And a substep S153 of performing an atomic operation on the debug processing stream after the multi-classification processing, and converting the debug processing stream after the atomic operation into an atomic operation label.

And a substep S154, according to the obtained atomic operation labels, counting original debugging logs of the same kind of atomic operation labels, optimizing embedded application codes of the marked original debugging logs obtained by counting, and obtaining processed debugging history information labels.

In substep S155, the processed debugging history information is labeled, and the analysis is performed according to each set keyword, thereby generating a debugging strategy for the laser printer.

In this embodiment, by adopting the above processing manner, the debugging processing flows of different time nodes included in the closed feedback dataflow graph are subjected to multi-classification processing, and fuzzy and inaccurate debugging history information can be automatically optimized to obtain a subsequent accurate debugging strategy, so that a higher debugging continuous effect is achieved, the burden of manual processing is reduced, and the accuracy of the debugging strategy is also improved because the embedded application code can be automatically optimized.

In some possible designs, for the sub-step S152, in order to improve the degree of intelligence in the multi-classification processing process and the flexibility of the processing, the sub-step S152 may be specifically implemented by:

firstly, debugging processing flow information of any one first debugging processing flow of different time nodes contained in a closed feedback data flow graph is obtained, and the debugging processing flow attribute of the first debugging processing flow is determined according to the debugging processing flow information of the first debugging processing flow.

Next, a target scene corresponding to the first debugging processing flow is determined based on a debugging processing flow scene in the debugging processing flow information of the first debugging processing flow, and printer information of the laser printer and each laser printer associated with the laser printer is obtained from the server, where the printer information may include printer attributes.

Then, target printer information matching the debugging process stream attribute of the first debugging process stream may be determined, and a laser printer having printer information matching the target printer information may be selected from among the laser printers and the laser printers of the printing process type.

And then, according to the debugging processing stream attribute of the first debugging processing stream and the printing permission levels of the plurality of laser printers with the target printer information in the target scene, selecting the target laser printer which executes the first debugging processing stream from the plurality of laser printers with the target printer information, wherein the target laser printer also needs to execute a second debugging processing stream.

Then, after the print configuration information of the first debugging processing flow included in the debugging processing flow information of the first debugging processing flow is acquired, the print configuration information of the second debugging processing flow included in the debugging processing flow information of the second debugging processing flow is acquired.

On the basis, if the printing configuration information of the first debugging processing flow is overlapped with the printing configuration information of the second debugging processing flow, the first debugging processing flow is not matched with the second debugging processing flow. A first printer sequence of laser printers that generate a first debugging process stream is determined among laser printers other than the target laser printer and laser printers of the same print process type. A second printer sequence of the laser printers that generate the second debugging processing flow is determined among the laser printers other than the target laser printer and the laser printers of the same printing processing type.

Therefore, the debugging history information of the second laser printer is selected from the first printer sequence or the second printer sequence, and then the debugging processing flow of different time nodes contained in the data flow graph with closed feedback is subjected to multi-classification processing according to at least any one of the following steps:

if the first printer sequence does not include a printer matching the laser printer and the second printer sequence includes a printer matching the laser printer, then a second laser printer is selected from the second printer sequence.

If the first sequence of printers includes a printer matching a laser printer and the second sequence of printers does not include a printer matching a laser printer, then selecting a second laser printer from the first sequence of printers.

And if the first printer sequence and the second printer sequence both comprise printers matched with the laser printers, determining to select the second laser printer from the first printer sequence or the second printer sequence according to the printing authority levels generated by the first debugging processing flow and the second debugging processing flow in the target laser printer.

In this embodiment, by adopting the above design, the debugging processing flows of different time nodes included in the closed feedback dataflow graph can be automatically subjected to multi-classification processing based on the attribute of the debugging processing flow, so that the intelligent degree in the multi-classification processing process and the processing flexibility are improved, the operation of the user is reduced, and the user experience can be improved.

In some possible designs, for the sub-step S154, in order to improve the accuracy of the debugging strategy, the quick and accurate generation of the debugging strategy is implemented, and the time difference of the generation of the debugging strategy is shortened, the sub-step S154 may be implemented specifically by:

firstly, acquiring an embedded code line at a first preset position in an embedded application code of a marked original debugging log obtained through statistics, and detecting a first debugging code plate block in the embedded code line to obtain a first positioning result corresponding to the first debugging code plate block.

Then, detecting other debugging code blocks in the intercepted embedded code line according to the positioning result corresponding to the previous debugging code block to obtain second positioning results respectively corresponding to the other debugging code blocks;

and then, continuously acquiring an embedded code line at a second preset position in the embedded application code and obtaining a corresponding third positioning result, wherein the first preset position and the second preset position are positions associated with the current time node indicated in the debugging and tracking history information.

And then, adding a corresponding positioning optimization code at a position corresponding to the embedded application code of the marked original debugging log obtained through statistics according to the first positioning result, the second positioning result and the third positioning result to obtain a processed debugging history information mark, wherein the positioning optimization code is a preset optimization code associated with the laser printer, and the optimization code is related to the printing processing type of the laser printer.

Therefore, the code optimization is carried out by identifying the optimized position according to each positioning result, and finally, the optimized debugging history information is labeled to generate the debugging strategy, so that the accuracy of the debugging strategy is improved, the debugging strategy is rapidly and accurately generated, and the time difference of the generation of the debugging strategy is shortened.

In some possible designs, for the sub-step S155, since the data amount of the debugging parameter is decreased due to the increase of the time interval in each debugging process, in order to better utilize the debugging history information label, the analysis process is generally required to be performed more densely, which results in the efficiency reduction, and the computing power consumption and the hardware cost are increased. Based on this, in order to solve or improve the above problem, the sub-step S154 may be specifically implemented by:

firstly, marking the processed debugging history information as input data, and extracting a key debugging history sequence marked by the processed debugging history information according to each set keyword.

Next, a debug policer for the critical debug history sequence is constructed. The debugging strategy device can comprise a sub debugging trace sequence and a father debugging trace sequence which is connected with the two sub debugging trace sequences, wherein the sub debugging trace sequence is used for representing variables to be debugged of a key debugging history sequence, and the father debugging trace sequence is used for representing the incidence relation between the variables to be debugged corresponding to the two connected sub debugging trace sequences. The variables to be debugged comprise debugging variables of chip parameters of the SOC chip and debugging variables of system data in the printing safety chip, the sub-debugging tracking sequences comprise a first debugging tracking sequence and a second debugging tracking sequence, the first debugging tracking sequence is used for representing the debugging variables of the chip parameters of the SOC chip, and the second debugging tracking sequence is used for representing the debugging variables of the system data in the printing safety chip.

Then, the first debugging trace sequence in the debugging strategy device is copied into more than two third debugging trace sequences, any one of the third debugging trace sequences has an association relation with a plurality of second association debugging trace sequences, the plurality of second association debugging trace sequences in the plurality of second association debugging trace sequences have the same association relation with the adjacent third debugging trace sequences, the second association debugging trace sequences have an association relation with at least one third debugging trace sequence, and the second association debugging trace sequences are the second debugging trace sequences having an association relation with the first debugging trace sequence.

And then, replacing the first debugging trace sequence in the corresponding debugging strategy device by the third debugging trace sequence to obtain a debugging strategy after replacing the debugging trace sequence, and generating the debugging strategy for the laser printer according to the debugging strategy device after replacing the debugging trace sequence.

Therefore, by adopting the design, the analysis efficiency of the debugging strategy can be improved, and the calculation power consumption and the hardware cost are reduced.

In some possible designs, in the process of generating the debugging strategy for the laser printer according to the debugging strategy device after replacing the debugging trace sequence, in order to accurately verify the accuracy of each debugging strategy in the process of generating the debugging strategy for the laser printer and further improve the reliability of the debugging strategy, the embodiment may specifically output a plurality of to-be-debugged strategies according to the debugging strategy device after replacing the debugging trace sequence, and acquire the debugging confidence value of each to-be-debugged strategy in the debugging strategy device in the plurality of to-be-debugged strategies, and then acquire the debugging interval set of each to-be-debugged strategy from the preset interval information table according to the debugging confidence value of each to-be-debugged strategy, where the debugging interval set includes a plurality of debugging directory range intervals and corresponding debugging times.

Then, further according to the debug directory range interval of the undetermined debug strategy associated with each undetermined debug strategy, debug interval information of the undetermined debug strategy is selected from the debug interval set corresponding to the undetermined debug strategy, wherein the debug interval information comprises the debug directory range interval and the corresponding debug times.

Then, the lower limit value of the debugging interval of each to-be-debugged strategy can be obtained by calculation according to the debugging processing type of each to-be-debugged strategy and the debugging directory range interval of each to-be-debugged strategy, and then a preset debugging information table is inquired according to the lower limit value of the debugging interval and the debugging times of each to-be-debugged strategy to obtain the debugging information streams of the to-be-debugged strategies. And then, determining a first debugging code line of a time node in the debugging information flow of each to-be-debugged strategy, which is closest to the current time node, and a first code line and a second code line of a target code line by using the first debugging code line, wherein the time sequence of the first code line is smaller than that of the second code line.

Then, a debugging code line meeting a first condition in the first code line can be determined, and a first weight corresponding to the first code line is determined according to the average value of the difference between the debugging confidence of the debugging code line meeting the first condition and a preset threshold; and the debugging code line with the debugging code behavior debugging confidence coefficient meeting the first condition smaller than a preset threshold value.

Then, according to a first weight corresponding to the first code line, performing weighted average on the debugging value of the first debugging code line and the feedback value corresponding to the first code line to obtain a pre-debugging value of the first debugging code line, where the feedback value corresponding to the first code line is an average value of the debugging values of the debugging code lines meeting the first condition in the first code line.

Then, according to a first weight corresponding to the first code line, a weighted average may be performed on the debug value of the first debug code line and the pre-debug value of the first code line to obtain a first simulated debug value of the first debug code line, and meanwhile, the first debug code line is subjected to simulated suppression according to the debug code line in the second code line to obtain a second simulated debug value of the first debug code line after the simulated suppression.

Then, according to the second weight, the first simulated debugging value and the second simulated debugging value are weighted and averaged, whether the simulated debugging value after weighted and averaged is larger than the set simulated debugging value or not is judged, and if the simulated debugging value after weighted and averaged is larger than the set simulated debugging value, the to-be-determined debugging strategy is determined as the debugging strategy for the laser printer. Or if the simulation debugging value after weighted average is not larger than the set simulation debugging value, configuring the to-be-debugged strategy into a dormant state, wherein the to-be-debugged strategy does not participate in the tracking debugging process of the laser printer in the dormant state.

Therefore, the accuracy of each debugging strategy can be accurately verified in the process of generating the debugging strategy of the laser printer, the reliability of the debugging strategy is further improved, and the undetermined debugging strategies can be mixed and analyzed by determining different weights, so that the logic redundancy is reduced.

In addition, in some possible designs, the debugging terminal may send a debugging policy generated according to the debugging trace history information to the operation server, and the operation server may generate a target debugging policy that integrates the debugging policy and the application scenario information according to the generated debugging policy and in combination with application scenario information subsequently sent by the laser printer, and send the target debugging policy to the laser printer for further debugging. Therefore, the debugging accuracy can be further improved by combining the debugging strategy and the target debugging strategy of the application scene information.

Based on the above description, in some possible designs, the operation server generates a target debugging policy that integrates the debugging policy and the application scenario information according to the generated debugging policy and by combining the application scenario information sent by the laser printer, which may specifically be implemented as follows:

and selecting a first greedy rule sequence of the debugging strategy and a second greedy rule sequence of the application scene information from a pre-stored greedy rule sequence table according to the debugging strategy and the application scene information, calling a printing function, and determining a first printing function value of each debugging key directory contained in the first greedy rule sequence and a second printing function value of each debugging key directory contained in the second greedy rule sequence through the printing function. Then, a first debugging condition of the debugging strategy and a second debugging condition of the application scenario information are determined by comparing a first printing function value of each debugging key directory contained in the first greedy rule sequence with a second printing function value of each debugging key directory contained in the second greedy rule sequence. The greedy rule sequence table is preset and stored, and each greedy rule sequence in the greedy rule sequence table can be modified according to actual conditions. And then, determining the confidence of each debugging key directory in the debugging strategy according to the first debugging condition, and performing fusion analysis on the debugging strategy and the application scene information according to the confidence of each debugging key directory in the debugging strategy to generate a target debugging strategy integrating the debugging strategy and the application scene information.

For example, the debugging strategy and the application scenario information may be fused according to the confidence of each debugging key directory in the debugging strategy to obtain an initial fusion strategy, the initial fusion strategy is decoded to obtain an initial reconstruction fusion strategy, the debugging strategy is at least partially processed according to the difference between the debugging strategy and the initial reconstruction fusion strategy to obtain a first refreshing debugging strategy, a historical debugging strategy associated with the debugging strategy is obtained, and the historical debugging strategy is at least partially processed according to the difference between the historical debugging strategy and the initial reconstruction fusion strategy to obtain a second refreshing debugging strategy. And generating a target debugging strategy according to the initial fusion strategy, the first refreshing debugging strategy and the second refreshing debugging strategy. Thus, accumulation and diffusion of errors due to fusion prediction quantization can be prevented, and fusion efficiency and error control are balanced.

Fig. 6 is a schematic structural diagram of an electronic device 400 for implementing the operation server 100, the laser printer 200, and the debugging terminal 300, according to an embodiment of the present disclosure, as shown in fig. 6, the operation server 100 may include a network interface 410, a machine-readable storage medium 420, a processor 430, and a bus 440. The number of the processors 430 may be one or more, and one processor 430 is taken as an example in fig. 6; the network interface 410, the machine-readable storage medium 420, and the processor 430 may be connected by a bus 440 or otherwise, as exemplified by the connection by the bus 440 in fig. 6.

The machine-readable storage medium 420 is a computer-readable storage medium, and can be used to store software programs, computer-executable programs, and modules, such as program instructions/modules corresponding to the debugging method of the laser printer in the embodiment of the present application. The processor 430 executes various functional applications and data processing of the terminal device by detecting software programs, instructions and modules stored in the machine-readable storage medium 420, that is, the debugging method of the laser printer is implemented, and details are not described herein.

The machine-readable storage medium 420 may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required for at least one function; the storage data area may store data created according to the use of the terminal, and the like. Further, the machine-readable storage medium 420 may be either volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory.

Processor 430 may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method embodiments may be performed by integrated logic circuits of hardware or instructions in the form of software in the processor 430.

Electronic device 100 may interact with other devices via communication interface 410. Communication interface 410 may be a circuit, bus, transceiver, or any other device that may be used to exchange information. Processor 430 may send and receive information using communication interface 410.

In the above embodiments, the implementation may be wholly or partially realized by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loaded and executed on a computer, cause the processes or functions described in accordance with the embodiments of the application to occur, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, the computer instructions may be transmitted from one website site, computer, operations server, or data center to another website site, computer, operations server, or data center by wire (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wirelessly (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device, such as a operations server, data center, etc., that includes one or more of the available media. The usable medium may be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., Solid State Disk (SSD)), among others.

Embodiments of the present application are described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

It will be apparent to those skilled in the art that various changes and modifications may be made in the embodiments of the present application without departing from the spirit and scope of the application. Thus, if such modifications and variations of the embodiments of the present application fall within the scope of the claims of the present application and their equivalents, the present application is also intended to encompass such modifications and variations.

Claims

1. The debugging method of the laser printer is characterized in that the debugging method is applied to a debugging system of the laser printer, the debugging system of the laser printer comprises the laser printer, a debugging terminal and an operation server which is in communication connection with the laser printer and the debugging terminal, printer use information of different laser printers is stored in the operation server, and the method comprises the following steps:

the debugging terminal generates a debugging strategy aiming at the laser printer according to the debugging tracking history information;

the step of obtaining the debugging trace history information with the current time node as the reference from the laser printer by the operation server according to the updating completion information trace comprises the following steps:

acquiring printing process information and data to be debugged from the laser printer according to the updating completion information track, wherein the printing process information is used for representing the debugging processing type;

according to the debugging processing type, a debugging processing link file corresponding to the debugging processing type is obtained from the laser printer in a tracking mode;

each debugging processing link file comprises a plurality of debugging processing sub-link files, each debugging processing sub-link file in each debugging processing link file has an order relation associated with the debugging processing type, each debugging processing sub-link file corresponds to a debugging processing mode, and each debugging processing sub-link file is used for carrying out the debugging processing process indicated by the debugging processing mode corresponding to the debugging processing sub-link file on the chip parameters of the SOC chip and the system data in the printing security chip;

determining a target debugging processing sub-link file corresponding to the current time node according to the debugging processing link file corresponding to the debugging processing type;

and acquiring debugging trace historical information with the current time node as the reference from the laser printer according to the target debugging processing sub-link file.

2. The debugging method of the laser printer according to claim 1, wherein the step of updating the chip parameters of the SOC chip and the system data in the printing security chip by the laser printer according to the debugging update data comprises:

acquiring a parameter combination to be updated and a system data combination to be updated corresponding to each debugging processing sub-link file, wherein the parameter combination to be updated comprises at least one chip debugging parameter, and the system data combination to be updated comprises at least one system data to be updated;

and inputting the parameter combination to be updated and the system data combination to be updated into each debugging processing sub-link file so as to update the chip parameters of the SOC chip and the system data in the printing security chip.

3. The debugging method of the laser printer according to claim 2, wherein the step of inputting the parameter combination to be updated and the system data combination to be updated into each of the debugging process child link files to update the chip parameters of the SOC chip and the system data in the print security chip comprises:

according to the parameter combination to be updated and the system data combination to be updated, determining the updating parameters of each updating file library in the chip parameters of the SOC chip and the updating data of each updating database in the system data in the printing security chip from each debugging processing sub-link file;

updating the chip parameters of the SOC chip and the system data in the printing safety chip according to the updating parameters of each updating file library and the updating data of each updating database in the system data in the printing safety chip;

the parameter combination to be updated comprises directory information of key files of an update file library corresponding to the printing processing type, an update authority identifier, an update range coefficient and an update upper limit coefficient of the update file library corresponding to the printing processing type;

the step of determining, from each of the debug process sub-link files, an update parameter of each update file library of chip parameters of the SOC chip and an update data of each update database of system data in the print security chip according to the combination of the parameters to be updated and the combination of the system data to be updated includes:

determining an updating size coefficient of the parameter combination to be updated according to the updating range coefficient of the parameter combination to be updated;

determining directory information of each key update file, and calculating a difference value between each key update file and each key file according to the directory information of each key update file, the directory information of the key file of the update file library corresponding to the printing processing type and the update authority identification of the update file library corresponding to the printing processing type;

determining a first intermediate parameter of each key update file according to the update authority identifier of the update file library corresponding to the printing processing type and the difference value of each key update file, wherein the first intermediate parameter is obtained by subtracting the product of the update authority identifier and the difference value from 1;

determining a second intermediate parameter of each key update file according to the first intermediate parameter of each key update file, the update upper limit coefficient and the update size coefficient, wherein the second intermediate parameter is the product of the first intermediate parameter minus the update upper limit coefficient and the update size coefficient;

determining an update size coefficient of each key update file according to a preset initial update size coefficient of the parameter combination to be updated and a second intermediate parameter of each key update file;

determining an updating strategy of each key updating file according to the updating size coefficient of each key updating file, wherein the updating strategy and the updating size coefficient have a one-to-one correspondence relationship;

and correspondingly updating the chip parameters of the SOC chip according to the updating strategy of the key updating file.

4. The debugging method of a laser printer according to any one of claims 1 to 3, wherein the step of generating, by the debugging terminal, a debugging policy for the laser printer based on the debugging trace history information includes:

aiming at debugged debugging history information in the debugging trace history information, identifying and processing the debugging processing information of the debugging history information in the same debugging processing type to obtain a closed feedback data flow graph;

carrying out multi-classification processing on debugging processing flows of different time nodes contained in the closed feedback data flow graph;

carrying out atomic operation on the debugging processing flow after the multi-classification processing, and converting the debugging processing flow after the atomic operation into an atomic operation label;

according to the obtained atomic operation labels, counting original debugging logs of the same kind of atomic operation labels, optimizing embedded application codes of the marked original debugging logs obtained through counting, and obtaining processed debugging history information labels;

and marking the processed debugging history information, analyzing according to each set keyword, and generating a debugging strategy for the laser printer.

5. The debugging method of the laser printer according to claim 4, wherein the step of performing multi-classification processing on the debugging processing flows of different time nodes contained in the closed-feedback dataflow graph comprises:

acquiring debugging processing flow information of any first debugging processing flow of different time nodes contained in the closed feedback data flow graph;

determining the attribute of the debugging processing flow of the first debugging processing flow according to the debugging processing flow information of the first debugging processing flow;

determining a target scene corresponding to the first debugging processing flow based on a debugging processing flow scene in the debugging processing flow information of the first debugging processing flow;

acquiring the laser printers and printer information of each laser printer related to the laser printers from the server, wherein the printer information comprises printer attributes;

determining target printer information matched with the debugging processing flow attribute of the first debugging processing flow;

selecting a laser printer with printer information matched with target printer information from the laser printer and the laser printer with the same printing processing type;

selecting a target laser printer executing a first debugging processing flow from the plurality of laser printers with target printer information according to the debugging processing flow attribute of the first debugging processing flow and the printing permission levels of the plurality of laser printers with the target printer information in a target scene, wherein the target laser printer also needs to execute a second debugging processing flow;

acquiring printing configuration information of the first debugging processing flow, wherein the debugging processing flow information of the first debugging processing flow comprises the printing configuration information of the first debugging processing flow;

acquiring printing configuration information of the second debugging processing flow, which is included in debugging processing flow information of the second debugging processing flow;

if the printing configuration information of the first debugging processing flow is overlapped with the printing configuration information of the second debugging processing flow, the first debugging processing flow is not matched with the second debugging processing flow;

determining a first printer sequence of laser printers that generate a first debugging processing flow among the laser printers other than the target laser printer and the laser printers of the same printing processing type;

determining a second printer sequence of laser printers that generate a second debugging processing flow among the laser printers other than the target laser printer and the laser printers of the same printing processing type;

selecting debugging history information of a second laser printer from the first printer sequence or the second printer sequence to carry out multi-classification processing on debugging processing flows of different time nodes contained in the closed feedback data flow graph according to at least any one of the following steps:

selecting a second laser printer from the second printer sequence if the first printer sequence does not include a printer matching the laser printer and the second printer sequence includes a printer matching the laser printer;

selecting a second laser printer from the first printer sequence if the first printer sequence includes a printer matching the laser printer and the second printer sequence does not include a printer matching the laser printer;

and if the first printer sequence and the second printer sequence both comprise printers matched with the laser printer, determining to select the second laser printer from the first printer sequence or the second printer sequence according to the generated printing permission levels of the first debugging processing stream and the second debugging processing stream in the target laser printer.

6. The debugging method of a laser printer according to claim 4, wherein the step of optimizing the embedded application code of the marked original debugging log obtained by statistics to obtain the processed debugging history information mark comprises:

acquiring an embedded code line at a first preset position in the embedded application code of the marked original debugging log obtained by statistics;

detecting a first debugging code plate in the embedded code line to obtain a first positioning result corresponding to the first debugging code plate;

detecting other debugging code plates in the embedded code line according to the positioning result corresponding to the previous debugging code plate to obtain second positioning results corresponding to the other debugging code plates respectively;

continuing to acquire an embedded code line at a second preset position in the embedded application code and obtaining a corresponding third positioning result, wherein the first preset position and the second preset position are positions associated with the current time node indicated in the debugging and tracking history information;

and adding corresponding positioning optimization codes at corresponding positions of embedded application codes of the marked original debugging logs obtained through statistics according to the first positioning result, the second positioning result and the third positioning result to obtain processed debugging history information marks, wherein the positioning optimization codes are preset optimization codes associated with the laser printer, and the optimization codes are related to the printing processing type of the laser printer.

7. The method of claim 4, wherein the step of labeling the processed debugging history information, analyzing the labeling according to the set keywords, and generating the debugging strategy for the laser printer includes:

marking the processed debugging history information as input data, and extracting a key debugging history sequence marked by the processed debugging history information according to each set keyword;

a debug policer to construct said key debug history sequence, said debug policer comprising a child debug trace sequence and a parent debug trace sequence connecting two of said child debug trace sequences, the sub debugging trace sequence is used for representing variables to be debugged of the key debugging history sequence, the father debugging trace sequence is used for representing the incidence relation between the variables to be debugged corresponding to the connected two sub debugging trace sequences, wherein the variables to be debugged comprise debugging variables of chip parameters of the SOC chip and debugging variables of system data in the printing security chip, the sub-debug trace sequence includes a first debug trace sequence and a second debug trace sequence, the first debug trace sequence is used for representing a debug variable of a chip parameter of the SOC chip, the second debugging trace sequence is used for representing debugging variables of system data in the printing security chip;

copying the first debugging trace sequence in the debugging strategy device into more than two third debugging trace sequences, wherein any one of the third debugging trace sequences has an association relation with a plurality of second associated debugging trace sequences, and the plurality of second associated debugging trace sequences in the plurality of second associated debugging trace sequences have the same association relation with the adjacent third debugging trace sequences, the second associated debugging trace sequences have an association relation with at least one third debugging trace sequence, and the second associated debugging trace sequences are the second debugging trace sequences having an association relation with the first debugging trace sequences;

replacing the first debugging trace sequence in the corresponding debugging strategy device by the third debugging trace sequence to obtain the debugging strategy device after replacing the debugging trace sequence;

and generating a debugging strategy aiming at the laser printer according to the debugging strategy device after replacing the debugging trace sequence.

8. The method of debugging a laser printer according to claim 7, wherein the step of generating a debugging strategy for the laser printer from the debugging strategy after the substitute debugging trace sequence comprises:

outputting a plurality of to-be-determined debugging strategies according to the debugging strategy device after replacing the debugging trace sequence;

acquiring a debugging confidence value of each to-be-debugged strategy in the debugging strategy device;

acquiring a debugging interval set of each to-be-debugged strategy from a preset interval information table according to the debugging confidence value of each to-be-debugged strategy, wherein the debugging interval set comprises a plurality of debugging catalog range intervals and corresponding debugging times;

selecting debugging interval information of the undetermined debugging strategy from a debugging interval set corresponding to the undetermined debugging strategy according to a debugging catalog range interval of the undetermined debugging strategy associated with each undetermined debugging strategy, wherein the debugging interval information comprises the debugging catalog range interval and corresponding debugging times;

calculating to obtain a debugging interval lower limit value of each to-be-debugged strategy according to the debugging processing type of each to-be-debugged strategy and the debugging directory range interval of each to-be-debugged strategy;

inquiring a preset debugging information table to obtain debugging information streams of the multiple to-be-debugged strategies according to the debugging interval lower limit value and the debugging times of each to-be-debugged strategy;

determining a first debugging code line of a time node in a debugging information stream of each to-be-debugged strategy, which is closest to a current time node, and a first code line and a second code line of a target code line by using the first debugging code line, wherein the time sequence of the first code line is smaller than that of the second code line;

determining debugging code lines meeting a first condition in the first code lines, and determining a first weight corresponding to the first code lines according to an average value of differences between debugging confidence degrees of the debugging code lines meeting the first condition and a preset threshold; the debugging code line meeting the first condition is a debugging code line of which the debugging confidence coefficient is smaller than the preset threshold;

according to a first weight corresponding to the first code line, carrying out weighted average on a debugging value of the first debugging code line and a feedback value corresponding to the first code line to obtain a pre-debugging value of the first debugging code line, wherein the feedback value corresponding to the first code line is an average value of the debugging values of the debugging code lines meeting a first condition in the first code line;

according to a first weight corresponding to the first code line, carrying out weighted average on the debugging value of the first debugging code line and the pre-debugging value of the first code line to obtain a first simulated debugging value of the first debugging code line;

performing analog suppression on the first debugging code line according to the debugging code line in the second code line to obtain a second analog debugging value of the first debugging code line after analog suppression;

according to a second weight, carrying out weighted average on the first simulation debugging value and the second simulation debugging value, and judging whether the simulation debugging value after weighted average is larger than a set simulation debugging value or not;

if the simulation debugging value after weighted average is larger than the set simulation debugging value, determining the to-be-determined debugging strategy as the debugging strategy for the laser printer;

and if the weighted average simulated debugging value is not greater than the set simulated debugging value, configuring the to-be-debugged strategy into a dormant state, wherein the to-be-debugged strategy does not participate in the tracking debugging process of the laser printer in the dormant state.

9. The debugging system of the laser printer is characterized by comprising the laser printer, a debugging terminal and an operation server in communication connection with the laser printer and the debugging terminal, wherein printer use information of different laser printers is stored in the operation server;

the debugging terminal is used for generating a debugging strategy aiming at the laser printer according to the debugging tracking historical information;

the operation server acquires debugging trace history information with the current time node as the reference from the laser printer according to the updating completion information trace, and the debugging trace history information comprises the following steps: