An intelligent management system of marine product supply chain based on RFID

Abstract

The present application relates to the technical field of supply chain management, and more particularly to a marine product supply chain RFID intelligent management system, comprising an RFID tag group bound to a supply chain unit, an identification terminal arranged at each node, a writing terminal and a central processing server. The tag group is composed of a master RFID and a plurality of slave RFIDs, the master RFID records master index data such as identity identification, flow state, slave mapping information and update strategy identification; the slave RFID records subdivided business data such as source batch, processing, temperature control monitoring and logistics handover. The central processing server is in communication connection with the identification terminal and the writing terminal, selects a data processing mode of quick release, directional completion, association reconstruction or abnormal correction based on the identification data, generates master-slave update instructions, and realizes hierarchical identification, selective update and abnormal recoverable management under multiple nodes.

Description

Technical Field

[0001] This invention relates to the field of supply chain management technology, and in particular to an RFID intelligent management system for seafood supply chain. Background Technology

[0002] The seafood supply chain typically includes multiple stages such as harvesting or aquaculture, temporary holding, sorting, processing, weighing, packing, cold chain transportation, warehousing, handover, and sales traceability. Due to the frequent batch changes, varied packaging formats, high temperature control requirements, and numerous handover points during the seafood distribution process, actual operations often require the use of RFID tags to record various data, including product identity, origin batch, processing information, logistics handover information, and temperature control information, to achieve identification and traceability throughout the entire seafood supply chain.

[0003] In existing technologies, a common approach is to centrally write data related to a supply chain unit into a single RFID tag, or to employ a similar writing and identification strategy for multiple RFID tags. In these solutions, the identification terminal typically needs to read a significant amount of data at each node, or perform relatively complete polling and identification of multiple tags to confirm whether the current status of the supply chain unit has changed. For the seafood supply chain, due to the large number of nodes and the fast processing pace of some nodes, using a heavy-duty full-data identification, full-data comparison, and full-data update method at most nodes can easily increase the processing burden on the identification processing end, prolong the operation time of a single node, and increase the number of times tags need to be repeatedly written.

[0004] Furthermore, supply chain units within the seafood supply chain are not always fixed. For example, during sorting, unpacking, consolidation, transshipment, and temporary storage and transfer, the same batch of seafood may be split, merged, or have its carrier changed. If the RFID system lacks a clear hierarchical relationship between tags, or if the original tag relationships are used after structural changes, it can easily lead to inconsistencies between the identified object and the actual carrier, lag in the status of other tags after local data updates, and unstable traceability links. Especially in scenarios with multiple tags, the lack of differentiated processing mechanisms for each tag may cause some nodes to need to read and process detailed data that is not actually necessary for current business judgments, further increasing the data processing pressure on the identification terminals.

[0005] Meanwhile, in actual circulation, there may be abnormal situations such as missing label identification, untimely updates of local data, and inconsistencies between the status of the main label and the auxiliary label. If the system does not establish corresponding differentiated processing methods for different identification results, but instead adopts a uniform processing logic, it will either lead to an overly conservative processing process that frequently requires manual review, or it will make it difficult to correct local anomalies in a timely manner, thereby affecting the accurate judgment of the status of supply chain units by subsequent nodes.

[0006] Therefore, in the context of the seafood supply chain, how to combine the characteristics of using multiple RFID tags to perform layered processing of identification data, reduce the processing pressure on the identification processing end while ensuring traceability integrity, and at the same time take into account the dynamic selection, selective updating and anomaly correction of master and slave tags, has become a technical problem that needs to be solved in this field. Summary of the Invention

[0007] Therefore, the present invention provides an RFID intelligent management system for the seafood supply chain to address at least one of the technical problems mentioned in the background art.

[0008] To achieve the above objectives, the present invention provides an RFID intelligent management system for seafood supply chain, comprising several RFID tag groups bound to seafood supply chain units, wherein the RFID tag group includes a master RFID and several slave RFID.

[0009] Several identification terminals set at nodes in the supply chain are used to identify the main RFID and / or the slave RFID and generate corresponding identification data;

[0010] A plurality of write terminals are provided for selectively writing or updating the master RFID and the slave RFID;

[0011] The central processing server is connected to each identification terminal and each writing terminal to determine the corresponding data processing method based on the identification data and generate the corresponding master-slave update instructions.

[0012] The main RFID tag is used to record the main index data of the corresponding supply chain unit. The main index data includes at least the identity identifier, circulation status, subordinate mapping information and update strategy identifier.

[0013] The RFID is used to record segmented business data for the corresponding supply chain unit. The segmented business data includes at least one or more of the following: source batch data, processing data, temperature control monitoring data, and logistics handover data.

[0014] Based on the identification data, the central processing server triggers the corresponding identification process using at least one of the following data processing methods:

[0015] A fast-release processing method is used to complete node passage confirmation based solely on the main RFID;

[0016] The targeted completion processing method is used to complete partial data from the RFID based on the target indicated by the main RFID;

[0017] The associated restructuring processing method is used to rebuild the master-slave relationship when supply chain units are split, merged, or repackaged;

[0018] Anomaly correction processing method is used to write back and update the master RFID and / or slave RFID in case of identification conflicts, missing data or inconsistent status.

[0019] As a preferred technical solution for the RFID intelligent management system for the seafood supply chain, the process by which the central processing server classifies the identification data includes: extracting the node category, identification completeness, state change amount, and historical update frequency corresponding to this identification.

[0020] Based on the node category, determine whether this identification belongs to a passage node, a task node, or a verification node;

[0021] Based on the identification completeness, determine whether this identification meets the minimum judgment condition of only reading the main RFID;

[0022] Determine whether there is new business data or changes to existing business data based on the state change amount.

[0023] Based on the historical update frequency, determine whether the corresponding supply chain unit has reached the master-slave relationship reorganization threshold;

[0024] When the completeness of identification reaches the minimum judgment condition and the amount of state change does not exceed the preset threshold, the central processing server triggers the fast release processing mode.

[0025] When the amount of state change exceeds a preset threshold and only involves a portion of the subdivided business data, the targeted completion processing method is triggered;

[0026] When the historical update frequency reaches the master-slave relationship reorganization threshold or when splitting, merging, or repackaging occurs, the associated reconstruction processing method is triggered.

[0027] As a preferred technical solution for the seafood supply chain RFID intelligent management system, for a single supply chain unit, the selection of the main RFID tag is performed by the main tag determination module, which is used to:

[0028] Identify the data carrying range, binding level, physical attachment stability, and expected circulation cycle of each RFID tag;

[0029] The RFID tag that is bound to a stable carrier, has the longest corresponding circulation cycle, and has the largest number of associated lower-level tags will be set as the candidate master RFID.

[0030] The candidate master RFID tags are sorted according to their identification priority, and the RFID tag with the highest identification priority is set as the master RFID tag.

[0031] The identification priority is related to the average readability of RFID in the supply chain nodes, the probability of repeated disassembly and assembly, and the necessity of business aggregation.

[0032] The slave RFID consists of the remaining RFIDs other than the master RFID, and each corresponds to a different category of segmented business data.

[0033] As a preferred technical solution for the RFID intelligent management system for the seafood supply chain, the process by which the central processing server allocates data from RFID tags includes:

[0034] Based on the frequency of change of segmented business data, data with an update frequency higher than a preset frequency threshold are assigned to the first RFID tag;

[0035] Based on the independence of traceability of segmented business data, data that requires independent traceability is allocated to the second RFID;

