A traceable management system based on a breeding industry service platform and a method thereof

Abstract

The application relates to the technical field of data management systems and methods of classification G06Q, and provides a traceable management system based on a breeding industry service platform and a method thereof, which comprises a server, a mobile data anchoring device, a detachable traceable label module, a life cycle state management module, an event hash and anchor point verification module and a blockchain intelligent verification module; the detachable traceable label module is used for identifying the individual identity of breeding and the life cycle state, and triggering state change events in the disassembly behavior; the mobile data anchoring device collects the data of key nodes and forms anchor point records; the life cycle state management module maintains the life cycle logical state diagram of each individual, and checks whether all event uploads are compliant; the event hash and anchor point verification module encapsulates all behavior nodes into structured hash events, compares and checks with the current state diagram, and forms trusted anchor points; and the blockchain intelligent verification module performs contract-level verification on the event hash and the state path.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of data management system and method for supervision purposes, and particularly relates to a traceable management system based on a breeding industry service platform and a method thereof. BACKGROUND

[0002] In the existing breeding industry, there are problems such as data fragmentation, unverifiable information, and difficult to trace the process in the process from feeding, transfer, transportation to slaughtering and sales. Especially in food safety and responsibility traceability, the traditional system relies on static labels and isolated records, lacks unified and reliable platform support, and consumers also have difficulty in obtaining complete and true industry chain information.

[0003] For example, the breeding traceability system based on a mobile terminal disclosed in Chinese patent CN107222535A can trace the breeding process through a mobile terminal, but cannot realize full-industry tracking, resulting in lack of persuasiveness in data security and reliability.

[0004] In addition, the prior art has the following defects:

[0005] 1. The label structure is single, and the life cycle cannot be distinguished. The same label runs through the entire life cycle, and the system cannot identify the state switching of the individual from "breeding" to "transportation" to "sales". If the label is illegally replaced or removed in advance, the system cannot identify or prevent it;

[0006] 2. The data collection link is broken, and the responsibility anchor point is unclear. Once a problem occurs, it is difficult to locate which link and which personnel caused it, and it is impossible to form a truly traceable evidence chain;

[0007] 3. Consumers have no way to verify whether the data has been tampered with, and the platform also lacks "irrefutability";

[0008] 4. The label behavior is out of sync with the system state;

[0009] 5. The process information is not on the chain, the data trustworthiness is low, and most platform data links only form a traceable two-dimensional code in the product packaging link. The front-end data is manually imported, and does not have process verifiability and tamper resistance.

[0010] In order to solve the problems of poor full-industry supervision ability, inability to guarantee safety, inability to guarantee tamper resistance, label and system state disconnection, and single label structure in the field, the present application is made. SUMMARY

[0011] The present application aims to solve the existing problems, and provides a traceable management system based on a breeding industry service platform and a method thereof.

[0012] In order to overcome the deficiencies of the prior art, the present application adopts the following technical solutions:

[0013] A traceable management system based on a breeding industry service platform, comprising a server and a mobile data anchoring device, the traceable management system based on the breeding industry service platform further comprising a detachable traceable label module, a life cycle state management module, an event hash and anchor point verification module, and a blockchain intelligent verification module;

[0014] The detachable traceable label module is used to identify the identity of a breeding individual, the life cycle state, and trigger state change events in the disassembly behavior.

[0015] The mobile data anchoring device collects data of key nodes and forms anchor point records.

[0016] The life cycle state management module maintains the life cycle logical state diagram of each individual and checks whether all event uploads are compliant.

[0017] The event hash and anchor point verification module encapsulates all behavior nodes into structured hash events, compares and checks them with the current state diagram to form trusted anchor points.

[0018] The blockchain intelligent verification module performs contract-level verification on event hash and state path, and only after passing the verification can the event be stored on the blockchain to form a traceable chain. Optionally, the detachable traceable label module comprises a label structure unit, a state chip, a unique ID encoder, and a tamper detection unit, the label structure unit constructs a separable but stable connection physical label structure, so that the label is stably bound to the individual during the breeding stage, and after the individual is slaughtered, the label can be detached and part of the information is retained for product stage display and traceability; the state chip records the current life cycle state of the label and automatically switches the state bit when a physical behavior changes; the unique ID encoder assigns a unique identity number to each label to ensure that it is bound to the animal individual file in the database; the tamper detection unit is used to identify whether the label has been illegally disassembled or destructively removed, and if an illegal disassembly or destructive removal behavior occurs, the system should be able to identify and mark it as a risk event.

[0019] The label structure unit comprises a first label segment and a second label segment, the first label segment is bound to the animal individual during the breeding period, and the state chip and the unique ID encoder are integrated inside; the second label segment can be detached from the first label segment and retain traceable information.

[0020] Optionally, the life cycle state management module comprises a state path graph modeling unit, a state transition control unit, an illegal state identifier, and a risk recorder, the state path graph modeling unit is used to preset and maintain the life cycle logical state graph of the individual farmed animal, including the state nodes of each stage and the legal transition path thereof; the state transition control unit records the current life cycle state of the tag according to the event data uploaded by the current tag, and calls the state path graph at each event upload to perform legality comparison on the path relationship between the target state of the current event and the historical previous state thereof;

[0021] If the comparison result is illegal state jump, state rollback or path break, the illegal state identifier marks the event as illegal state change behavior; the risk recorder receives the illegal mark, generates an abnormal event risk report, and submits a structural abstract thereof to the blockchain to form a risk mark node for subsequent supervision evidence collection and consumer visualized traceability display;

[0022] If the comparison result is legal state transition, the state transition control unit synchronously updates the life cycle state of the current tag, and transfers the compliant event to the subsequent verification process to realize dynamic maintenance of the state and continuous compliance of the data.

[0023] Optionally, the mobile data anchoring device comprises a tag identification unit, a locator, a collection unit, a data storage, and a communication unit; the tag identification unit is used to read the current tag ID and the state data of the tag at the key life cycle node, the locator is used to record the geographic position coordinates and the timestamp when the event occurs, the collection unit is used to collect the environment, animal signs, and breeding indicators of the breeding process in the breeding area; the data storage is used to store the tag ID, state data, and breeding indicators obtained by identification and collection; and the communication unit uploads the data stored in the data storage to the event hash and anchor verification module, the life cycle state management module, and the blockchain intelligent verification module for subsequent event legality judgment and on-chain processing.

[0024] Optionally, the event hash and anchor verification module comprises an event structure construction unit, a hash generation unit, a double-point anchoring comparison unit, and an abnormal jump detection unit, the event structure construction unit generates an original event structure based on a specific format (tag ID, event type, operation time, position coordinates, and device number); the hash generation unit encrypts the generated original event structure by a hash algorithm to form an event hash; the double-point anchoring comparison unit performs consistency verification on the device ID, event type, time, and position field of the data uploaded by different devices for the same tag event to realize a double physical verification mechanism of the event source; and the abnormal jump detection unit determines whether there is illegal state switching or reverse behavior by reading the tag state graph path and the previous event time, and rejects the data on-chain if abnormal.

[0025] Optionally, the blockchain intelligent verification module comprises a contract scheduling unit, a life cycle rule engine, a logical judgment unit and a result feedback unit, the contract scheduling unit calls the corresponding pre-deployed smart contract according to the event type and its hash value, serving as the entrance of the verification process; the life cycle rule engine is used for maintaining the life cycle state graph of the animal or product within the contract, and judging whether the current event is a legal successor event of the current state; the logical judgment unit performs comprehensive judgment on event double-point anchoring matching, state compliance, disassembly legality and time sequence; the result feedback unit performs corresponding operations according to the judgment result: if the verification is passed, the event data is written into the blockchain and the life cycle state is updated; if it is not passed, an alarm is triggered and the event is recorded in the exception chain segment pool for subsequent review and accountability.

