Laser label printing method and device, storage medium and electronic equipment

Abstract

The invention discloses a laser label printing method and device, a storage medium and electronic equipment, and relates to the technical field of laser, and the method comprises the steps that to-be-printed label information sent by a first client is received; generating printing task approval information corresponding to the to-be-printed label information, and sending the printing task approval information to a second client; in response to the received approval passing information sent by the second client, determining a target printing device for printing the to-be-printed label information; and sending a printing execution instruction corresponding to the to-be-printed label information to the target printing equipment. The to-be-printed label information is compressed through the first client and sent to the server, so that the processing efficiency is improved; printing task approval information is generated and submitted to the second client side for approval, and safety is improved; target printing equipment is determined, accurate matching of printing tasks and equipment resources is achieved, and the resource utilization rate is increased; the standardized printing execution instruction is sent to the target printing equipment, and the printing efficiency is improved.

Description

Technical Field

[0001] This application relates to the field of laser technology, and in particular to a laser label printing method, apparatus, storage medium and electronic device. Background Technology

[0002] In fields such as industrial manufacturing, logistics traceability, and precision instruments, laser label printing features high marking accuracy, strong wear resistance, and excellent anti-counterfeiting performance, making it a core technology for achieving product information visualization and traceability.

[0003] In current technologies, the data processing and printing execution stages of laser label printing are both completed within the same architecture, mainly using a CS (client / server) architecture or a BS (browser / server) architecture.

[0004] However, existing laser label printing technology requires a lot of time to adjust the data format during the data processing stage or to change the printing equipment during the printing execution stage, resulting in low printing efficiency. Summary of the Invention

[0005] In view of this, this application provides a laser label printing method, apparatus, storage medium and electronic device, the main purpose of which is to improve the problem that the existing technology requires a lot of time to adjust the data format in the data processing stage or to change the printing equipment in the printing execution stage, which leads to low printing efficiency.

[0006] Firstly, this application provides a method for printing all-laser labels, including:

[0007] The system receives label information to be printed sent by a first client. The label information to be printed is obtained by compressing the label information according to a target format with a compression ratio greater than or equal to a predetermined compression ratio threshold.

[0008] Generate print task approval information corresponding to the label information to be printed, and send the print task approval information to the second client. The print task approval information is used by the second client for approval.

[0009] In response to receiving the approval information corresponding to the print task approval information sent by the second client, the target printing device for printing the label information to be printed is determined;

[0010] A print execution command corresponding to the label information to be printed is sent to the target printing device. The print execution command is used to control the target printing device to print the label information to be printed.

[0011] Optionally, receiving the label information to be printed sent by the first client includes:

[0012] The authentication token sent by the first client is received through the upload interface corresponding to the first client. The authentication token is sent to the first client after determining that the first client has passed the initial authentication.

[0013] The authentication token is used to determine the first client's permission information and key validity information;

[0014] If the permission information and the key validity information are determined to be correct, the system receives the label information to be printed sent by the first client.

[0015] Optionally, receiving the label information to be printed sent by the first client when the authorization information and the key validity information are determined to be correct includes:

[0016] If the permission information and the key validity information are determined to be correct, the fragmented data corresponding to the label information to be printed sent by the first client is received;

[0017] The fragmented data is stored in a temporary cache according to the fragment index to generate the label information to be printed.

[0018] Optionally, generating print task approval information corresponding to the label information to be printed and sending the print task approval information to the second client includes:

[0019] The information of the label to be printed is encrypted to generate the approval information for the printing task;

[0020] The print job approval information is sent asynchronously to the second client via a message queue.

[0021] Optionally, before sending the print execution command corresponding to the label information to be printed to the target printing device, the method further includes:

[0022] The label information to be printed is parsed to obtain the label metadata corresponding to the label information to be printed, and the label metadata is stored in a temporary cache;

[0023] Sending the print execution command corresponding to the label information to be printed to the target printing device includes:

[0024] The label metadata is retrieved from the temporary cache, and the print execution instruction is generated based on the label metadata.

[0025] Optionally, after sending the print execution command corresponding to the label information to be printed to the target printing device, the method further includes:

[0026] In response to receiving print completion information sent by the target printing device, the print completion information is parsed to obtain the print log of the target printing device;

[0027] The printed log is sent to the second network device.

[0028] Optionally, after sending the print execution command corresponding to the label information to be printed to the target printing device, the method further includes:

[0029] In response to the detection of an interruption in the target printing device by the service monitoring module, the progress information of the target printing device is obtained at preset time intervals.

[0030] Based on the progress information, an interruption alarm message corresponding to the target printing device is generated.

[0031] Secondly, this application provides a laser label printing apparatus, comprising:

[0032] The receiving module is configured to receive label information to be printed sent by a first client, wherein the label information to be printed is obtained by compression processing according to a target format with a compression ratio greater than or equal to a predetermined compression ratio threshold;

[0033] The generation module is configured to generate print task approval information corresponding to the label information to be printed, and send the print task approval information to the second client, wherein the print task approval information is used by the second client for approval.

[0034] The response module is configured to determine the target printing device for printing the label information to be printed in response to receiving approval information corresponding to the print task approval information sent by the second client;

[0035] The sending module is configured to send a print execution command corresponding to the label information to be printed to the target printing device, the print execution command being used to control the target printing device to print the label information to be printed.

[0036] Thirdly, this application provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the laser label printing method described in the first aspect.

[0037] Fourthly, this application provides an electronic device, including a storage medium, a processor, and a computer program stored on the storage medium and executable on the processor, wherein the processor executes the computer program to implement the laser label printing method described in the first aspect.

[0038] By employing the above technical solutions, this application provides a laser label printing method, apparatus, storage medium, and electronic device. Compared with the prior art, this application receives label information to be printed sent by a first client, which is obtained by compressing the label information according to a target format with a compression ratio greater than or equal to a predetermined compression ratio threshold; generates printing task approval information corresponding to the label information to be printed and sends the printing task approval information to a second client, which is used for approval by the second client; in response to receiving the approval information corresponding to the printing task approval information sent by the second client, determines the target printing device for printing the label information to be printed; and sends a printing execution command corresponding to the label information to be printed to the target printing device, which is used to control the target printing device to print the label information to be printed. This application uses a first client to compress the label information to be printed into the target format and send it to the server. By using a unified compression format, the server's parsing cost is reduced and processing efficiency is improved. Print task approval information is generated and submitted to a second client for approval. A security audit mechanism is established to improve security. Based on this, after obtaining the approval information, the server coordinates and determines the target printing device to achieve precise matching between printing tasks and equipment resources, thereby improving resource utilization. Standardized print execution instructions are sent to the target printing device to shorten the task response cycle and comprehensively improve the overall efficiency of laser label printing. Attached Figure Description

