Intelligent correction method and system for abnormal identification in medical fabric handover process

Abstract

The application discloses an intelligent correction method and system for abnormal identification in a medical fabric handover process, and relates to the technical field of a cargo identification system based on RFID. The method comprises the following steps: performing non-full-quantity comparison according to a second RFID identification set and first comparison data to determine whether the current carrier has identification abnormalities; and triggering a review process for the current carrier if it is determined that the current carrier has identification abnormalities. The application triggers the acquisition of first comparison data on demand by means of a circulation task identification, then performs non-full-quantity comparison based on the first comparison data, then triggers a review process when an abnormality occurs, and finally corrects the relevant RFID (RFID Electronic Product Code (EPC)) identification set according to the review result. The technical means can reduce the communication overhead, storage overhead and calculation overhead required for abnormal identification in the medical fabric handover process, improve the abnormal identification efficiency, and improve the accuracy and reliability of the medical fabric handover data.

Description

Technical Field

[0001] This invention relates to the field of RFID-based cargo identification system technology, and in particular to an intelligent correction method and system for anomaly identification during the handover of medical fabrics. Background Technology

[0002] Medical textiles typically include reusable fabrics such as hospital gowns, surgical gowns, sheets, duvet covers, and drapes. Medical textiles moving between hospitals, transportation facilities, and laundry plants are usually handed over and managed in units such as bags, baskets, boxes, and trolleys. For laundry plants or hospital logistics departments, these textiles require batch identification similar to warehouse goods and transit goods during handover, temporary storage, incoming inventory, and subsequent sorting. Therefore, existing technologies typically combine RFID tags (i.e., RFID Electronic Product Codes, EPCs), RFID readers, terminal devices, and servers to form a goods identification system for identifying, recording, and tracing groups of medical textiles.

[0003] In the RFID management method for medical textiles using relevant technologies, the hospital packages the medical textiles to be recycled and then scans the textiles inside the package or bag using an RFID reader. When the package or bag arrives at the laundry plant, it is scanned again using RFID, and the scan data from the laundry plant is compared with the scan data from the hospital to confirm whether the quantity and details of the medical textiles are consistent. This method can, to a certain extent, achieve handover management between the hospital and the laundry plant.

[0004] However, in actual handover processes, medical textiles are typically transported in units such as bags, baskets, boxes, or trolleys. A single transport task may involve multiple carriers, each containing multiple RFID tags. When the second reading station at the laundry plant's handover point reads the current carrier, directly comparing the RFID tag set of the current carrier with the RFID tag sets of all carriers in that transport task would incur significant communication, storage, and computational overhead. Especially when the second terminal at the second reading station has limited computing power and requires RFID tag scanning of each bag passing through the station, if an abnormal carrier remains at the second reading station awaiting full verification, it will affect subsequent carriers entering the second reading station, reducing the overall line processing efficiency. Summary of the Invention

[0005] The purpose of this invention is to solve at least one of the above problems and provide an intelligent correction method and system for anomaly identification during the handover process of medical fabrics, which can reduce the computer resource overhead for anomaly identification during the handover process of medical fabrics and improve the efficiency of anomaly identification during the handover process of medical fabrics.

[0006] To achieve the above-mentioned objective, this invention provides an intelligent correction method for anomaly identification during the handover process of medical fabrics, the method comprising: The first terminal performs RFID reading on the target carrier carrying medical fabric at the first reading station, obtains the first RFID tag set corresponding to the target carrier, and sends the first RFID tag set to the server so that the server associates and stores the first RFID tag set with the transfer task record. The second terminal obtains the flow task identifier corresponding to the current flow task and sends a comparison data request carrying the flow task identifier to the server. The second terminal receives the first comparison data sent by the server in response to the comparison data request; wherein, the first comparison data is generated based on the first RFID tag set corresponding to multiple target carriers under the current circulation task, and the first comparison data is used to perform non-full representation of the first RFID tag set corresponding to the multiple target carriers; The second terminal performs RFID reading on the current carrier that has been transferred to the second reading station, obtains the second RFID tag set corresponding to the current carrier, and sends the second RFID tag set to the server so that the server associates and stores the second RFID tag set with the transfer task record. The second terminal performs a partial comparison between the second RFID tag set and the first comparison data to determine whether the current carrier has any identification anomalies. If the second terminal determines that there is an identification anomaly in the current carrier, it triggers a review process for the current carrier. Based on the review results of the review process, the server determines the set of RFID tags to be corrected from the first RFID tag set and the second RFID tag set associated with the workflow task, and corrects the set of RFID tags to be corrected.

[0007] On the other hand, the present invention also provides an intelligent correction system for abnormal identification during the handover process of medical fabrics. The system includes a memory, a processor, and a computer program stored in the memory. When the processor executes the computer program, it implements the steps of the above method performed by the first terminal, the second terminal, or the server.

[0008] Compared with the related technologies that directly compare the RFID tag set of the current carrier with the RFID tag sets of all carriers under the same transfer task in full detail, the present invention has at least the following advantages: First, in this invention, after obtaining the flow task identifier corresponding to the current flow task, the second terminal sends a comparison data request carrying the flow task identifier to the server. In response to this request, the server only sends the first comparison data corresponding to the current flow task. Therefore, the second terminal does not need to pre-acquire or store the complete RFID tag set details for multiple flow tasks; instead, it only acquires the comparison data corresponding to the current flow task as needed when the current flow task enters the second reading station. This reduces the data storage volume of the second terminal and the data transmission volume between the server and the second terminal.

[0009] Secondly, the first comparison data is generated based on the first RFID tag set corresponding to multiple target carriers under the current circulation task, and is used to perform a partial full-scale characterization of the first RFID tag set corresponding to multiple target carriers. After obtaining the second RFID tag set corresponding to the current carrier, the second terminal performs a partial full-scale comparison between the second RFID tag set and the first comparison data, rather than directly performing a full-scale detailed comparison between the second RFID tag set and each of the multiple first RFID tag sets under the current circulation task. Therefore, when determining whether there is an identification anomaly in the current carrier, the amount of data that needs to be compared can be reduced, the computer resource overhead of the second terminal can be reduced, and the efficiency of anomaly identification can be improved.

[0010] In summary, the present invention reduces the communication, storage, and computational overhead required for anomaly identification during the medical fabric handover process by triggering the acquisition of the first comparison data on demand through the transfer task identifier, then performing a non-full comparison based on the first comparison data, followed by triggering a review process when an anomaly occurs, and finally correcting the relevant RFID tag set based on the review results. This improves the efficiency of anomaly identification and enhances the accuracy and reliability of medical fabric handover data. Attached Figure Description

[0011] To make the technical problems solved by this invention, the technical means adopted, and the technical effects achieved clearer, specific embodiments of this invention will be described in detail below with reference to the accompanying drawings. However, it should be noted that the drawings described below are merely drawings of exemplary embodiments of this invention. Those skilled in the art can obtain drawings of other embodiments based on these drawings without any creative effort.

[0012] Figure 1 This is a schematic diagram of the intelligent correction process for anomaly identification during the handover of medical fabrics according to an embodiment of the present invention; Figure 2 This is a schematic diagram of the process for determining whether the current carrier has an identification anomaly in one embodiment of the present invention; Figure 3 This is a schematic diagram of the process for generating a carrier-level fingerprint in one embodiment of the present invention; Figure 4 This is a flowchart illustrating the process of triggering the current carrier review process in one embodiment of the present invention; Figure 5 A schematic diagram of the intelligent correction process for anomaly identification during the handover of medical fabrics, provided as another embodiment of the present invention; Figure 6 This is a flowchart illustrating a suspected duplicate reading anomaly in one embodiment of the present invention. Figure 7 This is a schematic diagram of the process for determining the target first RFID tag set and the differential RFID tag set corresponding to the current carrier to be reviewed in one embodiment of the present invention; Figure 8 This is a flowchart illustrating the intelligent correction process for anomaly identification during the handover of medical fabrics, as provided in another embodiment of the present invention. Figure 9 This is a schematic diagram of the process for detecting whether the object to be verified belongs to the current carrier in one embodiment of the present invention. Detailed Implementation

[0013] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, 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, 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.

[0014] The intelligent correction method for anomaly identification during the handover process of medical textiles provided in this invention is mainly applied to a full lifecycle management system for medical textiles consisting of a hospital, a laundry plant, and a server. The medical textiles include reusable textiles such as hospital gowns, surgical gowns, sheets, duvet covers, and drapes. Each piece of medical textile has a high-temperature resistant and washable UHF RFID (Ultra-High Frequency Radio Frequency Identification) tag sewn inside. This RFID tag stores a unique Electronic Product Code (EPC), which will be referred to as the RFID identifier. The medical textiles can include reusable textiles such as hospital gowns, surgical gowns, sheets, duvet covers, drapes, and towels. The target carrier or current carrier can be a bag, basket, box, trolley, or other carrier unit used to carry the medical textiles. The first reading station can be a reading station located at the medical textile recycling end or bagging end, and the second reading station can be a reading station located at the handover point in the laundry plant, equipped with a tunnel-type RFID reading device. The execution entities involved in this invention include a first terminal, a second terminal, and a server. The first terminal, located at the first RFID reading station (typically at the hospital), performs RFID readings on the carrier at the hospital and uploads the results to the server. The second terminal, located at the second RFID reading station (typically at the handover point in the laundry factory), performs RFID readings again after the carrier arrives at the laundry factory, compares the data with the first comparison data sent by the server, identifies anomalies, and triggers a review process. The server can communicate with both the first and second terminals via the internet and is used to store workflow records, generate the first comparison data, respond to requests from the second terminal, and process correction actions.

[0015] In one example, the hospital's weekly soiled medical textiles are manually or mechanically sorted into 50 bags, each containing several pieces of RFID-tagged medical textiles. These 50 bags constitute a single circulation task and are collected by a laundry plant. It should be noted that the number of textiles in each bag is not strictly uniform. Sometimes, when manually filling bags, operators seal them when they deem them full. Alternatively, bags may be sealed even if not full, as the collection vehicle has arrived. Laundry plant operators can bring a primary terminal to the hospital, or the primary terminal can be a device installed at the hospital. The operators use an RFID reader connected to this primary terminal to read the RFID tags on each bag individually and upload the reading results to a server via the primary terminal. Subsequently, a driver transports the 50 bags to the laundry plant's handover point. Before placing each bag into the tunnel-type RFID reader, the laundry plant's handover personnel can obtain the circulation task identifier corresponding to the current circulation task for that batch of bags. Specifically, in one example, to facilitate obtaining the task identifier for each transfer task, when the personnel receiving the batch of carriers corresponding to the current transfer task from the hospital, they will use a pre-carried RFID tag as the batch RFID tag for that transfer task. Then, they will use a first terminal to read this batch RFID tag, which will then be used as the transfer task identifier for the current transfer task. The personnel will then affix this batch RFID tag to one of the 50 carriers. Alternatively, the 50 carriers corresponding to the same transfer task can be placed in a larger transport bag with the batch RFID tag affixed to it, so that the batch RFID tag can be removed and read upon arrival at the factory. Generally, carriers with different markings can be provided for different hospitals to quickly distinguish the hospitals corresponding to different carriers. When the personnel arrive at the factory, before placing each carrier of the transfer task into the tunnel-type RFID reader, they can first use an RFID reader connected to a second terminal to read the batch RFID tag corresponding to that batch of carriers to obtain the transfer task identifier for the current transfer task. The second terminal sends the batch of RFID tags as a transfer task identifier to the server, and the server returns the corresponding comparison data to the second terminal based on the received transfer task identifier.Alternatively, in one example, after the first terminal uploads all the reading results corresponding to a certain transfer task at the hospital to the server, the server will assign a transfer task identifier to that transfer task and then return the transfer task identifier and the hospital information corresponding to that transfer task to the second terminal. When the handover personnel arrive at the factory, they can enter the specific hospital information, such as the hospital name, into the search interface of the second terminal to match the transfer task identifier corresponding to that hospital information. After the handover personnel confirm, the second terminal can also obtain the transfer task identifier corresponding to each transfer task.

[0016] Reference Figure 1 In one embodiment, an intelligent correction method for anomaly identification during the handover process of medical fabrics is provided, the method comprising: In step S201, the first terminal performs RFID reading on the target carrier carrying medical fabric at the first reading station, obtains the first RFID tag set corresponding to the target carrier, and sends the first RFID tag set to the server so that the server associates and stores the first RFID tag set with the transfer task record.

[0017] In this step, the first reading station can be an RFID reading station at the hospital, department, recycling, or bagging end. The target carrier can be a bag, basket, box, or trolley containing medical textiles. The first RFID tag set refers to the RFID tag set obtained by the first terminal after RFID reading the medical textiles in the target carrier at the first reading station. It should be noted that each target carrier corresponds to one first RFID tag set, and one transfer task corresponds to multiple target carriers, thus corresponding to multiple first RFID tag sets. For example, if a target carrier BAG_001 contains 100 pieces of medical textiles, and the RFID tags read by the first terminal are {T1,T2,...,T100}, then this set can be used as the first RFID tag set corresponding to BAG_001.

[0018] In one possible implementation, when the first terminal sends the first RFID tag set to the server, it may also send at least one of the following: carrier serial number, number of first tags, first reading time, first terminal identifier, and hospital information. Upon receiving this data, the server associates and stores the first RFID tag set with the corresponding transfer task record. In this step, the server can save the RFID reading results of each target carrier at the first reading station on a per-transfer-task basis, providing benchmark data for subsequent anomaly identification and verification at the second reading station.

[0019] In step S202, the second terminal obtains the flow task identifier corresponding to the current flow task and sends a comparison data request carrying the flow task identifier to the server.