[0026] Optionally, the logical judgment unit comprises a path disturbance detection subunit, which calculates an ordered event mapping conflict disturbance index D based on the historical event mapping trajectory and the current event mapping position, and judges whether the current event causes conflict disturbance of the life cycle path according to the conflict index, and if the conflict disturbance index D exceeds the system set monitoring evaluation threshold Monitor, the current event is marked as an abnormal event and is rejected from being chained.

[0027] The application further provides a traceable management method based on a breeding industry service platform, which comprises the following steps:

[0028] S1, in the early stage of individual animal breeding, an operator reads the unique ID of the detachable traceable label through a mobile data anchoring device, and the system binds the ID with the profile of the individual in the platform database, and sets the initial state of the label life cycle as: breeding;

[0029] S2, at the key link in the individual life cycle, the mobile data anchoring device collects data for each operation event, including label ID, event type, collection time, geographic location, current state value and breeding environment index, and the mobile data anchoring device uploads the collected data to the event hash and anchor point verification module, the life cycle state management module and the blockchain intelligent verification module through the communication unit;

[0030] S3, the event hash and anchor point verification module constructs the collected data into an original event structure according to a preset format, performs a hash algorithm on the original event structure to form an event hash value, and simultaneously, the event hash and anchor point verification module transmits the hash value to the contract scheduling unit in the blockchain intelligent verification module, for subsequent life cycle compliance judgment and event legality verification process;

[0031] S4, the event hash and anchor verification module carries out consistency check on the event fields uploaded by two independent mobile data anchoring devices, and judges whether the current event has abnormal evolution in time or path structure in combination with the life cycle state diagram, and if abnormality is found, the event is marked as illegal;

[0032] S5, the blockchain intelligent verification module extracts the mapping coordinate sequence from the historical events that have been chained, calculates the disturbance index in combination with the mapping value of the current event; if the conflict disturbance index value is less than the preset monitoring threshold Monitor of the system, it is determined that the path evolution of the current event is legal; otherwise, it is regarded as a path conflict event, and the system refuses to enter the chain process, and triggers an alarm and risk record;

[0033] S6, the blockchain intelligent verification module calls the contract to verify whether the event conforms to the legal successor path of the current state;

[0034] S7, the blockchain intelligent verification module performs event chain writing and state updating operation according to the contract verification result;

[0035] When the event passes the life cycle compliance judgment, the double-point anchoring verification, the disassembly legality verification and the conflict disturbance index D judgment, the system writes the structured data of the event together with the hash value as a new block into the blockchain, and synchronously updates the life cycle state of the individual to the new state corresponding to the current event;

[0036] If the event does not pass any of the above determinations, the event is marked as an abnormal event, the abnormal type and the triggering reason are recorded, and the abnormal state is synchronized to the supervision end.

[0037] Optionally, the traceable management method further comprises:

[0038] The consumer can view the complete breeding information and risk prompt record of the breeding individual by scanning the second label segment.

[0039] Optionally, the traceable management method further comprises:

[0040] In step S3, the preset format includes: label ID, event type, operation time, geographic location, device number.

[0041] The beneficial effects obtained by the present application are:

[0042] 1. Through the cooperation of event hash and anchor verification module and blockchain smart verification module, the event structure can be encrypted and hashed before writing data to the chain, and the generated trusted event hash and state transition information are handed over to the pre-deployed smart contract to perform rule-level legality judgment, so as to ensure that all data written into the blockchain are subjected to three verifications of structure verification, physical anchoring and life cycle path checking, and to realize a trusted on-chain mechanism of unforgeable data structure, non-jumping state and non-reversible sequence, which significantly improves the security strength of the traceability system in terms of data integrity, process compliance and tamper-proofing capability;

[0043] 2. Through the cooperation of mobile data anchoring device and blockchain smart verification module, the collected geographic coordinates, state data and device information can be packaged to generate structured events and hashed, and written into the blockchain after the event legality is judged by the smart contract, so as to ensure that all anchoring behaviors have the compliance advantages of leaving traces on the chain, device identification and process verification, avoiding the phenomenon of fake, supplementary record or responsibility evasion in the middle link;

[0044] 3. Through the cooperation of life cycle state management module and event hash and anchor verification module, the collected event data can be structured and packaged as hash events, and based on the pre-set life cycle state atlas, the path legality comparison and time sequence checking are performed, and at the same time, the multi-device cross verification is realized by means of double-point anchoring mechanism, so as to ensure that all reported events have chain integrity in structure and comply with the life cycle compliance logic in state, which improves the credibility of event identification and the intelligent level of path checking, and prevents abnormal events from bypassing the chain into the database;

[0045] 4. Through the cooperation of life cycle state management module and event hash and anchor verification module, the collected event data can be structured and packaged as hash events, and based on the pre-set life cycle state atlas, the path legality comparison and time sequence checking are performed, and at the same time, the multi-device cross verification is realized by means of double-point anchoring mechanism, so as to ensure that all reported events have chain integrity in structure and comply with the life cycle compliance logic in state, which improves the credibility of event identification and the intelligent level of path checking, and prevents abnormal events from bypassing the chain into the database;

[0046] 5. Through the cooperation of the detachable traceability label module and the mobile data anchoring device, the label identity recognition, key node state reading and real-time geographic position collection can be completed in the actual operation site of the breeding animals, so that each behavior data is derived from the real physical event of the labeled individual, and at the same time, the anti-disassembly detection mechanism is used to ensure that illegal prying or fraudulent behavior can be identified and reported in real time, so as to ensure the physical authenticity, time and space accuracy and tamper resistance of event data, and to provide a trusted anchor point for subsequent verification. BRIEF DESCRIPTION OF DRAWINGS

[0047] The present application can be further understood from the following description in conjunction with the drawings. The components in the drawings are not necessarily drawn to scale, but emphasis is instead placed upon illustrating the principles of the embodiments. Like reference numerals designate like parts throughout the different views.

[0048] Figure 1 It is an overall block schematic diagram of the present application.

[0049] Figure 2 It is a block schematic diagram of the lifecycle status management module of the present application.

[0050] Figure 3 It is a block schematic diagram of the mobile data anchoring device workflow of the present application.

[0051] Figure 4 It is a structural schematic diagram of the detachable traceability label module of the present application. DETAILED DESCRIPTION

[0052] The following describes the embodiments of the present application through specific, concrete examples, and the advantages and effects of the present application can be understood by the person skilled in the art from the disclosure of the present specification. The present application can be implemented or applied through other different concrete examples, and each detail in the present specification can be modified and changed in various ways based on different viewpoints and applications without departing from the spirit of the present application. In addition, the drawings of the present application are only simple schematic illustrations and are not drawn according to the actual size, which is declared in advance. The following embodiments will further describe the related technical content of the present application in detail, but the disclosed content is not used to limit the protection scope of the present application.

[0053] Embodiment One: According to Figure 1 , Figure 2 , Figure 3 , Figure 4 The present embodiment provides a traceability management system based on a breeding industry service platform, which comprises a server and a mobile data anchoring device. The traceability management system based on the breeding industry service platform further comprises a detachable traceability label module, a lifecycle status management module, an event hash and anchor point verification module, and a blockchain intelligent verification module. The server is connected with the mobile data anchoring device, the lifecycle status management module, the event hash and anchor point verification module, and the blockchain intelligent verification module, and stores the intermediate data and process data of the mobile data anchoring device, the lifecycle status management module, the event hash and anchor point verification module, and the blockchain intelligent verification module in the database of the server.