[0039] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0040] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, for those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0041] Figure 1 A schematic flowchart of a laser label printing method provided in an embodiment of this application is shown;

[0042] Figure 2 A schematic flowchart of a laser label printing method provided in an embodiment of this application is shown;

[0043] Figure 3 This paper shows a schematic diagram of the structure of a laser label printing device provided in an embodiment of this application;

[0044] Figure 4 A schematic diagram of the structure of an electronic device provided in an embodiment of this application is shown. Detailed Implementation

[0045] The embodiments of this application will now be described in more detail with reference to the accompanying drawings. It should be noted that, unless otherwise specified, the embodiments and features described herein can be combined with each other.

[0046] To address the issue of low printing efficiency caused by the significant time required for data format adjustments during data processing or printing device changes during the printing process in current technologies, this embodiment provides a laser label printing method. Figure 1 As shown, the method includes:

[0047] Step 101: Receive the label information to be printed sent by the first client.

[0048] The label information to be printed is obtained by compressing a target format with a compression ratio greater than or equal to a predetermined compression ratio threshold.

[0049] In this embodiment, the first client can be a label design terminal built on a client-server architecture, possessing local graphic editing and data compression capabilities. For example, the first client can be a Windows 10 computer (4GB memory, JRE 1.8) with the Java Swing graphics editing engine installed.

[0050] In this embodiment, based on the color complexity of the label image, the target format can be a specific data compression format used to compress the label information to be printed, and can be a format with a compression ratio greater than or equal to a predetermined compression ratio threshold. For example, when the number of colors in the label information to be printed is less than or equal to 16, the compression ratio is 1:4, and the target format can be RLE4 compression format; when the number of colors in the label information to be printed is greater than 16, the compression ratio is 1:2, and the target format can be RLE8 compression format.

[0051] In this embodiment, the operator can complete the graphic design of the label to be printed through a first client. The first client automatically selects the target format for compression based on the color complexity of the label image, and then sends the compressed label information to the server. The compression process can include, but is not limited to, the following three methods: micro-layer processing, color control, and hardware adaptation.

[0052] In this embodiment, the micro-layer processing may integrate either the RLE4 adaptive compression algorithm or the RLE8 adaptive compression algorithm. When the number of colors in the label information to be printed is less than or equal to 16, the RLE4 adaptive compression algorithm is enabled, meaning the target format is RLE4, and the compression ratio of the label information before and after compression is 1:4. When the number of colors in the label information to be printed is greater than 16, the RLE8 adaptive compression algorithm is enabled, meaning the target format is RLE8, and the compression ratio of the label information before and after compression is 1:2. Color control may support independent adjustment of four RGBA channels, with each channel having an accuracy of 8 bits, and achieving a color deviation of less than 2ΔE through ICC color profiles. Hardware adaptation may employ the abstract factory pattern to encapsulate the hardware interface, eliminating the need for specific printer drivers and adapting to mainstream brand UV laser equipment.

[0053] For example, if the operator's first client is a Windows 10 computer with a Java Swing graphics editing engine installed, and the operator designs a label for a circuit board, specifically 3×5mm in size and 20 colors, the first client automatically compresses the label data from 500KB to 250KB using the RLE8 format (i.e., the target format). Combined with independent adjustment of the RGBA four channels and using the ICC color profile, the color deviation of the label information to be printed is less than 2ΔE. The hardware interface is compatible with mainstream brands of UV laser equipment, such as Brand A or Brand B.

[0054] As an optional approach, when performing the "receiving the label information to be printed sent by the first client", the following method can be used, but is not limited to: receiving the authentication token sent by the first client through the upload interface corresponding to the first client, wherein the authentication token is a token sent to the first client after determining that the first client has passed the initial authentication; determining the first client's permission information and key validity information based on the authentication token; and receiving the label information to be printed sent by the first client if the permission information and key validity information are determined to be correct.

[0055] In this embodiment, the upload interface corresponding to the first client can be an API interface for receiving authentication tokens. It can be a RESTful interface that supports the POST method and only receives tokens sent by the first client that has completed initial authentication. For example, the upload interface corresponding to the first client can be the server-side / api / auth / token interface.

[0056] In this embodiment, initial authentication refers to the process where, upon the first client's initial access to the server, the client enters a username and password. After successful verification, the server generates an authentication token and returns it to the first client. The username and password can be encrypted and stored in the server's MySQL database. The authentication token serves as the first client's identity credential for subsequently sending tag information and may include information such as user role, permission scope, and validity period. The authentication method can employ JWT token authentication (HS512 signature algorithm).

[0057] For example, when the first client (CS-001) logs in for the first time, it enters the username operator01 and the password Encrypt123. After the server verifies the information, it generates a JWT token (HS512 signature). Before sending the label information to be printed, the first client sends the token to the server through this interface. If the first client is CS-002, the token obtained after the initial verification also needs to be submitted to the server through this interface.

[0058] In this embodiment of the application, after the server receives the authentication token, it can decrypt and verify the token through the parsing module (integrated in the Spring Security interceptor) and extract the permission information and key validity information from the payload of the token.

[0059] For example, if the server parses the JWT token sent by CS-001, it can obtain the permission information from the payload: role: Operator, permission: design or upload tag, key validity period: 30 minutes, not listed in the Redis blacklist; if the obtained permission information is: role: Viewer, permission: view only, it can be preliminarily determined that it does not have the qualification to upload.

[0060] In this embodiment, the server can perform verification based on the extracted permission information and key validity information. Specifically, it can determine whether the key validity information is correct and whether the permission information includes tag upload permission. If both conditions are met, the server receives the tag information to be printed sent by the first client.

[0061] For example, if the server parses the JWT token sent by CS-001, the permission information is "OPERATOR", which allows the user to design or upload tags, and the key validity information is "valid for 30 minutes", the server verifies the permission information and the key validity information. The verification result is that the key is within the validity period, not blacklisted, and the permission includes the right to upload.

