A multi-process task tracking management method and system

Abstract

This invention discloses a multi-process task tracking and management method and system, relating to the field of process task management technology. The method includes: generating a task data package for the next processing step of a product and organizing the task data packages in a task pool; extracting the data identifiers of the task data packages in the task pool and generating task QR codes based on a distributed lock mechanism; obtaining a verification data package based on the operator's QR code scanning and claiming operation; querying whether the target task's QR code is unlocked based on the target task information in the verification data package; if not, querying the target task's task data based on the target task information in the verification data package; detecting whether the device information identifier of the verification data package matches the data identifier of the task QR code; if they match, generating a task key based on the verification data package and outputting a message indicating successful task claiming. This method has the advantages of enabling real-time task allocation, accurately tracking the processing step status, and ensuring accurate matching between operators and tasks.

Description

Technical Field

[0001] This invention relates to the field of processing information management technology, specifically to a multi-process task tracking management method and system. Background Technology

[0002] For product assembly line processing operations, multiple processing steps need to be performed on the workpiece. The existing processing mode is to pre-allocate processing tasks so that the workpiece is processed sequentially according to the processing flow. This method results in a large time difference between the task allocation and the operator execution stage, which is not convenient for real-time tracking and management of product processing. Moreover, when some processing steps fail, the workpiece needs to be re-arranged, which affects the convenience and reliability of workpiece processing management. Summary of the Invention

[0003] The purpose of this invention is to overcome the shortcomings of the prior art. This invention provides a multi-process task tracking management method and system, which generates task data packets based on the product status entering the system and realizes dynamic task allocation and tracking based on a distributed lock mechanism and QR code verification. By generating encrypted task identifiers and matching equipment information in real time, it solves the problems of task lag, low efficiency of abnormal handling and personnel task matching errors in the traditional pre-allocation mode, and has the advantages of improving production flexibility and quality control accuracy.

[0004] This invention provides a multi-process task tracking and management method, the management method comprising:

[0005] S1: Based on the product status entering the system, generate a task data package for the next processing step of the product, and organize the task data package in the task pool;

[0006] S2: Extract the data identifier of the task data packets in the task pool, and generate a task QR code based on the distributed lock mechanism and the data identifier of the task data packets in the task pool.

[0007] S3: Based on the operator's scanning and claiming operation, extract the device information identifier and target task information of the scanning device to obtain the verification data packet;

[0008] S4: Based on the target task information in the verification data packet, check whether the target task's task QR code is in an unlocked state. If yes, proceed to step S5; otherwise, proceed to step S6.

[0009] S5: Output a message indicating that the task failed to be accepted;

[0010] S6: Based on the target task information of the verification data packet, query the task data of the target task, and check whether the device information identifier of the verification data packet matches the data identifier of the task QR code. If yes, proceed to step S7; otherwise, return to step S5.

[0011] S7: Generate a task key based on the verification data packet and output a message indicating that the task has been successfully claimed.

[0012] Furthermore, step S1 includes:

[0013] Schedule product processing tasks according to product specifications, detect completed processing tasks, and sort incomplete processing tasks according to product processing tasks.

[0014] Extract the data for the next processing step of the product and generate a task data package for the next processing step of the product.

[0015] The products are labeled and numbered, and the generated task data packages are stored in the task pool of the management system.

[0016] Furthermore, step S2 includes:

[0017] Obtain the data identifier of the data packet in the task pool, and encrypt the data identifier using the AES encryption algorithm;

[0018] A distributed lock mechanism is introduced to set a data lock on the encrypted data identifier, and the data lock is mapped to the corresponding task data packet based on the data identifier.

[0019] Furthermore, the step of obtaining the data identifier of the data packet within the task pool and encrypting the data identifier using the AES encryption algorithm includes:

[0020] Set the key length to 256 bits, encrypt the data content of the data identifier using the encryption key, and output the encrypted data identifier.