[0036] Based on the collaborative relationships of the segmented business data, the data that needs to be identified is assigned to several RFID tags with the same or adjacent numbers;

[0037] Among them, the first priority is to record processing data and logistics handover data from RFID;

[0038] The second method prioritizes recording source batch data and temperature control monitoring data from RFID.

[0039] The master RFID record records the data category index and read pointer corresponding to each slave RFID.

[0040] As a preferred technical solution for the RFID intelligent management system for the seafood supply chain, the rapid release processing method includes:

[0041] The identification terminal only reads the main RFID tag;

[0042] The central processing server determines whether the corresponding supply chain unit meets the release conditions of the current node based on the identity identifier, circulation status and update strategy identifier in the main RFID.

[0043] If the release conditions are met, a release confirmation result is generated;

[0044] If the release conditions are not met, the current identification will be switched to the directional completion processing method or the anomaly correction processing method.

[0045] The master RFID also records a digest check value, which is used to characterize the current consistency status of a number of slave RFIDs.

[0046] As a preferred technical solution for the RFID intelligent management system of the seafood supply chain, the targeted completion processing method includes:

[0047] The central processing server determines the target RFID set that needs to be read again based on the subordinate mapping information and update policy identifier in the master RFID;

[0048] The identification terminal performs supplementary identification on the target from the RFID set and generates partial completion data;

[0049] The central processing server determines whether the node operation has caused a state change based on the partially completed data.

[0050] When a status change occurs, the writing terminal only updates the RFID of the target corresponding to the status change, and synchronously updates the flow status, subordinate mapping version number and digest check value in the master RFID.

[0051] Among them, RFID tags not included in the target RFID set are kept unwritten.

[0052] As a preferred technical solution for the RFID intelligent management system of the seafood supply chain, the associated reconstruction processing method includes:

[0053] The central processing server identifies whether the current supply chain unit has been split, merged, or repackaged.

[0054] When a split occurs, the master index data corresponding to the original master RFID is used to generate several candidate master indices according to the split sub-units;

[0055] When a merger occurs, the master index data corresponding to several original master RFID tags are aggregated to generate a new aggregated master index;

[0056] When a change of equipment occurs, business data continuity must be maintained and the binding relationship between RFID and physical carrier must be re-established;

[0057] The central processing server reselects the master RFID after reconstruction and reallocates several slave RFIDs based on the reconstructed segmented business data.

[0058] After the association reconstruction process is completed, the original master RFID is set as a historical master RFID, retained master RFID, or converted to a slave RFID.

[0059] As a preferred technical solution for the RFID intelligent management system for the seafood supply chain, in the splitting scenario, the central processing server selects the corresponding master RFID based on the data integrity, subsequent flow independence, and expected update frequency of each sub-unit after splitting.

[0060] In the merged scenario, the central processing server selects a new master RFID tag based on the business aggregation level, physical attachment stability, and node access requirements of the merged aggregation unit.

[0061] Among them, for the original master RFID that is not selected as the new master RFID, if it still carries independent traceability data, it will be converted into a slave RFID.

[0062] If it only carries intermediate state data, then its data will be migrated and set as an invalid label.

[0063] As a preferred technical solution for the RFID intelligent management system of the seafood supply chain, the anomaly correction processing method includes:

[0064] When the identification terminal detects the presence of the main RFID but the target RFID is missing, the central processing server generates a missing tag based on the subordinate mapping information in the main RFID.

[0065] When the identification terminal detects that the slave RFID is present but the master RFID is missing, the central processing server uses the superior index information in the slave RFID to look up the corresponding master RFID.

[0066] When the status of the master RFID and the slave RFID is inconsistent, the central processing server determines the trusted data source based on the most recent valid node record, preset priority rules, and digest verification value.

[0067] The writing terminal performs a writeback on inconsistent master RFID and / or slave RFID based on the trusted data source;

[0068] The preset priority rules include at least node trust level, data time level, and data closed-loop integrity level.

[0069] As a preferred technical solution for the RFID intelligent management system for the seafood supply chain, the central processing server is also equipped with an update and compression module, which generates the corresponding compression and update results after completing the rapid release processing method, the targeted completion processing method, the associated reconstruction processing method, or the anomaly correction processing method.

[0070] For a single node operation, only the data representing the state conclusion is written to the main RFID, and the detailed business data on which the state conclusion depends is written to the corresponding slave RFID.

[0071] The status conclusion includes at least one or more of the following: passage conclusion, quality control conclusion, handover conclusion, and traceability conclusion;

[0072] The detailed business data includes at least one or more of the following: original records that led to the corresponding conclusions, process parameters, and timestamps.

[0073] This enables the identification terminal to prioritize processing the status conclusions in the master RFID in subsequent nodes, and to retrieve detailed business data from the corresponding slave RFID according to the slave mapping information when needed.

[0074] Compared with existing technologies, the advantages of this invention lie in dividing the RFID tags corresponding to the same supply chain unit into a main RFID and several slave RFID tags, with the main RFID recording master index data and the slave RFID recording detailed business data. This allows the system to adopt different processing methods for identification data at different supply chain nodes. For nodes that only need to complete passage confirmation, handover confirmation, or status verification, the identification terminal can prioritize making judgments based on the identity identifier, flow status, and subordinate mapping information in the main RFID, without having to process all detailed data each time. This reduces the amount of identification data and the comparison range at most conventional nodes, thereby reducing the processing pressure on the identification processing end and lowering the identification waiting time during node operations.

[0075] Furthermore, this invention does not employ a unified identification and update method for all RFID data. Instead, it divides the identification process into four modes based on node type, identification completeness, state change amount, and historical update frequency: rapid release processing, targeted completion processing, correlation reconstruction processing, and anomaly correction processing. This configuration allows different identification results to correspond to different processing depths: when state changes are minor and identification conditions are met, rapid determination can be achieved using only the master RFID; when only some business data changes, only the target slave RFID is read and updated; and when supply chain units are split, merged, or repackaged, the master-slave relationship is reconstructed. This approach does not simply reduce the number of reads, but rather, by first dividing the processing methods and then determining the reading and update ranges, it matches the identification and writing actions with actual business needs. Therefore, it is more suitable for seafood supply chain scenarios with frequent nodes and a fast pace.

[0076] Furthermore, this invention records subordinate mapping information, update policy identifiers, and digest verification values ​​in the master RFID, enabling the master RFID to function not only as a simple identification tag but also as a guiding entry point for reading and updating slave RFID. When further processing is required, the system can supplement the reading of the target slave RFID according to the master RFID indication, instead of identifying all slave RFID individually. This approach reduces the probability of irrelevant slave RFID participating in the current node identification process and ensures the continuity of key business decisions even when the identification terminal has limited capabilities or the node cycle is fast. In other words, this invention does not require each node to obtain all business details; instead, it uses the master RFID to first convey the status conclusion and then retrieves the corresponding detailed data when necessary, thus balancing identification efficiency and traceability requirements.

[0077] Furthermore, this invention improves the consistency between tag hierarchy settings and the actual flow structure by using differentiated selection rules for master and slave RFID tags. This invention does not arbitrarily fix a particular tag as the master RFID tag, but rather determines the master RFID tag by comprehensively considering data carrying capacity, binding level, physical attachment stability, expected flow cycle, average readability, and the necessity of business aggregation. For situations common in the seafood supply chain where outer boxes, turnover boxes, pallets, batch packages, and sub-packages coexist, this selection method makes the master RFID tag more likely to be placed on carriers with higher stability, clearer aggregation relationships, and higher cross-node reading requirements, thereby increasing the likelihood of the master RFID tag remaining usable in subsequent nodes. Thus, the master-slave distinction is no longer merely a static identification distinction, but forms a more stable correspondence with the actual supply chain structure.