[0062] In this embodiment, if the first client's authorization information and key validity information are verified correctly, the server enables the label information receiving channel (based on HTTPS protocol, TLS 1.3 encrypted transmission) to receive the label information to be printed sent by the first client. If the first client fails the two-factor authentication, the server will directly return a 401 unauthorized status code, refusing to receive data, ensuring that only legitimate and authorized clients can submit label information.

[0063] For example, if the authorization information and key validity information of CS-001 are verified to be correct, the server enables the / api / tag / upload interface to receive the tag information sent by it, and the transmission process is encrypted via HTTPS; if CS-001 fails the secondary verification, the server directly returns a 401 status code and refuses to receive it.

[0064] As an optional approach, when performing the action of "receiving the label information to be printed sent by the first client after determining that the permission information and key validity information are correct", the following method can be used, but is not limited to: if the permission information and key validity information of the first client are correct, the server receives the fragmented data corresponding to the label information to be printed sent by the first client; stores the fragmented data in a temporary cache according to the fragment index to generate the label information to be printed.

[0065] In this embodiment, when the amount of data for the label information to be printed is large (e.g., exceeding 1MB), the first client will split it into fixed-size data chunks (1MB per chunk by default). Each chunk carries a unique chunk index, task ID, and total number of chunks. Chunk upload is implemented using Ajax technology, supporting breakpoint resumption. If a chunk upload fails, only that chunk needs to be retransmitted next time. After the first client passes secondary verification, the server will enable the chunk receiving interface and receive the data chunk by chunk.

[0066] For example, if the first client CS-001 needs to upload 2.5MB of tag information, it is split into three slices: slice 0 includes 1MB, index 0, task ID TAG-001; slice 1 includes 1MB, index 1; and slice 2 includes 0.5MB, index 2. These slices are sent to the server one by one via the / api / tag / upload / slice interface. When the server receives each slice, it first verifies the association between the slice index and the task ID to ensure that the slice belongs to the correct entity.

[0067] In this embodiment, the fragment index can be a number carried in the fragment data to identify the splicing order. The server will store the fragment data in a temporary cache in an orderly manner according to the index and record the number of fragments received for each task ID. When the number of received fragments equals the total number of fragments, the server will splice all fragments into complete label information to be printed based on the index order, thus completing data reorganization.

[0068] For example, the server stores the three fragments sent by CS-001 in the MySQL fragment table in the order of index 0, 1, and 2. When it detects that the three received fragments are consistent with the total number of fragments, it concatenates fragment 0, fragment 1, and fragment 2 in the order of index to generate 2.5MB of tag information. If the temporary cache is an SSD hard disk folder, the fragments are stored with the names TAG-001_0, TAG-001_1, and TAG-001_2, and then concatenated into a complete file.

[0069] Step 102: Generate the print task approval information corresponding to the label information to be printed, and send the print task approval information to the second client.

[0070] The print job approval information is used for approval by the second client.

[0071] In this embodiment of the application, the printing task approval information can be an approval carrier generated by the server after processing the received label information to be printed, and can include key parameters of the label (size, precision, purpose), first client identifier, request time, and other information.

[0072] For example, if the label information to be printed received by the server is a military component identifier (size 8×8mm, resolution 1200dpi), the generated printing task approval information includes size 8×8mm, label purpose, requesting client ID, and application time.

[0073] In this embodiment, an RBAC model can be used, where approval permissions are bound to the administrator role, and the approval information is encrypted using the SHA-256 algorithm. The approval information is sent asynchronously to the second client via a message queue. The second client, acting as the administrator's approval terminal, only needs to receive and decrypt the approval information to execute an approval or rejection operation, thus achieving pre-emptive security control of printing tasks.