[0054] The detachable traceability label module is used to identify the identity and lifecycle status of a breeding individual, and trigger a status change event in a disassembly behavior, which is used for data traceability starting point binding.

[0055] The mobile data anchoring device collects data of key nodes and forms anchor point records; in the embodiment, the key nodes include breeding behavior, pen transfer, transportation, and leaving the pen.

[0056] The life cycle state management module maintains a life cycle logical state diagram of each individual and checks whether all events uploaded are compliant;

[0057] The event hash and anchor point verification module encapsulates all behavior nodes into structured hash events, compares them with the current state diagram, and forms trusted anchors;

[0058] The blockchain intelligent verification module performs contract-level verification on event hash and state path, and only after passing the verification can the events be stored on the blockchain to form a traceability chain.

[0059] The traceable management system based on the breeding industry service platform further includes a central processor, which is in control connection with the server, the mobile data anchoring device, the life cycle state management module, the event hash and anchor point verification module, and the blockchain intelligent verification module, and performs centralized control on the mobile data anchoring device, the life cycle state management module, the event hash and anchor point verification module, and the blockchain intelligent verification module based on the central processor, so as to improve the whole-system supervision on the whole process of the breeding industry.

[0060] In the embodiment, the mobile data anchoring device is a portable intelligent terminal device with identity recognition, environment sensing, positioning uploading capability, which is used by breeding managers, transporters, quarantine officers, etc. in the whole process of breeding, for “physical confirmation + data collection + location record” of events at key nodes, and uploads event information to the platform through the network to form “anchor points”.

[0061] Optionally, the mobile data anchoring device includes a tag recognition unit, a locator, a collection unit, a data storage, and a communication unit; the tag recognition unit is used to read the current tag ID and the state data of the tag at the key life cycle node, the locator is used to record the geographic position coordinates and time stamp when the event occurs, the collection unit is used to collect the environment, animal signs, and breeding indicators of the feeding process in the breeding area; the data storage is used to store the tag ID, state data, and breeding indicators obtained by recognition and collection; and the communication unit uploads the data stored in the data storage to the event hash and anchor point verification module, the life cycle state management module, and the blockchain intelligent verification module, for subsequent event legality judgment and chain processing.

[0062] The tag recognition unit includes a radio frequency identification reader, a state decoder, and a data interface buffer;

[0063] The radio frequency identification reader is used to read the unique encoded information and current life cycle status value from the traceability tag. The status decoder is used to parse the status bit information stored in the tag chip into structured data. The data interface buffer is used to temporarily store the parsed tag ID and status value for recording by the data storage device or uploading by the communication unit to the event verification module for subsequent processing.

[0064] The tag recognition unit enables the tag to not only acquire its ID but also to resolve its status.

[0065] The data acquisition unit includes a temperature sensor, a humidity sensor, an ammonia concentration sensor, a noise sensor, and a data processor. The temperature sensor collects real-time temperature data of the breeding area, the humidity sensor collects real-time humidity data of the breeding area, the ammonia sensor collects the ammonia content in the air, reflecting the level of breeding hygiene; excessive ammonia is a signal of animal stress or fecal accumulation. The noise sensor collects noise data and provides emergency feedback, aggression, or external interference to the farmed animals. The data processor processes the data collected by the temperature sensor, humidity sensor, ammonia concentration sensor, and noise sensor. The processing includes, but is not limited to, the following operations: analog-to-digital conversion, filtering, standardization, and outputting structured breeding indicator data.

[0066] In this embodiment, the aquaculture indicators include, but are not limited to, the following: ambient temperature, ambient humidity, ammonia concentration, and ambient noise.

[0067] The communication unit includes a communicator, a multi-module address encoder, a data compressor and encoder, a network status detector, and an upload control logic unit. The communicator establishes a communication connection between the server and the data acquisition unit and the tag recognition unit to identify and collect the number of users, and performs data transmission. The multi-module address encoder packages and marks the data to be uploaded according to the target module (such as the event hash module, lifecycle module, etc.) to achieve distributed upload. The data compressor and encoder compresses (e.g., JSON structure) and encodes (e.g., Base64) the collected data to reduce communication overhead. The network status detector detects the current network connection status and selects the appropriate network (e.g., 4G priority, NB-IoT low-power backup). The upload control logic unit is used to manage the upload timing, failure retry mechanism, and breakpoint resume strategy and make adaptive adjustments.

[0068] When necessary, the communication unit may also include a security encryption subunit, which is used to encrypt key data fields during transmission to prevent intermediate nodes from tampering with or intercepting them.

[0069] Optionally, the detachable traceability tag module includes a tag structure unit, a status chip, a unique ID encoder, and an anti-tamper detection unit. The tag structure unit constructs a separable but stably connected physical tag structure, allowing the tag to be firmly bound to the individual during the breeding stage and to be disassembled after slaughter, retaining some information for product display and traceability. The status chip records the current life cycle state of the tag and automatically switches the status position when the physical behavior changes. The unique ID encoder assigns a unique identification number to each tag, ensuring that it is bound one-to-one with the individual animal files existing in the database and being raised. The anti-tamper detection unit is used to identify whether the tag has been illegally disassembled or destructively removed. If illegal disassembly or destructive removal occurs, the system should be able to identify and mark it as a risk event.

[0070] The tag structure unit includes a first tag segment (segment A) and a second tag segment (segment B). The first tag segment is bound to the individual animal during the breeding period and integrates a status chip and a unique ID encoder. The second tag segment can be disassembled from the first tag segment and retains traceability information for consumer scanning and visual traceability display during the product stage.

[0071] The tamper detection unit includes a circuit breakage identification circuit, a contact point detection chip, a structural spring break trigger, and an illegal state writing control unit.

[0072] The circuit break detection circuit is located in the connection area between the first tag segment and the second tag segment, and is used to detect whether there is a circuit break.

[0073] The contact point detection chip is used to sense whether the physical contacts of the tag are in complete contact;

[0074] If the spring breaks or the connecting conductor is disconnected during the disassembly process, the illegal status writing control unit will automatically update the status chip to an illegal status value (such as 0xFF) and upload the abnormal status to the monitoring platform system through the mobile data anchoring device, so as to effectively identify and mark the risks of illegal disassembly or destructive removal.

[0075] In this embodiment, the platform system specifically refers to a livestock industry supervision platform, which is a technical means well known to those skilled in the art, and therefore will not be described in detail in this implementation.

[0076] The circuit breaker identification circuit includes a conductive bridge structure between the first tag segment and the second tag segment, a status chip detection pin, a closed loop terminal, and an alarm trigger logic unit. The conductive bridge structure is made of low-resistance metal wire or copper foil spring, with one end connected to the status chip detection pin and the other end connected to the reference voltage or ground terminal, forming a closed detection loop.

[0077] When the tag's physical structure is in a normal connection state, the level of the detection pin is at a stable reference value;

[0078] If the tag is disassembled and the conductive bridge breaks, causing the circuit to be disconnected, the status chip detection pin will detect the level change, trigger the internal status update logic, and automatically write the tag life cycle status into the illegal identifier value.

[0079] The first tag segment includes a plastic shell, an embedded chip, and a fixing buckle. The plastic shell serves as the external protective structure of the tag and has a chip slot or encapsulation cavity inside to accommodate and fix the status chip and unique coding module. The chip is embedded inside the shell through a slot or encapsulation method and is connected to a conductive spring located inside the shell through its pins. The fixing buckle structure forms a plug-in or integrated connection with the shell and is used to install the tag on the ear or a designated area of ​​an animal. The plug-in and plug-out structure of the fixing buckle is linked with the conductive spring. When an illegal disassembly occurs, the spring is triggered to break, thereby causing the status chip to detect the open circuit and automatically update the tag's life cycle status.