[0020] In this step, a transfer task identifier is used to identify a single medical textile transfer task. For example, a transfer task may correspond to a batch of medical textiles collected at the hospital and transported to a laundry facility. The transfer task identifier can be represented by a batch RFID tag, barcode, QR code, task number, or manually entered information.

[0021] In one example, 50 carriers corresponding to the same transfer task can be packed into a larger transport bag, which is affixed with a batch RFID tag. At the handover point in the laundry plant, the handover personnel use an RFID reader connected to a second terminal to read the batch RFID tag, obtain the transfer task identifier corresponding to the current transfer task, and send a comparison data request carrying the transfer task identifier to the server. In this step, the second terminal does not pre-acquire data corresponding to all transfer tasks, but rather requests comparison data on demand based on the transfer task identifier before the current transfer task actually enters the second reading station, thereby reducing the data storage pressure on the second terminal.

[0022] Step S203: The second terminal receives the first comparison data sent by the server in response to the comparison data request. The first comparison data is generated based on the first RFID tag set corresponding to multiple target carriers under the current transfer task, and is used to perform a partial representation of the first RFID tag set corresponding to the multiple target carriers.

[0023] In this step, the first comparison data is generated based on the first RFID tag set corresponding to multiple target carriers under the current workflow task. The first comparison data is used to perform a non-full representation of the first RFID tag set corresponding to multiple target carriers. The so-called non-full representation means that the first comparison data does not directly include all the details of the first RFID tags corresponding to each target carrier, but includes summary-type, fingerprint-type, or compressed data that can be used to represent the first RFID tag set corresponding to each target carrier.

[0024] In one implementation, the first comparison data may include a local fingerprint database containing multiple first carrier-level fingerprints, each corresponding to a target carrier in the current workflow task. For example, if the current workflow task includes 50 carriers, the server can generate 50 first carrier-level fingerprints based on the first RFID tag sets corresponding to each of the 50 carriers, and send these 50 first carrier-level fingerprints as the first comparison data to the second terminal, without needing to send all RFID details of the 50 carriers to the second terminal. In this embodiment, the first comparison data performs a partial representation of the first RFID tag set, which reduces the amount of data sent by the server to the second terminal and also reduces the amount of data that the second terminal needs to store for anomaly identification.

[0025] In step S204, the second terminal performs RFID reading on the current carrier transferred to the second reading station, obtains the second RFID tag set corresponding to the current carrier, and sends the second RFID tag set to the server so that the server associates and stores the second RFID tag set with the transfer task record.

[0026] In this step, the second reading station is a tunnel-type RFID reader. The current carrier refers to the carrier currently entering the reading area of ​​the second reading station; that is, among the 50 carriers corresponding to the transfer task, the carrier placed into the tunnel-type RFID reader by the personnel is the current carrier. The second RFID tag set refers to the set of RFID tags obtained by the second terminal after RFID reading the current carrier at the second reading station.

[0027] For example, after a carrier enters the tunnel-type RFID reader, 99 RFID tags are read after deduplication. These 99 RFID tags form the second RFID tag set corresponding to the current carrier. In one possible implementation, after the current carrier enters the second reading station, the handover personnel prevent other carriers from entering the second reading station temporarily to avoid mixed reading of RFID tags from multiple carriers. The next carrier is only placed into the second reading station after the current carrier leaves. Single-carrier reading can improve the accuracy of the correspondence between the second RFID tag set and the current carrier, and reduce the impact of cross-reading of adjacent carriers on the anomaly detection results.

[0028] Step S205: The second terminal performs a partial comparison between the second RFID tag set and the first comparison data to determine whether there is an identification anomaly in the current carrier.

[0029] In this step, non-full comparison means that the second terminal does not directly perform a full and detailed comparison of the second RFID tag set with the first RFID tag set of multiple target carriers under the current circulation task, but instead compares the second RFID tag set with the first comparison data.

[0030] In one implementation, the second terminal can generate a second carrier-level fingerprint based on a second RFID tag set, and compare the second carrier-level fingerprint with multiple first carrier-level fingerprints in the first comparison data. If the second carrier-level fingerprint matches any of the first carrier-level fingerprints, it is determined that the current carrier does not have an identification anomaly; if the second carrier-level fingerprint does not match any of the first carrier-level fingerprints, it is determined that the current carrier has an identification anomaly. It can be seen that in this step, the second terminal can perform anomaly identification based on incomplete characterization data, reducing the amount of data that needs to be compared, lowering computational resource overhead, and improving the anomaly judgment efficiency of the current carrier at the second reading station.

[0031] Step S206: If the second terminal determines that there is an identification anomaly in the current carrier, it triggers a verification process for the current carrier.

[0032] In this step, anomaly identification can include discrepancies between the RFID tag sets corresponding to the first and second reading stations, such as under-reading, over-reading, cross-reading, repeated reading, or differences in transportation handover. The verification process can include single-item discrepancy location, verification object prompting, re-RFID reading, entry into the verification station, manual verification, or server data correction requests. For example, when the second terminal determines that the current carrier does not match any of the first carrier-level fingerprints under the current transfer task, the verification process can be triggered to further determine the cause of the anomaly and the RFID tag set to be corrected. This step allows for targeted verification processing upon anomaly identification, rather than directly releasing the abnormal carrier, thereby improving the reliability of medical fabric handover data.

[0033] In step S207, the server determines the set of RFID tags to be corrected from the first RFID tag set and the second RFID tag set associated with the workflow task based on the review result of the review process, and corrects the set of RFID tags to be corrected.

[0034] Specifically, after receiving the verification result, the second terminal sends the verification result of the verification process or a correction request generated based on the verification result to the server and then sends the correction request to the server. In this step, the RFID tag set to be corrected can be either the first RFID tag set or the second RFID tag set corresponding to the verification result. For example, if the verification result shows that the first reading station missed reading an RFID tag, the server can add the RFID tag to the corresponding first RFID tag set; if the verification result shows that an RFID tag does not belong to the corresponding carrier, the server can delete the RFID tag from the corresponding RFID tag set or add an abnormal marker to it. In this step, the abnormal identification does not stop at discovering inconsistencies, but further corrects the relevant RFID tag set according to the verification result, thereby forming a closed loop of identification, verification, and correction.

[0035] Reference Figure 2 In one embodiment, the first comparison data includes a local fingerprint database corresponding to the current workflow task. The local fingerprint database includes multiple first carrier-level fingerprints, which are generated based on a first RFID tag set corresponding to multiple target carriers under the current workflow task. Each first carrier-level fingerprint includes a first structural fingerprint and a first tag quantity.

[0036] For example, if the current transfer task includes 50 carriers, the server can generate 50 first carrier-level fingerprints based on the 50 first RFID tag sets, and then send these 50 first carrier-level fingerprints to the second terminal to form a local fingerprint database. Therefore, in this embodiment, the second terminal only needs to store the carrier-level fingerprint corresponding to the current transfer task, and does not need to store all RFID details under multiple transfer tasks, which helps to reduce the storage overhead of the second terminal. Specifically, the first carrier-level fingerprints can be generated according to the following steps S401 to S404.

[0037] In this embodiment, the second terminal performs a partial comparison between the second RFID tag set and the first comparison data to determine whether the current carrier has any identification anomalies, specifically including: Step S301: The second terminal generates a second carrier-level fingerprint corresponding to the current carrier based on the second RFID tag set.

[0038] In this step, the second carrier-level fingerprint can be generated according to steps S401 to S404 below. The second carrier-level fingerprint includes a second structural fingerprint and a second number of identifiers. For example, if 100 RFID tags are read from the current carrier at the second reading station, the second terminal can generate a second structural fingerprint based on the 100 RFID tags and combine the second structural fingerprint with the second number of identifiers to form the second carrier-level fingerprint.

[0039] In step S302, the second terminal performs an XOR operation between the second structural fingerprint in the second carrier-level fingerprint and the first structural fingerprint in each of the first carrier-level fingerprints in the local fingerprint database to obtain multiple candidate difference identifiers. Each candidate difference identifier corresponds to one first carrier-level fingerprint.

[0040] In this step, each candidate difference identifier corresponds to a first carrier-level fingerprint. Assuming the local fingerprint database includes first carrier-level fingerprints A1, A2, and A3, and the current carrier corresponds to a second carrier-level fingerprint B, the second terminal can calculate: D1 = FP_B ⊕ FP_A1; D2 = FP_B ⊕ FP_A2; D3 = FP_B ⊕ FP_A3; where D1, D2, and D3 are candidate difference identifiers. In this step, the second terminal can quickly obtain the difference representation between the current carrier and each of the first carriers through XOR operations between structural fingerprints, without first downloading and comparing the details of each first RFID identifier set.

[0041] In step S303, if there is a candidate difference identifier with a value of zero, the second terminal determines that there is no identification anomaly in the current carrier and deletes the first carrier-level fingerprint corresponding to the candidate difference identifier with a value of zero from the local fingerprint database.

[0042] In this step, a candidate difference flag of zero indicates that the second structural fingerprint is identical to the corresponding first structural fingerprint. In one possible implementation, the number of flags can be further considered; that is, when the candidate difference flag is zero and the number of first and second flags is the same, it is determined that the current carrier does not have any identification anomalies. For example, if D2=0, it means that the current carrier matches the first carrier corresponding to A2 in the fingerprint dimension, the current carrier can be determined to be normal, and A2 can be deleted from the local fingerprint database. In this step, normal carriers can be quickly allowed to proceed; simultaneously, deleting the matched first carrier-level fingerprint can narrow the candidate comparison range for subsequent carriers, reducing subsequent computational load.

[0043] In step S304, if all the candidate difference identifiers are not zero, the second terminal determines that the current carrier has an identification anomaly.

[0044] In this step, if all candidate difference identifiers are non-zero, it indicates that the current carrier does not completely match any of the first carriers in the local fingerprint database, thus confirming that the current carrier has an identification anomaly. For example, if the current carrier corresponds to a second RFID tag set of 99 RFID tags, and the remaining first carrier-level fingerprints in the local fingerprint database are all XORed with these second carrier-level fingerprints and the result is not zero, then it can be determined that the current carrier needs further verification.

[0045] In one embodiment, the first carrier-level fingerprint and the second carrier-level fingerprint are generated in the following manner: Step S401: Deduplicate the RFID tag set corresponding to the carrier to obtain the deduplicated RFID tag set.

[0046] In this step, deduplication is used to remove duplicates of the same RFID tag that have been read repeatedly during a single reading process. For example, if the RFID reader reads {T1,T2,T2,T3} in a single reading process, the deduplicated set of RFID tags will be {T1,T2,T3}. Deduplication prevents the same RFID tag from being read repeatedly, thus avoiding deviations from the true set in carrier-level fingerprint calculations and improving the accuracy of subsequent anomaly detection.

[0047] Step S402: Convert each RFID tag in the deduplicated RFID tag set into a fixed-length normalized binary tag.

[0048] In this step, normalizing binary identifiers refers to converting RFID tags into binary data of the same length according to a preset encoding method. For example, an EPC format RFID tag can be converted into 96-bit or other fixed-length binary data. If different RFID tags have different original representations, a fixed-length representation can be formed through methods such as padding, truncation, encoding conversion, or unified field parsing. It is understandable that converting all RFID tags into fixed-length data facilitates subsequent XOR operations.

[0049] Step S403: Perform an XOR operation on the obtained multiple normalized binary identifiers to obtain the structural fingerprint corresponding to the carrier.

[0050] In this step, the structural fingerprint is obtained by performing an XOR operation on the normalized binary identifiers corresponding to multiple RFID tags within the same carrier. For example, if a carrier includes RFID tags T1, T2, and T3, the structural fingerprint can be represented as: FP = T1⊕T2⊕T3; where "⊕" represents a bitwise XOR operation. Since the XOR operation satisfies the commutative and associative laws, the structural fingerprints obtained by {T1,T2,T3} and {T3,T1,T2} are the same. Considering that when RFID readers perform anti-collision reading based on the EPC Gen2 protocol, the tag response order is determined by the random time slot allocation of the Q algorithm, the reading order of RFID tags from different models of readers, the same reader at different times, and different physical workstations (hospital and laundry factory) cannot be guaranteed to be consistent. The bitwise XOR method used in this step makes the generated structural fingerprint completely independent of the reading order, avoiding the unreliability of any order-sensitive method in multi-workstation reading scenarios. Even if the reading order of RFID tags at different workstations is different, it will not affect the calculation result of the structural fingerprint.

[0051] Step S404: Generate the carrier-level fingerprint based on the structural fingerprint and the number of identifiers in the deduplicated RFID identifier set; wherein, the structural fingerprint is independent of the order of the RFID identifiers in the deduplicated RFID identifier set.

[0052] In this step, the carrier-level fingerprint can include a structural fingerprint and an identifier count. The identifier count represents the number of RFID tags in the deduplicated RFID tag set. For example, the carrier-level fingerprint can be represented as (FP, C), where FP is the structural fingerprint and C is the RFID tag count. If the structural fingerprint of a bag of medical fabric is FP1 and the count is 100, then its carrier-level fingerprint can be represented as (FP1, 100). In this embodiment, by using both the structural fingerprint and the count to characterize the RFID set within the carrier, the reliability of the set characterization can be improved while maintaining a small data volume.

[0053] It should be noted that the generation methods corresponding to steps S401 to S404 are applicable to both the generation of the first carrier-level fingerprint on the server side and the generation of the second carrier-level fingerprint on the second terminal side.

[0054] Reference Figure 4 In one embodiment, when all the candidate difference identifiers are not zero, triggering the review process for the current carrier specifically includes: Step S501: The second terminal filters the multiple candidate difference identifiers based on preset filtering conditions; wherein, the preset filtering conditions include RFID identifier encoding rules.