[0078] Furthermore, when supply chain units are split, merged, or re-equipped, this invention reselects the master RFID and reassigns slave RFID tags through an associated reconstruction process. This avoids the problem that the original tag relationship is applicable to the initial state but not to subsequent flow states. For split sub-units, the system can determine new master RFID tags based on the data integrity, flow independence, and expected update frequency after the split; for merged aggregate units, the system can determine new master RFID tags based on the merged business summary level and node access requirements. Thus, the master-slave relationship can be dynamically adjusted as the supply chain structure changes, helping to maintain consistency between subsequent identification logic and actual business objects, and reducing the risk of update confusion or traceability breakage caused by master-slave mismatch.

[0079] Furthermore, this invention reduces the repeated writing of unchanged data through targeted completion and selective writing mechanisms. In actual supply chain nodes, not every operation causes changes to all business data. For example, at some handover nodes, only logistics handover information changes; at some quality inspection nodes, only status conclusions or partial processing records change; at some cold chain nodes, only temperature control-related data may need to be updated. In such scenarios, this invention only updates the target RFID related to the current status change, and simultaneously updates the flow status, mapping version number, and digest check value in the main RFID, while keeping the RFID tags not included in the target set unwritten. This relatively reduces the number of tag writes, lowers the processing overhead and data inconsistency risks caused by frequent full rewrites, and also helps to shorten the node operation time.

[0080] Furthermore, this invention improves the recoverability of the master-slave tag system in actual operation by setting up an anomaly correction processing method. In cases where the master RFID exists but the target slave RFID is missing, the slave RFID exists but the master RFID is missing, or the master-slave status is inconsistent, the system can determine a reliable data source based on the slave mapping information in the master RFID, the superior index information in the slave RFID, the most recently valid node record, and preset priority rules, and accordingly perform a write-back on the master RFID and / or slave RFID. This processing method does not mean that all anomalies can be completely eliminated, but it can at least provide a relatively consistent data foundation for subsequent nodes in cases of missing tags, identification omissions, or update delays, thereby reducing the continuous propagation of anomalies in subsequent links of the supply chain.

[0081] Furthermore, this invention achieves hierarchical storage of conclusion data and detailed data by writing the status conclusion into the main RFID and the detailed business data forming the status conclusion into the corresponding slave RFID. The advantage of this hierarchical approach is that, at regular nodes, the identification terminal prioritizes processing the passage conclusion, quality control conclusion, handover conclusion, or traceability conclusion from the main RFID, while only reading the original records, process parameters, or timestamps from the corresponding slave RFID during traceability, verification, sampling, or anomaly investigation. This not only improves the processing efficiency of most nodes but also helps retain sufficient detailed support when needed, making it more consistent with the business characteristics of the seafood supply chain.

[0082] In summary, the beneficial effects of this invention are not simply about dividing RFID into master and slave tags, but rather about establishing differentiated processing methods for identification data, dynamic selection mechanisms for master and slave tags, local update mechanisms, and anomaly correction mechanisms around the master-slave structure. Each part has a certain interconnectedness: the processing method is determined first during front-end identification, and the processing method then determines the reading and update range; the selection and reconstruction of the master-slave relationship provides the foundation for subsequent identification and updates; and anomaly correction complements the aforementioned structure. Therefore, this invention can more effectively reduce the burden on the identification processing end while ensuring the continuity of supply chain traceability, and improve the system's applicability in scenarios with multiple nodes, multiple tags, and frequent changes. Attached Figure Description

[0083] Figure 1 This is a structural block diagram of the seafood supply chain RFID intelligent management system according to an embodiment of the present invention. Detailed Implementation

[0084] To make the objectives and advantages of the present invention clearer, the present invention will be further described below with reference to embodiments; it should be understood that the specific embodiments described herein are merely for explaining the present invention and are not intended to limit the present invention.

[0085] Preferred embodiments of the present invention will now be described with reference to the accompanying drawings. Those skilled in the art should understand that these embodiments are merely illustrative of the technical principles of the present invention and are not intended to limit the scope of protection of the present invention.

[0086] See Figure 1 As shown, this disclosure relates to a master-slave RFID identification and management system for a seafood supply chain, and more particularly to an identification and updating scheme that divides multiple RFID tags corresponding to the same supply chain unit into master RFID and several slave RFID, and adopts different processing methods based on different states of the identification data. Here, the supply chain unit can be a carrier unit of the actual business object to be traced at a certain stage of circulation, such as a pallet unit, turnover box unit, full case unit, sub-packaging unit, or single batch combination unit. It should be understood that the physical carrier of seafood may change at different nodes; therefore, the supply chain unit does not always correspond to the same physical packaging, but rather to an object that needs to be identified, handed over, traced, or updated as a whole in the current business stage.

[0087] In seafood supply chain scenarios, common business data includes at least identification information, origin batches, fishing or aquaculture information, processing information, temperature control monitoring information, logistics handover information, quality inspection conclusions, node time information, and anomaly record information. In existing solutions, if the aforementioned data is centrally written to a single RFID tag, or if multiple RFID tags are used but each RFID tag employs a similar identification and update method at each node, the identification terminal will need to process a large amount of data or a large number of tag objects at most nodes. The core idea of ​​this invention is to first divide the RFID tags into master and slave segments, and then divide the processing methods for the identification data. This allows the identification terminal to prioritize processing the master index data in the master RFID tag at most nodes, and only perform supplementary readings, updates, or reconstructions on the corresponding slave RFID tags when necessary. This reduces the processing pressure on the identification processing end while maintaining the ability to trace detailed information in the seafood supply chain.

[0088] In a preferred embodiment, the system of the present invention includes an RFID tag group, an identification terminal, a writing terminal, and a central processing server. The RFID tag group is configured corresponding to a single supply chain unit and includes one master RFID and several slave RFID tags. The identification terminal is located at a node in the supply chain and is used to identify the master RFID and / or slave RFID tags and generate corresponding identification data. The writing terminal is used to selectively write or update the master and slave RFID tags. The central processing server is communicatively connected to each identification terminal and each writing terminal, and is used to determine the corresponding data processing method based on the identification data and generate corresponding master-slave update instructions. The central processing server can be implemented using an industrial server, an edge computing controller, a warehouse control host, a cold chain operation control host, or a control platform with data processing and rule execution capabilities; in some embodiments, the central processing server can also be connected to an enterprise resource planning system, a warehouse management system, a transportation management system, or a quality traceability database to receive node business events and output write-back strategies.

[0089] In this embodiment, the master RFID is used to record the master index data of the supply chain unit. The master index data preferably includes at least the following: supply chain unit identification, current circulation status, subordinate mapping information, update strategy identifier, mapping version number, and summary check value. The supply chain unit identification is used to uniquely represent the current supply chain unit and can be in the form of an encoded string, serial number, binary code, or a combination thereof; the current circulation status is used to represent the current business status of the supply chain unit, such as pending sorting, sorted, pending weighing, pending quality inspection, already in storage, pending outbound, in transit, pending handover, or frozen due to abnormality; the subordinate mapping information is used to indicate the set of subordinate RFIDs logically associated with the master RFID, and the subordinate mapping information can be stored in the form of a list of subordinate RFID numbers, a category identifier and number correspondence table, a category bitmap, or an index pointer; the update strategy identifier is used to represent the processing depth of the current node on the relevant data, such as master read priority, partial supplementary read, detailed review, reconstruction priority, and anomaly correction priority; the mapping version number is used to represent the version of the current master-slave relationship so as to distinguish the master-slave organizational structure at different stages after splitting, merging, or repackaging; and the digest check value is used to reflect the consistency status between the master RFID and several subordinate RFIDs.