[0074] For example, if the server receives a label information for military components (8×8mm size, 1200dpi resolution) to be printed, the generated print task approval information includes the size 8×8mm, label purpose, requesting client ID, and application time. This approval information is encrypted using SHA-256 and sent to the second client (the administrator's Chrome browser) via a RabbitMQ message queue.

[0075] As an optional approach, when performing the action of "generating print task approval information corresponding to the label information to be printed and sending the print task approval information to the second client", the following method can be used, but is not limited to: encrypting the label information to be printed to generate print task approval information; and asynchronously sending the print task approval information to the second client through a message queue.

[0076] In this embodiment, the encryption process may involve using the SHA-256 hash algorithm to encrypt key approval data extracted from the label information to be printed. A dynamic salt value is introduced during the encryption process, which can be generated by hashing the server device ID and the current timestamp. For example, the server extracts approval data from the label information: date, size 5×5mm, request ID: CS-002, and time. Using device ID SRV-001 and timestamp 123 as the salt value, it encrypts the data using SHA-256 to generate print job approval information.

[0077] In this embodiment, the message queue can be middleware deployed on the server side for asynchronous communication, such as RabbitMQ. The server encapsulates the encrypted print task approval information into a message and sends it to the designated message queue. It can then continue processing other tasks without waiting for a response from the second client. The second client can listen to the message queue in real time; once it receives the message, it can decrypt it and display the approval information.

[0078] For example, the server encapsulates the label printing task approval information into a message and sends it to the RabbitMQ approval_queue. The administrator's Edge browser (i.e., the second client) listens to the queue in real time via WebSocket, obtains the message, decrypts it with a key, and displays the approval content.

[0079] Step 103: In response to receiving the approval information corresponding to the print task approval information sent by the second client, determine the target printing device for printing the label information to be printed.

[0080] In this embodiment, the server monitors the approval results from the second client in real time. Upon receiving approval information, it initiates a device filtering mode, which involves: obtaining the real-time status of all registered UV laser printing devices, including whether they are idle, whether the consumable balance is greater than or equal to 20%, and whether they meet the label accuracy requirements; and using a load balancing algorithm, which may include allocating resources based on the current task queue length of the device, selecting the optimal device from the eligible devices as the target printing device to avoid device overload or resource waste.

[0081] For example, when the server receives the approval information for the military label, it can find that there are two compatible devices: printer A (idle, ink level 50%, supports 1200dpi) and printer B (busy, ink level 30%). Based on the device status of printer A and printer B, printer A is selected as the target printing device.

[0082] Step 104: Send the print execution command corresponding to the label information to be printed to the target printing device.

[0083] The print execution command is used to control the target printing device to print the label information to be printed.

[0084] In this embodiment, the print execution instruction can be a control instruction generated by the server based on the information of the label to be printed and the parameter requirements of the target printing device. It can include the decrypted label data to be printed and the printing parameter configuration (such as laser power, engraving speed, and adaptation based on label material). The instruction is sent to the target printing device through the device control API.

[0085] For example, if the target printing device is printer A, the print execution command generated by the server includes the decrypted label data in RLE8 format, laser power of 6W, and engraving speed of 350mm / s. It is sent to the device via the device control API RS232 protocol, and the device starts printing immediately after receiving it.

[0086] Compared with existing technologies, this application uses a first client to compress the label information to be printed into a target format and send it to the server. By using a unified compression format, the server's parsing cost is reduced and processing efficiency is improved. Print task approval information is generated and submitted to a second client for approval, establishing a security audit mechanism to improve security. Based on this, after obtaining the approval information, the server coordinates and determines the target printing device to achieve precise matching between printing tasks and equipment resources, improving resource utilization. Standardized printing execution instructions are sent to the target printing device to shorten the task response cycle and comprehensively improve the overall efficiency of laser label printing.

[0087] As an optional approach, before executing the "print execution instruction corresponding to the label information to be printed is sent to the target printing device", the following method can be used, but is not limited to: parsing the label information to be printed to obtain the label metadata corresponding to the label information to be printed, and storing the label metadata in a temporary cache; sending the print execution instruction corresponding to the label information to be printed to the target printing device, including: obtaining the label metadata from the temporary cache, and generating the print execution instruction based on the label metadata.

[0088] In this embodiment, the parsing process can be performed by the server using a dedicated label parsing module to extract uncompressed structured data from the label information to be printed. This data may include basic label parameters (size, precision, number of colors) and printing configuration requirements (compatible device type, laser power range, material requirements). The temporary cache is a high-performance cache, such as a Redis cache.

[0089] For example, the server parses the tag information (250KB, RLE8 compression), extracts the tag metadata, size: 3×5mm, resolution: 1200dpi, number of colors: 20, compatible device: laser printer A, laser power: 5-8W, and the temporary cache is a Redis cache.

[0090] In this embodiment, after the server determines the target printing device, it does not need to re-parse the complete label information to be printed. Instead, it can directly read the corresponding label metadata from the temporary cache and combine it with the parameters of the target printing device to generate a print execution instruction that conforms to the device instruction format. The print execution instruction may include key configurations from the metadata and decrypted label graphic data.

[0091] For example, after the server determines that the target printing device is printer A, it reads the tag metadata of TAG-003 from Redis and combines it with the parameters of printer A (maximum laser power 10W, default engraving speed 300mm / s) to generate a print execution command: laser power: 6W, engraving speed: 350mm / s, tag data: decrypted RLE8 graphic data, task ID: TAG-003.

[0092] As an optional approach, after executing the "print execution instruction corresponding to the label information to be printed is sent to the target printing device", the following method can be used, but is not limited to: in response to receiving the print completion information sent by the target printing device, parsing the print completion information to obtain the print log of the target printing device; and sending the print log to the second network device.

[0093] In this embodiment, the printing completion information can be a status notification sent to the server after the target printing device has completed printing all labels. It can include task ID, number of labels printed, printing time, device operation data (printer temperature, consumable consumption), and printing result (success or failure, with a reason for failure). After receiving this information through the device control API, the server parses it and organizes the structured data into a printing log to record key information throughout the printing process.

[0094] For example, after printer A completes printing 100 labels, it sends print completion information to the server: Task ID: TAG-003, Print Quantity: 100, Time Taken: 180 seconds, Printhead Temperature: 58℃, Ink Consumption: 8ml, Result: Success (1 label is slightly blurry). The server parses this information, generates a print log containing all the above information, and stores it in a MySQL log table.

[0095] In this embodiment of the application, the server can send logs to the second client through the notification mechanism of the BS platform (such as in-system message push, WebSocket real-time push), so that the administrator can understand the execution results of the printing task in a timely manner, including whether it is completed, whether there are any abnormalities, and the equipment consumption status, which facilitates the subsequent control of printing quality and maintenance management of the equipment.

[0096] For example, the server pushes the label printing log to the second client (the administrator's Chrome browser approval page) via WebSocket. The printing log can be displayed in the form of a task completion notification: TAG-003 completed, 100 sheets printed (1 slightly blurry), time taken 3 minutes, ink consumed 8ml.

[0097] Compared with existing technologies, this application uses a first client to compress the label information to be printed into a target format and send it to the server. By using a unified compression format, the server's parsing cost is reduced and processing efficiency is improved. Print task approval information is generated and submitted to a second client for approval, establishing a security audit mechanism to improve security. Based on this, after obtaining the approval information, the server coordinates and determines the target printing device to achieve precise matching between printing tasks and equipment resources, improving resource utilization. Standardized printing execution instructions are sent to the target printing device to shorten the task response cycle and comprehensively improve the overall efficiency of laser label printing. This application's embodiments employ a two-layer verification mechanism for secondary authentication, strictly limiting the access qualifications of the first client and enhancing system access security. This application's embodiments adopt a fragmented upload and index-based storage strategy, supporting breakpoint resumption and improving transmission stability and efficiency. This application's embodiments use SHA-256 encryption to process print task approval information and combine it with asynchronous message queue sending, balancing the security of the approval process with system operating efficiency. This application's embodiments generate and cache label metadata by parsing the label information to be printed. When generating subsequent print execution instructions, the metadata can be directly retrieved from the cache, eliminating the need to repeatedly parse the complete label data, thus improving the response speed of print tasks. This application's embodiments parse and generate print logs after printing and synchronize them to the second client, facilitating administrators to monitor printing results in real time, quickly locate printing anomalies, and provide data support for subsequent equipment maintenance and print quality control.

[0098] As an optional approach, after executing the "print execution command corresponding to the label information to be printed is sent to the target printing device", the following method can be used, but is not limited to it, which includes the following steps:

[0099] Step 201: In response to the detection of an interruption in the target printing device by the service monitoring module, obtain the progress information of the target printing device at preset time intervals;

[0100] In this embodiment, the service monitoring module can be a device status monitoring program deployed on the server side, which monitors the online status and printing progress of the target printing device in real time via the ICMP protocol or device status API. When the service monitoring module detects a device interruption, it immediately initiates the progress information acquisition logic and attempts to reconnect to the device at preset time intervals. If the connection is successful, the printing progress before the interruption is acquired; if the connection fails, the module continues to attempt reconnection at intervals until the maximum number of attempts is reached.

[0101] For example, the service monitoring module detects that printer A's label printing is interrupted (ping timeout), and attempts to connect to the device at a preset time interval of 30 seconds. The first attempt fails, the second attempt succeeds, and the progress information is: 60 labels have been printed, 40 labels remain, and the reason for the interruption is network fluctuation.

[0102] Step 202: Generate interruption alarm information corresponding to the target printing device based on the progress information.

[0103] In this embodiment of the application, the server can integrate, but is not limited to, device ID, interruption time, current progress, and possible causes of failure into interruption alarm information. If no progress information is obtained (multiple connection failures), the alarm information includes "progress unknown".

[0104] For example, the server generates an interruption alarm based on the progress information of printer A: Device interruption alarm: Device IDHZ-001 (print task TAG-003) interrupted, current progress: 60 pages printed (40 pages remaining), possible cause: network fluctuation.

[0105] Compared with existing technologies, this application embodiment completes the target format compression processing of the label information to be printed through a first client and sends it to the server. By using a unified compression format, the server's parsing cost is reduced, improving processing efficiency. Print task approval information is generated and submitted to a second client for approval, establishing a security audit mechanism to enhance security. Based on this, after obtaining the approval information, the server comprehensively determines the target printing device, achieving precise matching between printing tasks and device resources, improving resource utilization. Standardized print execution instructions are sent to the target printing device, shortening the task response cycle and comprehensively improving the overall efficiency of laser label printing. This application embodiment obtains printing progress information before device interruption and generates interruption alarm information based on the progress information, which can reduce task rework and material waste, ensure the continuity of the printing process, and improve the system's fault tolerance and overall operational stability in the face of sudden failures.

[0106] Optionally, this application also provides a full-color micro-layer ultraviolet laser label printing system, which solves the technical pain points of traditional systems in terms of architectural flexibility, process closure and data security by separating the design and operation links through a CS and BS hybrid architecture, a micro-layer dynamic compression algorithm and a security approval engine. It is suitable for the whole-process digital management scenario of high-precision industrial marking.

[0107] Existing laser label printing systems have the following technical shortcomings:

[0108] At the architectural level: Adopting a pure client-server (CS) or browser-server (BS) architecture results in deep coupling between the label design module and the printing execution module. In a CS architecture, graphics rendering relies on local hardware drivers, while in a BS architecture, the editing response latency exceeds 200ms, leading to poor portability and requiring over 30% code refactoring for cross-platform deployment.

[0109] Functionally, label design (such as third-party tools like Adobe Illustrator), print job scheduling (hardware manufacturer's built-in program), and security management (independent approval software) are discrete systems. Data interaction between modules relies on manual export and import, resulting in a breakpoint rate of over 40% throughout the entire process, making it impossible to form a closed loop.

[0110] Security aspects: Printed data is transmitted in plaintext HTTP, posing a risk of leakage of sensitive labels (such as military identification); operation permissions are based solely on simple account passwords, without implementing fine-grained role-based control, resulting in an unauthorized operation rate of over 15%; and there is a lack of operation log tracing mechanism, making it take more than 2 hours to locate abnormal operations.

[0111] At the analysis level: Printing process data (such as printhead temperature and consumable balance) are not collected in real time, and key indicators (such as equipment utilization and printing yield) need to be manually collected. The data lag is more than 8 hours, which cannot support dynamic decision-making.

[0112] This application provides a full-color micro-layer ultraviolet laser label printing system that achieves the following goals through technological innovation: It realizes end-to-end data connectivity for label design, printing monitoring, and security approval based on a modular interface design, eliminating process breakpoints; it adopts a CS+BS hybrid architecture, decoupling the design and operation ends and reducing cross-platform deployment and adaptation costs by 60%; it constructs a three-layer security system of token authentication, data encryption, and hierarchical access control, keeping the risk of data leakage below 0.1%; and it develops a real-time data acquisition and visualization engine with a key indicator response latency of less than 1 second, supporting accurate decision-making.

[0113] The core design scheme of a full-color micro-layer ultraviolet laser label printing system is as follows:

[0114] 1. Hybrid Architecture Design

[0115] (1) CS designer end (i.e., the first client in this application embodiment): a local graphics editing engine is built based on JavaSwing, and the core technologies include:

[0116] 1) Micro-layer processing: Integrates RLE4 or RLE8 adaptive compression algorithm. When the number of colors in the image is less than or equal to 16, RLE4 (compression ratio 1:4) is automatically enabled, and when it is greater than 16, RLE8 (compression ratio 1:2) is switched, which improves the compression efficiency by 30% compared with the traditional fixed algorithm.

[0117] 2) Color control: Supports independent adjustment of RGBA four channels (8-bit / channel precision), and achieves color deviation of less than 2ΔE through ICC color profile;

[0118] 3) Hardware adaptation: The hardware interface is encapsulated using the abstract factory pattern, eliminating the need for specific printer drivers and adapting to mainstream brand ultraviolet laser equipment.