[0055] In this step, the preset screening conditions include at least RFID tag encoding rules. The RFID tag encoding rules refer to the encoding rules of the RFID tags used on the medical fabric, including preset EPC prefixes, specific field formats, check digit rules, etc. In one embodiment, the RFID tags used in the laundry factory may all conform to the GS1SGTIN-96 standard and have a unified enterprise code prefix; in this case, the RFID tag encoding rules mean that candidate difference tags must conform to the SGTIN-96 format and have the enterprise code prefix.

[0056] Optionally, the preset filtering conditions also include a quantity filtering condition: the absolute value of the difference between the number of first identifiers of the first carrier-level fingerprint corresponding to the candidate difference identifier and the number of second identifiers of the second carrier-level fingerprint is 1. This quantity filtering condition means that if the candidate difference identifier corresponds to a single RFID missed read anomaly, the difference in the number of elements between the first RFID identifier set and the second RFID identifier set corresponding to the candidate difference identifier is only 1.

[0057] For example, suppose the second RFID tag set corresponding to the current carrier contains 99 RFID tags, and the local fingerprint database contains 49 first carrier-level fingerprints (i.e., the remaining 49 target carriers to be matched). The second terminal performs an XOR operation on the second carrier-level fingerprints and the 49 first carrier-level fingerprints respectively, obtaining 49 candidate difference tags. If a quantity-based filtering condition is used, the second terminal first filters out first carrier-level fingerprints with a first tag quantity of 98 or 100 (i.e., the absolute value of the quantity difference is 1), assuming 3 candidate difference tags are retained after filtering. Then, these 3 candidate difference tags are filtered using RFID tag encoding rules, assuming 1 candidate difference tag is retained. This retained candidate difference tag is the target for subsequent steps.

[0058] In this step, the dual filtering combination of "quantity screening + RFID tag encoding rule screening" can precisely narrow down the candidate difference range from all candidate difference tags to a single candidate difference tag. The computational cost of quantity screening is significantly less than that of RFID tag encoding rule screening (the former only requires a subtraction and absolute value comparison of the number of bound tags, while the latter requires multiple pattern matching operations on 96-bit binary data). Performing quantity screening first can quickly eliminate most obviously non-compliant candidate difference tags, improving screening efficiency.

[0059] In step S502, if the second terminal obtains a candidate difference identifier that uniquely meets the preset screening conditions, it determines the candidate difference identifier that uniquely meets the preset screening conditions as the target difference identifier.

[0060] In this step, the target difference identifier refers to the unique candidate difference identifier retained in the candidate difference identifier set after the screening in step S501. Since the screening was performed based on the RFID identifier encoding rules in step S501, the target difference identifier corresponds exactly to a real RFID identifier at the binary level. This RFID identifier is the root cause of the identification anomaly of the current carrier—it may have been missed at the first reading station, or it may have been missed at the second reading station (or lost during transportation).

[0061] In step S503, the second terminal identifies the medical fabric corresponding to the target difference identifier as the review object in the review process.

[0062] In this step, the object of verification refers to the specific medical fabric that needs further verification in the verification process. Since the target difference identifier corresponds to a specific RFID tag at the binary level, and this RFID tag uniquely corresponds to one piece of medical fabric, the object of verification is the specific medical fabric corresponding to that RFID tag. This step can precisely narrow the verification scope of the verification station from all medical fabrics within the entire carrier (e.g., 100 pieces) to a single piece of medical fabric, reducing the verification workload by approximately 99%, significantly reducing manpower costs, and avoiding low processing efficiency caused by long verification times.

[0063] In step S504, the second terminal determines the first carrier-level fingerprint to which the first structural fingerprint that participated in generating the target difference identifier belongs as the target first carrier-level fingerprint, and selects the target carrier corresponding to the target first carrier-level fingerprint as the selected target carrier.

[0064] In this step, the target first carrier-level fingerprint refers to the first carrier-level fingerprint that is XORed with the second carrier-level fingerprint in step S302 to obtain the target difference identifier. The selected target carrier refers to the target carrier corresponding to the target first carrier-level fingerprint—that is, the target carrier suspected of having a single-item difference from the current carrier's reading result at the first reading station. For example, suppose in step S302, the second terminal XORs the second carrier-level fingerprint with 49 first carrier-level fingerprints in the local fingerprint database to obtain 49 candidate difference identifiers; after filtering in step S501, only one candidate difference identifier is retained, and the unique candidate difference identifier corresponds to the 17th first carrier-level fingerprint in the local fingerprint database; then this step determines the 17th first carrier-level fingerprint as the target first carrier-level fingerprint, and the target carrier corresponding to it (such as the bag numbered BAG_017) is selected as the target carrier.

[0065] In step S505, the second terminal detects whether the object to be reviewed belongs to the current carrier. If yes, the output review result is used to indicate that the selected target carrier has experienced a missed read anomaly; if no, the output review result is used to indicate that the current carrier has experienced a missed read anomaly.

[0066] In one example, the specific method for detecting whether the object to be verified belongs to the current carrier is as follows: The target difference identifier is matched sequentially with each RFID tag in the second RFID tag set corresponding to the current carrier. If the target difference identifier successfully matches with any RFID tag in the second RFID tag set, it indicates that the RFID tag of the object to be verified has been successfully read at the second reading station, thus indicating that the object to be verified belongs to the current carrier; if the target difference identifier fails to match with any RFID tag in the second RFID tag set, it indicates that the RFID tag of the object to be verified has not been read at the second reading station.

[0067] When the object to be verified belongs to the current carrier, the current carrier physically contains the object to be verified. However, if the selected target carrier fails to read the RFID tag corresponding to the object to be verified during hospital-side reading, it indicates that a reading error occurred at the first reading station. Therefore, the output verification result is used to indicate that a reading error occurred at the selected target carrier. The second terminal sends a correction request to the server, which instructs the server to add the RFID tag corresponding to the target difference tag to the first RFID tag set corresponding to the selected target carrier and add a corrected mark. In this embodiment, the reading error is only used as a naming convention to indicate that the RFID tag corresponding to the object to be verified was not read at a certain station. It does not mean that a reading error actually occurred at a certain station. The actual reasons may include RFID reading error, fabric loss, cross-carrier cross-reading, or duplicate recording, etc. The actual reasons can be further confirmed by subsequent manual or business rules.

[0068] If the object to be verified does not belong to the current carrier, there are three possibilities: (a) the selected target carrier has recorded the RFID tag multiple times at the first reading station (i.e., the RFID tag is not actually in the carrier but was read at the first reading station); (b) the object to be verified was lost during transportation; (c) the object to be verified was missed during an occasional reading at the second reading station. To rule out scenario (c), if the object to be verified is detected as not belonging to the current carrier, the second terminal controls the tunnel RFID reader to perform RFID reading and deduplication on the current carrier again to obtain an updated second RFID tag set, and then checks again whether the object to be verified belongs to the current carrier. If the detection result is still that the object to be verified does not belong to the current carrier, scenario (c) can be ruled out, and it is finally determined that the current carrier has experienced a missed reading anomaly (i.e., the RFID tag should be in the current carrier but was not read, possibly due to scenario a or scenario b). The second terminal sends a correction request to the server, which instructs the server to delete the RFID tag corresponding to the target difference identifier from the first RFID tag set corresponding to the selected target carrier and add a corrected tag.

[0069] In this embodiment, by detecting whether the object to be reviewed belongs to the current carrier, the carrier corresponding to the missed read anomaly can be deduced. This allows for the determination of the RFID tag set to be corrected from the first and second RFID tag sets associated with the workflow task, and the correction of this set of RFID tags can be performed. Specifically, the review results of this application enable the correction action to have a clear direction (i.e., adding or deleting), avoiding erroneous modifications to the reading records; simultaneously, it provides data for subsequent responsibility demarcation.

[0070] In step S506, the second terminal deletes the first carrier-level fingerprint corresponding to the target difference identifier from the local fingerprint database.

[0071] In this step, after completing the verification and correction of the current carrier, the second terminal deletes the target first carrier-level fingerprint from the local fingerprint database, reducing the number of fingerprints in the local fingerprint database by 1. This embodiment is consistent with the dynamic maintenance mechanism of the local fingerprint database described in step S303, which allows the local fingerprint database to continuously shrink as the processing progresses, reducing the comparison overhead of subsequent carriers and providing an accurate basis for the remaining fingerprint data in the subsequent centralized processing at the verification station.

[0072] Reference Figure 5 In one embodiment, the method further includes: In step S601, if the second terminal does not obtain a candidate difference identifier that meets the preset screening conditions, it controls the current carrier to enter the verification station and allows the next carrier to enter the second reading station.

[0073] In the case of "no candidate difference identifier that meets the preset screening conditions is obtained", this situation usually occurs when there is more than one RFID tag that is missed or overread in the current carrier. It can be seen that the screening in step S501 cannot obtain a unique target difference identifier.

[0074] In this step, the verification station refers to a station located after the second reading station for temporarily storing carriers to be verified. If the current carrier still fails to accurately locate the anomaly using the above embodiments, the second terminal controls the conveyor belt to transport the current carrier to the verification station for temporary storage, awaiting subsequent centralized processing. Simultaneously, the control panel of the second terminal displays a prompt message, instructing the personnel to place the next carrier into the tunnel-type RFID reader at the second reading station.

[0075] As described above, by using a fast and slow channel diversion architecture that allows the next carrier to enter the second reading station when the location cannot be quickly determined, abnormal carriers that cannot be processed quickly do not block the throughput of the sorting line; normal carriers can continue to enter the second reading station for processing; thus significantly improving the sorting efficiency of the entire line.

[0076] Step S602: When the number of carriers leaving the second reading station in the transfer task reaches the number of carriers corresponding to the transfer task, the second terminal triggers the centralized processing flow of the verification station.

[0077] In this step, the second terminal continuously records the number of carriers leaving the second reading station during the transfer task. When the number of carriers reaches the preset total number of carriers corresponding to the transfer task (e.g., 50), it indicates that all target carriers under the transfer task have completed the first round of processing through the second reading station, and the centralized processing flow of the review station can be triggered.

[0078] For example, a certain workflow task corresponds to 50 target carriers. After all carriers have been processed at the second identification station, 47 carriers are found to be without anomalies or with only one missed or extra RFID tag read. These 47 carriers are then precisely processed and enter the sorting station. The sorting station receives carriers determined to have no identification anomalies and diverts them to the corresponding processing channels according to the type of medical fabric. For instance, if the sorting station determines that all carriers are trousers based on their RFID tags, they are diverted to the trousers processing channel. If the RFID tags indicate that the carrier contains multiple types of fabrics (e.g., trousers, sheets, and shirts), it is diverted to the manual sorting channel. The remaining 3 carriers are temporarily stored at the verification station awaiting centralized processing. When the total number of the 47 carriers plus the 3 carriers (i.e., 50) equals the preset total number of carriers for the workflow task, the centralized processing flow is triggered.

[0079] The centralized processing flow includes steps S6021 to S6023.

[0080] Step S6021: The second terminal requests the first RFID tag set corresponding to the remaining first carrier-level fingerprints in the local fingerprint database from the server.

[0081] In this step, since there are no anomalies or the anomalies are only a missed or overread RFID tag in the above embodiments, the first carrier-level fingerprint that has been successfully matched or accurately processed has been deleted from the local fingerprint database. Therefore, the remaining first carrier-level fingerprints in the local fingerprint database correspond to the target carrier that has not yet been accurately matched (that is, the carrier to be reviewed temporarily stored in the review station). The second terminal sends the fingerprint values ​​corresponding to the remaining first carrier-level fingerprints (e.g., 3 remaining) in the local fingerprint database to the server. The server searches for the corresponding first RFID tag set (e.g., 3 first RFID tag sets) based on the fingerprint values ​​and sends them to the second terminal.

[0082] In this embodiment, a delayed download mechanism that downloads only a few remaining RFID details as needed upon batch completion significantly saves bandwidth compared to downloading all RFID details at the start of the workflow task. In one example, if only 3 out of 50 carriers enter the verification station, the download volume is reduced by approximately 94%.

[0083] Step S6022: The second terminal obtains the set of carriers to be reviewed in the review station.

[0084] In this step, the set of carriers to be reviewed refers to the collection of all carriers temporarily stored in the review station. The second terminal performs review processing on each carrier in the set of carriers to be reviewed in a cyclical manner.

[0085] In step S6023, the second terminal determines whether the set of carriers to be reviewed is empty; if the set of carriers to be reviewed is not empty, the review process corresponding to steps S60231 to S60236 is executed; if the set of carriers to be reviewed is empty, the centralized processing process of the review station is terminated.

[0086] Step S60231: The second terminal determines the current carrier to be reviewed from the set of carriers to be reviewed.

[0087] In this step, the current carrier to be reviewed refers to the carrier to be reviewed that needs to be processed in this loop. In one embodiment, the current carrier to be reviewed can be any carrier selected from the set of carriers to be reviewed.

[0088] In step S60232, the second terminal obtains the third RFID tag set and the number of third tags corresponding to the current carrier to be verified.

[0089] In one optional implementation, the third RFID tag set refers to the set of all RFID tags obtained after using an RFID reader to perform RFID reading and deduplication on the current carrier to be verified; the third tag quantity refers to the number of elements in the third RFID tag set.

[0090] For example, the personnel in charge take out the carrier to be reviewed (such as BAG_007), use the RFID reader at the review station to read and deduplicate the RFID tags in the carrier again, and obtain a third RFID tag set, assuming it contains 97 RFID tags; then the number of the third tags is 97.