[0090] In this embodiment, the RFID is used to record detailed business data. This detailed business data is relative to the master index data in the main RFID and can be understood as detailed process data that constitutes the flow conclusion, quality control conclusion, or traceability conclusion. Detailed business data may include one or more of the following: source batch data, processing data, temperature control monitoring data, logistics handover data, and anomaly record data. It should be understood that different RFID tags do not necessarily need to record the same type of data; in a preferred embodiment, different RFID tags correspond to different detailed business categories so that the identification terminal can read data by category when supplementary reading is required. For example, the first RFID tag can record information such as source batch, origin, water area, fishing vessel number, or aquaculture pond; the second RFID tag can record processing information such as sorting, cleaning, weighing, cutting, packing, and pre-cooling; the third RFID tag can record the temperature range, number of times exceeding the temperature limit, duration of exceeding the temperature limit, and sampling timestamp during cold chain transportation; and the fourth RFID tag can record logistics handover information such as warehousing entry / exit, handover entity, handover time, destination node, and transportation batch. Those skilled in the art can make corresponding adjustments to the specific content carried by each RFID tag based on the type of seafood, the depth of the supply chain, and the storage capacity of the tag.

[0091] To facilitate implementation, this embodiment further explains the selection method of master RFID and slave RFID. In the seafood supply chain, multiple RFID tags may exist simultaneously on pallets, turnover boxes, full cases, or sub-packages within the same supply chain unit. To avoid placing master tags on carriers that are frequently disassembled or have short-cycle failures, in this embodiment, the master RFID is preferentially selected based on RFID tags that are bound to stable carriers, have long circulation cycles, strong business aggregation relationships, and high average readability at nodes. Here, a stable carrier can be a pallet, turnover box, standard outer box, or a carrier that is not frequently replaced during a single sorting; a long circulation cycle means that the carrier is expected to remain unchanged across multiple consecutive nodes; a strong business aggregation relationship means that there are a large number of its subordinate physical or logical objects, and the data of the subordinate objects needs to be referenced in the form of aggregated results at several nodes.

[0092] In one specific implementation, the central processing server can calculate the primary tag priority score for candidate RFID tags and determine the one with the highest score as the primary RFID tag. The priority score can be formed based on the following parameters: physical attachment stability score, expected turnover cycle score, average readability score, business aggregation necessity score, and a reverse score for the probability of repeated disassembly and reassembly. To enable those skilled in the art to implement this, in this embodiment, the above scores can be calculated using either a weighted summation method or a method of ranking items and then comparing priorities. Taking weighted summation as an example, if the total score is 100 points, physical attachment stability can account for 25 to 35 points, expected turnover cycle for 20 to 30 points, average readability for 20 to 30 points, business aggregation necessity for 10 to 20 points, and the reverse score for the probability of repeated disassembly and reassembly for 5 to 15 points. It should be understood that the above score range is only an example setting for ease of implementation and does not constitute a limitation of the present invention; in practical applications, the calibration and adjustment can be made according to the physical packaging structure, reading and writing equipment performance, and node layout of the seafood supply chain.

[0093] For the allocation of RFID tags, this embodiment preferably divides them according to data change frequency, traceability independence, and collaborative reading requirements. Data change frequency refers to the number of times a certain type of data is updated within a preset time window or preset node sequence; traceability independence refers to whether a certain type of data needs to be extracted and verified independently without relying on other data categories; collaborative reading requirements refer to whether two or more types of data typically need to be read simultaneously in most nodes. Based on this, data with an update frequency higher than a preset frequency threshold can be written to the first RFID tag, data requiring independent traceability can be written to the second RFID tag, and data that needs to be jointly retrieved in most nodes can be written to the same RFID tag or several RFID tags with adjacent numbers. To make the implementation path clearer, the preset frequency threshold in this embodiment can be determined based on the number of data updates within the most recent N nodes or the most recent T time period, where N can be 3 to 10 nodes, and T can be 12 hours, 24 hours, 48 ​​hours, or a complete delivery cycle. If the average number of updates for a certain type of data within the window is greater than or equal to the preset number, such as 2 or 3 times, it can be determined as high-frequency update data. Therefore, the system can extract high-frequency change information from the main RFID, so as to avoid writing too much detailed information to the main RFID every time it is updated.

[0094] In this embodiment, the digest check value in the master RFID is used to characterize the current master-slave consistency status. For ease of implementation, the digest check value can be generated by the central processing server based on the key fields, version number, update timestamp, and tag number of each slave RFID. The key fields can be the set of fields most representative of the current status in each slave RFID, such as the source batch number, the most recent processing status code, the most recent temperature control status code, the most recent handover status code, etc. The digest check value can be implemented using any of the following: cyclic redundancy check value, hash digest value, XOR check value, or preset encoded mapping value. Considering the limited RFID storage space, in a preferred embodiment, a 16-bit or 32-bit compressed digest can be used as the consistency characterization value in the master RFID. In this way, when the identification terminal only reads the master RFID, it can use the digest check value to initially determine whether the current master-slave data is consistent with the server record. If they are inconsistent, a further supplementary reading or correction process is triggered.

[0095] The following describes the data processing method. In this embodiment, after receiving the identification data uploaded by the identification terminal, the central processing server first extracts the node category, identification completeness, status change amount, and historical update frequency corresponding to this identification. The node category can be preset by the node configuration table or obtained by mapping the node ID. Preferably, the node categories can be divided into access nodes, operation nodes, and verification nodes. Access nodes are mainly used to confirm whether the supply chain unit is allowed to continue to circulate, such as outbound ports, inbound ports, transfer ports, or loading ports; operation nodes are mainly used to perform actual business processes such as sorting, weighing, processing, repackaging, splitting, and merging; verification nodes are mainly used to perform operations such as quality inspection, traceability review, regulatory spot checks, or anomaly review.

[0096] The identification completeness is used to characterize whether the current identification result meets the minimum judgment condition of the node. To enable those skilled in the art to implement this, in this embodiment, the identification completeness can be determined in any of the following ways: first, determining whether the main RFID tag was successfully identified and whether the key fields in the main RFID tag were completely read; second, determining whether the minimum tag set required by the current node has been identified; third, calculating the completeness percentage according to the ratio of the number of successfully identified fields to the number of target fields. For example, in a passage-type node, if the identity identifier, circulation status, and mapping version number in the main RFID tag are all successfully identified, the minimum judgment condition can be determined to have been met; in a work-type node, if the target to be operated is also successfully identified by the RFID tag in addition to the main RFID tag, the identification completeness requirement of the node can be considered to have been met. The minimum judgment condition can be pre-written into the central processing server through the node configuration table.