[0021] Furthermore, the encryption algorithm formula for the data identifier is as follows:

[0022] ;

[0023] Where C is the encrypted data, D is the original data, K is the encryption key, and IV is the random number.

[0024] Furthermore, step S3 includes:

[0025] During the operator's scanning and identification process, the scanning device generates a device information identifier with a key based on the built-in AES algorithm and the device information.

[0026] Based on the QR code information scanned by the operator, the target task information is extracted and combined with the device information identifier to generate verification data.

[0027] Furthermore, the formula for generating the key is:

[0028] ;

[0029] Where Key is the key. Here, is the key factor, date is the current date string, and N is the device information.

[0030] Furthermore, step S4 includes:

[0031] The verification data generated when the operator scans the task QR code is used to check whether the task QR code is in an unlocked state based on the target task information in the verification data. If it is, the target task is in an claimed state; if not, the target task is in a pending state.

[0032] Furthermore, step S6 includes:

[0033] The device information identifier of the verification data is matched and decrypted with the data identifier of the task QR code. If the decryption is successful, the device information identifier matches the task QR code.

[0034] If decryption fails, the device information identifier does not match the task QR code.

[0035] The present invention also provides a multi-process task tracking and management system, the tracking and management system being used to execute the management method, the management system comprising:

[0036] Task pool: Used to store the pending processing tasks of workpieces that have entered the system;

[0037] Data encryption module: used to encrypt the process task data in the task pool using a distributed lock mechanism;

[0038] Data management module: used to store encrypted information of process task data and obtain the operator's scan-to-claim data;

[0039] Data verification module: Used to perform matching and management of user scanning operations and target tasks.

[0040] This invention provides a multi-process task tracking and management method and system. It generates task data packets based on the product status entering the system and realizes dynamic task allocation and tracking based on a distributed lock mechanism and QR code verification. By generating encrypted task identifiers and matching equipment information in real time, it solves the problems of task lag, low efficiency of abnormal handling and personnel task matching errors in the traditional pre-allocation mode. It has the advantages of improving production flexibility and quality control accuracy. Attached Figure Description

[0041] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0042] Figure 1 This is a flowchart of the multi-process task tracking and management method in an embodiment of the present invention;

[0043] Figure 2 This is a schematic diagram of the structure of the multi-process task tracking management system in an embodiment of the present invention. Detailed Implementation

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

[0045] Example 1: Figure 1 A flowchart of a multi-process task tracking management method according to an embodiment of the present invention is shown. The management method includes:

[0046] S1: Based on the product status entering the system, generate a task data package for the next processing step of the product, and organize the task data package in the task pool;

[0047] The task data package refers to a data set containing the operation instructions and parameters for the next process, which is dynamically generated based on the current status of the product. Specifically, it can be implemented using a database table structure or task nodes in a message queue, to ensure that each process task is generated on demand and managed in an orderly manner.

[0048] The task pool refers to a centralized storage area used to temporarily store tasks to be assigned. Specifically, it can be implemented using an in-memory database or a distributed caching system to achieve efficient scheduling and allocation of tasks.

[0049] S2: Extract the data identifier of the task data packets in the task pool, and generate a task QR code based on the distributed lock mechanism and the data identifier of the task data packets in the task pool.

[0050] Distributed locking mechanisms refer to concurrency management protocols based on shared resource access control. Specifically, they can be implemented using atomic locks from Redis or ZooKeeper. They are used to prevent data conflicts caused by multiple operators simultaneously performing the same task. By setting up distributed locking mechanisms to control multiple concurrent tasks in a process, the order of task assignment can be ensured when multiple operators responsible for the same process simultaneously claim tasks. This ensures that the process tasks and operators can be matched one-to-one. At the same time, during the task claiming process, the processing progress status and other information of the workpiece can be updated and recorded in real time, thereby improving the reliability of workpiece product processing management.