[0091] Step S60233: The second terminal determines the comparison order between the third RFID tag set and each of the first RFID tag sets based on the quantity difference between the third tag quantity and the first tag quantity corresponding to each of the first RFID tag sets; wherein, the first RFID tag set with the larger absolute value of the quantity difference has a higher comparison priority.

[0092] In this step, the comparison order refers to the execution order in which the third RFID tag set and each of the first RFID tag sets are compared for set differences in the subsequent step S60234. The second terminal calculates the absolute value of the difference between the number of the third tag and the number of each first tag in the first RFID tag set corresponding to the remaining first carrier-level fingerprint obtained in step S6021 (i.e., the absolute value of the quantity difference), and sorts the remaining first RFID tag sets in descending order of the absolute value of the quantity difference to obtain the comparison order.

[0093] For example, the remaining three first RFID tag sets obtained in step S6021 are SET_A, SET_B, and SET_C, with corresponding first tag counts of 97, 98, and 101, respectively; the third tag count is 97. The absolute values ​​of the count differences are calculated as |97-97|=0, |97-98|=1, and |97-101|=4, respectively. Sorting the count differences from largest to smallest, the comparison order is: SET_C (count difference 4), SET_B (count difference 1), and SET_A (count difference 0).

[0094] This step employs a priority comparison strategy. Specifically, cases where the quantity difference is equal to 0 or 1 have typically been handled in the aforementioned normal matching or single-item difference processing flow (such as single-item missed reading anomalies). Carriers that can enter the verification station are more likely to belong to multiple-item differences. Therefore, in this embodiment, prioritizing the comparison of the first RFID tag set with a quantity difference greater than 1 can result in an earlier hit, thereby improving comparison efficiency and reducing comparison overhead.

[0095] In step S60234, the second terminal performs a set difference comparison between the third RFID tag set and each of the first RFID tag sets according to the comparison order, and determines the target first RFID tag set and the difference RFID tag set corresponding to the current carrier to be reviewed.

[0096] In this step, the target first RFID tag set refers to the first RFID tag set that actually corresponds to the carrier currently being verified. The difference RFID tag set refers to the differences between the third RFID tag set and the target first RFID tag set. For example, if the third RFID tag set is {T1,...,T97} and a certain first RFID tag set is {T1,...,T101}, then the difference RFID tag set includes {T98,T99,T100,T101}.

[0097] In step S60235, the second terminal generates a correction request based on the set of differential RFID tags.

[0098] In this step, the correction request can be used to request the server to correct the status of the target first RFID tag set, the second RFID tag set, or the transfer task. For example, when the verification result shows that the current carrier to be verified has 4 fewer RFID tags than the target first RFID tag set, the correction request can be used to instruct the server to perform operations such as deletion, addition, or marking on the relevant RFID tag set.

[0099] In step S60236, the second terminal removes the current carrier to be reviewed from the set of carriers to be reviewed and returns to execute step S6023.

[0100] In this step, after the current carrier to be reviewed completes the review process, it is removed from the carrier set to be reviewed. If the carrier set to be reviewed is still not empty, the next round of review processing continues; if the carrier set to be reviewed is empty, the centralized processing process ends.

[0101] In one embodiment, such as Figure 6 As shown, when multiple candidate difference identifiers satisfying the preset filtering conditions are obtained through filtering, the method further includes: Step S701: The second terminal detects whether there is a target candidate difference identifier among the plurality of candidate difference identifiers that meet the preset screening conditions; wherein, the first carrier-level fingerprint corresponding to the target candidate difference identifier and the second carrier-level fingerprint satisfy the single-item difference condition; the single-item difference condition includes: the absolute value of the difference between the number of first identifiers of the first carrier-level fingerprint corresponding to the target candidate difference identifier and the number of second identifiers of the second carrier-level fingerprint is 1.

[0102] In this step, the target candidate difference identifier refers to the candidate difference identifier that satisfies the single-item difference condition between the corresponding first carrier-level fingerprint and the second carrier-level fingerprint. The single-item difference condition may include: the absolute value of the difference between the number of first identifiers of the first carrier-level fingerprint and the number of second identifiers of the second carrier-level fingerprint corresponding to the target candidate difference identifier is 1. For example, if the current carrier corresponds to 100 second identifiers, and the two first carrier-level fingerprints correspond to 99 and 101 first identifiers respectively, and the candidate difference identifiers obtained by XORing these two with the second carrier-level fingerprint both conform to the RFID coding rules, then these two candidate difference identifiers can be used as the target candidate difference identifier.

[0103] In step S702, when the second terminal detects that there are at least two target candidate difference identifiers, it determines that there is a suspected duplicate reading anomaly at the first reading station.

[0104] In this step, a suspected duplicate reading anomaly indicates that the same actual carrier may be read as multiple first-end carrier records at the first reading station, or that multiple highly similar first RFID tag sets have been formed. For example, if carrier B currently has 100 RFID tags, and there are two records, A1 and A2, at the first end, where A1 differs from B by only one RFID tag, and A2 also differs from B by only one RFID tag, then it can be determined that there may be a duplicate reading or duplicate filing anomaly at the first end. In this embodiment, when multiple candidates all show single-item differences, the system does not forcibly select one candidate for correction, but instead identifies it as a suspected duplicate reading anomaly, thereby reducing the risk of miscorrection.

[0105] In step S703, the second terminal sends a duplicate reading correction request to the server. The duplicate reading correction request is used to instruct the server to merge, delete, mark, or verify the first RFID tag set corresponding to the first carrier-level fingerprints corresponding to the at least two target candidate difference tags.

[0106] In this step, the duplicate identification correction request instructs the server to merge, delete, mark, or verify the first RFID tag set corresponding to the first carrier-level fingerprints of at least two target candidate difference identifiers. For example, the server can mark two suspected duplicate first RFID tag sets as pending manual verification, or delete one of the duplicate records based on the manual verification result.

[0107] like Figure 7 As shown, in one embodiment, step S60234, which involves comparing the third RFID tag set with each of the first RFID tag sets according to the comparison order to determine the target first RFID tag set and the difference RFID tag set corresponding to the current carrier to be reviewed, specifically includes: In step S801, the second terminal determines the absolute value of the quantity difference corresponding to each of the first RFID tag sets, and sets N=1. Here, the absolute value of the quantity difference is the absolute value of the difference between the number of third tags in the third RFID tag set and the number of first tags in the corresponding first RFID tag set, and N is a positive integer variable.

[0108] In this step, the absolute value of the quantity difference refers to the absolute value of the difference between the number of third identifiers in the third RFID identifier set and the number of first identifiers in the corresponding first RFID identifier set. N is a positive integer variable used to represent the current comparison round. For example, if the number of third identifiers in the third RFID identifier set D is 101, and the number of first identifiers in the three first RFID identifier sets A, B, and C are 99, 101, and 102 respectively, then the absolute values ​​of the quantity difference for A, B, and C are: A: |101-99|=2, B: |101-101|=0, C: |101-102|=1. Initially, let N=1, indicating that we are currently in the first round of member matching. This step provides basic data for subsequent round-based screening of candidate first RFID identifier sets. That is, whether each first RFID identifier set participates in the Nth round of member matching depends on whether its absolute value of the quantity difference meets the screening criteria for the Nth round.

[0109] In step S802, the second terminal determines the Nth round of candidate first RFID tag sets from each of the first RFID tag sets. The absolute value of the difference in the number of candidates in the Nth round of candidate first RFID tag sets is greater than or equal to N-1.

[0110] It should be noted that in the rules for determining the candidate first RFID tag set in the Nth round, the "absolute value of the quantity difference is greater than or equal to N-1" is not an arbitrarily increasing threshold, but rather a lower bound condition for the quantity difference determined by the matching results of previous members. Specifically, when the comparison process enters the Nth round, it means that the target first RFID tag set has not yet been determined in the previous N-1 rounds of member matching. For a certain candidate first RFID tag set, if none of the RFID tags selected from the third RFID tag set in the previous N-1 rounds are matched in the candidate first RFID tag set, it means that the third RFID tag set has shown at least N-1 unmatched selected RFID tags relative to the candidate first RFID tag set. In the scenario of quantity-based differences, these at least N-1 unmatched selected RFID tags correspond to the lower bound of the difference scale between the third RFID tag set and the candidate first RFID tag set. Therefore, only when the absolute value of the quantity difference corresponding to the candidate first RFID tag set is greater than or equal to N-1 can it continue to explain the previous missed results; if the absolute value of the quantity difference is less than N-1, the size of the quantity difference of the candidate first RFID tag set is insufficient to explain the previous missed results, and continuing to participate in the Nth round of member matching will increase the overhead of invalid comparisons.

[0111] For example, the third RFID tag set includes a1, a2, ..., a99, x, y, totaling 101 RFID tags; the first RFID tag set A includes a1, a2, ..., a99, totaling 99 RFID tags; the first RFID tag set B has 101 tags; and the first RFID tag set C has 102 tags. At this point, the absolute values ​​of the quantity differences for the first RFID tag sets A, B, and C are 2, 0, and 1, respectively. If in the first round x is selected from the third RFID tag set for member matching, and A, B, and C all fail to match, then for the above candidate sets, there is already one RFID tag selected from the third RFID tag set but not matched. In the second round, the absolute value of the quantity difference for the first RFID tag set B is 0, which is less than the lower bound of 1 required for the second round. This indicates that the first RFID tag set B is insufficient to explain the observed miss result in the quantity difference scenario. Therefore, in the second round, it is not necessary to continue comparing the first RFID tag set B; only the first RFID tag sets A and C, whose absolute values ​​of quantity differences are greater than or equal to 1, need to be included in the comparison. If the second round of member matching for y still fails, then in the third round, two RFID tags selected from the third RFID tag set but not matched have been observed. At this point, only the first RFID tag set A with an absolute difference in quantity greater than or equal to 2 needs to be retained. Since the first RFID tag set A and the third RFID tag set have common RFID tags a1 to a99, selecting any RFID tag from this common part in the third round will result in a match, thus determining the first RFID tag set A as the target first RFID tag set.

[0112] Therefore, the above rule does not simply adjust the screening threshold arbitrarily with each round. Instead, it transforms the number of missing RFID tags observed in previous member matching into a lower bound of the number difference required for the candidate first RFID tag set to continue participating in subsequent rounds of comparison. This rule can exclude candidate first RFID tag sets whose number difference is insufficient to explain the previous missing results, reducing invalid comparisons caused by their continued participation in member matching. Furthermore, compared to using a fixed, high number difference threshold or threshold adjustment methods lacking evidence of missing results, this rule only raises the candidate retention criteria when there are already supporting missing results, thereby reducing the risk of candidate sets being excluded without basis and improving the efficiency and reliability of determining the target first RFID tag set during the centralized review phase.

[0113] If the method of always retaining the entire candidate set is adopted, it is impossible to reduce the number of subsequent comparison objects based on the previous miss results; if a fixed high threshold or a threshold that is unrelated to the number of misses is adopted, the candidate set may be excluded in the absence of member matching results; if the method of the absolute value of the quantity difference is less than or equal to the round threshold is adopted, the candidate set with smaller quantity difference will be retained first, which is difficult to adapt to the application scenario of the centralized review stage in this embodiment, which mainly deals with the quantity of multiple differences.

[0114] In step S803, the second terminal performs Nth round member matching on the third RFID tag set and each of the Nth round candidate first RFID tag sets according to the comparison order.

[0115] In this step, the Nth round of member matching refers to determining, in the current comparison round N, whether there are common RFID tags between the third RFID tag set and the Nth round candidate first RFID tag set that can be used to determine the correspondence. The comparison order can be obtained from the comparison order determined in step S60233 of the above embodiment. For example, the first RFID tag set with the larger absolute value of the quantity difference can be compared first. In the example of S701, the absolute values ​​of the quantity difference are A=2, C=1, and B=0, so the comparison order of the first round can be A, C, B. For example, the third RFID tag set D is: {a1,a2,...,a99,x,y}, the first RFID tag set A is: {a1,a2,...,a99}, the first tag number of the first RFID tag set B is 101, and the first tag number of the first RFID tag set C is 102. If the first round candidate first RFID tag sets are A, B, and C, then the second terminal can perform the first round of member matching for D and A, D and C, and D and B respectively according to the comparison order of A, C, B.

[0116] The specific member matching method in this step can be implemented in various ways. For example, in one implementation, an RFID tag that has not been selected before can be selected from the third RFID tag set as the current matching RFID tag, and it can be determined whether the current matching RFID tag exists in the candidate first RFID tag set of each Nth round. In another implementation, the method described in subsequent steps S8031 to S8037 can also be used, that is, between the third RFID tag set and the current candidate first RFID tag set, the RFID tag corresponding to the current comparison round N is selected from the side with fewer tags, and member matching is performed with the other side.

[0117] In step S804, if the third RFID tag set and any candidate first RFID tag set in the Nth round match are matched in the Nth round, the second terminal determines the matched candidate first RFID tag set in the Nth round as the target first RFID tag set corresponding to the current carrier to be reviewed, and performs a set difference comparison between the third RFID tag set and the target first RFID tag set to obtain the difference RFID tag set.

[0118] In this step, "hit" means that the current RFID tag exists in a certain candidate first RFID tag set in the Nth round. If the current RFID tag hits a certain first RFID tag set, it can be considered that the first RFID tag set has a high probability of corresponding with the current carrier to be reviewed, and therefore it is determined as the target first RFID tag set. For example, in one example, the third RFID tag set is: {a1,a2,...,a99,x,y}, and the first RFID tag set C is: {a1,a2,...,a99,x,y,z}. If the current RFID tag selected in the first round is x, and x exists in C, then C can be determined as the target first RFID tag set. Subsequently, the set difference between the third RFID tag set and C is compared to obtain the difference RFID tag set: {z}. This difference RFID tag set can be used to generate a correction request or to prompt the reviewer to check the medical fabric corresponding to z. In this embodiment, after a candidate set is hit, the full set difference comparison is no longer performed on other first RFID tag sets. Instead, the full set difference calculation is only performed on the third RFID tag set and the target first RFID tag set, thereby reducing the number of full set comparisons.