[0097] The state change quantity is used to characterize the degree of data change caused by the current node's business event relative to the previous valid node record. Preferably, the state change quantity can be determined by any one of the following: the number of changed fields, the cumulative weight of the changed fields, or the change category level. For example, if only the handover timestamp changes, the state change quantity is small; if packaging structure changes, batch affiliation changes, and temperature control anomaly status changes occur simultaneously, the state change quantity is large. For ease of implementation, the central processing server can pre-set change weights for different fields or different field groups, such as setting the flow status change as a first-level weight, the processing step change as a second-level weight, and the splitting or merging event as a third-level weight. Then, the change weights triggered by the current node are summed. If the sum does not exceed a first preset threshold, it is determined to be a minor change; if it exceeds the first preset threshold but does not reach the reconstruction threshold, it is determined to be a partial change; if it reaches the reconstruction threshold, it is determined to be a structural change. The preset threshold here can be obtained by calibration using historical samples based on business complexity and tag writing cost.

[0098] Historical update frequency is used to characterize the intensity of updates occurring in a supply chain unit over a period of time. Preferably, the central processing server can count the number of writes, mapping changes, anomaly corrections, or master-slave relationship adjustments for the current supply chain unit in the most recent T time period or the most recent N nodes, and determine whether the master-slave relationship reorganization threshold has been reached based on the statistical results. The reorganization threshold here is used to determine whether the existing master-slave structure is still suitable for subsequent flows. If a supply chain unit frequently changes its configuration, frequently merges or splits, or frequently performs partial updates within a short period of time, it indicates that its current master-slave configuration may no longer be conducive to the efficient identification of subsequent nodes, and at this time, the associated reconstruction processing method can be triggered. The reorganization threshold can be set based on business experience to a minimum of 2, 3, or more mapping adjustments within a preset time period, or it can be set to a percentile value higher than the average level based on sample statistics.

[0099] Based on the above parameters, the central processing server divides this identification process into at least one of the following: rapid release processing, targeted completion processing, correlation reconstruction processing, and anomaly correction processing. When the identification completeness reaches the minimum judgment condition and the state change amount does not exceed the first preset threshold, rapid release processing is preferred. When the state change amount exceeds the first preset threshold but only involves some subdivided business data, and the current master-slave structure remains valid, targeted completion processing is preferred. When splitting, merging, or repackaging occurs, or the historical update frequency reaches the master-slave relationship reorganization threshold, correlation reconstruction processing is preferred. When the identification terminal identifies master-slave missing, master-slave inconsistent, version number misaligned, or summary verification abnormalities, anomaly correction processing is preferred. It should be understood that in actual business operations, a single identification process may trigger two or more processing methods sequentially. For example, rapid release may fail first, followed by targeted completion; or anomalies may be detected first, followed by reconstruction processing after anomaly correction.

[0100] In most common nodes, the system does not need to obtain all business details at the node, but only needs to confirm whether the supply chain unit is qualified to continue circulation. Therefore, in the fast release processing mode, the identification terminal prioritizes reading only the master RFID and uploads the identity identifier, circulation status, subordinate mapping information, update strategy identifier, mapping version number, and digest check value from the master RFID to the central processing server. The central processing server determines whether the supply chain unit corresponding to the master RFID meets the release conditions based on the current node category and node permissions. The release conditions may include at least: valid identity identifier, circulation status matching the current node's allowed status, mapping version number not expired, and digest check value consistent with the most recent valid record or within the tolerable deviation range. If the release conditions are met, the central processing server generates a release confirmation result and can send the result back to the identification terminal or node control device; if the release conditions are not met, the identification process switches to a targeted completion processing mode or anomaly correction processing mode. Thus, the system reduces the reading requirements of most nodes for slave RFID without sacrificing the main status judgment capability.

[0101] In this embodiment, the tolerable deviation range is used to accommodate temporary inconsistencies between the master RFID digest and the latest detailed record in the server due to network latency, asynchronous write-back, or short-term caching. To avoid confusion for those skilled in the art due to unclear wording, the tolerable deviation range in this embodiment can be preset to any of the following conditions: the master RFID digest is inconsistent with the server digest, but the master RFID update time does not lag behind the server update time by more than a preset duration; or, the master RFID digest is inconsistent, but the inconsistency only occurs in field groups that do not affect the current node's judgment; or, the master RFID digest differs from the server digest, but the latest version corresponding to the master RFID is not marked as an invalid version. The preset duration can be set to several seconds, tens of seconds, or longer depending on the network topology and node deployment, as long as reasonable asynchronous errors are allowed without substantially affecting the current node's security judgment.

[0102] In this embodiment, when the central processing server determines that the current node has undergone partial data changes, the digest verification value in the main RFID does not support direct release, or the current node itself is an operational node that requires extraction of partial details, the system triggers a targeted completion processing method. Specifically, the central processing server determines the target slave RFID set that needs to be read for this node based on the slave mapping information and update strategy identifier in the main RFID. The target slave RFID set can be generated according to data category or field requirements. For example, at the weighing node, only slave RFID recording processing or packaging data is read; at the cold chain handover node, only slave RFID recording temperature control status and logistics handover is read; at the regulatory sampling node, slave RFID corresponding to the source batch and quality inspection history can be read. After receiving the read instruction from the central processing server, the identification terminal only performs supplementary identification on the target slave RFID set and generates partial completion data, which is then uploaded to the server.

[0103] After obtaining partially completed data, the central processing server compares the current node event with the most recently valid node record and confirms whether the current node operation has caused a state change. If no state change occurs, the tag data remains unchanged, and only the node access record on the server side is updated. If a state change occurs, the writing terminal only updates the target RFID corresponding to the state change and synchronously updates the flow status, mapping version number, and digest check value in the master RFID. This synchronous update does not require absolutely simultaneous writing, but rather that the server generates a unified update sequence within the same business transaction, ensuring that the data versions of the master RFID and related slave RFID maintain a corresponding relationship. To make the implementation process clearer, in a preferred implementation, the server can first generate new slave RFID data and its version number, then recalculate the master RFID digest based on the new slave RFID version and key fields, and subsequently send slave RFID write commands and master RFID write commands to the writing terminal sequentially. After both return successful results, the update record is marked as committed. Slave RFID tags not included in the target set are not written to reduce redundant updates of irrelevant tags.

[0104] In this embodiment, the writing terminal can be a handheld writing device, a fixed RFID reader / writer, a benchtop near-field writing module, or a writing station encapsulated in an online system. To reduce the risk of master-slave mismatch caused by writing failure, preferably, the writing terminal reads the current version number of the target RFID tag before writing, and performs the writing only after confirming that the current version number is consistent with the server's expectation or is within the allowable coverage range; after writing, it reads back at least one key field or the version number to confirm whether the writing was successful. If the writing fails, the server can temporarily mark the tag as pending correction and attempt to write it back again in subsequent nodes or switch to an abnormal correction process.

[0105] Specifically, in the seafood supply chain, supply chain units frequently undergo splitting, merging, and repackaging. Splitting refers to the division of a previously unified supply chain unit into two or more independently circulating sub-units; merging refers to the combination of two or more previously independently circulating supply chain units into a new aggregate unit; and repackaging refers to the replacement of the original carrier without altering the business affiliation or with only minor changes, such as replacing a crate with a foam box, or a pallet with the internal frame of a cold chain transport vehicle. In these scenarios, maintaining the original master-slave relationship may lead to inconsistencies between the master RFID tag and the actual physical object in subsequent nodes, thus affecting identification efficiency and traceability accuracy. Therefore, in this embodiment, when the central processing server detects the aforementioned structural changes, it triggers an associated reconstruction process.