[0080] In addition, the fixing buckle is generally a barbed ear tag insert or a rotating locking buckle, which cannot be pulled out in reverse after being inserted into the animal's ear; the fixing buckle structure and the shell are: an integral injection molding structure (direct molding) or a plug-in combination (such as inserting into a locking groove and locking).

[0081] The second label segment includes a QR code and a display area. The QR code identification layer displays the QR code information corresponding to the unique encoder, allowing consumers to scan and obtain platform traceability information. The information display area, located below or around the QR code identification layer, displays additional visual information such as product batch, origin, and production time. The QR code identification layer is fixed to the surface of the supporting shell of the second label segment by printing, laser engraving, or patching. The information display area and the QR code identification layer are integrally set in the display surface. The second label segment forms a detachable whole with the first label segment through structural connection points. These connection points employ a breakable bridging structure or a snap-fit ​​structure, allowing for removal and retention by the consumer. Even after removal, the QR code and display information are retained, ensuring the label has independent traceability capabilities throughout the product circulation process.

[0082] The alarm triggering logic unit includes a level change detector, a status update trigger, an alarm flag register, and an upload trigger initiator. When the status chip's detection pin detects a sudden change in level from normal to off, the level change detector generates an interrupt signal. The status update trigger responds to the interrupt signal by writing an illegal status value (such as 0xFF) into the status chip's storage area. The alarm flag register is set to "1" to indicate that the tag is currently in an illegal disassembly state. The upload trigger initiator generates an upload preparation flag, which automatically uploads the risk status to the platform for anomaly recording and monitoring warnings when the mobile data anchoring device reads the tag the next time.

[0083] like Figure 4 As shown, in the initial state, the circuit is on (closed), and the status chip's GPIO detects a "low level" or "stable voltage". If the user pries open segment B (the second tag segment), the bridge wire breaks, causing the circuit to disconnect. The status chip's IO pin detects a level change (such as changing from low level to floating or high impedance). The status chip performs an interrupt or polling judgment to confirm the illegal disassembly. The status chip immediately writes an "illegal status code (such as 0xFF)" for the mobile data anchoring device to read later. Once the mobile data anchoring device reads the tag again, it can identify it as an "illegal removal status" and upload it to form a risk event.

[0084] Among them, Figure 4 The data display area is used by consumers to scan and obtain traceability information, which is then bound to a unique code to display the traceability URL or status.

[0085] By combining detachable traceability tag modules with mobile data anchoring devices, tag identification, key node status reading, and real-time geolocation data collection can be completed at the actual operation site of farmed animals. This ensures that every piece of behavioral data originates from a real physical event of the tagged individual. In addition, the anti-tampering detection mechanism ensures that illegal prying or misuse can be identified and reported in a timely manner, thereby guaranteeing the physical authenticity, spatiotemporal accuracy, and anti-tampering capability of the event data, and providing a reliable anchor point for subsequent verification.

[0086] Optionally, the lifecycle state management module includes a state path graph modeling unit, a state transition control unit, an illegal state identifier, and a risk recorder. The state path graph modeling unit is used to pre-set and maintain the lifecycle logical state graph of individual farmed animals, including state nodes at each stage and their legal transition paths. The state transition control unit records the current lifecycle state of the tag based on the event data uploaded by the tag, and calls the state path graph each time an event is uploaded to perform a legality comparison of the path relationship between the current event target state and its historical previous states.

[0087] If the comparison result is an illegal state jump, state rollback, or path break, the illegal state identifier marks the event as an illegal state change behavior; the risk recorder receives the illegal mark, generates an abnormal event risk report, and submits its structural summary to the blockchain to form a risk mark node for subsequent regulatory evidence collection and consumer visual traceability display.

[0088] If the comparison result indicates a valid state transition, the state transition control unit synchronously updates the current tag's lifecycle state and transfers the compliance event to the subsequent verification process, thereby achieving dynamic state maintenance and continuous data compliance.

[0089] The state path graph modeling unit constructs a complete state path graph through the various state nodes of the animal's life cycle, records each life cycle state (and sets legal transition conditions for each state).

[0090] The various status nodes include: in breeding, ready for market, and slaughtered.

[0091] Using a pre-defined life cycle model, create a state transition diagram of an animal from birth to market weight.

[0092] For example: during breeding → transfer to pen → slaughter → sale, the legal connections between each state are set by rules to ensure that state changes conform to business logic.

[0093] The status transition control unit records the current lifecycle status of the tag and compares the path with the previous status based on the current status and upload time to confirm whether the transition is legal.

[0094] Specifically, the state transition control unit obtains the current tag's state information (e.g., retrieves the current state code from a state chip or database). Based on the uploaded event timestamp, it determines whether the current state matches historical states. It compares the current state with historical states to see if they conform to the state transition path diagram and verifies the time sequence and state validity. If a transition that does not conform to the rules or an abnormal time sequence is found, it is marked as an illegal event.

[0095] The illegal status identifier acquires the currently uploaded status information and compares it with the status path graph. It compares the current status with the previous legal status to determine if there is any illegal jump behavior (e.g., jumping directly from slaughter to sales). It checks if the timestamp of the uploaded event matches the status sequence to prevent time reversal (e.g., the slaughter event time is later than the slaughter date). If an illegal status is found, it is flagged and an alarm is triggered.

[0096] The risk recorder records and marks abnormal events. When an illegal state or illegal transaction is detected, a risk event record is generated and reported to the blockchain, generating an immutable risk marker. The specific process is as follows: upon detecting an illegal state or abnormal event, the event is marked as a risk event, and information such as the risk type, event details, and operator is recorded. This information is then uploaded to the blockchain smart verification module via a communication unit, generating a risk marker on the blockchain.

[0097] Among them, risk events will affect the traceability path of the farmed animal, and its historical issues can be clearly seen during subsequent review and tracing.

[0098] Optionally, the event hashing and anchor verification module includes an event structure construction unit, a hash generation unit, a two-point anchoring comparison unit, and an abnormal jump detection unit. The event structure construction unit generates the original event structure based on a specific format; the hash generation unit encrypts the generated original event structure using a hash algorithm to form an event hash; the two-point anchoring comparison unit performs consistency checks on data uploaded by different devices for the same tag event using device ID, event type, time, and location fields, realizing a dual physical verification mechanism for the event source; the abnormal jump detection unit reads the tag state graph path and the time of the previous event to determine whether there is an illegal state switch or reverse order behavior. If an anomaly is found, the data is rejected from being uploaded to the blockchain, ensuring the dual legality of the data stream's time sequence and logical order.

[0099] In this embodiment, the specific format includes: tag ID, event type, operation time, location coordinates, and device number;

[0100] The event structure construction unit formats the event according to the structure template corresponding to the specific format, outputs it as a standard time structure string, and hands it over to the hash generation unit.

[0101] The hash generation unit performs hash function processing (such as SHA-256) on the standardized event structure to generate a unique and irreversible event hash value. The hash value is calculated from a structure string formed by concatenating fields such as tag ID, event type, event time, device number, and geographic coordinates, ensuring that the event has uniqueness, tamper resistance, and privacy protection capabilities at the data layer. Even a slight change in any field will result in a completely different hash result, ensuring the credibility of event information during internal platform verification and blockchain writing.

[0102] For example, in aquaculture, at a certain point in time, the data is anchored to the following:

[0103] Tag ID: TAG-8721-A;

[0104] Event type: transfer (column transition);

