A method and system for product life cycle control and supervision based on NFC and RFID double tag forced interlocking
By using a dual-tag mandatory interlocking mechanism of NFC and RFID, the problems of bypassing product status changes and data tampering in existing technologies are solved, enabling strict supervision and accountability throughout the product lifecycle, and providing tamper-proof status transition records and emergency exemption mechanisms.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- 殷跃勇
- Filing Date
- 2026-05-12
- Publication Date
- 2026-07-31
AI Technical Summary
Existing product traceability systems based on single RFID tags cannot enforce changes in product status. Process nodes can be bypassed or falsified, leading to distorted audit data and difficulty in tracing responsibility. NFC technology also lacks batch management capabilities.
The system employs a dual-tag mandatory interlocking mechanism of NFC and RFID. It uses RFID tags to perform batch detection of product presence and combines NFC tag authorization verification to achieve single-point confirmation of product lifecycle status changes. Status transitions must simultaneously meet both RFID detection and NFC confirmation conditions. Operation records are stored in an immutable hash chain.
It ensures that the product lifecycle state transition process is unbypassable and tamper-proof, detects and blocks abnormal scenarios, ensures that the responsible parties are clearly traceable, and provides a four-level authorization system and an emergency exemption mechanism to guarantee system integrity.
Smart Images
Figure CN122491672A_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the fields of Internet of Things (IoT) and intelligent supply chain management, and in particular to a method and system for product lifecycle control and supervision based on mandatory interlocking of NFC and RFID dual tags. Background Technology
[0002] Existing product traceability systems based on single RFID tags are mainly used for batch identification of product status and inventory management. They rely on manual operation to trigger status changes, and process nodes can be skipped or forged. Enforcement at the technical level is impossible, and historical operation records can be modified by personnel with database access, leading to distorted audit data and difficulties in tracing responsibility. NFC technology supports single-point interaction but cannot manage batches, while RFID technology supports batch identification but lacks user-level confirmation capabilities. Simply combining the two does not solve the above problems; the key issue is the lack of a technical interlocking mechanism between them. Any single tag can independently complete status changes, and the process can still be bypassed. Therefore, this application is proposed. Summary of the Invention
[0003] The purpose of this application is to overcome the shortcomings and deficiencies of the existing technology and to propose a method and system for product lifecycle control and supervision based on mandatory interlocking of NFC and RFID dual tags. The method includes the following steps: Lifecycle state machine definition: In a cloud management system, the lifecycle of a target product is defined as a finite set of states, which at least include production, outbound, inbound, use, and scrapping; Unique ID code generation: In production mode, a unique ID code for each target product is generated based on its original identification information; Dual-tag initialization binding: The unique ID code of each target product is written into the RFID tag and NFC tag fixed on the target product respectively, and recorded into the cloud database. The unique ID code cannot be changed after being recorded. The RFID tag is set to read-only state after being written, and is used for batch detection of product existence status. The NFC tag is set to permission verification interaction state, and is used for single-point confirmation of product life cycle status changes. State transition execution and immutable recording: The transition between states can only be triggered if the following three conditions are met simultaneously: Condition 1, the RFID reader detects the existence of the target product's unique ID code in the current state; Condition 2, within a preset time, an authorized operator completes NFC tag permission verification and detection of the target product through the NFC reader and executes the state change operation; Condition 3, the unique ID codes in the detected RFID tags and NFC tags are consistent with the records in the cloud database; only after the conditions are met can the system execute the state transition and record the operator information and transition state information immutably in the cloud database using an immutable storage mechanism; the state transition is irreversible, and the completed state change cannot be rolled back; Anomaly detection and forced blocking: The cloud management system detects abnormal states in real time. Once any abnormal condition is triggered, the cloud management system can forcibly block the state transition process and can simultaneously record abnormal events and / or trigger alarms and / or freeze operator permissions.
[0004] Furthermore, the ID encoding structure in the unique ID encoding generation step is a segmented encoding, specifically including: The first segment, the product origin code, is used to identify the manufacturer or importer of the target product. The second part, the product category code, is used to identify the category of the target product; The third segment, the batch code, is used to identify the production batch and date of the target product; The fourth segment is the serial number, which is used to identify a unique serial number of a single target product within the same production batch; The fifth segment is the checksum, used to verify the integrity of the encoding. The unique ID code cannot be reused, modified, or transferred within the cloud management system.
[0005] Furthermore, the preset time can be configured by the system administrator according to the business scenario, with a default value not exceeding 60 seconds.
[0006] Furthermore, the NFC tag permission verification in the state transition execution and tamper-proof recording steps adopts a hierarchical authorization mechanism, with permission levels divided as follows: Level L1 can only perform operations in the "use" and "scrap" states; Level L2 can perform "inbound" and "outbound" status operations; Level 3, capable of performing all state operations; Level 4, with read-only access to all data and mandatory verification permissions; Different permission levels are independent of each other. Lower-level permissions cannot perform operations with higher-level permissions. Unauthorized operations will be forcibly rejected and recorded by the system.
[0007] Furthermore, it also includes an emergency exemption mechanism. When an L1 user initiates an emergency use request, a state transition can be allowed even if the NFC tag permission verification is not met, and this state transition will be marked as an exemption event, provided that the following conditions are met simultaneously: Condition 1: Confirm the presence of the target product through RFID tag detection; Condition 2: The operator enters an emergency authorization code; Condition 3: The system automatically records the exemption event and requests supplementary NFC tag permission verification within the preset exemption time window; The preset exemption time window can be configured by the system administrator according to the business scenario. The default value is no more than 24 hours. The exemption event will be automatically pushed to L3 level user for review. Exemption events that have not been supplemented with NFC tag permission verification within the time limit will be automatically marked as abnormal events pending verification.
[0008] Furthermore, the operator information and transfer status information include a unique ID code, pre-transfer status, post-transfer status, operation timestamp, operator identity identifier, geographical location information, RFID reading raw data, and NFC verification raw data. The tamper-proof storage mechanism includes storing the operator information and transfer status information using a hash chain storage structure.
[0009] Furthermore, the abnormal conditions include: Abnormal condition one: The target product is detected by the RFID tag, but the corresponding NFC tag permission verification and status change operation are not completed within the preset time. Abnormal condition 2: The NFC tag detects a verification operation in the current state, but the RFID tag does not detect the target product corresponding to the current state. Thirdly, the unique ID code of the NFC or RFID tag does not match the cloud record. Abnormal condition four: The same unique ID code is used for duplicate confirmation operations under the same state; Abnormal condition five: The authorized operator's permission level does not match the permission level required for the current state transition.
[0010] Furthermore, the detection method for the third abnormal condition includes extracting the unique ID code stored in the NFC tag and RFID tag in real time each time the NFC tag permission verification operation occurs, and comparing it with the unique ID code recorded in the cloud; if the unique ID code of the NFC tag or RFID tag is inconsistent with the cloud record, it is determined that the product tag is counterfeited, replaced or damaged.
[0011] Furthermore, it also includes a batch inventory function, which involves scanning the RFID tags of target products in any state and automatically comparing the scan results with the records of target products in the corresponding state in the cloud database, and generating an inventory discrepancy report. The inventory discrepancy report marks the following three types of abnormal products: Type 1: The product is recorded in the cloud database but not scanned by the RFID tag, indicating that the target product is suspected to be lost; Type 2: The RFID tag is scanned, but the cloud database records that the target product is not in this state, indicating that the target product is suspected of being misplaced or abnormally transferred; Type 3: If an RFID tag is scanned but there is no corresponding record in the cloud database, it indicates that the target product is suspected to be an illegal product. The batch inventory mode does not trigger the state transition of the target product and is only used for inventory verification. The inventory discrepancy report is automatically uploaded to the cloud and saved as an audit record.
[0012] This application also includes a system for product lifecycle control and monitoring based on NFC and RFID dual-tag forced interlocking, the system being able to perform any of the methods described above.
[0013] The beneficial effects of this application include: 1. This application can ensure that the relevant process nodes in the various states of the target product's life cycle are unbypassable; 2. This application can ensure the immutability of relevant process nodes during the transition of each state in the life cycle of the target product; 3. This application can detect and forcibly block abnormal scenarios such as illegal products, counterfeit labels, and unauthorized circulation.
[0014] 4. This application establishes a four-level authorization system, which strictly isolates the authority of manufacturers, distributors, end users, and regulatory agencies, and ensures that the responsible parties are clearly traceable.
[0015] 5. This application balances flexibility and rigor. The emergency exemption mechanism ensures availability in emergency scenarios while maintaining system integrity through mandatory supplementary confirmation and automatic marking mechanisms. Attached Figure Description
[0016] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.
[0017] Figure 1Schematic diagram of the target product state transition detection conditions in this invention Figure 2 Schematic diagram of abnormal state detection and handling during target product state transition in this invention. Detailed Implementation
[0018] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the inventive content and technical solutions of this application will be clearly and completely described below in conjunction with the embodiments of this application. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.
[0019] The terminology used in this application is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. The singular forms “a,” “the,” and “the” used in this application and the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise. It should also be understood that the term “and / or” as used herein refers to and includes any and all possible combinations of one or more of the associated listed items.
[0020] This application protects a method and system for product lifecycle control and supervision based on mandatory interlocking of NFC and RFID dual tags. The unique product ID is simultaneously written into two physically independent tag carriers: the RFID tag is a read-only tag used for detecting the presence or absence of the target product; the NFC tag is an access control tag used for confirming state changes. The unique ID is entered into a cloud database and cannot be changed after entry. The product lifecycle is defined as a finite set of states, and state transitions require the simultaneous fulfillment of two independent conditions: RFID detection and NFC confirmation. Neither condition can be omitted, and no single condition can independently trigger a state transition at the system's technical level.
[0021] In one embodiment of this application, the lifecycle of a target product is defined in the management system as five states: production, outbound, inbound, use, and disposal. The manufacturer of the target product is a medical device manufacturer. For a batch of products produced by the medical device manufacturer, the system generates a unique ID code for each product based on the original identification information of these products, for example: 1001-1002-2604261-0001-07. Here, 1001 is the enterprise code, used to identify the specific medical device manufacturer; 1002 is the product category code corresponding to the target product, used to identify the product classification; 2604261 is the production batch code corresponding to the target product, used to identify the production batch and date of the target product; 0001 is the unique serial number corresponding to the target product, used to identify the unique serial number of a single target product within the same production batch; and 07 is a check code, used to verify the integrity of the code. Through this coding setting, each product in the batch can be assigned a unique number, thereby achieving precise control and supervision of each product throughout its lifecycle. An RFID tag and an NFC tag are affixed to each target product or its outer packaging. A unique ID code corresponding to each target product is written into the RFID tag and NFC tag respectively via an NFC and RFID reader / writer, and recorded in a cloud database. This unique ID code cannot be changed after being recorded. The RFID tag is set to read-only for batch automatic detection of product presence / absence, and the NFC tag is set to an authorization verification interaction state for single-point confirmation of product lifecycle status changes. After the medical device manufacturer produces the target product and completes the above operations, the target product's status is recorded as "in production".
[0022] Upstream entities, such as medical device manufacturers, can be granted Level 3 permissions, enabling them to perform all status confirmations and supplemental authorizations for abnormal situations. Downstream entities, such as distributors, retailers, and hospitals, can be granted Level 2 permissions, enabling them to perform "inbound" and "outbound" status confirmations. Product operators, such as medical personnel, can be granted Level 1 permissions, enabling them to perform only "use" and "scrap" status confirmations. Regulatory entities, such as administrative agencies, can be granted Level 4 permissions, possessing read-only access to all data and the authority to conduct mandatory verifications.
[0023] When the medical device manufacturer ships goods to its regional distributor, the manufacturer's operators must simultaneously complete the following: RFID reader scan to confirm product presence; NFC device reads the tag to complete L3 level access verification and executes the "outbound" operation. If both conditions are met simultaneously within a preset time (e.g., 60 seconds), and the unique ID codes in both the RFID and NFC tags detected by the system match the records in the cloud database, the system execution status shifts from "production" to "outbound." The system records the target product's unique ID code, its status before and after the transfer, the operation timestamp, operator identification, geographical location information, original RFID reading data, and original NFC verification data. This information is stored using a hash chain storage structure, and the immutable records are stored in the cloud database, generating an immutable record. Any tampering with historical records will invalidate the hash values of all subsequent records. At this point, the system indicates that the target product is no longer in the medical device manufacturer's warehouse. Furthermore, the medical device manufacturer can also select and record the distributor to whom the target product will be shipped in the system.
[0024] When the distributor receives the goods, the distributor's operators must simultaneously complete the following: RFID reader scan to confirm the product's presence; NFC device reads the tag to complete L2-level access verification and executes the "warehousing" operation. If both conditions are met simultaneously within a preset time (e.g., 60 seconds), and the unique ID codes in both the RFID and NFC tags detected by the system match the records in the cloud database, the system execution status changes from "outbound" to "inbound." The system records the target product's unique ID code, its status before and after the transfer, the operation timestamp, operator identification, geographical location information, original RFID reading data, and original NFC verification data. This information is stored using a hash chain storage structure, and the immutable records are stored in the cloud database, generating an immutable record. Any alteration of the historical record will invalidate the hash values of all subsequent records. At this point, the system indicates that the target product belongs to this specific distributor.
[0025] When the distributor ships goods to the hospital, the distributor's operators must simultaneously complete the following: RFID reader scan to confirm the product's presence; NFC device reads the tag to complete L2-level access verification and executes the "outbound" operation. If both conditions are met simultaneously within a preset time (e.g., 60 seconds), and the unique ID codes in both the RFID and NFC tags detected by the system match the records in the cloud database, the system execution status changes from "inbound" to "outbound." The system records the target product's unique ID code, its status before and after the transfer, the operation timestamp, operator identification, geographical location information, original RFID reading data, and original NFC verification data. This information is stored using a hash chain storage structure, and the immutable records are stored in the cloud database, generating an immutable record. Any tampering with the historical record will invalidate the hash values of all subsequent records. At this point, the system indicates that the target product is no longer in the distributor's warehouse. Furthermore, the distributor can also select and record the hospital to which the target product is to be shipped in the system.
[0026] When the hospital receives the goods, its operators must simultaneously complete the following: RFID reader scan to confirm the product's presence; NFC device reads the tag to complete L2-level access verification and executes the "warehousing" operation. If both conditions are met simultaneously within a preset time (e.g., 60 seconds), and the unique ID codes in both the RFID and NFC tags detected by the system match the records in the cloud database, the system's execution status changes from "outbound" to "inbound." The system records the target product's unique ID code, its status before and after the transfer, the operation timestamp, operator identification, geographical location information, original RFID reading data, and original NFC verification data. This information is stored using a hash chain storage structure, and the immutable records are uploaded to the cloud database, generating an immutable record. Any alteration of the historical record will invalidate the hash values of all subsequent records. At this point, the system indicates that the target product belongs to this specific hospital.
[0027] When hospital medical staff use the product, the operator must simultaneously complete the following: RFID reader scan to confirm the product's presence; NFC device reads the tag to complete L1 level permission verification and execute the "use" operation. If both conditions are met simultaneously within a preset time (e.g., 60 seconds), and the unique ID codes in both the RFID and NFC tags match the records in the cloud database, the system's execution status changes from "inventory" to "use." The system records the target product's unique ID code, its state before and after the transfer, the operation timestamp, operator identification, geographical location information, original RFID reading data, and original NFC verification data. This information is stored using a hash chain storage structure, ensuring immutability in the cloud database and generating an unalterable record. Any alteration of the historical record will invalidate the hash values of all subsequent records. At this point, the system indicates that the target product has been used. Furthermore, the system can also record the target product's usage time, user identity, and patient-related information.
[0028] When hospital medical staff need to dispose of products, the operator must simultaneously complete the following: RFID reader scan to confirm the product's existence; NFC device reads the tag to complete L1 level access verification and executes the "disposal" operation. If both conditions are met simultaneously within a preset time (e.g., 60 seconds), and the unique ID codes in both the RFID and NFC tags match the records in the cloud database, the system's execution status changes from "inbound" to "disposal." The system records the target product's unique ID code, its state before and after the transfer, the operation timestamp, operator identification, geographical location information, original RFID reading data, and original NFC verification data. This information is stored using a hash chain storage structure, ensuring immutability. Any alteration to the historical record will invalidate the hash values of all subsequent records. At this point, the system marks the target product as disposed of.
[0029] The following are handling scenarios for several abnormal situations: If the target product is detected by the RFID tag, but the operator fails to complete the corresponding NFC tag permission verification and perform the status change operation within the preset time, such as 60 seconds, but the operator fails to perform NFC tag permission verification or perform the status change operation within 60 seconds, an abnormality will occur. If an NFC tag detects a verification operation in the current state, but the RFID tag fails to detect the corresponding target product in the current state, such as a target product mistakenly entering distributor A's warehouse, and therefore not being recorded as belonging to distributor A, then when distributor A tries to remove the target product, the RFID tag will fail to detect the target product in the current state, resulting in an anomaly. Alternatively, if a target product is left in the warehouse and fails to be successfully removed, meaning the system records that the target product has been removed, but the physical product remains in the warehouse, then when the physical product is scanned again for removal, the RFID tag will fail to detect the target product in the current state (i.e., the "inbound" state), resulting in an anomaly. If the unique ID code of the NFC tag or RFID tag does not match the record in the cloud, such as when a distributor attempts to mix products of unknown origin into the market, the unique code of the NFC tag or RFID tag of the product of unknown origin cannot correspond to the record in the cloud database, and an anomaly will occur. If the same unique ID code is repeatedly confirmed in the same state, such as when the same target product is subjected to multiple state transition operations, an exception will occur when the state transition operation is performed for the second, third, or fourth time. If the authorized operator's permission level does not match the permission level required for the current state transition, such as a medical staff member with only L1 level permission selecting the "outbound" operation, an exception will occur. If any of the above abnormal situations occur, the cloud management system can forcibly block the state transition process and can simultaneously record the abnormal event and / or trigger alarms and / or freeze the operator's permissions.
[0030] In emergency situations, this embodiment also includes an emergency exemption mechanism. In emergency scenarios, when medical personnel urgently need to use a target product, and the NFC tag's authorization verification cannot be completed temporarily, the medical personnel can enter an emergency authorization code into the system. As long as the target product's existence is confirmed via RFID, the system will allow this state transition and simultaneously forcefully push a supplementary confirmation task to the responsible person, and automatically push it to an L3-level user for review. The operator must complete the supplementary authorization verification of the NFC tag within 24 hours; otherwise, the system will automatically mark this state transition as an abnormal event pending verification.
[0031] This embodiment also includes a batch inventory function, which can scan the RFID tags of target products in any state and automatically compare the scan results with the target product records in the cloud database in the corresponding state, and generate an inventory discrepancy report. The inventory discrepancy report marks the following three types of abnormal products: Type 1: The product is recorded in the cloud database but not detected by RFID, indicating that the target product is suspected to be lost. Type 2: If the RFID scan detects the target product but the cloud database records that the target product is not in that state, it indicates that the target product is suspected of being misplaced or abnormally transferred. Type 3: If an RFID scan detects a product but there is no corresponding record in the cloud database, it indicates that the target product is suspected to be an illegal product. The batch inventory mode does not trigger the state transition of the target product and is only used for inventory verification. The inventory discrepancy report is automatically uploaded to the cloud and saved as an audit record.
[0032] In another embodiment of this application, the status also includes "transfer". The target product status can be displayed as "transfer" between "outbound" and "inbound". L2 and L3 level permissions can perform "transfer" status operations.
[0033] In another embodiment of this application, the end user may also be an entity other than a hospital, such as a testing institution.
Claims
1. A method for product lifecycle control and regulation based on NFC and RFID dual tag mandatory interlocking, characterized in that, The method includes the following steps: Lifecycle state machine definition: In a cloud management system, the lifecycle of a target product is defined as a finite set of states, which at least include production, outbound, inbound, use, and scrapping; Unique ID code generation: In production mode, a unique ID code for each target product is generated based on its original identification information; Dual-tag initialization binding: The unique ID code of each target product is written into the RFID tag and NFC tag fixed on the target product respectively, and recorded into the cloud database. The unique ID code cannot be changed after being recorded. The RFID tag is set to read-only state after being written, and is used for batch detection of product existence status. The NFC tag is set to permission verification interaction state, and is used for single-point confirmation of product life cycle status changes. State transition execution and immutable recording: The transition between states can only be triggered if the following three conditions are met simultaneously: Condition 1, the RFID reader detects the existence of the target product's unique ID code in the current state; Condition 2, within a preset time, an authorized operator completes NFC tag permission verification and detection of the target product through the NFC reader and executes the state change operation; Condition 3, the unique ID codes in the detected RFID tags and NFC tags are consistent with the records in the cloud database; only after the conditions are met can the system execute the state transition and record the operator information and transition state information immutably in the cloud database using an immutable storage mechanism; the state transition is irreversible, and the completed state change cannot be rolled back; Anomaly detection and forced blocking: The cloud management system detects abnormal states in real time. Once any abnormal condition is triggered, the cloud management system can forcibly block the state transition process and can simultaneously record abnormal events and / or trigger alarms and / or freeze operator permissions.
2. The method of claim 1, wherein, The unique ID encoding generation step uses a segmented encoding structure, specifically including: The first segment, the product origin code, is used to identify the manufacturer or importer of the target product. The second part, the product category code, is used to identify the category of the target product; The third segment, the batch code, is used to identify the production batch and date of the target product; The fourth segment is the serial number, which is used to identify a unique serial number of a single target product within the same production batch; The fifth segment is the checksum, used to verify the integrity of the encoding. The unique ID code cannot be reused, modified, or transferred within the cloud management system.
3. The method of claim 1, wherein, The preset time can be configured by the system administrator according to the business scenario, with a default value not exceeding 60 seconds.
4. The method of claim 1, wherein, The NFC tag permission verification in the state transition execution and tamper-proof recording steps adopts a hierarchical authorization mechanism, with permission levels divided as follows: Level L1 can only perform operations in the "use" and "scrap" states; Level L2 can perform "inbound" and "outbound" status operations; Level 3, capable of performing all state operations; Level 4, with read-only access to all data and mandatory verification permissions; Different permission levels are independent of each other. Lower-level permissions cannot perform operations with higher-level permissions. Unauthorized operations will be forcibly rejected and recorded by the system.
5. The method of claim 4, wherein, It also includes an emergency exemption mechanism. When an L1 user initiates an emergency use request, a state transition can be allowed to proceed even if the NFC tag permission verification is not met, and this state transition will be marked as an exemption event, provided that the following conditions are met simultaneously: Condition 1: Confirm the presence of the target product through RFID tag detection; Condition 2: The operator enters an emergency authorization code; Condition 3: The system automatically records the exemption event and requests supplementary NFC tag permission verification within the preset exemption time window; The preset exemption time window can be configured by the system administrator according to the business scenario. The default value is no more than 24 hours. The exemption event will be automatically pushed to L3 level user for review. Exemption events that have not been supplemented with NFC tag permission verification within the time limit will be automatically marked as abnormal events pending verification.
6. The method of claim 1, wherein, The operator information and transfer status information include a unique ID code, pre-transfer status, post-transfer status, operation timestamp, operator identity identifier, geographical location information, RFID read original data, and NFC verification original data. The tamper-proof storage mechanism includes storing the operator information and transfer status information using a hash chain storage structure.
7. The method of claim 1, wherein, The abnormal conditions include: Abnormal condition one: The target product is detected by the RFID tag, but the corresponding NFC tag permission verification and status change operation are not completed within the preset time. Abnormal condition 2: The NFC tag detects a verification operation in the current state, but the RFID tag does not detect the target product corresponding to the current state. Thirdly, the unique ID code of the NFC or RFID tag does not match the cloud record. Abnormal condition four: The same unique ID code is used for duplicate confirmation operations under the same state; Abnormal condition five: The authorized operator's permission level does not match the permission level required for the current state transition.
8. The method of claim 7, wherein, The detection method for the third abnormal condition includes extracting the unique ID code stored in the NFC tag and RFID tag in real time each time the NFC tag permission verification operation occurs, and comparing it with the unique ID code recorded in the cloud; if the unique ID code of the NFC tag or RFID tag is inconsistent with the cloud record, it is determined that the product tag is counterfeited, replaced or damaged.
9. The method of claim 1, wherein, It also includes a batch inventory function, which scans the RFID tags of target products in any state and automatically compares the scan results with the records of target products in the corresponding state in the cloud database, and generates an inventory discrepancy report. The inventory discrepancy report marks the following three types of abnormal products: Type 1: The product is recorded in the cloud database but not scanned by the RFID tag, indicating that the target product is suspected to be lost; Type 2: The RFID tag is scanned, but the cloud database records that the target product is not in this state, indicating that the target product is suspected of being misplaced or abnormally transferred; Type 3: If an RFID tag is scanned but there is no corresponding record in the cloud database, it indicates that the target product is suspected to be an illegal product. The batch inventory mode does not trigger the state transition of the target product and is only used for inventory verification. The inventory discrepancy report is automatically uploaded to the cloud and saved as an audit record.
10. A system for product lifecycle control and regulation based on NFC and RFID dual tag mandatory interlocking, characterized in that, The system can perform the method of any of claims 1-9.