[0051] Specifically, the task QR code is a graphical encoding generated by an encryption algorithm to uniquely identify the task data packet. This can be achieved using AES encryption combined with Base64 encoding, ensuring the uniqueness of the task identifier and the security of operation permissions. By integrating data encryption algorithms into a distributed lock mechanism, data from the product processing steps' self-acquisition process can be encrypted and protected. Simultaneously, it ensures the correlation and accuracy between each process task and its corresponding operator, enabling operators to accurately obtain the corresponding process task. The task allocation is triggered by scanning the task QR code using a scanning device, which can be a mobile terminal or an industrial barcode scanner. This dynamically binds the task to the operating equipment, enabling orderly management of workpiece production.

[0052] S3: Based on the operator's scanning and claiming operation, extract the device information identifier and target task information of the scanning device to obtain the verification data packet;

[0053] The verification data packet refers to a set of matching verification information containing device identifiers and task identifiers. Specifically, it can be implemented by encapsulating hash values ​​or digital signatures in JSON format, and is used to verify the legitimacy of operation permissions.

[0054] S4: Based on the target task information in the verification data packet, check whether the target task's task QR code is in an unlocked state. If yes, proceed to step S5; otherwise, proceed to step S6.

[0055] Specifically, the logic for determining whether a task can be claimed is based on querying the distributed lock status. This can be implemented using a lock status flag or a heartbeat detection mechanism to ensure that a task can only be allocated when it is not occupied, and that the claimed task can be unlocked to prevent different operators from claiming the same task repeatedly.

[0056] S5: Output a message indicating that the task failed to be accepted;

[0057] S6: Based on the target task information of the verification data packet, query the task data of the target task, and check whether the device information identifier of the verification data packet matches the data identifier of the task QR code. If yes, proceed to step S7; otherwise, return to step S5.

[0058] S7: Generate a task key based on the verification data packet and output a message indicating that the task has been successfully claimed.

[0059] Device information identification matching refers to the process of verifying the consistency between the hardware characteristics of the operating device and the preset permissions of the task. Specifically, it can be implemented by MAC address hashing or device certificate decryption verification to prevent unauthorized devices from operating the device by mistake.

[0060] A task key is a temporary operation permission token generated after successful verification. It can be implemented using a JWT token or a time-limited key and is used to authorize the operator to execute a specified process task.

[0061] Specifically, this embodiment of the invention achieves real-time allocation and conflict control of process tasks by combining dynamically generated task data packets with a distributed lock mechanism. At the same time, based on the dual verification mechanism of encrypted QR codes and device identifiers, it solves the problems of task lag and difficulty in process adjustment in the traditional pre-allocation mode, thereby improving the real-time tracking capability and management reliability of the processing flow.

[0062] The working process and principle of this application are as follows: A task data package for the next processing step is generated based on the product status entering the system, and this task data package is then organized in a task pool. This step enables dynamic task generation, ensuring that tasks are synchronized with the actual product status.

[0063] Next, the data identifiers of the task data packets within the task pool are extracted. Based on a distributed lock mechanism and the data identifiers, a task QR code is generated for each task data packet. The distributed lock mechanism ensures the atomicity of task state updates and prevents data inconsistencies caused by concurrent operations.

[0064] When an operator scans a code to claim a task, the system extracts the device information identifier and target task information from the scanning device to obtain a verification data packet. This step establishes the association between the task and the specific device executing it.

[0065] The system checks whether the task QR code of the target task is unlocked based on the target task information in the verification data packet. If it is unlocked, it indicates that the task has been claimed, and the system outputs a message indicating that the task claiming failed. If it is not unlocked, the system further checks whether the device information identifier in the verification data packet matches the data identifier of the task QR code.

[0066] After the matching check is successful, the system generates a task key based on the verification data packet and outputs a message indicating that the task has been successfully completed. The generation of the task key ensures that only legitimate devices can execute the task, thus improving system security.