[0119] In step S805, if the second terminal fails to match any of the third RFID tag set and each of the Nth round candidate first RFID tag sets in the Nth round member matching, it sets N to N+1 and returns to the step of determining the Nth round candidate first RFID tag set from each of the first RFID tag sets, that is, returns to step S802 until the target first RFID tag set is determined or the stopping condition is met.

[0120] In this step, if the current RFID tag does not match any candidate first RFID tag set in the Nth round, it indicates that the current RFID tag may belong to the third RFID tag set, which contains additional difference tags compared to the target first RFID tag set. At this time, the second terminal increments the comparison round N by 1 and returns to execute step S802. For example, if x is selected in the first round, and x does not match A, C, or B, then N=2. In the second round, if y is selected as the current RFID tag, it is only matched with the first RFID tag sets A and C, where the absolute value of the quantity difference is greater than or equal to 1, and is no longer matched with B, where the absolute value of the quantity difference is 0. If y still does not match A and C in the second round, then N=3. In the third round, it is only matched with A, where the absolute value of the quantity difference is greater than or equal to 2. Since A includes a1, a2, ..., a99, selecting any RFID tag from a1 to a99 in the third RFID tag set will match A, thus determining A as the target first RFID tag set.

[0121] The stopping condition means that in step S902, when the current comparison round N is greater than M and the target first RFID tag set has not yet been determined, the second terminal marks the current carrier to be reviewed as pending manual review and stops the set difference comparison.

[0122] In this embodiment, by combining the absolute value of the quantity difference with the current comparison round N, the range of candidate first RFID tag sets is dynamically narrowed in each round of member matching, reducing unnecessary candidate set comparisons. Specifically, whenever a round of matching fails, the number of first RFID tag sets participating in the comparison is reduced in the next round based on the absolute value of the quantity difference, thereby reducing invalid matches and improving the efficiency of the review process.

[0123] In one embodiment, step S803, which involves performing Nth round member matching between the third RFID tag set and each of the Nth round candidate first RFID tag sets according to the comparison order, specifically includes: Step S8031: The second terminal determines the current candidate first RFID tag set from the candidate first RFID tag set of the Nth round that has not yet undergone the Nth round of member matching, according to the comparison order.

[0124] In this step, the Nth round candidate first RFID tag set may include one or more first RFID tag sets. The current candidate first RFID tag set refers to the candidate set that needs to be matched with the third RFID tag set in the Nth round. The second terminal determines the current candidate first RFID tag set from the Nth round candidate first RFID tag sets that have not yet undergone Nth round member matching according to the comparison order.

[0125] For example, in the first round, the first candidate first RFID tag set includes A, B, and C, and the comparison order is A, C, B. If A has not yet undergone the first round of member matching, then A is determined as the current candidate first RFID tag set. If A is not matched, then C is determined as the new current candidate first RFID tag set from the candidate sets that have not yet undergone the first round of member matching.

[0126] This step ensures that each candidate first RFID tag set in the Nth round is processed sequentially according to the comparison order, avoiding the termination of the Nth round member matching by comparing only one candidate set.

[0127] In step S8032, the second terminal determines the RFID tag set with the smaller number of tags in the third RFID tag set and the current candidate first RFID tag set based on the number of third tags in the third RFID tag set and the number of first tags in the current candidate first RFID tag set, and determines the other one as the RFID tag set to be matched.

[0128] In this step, the candidate RFID tag set is the set used to provide currently matching RFID tags; the matching RFID tag set is the set used to determine whether a currently matching RFID tag exists. For example, the third RFID tag set D is {a1,a2,...,a99,x,y}, with 101 third tags. The current candidate first RFID tag set A is {a1,a2,...,a99}, with 99 first tags. Since the number of tags in A is less than the number of tags in D, A is determined as the candidate RFID tag set, and D is determined as the matching RFID tag set. As another example, the current candidate first RFID tag set C is {a1,a2,...,a99,x,y,z}, with 102 first tags, while D has 101 third tags. Therefore, D is determined as the candidate RFID tag set, and C is determined as the matching RFID tag set.

[0129] In this embodiment, in scenarios with abnormal quantity differences, the side with more tags may typically contain more RFID tags than the other side. If an RFID tag is selected from the side with more tags, the extra RFID tags may be selected, resulting in a miss; if an RFID tag is selected from the side with fewer tags, it is easier to match the other side, thereby improving the member matching hit rate.

[0130] In step S8033, the second terminal determines the RFID tag corresponding to the current comparison round N from the candidate RFID tag set as the currently matched RFID tag, based on the current comparison round N. The RFID tags in the candidate RFID tag set are arranged in a preset order, and the RFID tag corresponding to the current comparison round N is the Nth RFID tag in the candidate RFID tag set arranged in the preset order.

[0131] In this step, the RFID tags in the candidate RFID tag set can be arranged in a preset order. The preset order can be the numerical order of the RFID tags, lexicographical order, server-issued order, first reading order, second reading order, or other order that can stably determine the position of elements within the set. In one implementation, the second terminal can represent the candidate RFID tag set as an array and determine the array element corresponding to the current comparison round N as the currently matching RFID tag. For example, when N=1, the first RFID tag in the array is selected; when N=2, the second RFID tag is selected; and when N=3, the third RFID tag is selected. For example, if the candidate RFID tag set A is [a1, a2, ..., a99], when the current comparison round N=1, a1 is selected as the currently matching RFID tag; and when the current comparison round N=2, a2 ​​is selected as the currently matching RFID tag.

[0132] In this embodiment, the second terminal does not need to maintain a record of selected RFID tags for each first RFID tag set, nor does it need to allocate additional storage space for multiple candidate sets to record selected elements. The current matching RFID tag in this round can be determined by the current comparison round N and the preset order in the candidate RFID tag sets, thereby reducing memory usage and simplifying the comparison control logic.

[0133] Step S8034: The second terminal determines whether the currently matched RFID tag exists in the set of RFID tags to be matched.

[0134] In this step, the second terminal can determine whether the currently matching RFID tag exists in the set of RFID tags to be matched by traversal query, hash query, index query, or other member query methods. For example, if the currently matching RFID tag is a1, and the set of RFID tags to be matched D is {a1,a2,...,a99,x,y}, since a1 exists in D, it is determined that the currently matching RFID tag exists in the set of RFID tags to be matched.

[0135] Step S8035: If the currently matched RFID tag exists in the set of RFID tags to be matched, the second terminal determines that the third RFID tag set and the current candidate first RFID tag set match in the Nth round of member matching.

[0136] In this step, if the currently matching RFID tag exists in the set of RFID tags to be matched, it means that there is a common RFID tag between the third RFID tag set and the current candidate first RFID tag set. Therefore, it can be determined that the third RFID tag set and the current candidate first RFID tag set have matched in the Nth round of member matching. For example, the third RFID tag set D is {a1,a2,...,a99,x,y}, and the current candidate first RFID tag set A is {a1,a2,...,a99}. When the first RFID tag a1 is selected from A and it is determined that a1 exists in D, it can be determined that D and A have matched in the first round of member matching. Subsequently, the second terminal identifies A as the target first RFID tag set and performs a complete set difference comparison between D and A to obtain the difference RFID tag set: {x,y}.

[0137] In this embodiment, the target candidate set can be located by a single member matching, avoiding the need to perform a complete set difference comparison on multiple first RFID tag sets.

[0138] In step S8036, if the currently matched RFID tag does not exist in the set of RFID tags to be matched, and there is a set of candidate first RFID tags for the Nth round that has not yet undergone the Nth round of member matching, the second terminal determines a new set of current candidate first RFID tags from the set of candidate first RFID tags for the Nth round that has not yet undergone the Nth round of member matching according to the comparison order, and returns to execute step S8032.

[0139] In this step, if the current candidate first RFID tag set fails to match in the Nth round, and there are still candidate sets in the Nth round candidate first RFID tag set that have not yet undergone member matching, the second terminal determines a new current candidate first RFID tag set according to the comparison order and continues to execute steps S8032 to S8035. For example, in the first round, the first round candidate first RFID tag set includes A, C, and B, and the comparison order is A, C, B. If A fails to match, the second terminal determines C as the new current candidate first RFID tag set and re-executes steps S8032 to S8035. If C also fails to match, then processing continues with B.

[0140] In this embodiment, the remaining candidate sets are processed only when the current candidate first RFID tag set is not matched, so that the Nth round member matching can completely traverse all Nth round candidate first RFID tag sets.

[0141] In step S8037, if the currently matched RFID tag does not exist in the set of RFID tags to be matched, and there is no set of candidate first RFID tags for the Nth round that has not yet undergone the Nth round of member matching, the second terminal determines that the third RFID tag set and each of the candidate first RFID tags for the Nth round have not been matched in the Nth round of member matching.

[0142] In this step, if all candidate first RFID tag sets in round N have completed member matching and none have been matched, the second terminal can determine that the third RFID tag set and each candidate first RFID tag set in round N have not been matched in the member matching of round N. Subsequently, the second terminal sets N=N+1 and returns to step S802 to redetermine the candidate first RFID tag sets for the next round. For example, the candidate first RFID tag sets in round 1 include A, C, and B. If A, C, and B have all completed member matching in round 1 and none have been matched, the second terminal determines that none of them have been matched in round 1 and proceeds to round 2.

[0143] In this embodiment, the next round is only entered if all candidate sets are not matched in the Nth round, thus ensuring that the judgment that none of the candidate sets are matched in the Nth round has a complete data basis.

[0144] In this embodiment, when the second terminal performs member matching between the third RFID tag set and a candidate first RFID tag set in the Nth round, it does not always select RFID tags from the third RFID tag set. Instead, it compares the number of tags in both sets, designating the set with fewer tags as the candidate RFID tag set and the other set as the set to be matched. Then, based on the current comparison round N, the second terminal determines the corresponding RFID tag from the candidate RFID tag set as the currently matched RFID tag and checks whether the currently matched RFID tag exists in the set of RFID tags to be matched.

[0145] In this embodiment, in each pair of "third RFID tag set and Nth round candidate first RFID tag set" member matching, the RFID tag corresponding to the current comparison round N is selected from the side with fewer tags, thereby reducing the probability of selecting redundant and different RFID tags and improving the hit rate of a single member matching. Furthermore, by arranging the candidate RFID tag sets in a preset order and directly selecting the Nth RFID tag based on the current comparison round N, the second terminal does not need to maintain a record of selected RFID tags for each candidate set, reducing the memory overhead required for state recording and simplifying the comparison control logic in the review stage.

[0146] like Figure 8 As shown, in one embodiment, the method further includes: Step S901: The second terminal determines the maximum value M among the absolute values ​​of the quantity differences corresponding to each of the first RFID tag sets. Here, M is an integer variable.

[0147] In this step, the second terminal can further determine the maximum value M based on the already determined absolute values ​​of multiple quantity differences. For example, if the number of third identifiers in the third RFID identifier set corresponding to the carrier to be verified is 101, and the number of first identifiers in the remaining three first RFID identifier sets A, B, and C are 99, 101, and 102 respectively, then the absolute values ​​of the quantity differences corresponding to the three first RFID identifier sets are: A: |101-99|=2, B: |101-101|=0, C: |101-102|=1. Therefore, the maximum value M among the absolute values ​​of quantity differences is 2.

[0148] The effective range of rounds in the automatic set difference comparison process is determined by the absolute value of the maximum quantity difference. In other words, if the current comparison round has exceeded the absolute value of the maximum quantity difference and still fails to hit the target first RFID tag set, it means that the current carrier to be reviewed no longer conforms to the quantity-type difference rule that is prioritized in this embodiment.

[0149] In step S902, if the current comparison round N is greater than M and the target first RFID tag set has not yet been determined, the second terminal marks the current carrier to be reviewed as pending manual review and stops the set difference comparison.

[0150] In this step, the current comparison round N can be the positive integer variable used in step S803 above to control multi-round member matching. If the current comparison round N is greater than the absolute value of the maximum quantity difference M, and the target first RFID tag set is still not determined, the second terminal can stop the automatic set difference comparison process and mark the current carrier to be reviewed as awaiting manual review. For example, continuing the example of step S901, M=2. If the first round N=1 fails, the second round N=2 fails, and the third round N=3 still fails to determine the target first RFID tag set, then since N=3 is greater than M=2, the second terminal can mark the current carrier to be reviewed as awaiting manual review and stop the automatic set difference comparison process.

[0151] It should be noted that the automatic processing flow in this embodiment is mainly applicable to quantity-based discrepancies. A quantity-based discrepancy can be understood as follows: the difference between the first RFID tag set and the third RFID tag set is mainly manifested in one having one or more RFID tags more or less than the other. For example, the first RFID tag set A is {a1,a2,...,a99}, and the third RFID tag set is {a1,a2,...,a99,x,y}. In this case, the third RFID tag set has two more RFID tags than the first RFID tag set A, which constitutes a quantity-based discrepancy.

[0152] Conversely, if the first RFID tag set and the third RFID tag set have the same number of tags, but each set contains different RFID tags, for example: first RFID tag set: {a1,a2,...,a99,x}, third RFID tag set: {a1,a2,...,a99,y}. In this case, although the quantity is the same, there is a substitution-type difference, such as adding a piece of fabric after bagging and scanning at the hospital, while another piece of fabric is lost during transportation. Therefore, this embodiment does not need to perform automatic correction for such situations, but instead marks the current carrier to be reviewed as awaiting manual review.