[0105] Operation time: 2025-04-13T10:45:00;

[0106] Location coordinates: N34.2274, E118.3382;

[0107] Equipment number: MDA_0043;

[0108] Concatenate the above five fields in a fixed order and format to form a structure string (common form: key-value pairs + concatenation operator): TAG-8721-A|transfer|2025-04-13T10:45:00|34.2274,118.3382|MDA_0043;

[0109] The concatenated string is fed into a hash algorithm for processing. Taking SHA-256 as an example, the final output is: e3d0ab97b1345fc3c0d204aa07d24f5ea57f09e1607fd73b40b2d5f5bc58cd2e.

[0110] The dual-point anchoring comparison unit determines whether two different devices have uploaded the same event and performs a field consistency comparison. Specifically, the comparison process includes:

[0111] Check if another device has uploaded the same event type at the same time, location, and tag ID in the platform database; if a second upload record is found, extract the fields and compare them.

[0112] The comparison parameters include: whether the timestamp is within the allowable error range (e.g., ±2 minutes), whether the coordinate distance is within the geographical error tolerance (e.g., ≤100m), whether the event type, device ID, and tag ID are completely consistent, and if the comparison passes, it is marked as: two-point confirmation event;

[0113] If no two-point records are found or the fields are inconsistent, it is marked as a single-point event for subsequent determination of whether to downgrade the processing or reject it.

[0114] The system comprises an anomaly jump detection unit, a path comparison subunit, and a time sequence judgment subunit. The path comparison subunit determines whether the current event state is a legitimate successor to the previous state by comparing the current event state with the historical state information of the tag and a preset lifecycle state diagram. If a state jump or illegal transition is detected, the event is marked as an illegal state change. The time sequence judgment subunit compares the current event timestamp with the timestamp of the previous legitimate event. If the current time is earlier than the previous event time, or the deviation exceeds the system's tolerance threshold, it is considered a time reversal behavior. After determining the anomaly, this unit submits the event to the blockchain smart verification module and sends a signal to refuse to upload it to the chain, ensuring the consistency and legality of the event data in terms of time dimension and state logic.

[0115] Optionally, the blockchain smart verification module includes a contract scheduling unit, a lifecycle rule engine, a logic judgment unit, and a result feedback unit. The contract scheduling unit calls the corresponding pre-deployed smart contract based on the event type and its hash value, serving as the entry point for the verification process. The lifecycle rule engine is used to maintain the lifecycle state diagram of the animal or product within the contract and determine whether the current event is a legitimate successor event of the current state. The logic judgment unit performs a comprehensive judgment based on the event's two-point anchoring matching, state compliance, decomposition legality, and time sequence. The result feedback unit performs corresponding operations based on the judgment result: if the verification passes, the event data is written to the blockchain and the lifecycle state is updated; if it fails, an alarm is triggered and the event is recorded in the abnormal chain segment pool for subsequent review and accountability.

[0116] The contract scheduling unit is used to look up the corresponding smart contract address in the preset contract mapping table based on the structure fields (including event type and tag ID) of the currently uploaded event; then it calls the target contract (pre-set) and passes the event hash value and structure fields as verification parameters; inside the contract, the lifecycle rule engine determines whether the current event is a valid successor state in the tag state diagram, and the logic judgment unit completes multi-dimensional verification; after the contract is executed, the verification result, exception type, etc. are fed back to the result feedback unit, which decides whether to write to the chain or generate an exception flag.

[0117] The target contract is a smart contract pre-deployed on the blockchain network by the platform. Each event type corresponds to a unique contract address, which is mapped to the event type field through the contract registry. The contract address can be stored in the on-chain index area or in the contract scheduling configuration managed by the platform server. The contract scheduling unit automatically retrieves the contract address and initiates the call based on the event type field in the event structure, ensuring the consistency of the event verification process and the security of the contract call.

[0118] The lifecycle rule engine includes a lifecycle state graph database, a tag historical state extractor, a state jump comparison unit, a path graph tracker, and an exception code generator. The tag historical state extractor extracts the state and time information of the last on-chain event of the current tag from the platform or blockchain. The state jump comparison unit determines whether the current event state is a direct successor state of the previous state. When there are state branch paths or nested structures, the state graph tracker performs state path tracing to confirm the legality of the path. The exception code generator outputs a state legality flag based on the comparison result. If it is invalid, it generates an exception state code and corresponding explanation, which is passed to the logic judgment unit for the final on-chain decision.

[0119] Specifically: Tag history status extraction: Based on the current tag ID, retrieve the most recent legitimate event status and its timestamp from the blockchain or database; for example, the current tag is pig A1, and the last status was slaughter.

[0120] Next, extract fields from the current event structure and map them to lifecycle state nodes. For example, if the event type is slaughter, call the lifecycle state graph database and query the lifecycle graph of the current farmed animal's category, such as: farming → transfer to pen → slaughter → sale.

[0121] The state jump comparison unit checks whether the current state is a direct successor to the state of the most recent legal event; if so, it is compliant; otherwise, it is determined to be an abnormal state jump.

[0122] If complex state branches are involved (such as multiple categories, column exit process), the execution path graph is traversed: starting from the most recent valid event state, whether there is a path: most recent valid event state → ... → current state. If it exists but is not a direct successor, it is marked as: indirect jump; if the path does not exist, it is marked as: illegal transfer.

[0123] The logical judgment unit includes an anchor matching judge, a state validity receiver, a disassembled state judge, a time sequence comparator, a result aggregator, and an anomaly identifier encoder.

[0124] The status legitimacy receiver receives the event path compliance judgment result output by the lifecycle rule engine. If it is an illegal status jump or reversal, it is directly marked as an illegal event and the subsequent judgment process is stopped. If the status is compliant, the judgment process continues by the disassembly status judge reading the status code of the current tag to confirm whether the tag has been illegally disassembled.

[0125] If the status is an invalid code, the event is determined to be invalid, and the exception identifier encoder is triggered to mark it as a disassembly exception;

[0126] If the disassembly is compliant, the process continues to the time sequence comparator, which compares the current event timestamp with the time of the previous valid event. If the times are reversed, a time exception is returned.

[0127] If the time is valid, the device enters the anchor matching judge to confirm the consistency of multi-point uploads and passes the anchor matching status as a credibility level identifier to the result aggregator. Finally, the result aggregator comprehensively judges whether the event is valid based on the three strong constraint results. If all are valid, writing to the chain is allowed. If any one fails, the exception encoder generates the corresponding error code and submits it to the result feedback unit for processing.

[0128] The result feedback unit includes a write chain controller, a lifecycle state updater, an exception record manager, an alarm trigger, and a response feedback unit. When the logic judgment unit returns a verification pass signal, the write chain controller writes the event structure and hash value into the blockchain network, and at the same time, the lifecycle state updater updates the lifecycle state of the tag to the new state in the event.

[0129] When the judgment result is failure, the exception record manager encodes and packages the event and the reason for failure into an exception record and writes it into the exception chain pool. The alarm trigger then triggers a system-level warning to notify the regulator or platform administrator.

[0130] After the event is processed, the response feedback device sends the processing status back to the upper layer of the system, completing the event processing loop.

[0131] By cooperating with the event hash and anchor verification module and the blockchain smart verification module, the event structure can be encrypted and hashed before data is written to the blockchain, and then compared with dual-device anchoring. The generated trusted event hash and state transition information are handed over to the pre-deployed smart contract to perform rule-level legality judgment. This ensures that all data written to the blockchain undergoes triple verification of structure verification, physical anchoring, and lifecycle path verification, realizing a trusted on-chain mechanism that ensures that the data structure cannot be forged, the state cannot be skipped, and the order cannot be reversed. This significantly improves the security strength of the traceability system in terms of data integrity, process compliance, and anti-tampering capabilities.