[0067] The entire process enables dynamic task generation, synchronized status updates, device matching verification, and secure execution, effectively solving problems such as task-actual state asynchrony and device matching difficulties in the traditional pre-allocation mode.

[0068] Specifically, step S1, based on the product status entering the system, generates a task data package for the next processing step of the product, and organizes the task data package in the task pool, including:

[0069] The system schedules product processing tasks according to product specifications, detects completed processing tasks, sorts incomplete processing tasks based on product processing tasks, extracts data for the next processing task, generates a task data package for the next processing task, marks and numbers the product, and stores the generated task data package in the task pool of the management system.

[0070] Furthermore, the marking number is used to record the processing route and processing progress of the workpiece after it enters the production line. By marking the workpiece that enters the production line for the first time, the processing progress of the workpiece in the production line can be recorded in real time when the workpiece completes the current process task and updates the next process task, thereby ensuring the accuracy of the processing management of the workpiece in the production line.

[0071] The specification scheduling module determines the process flow tree by reading product process parameters and marks completed processes based on the status of process tree nodes. The sorting of incomplete processes adopts a dynamic linked list structure, and the execution order of processes is adjusted in real time according to the equipment load rate. The marking number adopts a composite coding rule, which consists of product batch number, process code and timestamp to form a unique identifier. The task data packet storage adopts a fragmented database structure, with each data packet corresponding to an independent storage unit.

[0072] Specifically, when a product enters the management system, the process analysis module calls the product specification database to generate a process flow tree and obtains the node status of completed processes through sensors. A dynamic sorting algorithm traverses the nodes of incomplete processes and generates a priority queue based on real-time equipment status data, forming an adjustable process execution sequence.

[0073] The data packet generation module extracts the process parameters and equipment configuration requirements for the next process step and encapsulates them into data units containing processing parameters and quality inspection standards. The tagging and numbering system assigns a unique identifier to each data packet, consisting of a batch number, process code, and millisecond-level timestamp, which is then mapped to an independent storage partition in the task pool using a hash algorithm. A columnar database structure is used during storage, with each data packet corresponding to an independent data block, avoiding data coupling between different process tasks.

[0074] Furthermore, based on product specifications and current processing progress, the system automatically generates task data packages for the next process and stores them in a task pool. This method improves the flexibility and efficiency of process allocation, making the product processing flow smoother. Simultaneously, by marking and numbering products, the system can accurately track the processing status of each product, facilitating real-time monitoring and management. This improvement effectively solves the time lag problem caused by traditional pre-allocation methods, enhancing the convenience and reliability of product processing management.

[0075] Specifically, step S2, which involves extracting the data identifier of the task data packets within the task pool and generating task QR codes for the task data packets based on the distributed lock mechanism and the data identifier, includes:

[0076] Obtain the data identifier of the data packet in the task pool, and encrypt the data identifier using the AES encryption algorithm;

[0077] A distributed lock mechanism is introduced to set a data lock on the encrypted data identifier, and the data lock is mapped to the corresponding task data packet based on the data identifier.

[0078] Specifically, the system first obtains the data identifier of the task data in the task pool, and generates encrypted data using the AES algorithm combined with a 256-bit key and a random number. For example, the original data D is a string combining the task number and the process code, the encryption key K is generated by a system-preset 256-bit binary sequence, and the random number IV is generated by a hardware random number generator. The encrypted data identifier C is transmitted to the distributed lock module, which creates a unique task QR code based on the data identifier and establishes a mapping relationship between the lock and the corresponding task data packet, so that the task data packets in the task pool can correspond to the task QR code. When the operator performs a scanning operation, they can directly identify and obtain the corresponding process task.

[0079] Furthermore, the step of obtaining the data identifier of the data packet within the task pool and encrypting the data identifier using the AES encryption algorithm includes:

[0080] Set the key length to 256 bits, encrypt the data content of the data identifier using the encryption key, and output the encrypted data identifier.