[0153] In this embodiment, when the current carrier to be reviewed does not conform to the automatic processing rules for quantitative discrepancies, invalid automatic matching can be terminated in a timely manner to avoid further consumption of computing resources. Simultaneously, by transferring the process to manual review, the risk of mismatches and miscorrections can be reduced, improving the reliability of anomaly handling.

[0154] It should be noted that during the handover of medical textiles, reading anomalies are more likely to manifest as quantitative differences. Specifically, medical textiles are typically transported in units such as bags, baskets, boxes, or trolleys, with each unit containing multiple medical textiles tagged with RFID. When RFID batch readings are performed at the first and second reading stations respectively, common anomalies include RFID missed reads, duplicate reads, occasional cross-reads, missing textiles during transport, and changes in the results of subsequent reads at the verification station. These anomalies usually result in the current unit's RFID tag set showing one or more more RFID tags or one or more fewer RFID tags than a given first RFID tag set, i.e., a quantitative difference.

[0155] In contrast, substitution-type differences typically refer to situations where two RFID tag sets have the same number of tags but different set members. This type of situation usually requires the simultaneous presence of "at least one missing RFID tag" and "at least one extra RFID tag," with the two canceling each other out in quantity. For example, a medical fabric that should belong to the current carrier might not be read, while another medical fabric that does not belong to the current carrier might be read incorrectly or mistakenly, resulting in a substitution-type difference where the number of tags is the same but the set members are different. Therefore, in the medical fabric handover scenario addressed in this application, compared to quantitative differences caused by simple missed reads, simple overreads, simple missing tags, or simple cross-reads, substitution-type differences usually require multiple abnormal factors to occur simultaneously. Their occurrence conditions are more complex, and their frequency is generally lower than that of quantitative differences.

[0156] Based on the characteristics of the above scenario, this embodiment prioritizes using the absolute value of the quantity difference as the screening criterion for the candidate first RFID tag set during the centralized processing stage of the review station. Specifically, in the Nth round of member matching, only the first RFID tag set with an absolute value of the quantity difference greater than or equal to N-1 is retained for comparison, so that the retention condition of the candidate set corresponds to the number of missing RFID tags observed in the previous rounds. This reduces the number of comparisons of invalid candidate sets for quantity-related differences that are more common in the handover of medical fabrics, improving the efficiency of determining the target first RFID tag set in the centralized review stage. For substitution-type differences where the quantity is the same but the members are different, or in cases where the target first RFID tag set cannot be determined by the quantity-related difference rule, the corresponding carrier to be reviewed can be marked as awaiting manual review to reduce the risk of mismatch and miscorrection.

[0157] Therefore, this application does not arbitrarily select the absolute value of the quantity difference as the basis for comparison. Instead, it combines the absolute value of the quantity difference with the comparison round N based on the characteristics of the scenario where quantity differences are more common and replacement differences are usually composite anomalies in the RFID handover process of medical fabrics. This allows for priority processing of higher frequency quantity anomalies, and when the quantity difference does not conform to the pattern, it is transferred to manual review.

[0158] like Figure 9 As shown, in one embodiment, step S505, detecting whether the review object belongs to the current carrier, specifically includes: Step S1001: The second terminal obtains the number of second identifiers corresponding to the current carrier and the number of first identifiers corresponding to the selected target carrier.

[0159] In this step, the second identifier quantity is the number of RFID tags in the second RFID tag set corresponding to the current carrier. The first identifier quantity is the number of RFID tags in the first RFID tag set corresponding to the selected target carrier. For example, if the current carrier is read at the second reading station, and the second RFID tag set is {T1,T2,...,T100}, then the second identifier quantity is 100. If the first RFID tag set corresponding to the selected target carrier at the first reading station is {T1,T2,...,T99}, then the first identifier quantity is 99.

[0160] In one possible implementation, the number of first identifiers can be sent to the second terminal along with the first carrier-level fingerprint, or it can be obtained by the second terminal based on the first comparison data sent by the server. The number of second identifiers can be obtained by the second terminal after deduplicating the second RFID identifier set. This step provides a quantitative basis for subsequent determination of whether the object to be verified belongs to the current carrier or the selected target carrier.

[0161] In step S1002, if the number of the second identifiers is greater than the number of the first identifiers, the second terminal determines that the object to be reviewed belongs to the current carrier.

[0162] In this step, if the number of second identifiers is greater than the number of first identifiers, it means that the current carrier has read more RFID tags at the second reading station than the selected target carrier has recorded more RFID tags at the first reading station. In single-item differential positioning scenarios, this quantitative relationship usually indicates that the target differential identifier exists in the second RFID tag set but not in the first RFID tag set.

[0163] For example, the first RFID tag set is {T1,T2,...,T99}, and the second RFID tag set is {T1,T2,...,T99,T100}. In this case, the number of first tags is 99, the number of second tags is 100, and the target difference tag is T100. Since the number of second tags is greater than the number of first tags, it can be determined that the verification object corresponding to T100 belongs to the current carrier. In this situation, the verification result can be used to indicate that a missed read anomaly has occurred on the selected target carrier. The server can find the corresponding first RFID tag set based on the first carrier-level fingerprint corresponding to the selected target carrier and add the target difference tag to that first RFID tag set, or add a corrected mark to that first RFID tag set.

[0164] In this embodiment, it is not necessary to match the target difference identifier with the second RFID identifier set item by item again. The belonging of the object to be checked can be determined based on the relationship between the number of the first identifier and the number of the second identifier, thereby reducing the judgment steps and improving the efficiency of single-item difference correction.

[0165] In step S1003, if the number of the second identifiers is less than the number of the first identifiers, the second terminal determines that the object to be reviewed does not belong to the current carrier.

[0166] In this step, if the number of second identifiers is less than the number of first identifiers, it means that the number of RFID tags read by the current carrier at the second reading station is less than the number of RFID tags recorded by the selected target carrier at the first reading station. In a single-item differential positioning scenario, this quantitative relationship usually indicates that the target differential identifier exists in the first RFID tag set but not in the second RFID tag set.

[0167] For example, the first RFID tag set is {T1,T2,...,T100}, and the second RFID tag set is {T1,T2,...,T99}. In this case, the first tag set contains 100 tags, the second tag set contains 99 tags, and the target difference tag is T100. Since the number of second tags is less than the number of first tags, it can be determined that the verification object corresponding to T100 does not belong to the current carrier, or in other words, the current carrier lacks this verification object relative to the selected target carrier. In this situation, the verification result can be used to indicate that the current carrier has experienced a missed read anomaly. The server can correct the second RFID tag set, the first RFID tag set, or the corresponding transfer status according to business rules. For example, if it is confirmed that the current carrier does not actually contain the medical fabric corresponding to T100, the server can delete T100 from the first RFID tag set corresponding to the selected target carrier, or mark T100 as lost during transport, pending verification, or in an abnormal handover status.

[0168] It should be noted that when the number of the second identifier is equal to the number of the first identifier, the current carrier is marked as awaiting manual review.

[0169] In this embodiment, by using the relationship between the number of first identifiers and the number of second identifiers, it is possible to quickly determine whether the medical fabric corresponding to the target difference identifier should belong to the current carrier, thereby providing a basis for the server to determine the set of RFID identifiers to be corrected.

[0170] Note that in steps S801 to S805, the second terminal needs to perform Nth-round member matching between the third RFID tag set and each of the Nth-round candidate first RFID tag sets according to the comparison order. If a match is found, the target first RFID tag set is determined; if no match is found, N=N+1 and the process returns to redetermine the Nth-round candidate first RFID tag set. Therefore, the third RFID tag set not only participates in set difference comparison but also directly participates in determining the absolute value of the quantity difference, candidate set screening, and Nth-round member matching. However, when the verification station performs RFID reading on the current carrier to be verified, occasional missed reads, occasional cross-reads, tag posture changes, or tag aging may still occur. For example, some RFID tags in the current carrier to be verified may not be read in a single reading due to stacked medical fabrics, dampness, curling, or obstruction; RFID tags in other carriers to be verified near the verification station may also be read occasionally by the RFID reader. If the results of a single verification reading are directly used as the third RFID tag set, the third RFID tag set may be mixed with unstable RFID tags, which will affect the absolute value of the quantity difference, the selection of candidate first RFID tag sets, and the Nth round of member matching.

[0171] Based on this, in one optional approach, the third RFID tag set is obtained through steps S1101 to S1105. Given the potential for occasional fluctuations in the RFID reading results at the verification station, the third RFID tag set participating in the quantity difference calculation and the Nth round of member matching in steps S801 to S805 is composed of stable and reliable RFID tags, thereby reducing the impact of occasional missed reads or cross-reads on the determination result of the target first RFID tag set. The third RFID tag set is obtained through steps S1101 to S1105 and can be applied in steps S801 to S805. Specifically, after determining the current carrier to be verified from the set of carriers to be verified, the second terminal can perform multiple reads on the current carrier using the RFID reader at the verification station, and determine stable RFID tags based on the multiple read results. The set of stable RFID tags is then determined as the third RFID tag set.

[0172] Specifically, in this embodiment, the third RFID tag set is obtained through the following steps S1101 to S1105: Step S1101: The second terminal performs multiple RFID reads on the current carrier to be verified to obtain multiple verification read sets.

[0173] In this step, the current carrier to be verified refers to the carrier at the verification station that currently needs centralized processing. This carrier can be a bag, basket, box, trolley, or other carrier unit used to carry medical textiles. Multiple RFID reads refer to the second terminal controlling the RFID reader at the verification station to perform at least two consecutive or intermittent RFID reads on the same current carrier to be verified. After each RFID read, the second terminal can deduplicate the RFID tags obtained from that read and combine the deduplicated RFID tags into a verification read set. The purpose of deduplication is to avoid the same RFID tag being read repeatedly in one reading process, thus affecting the subsequent occurrence count. For example, if the current carrier to be verified is BAG_015, the second terminal controls the RFID reader to read BAG_015 three times consecutively. After the first reading and deduplication, a set of verification readings is obtained: R1 = {T1, T2, T3, T4, T5, X}; after the second reading and deduplication, a set of verification readings is obtained: R2 = {T1, T2, T3, T4, T5}; after the third reading and deduplication, a set of verification readings is obtained: R3 = {T1, T2, T3, T4, T5, Y}. R1, R2, and R3 are multiple sets of verification readings.

[0174] Through this step, the second terminal obtains the RFID reading results of the same carrier to be verified at different reading times. Since medical fabrics may be stacked, obscured, curled, or have changes in tag posture within the carrier, relying solely on a single reading result may not accurately reflect the stable RFID tags present in the carrier to be verified; through multiple readings, a data foundation can be provided for subsequent screening of stable RFID tags.

[0175] Step S1102: The second terminal determines the number of times each RFID tag appears in the multiple verification and reading sets based on the multiple verification and reading sets.

[0176] In this step, the occurrence count of a given RFID tag refers to the number of times that RFID tag appears in multiple verification read sets. Since each verification read set has undergone single-read deduplication, the occurrence count indicates the number of times the RFID tag is read at multiple read times, rather than the number of repeated reads within the same read. For example, in the examples R1={T1,T2,T3,T4,T5,X}, R2={T1,T2,T3,T4,T5}, and R3={T1,T2,T3,T4,T5,Y}, T1, T2, T3, T4, and T5 all appear in R1, R2, and R3, so their occurrence count is 3; X only appears in R1, so its occurrence count is 1; and Y only appears in R3, so its occurrence count is 1.

[0177] Through this step, the second terminal can convert RFID tags from multiple verification and reading sets into data with occurrence stability. RFID tags with a higher occurrence frequency are generally more likely to truly belong to the current carrier to be verified; RFID tags with a lower occurrence frequency may be the result of occasional cross-reading, occasional identification, temporary removal of obstruction, or interference from the verification workstation environment.

[0178] In step S1103, the second terminal determines a stable RFID tag from among the RFID tags based on the number of occurrences.

[0179] In this step, a stable RFID tag refers to an RFID tag whose occurrence frequency meets a stable condition. This stable condition can be determined based on the total number of verified reads. For example, if the total number of verified reads is K, the stable condition can be that the occurrence frequency is greater than or equal to a preset threshold. The preset threshold can be K, or it can be a positive integer greater than half of K. For instance, when the total number of verified reads is 3, the stable condition can be that the occurrence frequency is greater than or equal to 2, or it can be that the occurrence frequency equals 3. If the stable condition is that the occurrence frequency is greater than or equal to 2, then in the above example, T1, T2, T3, T4, and T5 are determined to be stable RFID tags, while X and Y are not. If the stable condition is that the occurrence frequency equals 3, then T1, T2, T3, T4, and T5 are still determined to be stable RFID tags, while X and Y are still not determined to be stable RFID tags.

[0180] In one possible implementation, the second terminal can also mark RFID tags that have not been determined to be stable RFID tags as unstable RFID tags. Unstable RFID tags can include aging tags, structurally damaged tags, suspected cross-read tags, suspected sporadic read tags, or tags indicating interference from the verification environment. It should be noted that unstable RFID tags can be recorded as verification auxiliary information but do not participate in the generation of the third RFID tag set.

[0181] This step allows the second terminal to perform stability screening on RFID tags from multiple verification and reading sets before generating the third RFID tag set. Compared to directly using the results of a single verification and reading, this step reduces the probability of occasional cross-reading tags or occasional reading tags entering the third RFID tag set.