[0132] Optionally, the logical judgment unit includes a path disturbance detection subunit. The path disturbance detection subunit calculates the ordered event mapping conflict disturbance index D based on the historical event mapping trajectory and the current event mapping position, and judges whether the current event causes conflict disturbance in the life cycle path according to the conflict index. If the conflict disturbance index D exceeds the monitoring evaluation threshold Monitor set by the system, it is marked as an abnormal event and its on-chain is rejected (i.e., the event data is written into the blockchain ledger).

[0133] The path disturbance detection subunit extracts key fields such as event type, device number, and event timestamp for each successfully uploaded historical event. The event timestamp uses the Unix standard representation (unit: seconds or milliseconds), for example, converting the event "2025-03-01 15:32:10" into the integer time value 1740816730. These fields are then concatenated into a structured string, such as:

[0134] "SALE"+"MDA03"+"1740816730"→ALEMDA031740816730;

[0135] Perform a hash compression operation (such as SHA-256) on the structure string, and extract different segments from the hash result to generate two-dimensional coordinate points:

[0136] Take the first 8 hexadecimal digits and convert them into the x component;

[0137] Take the last 8 hexadecimal digits and convert them into the y component;

[0138] Let this coordinate point be denoted as the event mapping value P. i =(x i ,y i ), used to construct historical path trajectories.

[0139] Simultaneously, the path disturbance detection subunit also performs the same structure concatenation and hash compression on the current uploaded event to obtain the current mapped coordinates C=(x c ,y c And insert C into the historical path sequence {P1,P2,...,P}. i-1};

[0140] The path disturbance detection subunit calculates the collision disturbance index D according to the following formula:

[0141] ;

[0142] In the formula, Δ dir The coefficient of change in the direction of time (1 for reverse order, 0 for forward order), Δ dist σ is the mapping distance between the current point and the previous point, σ is the historical average perturbation scale in the path, and α and β are the perturbation weighting factors set by the system.

[0143] Among them, the time direction transformation coefficient Δ dir Calculate according to the following formula:

[0144] ;

[0145] In the formula, T now T is the timestamp of the current event. prew The timestamp of the most recent legitimate event added to the blockchain;

[0146] The mapping distance Δ between the current point and the previous point dist Calculate according to the following formula:

[0147] ;

[0148] In the formula, (x1, y1) are the hash mapping coordinates of the previous event, and (x2, y2) are the hash mapping coordinates of the current event.

[0149] The historical average disturbance scale σ in the path is calculated according to the following formula:

[0150] ;

[0151] In the formula, n is the number of event points in the historical event sequence that have been verified by the system and uploaded to the chain and are bound to the current tag ID, (x i y i Let (x) be the hash mapping coordinates of the i-th event. i+1 y i+1 ) represents the hash mapping coordinates of the (i+1)th event.

[0152] The above formula forms a disturbance tolerance standard by statistically analyzing the historical path jump amplitude.

[0153] In addition, this embodiment also provides examples of the values ​​of the system-defined perturbation weight factors α and β:

[0154] 1) In the scenario of a column dedicated to farmed animals (frequent column switching, potential overlapping reports, and easy reversal of time sequence, requiring strict verification), then:

[0155] α = 0.7;

[0156] β=0.3;

[0157] 2) In the scenario of transporting animals out of the farm (where the geographical span is large and distance deviations are prone to errors; however, the time is relatively fixed), then:

[0158] α = 0.3;

[0159] β=0.7;

[0160] 3) In scenarios involving batch injection / labeling operations (operations occur simultaneously and at the same time, without excessive restrictions on the order), then:

[0161] α = 0.4;

[0162] β=0.6;

[0163] 4) In scenarios where routine inspections and reports are conducted (non-critical behaviors, with high tolerance for sequence and position), then:

[0164] α = 0.5;

[0165] β=0.5;

[0166] 5) In scenarios involving accountability and review (tracing incidents) (where time logic is particularly critical and the order must be strictly controlled), then:

[0167] α = 0.8;

[0168] β=0.2;

[0169] In summary, in this embodiment, it is necessary to select appropriate perturbation weight factors α and β based on the specific scenario and input them from the human-computer interaction interface. This is a technical means well known to those skilled in the art, and therefore will not be described in detail in this embodiment.

[0170] In this embodiment, the monitoring threshold "Monitor" is determined by the system based on actual conditions. Furthermore, this embodiment provides a specific value example:

[0171] 1) In the scenario of daily feeding in the breeding area (the behavior of animals in the same batch is concentrated in the location, the event time is stable, and the tolerance for path disturbance is low), the monitoring threshold is Monitor=0.5;

[0172] 2) In the scenario of transferring between pens (transferring between pens) (there is a small-scale path disturbance, some displacement should be allowed but the process should still be executed sequentially), the monitoring threshold Monitor=0.9;

[0173] 3) In the scenario of transporting livestock out of the farm (spanning a long geographical area, the path naturally has location disturbances), the monitoring threshold Monitor=1.5;

[0174] In this embodiment, the specific value of the monitoring threshold (Monitor) needs to be determined based on the specific usage scenario and input from the human-computer interaction interface. This is a technical method well known to those skilled in the art, and therefore will not be described in detail in this embodiment.

[0175] By collaborating with mobile data anchoring devices and blockchain smart verification modules, the collected geographic coordinates, status data, and device information can be packaged to generate structured events and hashed. After the legality of the events is judged by smart contracts, they are written into the blockchain, thereby ensuring that all anchoring behaviors have the compliance advantages of on-chain traceability, device recognition, and process verifiability, and avoiding fraud, supplementary recording, or evasion of responsibility in the intermediate links.

[0176] This invention also provides a traceable management method based on a livestock industry service platform, the traceable management method comprising the following steps:

[0177] S1. In the early stages of individual animal breeding, the operator reads the unique ID of the detachable traceability tag through a mobile data anchoring device. The system binds the ID to the individual's file in the platform database and sets the initial lifecycle status of the tag to: breeding.

[0178] S2. At key stages of an individual's life cycle, the mobile data anchoring device collects data for each operation event. The collected data includes tag ID, event type, collection time, geographical location, current status value, and aquaculture environment indicators. Simultaneously, the mobile data anchoring device uploads the collected data to the event hash and anchor point verification module, the life cycle status management module, and the blockchain smart verification module via the communication unit.

[0179] S3. The event hashing and anchor verification module constructs the collected data into an original event structure according to a preset format, performs a hash algorithm on the original event structure to form an event hash value, and transmits the hash value to the contract scheduling unit in the blockchain smart verification module for subsequent lifecycle compliance judgment and event legality verification process.

[0180] S4. The event hash and anchor verification module performs consistency verification on the event fields uploaded by the two independent mobile data anchoring devices, and determines whether the current event has abnormal evolution in time or path structure in combination with the life cycle state diagram. If an abnormality is found, the event is marked as illegal.

[0181] S5. The blockchain intelligent verification module extracts the mapping coordinate sequence of historical events that have been uploaded to the chain and calculates the disturbance index by combining it with the current event mapping value. If the conflict disturbance index value is less than the system's preset monitoring threshold, the current event path evolution is deemed legal. Otherwise, it is regarded as a path conflict event, and the system refuses to let it enter the chain process and triggers alarms and risk records.

[0182] S6. The blockchain smart verification module calls the contract to verify whether the event conforms to the legal subsequent path of the current state;

[0183] S7. The blockchain smart verification module performs event writing and state update operations based on the aforementioned contract verification results.