[0081] The encryption key is dynamically generated by the key generation module, with a key length of 256 bits to ensure a sufficiently large key space to resist brute-force attacks. After the original data of the data identifier is input into the encryption module, multiple rounds of replacement and permutation operations are performed according to the AES-256 algorithm standard. Each round of operations involves a non-linear transformation based on the encryption key and random number parameters. The encrypted data identifier is output in hexadecimal string format, with its length maintaining a fixed proportion to the original data to avoid data bloat and storage burden. This encryption method prevents unauthorized devices from tampering with or forging the data identifier during the storage and transmission of task data packets within the task pool, ensuring the reliability of the matching between device information identifiers and task QR codes in subsequent QR code scanning and claiming operations.

[0082] Specifically, the encryption algorithm formula for the data identifier is as follows:

[0083] ;

[0084] Where C represents the encrypted data, D represents the original data, K represents the encryption key, and IV represents the random number. This is an encryption operator.

[0085] Furthermore, a distributed lock is set up based on the encrypted data identifier. When an operator accesses the task pool through the device, the distributed lock module verifies the data lock status based on the data identifier. If the data lock is in a locked state, it indicates that the task is pending, and the operator can claim the task by scanning a code. The mapping connection between the encrypted data identifier and the distributed lock prevents data conflicts caused by concurrent operations from multiple devices, while AES encryption ensures the security of the data identifier during transmission.

[0086] Furthermore, during the data identification encryption stage, the encryption key K is 256 bits long, conforming to the AES-256 encryption standard, ensuring that the encryption strength meets industrial-grade security requirements. The random number IV is dynamically generated by a random number generator independent of the key generation process and injected into the algorithm in each encryption operation, introducing unpredictable random variables into the encryption process. Through the synergy of key K and random number IV, the encryption algorithm effectively improves the anti-attack capability of encrypted data while ensuring key management efficiency, preventing the risk of unauthorized unlocking of data locks due to a single encryption mode.

[0087] Specifically, a task QR code is generated based on the encrypted data identifier. To ensure the accuracy of the generated QR code information, a modulo operation checksum calculation method can be used to verify the task QR code. The verification operation is as follows:

[0088] Set the task ID as A (8-digit number, each digit designated A1, A2, ..., A8), the process number as B (2-digit number, each digit designated B1, B2), and the task generation timestamp as C (13-digit number, each digit designated C1, C2, ..., C8). 13 ).

[0089] Calculate the weighted sum S:

[0090] S = (A1×8 + A2×7 +... + A8×1) + (B1×2 + B2×1) + (C1×13 + C2×12+... + C 13 ×1);

[0091] Calculate the check digit D (4 digits):

[0092] D = (S mod 9999) + 1000 (If the result is less than 4 digits, add leading zeros; if the result is more than 4 digits, take the last 4 digits).

[0093] The verification code calculated by this formula can be used to verify the integrity and accuracy of QR code information during scanning and parsing. If the parsed verification code is inconsistent with the calculated result, the QR code is deemed invalid, thereby improving the accuracy of QR code scanning and task claiming and ensuring the operational reliability of the management system.

[0094] Specifically, step S3, based on the operator's QR code scanning and claiming operation, extracts the device information identifier and target task information of the scanning device to obtain a verification data packet, including:

[0095] During the operator's scanning and identification process, the scanning device generates a device information identifier with a key based on the built-in AES algorithm and the device information.

[0096] Based on the QR code information scanned by the operator, the target task information is extracted and combined with the device information identifier to generate verification data.