[0182] Step S1104: The second terminal generates the third RFID tag set based on the stable RFID tag. The third RFID tag set is composed of the stable RFID tags, and is used to determine the absolute value of the quantity difference with each of the first RFID tag sets, and to perform Nth round member matching with each of the Nth round candidate first RFID tag sets.

[0183] In this step, the second terminal forms a set of stable RFID tags determined in step S1203, and defines this set as the third RFID tag set corresponding to the current carrier to be verified. That is, the third RFID tag set consists of stable RFID tags and does not include RFID tags that do not meet the stability condition. For example, in the above example, if the stable RFID tags are T1, T2, T3, T4, and T5, then the third RFID tag set generated by the second terminal is {T1, T2, T3, T4, T5}. RFID tags X and Y are not included in the third RFID tag set because they do not meet the stability condition.

[0184] This step ensures that the third RFID tag set used in steps S801 to S805 is no longer the original set obtained from a single verification read, but a stable set obtained through multiple verification reads and screenings. Therefore, each RFID tag in the third RFID tag set has higher read reliability, reducing the probability of interference from occasional RFID tags in subsequent calculations of the absolute value of the quantity difference and the Nth round of member matching.

[0185] In step S1105, the second terminal determines the number of stable RFID tags as the number of third tags.

[0186] In this step, the third identifier quantity refers to the number of RFID tags in the third RFID tag set. Since the third RFID tag set consists of stable RFID tags, the third identifier quantity is the same as the number of stable RFID tags. For example, if the third RFID tag set is {T1,T2,T3,T4,T5}, then the third identifier quantity is 5. Although X and Y may have appeared in multiple verification and reading sets, X and Y were not identified as stable RFID tags and therefore are not included in the third identifier quantity.

[0187] Through this step, the number of third identifiers used in steps S801 to S805 to calculate the absolute value of the quantity difference with the number of first identifiers corresponding to each first RFID tag set is also derived from the stable number of RFID tags. Therefore, the absolute value of the quantity difference can more accurately reflect the difference between the number of RFID tags stably read in the current carrier to be verified and the number of each first RFID tag set, avoiding the false increase in the number of third identifiers caused by occasional cross-reading, and also avoiding the direct formation of unstable quantity statistics due to occasional missed reads.

[0188] This embodiment retains the original N-round progressive mechanism from steps S801 to S805, while basing the N-round progression on the member matching results of a stable RFID tag set. This reduces the exclusion of erroneous candidates due to unstable RFID tags, improving the accuracy and reliability of centralized processing at the review station.

[0189] It should be noted that inconsistencies in the RFID tag sets among the first reading station, the second reading station, and the verification station are not necessarily due to missing or mixed-in items; they may also stem from the unique tag reading stability issues specific to medical textile scenarios. The temperature RFID tags and unstable RFID tags obtained in steps S1101 to S1105 are two types of RFID tags. Stable RFID tags can be used to generate the third RFID tag set, while unstable RFID tags can further provide verification and replacement warnings for aging tags or tags with internal structural damage.

[0190] In one embodiment, in steps S1101 to S1105, the second terminal has performed multiple RFID reads on the current carrier to be verified, obtaining multiple verification read sets, and determining stable RFID tags based on the frequency of each RFID tag appearing in the multiple verification read sets. The second terminal generates a third RFID tag set based on the stable RFID tags, and determines the number of stable RFID tags as the third tag quantity. This third RFID tag set can be further used for the absolute value calculation of the quantity difference in steps S801 to S805, the determination of the Nth round of candidate first RFID tag set, and the Nth round of member matching.

[0191] Furthermore, after generating the third RFID tag set based on the stable RFID tags and determining the target first RFID tag set corresponding to the carrier to be verified to which the current unstable RFID tag belongs, the second terminal can also perform tag quality anomaly identification on the unstable RFID tag corresponding to the carrier to be verified. The target first RFID tag set refers to the first RFID tag set corresponding to the carrier to be verified, determined based on steps S801 to S805. Since the correspondence between the carrier to be verified and the target first RFID tag set has been determined at this time, the second terminal can further determine whether the unstable RFID tags excluded from the third RFID tag set may correspond to aging, structurally damaged, or sensitivity-degraded RFID tags without affecting the participation of the third RFID tag set in matching.

[0192] It should be noted that the RFID tags on medical fabrics can be passive RFID tags. Passive RFID tags typically rely on radio frequency signals emitted by an RFID reader to obtain energy and return a response signal through the tag antenna after the tag chip is activated. If the RFID tag is subjected to high-temperature washing, disinfection, drying, folding, squeezing, or friction with the medical fabric for a long time, it may cause micro-cracks in the tag antenna, loosening of the connection point between the antenna and the chip, aging of the tag packaging, water ingress, or bending deformation, thereby reducing the tag's energy receiving capability, making the chip activation unstable, or weakening the returned response signal. In this case, the RFID tag may not be completely unreadable, but may only be read a portion of the times in multiple RFID reads of the same verification station and the same carrier to be verified. For example, if a certain RFID tag T6 appears only twice in 5 RFID reads of its carrier to be verified, it does not meet the stability condition in step S1103 and is therefore not included in the third RFID tag set. However, if RFID tag T6 does not appear in either the first or second RFID tag set corresponding to other target carriers in the current circulation task, and the overall reading of the target carrier is stable, then RFID tag T6 is more likely due to intermittent reading caused by the aging, structural damage, or decreased sensitivity of its corresponding RFID tag, rather than by cross-reading of other target carriers.

[0193] Based on this, after obtaining the third RFID tag set according to steps S1101 to S1105 and determining the target first RFID tag set corresponding to the carrier to be verified to which the current unstable RFID tag belongs, the method further includes: Step S1201: The second terminal acquires multiple unstable RFID tags that have not been identified as stable RFID tags.

[0194] In this step, an unstable RFID tag refers to an RFID tag whose occurrence count in multiple verification read sets of its respective carrier does not meet the stability condition. This stability condition is consistent with the stability condition in step S1103. For example, if the total number of verification reads is K, the stability condition can be that the occurrence count is greater than or equal to a preset threshold; the preset threshold can be K, or it can be a positive integer greater than half of K. For example, the second terminal performs 5 consecutive RFID reads on the carrier BAG_015 to be verified, obtaining 5 verification read sets. If the stability condition is that the occurrence count is greater than or equal to 4, and RFID tag T6 only appears in 2 of the verification read sets, then RFID tag T6 is not determined to be a stable RFID tag, but is determined to be an unstable RFID tag.

[0195] Through this step, the second terminal can retain RFID tags that have not entered the third RFID tag set. These unstable RFID tags will not participate in the calculation of the number of third tags and the Nth round of member matching in steps S801 to S805, thereby avoiding interference with the determination process of the target first RFID tag set; at the same time, these unstable RFID tags can also serve as the data basis for subsequent tag quality anomaly judgment.

[0196] In step S1202, the second terminal selects the current unstable RFID tag from the plurality of unstable RFID tags and determines the carrier to be verified to which the current unstable RFID tag belongs.

[0197] In this step, multiple unstable RFID tags can originate from the same carrier to be verified, or they can originate from multiple carriers in a set of carriers to be verified. The second terminal can select the current unstable RFID tag one by one from the multiple unstable RFID tags in a preset order, and determine the carrier to which the current unstable RFID tag belongs based on the multiple verification read sets corresponding to the generation of the unstable RFID tag. For example, if RFID tag T6 is identified as an unstable RFID tag after 5 RFID reads of carrier BAG_015, then the second terminal can determine that the carrier to which RFID tag T6 belongs is BAG_015. As another example, if RFID tag 2000 is identified as an unstable RFID tag after multiple RFID reads of carrier BAG_016, then the second terminal can determine that the carrier to which RFID tag 2000 belongs is BAG_016.

[0198] Through this step, the second terminal can establish a correspondence between "currently unstable RFID tag - its corresponding carrier to be reviewed". When subsequently determining whether the currently unstable RFID tag is a suspected quality anomaly RFID tag, the judgment can be based on the review and reading results of its corresponding carrier, the overall reading stability, and the RFID tag set of other target carriers in the current transfer task.

[0199] Step S1203: After determining the target first RFID tag set corresponding to the carrier to be verified to which the current unstable RFID tag belongs, the second terminal obtains at least one of the first RFID tag set or the second RFID tag set corresponding to other target carriers in the current transfer task, excluding the carrier to be verified to which the current unstable RFID tag belongs.

[0200] In this step, the target first RFID tag set corresponding to the carrier to be verified to which the current unstable RFID tag belongs refers to the target first RFID tag set determined in steps S801 to S805 by performing Nth round member matching between the third RFID tag set corresponding to the carrier to be verified and each Nth round candidate first RFID tag set. Other target carriers refer to target carriers in the current workflow task other than the carrier to be verified to which the current unstable RFID tag belongs. The first RFID tag set corresponding to other target carriers can be the first RFID tag set obtained by the first reading station for the other target carrier and uploaded to the server. The second RFID tag set corresponding to other target carriers can be the second RFID tag set obtained by the second reading station for the other target carrier.

[0201] For example, the current transfer task includes target carriers BAG_015, BAG_016, and BAG_017. If the carrier to be verified to which the current unstable RFID tag T6 belongs is BAG_015, then BAG_016 and BAG_017 can be used as other target carriers. The second terminal can obtain at least one of the first RFID tag set or the second RFID tag set corresponding to BAG_016 and BAG_017 to determine whether RFID tag T6 appears in other target carriers.

[0202] Through this step, the second terminal can use the RFID tag set of other target carriers in the current transfer task to determine whether the currently unstable RFID tag may originate from other target carriers. This step is used to rule out the possibility of cross-reading from other target carriers before generating a tag quality anomaly alert.

[0203] Step S1204: The second terminal determines whether the current unstable RFID tag appears in the other target carrier based on at least one of the first RFID tag set or the second RFID tag set corresponding to the other target carrier.

[0204] In this step, the second terminal can query whether the currently unstable RFID tag exists in the first or second RFID tag set corresponding to other target carriers. If the currently unstable RFID tag exists in the first or second RFID tag set corresponding to other target carriers, it indicates that the currently unstable RFID tag may be associated with other target carriers and should not be directly identified as a suspected quality abnormality RFID tag. If the currently unstable RFID tag does not appear in the first or second RFID tag set corresponding to other target carriers, the possibility of it originating from cross-reading from other target carriers can be reduced. For example, RFID tag T6 appears only twice in 5 RFID reads of BAG_015, belonging to an unstable RFID tag. The second terminal queries the first or second RFID tag sets corresponding to BAG_016 and BAG_017 and does not find RFID tag T6, so the second terminal can determine that RFID tag T6 does not appear in other target carriers.

[0205] This step helps the second terminal avoid misidentifying RFID tags from other target carriers as aging or structurally damaged RFID tags from the current carrier being reviewed. Suspected quality anomaly assessment only continues if the currently unstable RFID tag does not appear in the first or second RFID tag set corresponding to other target carriers.

[0206] In step S1205, the second terminal determines whether the carrier to which the currently unstable RFID tag belongs meets the overall reading stability condition based on multiple verification and reading sets of the carrier to which the currently unstable RFID tag belongs. The overall reading stability condition includes: determining the number of stable RFID tags and the total number of RFID tags participating in the statistics based on multiple verification and reading sets of the carrier to which the currently unstable RFID tag belongs; and determining that the carrier to which the currently unstable RFID tag belongs meets the overall reading stability condition if the ratio between the number of stable RFID tags and the total number of RFID tags participating in the statistics is greater than or equal to a preset overall stability threshold.

[0207] In this step, the overall reading stability condition is used to characterize whether the overall reading environment of the carrier to which the currently unstable RFID tag belongs is stable during multiple RFID reading processes. The second terminal can determine the number of stable RFID tags and the total number of RFID tags participating in the statistics based on multiple verification reading sets of the carrier to be verified, and determine whether the overall reading stability condition is met based on the ratio between the two.

[0208] Specifically, the total number of RFID tags included in the statistics can be the number of RFID tags in the union of multiple verification and reading sets of the carrier to be verified. The number of stable RFID tags can be the number of stable RFID tags determined in step S1103 based on the multiple verification and reading sets of the carrier to be verified. If the ratio between the number of stable RFID tags and the total number of RFID tags included in the statistics is greater than or equal to a preset overall stability threshold, then the carrier to be verified is determined to meet the overall reading stability condition. For example, the union of the 5 verification and reading sets of the carrier BAG_015 includes 100 RFID tags, of which 96 RFID tags meet the stability condition and 4 RFID tags do not. If the preset overall stability threshold is 90%, then the ratio between the number of stable RFID tags and the total number of RFID tags included in the statistics is 96%, which is greater than the preset overall stability threshold. Therefore, the second terminal determines that BAG_015 meets the overall reading stability condition.

[0209] Through this step, the second terminal can determine whether the overall reading environment of the carrier to which the currently unstable RFID tag belongs is reliable during this verification process. If the overall reading is unstable, the low-frequency occurrence of the currently unstable RFID tag may be caused by carrier placement, fabric obstruction, insufficient reader power, or interference from the verification station environment, and it is not advisable to directly generate verification and replacement reminders. If the overall reading is stable, but the currently unstable RFID tag still occurs at a low frequency, the currently unstable RFID tag is more likely related to the aging, structural damage, or decreased sensitivity of the corresponding RFID tag itself.

[0210] Step S1206: If the current unstable RFID tag does not appear in the first RFID tag set or the second RFID tag set corresponding to the other target carrier, and the carrier to be verified to which the current unstable RFID tag belongs meets the overall reading stability condition, the second terminal determines the current unstable RFID tag as a suspected quality abnormality RFID tag.