[0184] Once an event passes the lifecycle compliance judgment, two-point anchoring verification, decomposition legality verification, and conflict disturbance index determination, the system writes the structured data of the event along with the hash value into the blockchain as a new block, and simultaneously updates the lifecycle state of the individual to the new state corresponding to the current event.

[0185] If an event fails to pass any of the above criteria, it will be marked as an abnormal event, the abnormality type and triggering reason will be recorded, and the abnormal status will be synchronized to the regulatory end to trigger the platform's early warning mechanism for the regulatory authorities to review, handle, and hold accountable.

[0186] Optionally, the traceability management method further includes:

[0187] Consumers can scan the second tab of the QR code to view the complete breeding information and risk warning records of individual breeders.

[0188] Optional traceability management methods also include:

[0189] The preset format mentioned in step S3 includes: tag ID, event type, operation time, geographical location, and device number.

[0190] The blockchain referred to in this application is a data ledger system built on a distributed consensus mechanism. It records multiple behavioral event data sequentially through a block structure to form an immutable, traceable, and verifiable data chain. It also ensures the consistency and anti-counterfeiting capabilities of events among network nodes through chain encryption and consensus mechanisms.

[0191] In this application, the blockchain is used to record key event information of the farmed individual at each node of its life cycle, including but not limited to: tag status changes, anchor data, life cycle transition events, abnormal behavior markers, etc. The event structure's hash digest and its state path are submitted to a pre-deployed smart contract for legality verification. Only after the verification is passed can the data be written into the blockchain main ledger, forming a traceability data chain that can be jointly verified by consumers, regulators, and production enterprises.

[0192] The blockchain system can adopt a consortium blockchain, a permissioned blockchain, or a lightweight sidechain architecture built with edge nodes, supporting event interaction and state synchronization between on-chain data and off-chain smart platforms.

[0193] The on-chain operation refers to submitting the verified event data structure to the blockchain ledger and recording it as a chain node; the chain segment pool refers to the event chain segments that are marked as abnormal but retained, used for regulatory review rather than the part visible to consumers; smart contracts play the functional role of event verification and legality judgment in this architecture; the blockchain ensures that the data has the advantages of being tamper-proof, chronologically arranged, traceable in identity, and identifiable in responsibility.

[0194] Through the collaboration of the lifecycle state management module and the event hashing and anchor verification module, the collected event data can be structurally encapsulated into hash events. Based on the preset lifecycle state graph, path legality comparison and time sequence verification are performed. At the same time, the dual-point anchoring mechanism enables cross-verification by multiple devices, thereby ensuring that all reported events have chain integrity in structure and conform to lifecycle compliance logic in state. This improves the credibility of event identification and the intelligence level of path verification, and prevents abnormal events from being included in the database by bypassing the chain.

[0195] Example 2: This example should be understood as including all the features of any of the foregoing examples, and further improving upon them, according to... Figure 1 , Figure 2, Figure 3 ,as well as Figure 4 As shown, the traceability management system based on the aquaculture industry service platform also includes a platform service management module. The platform service management module opens a visual tracking platform to consumers and regulatory authorities, displaying the label lifecycle event chain, abnormal behavior, and the path of responsible persons.

[0196] The platform service management module generates an individual lifecycle graph, which displays the event chain, state evolution, responsible personnel, and equipment experienced by the tag.

[0197] The platform service management module includes a lifecycle graph builder, an abnormal event layer overlay, a responsibility chain path aggregator, a regulatory interface server, a consumer visualization display terminal, and a risk push service unit.

[0198] The lifecycle graph builder parses the historical events and state change information of each individual tag from blockchain data and constructs an interactive lifecycle traceability graph in a graph structure.

[0199] The abnormal event layer overlay tool visually overlays abnormal events (such as state jumps, illegal dismantling, and reverse behavior) recorded in the blockchain onto the graph using icons, colors, path weighting, and other methods.

[0200] The responsibility chain path aggregator is used to extract the information of the responsible parties for the behavior based on the operating device ID and personnel account in the event structure, and to construct the behavior responsibility path in the graph;

[0201] The regulatory interface server is used to provide auditors with functions such as exporting tag maps, downloading historical anomalies, and tracing accountability.

[0202] The consumer display terminal combines the label QR code recognition results to show users a complete life cycle status map of an individual, risk markers, and traceability paths of responsible personnel, ensuring that the source of food products is transparent and visible;

[0203] The risk push service supports setting subscription conditions for abnormal behavior events and pushing high-risk behavior event warnings to responsible personnel, so as to make management responsibility traceable and event information verifiable.

[0204] The platform service management module further includes a responsibility path deviation analysis unit. This unit constructs the deviation Ri between each responsible person's participation path in the node's individual lifecycle map and the average behavioral path of that node group.

[0205] ;

[0206] In the formula, L i P represents the number of lifecycle event nodes in which the responsible party participated.ij Let P be the mapped coordinates of the responsible person's operation event in the j-th event node. j Let d(P) be the average mapping position of all responsible persons' actions in the j-th node. ij ,P j Let be the geometric deviation between the responsible person and the average behavioral position in the j-th node, and its value is calculated according to the following formula:

[0207] ;

[0208] When R i When the behavior exceeds the system's set threshold, the platform will mark the responsible person's behavior as a deviation risk for priority review by regulators.

[0209] The system sets the threshold SETing according to the actual situation and inputs it from the human-machine interface. This is a technical means well known to those skilled in the art, and therefore will not be described in detail in this embodiment.

[0210] In this embodiment, an example of the value of the system setting threshold SETing is provided, specifically:

[0211] 1) In the breeding stage (feeding and transfer) scenario (all operations occur within a fixed area with little spatial variation and the smaller the deviation, the better), the system sets the threshold SETing=5;

[0212] 2) In the scenario of outbound transportation (where the geographical coordinates of the transportation span a large range, the routes are scattered, and the tolerance is increased), the system sets the threshold SETing=15;

[0213] 3) In the scenario of accountability audit (when conducting targeted investigations, it is necessary to accurately identify the suspected responsible persons), the system sets the threshold SETing=3;

[0214] 4) In the scenario of epidemic prevention and control inspection (the same group of people should have a consistent behavior path in epidemic prevention and control actions), the system sets the threshold SETing=6;

[0215] In summary, the specific system setting threshold SETing needs to be combined with the specific use scenario to select an appropriate value and input from the user interface. This is a technical method well known to those skilled in the art, and therefore will not be described in detail in this embodiment.

[0216] Through the collaboration of the event hashing and anchor verification module with the platform service management module, each verified anchored event is encapsulated as a chain of data nodes and automatically added to the lifecycle graph. When displaying the graph, the system can simultaneously show the event structure summary, location anchoring records, and device information, thereby providing consumers and regulators with a more structured, reliable, and chain-like method for tracking tagged events.

[0217] The content disclosed above is only a preferred and feasible embodiment of the present invention, and is not intended to limit the scope of protection of the present invention. Therefore, all equivalent technical changes made based on the content of the present invention specification and drawings are included within the scope of protection of the present invention. Furthermore, the elements therein can be updated as technology develops.

Claims