[0097] When an operator uses a scanning device to perform a barcode scan, the system obtains the current date string "date" in real time, reads the device information "N", and calls the pre-stored key factor "γ". These three elements are then input into the SHA-256 algorithm for hash calculation to generate a dynamic key "Key". This key serves as the basis for generating the device information identifier, ensuring that the device information identifier simultaneously contains information from the time dimension, device dimension, and encryption factor dimension. When the generated device information identifier is matched with the data identifier of the task QR code, it must simultaneously satisfy the time validity, device legitimacy, and encryption factor correctness. This avoids the risk of forgery due to static keys or simple combinations, ensuring that the device information identifier cannot be reverse-engineered or reused, thereby increasing the security threshold of the task claim verification process.

[0098] Specifically, the formula for generating the key is:

[0099] ;

[0100] Where Key is the key. Here, N represents the key factor, date is the current date string, and N represents the device information. This is a key generation algorithm.

[0101] Furthermore, based on the device information N automatically obtained by the system, combined with the date string "date" and a preset key factor γ, a unique key is generated using the SHA-256 algorithm. This key serves as a dynamic variable in the generation process of the device information identifier, ensuring that the identifier generated by the same device on different dates or by different devices on the same date is different. Since the key is generated based on a hash algorithm, the original parameters cannot be obtained through reverse derivation, avoiding the risk of key cracking. The dynamically changing key further ensures the timeliness of the device information identifier, prevents the reuse of historical identifiers, and thus improves the security and reliability of the QR code retrieval operation.

[0102] Specifically, step S4, which queries whether the target task's QR code is in an unlocked state based on the target task information in the verification data packet, includes:

[0103] The verification data generated when the operator scans the task QR code is used to check whether the task QR code is in an unlocked state based on the target task information in the verification data. If it is, the target task is in an claimed state; if not, the target task is in a pending state.

[0104] Specifically, the target task information in the verification data is directly obtained by scanning the task QR code and associated with the encrypted data identifier in the distributed lock mechanism. The unlocking status of the task QR code is determined by the holding status of the distributed lock. If the lock has not been released, the task is in the claimed state; if the lock has been released, the task is in the pending claim state. Furthermore, the distributed lock status query is implemented by calling the lock management interface, which returns the lock holder information and the lock's expiration time. For example, when an operator scans the task QR code, the system initiates a query request to the lock management service based on the encrypted data identifier corresponding to the QR code. The lock management service returns the current lock status; if the lock is occupied and has not expired, it is determined to be in the claimed state.

[0105] When an operator performs a QR code scanning operation, the system extracts the target task information from the verification data and initiates a status query request to the distributed lock management module based on this information. If the lock is in an unlocked state, it indicates that the current task has not been claimed, and the system marks the lock as occupied and returns a success message. If the lock is in a locked state, it determines that the task has been claimed by another operator and returns a failure message. By directly associating the distributed lock status with the unlocked status of the task QR code, task allocation conflicts caused by lock status update delays or query errors are avoided, ensuring the real-time nature and accuracy of the task claiming process.

[0106] Specifically, step S6, based on the target task information of the verification data packet, queries the task data of the target task and checks whether the device information identifier of the verification data packet matches the data identifier of the task QR code, including:

[0107] The device information identifier of the verification data is matched and decrypted with the data identifier of the task QR code. If the decryption is successful, the device information identifier matches the task QR code.

[0108] If decryption fails, the device information identifier does not match the task QR code.

[0109] Specifically, the equipment information identifier and the task QR code each carry encrypted information, and the decryption process requires a specific key. The task QR code's data identifier uses the AES encryption algorithm, and the equipment information identifier contains a built-in decryption key corresponding to the encryption algorithm. When the equipment scans the task QR code, the system automatically calls the equipment's built-in key to decrypt the data identifier. Successful decryption indicates that the equipment has legitimate operating permissions, while decryption failure indicates that permissions are missing. The decryption process further incorporates a distributed lock mechanism, linking the data lock status of the task QR code with the decryption result. Only when the data lock is locked and decryption is successful is the equipment information identifier considered a valid match. This ensures that when multiple operators scan the same task QR code, the technical effect of a one-to-one correspondence between the work process / task and the operator can be achieved.