[0211] In this step, suspected quality anomaly RFID tags can be suspected aging RFID tags, suspected damaged tag structures RFID tags, suspected decreased tag sensitivity RFID tags, or suspected intermittent reading RFID tags. For example, RFID tag T6 meets the following conditions: First, RFID tag T6 is an unstable RFID tag corresponding to BAG_015; second, RFID tag T6 does not appear in the first or second RFID tag set corresponding to other target carriers BAG_016 and BAG_017 in the current circulation task; third, BAG_015 meets the overall reading stability condition. At this time, the second terminal can identify RFID tag T6 as a suspected quality anomaly RFID tag.

[0212] It should be noted that this step does not determine a suspected quality anomaly RFID tag solely based on the low frequency of RFID tag T6 occurrences. Instead, it combines the exclusion criteria from other target carriers and the overall stability of readability. This approach reduces the probability of misjudging tag quality anomalies by cross-reading tags from other target carriers or by overall readability instability at the verification station.

[0213] In step S1207, the second terminal generates a verification and replacement reminder based on the suspected quality anomaly RFID tag.

[0214] In this step, the verification and replacement reminder is used to prompt manual verification or RFID tag replacement for medical fabrics corresponding to suspected quality abnormality RFID tags. The verification and replacement reminder may include at least one of the following: suspected quality abnormality RFID tag, the carrier to which the currently unstable RFID tag belongs, the target first RFID tag set, the number of occurrences, the total number of verification reads, whether it appears in other target carriers, overall reading stability, the cause of the suspected abnormality, and suggested handling methods. For example, the second terminal may generate the following verification and replacement reminder: "RFID tag T6 is an unstable RFID tag corresponding to carrier BAG_015 to be verified, appearing only 2 times in 5 verification reads; this RFID tag does not appear in the first or second RFID tag set corresponding to other target carriers in the current workflow task, and BAG_015 has stable overall reading; it is recommended to manually verify the corresponding medical fabric and check or replace the RFID tag."

[0215] The second terminal can send verification and replacement reminders to the server. Upon receiving the reminder, the server can mark the medical fabric corresponding to the suspected quality anomaly RFID tag as pending manual verification, suspected tag aging, suspected tag quality anomaly, or tag to be replaced. Subsequent staff can then use this reminder to check or replace the corresponding medical fabric tags during the sorting, washing, warehousing, outbound, or manual verification stages.

[0216] Through this step, unstable RFID tags are no longer merely excluded from the third RFID tag set as abnormal data, but are further used to identify RFID tags that may cause repeated anomalies in subsequent transfer tasks. Therefore, tag verification and replacement reminders can be generated in advance without affecting the matching process from steps S801 to S805, improving the long-term stability of the medical textile handover system.

[0217] In one alternative approach, step S1208 is further included, whereby the second terminal or server adjusts the alert level of the verification and replacement alert based on the historical reading stability information corresponding to the suspected quality anomaly RFID tag.

[0218] In this step, historical stable reading information can include at least one of the following: historical instability frequency, historical occurrence rate, the time when it was most recently identified as an unstable RFID tag, number of washes, usage duration, and tag replacement records. For example, if RFID tag T6 is identified as a suspected quality anomaly RFID tag in this circulation task, and the server further queries and finds that this RFID tag has been identified as an unstable RFID tag twice in the last three circulation tasks, or that the number of washes of its corresponding medical fabric has exceeded a preset washing threshold, then the server can adjust the alert level of the verification and replacement reminder from a normal verification reminder to a priority replacement reminder. Through this step, the system can further distinguish between occasional quality anomaly reminders and persistent quality anomaly reminders. For RFID tags that have repeatedly shown unstable reading in the past, the system can increase the replacement priority, thereby reducing the probability that the same quality anomaly tag will repeatedly trigger identification anomalies and review processes in subsequent medical fabric circulation tasks.

[0219] On the other hand, in one embodiment, an intelligent correction system for abnormal identification during the handover of medical fabrics is provided. The system includes a memory, a processor, and a computer program stored in the memory. When the processor executes the computer program, it implements the steps of the above method performed by a first terminal, a second terminal, or a server.

[0220] Those skilled in the art will understand that all or part of the processes in the above embodiments can be implemented by a computer program instructing related hardware. The program can be stored in a non-volatile computer-readable storage medium, and when executed, it can include the processes of the embodiments described above. Any references to memory, storage, databases, or other media used in the embodiments provided in this application can include non-volatile and / or volatile memory. Non-volatile memory can include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory. Volatile memory can include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in various forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), dual data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRA), direct RAM via Rambus (RDRA), direct memory bus dynamic RAM (DRDRAM), and dynamic RAM via Rambus (RDRAM), etc.

Claims

1. An intelligent correction method for anomaly identification during the handover process of medical fabrics, characterized in that, The method includes: The first terminal performs RFID reading on the target carrier carrying medical fabric at the first reading station, obtains the first RFID tag set corresponding to the target carrier, and sends the first RFID tag set to the server so that the server associates and stores the first RFID tag set with the transfer task record. The second terminal obtains the flow task identifier corresponding to the current flow task and sends a comparison data request carrying the flow task identifier to the server. The second terminal receives the first comparison data sent by the server in response to the comparison data request; wherein, the first comparison data is generated based on the first RFID tag set corresponding to multiple target carriers under the current circulation task, and the first comparison data is used to perform non-full representation of the first RFID tag set corresponding to the multiple target carriers; The second terminal performs RFID reading on the current carrier that has been transferred to the second reading station, obtains the second RFID tag set corresponding to the current carrier, and sends the second RFID tag set to the server so that the server associates and stores the second RFID tag set with the transfer task record. The second terminal performs a partial comparison between the second RFID tag set and the first comparison data to determine whether the current carrier has any identification anomalies. If the second terminal determines that there is an identification anomaly in the current carrier, it triggers a review process for the current carrier. Based on the review results of the review process, the server determines the set of RFID tags to be corrected from the first RFID tag set and the second RFID tag set associated with the workflow task, and corrects the set of RFID tags to be corrected.

2. The method according to claim 1, characterized in that, The first comparison data includes a local fingerprint database corresponding to the current transfer task. The local fingerprint database includes multiple first carrier-level fingerprints, which are generated based on a set of first RFID tags corresponding to multiple target carriers under the current transfer task. The first carrier-level fingerprint includes a first structural fingerprint and a first number of tags. The second terminal performs a partial comparison between the second RFID tag set and the first comparison data to determine whether the current carrier has any identification anomalies, including: A second carrier-level fingerprint is generated based on the second RFID tag set corresponding to the current carrier; wherein, the second carrier-level fingerprint includes a second structural fingerprint and a second tag quantity; The second structural fingerprint in the second carrier-level fingerprint is XORed with the first structural fingerprint in each first carrier-level fingerprint in the local fingerprint database to obtain multiple candidate difference identifiers; wherein, each candidate difference identifier corresponds to a first carrier-level fingerprint; If there is a candidate difference identifier with a value of zero, it is determined that the current carrier does not have an identification anomaly, and the first carrier-level fingerprint corresponding to the candidate difference identifier with a value of zero is deleted from the local fingerprint database. If all of the candidate difference identifiers are not zero, it is determined that the current carrier has an identification anomaly.

3. The method according to claim 2, characterized in that, The first carrier-level fingerprint and the second carrier-level fingerprint are generated in the following manner: The RFID tag set corresponding to the carrier is deduplicated to obtain the deduplicated RFID tag set; Each RFID tag in the deduplicated RFID tag set is converted into a fixed-length normalized binary tag; Perform an XOR operation on the obtained multiple normalized binary identifiers to obtain the structural fingerprint corresponding to the carrier; The carrier-level fingerprint is generated based on the structural fingerprint and the number of identifiers in the deduplicated RFID tag set; wherein the structural fingerprint is independent of the order of the RFID tags in the deduplicated RFID tag set.

4. The method according to claim 3, characterized in that, If all of the candidate difference identifiers are not zero, the triggering of the review process for the current carrier includes: The multiple candidate difference identifiers are filtered based on preset filtering conditions; wherein, the preset filtering conditions include RFID identifier encoding rules; If a candidate difference identifier that uniquely satisfies the preset screening conditions is obtained through screening, the candidate difference identifier that uniquely satisfies the preset screening conditions is determined as the target difference identifier. The medical fabric corresponding to the target difference identifier is identified as the review object in the review process; The first carrier-level fingerprint to which the first structural fingerprint involved in generating the target difference identifier belongs is determined as the target first carrier-level fingerprint, and the target carrier corresponding to the target first carrier-level fingerprint is selected as the target carrier. The system checks whether the object being reviewed belongs to the current carrier. If it does, the output review result indicates that the selected target carrier has experienced a missed read anomaly; otherwise, the output review result indicates that the current carrier has experienced a missed read anomaly. The first carrier-level fingerprint corresponding to the target difference identifier is deleted from the local fingerprint database.

5. The method according to claim 4, characterized in that, The method further includes: If no candidate difference identifiers that meet the preset screening conditions are obtained through screening, the current carrier is controlled to enter the verification station, and the next carrier is allowed to enter the second reading station. If the number of carriers leaving the second reading station in the workflow task reaches the number of carriers corresponding to the workflow task, the centralized processing flow of the verification station is triggered, and the centralized processing flow includes: Based on the remaining first carrier-level fingerprints in the local fingerprint database, request the server for the first RFID tag set corresponding to the remaining first carrier-level fingerprints; Obtain the set of carriers to be reviewed in the review station; If the set of carriers to be reviewed is not empty, the following review process is performed repeatedly until the set of carriers to be reviewed is empty: Determine the current carrier to be reviewed from the set of carriers to be reviewed; Obtain the third RFID tag set and the number of third tags corresponding to the current carrier to be reviewed; The comparison order between the third RFID tag set and each of the first RFID tag sets is determined based on the difference between the third tag quantity and the first tag quantity corresponding to each of the first RFID tag sets; wherein, the larger the absolute value of the difference between the third tag quantity and the corresponding first tag quantity, the higher the comparison priority of the first RFID tag set corresponding to that first tag quantity. According to the comparison order, the third RFID tag set is compared with each of the first RFID tag sets to determine the target first RFID tag set and the difference RFID tag set corresponding to the current carrier to be reviewed; A correction request is generated based on the set of differential RFID tags; Remove the current carrier to be reviewed from the set of carriers to be reviewed.

6. The method according to claim 4, characterized in that, When multiple candidate difference identifiers that meet the preset filtering conditions are obtained through screening, the method further includes: The system detects whether a target candidate difference identifier exists among the plurality of candidate difference identifiers that meet the preset screening conditions; wherein, the first carrier-level fingerprint corresponding to the target candidate difference identifier and the second carrier-level fingerprint satisfy a single-item difference condition; the single-item difference condition includes: the absolute value of the difference between the number of first identifiers of the first carrier-level fingerprint corresponding to the target candidate difference identifier and the number of second identifiers of the second carrier-level fingerprint is 1. When at least two target candidate difference identifiers are detected, it is determined that there is a suspected duplicate reading anomaly at the first reading station; Send a duplicate identification correction request to the server. The duplicate identification correction request is used to instruct the server to merge, delete, mark or verify the first RFID tag set corresponding to the first carrier-level fingerprint corresponding to the at least two target candidate difference identifiers.

7. The method according to claim 5, characterized in that, The step of performing a set difference comparison between the third RFID tag set and each of the first RFID tag sets according to the comparison order to determine the target first RFID tag set and the difference RFID tag set corresponding to the current carrier to be reviewed includes: Determine the absolute value of the quantity difference corresponding to each of the first RFID tag sets, and let N=1; wherein, the absolute value of the quantity difference is the absolute value of the difference between the third tag quantity of the third RFID tag set and the first tag quantity of the corresponding first RFID tag set, and N is a positive integer variable; The Nth round of candidate first RFID tag sets are determined from each of the first RFID tag sets; wherein the absolute value of the difference in the number of the Nth round of candidate first RFID tag sets is greater than or equal to N-1; According to the comparison order, the third RFID tag set is matched with each of the Nth round candidate first RFID tag sets in the Nth round; If the third RFID tag set matches any candidate first RFID tag set in the Nth round of member matching, the matched candidate first RFID tag set in the Nth round is determined as the target first RFID tag set corresponding to the current carrier to be reviewed, and the third RFID tag set and the target first RFID tag set are compared to obtain the difference RFID tag set. If neither the third RFID tag set nor each of the Nth round candidate first RFID tag sets matches in the Nth round member matching, let N = N + 1, and return to the step of determining the Nth round candidate first RFID tag set from each of the first RFID tag sets, until the target first RFID tag set is determined or the stopping condition is met.

8. The method according to claim 7, characterized in that, The method further includes: Determine the maximum value M among the absolute values ​​of the quantity differences corresponding to each of the first RFID tag sets; If the current comparison round N is greater than M and the target first RFID tag set has not yet been determined, the current carrier to be reviewed is marked as awaiting manual review, and the set difference comparison is stopped.

9. The method according to claim 4, characterized in that, The step of detecting whether the object to be reviewed belongs to the current carrier specifically includes: Obtain the number of second identifiers corresponding to the current carrier and the number of first identifiers corresponding to the selected target carrier; If the number of the second identifiers is greater than the number of the first identifiers, it is determined that the object to be reviewed belongs to the current carrier; If the number of the second identifiers is less than the number of the first identifiers, it is determined that the object to be reviewed does not belong to the current carrier.

10. An intelligent correction system for anomaly identification during the handover process of medical fabrics, the system comprising a memory, a processor, and a computer program stored in the memory, characterized in that, When the processor executes the computer program, it implements the steps of the method described in any one of claims 1 to 9 that are performed by the first terminal, the second terminal, or the server.

Images