[0119] (2) BS runtime platform (i.e., the server in this application embodiment): a cloud service cluster built on Spring Boot 2.7, with the following technical features:

[0120] 1) Service architecture: It adopts a RESTful API design (supports GET / POST / PUT / DELETE methods), and the single-node concurrent processing capacity is greater than or equal to 500 TPS;

[0121] 2) Task scheduling: Integrates the Quartz timer framework, supporting millisecond-level task triggering (error less than 10ms);

[0122] 3) Cross-platform support: Achieves compatibility with Windows or Linux systems through the JVM virtual machine, and 100% browser compatibility (supports Chrome, Edge, or Firefox).

[0123] (3) Data Interaction Layer:

[0124] 1) Standardized interface: Data format is defined using JSON Schema, and field validation is supported (e.g., label size range 0.5×0.5mm-100×100mm);

[0125] 2) Cross-domain communication: Based on CORS policy configuration of access whitelist, combined with HTTPS encrypted transmission (TLS1.3 protocol), the data transmission security complies with ISO27001 standard.

[0126] 2. Implementation of core functional technologies

[0127] The core functional technologies are shown in Table 1, including functional modules and specific technical solutions:

[0128] Table 1

[0129]

[0130]

[0131] The key technological innovations and effects of a full-color micro-layer ultraviolet laser label printing system provided in this application embodiment may include:

[0132] (1) Dynamic compression technology of micro-layers:

[0133] Innovation: An adaptive compression algorithm based on color complexity solves the problem of low compression efficiency of traditional fixed algorithms in multi-color scenes;