[0110] Furthermore, when operators scan the task QR code using the scanning device, the system extracts the key from the device information identifier and performs a decryption operation on the data identifier of the task QR code. If the data identifier can be decrypted correctly, it indicates that the encryption logic of the device information identifier and the task QR code is consistent, and the two have a legitimate association. The system determines that the match is successful and allows task claiming. If decryption fails, it determines that the device does not have operating authority and prevents task claiming. This process, through the binding mechanism between the encryption algorithm and the device key, ensures that only authorized devices can complete the decryption operation, thereby eliminating the possibility of identifier forgery or mismatch, and improving the security and reliability of the task claiming process.

[0111] This invention provides a multi-process task tracking and management method. It generates task data packets based on the product status entering the system and realizes dynamic task allocation and tracking based on a distributed lock mechanism and QR code verification. By generating encrypted task identifiers and matching equipment information in real time, it solves the problems of task lag, low efficiency of abnormal handling and personnel task matching errors in the traditional pre-allocation mode. It has the advantages of improving production flexibility and quality control accuracy.

[0112] Example 2: Figure 2 A schematic diagram of the structure of a multi-process task tracking management system according to an embodiment of the present invention is shown. The management system includes:

[0113] Task Pool 10: Used to store the pending processing tasks of workpieces that have entered the system;

[0114] Data encryption module 20: used to encrypt the process task data in the task pool using a distributed lock mechanism;

[0115] Data Management Module 30: Used to store encrypted information of process task data and obtain the operator's scan-to-claim data;

[0116] Data verification module 40: Used to perform matching management of user scanning operations and target tasks.

[0117] The task pool 10 stores tasks awaiting processing, employing a database cluster architecture for distributed task data storage. The data encryption module 20 encrypts task identifiers using the AES-256 algorithm; the encryption key is generated from device information and date parameters using the SHA-256 algorithm, and a data lock is established using a Redis distributed lock mechanism. The data management module 30 includes a relational database and a time-series database, storing encrypted metadata and barcode scanning operation logs, respectively. The data verification module 40 incorporates a decryption unit and a matching engine; the matching engine uses a Bloom filter for fast data retrieval.

[0118] Specifically, when a workpiece enters the system, the task pool 10 generates a task data packet containing the process number and equipment parameters. The data encryption module 20 encrypts the data packet, generating a unique encrypted QR code, which is bound to the physical device via a distributed lock. When an operator uses a scanning device to read the QR code, the data management module 30 records operation logs such as the device MAC address and timestamp. The data verification module 40 synchronously retrieves the key factor from the encryption module and performs bidirectional decryption verification of the device information and task identifier. When the decrypted device serial number matches the device number bound to the task, the process task execution permission is granted. The entire process achieves separation of data flow and control flow through modular design. The task pool 10 and the data encryption module 20 communicate asynchronously using message queues, and the data verification module 40 interacts with external devices through an API gateway.

[0119] Through the above technical solution, this application achieves dynamic binding between process tasks and physical equipment, effectively eliminating the task idle window period under the pre-allocation mode. A distributed lock mechanism based on encrypted identifiers prevents task conflicts caused by concurrent operations of multiple devices. The barcode verification process is linked in real time with the equipment on the production floor, ensuring accurate synchronization of process flow status. When a process anomaly occurs, the task pool can quickly reconstruct the processing queue based on real-time status data, without requiring manual intervention to re-arrange tasks.

[0120] Those skilled in the art will understand that all or part of the steps in the various methods of the above embodiments can be implemented by a program instructing related hardware. The program can be stored in a computer-readable storage medium, which may include: read-only memory (ROM), random access memory (RAM), magnetic disk or optical disk, etc.

[0121] Furthermore, the embodiments of the present invention have been described in detail above. Specific examples have been used to illustrate the principles and implementation methods of the present invention. The descriptions of the above embodiments are only for the purpose of helping to understand the method and core ideas of the present invention. At the same time, for those skilled in the art, there will be changes in the specific implementation methods and application scope based on the ideas of the present invention. Therefore, the content of this specification should not be construed as a limitation of the present invention.