[0106] In a splitting scenario, the central processing server generates several candidate master indices from the original master RFID's corresponding master index data according to the splitting rules, based on the splitting sub-units. The splitting rules can be generated based on business event inputs, sorting equipment outputs, manual confirmation results, or packing station records. For example, if the original tote contains three sizes of seafood, and after sorting, they enter three sub-packaging units, the system will generate candidate identity identifiers, candidate flow statuses, and candidate subordinate mapping ranges for each sub-packaging unit based on the sorting results. Then, the server analyzes the data completeness, subsequent flow independence, and expected update frequency corresponding to each sub-unit, and selects a new master RFID for each sub-unit. Here, data completeness measures whether a sub-unit currently possesses the minimum master index data required for independent flow; subsequent flow independence measures whether the sub-unit will be independently handed over, independently monitored, or independently priced in subsequent nodes; and expected update frequency measures whether its detailed information will still change frequently in subsequent nodes. If a sub-unit already has a relatively complete independent business identity and the probability of subsequent independent transfer is high, then a new master RFID will be selected for it first; conversely, if a sub-unit is only a short-term intermediate unit or will be aggregated again later, its RFID can temporarily maintain the role of slave RFID.

[0107] In the merged scenario, the central processing server aggregates the master index data corresponding to several original master RFID tags to generate a new aggregated master index and reselects a new master RFID tag. The new master RFID tag is preferably placed on the most stable physical carrier after the merge and the carrier most likely to continue existing across multiple subsequent nodes. For original master RFID tags not selected as new master RFID tags, the server determines their subsequent role based on the nature of the data they carry: if they still carry independent traceability data, such as the original batch origin, original fishing vessel number, or original temperature control history, they can be converted to slave RFID tags and retained; if they only carry intermediate state data, and their key information has been migrated to the new master RFID tag or other slave RFID tags, they can be set as invalid tags after the data migration is completed. For ease of implementation, in this embodiment, setting a tag as invalid can be achieved in any of the following ways: writing an invalid status code into the tag; marking its status as unusable in the server; or simultaneously recording in both the tag and the server that it has exited the current master-slave structure. This helps subsequent nodes avoid mistakenly treating old tags as currently valid master tags when they are identified.

[0108] In the context of data replacement, the system prioritizes maintaining the continuity of business data and focuses on rebuilding the binding relationship between RFID and the physical carrier. For example, when replacing a tote box with a transport foam box, if the original master RFID is bound to the tote box and the tote box does not travel with the goods, the master index data needs to be migrated to the RFID on the new carrier, and the master-slave mapping version number needs to be updated. If the original master RFID on the tote box travels with the goods and the new carrier is only additional packaging, the original master RFID can be retained, and only the slave mapping information needs to be updated. It should be understood that data replacement does not necessarily lead to a change in the master RFID. The system can determine whether to replace the master RFID based on the stability of the carrier after the replacement, the readability of subsequent nodes, and business aggregation requirements.

[0109] In this embodiment, to avoid data loss during the reconstruction process, the central processing server preferably adopts an update method of first establishing new relationships and then switching old relationships. Specifically, the server first generates a new master index, a new subordinate mapping relationship, and a new version number for the new structure, and then completes the writing of the new master RFID and related slave RFID through the writing terminal; only after confirming that the new structure is fully effective is the original master RFID marked as a historical master RFID, retained as a master RFID, or converted to a slave RFID. The historical master RFID is used to retain traceability associations for a period of time so that the previous structure can be traced during review or regulatory spot checks; it can record historical status codes in the tag and record the corresponding new version mapping relationship in the server.

[0110] In practical use, situations may arise such as the master RFID being identifiable while some slave RFID tags are missing, slave RFID tags being identifiable while the master RFID is missing, inconsistent master-slave status, inconsistent master-slave version numbers, digest verification anomalies, or tag read / write failures. To address these issues, this embodiment includes an anomaly correction process to improve system recoverability. When the master RFID exists but the target slave RFID is missing, the central processing server generates a missing tag based on the slave mapping information in the master RFID and determines whether the missing tag affects the current node's judgment by combining this with the most recent valid record in the server. If it does not affect the judgment, for example, if the missing tag is a historical detail slave RFID tag unrelated to the current node, the system can allow the pass and record it as an anomaly awaiting rewriting. If it affects the current node's judgment, for example, if the missing tag is a temperature control slave RFID tag that the current node must verify, the system prohibits direct release and prompts the user to enter a rewriting, manual review, or anomaly freeze state.

[0111] When a slave RFID tag exists but the master RFID tag is missing, the central processing server uses the superior index information, the most recent valid node record, or the tag group's historical mapping record in the slave RFID tag to look up the corresponding master RFID tag. To enable implementation by those skilled in the art, in this embodiment, the slave RFID tag preferably records at least the superior index identifier, its version number, and its own data category code. Thus, when the master RFID tag is missing, the server can find the possible corresponding master RFID tag through the superior index identifier, and then combine version number matching and node context to determine the most likely valid master RFID tag. If a valid master RFID tag is found, the writing terminal can be notified to rewrite or replace it; if no valid master RFID tag is found, but the current slave RFID tag contains key fields sufficient to characterize the current business object, the system can temporarily generate a transitional master index, and complete the formal master-slave relationship restoration in a subsequent reconstruction node.

[0112] When the master RFID and slave RFID statuses are inconsistent, the central processing server determines the trusted data source based on the most recent valid node record, preset priority rules, and digest verification values. The preset priority rules can include at least node trust level, data time level, and data loop integrity level. The node trust level distinguishes the trustworthiness of different node records; for example, the trust level of regulatory verification nodes and formal handover nodes is usually higher than that of ordinary access nodes. The data time level compares the order of data records, prioritizing the latest and completed valid records. The data loop integrity level compares whether a record contains a complete transaction chain from generation and writing to readback confirmation. Preferably, the server can first compare the node trust level, then the data time level, and finally the data loop integrity level to determine the final trusted data source. The writing terminal performs a write-back operation on the inconsistent master RFID and / or slave RFID based on the trusted data source to complete the anomaly correction.

[0113] In a preferred feasible approach, the central processing server can also generate a transaction identifier for each write and write the transaction identifier to the transaction record field of both the server log and the target tag. This allows for the determination of whether an update has been fully executed during anomaly correction based on the transaction identifier, thereby reducing version confusion caused by partial write successes and failures. If tag space is limited, the transaction identifier can be fully stored only on the server, while only the transaction abbreviation or transaction sequence number is written to the tag.

[0114] In this embodiment, the system also includes an update compression module to generate corresponding compressed update results after completing the rapid release processing, targeted completion processing, associated reconstruction processing, or anomaly correction processing. Compressed update does not simply mean compressing the data encoding length, but rather writing only the data representing the status conclusion into the main RFID, and writing the detailed business data upon which the status conclusion depends into the corresponding slave RFID. For example, after completing an outbound node, the main RFID can write status conclusions such as "outbound, transfer permitted, temperature control normal, handover effective," while detailed information such as the outbound time, outbound operator, vehicle number, and temperature sampling values ​​for each time period are written into the corresponding slave RFID. With this setup, the identification terminal prioritizes processing the status conclusions in the main RFID in subsequent nodes, and retrieves detailed business data from the relevant slave RFID when needed based on the slave mapping information in the main RFID. This method is beneficial for rapid decision-making at multiple nodes and for reconstructing detailed processes during spot checks, reviews, or dispute resolution.