[0134] Results: Data transfer volume for 1000 mixed color labels (including monochrome / multicolor) is reduced by 70%, and print preparation time is shortened to less than 2 seconds.

[0135] (2) Secure approval workflow engine:

[0136] Innovation: The software approval process is bound to the hardware execution status, and the rigid linkage between "approval result → device action" is achieved through encrypted instructions;

[0137] Results: 100% interception rate for unapproved label printing; compliance rate for sensitive label operations increased to 100%.

[0138] (3) Real-time data-driven dashboards:

[0139] Innovation: Integrating equipment sensor data (temperature, humidity), task data (queue length), and personnel operation data (response speed) to construct a three-dimensional analysis model;

[0140] Results: Equipment anomaly warning accuracy >90%, troubleshooting time reduced by 50%.

[0141] (4) Hybrid architecture resource scheduling:

[0142] Innovation: The client-side performs computationally intensive operations (graphics rendering) offline, while the client-side (BS) processes business logic (task scheduling) in the cloud, and data synchronization is achieved through lightweight JSON;

[0143] Results: A single server supports concurrent processing of 1000+ tags, improving resource utilization by 40%.

[0144] The full-color micro-layer ultraviolet laser label printing system provided in this application embodiment, based on the above-mentioned key technical innovations, can achieve the following beneficial effects:

[0145] 1. Efficiency Improvement:

[0146] Tag processing: Micro-layer compression reduces the data size of a single tag from 500KB to 150KB, and increases transmission speed by 40% (based on 100Mbps network testing);

[0147] Approval process: Electronic approval replaces paper-based processing, reducing the average processing time from 2 hours to 5 minutes (based on statistics from 1,000 approval samples).

[0148] 2. Enhanced security:

[0149] Access control: JWT token + SHA-256 encryption + RBAC permission triple protection, 100% unauthorized access interception rate (simulated 1000 attack tests);

[0150] Operation traceability: Full-link logging achieves 100% operation traceability, reducing the time for locating abnormal operations from 2 hours to 10 minutes.

[0151] 3. System stability:

[0152] Portability: 100% pass rate in cross-platform adaptation (Windows 10 / 11, Linux CentOS 7 / 8) tests, and deployment time reduced from 1 day to 2 hours;

[0153] Fault tolerance: The service monitoring module checks the process status every 30 seconds, and crashed processes are automatically restarted (recovery time < 30 seconds), with system availability reaching 99.9%.

[0154] 4. Decision optimization:

[0155] Equipment utilization: The load balancing algorithm dynamically allocates tasks, reducing the equipment idle rate from 30% to 19.5%, and increasing utilization by 35%.

[0156] Consumables control: The ink volume sensor collects data in real time, and the threshold (default 20%) warning triggers a purchase reminder, increasing the inventory turnover rate of consumables by 25%.

[0157] As an optional approach, a specific implementation of the full-color micro-layer ultraviolet laser label printing system provided in this application embodiment may include:

[0158] 1. System Deployment:

[0159] CS designer side (i.e., the first client in this embodiment of the disclosure):

[0160] Operating environment: JRE 1.8+ (memory ≥ 2GB), supports Windows 7 and above, macOS 10.12 and above;

[0161] Core functionality: Locally complete label micro-layer design (including color configuration and RLE compression), and output label description files conforming to the JSONSchema specification (with the extension .lab).

[0162] BS operating platform (i.e., the server in this embodiment of the disclosure):

[0163] Server configuration: CPU ≥ 4 cores, memory ≥ 8GB, hard disk ≥ 100GB (SSD);

[0164] Technology stack: Nginx 1.21 (reverse proxy + load balancer), Spring Boot 2.7, MySQL 8.0 (master-slave replication), Redis 6.2 (caching), WebSocket (real-time communication);

[0165] Deployment architecture: Docker containerized deployment is adopted, supporting horizontal scaling (a single cluster supports a maximum of 10 nodes).

[0166] 2. Label printing process:

[0167] Process nodes: Design (CS side) → Upload (JSON format) → Review (BS side) → Scheduling (task queue) → Print (laser equipment) → Feedback (status synchronization);

[0168] Core Logic Explanation: The core logic of the RLE adaptive compression algorithm is to first obtain the number of colors in the image data. If the number of colors is less than or equal to 16, then RLE4 compression mode is used to compress the image data; if the number of colors is greater than 16, then RLE8 compression mode is used to compress the image data.

[0169] 3. Implementation of safety controls:

[0170] Identity verification:

[0171] Login process: User enters account and password → Server verification → Generates JWT token (including user role and permission information) → Client storage (localStorage, with expiration cleanup mechanism);

[0172] Request verification: Each API request carries a token in the header. The interceptor (HandlerInterceptor) verifies the validity of the token (signature + validity period). If invalid, it returns a 401 status code.

[0173] Access control hierarchy:

[0174] Role definitions: Administrator, Operator, Viewer;

[0175] Permission matrix:

[0176] Administrator: Full permissions for design / upload / approval / monitoring / configuration;

[0177] Operator: Design / upload / monitoring permissions;

[0178] Viewer: Only monitoring and viewing permissions.

[0179] Data encryption:

[0180] Transport layer: All communication data is encrypted using HTTPS (TLS 1.3);

[0181] Storage layer: Sensitive data (such as approval records) is stored after being encrypted with SHA-256 (salt value = device ID + timestamp hash).

[0182] 4. Exception handling mechanism:

[0183] Print interruption: The print progress is saved every 5 seconds (stored in Redis) through the checkpoint mechanism. When resuming, printing is resumed from the breakpoint, with a data loss rate of 0%.

[0184] Equipment failure: The service monitoring module detects the equipment status via the ICMP protocol (ping interval of 10 seconds). When an abnormality occurs, it triggers a three-level alarm (system notification → SMS → telephone) and automatically switches to the backup equipment (equipment priority needs to be configured in advance).

[0185] This application provides a full-color micro-layer ultraviolet laser label printing system that can be applied to industrial labeling: for precision electronic components (such as chips and circuit boards), it achieves micron-level label printing with a precision of 1200 dpi, supporting alcohol resistance and high-temperature resistance (-40℃~120℃) environments; product traceability: combined with UV fluorescent ink, it prints anti-counterfeiting labels for pharmaceuticals containing encrypted QR codes, and the traceability information can be read through a dedicated barcode scanning device (supporting offline verification); high-end logistics: it prints low-temperature resistant labels (not falling off at -40℃) for cold chain transport items, and the labels contain temperature and humidity sensing chips (data is transmitted back to the system in real time).