1. A traceable management system based on a breeding industry service platform, the traceable management system based on the breeding industry service platform comprising a server and a mobile data anchoring device, characterized in that, The traceable management system based on the breeding industry service platform further comprises a detachable traceable label module, a life cycle state management module, an event hash and anchor point verification module, and a blockchain intelligent verification module. The detachable traceable label module is used for identifying the individual identity and life cycle state of breeding, and triggering state change events in the disassembly behavior. The mobile data anchoring device collects data of key nodes and forms anchor point records. The life cycle state management module maintains the life cycle logical state diagram of each individual and verifies whether all event uploads are compliant. The event hash and anchor point verification module encapsulates all behavior nodes into structured hash events, compares them with the current state diagram, and forms trusted anchors. The blockchain intelligent verification module performs contract-level verification on event hash and state path, and only after passing the verification can the event data be stored on the blockchain to form a traceable chain. The blockchain intelligent verification module comprises a contract scheduling unit, a life cycle rule engine, a logical judgment unit, and a result feedback unit. The contract scheduling unit calls the corresponding pre-deployed smart contract according to the event type and its hash value, serving as the entrance of the verification process. The life cycle rule engine is used for maintaining the life cycle state diagram of animals or products within the contract and judging whether the current event is a legal successor event of the current state. The logical judgment unit performs comprehensive judgment on event double-point anchoring matching, state compliance, disassembly legality, and time sequence. The result feedback unit performs corresponding operations according to the judgment result: if the verification is passed, the event data is written into the blockchain and the life cycle state is updated; if the verification is not passed, an alarm is triggered and the event is recorded in the exception chain segment pool for subsequent review and accountability. The logical judgment unit comprises a path disturbance detection subunit. Based on the historical event mapping trajectory and the current event mapping position, the path disturbance detection subunit calculates an ordered event mapping conflict disturbance index D, and judges whether the current event causes a conflict disturbance of the life cycle path according to the conflict index. If the conflict disturbance index D exceeds the system set monitoring evaluation threshold Monitor, the current event is marked as an abnormal event and is rejected from being uploaded to the blockchain.

2. The traceability management system based on the farming industry service platform according to claim 1, characterized in that, The detachable traceable label module comprises a label structure unit, a state chip, a unique ID encoder, and a tamper detection unit. The label structure unit constructs a separable but stable connection physical label structure, so that the label is stably bound to the individual during the breeding stage, and can be detached after the individual is slaughtered and part of the information is retained for product stage display and traceability. The state chip records the current life cycle state of the label and automatically switches the state bit when a physical behavior changes. The unique ID encoder assigns a unique identity number to each label, ensuring that it is bound to the individual file of the animal in the database. The tamper detection unit is used to identify whether the label is illegally disassembled or destructively removed. If illegal disassembly or destructive removal occurs, the system should be able to identify and mark it as a risk event. The tag structure unit comprises a first tag segment and a second tag segment, the first tag segment is bound to an individual animal during the breeding period, and is internally integrated with a state chip and a unique ID encoder; the second tag segment can be detached from the first tag segment and retains traceability information.

3. The traceability management system based on the farming industry service platform according to claim 2, wherein, The life cycle state management module comprises a state path graph modeling unit, a state transition control unit, an illegal state identifier, and a risk recorder, the state path graph modeling unit is used for presetting and maintaining a life cycle logical state graph of the individual animal, including state nodes of each stage and their legal transition paths; the state transition control unit records the current life cycle state of the tag according to event data uploaded by the tag, and calls the state path graph to perform a legality comparison between a target state of the current event and a historical preceding state of the target state at each event upload; If the comparison result is illegal state jump, state rollback, or path break, the illegal state identifier marks the event as illegal state change behavior; the risk recorder receives the illegal mark, generates an abnormal event risk report, and submits a structural abstract of the report to the blockchain to form a risk mark node, which is used for subsequent supervision evidence collection and consumer visualized traceability display; If the comparison result is legal state transition, the state transition control unit synchronously updates the life cycle state of the current tag, and transfers the compliant event to a subsequent verification process, so as to realize dynamic state maintenance and continuous data compliance.

4. The traceability management system based on the aquaculture industry service platform according to any one of claims 1 or 3, characterized in that, The mobile data anchoring device comprises a tag identification unit, a locator, a collection unit, a data storage, and a communication unit; the tag identification unit is used for reading a current tag ID and state data of the tag at key life cycle nodes, the locator is used for recording geographical position coordinates and a timestamp when the event occurs, the collection unit is used for collecting environment, animal signs, and breeding indicators of a breeding process in a breeding area; the data storage is used for storing the tag ID, the state data, and the breeding indicators obtained by identification and collection; and the communication unit uploads data stored in the data storage to the event hash and anchor verification module, the life cycle state management module, and the blockchain intelligent verification module, for subsequent event legality judgment and on-chain processing.

5. The traceability management system based on the aquaculture industry service platform according to claim 4, wherein, The event hash and anchor verification module comprises an event structure construction unit, a hash generation unit, a double-point anchoring comparison unit, and an abnormal jump detection unit, the event structure construction unit generates an original event structure based on a specific format; the hash generation unit encrypts the generated original event structure by using a hash algorithm to form an event hash; the double-point anchoring comparison unit performs consistency verification on device IDs, event types, times, and positions of data uploaded by different devices for the same tag event, so as to realize a double-physical verification mechanism of an event source; the abnormal jump detection unit determines whether there is illegal state switching or reverse behavior by reading a tag state graph path and a previous event time, and rejects data on-chain if there is an abnormality.

6. A traceable management method based on a breeding industry service platform, applied to the traceable management system based on the breeding industry service platform in claim 5, characterized in that, The traceable management method comprises the following steps: S1, in the early stage of individual animal breeding, the unique ID of the detachable traceable tag is read by the operator through the mobile data anchoring device, the system binds the ID with the profile of the individual in the platform database, and sets the initial state of the life cycle of the tag as: breeding; S2, in the key link of the individual life cycle, the mobile data anchoring device collects data for each operation event, including tag ID, event type, collection time, geographic location, current state value and breeding environment index, at the same time, the mobile data anchoring device uploads the collected data to the event hash and anchor verification module, the life cycle state management module and the block chain intelligent verification module through the communication unit; S3, the event hash and anchor verification module constructs the original event structure according to the preset format, executes the hash algorithm on the original event structure, forms the event hash value, and at the same time, the event hash and anchor verification module transmits the hash value to the contract scheduling unit in the block chain intelligent verification module, which is used for subsequent life cycle compliance judgment and event legality verification process; S4, the event hash and anchor verification module performs consistency check on the event fields uploaded by two independent mobile data anchoring devices, and judges whether the current event exists abnormal evolution in time or path structure according to the life cycle state diagram, if abnormal, the event is marked as illegal; S5, the block chain intelligent verification module extracts the mapping coordinate sequence from the historical events in the chain, calculates the disturbance index combined with the current event mapping value; if the conflict disturbance index value is less than the system preset monitoring threshold Monitor, it is determined that the current event path evolution is legal; otherwise, it is regarded as a path conflict event, and the system refuses to enter the chain process, and triggers alarm and risk record; S6, the block chain intelligent verification module calls the contract to verify whether the event conforms to the legal successor path of the current state; S7, the block chain intelligent verification module performs event writing chain and state updating operation according to the contract verification result; When the event passes the life cycle compliance judgment, the double point anchoring verification, the disassembly legality verification and the conflict disturbance index D judgment, the system writes the structured data of the event together with the hash value as a new block into the block chain, and synchronously updates the life cycle state of the individual to the new state corresponding to the current event; If the event does not pass any of the above determinations, the event is marked as an abnormal event, the abnormal type and the triggering reason are recorded, and the abnormal state is synchronized to the supervision end.

7. The traceable management method based on the aquaculture industry service platform according to claim 6, wherein, The traceable management method further comprises: Consumers can view the complete breeding information and risk prompt record of the breeding individual by scanning the second label segment.

8. The traceable management method based on the aquaculture industry service platform according to claim 7, characterized in that, The traceable management method further comprises: In step S3, the preset format includes: tag ID, event type, operation time, geographic location, device number.

Images