Claims

1. A multi-process task tracking and management method, characterized in that, The management method includes: S1: Based on the product status entering the system, generate a task data package for the next processing step of the product, and organize the task data package in the task pool; S2: Extract the data identifier of the task data packets in the task pool, and generate a task QR code based on the distributed lock mechanism and the data identifier of the task data packets in the task pool. S3: Based on the operator's scanning and claiming operation, extract the device information identifier and target task information of the scanning device to obtain the verification data packet; S4: Based on the target task information in the verification data packet, check whether the target task's task QR code is in an unlocked state. If yes, proceed to step S5; otherwise, proceed to step S6. S5: Output a message indicating that the task failed to be accepted; S6: Based on the target task information of the verification data packet, query the task data of the target task, and check whether the device information identifier of the verification data packet matches the data identifier of the task QR code. If yes, proceed to step S7; otherwise, return to step S5. S7: Generate a task key based on the verification data packet and output a message indicating that the task has been successfully claimed.

2. The multi-process task tracking and management method according to claim 1, characterized in that, Step S1 includes: Schedule product processing tasks according to product specifications, detect completed processing tasks, and sort incomplete processing tasks according to product processing tasks. Extract the data for the next processing step of the product and generate a task data package for the next processing step of the product. The products are labeled and numbered, and the generated task data packages are stored in the task pool of the management system.

3. The multi-process task tracking and management method according to claim 1, characterized in that, Step S2 includes: Obtain the data identifier of the data packet in the task pool, and encrypt the data identifier using the AES encryption algorithm; A distributed lock mechanism is introduced to set a data lock on the encrypted data identifier, and the data lock is mapped to the corresponding task data packet based on the data identifier.

4. The multi-process task tracking and management method according to claim 3, characterized in that, The step of obtaining the data identifier of the data packet in the task pool and encrypting the data identifier using the AES encryption algorithm includes: Set the key length to 256 bits, encrypt the data content of the data identifier using the encryption key, and output the encrypted data identifier.

5. The multi-process task tracking and management method according to claim 4, characterized in that, The encryption algorithm formula for the data identifier is: ； Where C is the encrypted data, D is the original data, K is the encryption key, and IV is the random number.

6. The multi-process task tracking and management method according to claim 1, characterized in that, Step S3 includes: During the operator's scanning and identification process, the scanning device generates a device information identifier with a key based on the built-in AES algorithm and the device information. Based on the QR code information scanned by the operator, the target task information is extracted and combined with the device information identifier to generate verification data.

7. The multi-process task tracking and management method according to claim 6, characterized in that, The formula for generating the key is: ； Where Key is the key. Here, is the key factor, date is the current date string, and N is the device information.

8. The multi-process task tracking and management method according to claim 1, characterized in that, Step S4 includes: The verification data generated when the operator scans the task QR code is used to check whether the task QR code is in an unlocked state based on the target task information in the verification data. If it is, the target task is in an claimed state; if not, the target task is in a pending state.

9. The multi-process task tracking and management method according to claim 1, characterized in that, Step S6 includes: The device information identifier of the verification data is matched and decrypted with the data identifier of the task QR code. If the decryption is successful, the device information identifier matches the task QR code. If decryption fails, the device information identifier does not match the task QR code.

10. A multi-process task tracking and management system, characterized in that, The tracking and management system is used to execute the management method as described in any one of claims 1 to 9, the management system comprising: Task pool: Used to store the pending processing tasks of workpieces that have entered the system; Data encryption module: used to encrypt the process task data in the task pool using a distributed lock mechanism; Data management module: used to store encrypted information of process task data and obtain the operator's scan-to-claim data; Data verification module: Used to perform matching and management of user scanning operations and target tasks.

Images