[0186] Compared with existing technologies, the full-color micro-layer ultraviolet laser label printing system provided in this application embodiment uses a hybrid architecture separation technology: the CS end (i.e., the first client in this application embodiment) focuses on graphic editing (local high performance), while the BS end (i.e., the server in this application embodiment) is responsible for operation and management (cross-platform flexibility), solving the coupling problem of traditional architectures; dynamic micro-layer compression: the RLE4 / RLE8 adaptive algorithm balances compression efficiency and image quality, reducing data transmission costs; secure approval closed loop: the software approval process is linked with the hardware execution status, and full-link security management is achieved through encryption and access control; real-time data dashboard: it integrates equipment, task, and personnel data, and drives decision optimization through visualization. The system provided in this application embodiment can effectively solve the problems of rigid architecture, fragmented functions, and weak security in traditional laser label printing, providing reliable technical support for high-precision industrial marking, product traceability, and other scenarios, and has significant technological advancement and practical value.

[0187] Furthermore, as Figure 1 and Figure 2 The specific implementation of the method shown in this embodiment provides a laser label printing device, such as... Figure 3 As shown, the device includes: a receiving module 31, a generating module 32, a response module 33, and a sending module 34.

[0188] The receiving module 31 is configured to receive the label information to be printed sent by the first client. The label information to be printed is obtained by compression processing according to a target format with a compression ratio greater than or equal to a predetermined compression ratio threshold.

[0189] The generation module 32 is configured to generate print task approval information corresponding to the label information to be printed, and send the print task approval information to the second client. The print task approval information is used by the second client for approval.

[0190] The response module 33 is configured to determine the target printing device for printing the label information to be printed in response to receiving the approval information corresponding to the print task approval information sent by the second client.

[0191] The sending module 34 sends a print execution command corresponding to the label information to be printed to the target printing device. The print execution command is used to control the target printing device to print the label information to be printed.

[0192] In some examples of this embodiment, the receiving module 31 is specifically configured to receive the authentication token sent by the first client through the upload interface corresponding to the first client. The authentication token is a token sent to the first client after determining that the first client has passed the initial authentication. Based on the authentication token, the first client's permission information and key validity information are determined.

[0193] In some examples of this embodiment, the receiving module 31 is specifically configured to receive the label information to be printed sent by the first client when the authorization information and key validity information are determined to be correct.

[0194] In some examples of this embodiment, the receiving module 31 is specifically configured to receive the fragmented data corresponding to the label information to be printed sent by the first client when the authorization information and key validity information are determined to be correct.

[0195] In some examples of this embodiment, the generation module 32 is specifically configured to store the fragmented data in a temporary cache according to the fragmented index to generate label information to be printed.

[0196] In some examples of this embodiment, the generation module 32 is specifically configured to encrypt the label information to be printed and generate print task approval information.

[0197] In some examples of this embodiment, the sending module 34 is specifically configured to asynchronously send print job approval information to the second client via a message queue.

[0198] In some examples of this embodiment, the generation module 32 is specifically configured to parse the label information to be printed, obtain the label metadata corresponding to the label information to be printed, and store the label metadata in a temporary cache; send the print execution instruction corresponding to the label information to be printed to the target printing device, including: obtaining the label metadata from the temporary cache and generating the print execution instruction based on the label metadata.

[0199] In some examples of this embodiment, the response module 33 is specifically configured to parse the print completion information in response to receiving print completion information sent by the target printing device, and obtain the print log of the target printing device.

[0200] In some examples of this embodiment, the sending module 34 is specifically configured to send print logs to the second network device.

[0201] In some examples of this embodiment, the response module 33 is specifically configured to obtain the progress information of the target printing device at preset time intervals in response to the detection of an interruption of the target printing device by the service monitoring module.

[0202] In some examples of this embodiment, the generation module 32 is specifically configured to generate interruption alarm information corresponding to the target printing device based on the progress information.

[0203] It should be noted that other corresponding descriptions of the functional units involved in the laser label printing device provided in this embodiment can be found in [reference needed]. Figure 1 and Figure 2 The corresponding descriptions in [the document] will not be repeated here.

[0204] Based on the above, Figure 1 and Figure 2 Accordingly, this embodiment also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the above-described method. Figure 1 and Figure 2 The method shown.

[0205] Based on this understanding, the technical solution of this application can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (such as CD-ROM, USB flash drive, mobile hard drive, etc.) and includes several instructions to cause a computer device (such as personal computer, server, or network device, etc.) to execute the methods of various implementation scenarios of this application.

[0206] like Figure 4 The diagram shown is a hardware structure schematic of an electronic device according to the present invention, comprising:

[0207] At least one processor 401; and,

[0208] Memory 402 is communicatively connected to at least one processor 401; wherein,

[0209] The memory 402 stores instructions that can be executed by at least one processor to enable the at least one processor to perform the laser label printing method as described above.

[0210] Figure 4 Take a processor 401 as an example.

[0211] The electronic device may also include an input device 403 and a display device 404.

[0212] The processor 401, memory 402, input device 403, and display device 404 can be connected via a bus or other means. Figure 4 Taking the example of a connection between China and Israel via a bus.

[0213] The memory 402, as a non-volatile computer-readable storage medium, can be used to store non-volatile software programs, non-volatile computer-executable programs, and modules, such as the program instructions / modules corresponding to the laser label printing method in the embodiments of this application. Figure 1 and Figure 2 The method flow is shown. The processor 401 executes various functional applications and data processing by running non-volatile software programs, instructions, and modules stored in the memory 402, thereby realizing the laser label printing method in the above embodiments.

[0214] The memory 402 may include a program storage area and a data storage area. The program storage area may store an operating system and an application program required for at least one function; the data storage area may store data created based on the use of the laser label printing method. Furthermore, the memory 402 may include high-speed random access memory and may also include non-volatile memory, such as at least one disk storage device, flash memory device, or other non-volatile solid-state storage device. In some embodiments, the memory 402 may optionally include memory remotely located relative to the processor 401, and these remote memories may be connected via a network to the apparatus performing the laser label printing method. Examples of such networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.

[0215] Input device 403 can receive user clicks and generate signal inputs related to user settings and function control of the laser label printing method. Display device 404 may include display devices such as a display screen.