[0115] To further illustrate the implementation process of this invention, a seafood cold chain logistics example is provided below. Assume a container holds the same batch of shrimp products, forming an initial supply chain unit at the temporary holding and shipping node. At this point, the system designates the RFID tag bound to the outside of the container, which is expected to remain unchanged across subsequent nodes, as the master RFID tag. Several slave RFID tags are designated on the source batch card, processing record card, temperature control record card, and logistics handover card, respectively. The master RFID tag contains the supply chain unit identification, current status (pending sorting), slave mapping information, initial version number, and a summary checksum formed from the key information of each slave RFID tag. The source batch slave RFID tag contains information such as the aquaculture area, stocking batch, and quarantine batch; the processing record slave RFID tag is initially empty or only records the pending processing status; the temperature control record slave RFID tag begins recording the initial storage temperature and on-chain time; and the logistics handover slave RFID tag records the current node information.

[0116] When the tote enters the sorting node, the node category is a work-type node. The identification terminal first reads the master RFID. The central processing server determines, based on the node category and update strategy identifier, that the current node needs to supplement the processing record RFID and the source batch RFID, thus triggering a targeted completion processing method. After sorting, if the tote is divided into two sub-packaging units, the system triggers an association reconstruction processing method. The server generates candidate master indices for the two sub-packaging units based on the sorting results and analyzes that the two sub-packaging units will subsequently enter the weighing, packaging, and transportation nodes independently, thus selecting new master RFID for each. The original tote's master RFID is set as the historical master RFID and its mapping relationship to the two new master RFIDs is retained; the two new master RFIDs record the new supply chain unit identity, status "sorted and awaiting weighing," corresponding subordinate mapping version number, and new summary check value, respectively. If the original source batch RFID has traceability significance for both sub-packaging units, the association relationship can be copied or mapped to the two sub-packaging units respectively; the original processing record RFID can be split into two new processing record RFIDs based on the sorting results.

[0117] When one of the sub-packaging units enters the weighing node, the node category remains an operational node, but this node only needs to update the weighing result and packaging status. At this time, after reading the main RFID of the sub-packaging unit, the system determines that the current status change only involves processing data. Therefore, it only reads and updates the processing record from the RFID, while simultaneously updating the flow status in the main RFID to "weighed and awaiting warehousing," and recalculating the summary verification value. The other sub-packaging unit that has not entered the weighing node does not participate in this update, and its corresponding RFID remains unwritten.

[0118] When the sub-packaging unit enters the cold storage and undergoes several temperature control sampling points before transportation, due to frequent temperature data updates, the system continuously writes temperature control details to the temperature control slave RFID, while the master RFID only updates the temperature control conclusion periodically or when a state boundary event occurs. For example, if all temperature control sampling is within the preset temperature zone, the temperature control status in the master RFID can remain normal; if continuous over-temperature occurs and a preset judgment condition is met, the master RFID is updated to temperature control abnormality pending verification. The preset temperature zone, the number of consecutive over-temperature occurrences, or the duration of over-temperature can be set according to product type, cold chain specifications, and enterprise internal control standards. To enable implementation by those skilled in the art, these thresholds can be pre-stored in the central processing server or node configuration terminal and can be configured separately according to seafood category.

[0119] At the transport handover node, the identification terminal first reads the master RFID. If the master RFID shows a status that allows handover and the digest check value matches the server side, the system can directly execute the fast release process. If the master RFID shows a temperature control anomaly requiring verification or the digest check value is inconsistent, the system triggers a targeted completion or anomaly correction process, reading the temperature control slave RFID and the logistics handover slave RFID for further confirmation. If, during this process, it is found that the logistics handover slave RFID is identifiable but the master RFID is missing, the server uses the superior index information in the logistics handover slave RFID to look up the master RFID and generates a rewrite instruction based on the most recent valid node record, rewriting the new master RFID onto the current packaging carrier to restore the master-slave identification capability of the sub-packaging unit.

[0120] The implementation process of the method of the present invention is further described below. In one embodiment, the master-slave RFID identification management method for the seafood supply chain includes at least the following steps:

[0121] Step S1: Establish the correspondence between supply chain units and RFID tag groups, and select the master RFID based on carrier stability, circulation cycle, readability and business aggregation necessity, and allocate the remaining RFID as several slave RFID according to data change frequency, traceability independence and collaborative reading requirements.

[0122] Step S2: At the supply chain node, the identification terminal reads the master RFID and / or slave RFID and generates identification data;

[0123] Step S3: The central processing server classifies the processing method for this identification process based on node type, identification completeness, state change amount, and historical update frequency.

[0124] Step S4: When the rapid determination conditions are met, the node release or status confirmation is completed solely based on the main RFID.

[0125] Step S5: When there is a local data change, determine the target slave RFID set according to the slave mapping information in the master RFID, and perform supplementary reading and selective update on the target slave RFID set;

[0126] Step S6: When splitting, merging, or repackaging occurs, perform master-slave relationship reconstruction, reselect the master RFID and rebuild the slave mapping relationship;

[0127] Step S7: When a master-slave node is missing, master-slave node is inconsistent, or the summary is abnormal, perform anomaly correction based on the most recent valid node record and preset priority rules.

[0128] Step S8: After completing any of the above processing methods, generate a compressed update result, write the status conclusion to the master RFID, write the detailed business data to the corresponding slave RFID, and update the version number and summary verification value.

[0129] In this embodiment, the above steps are not required to be executed mechanically in sequence. In practical applications, steps S4 to S7 can be triggered individually or in combination based on the identification results. For example, in a node processing operation, step S4 can be executed first to attempt rapid release; if an anomaly is found in the digest, the process proceeds to step S7; if a change of equipment is detected in step S7, the process further proceeds to step S6. For those skilled in the art, any processing logic that reflects the hierarchical management of master-slave RFID, the differentiated division of identification processing methods, and the selective update concept can be considered a reasonable implementation of the technical concept of this invention.

[0130] It should be further explained that the parameters involved in this invention, such as preset threshold, preset range, preset frequency threshold, minimum judgment condition, tolerable deviation range, and resetting threshold, can all be determined through at least one of the following methods: pre-setting according to the business specifications of seafood categories; statistical calibration based on historical operating data; obtaining based on actual measurement of equipment identification performance; or being imported by the administrator according to node configuration during the system deployment phase. In other words, this invention does not rely on any specific absolute value, but allows those skilled in the art to engineer the parameter values ​​according to the specific application environment. As long as these parameters can support the system in completing processing mode division, master-slave selection, selective update, and anomaly correction at different nodes, this invention can be realized.

[0131] The specific embodiments of the present invention have now been described in detail. It will be readily understood by those skilled in the art that the scope of protection of the present invention is obviously not limited to the specific embodiments described above. Without departing from the principles of the present invention, those skilled in the art can make equivalent modifications or substitutions to the RFID quantity, tag carrier, field types, version control method, digest generation method, threshold setting method, and node execution order; all such modified or substituted technical solutions should fall within the scope of protection of the present invention.

Claims