[0216] One or more modules are stored in memory 402, and when run by one or more processors 401, the laser label printing method in any of the above method embodiments is executed.

[0217] Optionally, the aforementioned physical devices may also include a user interface, a network interface, a camera, radio frequency (RF) circuitry, sensors, audio circuitry, a Wi-Fi module, etc. The user interface may include a display screen, input units such as a keyboard, etc., and optional user interfaces may also include USB interfaces, card reader interfaces, etc. The network interface may optionally include standard wired interfaces, wireless interfaces (such as Wi-Fi interfaces), etc.

[0218] Those skilled in the art will understand that the physical device structure provided in this embodiment does not constitute a limitation on the physical device, and may include more or fewer components, or combine certain components, or have different component arrangements.

[0219] The storage medium may also include an operating system and a network communication module. The operating system is a program that manages the hardware and software resources of the aforementioned physical device, supporting the operation of information processing programs and other software and / or programs. The network communication module is used to enable communication between the various components within the storage medium, as well as communication with other hardware and software in the information processing physical device.

[0220] Through the above description of the embodiments, those skilled in the art can clearly understand that this application can be implemented by means of software plus necessary general-purpose hardware platforms, or it can be implemented by hardware. Compared with the prior art, by applying the solution of this embodiment, this application embodiment completes the target format compression processing of the label information to be printed through a first client and sends it to the server. By using a unified compression format, the server's parsing cost is reduced, and processing efficiency is improved. Print task approval information is generated and submitted to a second client for approval, establishing a security review mechanism to improve security. Based on this, after obtaining the approval information, the server coordinates and determines the target printing device, achieving precise matching of printing tasks and device resources, and improving resource utilization. Standardized printing execution instructions are sent to the target printing device, shortening the task response cycle and comprehensively improving the overall efficiency of laser label printing. This application embodiment uses SHA-256 encryption to process the print task approval information and combines it with asynchronous message queue processing. This approach balances security in the approval process with system efficiency. This embodiment generates and caches label metadata by parsing the label information to be printed. Subsequent printing execution commands can directly retrieve the metadata from the cache, eliminating the need to repeatedly parse the complete label data and improving the response speed of printing tasks. After printing is complete, this embodiment parses and generates printing logs, which are then synchronized to a second client. This allows administrators to monitor printing results in real time, quickly locate printing anomalies, and provides data support for subsequent equipment maintenance and printing quality control. This embodiment obtains printing progress information before equipment interruption and generates interruption alarm information based on this progress information. This reduces task rework and material waste, ensures the continuity of the printing process, and improves the system's fault tolerance and overall operational stability in the face of sudden failures.

[0221] It should be noted that, in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes the element.

[0222] The above are merely specific embodiments of this application, enabling those skilled in the art to understand or implement this application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of this application. Therefore, this application is not to be limited to these embodiments, but is to be accorded the widest scope consistent with the principles and novel features claimed herein.

Claims

1. A laser label printing method, characterized in that, include: The system receives label information to be printed sent by a first client. The label information to be printed is obtained by compressing the label information according to a target format with a compression ratio greater than or equal to a predetermined compression ratio threshold. Generate print task approval information corresponding to the label information to be printed, and send the print task approval information to the second client. The print task approval information is used by the second client for approval. In response to receiving the approval information corresponding to the print task approval information sent by the second client, the target printing device for printing the label information to be printed is determined; A print execution command corresponding to the label information to be printed is sent to the target printing device. The print execution command is used to control the target printing device to print the label information to be printed.

2. The method according to claim 1, characterized in that, The receipt of the label information to be printed sent by the first client includes: The authentication token sent by the first client is received through the upload interface corresponding to the first client. The authentication token is a token sent to the first client after determining that the first client has passed the initial authentication. The authentication token is used to determine the first client's permission information and key validity information; If the permission information and the key validity information are determined to be correct, the system receives the label information to be printed sent by the first client.

3. The method according to claim 2, characterized in that, The step of receiving the label information to be printed sent by the first client when the authorization information and the key validity information are determined to be correct includes: If the permission information and the key validity information are determined to be correct, the fragmented data corresponding to the label information to be printed sent by the first client is received; The fragmented data is stored in a temporary cache according to the fragment index to generate the label information to be printed.

4. The method according to claim 1, characterized in that, The step of generating print task approval information corresponding to the label information to be printed and sending the print task approval information to the second client includes: The information of the label to be printed is encrypted to generate the approval information for the printing task; The print job approval information is sent asynchronously to the second client via a message queue.

5. The method according to claim 1, characterized in that, Before sending the print execution command corresponding to the label information to be printed to the target printing device, the method further includes: The label information to be printed is parsed to obtain the label metadata corresponding to the label information to be printed, and the label metadata is stored in a temporary cache; Sending the print execution command corresponding to the label information to be printed to the target printing device includes: The label metadata is retrieved from the temporary cache, and the print execution instruction is generated based on the label metadata.

6. The method according to claim 1, characterized in that, After sending the print execution command corresponding to the label information to be printed to the target printing device, the method further includes: In response to receiving print completion information sent by the target printing device, the print completion information is parsed to obtain the print log of the target printing device; The printed log is sent to the second client.

7. The method according to claim 1, characterized in that, After sending the print execution command corresponding to the label information to be printed to the target printing device, the method further includes: In response to the detection of an interruption in the target printing device by the service monitoring module, the progress information of the target printing device is obtained at preset time intervals. Based on the progress information, an interruption alarm message corresponding to the target printing device is generated.

8. A laser label printing device, characterized in that, include: The receiving module is configured to receive label information to be printed sent by a first client, wherein the label information to be printed is obtained by compression processing according to a target format with a compression ratio greater than or equal to a predetermined compression ratio threshold; The generation module is configured to generate print task approval information corresponding to the label information to be printed, and send the print task approval information to the second client, wherein the print task approval information is used by the second client for approval. The response module is configured to determine the target printing device for printing the label information to be printed in response to receiving approval information corresponding to the print task approval information sent by the second client; The sending module is configured to send a print execution command corresponding to the label information to be printed to the target printing device, the print execution command being used to control the target printing device to print the label information to be printed.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the method of any one of claims 1 to 7.

10. An electronic device comprising a storage medium, a processor, and a computer program stored on the storage medium and executable on the processor, characterized in that, When the processor executes the computer program, it implements the method of any one of claims 1 to 7.

Images