1. A marine product supply chain RFID intelligent management system, characterized in that, include: A plurality of RFID tag groups bound to seafood supply chain units, the RFID tag group comprising a master RFID and a plurality of slave RFID; Several identification terminals set at nodes in the supply chain are used to identify the main RFID and / or the slave RFID and generate corresponding identification data; A plurality of write terminals are provided for selectively writing or updating the master RFID and the slave RFID; The central processing server is connected to each identification terminal and each writing terminal to determine the corresponding data processing method based on the identification data and generate the corresponding master-slave update instructions. The main RFID tag is used to record the main index data of the corresponding supply chain unit. The main index data includes at least the identity identifier, circulation status, subordinate mapping information and update strategy identifier. The RFID is used to record segmented business data for the corresponding supply chain unit. The segmented business data includes at least one or more of the following: source batch data, processing data, temperature control monitoring data, and logistics handover data. Based on the identification data, the central processing server triggers the corresponding identification process using at least one of the following data processing methods: A fast-release processing method is used to complete node passage confirmation based solely on the main RFID; The targeted completion processing method is used to complete partial data from the RFID based on the target indicated by the main RFID; The associated restructuring processing method is used to rebuild the master-slave relationship when supply chain units are split, merged, or repackaged; Anomaly correction processing method is used to write back and update the master RFID and / or slave RFID in case of identification conflicts, missing data or inconsistent status.

2. The seafood supply chain RFID intelligent management system according to claim 1, characterized in that, The process by which the central processing server classifies the processing methods of the identification data includes: extracting the node category, identification completeness, state change amount, and historical update frequency corresponding to this identification; Based on the node category, determine whether this identification belongs to a passage node, a task node, or a verification node; Based on the identification completeness, determine whether this identification meets the minimum judgment condition of only reading the main RFID; Determine whether there is new business data or changes to existing business data based on the state change amount. Based on the historical update frequency, determine whether the corresponding supply chain unit has reached the master-slave relationship reorganization threshold; When the completeness of identification reaches the minimum judgment condition and the amount of state change does not exceed the preset threshold, the central processing server triggers the fast release processing mode. When the amount of state change exceeds a preset threshold and only involves a portion of the subdivided business data, the targeted completion processing method is triggered; When the historical update frequency reaches the master-slave relationship reorganization threshold or when splitting, merging, or repackaging occurs, the associated reconstruction processing method is triggered.

3. The seafood supply chain RFID intelligent management system according to claim 1, characterized in that, For a single supply chain unit, the selection of the main RFID tag is performed by the main tag determination module, which is used to: Identify the data carrying range, binding level, physical attachment stability, and expected circulation cycle of each RFID tag; The RFID tag that is bound to a stable carrier, has the longest corresponding circulation cycle, and has the largest number of associated lower-level tags will be set as the candidate master RFID. The candidate master RFID tags are sorted according to their identification priority, and the RFID tag with the highest identification priority is set as the master RFID tag. The identification priority is related to the average readability of RFID in the supply chain nodes, the probability of repeated disassembly and assembly, and the necessity of business aggregation. The slave RFID consists of the remaining RFIDs other than the master RFID, and each corresponds to a different category of segmented business data.

4. The seafood supply chain RFID intelligent management system according to claim 3, characterized in that, The process by which the central processing server distributes data from RFID tags includes: Based on the frequency of change of segmented business data, data with an update frequency higher than a preset frequency threshold are assigned to the first RFID tag; Based on the independence of traceability of segmented business data, data that requires independent traceability is allocated to the second RFID; Based on the collaborative relationships of the segmented business data, the data that needs to be identified is assigned to several RFID tags with the same or adjacent numbers; Among them, the first priority is to record processing data and logistics handover data from RFID; The second method prioritizes recording source batch data and temperature control monitoring data from RFID. The master RFID record records the data category index and read pointer corresponding to each slave RFID.

5. The seafood supply chain RFID intelligent management system according to claim 1, characterized in that, The fast release processing method includes: The identification terminal only reads the main RFID tag; The central processing server determines whether the corresponding supply chain unit meets the release conditions of the current node based on the identity identifier, circulation status and update strategy identifier in the main RFID. If the release conditions are met, a release confirmation result is generated; If the release conditions are not met, the current identification will be switched to the directional completion processing method or the anomaly correction processing method. The master RFID also records a digest check value, which is used to characterize the current consistency status of a number of slave RFIDs.

6. The seafood supply chain RFID intelligent management system according to claim 5, characterized in that, The targeted completion processing method includes: The central processing server determines the target RFID set that needs to be read again based on the subordinate mapping information and update policy identifier in the master RFID; The identification terminal performs supplementary identification on the target from the RFID set and generates partial completion data; The central processing server determines whether the node operation has caused a state change based on the partially completed data. When a status change occurs, the writing terminal only updates the RFID of the target corresponding to the status change, and synchronously updates the flow status, subordinate mapping version number and digest check value in the master RFID. Among them, RFID tags not included in the target RFID set are kept unwritten.

7. The seafood supply chain RFID intelligent management system according to claim 1, characterized in that, The association reconstruction processing method includes: The central processing server identifies whether the current supply chain unit has been split, merged, or repackaged. When a split occurs, the master index data corresponding to the original master RFID is used to generate several candidate master indices according to the split sub-units; When a merger occurs, the master index data corresponding to several original master RFID tags are aggregated to generate a new aggregated master index; When a change of equipment occurs, business data continuity must be maintained and the binding relationship between RFID and physical carrier must be re-established; The central processing server reselects the master RFID after reconstruction and reallocates several slave RFIDs based on the reconstructed segmented business data. After the association reconstruction process is completed, the original master RFID is set as a historical master RFID, retained master RFID, or converted to a slave RFID.

8. The seafood supply chain RFID intelligent management system according to claim 7, characterized in that, In the splitting scenario, the central processing server selects the corresponding master RFID based on the data integrity of each sub-unit after splitting, the independence of subsequent flow, and the expected update frequency. In the merged scenario, the central processing server selects a new master RFID tag based on the business aggregation level, physical attachment stability, and node access requirements of the merged aggregation unit. Among them, for the original master RFID that is not selected as the new master RFID, if it still carries independent traceability data, it will be converted into a slave RFID. If it only carries intermediate state data, then its data will be migrated and set as an invalid label.

9. The seafood supply chain RFID intelligent management system according to claim 1, characterized in that, The anomaly correction processing method includes: When the identification terminal detects the presence of the main RFID but the target RFID is missing, the central processing server generates a missing tag based on the subordinate mapping information in the main RFID. When the identification terminal detects that the slave RFID is present but the master RFID is missing, the central processing server uses the superior index information in the slave RFID to look up the corresponding master RFID. When the status of the master RFID and the slave RFID is inconsistent, the central processing server determines the trusted data source based on the most recent valid node record, preset priority rules, and digest verification value. The writing terminal performs a writeback on inconsistent master RFID and / or slave RFID based on the trusted data source; The preset priority rules include at least node trust level, data time level, and data closed-loop integrity level.

10. The seafood supply chain RFID intelligent management system according to claim 9, characterized in that, The central processing server is also equipped with an update and compression module, which is used to generate corresponding compressed update results after completing the fast release processing method, the targeted completion processing method, the associated reconstruction processing method, or the anomaly correction processing method. For a single node operation, only the data representing the state conclusion is written to the main RFID, and the detailed business data on which the state conclusion depends is written to the corresponding slave RFID. The status conclusion includes at least one or more of the following: passage conclusion, quality control conclusion, handover conclusion, and traceability conclusion; The detailed business data includes at least one or more of the following: original records that led to the corresponding conclusions, process parameters, and timestamps. This enables the identification terminal to prioritize processing the status conclusions in the master RFID in subsequent nodes, and to retrieve detailed business data from the corresponding slave RFID according to the slave mapping information when needed.

Images