CN113362074A

CN113362074A - Product tracking management system, method, tracking information recording method and tracking method

Info

Publication number: CN113362074A
Application number: CN202010154402.2A
Authority: CN
Inventors: 田姗; 尚渭萍; 王岳彪; 刘禹; 李挺; 吴向军; 朱龙龙; 王哲; 雷洋
Original assignee: Shaanxi Shangpin Information Technology Co ltd
Current assignee: Shaanxi Shangpin Information Technology Co ltd
Priority date: 2020-03-07
Filing date: 2020-03-07
Publication date: 2021-09-07

Abstract

The application discloses a product tracking management system, a product tracking management method, a tracking information recording method and a tracking method; the system comprises: the RFID reader-writer and the first server are started in each circulation link of the product; the RFID reader-writer started in each circulation link is used for reading the RFID label on the minimum unit level package of the product; generating record data according to the tracking information and the unique identification of the RFID label which need to be input in the circulation link; sending the recorded data to the first server so that the first server uploads the recorded data to the alliance chain; the first server started in each circulation link responds to a first tracking request aiming at a target product and acquires related recorded data from a alliance chain; and determining a first tracking result corresponding to the first tracking request according to the acquired record data. The application improves the counterfeiting cost, thereby inhibiting the counterfeiting phenomenon of the product.

Description

Product tracking management system, method, tracking information recording method and tracking method

Technical Field

The application belongs to the technical field of anti-counterfeiting, and particularly relates to a product tracking management system and method, a tracking information recording method and a tracking method.

Background

The product goes through a plurality of circulation links from the production, transportation and sale processes; in each distribution segment, the product may be artificially imitated or faked. After consumers buy counterfeit foods or medicines, economic losses are caused slightly, and life and health are seriously damaged. In addition, counterfeit foods or medicines cause huge economic loss and credit loss for regular manufacturers and distributors. Therefore, measures are necessary to prevent the products from being counterfeited in each circulation link.

At present, the anti-counterfeiting measures adopted for the products are usually implemented by manufacturers. The manufacturer prints the anti-counterfeiting code on the outer package of the product and automatically establishes a database of the corresponding relation between the anti-counterfeiting code and the product. The consumer can inquire the truth of the product from the database inquiring system provided by the manufacturer through the anti-counterfeiting code on the outer package of the product.

However, the anti-counterfeit measures currently taken by manufacturers cannot effectively inhibit the counterfeit phenomenon implemented by copying the anti-counterfeit code or recycling the outer package, so that the counterfeit phenomenon of the product sometimes occurs.

Disclosure of Invention

In order to effectively suppress the counterfeit phenomenon by copying the anti-counterfeit code or recycling the outer package, the application provides a product tracking management system, a product tracking management method, a tracking information recording method and a tracking method.

The technical problem to be solved by the application is realized by the following technical scheme:

in a first aspect, the present application provides a product tracking management system, including: an RFID (Radio Frequency Identification) reader-writer and a first server which are started in each circulation link of the product; the first server started in each circulation link is a server for managing the non-individual main body of the product in the circulation link, and the first servers started in each circulation link are all added into the same alliance chain;

the RFID reader-writer started in each circulation link is used for reading the RFID label on the minimum unit level package of the product to obtain the unique identification of the product; generating recording data according to the tracking information of the product to be recorded in the circulation link and the read unique identifier; sending the generated recording data to a first server started in the circulation link;

the first server started in each circulation link is used for receiving the recorded data sent by the RFID reader-writer started in the circulation link and uploading the received recorded data to the alliance chain; responding to a first tracking request aiming at a target product, acquiring recorded data related to the target product from the alliance chain, and determining a first tracking result corresponding to the first tracking request according to the acquired recorded data.

According to the product tracking management system, the RFID reader-writer started in each circulation link is utilized to read the RFID label on the minimum unit level package of the product, and the unique identification of the product is obtained; generating recording data according to the tracking information of the product to be recorded in the circulation link and the read unique identifier; sending the generated recording data to a first server started in the circulation link; the recorded data is then uploaded into the federation chain by a first server enabled in the distribution link. Because the unique identification of the RFID label has uniqueness and the recorded data in the alliance chain cannot be falsified, even if the product is counterfeited by counterfeiting the RFID label or recycling the outer package, the counterfeit RFID label or the reusable RFID label can be effectively identified by tracking the product by using the first server, and then the counterfeited product can be effectively identified.

In addition, the federation chain is characterized in that the first servers joining the federation chain all need to pass authentication; in the application, each first server added to the alliance chain is a server for managing the non-individual main body of the product in each circulation link of the product; thus, the counterfeiter cannot join the federation chain; and even if the recorded data on the individual first server is tampered, the real validity of the recorded data on the alliance chain is not affected. And the cost for the counterfeiting party to tamper most or all of the recorded data on the first server is huge, the counterfeiting can hardly be realized, and the counterfeiting is difficult to implement.

Therefore, under the two advantages of easy identification of counterfeit products and high counterfeit cost, the product tracking management system provided by the application can effectively inhibit the counterfeit phenomenon implemented by copying the anti-counterfeit code or recycling the outer package, thereby reducing the counterfeit phenomenon of the products.

In addition, in the present application, an RFID tag is attached to a minimum unit level package of a product; in this way, efficient tracking of the smallest unit level packaged product can be achieved.

In one implementation manner of the present application, the system further includes: at least one second server joining the federation chain, the second server having a different principal than the first server;

each second server is used for responding to a second tracking request which is sent by the terminal equipment and aims at a product corresponding to any one or more unique identifiers, acquiring recorded data under the unique identifier aiming at the second tracking request from the alliance chain, and determining a second tracking result corresponding to the second tracking request according to the acquired recorded data; and returning the second tracking result to the terminal equipment.

In the application, the second server is added into the alliance chain, and the record data can be acquired from the alliance chain without difference from the first server; in addition, the main body to which the second server belongs does not belong to any circulation link of the product and is not controlled by a non-individual main body in each circulation link of the product, so that the second server can provide a tracking service for a full circulation link of the product corresponding to any one or more unique identifiers for the terminal equipment.

In an implementation manner of the present application, each of the at least one second server is further configured to perform a data analysis task according to one or more predetermined data analysis rules according to the recorded data in the federation chain, so as to obtain a data analysis result corresponding to each data analysis rule.

In the application, the second server is added into the alliance chain, and the recorded data can be acquired from the alliance chain without difference from the first server, so that the second server can execute a data analysis task according to a preset data analysis rule, and further diversified tracking management of the product is realized.

In an implementation manner of the present application, each circulation link of the product includes:

a production link, at least one transportation link, at least one sales link and an overdue destruction link.

The product tracking management system provided by the application can perform whole-course tracking management on products from production to destruction.

In an implementation manner of the present application, each circulation link further includes:

an application consumption step of any of the non-individual subjects to the product; the application consumption link is a link for applying or consuming a product by any one of the non-personal subjects.

The product tracking management system provided by the application can also perform effective tracking management on the condition that the non-individual main body in each circulation link performs internal application or internal consumption on the product.

In an implementation manner of the present application, the tracking information of the product to be entered in each circulation link includes: current circulation state information of the product; the circulation state information is information representing a circulation link where the product is located.

According to the method and the system, after the current circulation state information of the product is recorded in each circulation link, the first server acquires the recorded data containing the circulation state information from the alliance chain, so that the latest circulation state of the product can be determined, and the effect of tracking the latest circulation state of the product is achieved.

In an implementation manner of the present application, the tracking information of the product to be entered in the production link includes:

research and development information of the product, supplier information of materials required for producing the product, production information of the product, and qualification information of the product.

The product tracking management system provided by the application not only can track and manage information after a production link, but also can track and manage information before the production link.

In an implementation manner of the present application, one or more environmental parameter acquisition modules are integrated in the RFID reader;

the tracking information of the products to be input in each circulation link comprises the following steps: the one or more environmental parameter acquisition modules acquire the parameters of the environment where the product is located.

The product tracking management system provided by the application not only can track and manage the information of the product in the product circulation process, but also can track and manage the parameters of the environment where the product is located in the circulation process.

In an implementation manner of the present application, the first tracking request responded by the first server enabled in each circulation link is initiated by the terminal device connected to the first server or an out-of-link server that is in communication with the first server and does not join the federation chain;

and the first server started in each circulation link is also used for returning the determined first tracking result to the terminal equipment or the out-of-chain server initiating the first tracking request.

In the product tracking management system provided by the application, the first server can provide tracking management service for the terminal device and the off-link server which are not joined in the alliance chain.

In an implementation manner of the present application, the RFID reader enabled in each circulation link is further configured to:

and after the RFID label on the minimum unit level package of the product is read and the unique identifier of the product is obtained, the tracking information of the product to be recorded in the circulation link is written into the read RFID label.

In the application, in a scene that no network connection is available and no alliance chain can be accessed, the tracking information of the product can be acquired by directly reading the RFID tag.

In one implementation manner of the present application, the system further includes: a third server joining the federation chain;

the third server is used for verifying the registration application when receiving the registration application that any server applies to become the first server or the second server joining the alliance chain; and when the registration application passes the verification, issuing an identity certificate for the first server or the second server which is successfully registered, and broadcasting the identity certificate of the first server or the second server which is successfully registered to the first server and the second server which are already in the alliance chain.

In the application, under the management of the third server, the product tracking management system provided by the application can further realize the capacity expansion of the system on the premise of ensuring the safety of the alliance chain.

In one implementation of the present application, the RFID tag of each minimum unit level packaged product is attached to the outer packaging of the product at the tear-off location.

In this application, once the outer package of product is unsealed, the RFID label destroys promptly, can't be used repeatedly to can further restrain and carry out the fake phenomenon through retrieving the outer package.

In a second aspect, the present application provides a product tracking management method, applied to a first server enabled in each circulation link of a product; the first server started in each circulation link is a server of a non-individual main body of a management product in the circulation link, and the first servers started in each circulation link are all added into the same alliance chain;

the method comprises the following steps:

receiving recorded data sent by an RFID reader-writer started in the current circulation link, and uploading the received recorded data to the alliance chain; the recorded data is generated by the RFID reader according to the unique identification of the product and the tracking information of the product to be recorded in the current circulation link; the unique identification is read by the RFID reader from an RFID tag on a minimum unit level package of a product;

in response to a first tracking request for a target product, acquiring recorded data related to the target product from the alliance chain; and determining a first tracking result corresponding to the first tracking request according to the acquired record data.

In the product tracking management method provided by the application, a first server receives recorded data sent by an RFID reader-writer started in a current circulation link and uploads the received recorded data to an alliance chain; acquiring record data related to the target product from the alliance chain in response to a first tracking request aiming at the target product; determining a first tracking result corresponding to the first tracking request according to the acquired recording data; the first server added to the alliance chain is a server for managing the non-personal main body of the product in each circulation link of the product, and any first server added to the alliance chain needs to pass authentication, so that recorded data on the alliance chain cannot be tampered. Thus, even if a product is counterfeited by counterfeiting an RFID tag or recycling an outer package, the counterfeit RFID tag or the reusable RFID tag can be effectively identified by tracking the product by using the first server, and the counterfeited product can be effectively identified. Therefore, in the product tracking management method provided by the application, the tracking information of the product is safe and reliable, and correspondingly, the tracking result of the product is credible.

In a third aspect, the present application provides a method for recording tracking information of a product, which is applied to an RFID reader enabled in each circulation link of the product, and includes:

reading the RFID label on the minimum unit level package of the product to obtain the unique identification of the product;

generating recording data according to the tracking information of the product to be recorded in the current circulation link and the read unique identifier;

sending the generated recording data to a first server started in a current circulation link, so that the first server uploads the received recording data to a federation chain joined by the first server;

the first server started in each circulation link is a server of a non-individual main body of the management product in the circulation link, and the first server started in each circulation link is added into the alliance chain.

According to the tracking information recording method of the product, the RFID reader started in each circulation link is utilized to read the RFID label on the minimum unit level package of the product, and the unique identification of the product is obtained; generating recording data according to the tracking information of the product to be recorded in the circulation link and the read unique identifier; writing the generated recording data into the RFID label and sending the recording data to a first server started in the circulation link; the recorded data is then uploaded into the federation chain by a first server enabled in the distribution link. Because the unique identification of the RFID label has uniqueness and the recorded data in the alliance chain cannot be tampered, the method for recording the tracking information of the product can ensure the safety and the effectiveness of the tracking information of the product.

In a fourth aspect, the present application provides a product tracking method, which is applied to a terminal device, and the method includes:

receiving a first tracking request for a target product input by a user; the first tracking request carries the unique identifier of the target product;

sending the first tracking request to a first server in a product tracking management system, so that the first server responds to the first tracking request, acquires recorded data under the unique identifier from a federation chain maintained by the product tracking management system, determines a first tracking result corresponding to the first tracking request according to the acquired recorded data, and returns the first tracking result; the product tracking management system is a system for tracking and managing information generated in each circulation link of a product by utilizing the alliance chain;

and outputting the first tracking result.

In the product tracking method provided by the application, the terminal device sends the first tracking request to the first server, so that the first server responds to the first tracking request, acquires the recorded data under the unique identifier from the alliance chain maintained by the product tracking management system, determines a first tracking result corresponding to the first tracking request according to the acquired recorded data, and returns the first tracking result. In the process, the recorded data of the product acquired by the first server is relatively safe and reliable because the recorded data on the alliance chain cannot be tampered, so that the first tracking result of the product output by the terminal device is relatively credible in the product tracking method provided by the application.

In a fifth aspect, the present application provides a product tracking method, applied to a terminal device, the method including:

receiving a second tracking request which is input by a user and aims at the product corresponding to any one or more unique identifiers;

sending the second tracking request to a second server in a product tracking management system, so that the second server responds to the second tracking request, acquires the recorded data under the one or more unique identifiers from a alliance chain maintained by the product tracking management system, determines a second tracking result corresponding to the second tracking request according to the acquired recorded data, and returns the second tracking result; the product tracking management system is a system for tracking and managing information generated in each circulation link of a product by utilizing the alliance chain;

and outputting the second tracking result.

In the product tracking method provided by the application, the terminal device sends a second tracking request input by a user to the second server, so that the second server responds to the second tracking request, acquires the recorded data under the one or more unique identifiers from the alliance chain maintained by the product tracking management system, determines a second tracking result corresponding to the second tracking request according to the acquired recorded data, and returns the second tracking result. In the process, the recorded data of the product acquired by the second server is relatively safe and reliable because the recorded data on the alliance chain cannot be tampered, so that the second tracking result of the product, which is output to the user by the terminal device, is relatively credible in the product tracking method provided by the application.

The present application will be described in further detail with reference to the accompanying drawings and examples.

Drawings

FIG. 1 is a schematic structural diagram of a product tracking management system provided by an embodiment of the present application;

FIG. 2 is a schematic block diagram of a food tracking management system according to the exemplary illustration of the product tracking management system of FIG. 1;

FIG. 3 is a schematic block diagram of another food tracking management system according to the illustration of the product tracking management system of FIG. 1;

FIG. 4 is a schematic block diagram of a drug tracking management system according to the exemplary illustration of the product tracking management system of FIG. 1;

FIG. 5 is a schematic diagram of the interaction of the RFID reader of the product tracking management system of FIG. 1 with the first server during operation;

FIG. 6 is a schematic diagram of the interaction of a first server with an RFID reader in operation in the product tracking management system of FIG. 1;

FIG. 7 is a schematic illustration of a specific workflow of the workflow of FIG. 6 in which a first server uploads received log data to a federation chain;

FIG. 8 is an interface diagram illustrating a software client installed by a first server in a production session;

FIG. 9 is a schematic structural diagram of another product tracking management system provided in an embodiment of the present application;

FIG. 10 is a diagram illustrating a specific response process of the first server to the first tracking request in the workflow of FIG. 6;

FIG. 11 is a schematic illustration of another specific response process of the first server to the first type of first trace request in the workflow of FIG. 6;

FIG. 12 is a diagram illustrating a specific response process of the first server to the second first trace request in the workflow of FIG. 6;

FIG. 13 is a schematic illustration of another specific response process of the first server to the second first trace request in the workflow of FIG. 6;

FIG. 14 is a diagram illustrating a specific response process of the first server to the third first trace request in the workflow of FIG. 6;

FIG. 15 is a diagram illustrating another specific response process of the first server to the third first trace request in the workflow of FIG. 6;

fig. 16(a) is a schematic structural diagram of another product tracking management system provided in the embodiment of the present application;

fig. 16(b) is an interface diagram of an APP installed in a terminal device connected to a second server for interacting with the second server, which is exemplarily shown;

fig. 16(c) is another interface diagram of an APP installed in a terminal device connected to a second server for interacting with the second server, which is exemplarily shown;

fig. 16(d) is an operation panel diagram of a terminal device connected to a second server exemplarily shown;

fig. 16(e) is an operation panel diagram of another terminal device connected to a second server exemplarily shown;

FIG. 17 is a schematic structural diagram of another product tracking management system provided in an embodiment of the present application;

FIG. 18 is a diagram illustrating a specific response procedure of a second server to a first type of second tracking request in the product tracking management system shown in FIG. 16(a) or FIG. 17;

FIG. 19 is a diagram showing a specific response process of a second server to a second type of second tracking request in the product tracking management system shown in FIG. 16(a) or FIG. 17;

FIG. 20 is a diagram showing a specific response process of a second server to a third second tracking request in the product tracking management system shown in FIG. 16(a) or FIG. 17;

fig. 21 is another interface diagram of an APP installed in a terminal device connected to a second server for interacting with the second server, which is exemplarily shown;

FIG. 22 is a schematic structural diagram of another product tracking management system provided in the embodiments of the present application;

fig. 23 is a schematic diagram illustrating interaction between a first server and an RFID reader in a product tracking management method according to an embodiment of the present application;

fig. 24 is a schematic flowchart illustrating an interaction between an RFID reader and a first server in a tracking information recording method for a product according to an embodiment of the present application;

fig. 25 is an interaction diagram of a terminal device connected to a first server and the first server in a product tracking method according to an embodiment of the present application;

fig. 26(a) is an interface diagram of an APP installed in a terminal device connected to a first server for interacting with the first server, which is exemplarily shown;

fig. 26(b) is an operation panel diagram of an exemplary terminal device connected to a first server;

fig. 26(c) is an operation panel diagram of another exemplary terminal device connected to a first server;

fig. 27 is a schematic interaction diagram of a terminal device connected to a second server and the second server in another product tracking method provided in the embodiment of the present application.

Detailed Description

The present application will be described in further detail with reference to specific examples, but the embodiments of the present application are not limited thereto.

In order to effectively inhibit the counterfeiting phenomenon of the product, which is implemented by copying the anti-counterfeiting code or recycling the outer package, the embodiment of the application provides a product tracking management system. As shown in fig. 1, the system includes: the RFID reader-writer 10 and the first server 20 are respectively started in each circulation link of the product.

Wherein, the first server 20 started in each circulation link is a server for managing the non-personal main body of the product in the circulation link; also, as shown in fig. 1, the first server 20 enabled in each distribution link joins the same federation chain.

The RFID reader-writer started in each circulation link is used for reading the RFID label on the minimum unit level package of the product to obtain the unique identifier UID (unique identification) of the product; generating record data according to the tracking information of the product to be recorded in the circulation link and the read UID; and sending the generated record data to a first server started in the circulation link.

The first server started in each circulation link is used for receiving the recorded data sent by the RFID reader-writer started in the circulation link and uploading the received recorded data to the alliance chain; and responding to a first tracking request aiming at the target product, acquiring recorded data related to the target product from the alliance chain, and determining a first tracking result corresponding to the first tracking request according to the acquired recorded data.

The product tracking management system is suitable for use in medicine, food, daily necessities, electronic devices, and the like, but is not limited thereto. In addition, the target product targeted in the first tracking request may be a product packaged at a minimum unit level corresponding to any one or more UIDs; alternatively, the target product may be a batch of products circled with any one or more attributes of the product; for example, the target product may be a batch of products that are circled with an attribute such as a product name, or the target product may be a batch of products that are circled with an attribute such as a product code, or the target product may be a batch of products that are circled with both attributes such as a product name and a product batch number, or the like.

It is understood that a federation chain is one type of block chain. The block chain comprises a public chain, a private chain and a alliance chain; the public chain is a block chain which is completely decentralized, any person can join the public chain, and the scale is large; the private chain is a centralized block chain, only the internal members of a single organization can be added, and the scale is smaller than that of the public chain; a federation chain is a block chain between a public chain and a private chain, and belongs to a multicentralized block chain. Federation chains are typically larger in size than private chains and smaller in size than public chains. Members joining a federation chain are typically members of a particular organization, such as members of a particular industry federation, and so forth. Thus, a node of a federation chain is typically a server of a member of a particular industry federation. In the embodiment of the application, the first servers of the non-individual main bodies of the management products are all nodes of a alliance chain. It is emphasized that recorded data on a federation chain is not exposed to the outside, and only members joining the federation chain have access rights.

It will be appreciated that the various distribution links for different products may differ. For example, each circulation link of the product may include:

Wherein, in the production link, the non-individual subject managing the product may be a producer; in the transportation segment, the non-individual subject managing the product may be a carrier; in the sales link, the non-individual subject managing the product may be a vendor; in the past due destruction stage, the non-individual subject managing the product may be the manufacturer, the carrier, the seller and/or other subjects. Other principals referred to herein may be government or industry association initiated organizations that perform fixed point destruction of expired products, and the like.

It can be understood that the product may be out of date due to some factors in the production, transportation and sale links; at this time, the expired product is not suitable for continued circulation, so that the circulation process of the expired product can be ended by an unauthorized subject who finds the product failure.

In addition, each circulation link of the product can further comprise: the consumption link of any non-personal subject to the application of the product; here, the application consumption link is a link in which any non-personal subject applies or consumes a product. For example, in the case of drugs, medical structures that are not the subject of an individual may consume the drug for use, such as by selling the drug to an outpatient or administering the drug directly to a patient within a medical facility. Since the medical institution consumes a large amount of the application of the drug compared with the individual consumer, it is necessary to track the flow direction of the drug in the application consumption link, so that the RFID reader and the first server may be provided in the application consumption link to upload the tracking information to the federation chain in the form of recorded data. Also, in any distribution segment, there is a possibility that an impersonal subject may consume the product internally. For example, a food seller distributes the food sold by the seller as a holiday prize to internal employees; alternatively, the vaccine manufacturer injects the produced vaccine to internal personnel, and the like.

For clarity of the scheme, the following describes an exemplary specific structural component of the product tracking management system provided in the embodiments of the present application.

Example 1, assume that there are various circulation segments of a food product including: a production link, a first transportation link from a production factory to a wholesale place, a wholesale link where a wholesaler is located, a second transportation link from the wholesale place to a retail place, a retail link where the retailer is located, and an overdue destruction link; accordingly, as shown in fig. 2, the food tracking management system may include: the RFID reader-writer 10 and the first server 20 in the production link, the RFID reader-writer 10 and the first server 20 in the first transportation link, the RFID reader-writer 10 and the first server 20 in the wholesale link, the RFID reader-writer 10 and the first server 20 in the second transportation link, and the RFID reader-writer 10 and the first server 20 in the retail link. In fig. 2, the direction of the hollow arrow indicates the direction of the circulation of the food, and it can be seen that, except for the overdue destruction link, each circulation link can be directly transited to the overdue destruction link. It is understood that both the wholesale and retail segments belong to the sales segment.

Wherein, the manufacturers, the transporters, the wholesalers and the retailers are all non-personal subjects managing the food, and the first servers of the non-personal subjects are all joined in the alliance chain.

In addition, in the tracking management system, the RFID reader-writer and the first server which manage the non-individual main body of the food in any circulation link can also be used for the overdue destruction link of the food. At the moment, only the tracking information needing to be input in the RFID reader-writer needs to be correspondingly changed, and record data showing that the food is destroyed after being expired is generated; then, the RFID reader-writer sends the recorded data to the first server of the non-personal subject, and the first server uploads the recorded data to the alliance chain.

Alternatively, in the tracking management system, any one impersonal agent may have more than one RFID reader; different RFID readers can be used for inputting the tracking information required to be input in different circulation links. For example, as shown in fig. 3, 2 RFID readers 10 are associated with each of the first servers 20 in the production link, the wholesale link, and the retail link; one of the 2 RFID readers 10 in the production link can be used for inputting tracking information related to production in the production link, and the other RFID reader can be used for inputting tracking information related to overdue destruction of food in the overdue destruction link; one of the 2 RFID readers 10 in the wholesale link can be used for inputting tracking information related to wholesale sales in the sales link where the reader is located, and the other RFID reader can be used for inputting tracking information related to overdue destruction of food in the overdue destruction link; one of the 2 RFID readers 10 in the retail link can be used for entering tracking information related to retail sale in the sales link where the RFID reader is located, and the other RFID reader can be used for entering tracking information related to food overdue destruction in the overdue destruction link. The direction of the outlined arrow in fig. 3 indicates the direction of flow of the food product, as in fig. 2.

In practical application, the content of the recording data specifically generated by the RFID reader can be configured by using the upper computer client of the RFID reader.

Example 2, assume that there are various circulation links for a drug including: a production link, a first transportation link from a production factory to a medicine selling place, a selling link of a medicine seller, a second transportation link from the selling place to a medical structure, an application consumption link of the medical structure and an overdue destruction link; accordingly, as shown in fig. 4, the tracking management system for the drug may include: the RFID reader-writer 10 and the first server 20 in the production link, the RFID reader-writer 10 and the first server 20 in the first transportation link, the RFID reader-writer 10 and the first server 20 in the sales link, the RFID reader-writer 10 and the first server 20 in the second transportation link, and the RFID reader-writer 10 and the first server 20 in the application consumption link where the medical institution is located. Wherein, manufacturers, transporters, drug vendors and medical structures can all be non-individual subjects managing food, and the first servers of the non-individual subjects all join the alliance chain.

In addition, as shown in fig. 4, except for the overdue destruction link, each circulation link can directly transit to the overdue destruction link; at this time, the RFID reader and the first server of each non-personal subject may also be used for an overdue destruction procedure of the medicine. In fig. 4, the hollow arrows represent the circulation direction of the medicine, i.e., the hollow arrows may represent the flow direction relationship of the circulation link.

In addition, in the product tracking management system provided by the embodiment of the application, various communication connection modes exist between the RFID reader-writer and the first server which are started in each circulation link. For example, the RFID reader may communicate with the first server through various communication interfaces such as a USB (Universal Serial Bus) interface, an RS232 interface, an RS485 interface, a bluetooth interface, or a TCP/IP (Transmission Control Protocol/Internet Protocol) interface. It can be understood that the RFID reader/writer is provided with a communication module required for communication connection with the first server.

Based on the above embodiments, it can be seen that the product tracking management system provided in the embodiments of the present application reads the RFID tag on the minimum unit level package of the product by using the RFID reader enabled in each circulation link, and obtains the UID of the product; generating record data according to the tracking information to be input in the circulation link and the read UID; sending the generated recording data to a first server started in the circulation link; the recorded data is then uploaded into the federation chain by a first server enabled in the distribution link. Because the UID of the RFID label has uniqueness and the recorded data in the alliance chain cannot be tampered, even if the product is counterfeited by counterfeiting the RFID label or recycling the outer package, the counterfeit RFID label or the reusable RFID label can be effectively identified by tracking the product by using the first server, and then the counterfeited product is identified.

In addition, the federation chain is characterized in that the first servers joining the federation chain all need to pass authentication; thus, the counterfeiter cannot join the federation chain; in the embodiment of the application, each first server added into the alliance chain is a server for managing the non-individual main body of the product in each circulation link of the product; therefore, even if the recorded data on the individual first servers are tampered, the real validity of the recorded data on the alliance chain is not affected, and the counterfeiting party needs to pay huge cost for tampering most or all the recorded data on the first servers, so that the counterfeiting is almost impossible and difficult to implement.

Therefore, under the two advantages of easy identification of counterfeit products and high counterfeit cost, the product tracking management system provided by the embodiment of the application can effectively inhibit the counterfeit phenomenon implemented by copying the anti-counterfeit code or recycling the outer package, thereby reducing the counterfeit phenomenon of the product.

In addition, in the scheme, the RFID label is attached to the minimum unit level package of the product; in this way, efficient tracking of the smallest unit level packaged product can be achieved.

For clarity of the solution, the following respectively describes in further detail the operation modes of the RFID reader and the first server in the product tracking management system provided in the embodiment of the present application.

First, a workflow of the RFID reader is described, and for clarity of the scheme, the workflow is described by using an interaction diagram of the RFID reader and the first server shown in fig. 5. As shown in fig. 5, the workflow is as follows:

s501: and reading the RFID label on the minimum unit level package of the product by the RFID reader-writer to obtain the UID of the product.

The RFID tag consists of an internal chip and an antenna circuit; when each RFID label is delivered from a factory, a manufacturer producing the RFID label can allocate a UID to each RFID label, and the UID is written in a chip of the RFID label and cannot be modified.

Moreover, some information, such as factory information of the RFID tag, may be written in advance in the chip inside the RFID tag; in addition, the chip in the RFID label can be written with the customized information of the manufacturer of the product in advance; here, the customization information may include: research and development information of the product, supplier information of materials required for producing the product, qualification information of the product and the like. It will be appreciated that the customized information is information that has been generated before the product enters the production chain.

RFID tags can be classified into active RFID tags and passive RFID tags. The passive RFID tag needs to transmit information stored in a chip by means of electromagnetic energy in a signal sent by an antenna circuit of an RFID reader-writer, has lower operating power but lower manufacturing cost, small volume and light weight; the active RFID tag is provided with a built-in power supply, so that the operating power is high, the signal propagation distance is longer, and the built-in power supply can increase the volume and the weight of the RFID tag. Therefore, in the embodiment of the application, in order to make the RFID tag suitable for being attached to the minimum unit level package of the product, the passive RFID tag is adopted. Here, the minimum unit level package is understood to be a minimum sales unit of the product.

In addition, in the product tracking management system provided by the embodiment of the application, the antenna circuit of the RFID tag may be printed by using conductive ink. Among them, conductive ink such as nano silver ink, etc. It will be appreciated that printing the manufactured RFID tag with conductive ink may make the RFID tag more lightweight, thereby facilitating attachment to the smallest unit-level packaging of the product. Of course, the antenna circuit of the RFID tag may be manufactured by other manufacturing processes, such as a metal etching process, and the like.

S502: and the RFID reader generates recording data according to the tracking information of the product to be recorded in the current circulation link and the read UID.

In this step, according to the tracking information of the product to be entered in the current circulation link and the read UID, a specific implementation manner of generating the record data may include:

and taking the tracking information required to be input in the current circulation link as the tracking information required to be input in the current circulation link corresponding to the read UID, and generating recording data according to a preset data format.

It is understood that the tracking information to be entered in each circulation link may include one or more types; therefore, when generating a data record in which the UID corresponds to the trace information, the data record may be generated in a predetermined data format.

For example, in one implementation, the read UID may be used as a key, and each trace information that needs to be entered may be used as a key value, so as to obtain a plurality of key-value pairs as the generated record data. For example, assuming that the tracking information to be entered in the production link includes the product code, the production date and the shelf life of the product, the UID is 12345; the generated logging data may include: 0101 at 12345-A, 20200202 at 12345-B, and 2 years at 12345-C; wherein A represents a product code, B represents a production date, and C represents a shelf life; the lower case letters after the colon are the specific contents of the tracking information represented by the upper case letters before the colon.

In another implementation mode, the read UID can be used as a key, and various tracking information to be entered can be used as key values to generate a key-value pair as generated record data; in the key value of each key-value pair, a separator is adopted to separate various kinds of tracking information, and the sequence of the various kinds of tracking information in the key value can be preset. For example, it is assumed that the trace information to be entered includes A, B, C and D, and the arrangement order of the various trace information in the key values is designated as A, B, C, D; assuming a UID of 12345, the record data generated may be: 12345- [ A/B/C/D ], 12345- [ A # B # C # D ] or 12345- [ A | B | C | D ].

It should be noted that the data format of the recorded data shown above is only an example, and does not constitute a limitation to the embodiments of the present application, and any data format suitable for the RFID reader to perform reading and writing operations and transmit is suitable for the embodiments of the present application.

In addition, for the sake of clarity of the scheme and clarity of layout, the following exemplary description is made on the trace information that needs to be entered in each circulation link.

S503: and the RFID reader sends the generated recording data to a first server started in the current circulation link.

S504: the first server uploads the received record data to a federation chain joined by the first server.

In step S503, the specific implementation manner that the RFID reader sends the generated recording data to the first server activated in the current circulation link mainly depends on the communication connection manner between the RFID reader and the first server. For example, if the RFID reader is connected to the first server by a wired communication method such as a USB interface or an RS232 interface, the RFID reader directly transmits the generated recording data to the first server through the communication connection line.

Or if the RFID reader-writer is connected with the first server in a wireless communication mode, the RFID reader-writer sends the generated recording data to the first server in a wireless communication mode. For example, a mobile communication module may be disposed in the RFID reader; then, the RFID reader may transmit the record data to the first server through a mobile communication network using the mobile communication module. Here, the mobile communication module may be a 3G module or a 4G module, etc.; correspondingly, the mobile communication network refers to a third generation mobile communication network or a fourth generation mobile communication network; or, a bluetooth module can be arranged in the RFID reader; then, the RFID reader may directly transmit the recorded data to the first server through the bluetooth interface. Or, a Wi-Fi (Wireless-Fidelity) module may be disposed in the RFID reader; then, the RFID reader may transmit the recorded data to the first server through the wireless local area network using the Wi-Fi module.

It should be noted that, when reading an RFID tag, an RFID reader may read a plurality of RFID tags at the same time; for clarity of description of the work flow of the RFID reader, the work flow shown in fig. 5 is a process for one RFID tag, and it can be understood that, when the RFID reader reads a plurality of RFID tags, the process can be referred to for each RFID tag.

In the following, exemplary descriptions are given to the trace information that needs to be entered in each circulation link.

For example, in one implementation, the tracking information to be entered in each circulation segment of the product may include: the current circulation state information of the product.

Here, the circulation state information is information representing a circulation link in which the product is located. For example, the circulation status information may specifically include: the name of the non-individual subject who manages the product, the time when the non-individual subject starts managing the product, and the time when the non-individual subject ends managing the product, and the like.

It can be understood that, based on tracking the circulation state information of the product, the current manager of the product can determine the authenticity of the product by comparing the latest circulation state information recorded in the tracking management system with the information of the current manager.

In another implementation, in order to enable the tracking management system to achieve various management requirements for the product, the tracking information to be entered in each circulation link may include more information.

For example, in the production process, the trace information to be entered may include: production information of the product; here, the specific contents of the production information of the product may be various; for example, the product code or name of the product, the model of the product, the date of manufacture of the product, and the shelf life of the product, among others.

In addition, one or more of the above-mentioned customized information can be re-placed in the production link, and the manufacturer uses the information as the tracking information to be entered in the production link to generate corresponding recorded data. Thus, the manufacturer can purchase the RFID tag written with the UID without specially customizing the RFID tag.

In each transportation segment, the tracking information to be entered may include: logistics tracking information. Here, the specific content of the logistics tracking information may include various information; for example, information on a logistics company that takes over transportation, information on a vehicle that takes over transportation, information on a person who takes over transportation, information on the location of food or medicine, and information on the time of transportation of a product, and the like.

In each sales segment, the tracking information to be entered may include: sales information; the sales information may specifically include a variety of information; for example, the sales information may include: vendor information, sales flow information for the product, time of arrival information for the product, and time of sale information for the product, among others. The sales flow information of the product may include account information for purchasing the product.

In the expired destruction link, the tracking information to be entered may include: the destruction time of the product; the method can also comprise the following steps: information on the performers who destroyed the product, etc.

In the application consumption link, the trace information to be entered may include: the application flow information of the product, the application consumption time of the product, and the like. The application flow information of the product may include information on a person who applies or consumes the product, or may include information on an organization of the application or the product.

The above is an exemplary description of the trace information that needs to be entered in each distribution link. It should be noted that the trace information that needs to be entered in each circulation link is only used as an example, and should not be construed as a limitation to the embodiments of the present application.

Next, the operation of the first server in the product tracking management system provided in the embodiment of the present application is further described in detail. For clarity of the scheme, the workflow is described by using an interaction diagram of the first server and the RFID reader shown in fig. 6. As shown in fig. 6, the workflow is as follows:

s610: and the RFID reader-writer started in the current circulation link sends the recorded data in the current circulation link to the first server.

The first server receives the recorded data sent by the RFID reader-writer, and the specific implementation mode of the first server receiving the recorded data sent by the RFID reader-writer started in the current circulation link mainly depends on the communication connection mode between the first server and the RFID reader-writer. For example, if the first server and the RFID reader are connected by a wired communication method such as a USB interface or an RS232 interface, the first server directly receives the recording data sent by the RFID reader through the communication connection line.

Or, if the first server is connected with the RFID reader in a wireless communication manner, the first server receives the recording data sent by the RFID reader in a wireless communication manner. For example, if the RFID reader is provided with a mobile communication module, the recorded data is sent to the first server through a mobile communication network; then, the first server can access to the mobile communication network through the internet, thereby receiving the recorded data sent by the RFID reader. Or, if the RFID reader-writer is provided with a Bluetooth module; then, the first server can receive the record data sent by the RFID reader through the Bluetooth interface; it is understood that the first server may also be provided with a bluetooth module. Or if the Wi-Fi module is arranged in the RFID reader-writer, the recorded data is sent to the first server through the wireless local area network; then, the first server may receive the recorded data sent by the RFID reader through the wireless lan.

S620: the first server uploads the received logging data into the federation chain.

S630: the first server responds to a first tracking request aiming at a target product, obtains recorded data related to the target product from the alliance chain, and determines a first tracking result corresponding to the first tracking request according to the obtained recorded data.

In step S620, the specific workflow of the first server uploading the received record data to the federation chain may be as shown in fig. 7, including:

s6201: the received record data is packaged into a federation chain transaction record form.

In step S6201, there are various specific implementation manners for packaging the record data into a transaction record form of the alliance chain; for example, in one implementation, the corresponding transaction parties and transaction amount may be set for the product record data corresponding to each UID, so that each piece of record data may serve as one transaction record; the two transaction parties of the recorded data in each circulation link can be a first server of the circulation link and a first server of any circulation link in the adjacent circulation links; the transaction amount may be set according to a predetermined convention, which is not limited in the embodiment of the present application.

Here, the recorded data is packaged into a transaction record form of the alliance chain, so that each server joining the alliance chain can conveniently start an consensus verification algorithm to perform consensus verification on the recorded data subsequently.

In addition, it can be understood that, when the transaction amount of the transaction record is set according to a predetermined convention, for each UID, the calculation result obtained by calculating the record data in the form of the transaction record according to time sequence can be used for representing the current circulation state of the product corresponding to the UID; moreover, when the reverse operation is performed according to the time sequence, the effect of backtracking operation on the recorded data can be achieved.

S6202: broadcasting the packaged recorded data to each server joining the alliance chain so that the packaged recorded data is identified and verified by each server; when the packaged record data is identified and verified by all the servers, uploading the record data to a alliance chain; wherein, each server joining the federation chain includes: each first server joining the federation chain.

It is to be understood that the type of server joining the federation chain is not limited to the first server, and that other types of servers joining the federation chain are described subsequently for clarity of the scheme and clarity of layout.

In step S6202, when the packaged record data is verified by the consensus of the servers, the servers synchronize the record data to the blocks of the self-maintained federation chain respectively. Thus, the uplink of the recorded data is completed. It can be understood that, if the verification result of the consensus verification of the packaged record data by each first server is failed, each first server will not synchronize the record data into the block of the self-maintained federation chain; accordingly, the log data is not uploaded into the federation chain.

In practical applications, each server joining the federation chain may be responsible for collecting the recording data broadcast by each first server joining the federation chain in turn, and packing the collected recording data into a block, which is sent to each server joining the federation chain. After each server receives the block, the consensus algorithm is used for performing consensus verification on the recorded data on the block, and after the verification result passes, the block can become a formal block on the alliance chain. Wherein, the consensus algorithm is used to solve the problem of how each server joining the federation chain reaches a resolution. In the embodiment of the present application, the consensus algorithm may use a PBFT (Practical Byzantine Fault Tolerance) algorithm, a PoI (Proof of Importance) consensus algorithm, or a raft (verified And failed Fault Tolerance) algorithm, And the like, but is not limited thereto. RAFT, among others, is an existing distributed consensus algorithm. It is understood that, so-called consensus verification, each server participating in verification can obtain a verification result that is verified only when the verification results of all the servers joining the blockchain are passed, or the verification results of most of the servers joining the blockchain are passed.

It is understood that the functions embodied by each first server further include: and participating in consensus verification of the recorded data on the alliance chain.

It is understood that, in step S630, the tracking information of the target product has been entered into the tracking management system.

In the workflow, the first tracking request for the target product may be issued by a user of the first server. Here, the user of the first server is generally a non-personal subject of the management product in the circulation link of the first server, and specifically, may be a user assigned by the non-personal subject and having an access right to the first server.

In practical applications, a software client may be installed in the first server, and a user of the first server may send a first tracking request for a target product to the first server through the software client. It is understood that the software interface of the software client is provided with the function options of setting the request content of the first trace request and issuing the first trace request to the first server. FIG. 8 is an interface diagram illustrating a software client installed in a first server in a production session; as shown in fig. 8, in the software client, in addition to the first tracking request may be initiated using the UID query box, the first tracking request may be initiated using a product name query box, a product code query box, and/or a product batch number query box. It is understood that in the interface shown in fig. 8, the query boxes may be used in combination.

Alternatively, the first trace request may be issued by another device in communication with the first server in the workflow. The other device may be a terminal device corresponding to the first server, or may be another server that can communicate with the first server. Here, the terminal device corresponding to the first server may be a mobile terminal, a computer, a digital broadcast terminal, a messaging device, a medical device, or a personal digital assistant, etc.

Wherein, the other servers include the off-link servers which can communicate with the first server activated in the current circulation link and do not join the alliance chain; of course, any server that joins the federation chain may also be included, e.g., the first server that is not enabled in the current circulation segment.

It should be noted that, the out-link server that can communicate with the first server may be a server that establishes a mutually trusted communication connection relationship with the first server, that is, a site where the out-link server is located belongs to a trusted site of the first server. In general, there may be a cooperative relationship between users of such an out-of-chain server and the non-personal agent that manages the first server.

It can be understood that, besides the need of tracking management for the product, the non-individual subject in each circulation link of the product can also provide tracking management service for the outside users and other non-individual subjects in other circulation links. Accordingly, external users and other non-personal subjects in the circulation link can send a first tracking request for the product to the first server through the other devices.

For example, an external user may send a first tracking request to the first server through a terminal device, or the external user may send the first tracking request to the first server through a server which is not joined in a federation chain and may communicate with the first server; and the non-individual main body in other circulation links can send a first tracking request to the first server of the current circulation link through the first server started in the circulation link in which the non-individual main body is positioned. It will be appreciated that each of the other devices may be provided with the functionality option of setting the requested content of the first trace request and issuing the first trace request to the first server.

Therefore, on the basis of the tracking management system shown in fig. 1, the product tracking management system provided in the embodiment of the present application may include, as shown in fig. 9: the RFID reader-writer 10 started by each circulation link, the first server 20 started by each circulation link, the terminal device 30 corresponding to each first server, and the off-link server 40 which can communicate with each first server and is not joined in the alliance chain.

Based on the tracking management system shown in fig. 9, it can be seen that the product tracking management system provided in the embodiment of the present application can provide tracking management services to users outside the system and members inside the system. In addition, the product tracking management system provided by the embodiment of the application can provide diversified tracking management services.

Next, a tracking management service provided by the product tracking management system provided in the embodiment of the present application is exemplarily described.

It is to be understood that different types of trace management services may correspond to different types of first trace requests; when the types of the first tracking requests are different, request parameters carried in the first tracking requests can be different; accordingly, the first server responds to the first trace requests of different types differently. In the following, various first trace requests of different types and the manner in which the first server responds to each first trace request are exemplarily described.

In a first example, a first type of first tracking request to be responded by a first server in a current circulation link may be a request for tracing a source of a target product corresponding to any one or more UIDs, which is provided by an off-link server in communication with the first server; the first tracking request carries the UID of the target product to be traced.

Accordingly, as shown in fig. 10, in step S630, the acquiring, by the first server, the record data related to the target product from the federation chain in response to the first tracking request for the target product, and determining a first tracking result corresponding to the first tracking request according to the acquired record data may include:

s6301 a: and responding to a first tracking request aiming at the target product, and acquiring the record data under one or more UIDs carried in the first tracking request from the alliance chain.

S6302 a: and screening the recorded data of the current circulation link and the circulation link before the current circulation link from the acquired recorded data to serve as a first tracking result corresponding to the first tracking request.

It will be appreciated that since the data on the federation chain is commonly maintained by all servers joining the federation chain, that is, any server joining the federation chain can indiscriminately obtain the logging data from the federation chain. Therefore, the first server of the current circulation link can acquire the current circulation link and the recorded data of the circulation link before the current circulation link from the alliance chain, and the purpose of tracing the target product is achieved.

In addition, after the first server in the current circulation link determines the first tracking result, the first tracking result can be further fed back to the out-of-link server which provides the first tracking request; therefore, as shown in fig. 11, step S630 may further include the following sub-steps:

s6303 a: and feeding back a first tracking result corresponding to the first tracking request to an off-chain server which makes the first tracking request.

In addition, before the first server of the current circulation link feeds back the first tracking result corresponding to the first tracking request to the off-link server which makes the first tracking request, the form or content of the first tracking result can be adjusted in favor of sending, so that the adjusted first tracking result is fed back to the off-link server.

In a second example, the second type of first tracking request to be responded by the first server in the current circulation link may be a request for querying whether the target product corresponding to any one or more UIDs is true or false, which is provided by the terminal device corresponding to the first server; the first tracking request carries the UID of the target product to be inquired.

Accordingly, as shown in fig. 12, in step S630, the acquiring, by the first server, the record data related to the target product from the federation chain in response to the first tracking request for the target product, and determining a first tracking result corresponding to the first tracking request according to the acquired record data may include:

s6301 b: and responding to a first tracking request aiming at the target product, and acquiring the record data under one or more UIDs carried in the first tracking request from the alliance chain.

S6302 b: and screening the record data belonging to the current circulation link from the acquired record data to serve as a first tracking result corresponding to the first tracking request.

It can be understood that most users of the terminal devices are individual users, and the individual users choose to inquire the authenticity of the product from the first server of the non-individual main body, which is usually the case that the users ask about the authenticity of the product in the circulation link of the non-individual main body; moreover, limited to the cooperative engagement of the industry alliance of the product, even if any server added into the alliance chain can indiscriminately obtain the recorded data from the alliance chain, the first server in a single circulation link is not convenient for directly feeding back all the recorded data in the circulation link other than the first server to the individual user. Therefore, in this example, the first server of the current circulation link may filter the record data belonging to the current circulation link from the acquired record data as the first tracking result corresponding to the first tracking request.

Correspondingly, after the first server in the current circulation link determines the first tracking result, the first tracking result can be further fed back to the terminal device which provides the first tracking request; therefore, as shown in fig. 13, step S630 may further include the following sub-steps:

s6303 b: and feeding back a first tracking result corresponding to the first tracking request to the terminal equipment which makes the first tracking request.

Similarly, before feeding back the first tracking result corresponding to the first tracking request to the terminal device that has made the first tracking request, the first server in the current circulation link may also perform adjustment that facilitates sending the form or content of the first tracking result, so as to feed back the adjusted first tracking result to the terminal device.

Or before the first server of the current circulation link feeds back the first tracking result corresponding to the first tracking request to the terminal device which makes the first tracking request, the form or content of the first tracking result may also be adjusted so as to facilitate the user of the terminal device to check, so that the adjusted first tracking result is fed back to the terminal device. Here, the adjustment that facilitates the user view of the terminal device includes: and screening the tracking information concerned by the user of the terminal equipment according to a preset screening rule.

In a third example, the third first tracking request to be responded by the first server in the current circulation link may be a request for counting target tracking information of the target product, which is provided by a user of the first server, where the target tracking information may be one or more types of information belonging to tracking information entered in the current circulation link; the first tracking request carries the name of the target product and the name of the target tracking information; and, the name of the target product carried in the first tracking request may be more than one.

It will be appreciated that the number of products packaged at the minimum unit level is many for each product, and therefore, the first trace request is intended to count the target trace information under all UIDs under that product.

Accordingly, as shown in fig. 14, in step S630, the acquiring, by the first server, the record data related to the target product from the federation chain in response to the first tracking request for the target product, and determining a first tracking result corresponding to the first tracking request according to the acquired record data may include:

s6301 c: and responding to the first tracking request aiming at the target product, and acquiring the recorded data containing the target tracking information under the name of the target product from the alliance chain.

S6302 c: and counting the target tracking information to be counted according to the acquired recording data, and taking the counting result as a first tracking result corresponding to the first tracking request.

In step S6302c, the statistics performed by the first server on the target tracking information may be a simple data statistics task performed according to a predetermined statistical rule; or a complex data statistical task performed by a professional statistical tool according to a predetermined statistical rule.

It will be appreciated that the non-individual subject in each distribution segment will typically have a need to keep track of certain tracking information for the products involved in the distribution, for regulatory responsibility on the products that they themselves participate in the distribution. For example, a manufacturer of a drug or food may want to keep track of the current circulation status of a new type of drug or food from the factory; alternatively, a food producer may want to keep track of sales flow information for one food product leaving the factory; alternatively, in the application consumption of drugs, the medical structure may want to count the application flow information and/or application consumption time of a drug, and so on. Thus, in this example, the first server may obtain the corresponding record data from the federation chain in response to a first tracking request of this type by the user; and screening the recorded data and further counting the screened target tracking information to obtain a final first tracking result.

In addition, after determining the first tracking result, the first server may further output the first tracking result to the user; therefore, as shown in fig. 15, step S630 may further include the following sub-steps:

s6303 c: and outputting a first tracking result corresponding to the first tracking request.

In addition, before the first server displays the first tracking result corresponding to the first tracking request to the user, the first server may perform adjustment which is beneficial to output on the form or content of the first tracking result, so as to output the adjusted first tracking result to the user.

In a fourth example, the fourth first tracking request to be responded by the first server in the current circulation link may be a request for counting the target tracking information of the target product, which is provided by any one server joining the federation chain; at this time, the first tracking request carries the name of the target product and the name of the target tracking information to be counted; here, any one of the servers that join the federation chain may be the first server in a non-current distribution link or any other server that joins the federation chain.

It can be understood that, although any server added to the federation chain can indiscriminately obtain the recorded data of all circulation links of the product from the federation chain, some non-personal subjects in the circulation links may have data statistics capability only for the recorded data in the circulation links where the non-personal subjects are located, and may not have data statistics capability for the recorded data in the circulation links where the non-personal subjects are located; or, the main body to which the other servers added to the federation chain belong may not have the capability of performing data statistics on the recorded data in some circulation links; at this time, the servers joining the federation chain may form a mutual federation; that is, the first server in each distribution link may receive a request for statistics of target tracking information of a target product from any one server participating in the federation chain, and accordingly respond to the first tracking request of this type. For a specific response procedure of the first server, reference may be made to the response procedures of steps S6301c to S6302c in the third example, which is not described again in this example.

In addition, in this example, after determining the first tracking result, the first server may further feed back the first tracking result to the server that initiated the first tracking request. And before feeding back the first tracking result corresponding to the first tracking request, the first server may perform adjustment that facilitates sending on the form or content of the first tracking result, so as to feed back the adjusted first tracking result to the server that provided the first tracking request.

The above is an exemplary description of different types of multiple first trace requests and the response manner of the first server to each first trace request. It should be noted that the above 4 examples do not constitute a limitation on the tracking management service that the first server can provide, and by transforming the category of the first tracking request, the first server can also provide more types of tracking management services, which is limited to space and will not be further described here.

On the basis of the product tracking management system shown in fig. 1, as shown in fig. 16(a), the product tracking management system provided in the embodiment of the present application may further include: at least one second server 50 joining the federation chain; the second server 50 belongs to a different subject than the first server 20.

Each second server 50 is configured to, in response to a second tracking request sent by a terminal device for a product corresponding to any one or more UIDs, acquire, from the federation chain, recorded data under the UID to which the second tracking request is directed, and determine, according to the acquired recorded data, a second tracking result corresponding to the second tracking request; and returning the second tracking result to the terminal equipment.

Here, the second server 50 joining the federation chain, i.e., may be the other types of servers joining the federation chain mentioned above; the terminal device that transmits the second tracking request to the second server 50 may be a terminal device connected to the second server 50.

It is understood that, if the second server 50 joins the alliance chain, the second server 50 can be used as a node of the alliance chain to participate in the consensus verification of the uplink of the record data; however, unlike the first server 20, the second server 50 does not write the log data into the federation chain.

In practical applications, there may be a plurality of subjects to which the second server 50 belongs. For example, the subject to which any of the second servers 50 belongs may be a regulatory agency of the product, or an industry association of the product, or the like. In addition, the non-individual main body in each circulation link can also apply for a second server of the self; in this way, for the non-individual subject in each circulation link, the recorded data can be written into the alliance chain by using the first server of the non-individual subject, and the data can be acquired from the alliance chain by using the second server of the non-individual subject, so that the tracking management service can be provided for the user of the external terminal equipment. It will be appreciated that one of the primary purposes of providing the second server 50 in a tracking management system is to provide product tracking services to users of terminal devices.

Here, the terminal device is used for reading the RFID label on the outer package of the product and obtaining the UID of the product; then, the terminal device sends a second tracking request given by the user in the terminal device and the read UID to a second server, and the second server gives a specific response to the second tracking request; and after responding to the second tracking request and determining a second tracking result, the second server feeds the second tracking result back to the terminal equipment so that the terminal equipment outputs the second tracking result to the user.

The specific implementation manner of the user giving the second tracking request in the terminal device may be different for different types of terminal devices. For example, in a terminal device, an APP for interacting with a second server may be installed, and a user may initiate a second tracking request to the second server in the APP. Fig. 16(b) is an interface diagram illustrating an APP installed in a terminal device; as shown in fig. 16(b), the user is prompted in the interface to bring the product close to the NFC sensing area to start tracking the product; in this way, the APP may read the RFID tag of the product by using an NFC (Near Field Communication) function integrated in the mobile phone, so as to initiate a second tracking request. FIG. 16(c) illustrates another interface diagram of the APP; as shown in fig. 16(b), in this interface, the user may manually enter the UID of the product in the APP, thereby initiating a second trace request through the APP; it will be appreciated that at this point, the RFID tag of the product may be printed with the UID for use by the user in manually entering the UID.

Alternatively, in another terminal device, a key for initiating a second tracking request to a second server may be provided; thus, a user clicking on a button may initiate a second tracking request to the second server. Fig. 16(d) is a schematic view exemplarily showing an operation panel of the terminal device; as shown in fig. 16(d), the operation panel of the terminal device is provided with 3 keys, and each key corresponds to a preset second tracking request. In addition, in fig. 16(d), the boxes above the three keys are the display screens of the terminal device.

Alternatively, in another terminal device, the user may initiate a second tracking request to the second server by placing the RFID tag of the product proximate to the sensing zone of the terminal device. Fig. 16(e) is a schematic view exemplarily showing an operation panel of the terminal device; as shown in fig. 16(e), the operation panel is provided with a prompt to prompt the user to attach the RFID tag to the sensing area, so as to initiate a second tracking request, where the second tracking request may specifically be a request for inquiring whether the product is true or false and knowing the production date and expiration date of the product.

It can be understood that, in the terminal device, an NFC module may be integrated, and the terminal device reads the RFID tag on the outer package of the product through the NFC module; or, an RFID reader with a shielded writing function may be integrated in the terminal device, and the terminal device may read an RFID tag on an outer package of a product through the RFID reader; when the volume of the RFID reader integrated in the latter terminal device is large, and the terminal device is not suitable for a mobile application scenario, the terminal device may be disposed in a retail location of a product or other places convenient for consumers of the product to use. In this way, the consumer can use either terminal device to read the RFID tag on the outer packaging of the purchased product. It will be understood that such terminal devices are of a common nature, and that the consumer, as referred to herein, is the user of such terminal device.

In addition, the specific implementation manner of outputting the second tracking result by the terminal device may also be different for different types of terminal devices. For example, for the terminal device installed with the APP, the terminal device may display the second tracking result in the APP; or, in a terminal device, the second tracking result may be output in a voice broadcast manner; still alternatively, for a terminal device having a display screen, the second tracking result may be displayed in the display screen.

In practical applications, the terminal device that sends the second tracking request to the second server 50 may specifically be a mobile terminal, a computer, a digital broadcast terminal, a sales device, a messaging device, a medical device, or a personal digital assistant, and the like, but is not limited thereto.

Thus, after the tracking management systems shown in fig. 16(a) and fig. 9 are combined, the components of the product tracking management system provided by the embodiment of the present application may be as shown in fig. 17, including:

the RFID reader-writer 10 which is respectively started in each circulation link, the first server 20 which is respectively started in each circulation link, the terminal equipment 30 corresponding to each first server, the out-of-link server 40 which is communicated with each first server, each second server 50 which is added into the alliance chain and the terminal equipment 30 corresponding to each second server.

In practical applications, the terminal device 30 corresponding to the first server 20 and the terminal device 30 corresponding to the second server 50 may be the same terminal device.

There may be a variety of types of second tracking requests to which the second server 50 responds, similar to the first tracking request to which the first server 20 responds. When the types of the second trace requests are different, the request parameters carried in the second trace requests may be different. Accordingly, the response manner of the second server to the second tracking request of different type may also be different. Next, a plurality of second tracking requests of different types and a manner of responding to each second tracking request by the second server will be described as an example.

In example a, the first tracking request to be responded by the second server 50 may be a request for querying the authenticity of a product corresponding to any one or more UIDs, which is provided by a terminal device connected to the second server 50; the second tracking request carries the UID of the product to be queried for authenticity.

Correspondingly, as shown in fig. 18, the step of, by the second server, in response to a second tracking request sent by the terminal device for a product corresponding to any one or more UIDs, acquiring, from the federation chain, record data under the UID to which the second tracking request is directed, and determining, according to the acquired record data, a second tracking result corresponding to the second tracking request may include:

s1810: and responding to a second tracking request aiming at products corresponding to any one or more UIDs sent by the terminal equipment, and acquiring the recorded data under one or more UIDs carried in the second tracking request from the alliance chain.

S1820: and screening the record data in the latest circulation link from the acquired record data to be used as a second tracking result corresponding to the second tracking request.

It can be understood that the user of the terminal device can determine the authenticity of the product by checking the recorded data in the latest circulation link of the product and comparing the recorded data with the information such as the channel and time of the product acquired by the user.

For example, when the tracking information to be entered in each circulation link includes current circulation state information of a product, assuming that a user of the terminal device is a drug purchased in a sales link, a seller in the sales link writes the circulation state information of the drug into a alliance chain; since the circulation status information includes the name of the seller and the time when the seller finishes managing the medicine, when the user of the terminal device requests the second server 50 to inquire the authenticity of the obtained product through the terminal device, the second server may feed back the recorded data in the sales link acquired from the alliance chain to the terminal device; therefore, the user of the terminal equipment can determine the authenticity of the purchased product by comparing the recorded data with the place and time of purchasing the medicine. It will be appreciated that the name of a non-personal subject, such as a vendor in a sales link, will typically include the location of the sale. For example, the name of a drug vendor is typically XX pharmacy XX road shop. In addition, it can be understood that the time when the seller finishes managing the medicine is the selling time information of the medicine.

For another example, when the tracking information to be entered in each circulation link is more detailed, assuming that the user of the terminal device is a drug obtained from a hospital in an application consumption link, in the application consumption link, the hospital writes circulation state information of the product into a alliance chain; since the circulation status information includes information such as the name of the hospital, the flow direction information of the medicine, and the application consumption time of the medicine, when the user of the terminal device requests the second server 50 through the terminal device to inquire the authenticity of the obtained product, the second server feeds back the recorded data in the application consumption link acquired from the alliance chain to the terminal device; therefore, the user of the terminal equipment can determine the authenticity of the product acquired by the user by comparing the recorded data with the time for acquiring the medicine and the personal identity of the user.

In addition, before feeding back a second tracking result corresponding to the second tracking request to the terminal device which has made the second tracking request, the second server may adjust the content of the second tracking result, which is beneficial for the user of the terminal device to view, so as to feed back the adjusted second tracking result to the terminal device. Here, the adjustment that facilitates the user view of the terminal device includes: and screening the tracking information concerned by the user according to a preset screening rule.

Example b, the second type of second tracking request to be responded by the second server may be a request for tracing a source of a product corresponding to any one or more UIDs, which is provided by the terminal device corresponding to the second server; the second tracking request carries the UID of the product to be traced.

Correspondingly, as shown in fig. 19, the step of, by the second server, in response to a second tracking request sent by the terminal device for a product corresponding to any one or more UIDs, acquiring, from the federation chain, record data under the UID to which the second tracking request is directed, and determining, according to the acquired record data, a second tracking result corresponding to the second tracking request may include:

s1910: and responding to a second tracking request aiming at a product corresponding to any one or more UIDs sent by the terminal equipment, and acquiring recorded data in all circulation links under one or more UIDs carried in the second tracking request from the alliance chain.

S1920: and taking the acquired record data as a second tracking result corresponding to the second tracking request.

It is understood that so-called traceability generally refers to the direction of the production source of the product; in this example, it is considered that the recorded data in all circulation links of the product are generally located at the end of the circulation link, and therefore, it is reasonable to use the recorded data in all circulation links as the second tracking result after tracing.

In the same way, in this example, before feeding back the second tracking result corresponding to the second tracking request to the terminal device that has made the second tracking request, the second server may adjust the content of the second tracking result, which is beneficial for the user of the terminal device to view, so as to feed back the adjusted second tracking result to the terminal device.

In example c, the third second tracking request to be responded by the second server may be a request for querying target tracking information of a product corresponding to any one or more UIDs, which is provided by the terminal device corresponding to the second server; the second tracking request carries the UID of the product to be traced and the name of the target tracking information; also, the number of target tracking information referred to herein may be more than one.

Correspondingly, as shown in fig. 20, the step of, by the second server, in response to a second tracking request sent by the terminal device for a product corresponding to any one or more UIDs, acquiring, from the federation chain, record data under the UID to which the second tracking request is directed, and determining, according to the acquired record data, a second tracking result corresponding to the second tracking request may include:

s2010: and responding to a second tracking request aiming at a product corresponding to any one or more UIDs sent by the terminal equipment, and acquiring recorded data which are carried in the second tracking request and contain target tracking information under the UID from the alliance chain.

S2020: and taking the target tracking information in the acquired record data as a second tracking result corresponding to the second tracking request.

It will be appreciated that in the case of a large amount of recorded data in a single distribution link, a user may only be interested in a certain item or items of tracking information in the recorded data; therefore, the second tracking request and the response manner of the second server to the second tracking request shown in this example just can meet the requirement of the user of the terminal device, so that the second tracking result has better user friendliness.

For example, for a user of a terminal device as a consumer, only the authenticity, production date and shelf life of the product may be of real concern. Therefore, when the user initiates a second tracking request to the second server through the terminal device, the user can select the tracking information concerned by the user for tracking. As shown in fig. 21, fig. 21 is an interface diagram exemplarily showing an APP installed in a terminal device; as can be seen in FIG. 21, a plurality of tracking information may be provided in the interface for user selection; in addition, in specific application, the tracking information that the user may care about may be primarily screened or merged, so that the screened tracking information is displayed to the user in the APP for the user to select. For example, in fig. 12, various tracking information in the transportation link is merged into logistics tracking information.

It should be noted that the example a, the example b, and the example c should not constitute a limitation on the tracking service that the second server can provide, and by transforming the kind of the second tracking request, the second server can also provide more types of tracking services, which is not described herein more for brevity.

In addition, in this embodiment of the application, each second server may be further configured to perform a data analysis task according to one or more predetermined data analysis rules according to the recorded data in the federation chain, so as to obtain a data analysis result corresponding to each data analysis rule.

It will be appreciated that the subject to which the second server belongs is typically a regulatory body of the product, or an industry association of the product, or the like. Therefore, these subjects need to perform data analysis on the recorded data of the products on the federation chain for regulatory responsibility or business requirements.

There may be a plurality of predetermined data analysis rules. In the following, the data analysis task executed by the second server is exemplified by taking several exemplary data analysis rules as examples.

The data analysis rule 1 is used for counting the time spent on fresh food from delivery to the hands of consumers so as to judge whether the food is in the risk of putrefaction due to overlong circulation time and give an early warning to the risk in time; specifically, the production date of the food is obtained from the production link, and the selling time of the food is obtained from the last selling link; in this way, the length of time it takes for the food product to leave the factory until it reaches the consumer's hand can be calculated.

The data analysis rule 2 is used for statistically analyzing the flow direction information of the medicines in each sales link and application consumption link to obtain the distribution condition of the flow direction of the medicines, so that abnormal medicine sales conditions or abnormal medicine use conditions can be found; for example, the number of sales of some specific medicines is obviously abnormal, or the number of usage of some specific medicines is obviously abnormal, etc. And, according to the distribution situation, can also be convenient for retrieving the medicine that has quality problem or safety problem.

The data analysis rule 3 can verify the qualification information of the drugs or foods recorded in the production link for the drugs or foods, so as to find out the drugs or foods with expired qualification.

A data analysis rule 4, for the medicine, when the application flow information of the input product contains the personal information of the patient using the medicine in the application consumption link of the medical institution; by counting the application flow information, the applicable population of the medicine and the age of the applicable population can be determined.

It can be understood that, based on that the second server can obtain the recorded data in all circulation links of the product from the federation chain, the second server can also execute more predetermined data analysis rules to complete more data analysis tasks, which is limited to space and is not described herein.

Optionally, in the product tracking management system provided in the embodiment of the present application, one or more environmental parameter acquisition modules may be integrated in the RFID reader enabled in each circulation link.

Correspondingly, the tracking information to be entered in each circulation link may include: the parameters of the environment where the product is located are collected by one or more environment parameter collection modules integrated in the RFID reader-writer.

Here, the environmental parameter acquisition module that can be integrated in the RFID reader may include one or more of the following modules:

a temperature acquisition module, a humidity acquisition module, a GPS (Global Positioning System) Positioning module, and an optical sensor.

The temperature acquisition module can be used for acquiring the temperature of the environment where the product is located; the humidity acquisition module can be used for acquiring the humidity of the environment where the product is located; the GPS positioning module can be used for acquiring the geographic position of the environment where the product is located; the optical sensor can be used for collecting the brightness of the environment where the product is located. When the RFID reader-writer works, the modules can send the acquired parameters to the processing module of the RFID reader-writer, so that the RFID processing module takes the parameters as information to be recorded and further generates recorded data.

It can be understood that the temperature acquisition module and the humidity acquisition module are integrated in the RFID reader-writer, so that the effect of monitoring the temperature and the humidity of the product in the whole circulation process can be achieved; in specific application, the temperature acquisition module and the humidity acquisition module can be an integrated temperature and humidity acquisition module.

In addition, a GPS positioning module is integrated in the RFID reader-writer, so that the effect of monitoring the geographic position of the product in the whole circulation process can be achieved; the geographical position of the product in the whole circulation process is monitored, so that the logistics information of the product is more accurate; for example, when a product has a quality problem or a security problem and needs to be recalled, the geographic location of the product can be conveniently obtained from a federation chain.

In the embodiment, the optical sensor is integrated in the RFID reader-writer, and the light and shade degree of the circulation link where the product is located is acquired, so that whether a packing box or a transport carriage containing the product is opened or not in the circulation process of the product can be detected. At this time, the RFID reader may be placed in a packing box together with the product. When the packing box is opened, the optical sensor detects that light rays are changed violently, and therefore detected parameters are sent to the processing module of the RFID reader-writer.

In addition, when the communication connection between the RFID reader and the first server is described, the RFID reader and the first server may be connected by wireless communication. When the communication module integrated with the RFID reader-writer is a mobile communication module, the RFID reader-writer can perform long-distance wireless communication with the first server. At this time, even in the transportation link of the product, the RFID reader may send the parameters acquired by the various environmental parameter acquisition modules to the first server. Therefore, the product tracking management system provided by the embodiment of the application can also be suitable for tracking management of products in a cold chain.

In addition, the product tracking management system provided by the embodiment of the application can be further associated with the existing management system in each circulation link. For example, a product tracking management system is associated with an existing production management system in a production link; associating a product tracking management system with the existing cash register systems in each sales link; and associating the product tracking management system with the existing logistics management system in each transportation link, and the like.

The product tracking management system provided by the embodiment of the application has various specific implementation modes for associating with the existing management system in each circulation link.

For example, in an implementation manner, in the product tracking management system provided in the embodiment of the present application, the RFID reader may be integrated with an infrared code scanning module.

Correspondingly, replacing the infrared code scanner started by the existing management system in each circulation link with the RFID reader-writer; then, a management host in an existing management system in each circulation link is added into the alliance chain, and applies for becoming a first server of the alliance chain; therefore, when the RFID reader-writer integrated infrared scanning module is used for scanning the bar code of the product, the RFID label of the product can be synchronously read; then, the existing management system continues to perform subsequent operations, and the product tracking management system provided in the embodiment of the present application continues to complete the uplink operation of the recorded data.

In another implementation manner, a management system of each circulation link may be developed on the basis of the product tracking management system provided in the embodiment of the present application.

During specific development, the RFID label is adopted to replace the existing bar code; replacing the existing infrared scanner with an RFID reader-writer; each circulation link applies for a first server to join the alliance chain; then, developing a management client of the first server; in the workflow of the management client, when tracking information of a product needing to be input into a alliance chain is generated, recording data are generated through a first server and are uploaded to the alliance chain; when the management client needs to perform tracking management on the product, the corresponding tracking information can be acquired from the alliance chain through the first server. The development content of other operations that are implemented by the management client and are unrelated to the federation chain is not the point of the invention of the embodiment of the present application, and details are not described here.

In addition, on the basis of the tracking management system shown in fig. 17, as shown in fig. 22, the product tracking management system provided in the embodiment of the present application may further include: at least one third server 70.

Each third server 70 is configured to verify the registration application when receiving a registration application that any server applies for becoming the first server 20 or the second server 50 joining the federation chain; when the registration application is verified, the first server 20 or the second server 50 which is successfully registered is issued with the identification, and the identification of the first server 20 or the second server 50 which is successfully registered is broadcasted to the existing first server 20 and second server 50.

It is understood that when the third server 70 receives a registration request for either server to become the first server 20 or the second server 50, if the software and hardware conditions of the server meet the requirements of the first server 20 or the second server 50, the third server 70 may issue an identification for the first server 20 or the second server 50 and broadcast the identity information of the server to the first server 20 and the second server 50 that have joined the federation chain; if the software and hardware conditions of the server do not meet the requirements of the first server 20 or the second server 50, the third server 70 may reject the request from the server.

When any server submits a registration request to the third server 70, information of the application subject may be submitted together in the registration request. In this way, the third server 70 can verify the information of the application subject, and after the verification is passed, the third server can continue the verification work of the registration application.

In practice, the third server 70 may be built and managed by a contractor of the tracking management system.

It will be appreciated that the third server 50 is also of the other type of server mentioned above that joins the federation chain.

Optionally, in an implementation manner, the RFID reader enabled in each circulation link may be further configured to:

and after reading the RFID label on the minimum unit level package of the product and obtaining the UID of the product, writing the tracking information of the product to be recorded in the circulation link into the read RFID label.

It can be understood that after the tracking information is written into the RFID tag, a common consumer can read the tracking information in the RFID tag by using a mobile terminal with an NFC function without networking the mobile terminal.

In practical applications, the chip in the RFID tag has a plurality of different storage areas, and the UID and tracking information of the product are stored in the different storage areas, respectively. Wherein, the storage area for storing UID is called label identification number area, and the data in the storage area can not be rewritten by the user of RFID label; and the tracking information can be written to an area rewritable by the user, which is called a user area. Alternatively, when a product code is used to further distinguish between different products and needs to be written to the RFID tag as a kind of tracking information, the product code may be written to another storage area of the RFID tag, which is called an electronic product code area.

In addition, in order to ensure the consistency relationship between the tracking information read by the mobile terminal without networking and the recorded data on the alliance chain, a password verification function can be arranged in the chip of the RFID tag. Before the RFID reader writes the tracking information into the RFID tag, the password needs to be sent first, and only after the password verification is passed, the tracking information can be written into the RFID tag. Thus, the ordinary consumer cannot rewrite the RFID tag using NFC of the mobile terminal.

It is understood that the purpose of writing trace information to the RFID tag is to provide a method for acquiring trace information, which has no influence on the accuracy and security of recorded data in the federation chain even if the RFID tag is rewritten.

Additionally, optionally, in one implementation, to further ensure one product to one code, the RFID tag of each minimum unit level packaged product may be affixed to the tamper evident location of the outer packaging of that product.

In this way, once the product is unsealed, the RFID tag on the outer package is damaged and cannot be reused, so that the possibility that the waste outer package of the product is used for counterfeiting is further reduced.

Based on the same inventive concept, the embodiment of the application also provides a product tracking management method which is applied to a first server started in each circulation link of a product; the first server started in each circulation link is a server of a non-individual main body of the management product in the circulation link, and the first servers started in each circulation link are all added into the same alliance chain. For clarity, the method is described with an interaction diagram of the first server and the RFID reader shown in fig. 23, and the method may include the following steps:

s2301: and the first server receives the recorded data sent by the RFID reader-writer started in the current circulation link and uploads the received recorded data to the alliance chain.

The recorded data is generated by the RFID reader according to the UID of the product and the tracking information of the product to be recorded in the current circulation link; the UID is read by the RFID reader from the RFID tag on the minimum unit level packaging of the product.

S2302: the first server responds to a first tracking request aiming at a target product, and obtains record data related to the target product from the alliance chain; and determining a first tracking result corresponding to the first tracking request according to the acquired record data.

It is understood that the first tracking request responded by the first server may be any one of the four first tracking requests responded by the first server in the tracking management system. The manner of responding to each first trace request by the first server has been described in detail above, and is not described herein again.

In the product tracking management method provided by the embodiment of the application, a first server receives recorded data sent by an RFID reader-writer started in a current circulation link, and uploads the received recorded data to a alliance chain; acquiring record data related to the target product from the alliance chain in response to a first tracking request aiming at the target product; determining a first tracking result corresponding to the first tracking request according to the acquired recording data; the first server added to the alliance chain is a server for managing the non-personal main body of the product in each circulation link of the product, and any first server added to the alliance chain needs to pass authentication, so that recorded data on the alliance chain cannot be tampered. Thus, even if food or medicine is counterfeited by counterfeiting the RFID tag or recycling the outer package, the counterfeit RFID tag or the reusable RFID tag can be effectively identified by tracking the product by using the first server, and the counterfeited product can be effectively identified. Therefore, in the product tracking management method provided by the embodiment of the application, the tracking information of the product is safe and reliable, and correspondingly, the tracking result of the product is relatively credible.

Based on the same invention concept, the embodiment of the application also provides a product tracking information recording method which is applied to the RFID reader started in each circulation link of the product; for clarity, the method is described with reference to fig. 24 by using an interaction diagram of the RFID reader and the first server shown in fig. 24, and the method may include the following steps:

s2401: and reading the RFID label on the minimum unit level package of the product by the RFID reader-writer to obtain the UID of the product.

S2402: and the RFID reader generates recording data according to the tracking information of the product to be recorded in the current circulation link and the read UID.

S2403: and the RFID reader sends the generated recording data to a first server started in the current circulation link.

S2404: the first server uploads the received record data to a federation chain which the first server joins.

The first server started in each circulation link is a server of a non-individual main body of a management product in the circulation link, and the first server started in each circulation link is added into a alliance chain.

In addition, the detailed description of the specific work flow of the RFID reader has already been described above, and is not repeated here.

In the method for recording the tracking information of the product, the RFID reader started in each circulation link is used for reading the RFID label on the minimum unit level package of the product to obtain the UID of the product; generating record data according to the tracking information of the product to be recorded in the circulation link and the read UID; writing the generated recording data into the RFID label and sending the recording data to a first server started in the circulation link; the recorded data is then uploaded into the federation chain by a first server enabled in the distribution link. Because the UID of the RFID tag has uniqueness and the recorded data in the alliance chain cannot be tampered, the method for recording the tracking information of the product can ensure the safety and the effectiveness of the tracking information of the product.

In addition, in the scheme, the RFID label is attached to the minimum unit level package of the product; therefore, the RFID reader-writer reads the RFID label on the outer package of the product, and the tracking information of the product packaged at the minimum unit level can be recorded.

The embodiment of the application also provides a product tracking method, which is applied to the terminal equipment; as shown in fig. 25, the method may include the steps of:

s2501: the method comprises the steps that terminal equipment receives a first tracking request aiming at a target product and input by a user; the first tracking request carries the UID of the target product.

S2502: the terminal device sends the first tracking request to a first server in the product tracking management system.

S2503: and the first server responds to the first tracking request, acquires the recorded data under the UID from the alliance chain maintained by the product tracking management system, and determines a first tracking result corresponding to the first tracking request according to the acquired recorded data.

S2504: the first server returns a first tracking result.

S2505: the terminal equipment outputs a first tracking result.

The product tracking management system is a system for tracking and managing information generated in each circulation link of a product by using a federation chain, and may specifically be any one of the product tracking management systems shown in fig. 1, 9, 16(a), 17 or 22.

In the tracking method, a user can input the first tracking request in an APP which is set in a terminal device and is dedicated to product tracking management. Alternatively, the user may also enter the first trace request in a functional module integrated in an existing integrated services class APP in the terminal device. Fig. 26(a) is an interface diagram illustrating an APP installed in a terminal device connected to a first server for interacting with the first server; as shown in fig. 26(a), two ways of initiating the first trace request are provided in the interface; in the first mode, a user can manually input the UID of the product in an input box, and click 'start' to initiate a first tracking request; in the second mode, the RFID tag of the product is attached to the terminal device, and the UID of the product is automatically read from the RFID tag of the product by the terminal device, thereby initiating the first tracking request.

Alternatively, in a terminal device, the user may input the first tracking request to the terminal device by clicking a key provided by the terminal device. FIG. 26(b) is a schematic diagram illustrating an operation panel of a terminal device connected to a first server in a sales link; it can be seen that in the operation panel, 2 ways of initiating the first trace request are provided; wherein, clicking the first button can inquire the authenticity of the product; clicking the second button can obtain the sales information of the product.

In another terminal device, when a user puts an RFID label on an outer package of a product close to a sensing area of the terminal device, a first tracking request is input to the terminal device. Fig. 26(c) is a schematic view illustrating an operation panel of such a terminal device connected to the first server.

In step S2505, there are various specific ways in which the terminal device outputs the first tracking result. For example, when the user sends the first trace request through the APP, the terminal device may correspondingly present the first trace result to the user in the APP.

Or, the terminal device may output the first tracking result to the user in a voice broadcast or screen output manner.

It is understood that, in the tracking method, the first tracking request received by the terminal device is the second type of first tracking request responded by the first server. The manner in which the first server responds to such a first trace request has already been described in detail above, and is not described here again.

In the product tracking method provided by the embodiment of the application, the terminal device sends a first tracking request input by a user to the first server, so that the first server responds to the first tracking request, acquires the recorded data under the UID from the added alliance chain, determines a first tracking result corresponding to the first tracking request according to the acquired recorded data, and returns the first tracking result. In this process, since the recorded data on the federation chain cannot be tampered, the recorded data of the product acquired by the first server is relatively safe and reliable, and therefore, in the product tracking method provided by the embodiment of the application, the first tracking result of the product, which is output to the user by the terminal device, is relatively credible.

For clarity of the solution, the method is described with an interaction diagram of the terminal device and the second server shown in fig. 27. As shown in fig. 27, the method may include the steps of:

s2701: and the terminal equipment receives a second tracking request which is input by the user and aims at the product corresponding to any one or more UIDs.

Wherein the user can input the second trace request in an APP dedicated to trace management of the product provided in the terminal device. Alternatively, the user may also enter the second trace request in a functional module integrated in an existing service class APP in the terminal device.

Alternatively, in a terminal device, the user may input the second tracking request to the terminal device by clicking a key provided by the terminal device.

In another terminal device, when a user puts the RFID label on the outer package of the product close to the sensing area of the terminal device, the second tracking request is input to the terminal device.

S2702: and the terminal equipment sends the second tracking request to a second server in the product tracking management system.

S2703: and the second server responds to the second tracking request, acquires the recorded data under the one or more UIDs from the alliance chain maintained by the product tracking management system, and determines a second tracking result corresponding to the second tracking request according to the acquired recorded data.

S2704: the second server returns a second tracking result.

The product tracking management system is a system for tracking and managing information generated in each circulation link of a product by using a federation chain, and may specifically be any one of the product tracking management systems shown in fig. 16(a), 17, and 22.

S2705: and the terminal equipment outputs a second tracking result.

In this step, there are various specific ways in which the terminal device outputs the second tracking result. For example, when the user sends the second trace request through the APP, the terminal device may correspondingly present the second trace result to the user in the APP.

Or, the terminal device may output the second tracking result to the user in a voice broadcast or screen output manner.

It is to be understood that, in the tracking method, the second tracking request may be any one of three second tracking requests to which the second server responds in the tracking management system described above. The manner in which the second server responds to each second tracking request has already been described in detail above, and is not described here again.

In the product tracking method provided by the embodiment of the application, the terminal device sends a second tracking request input by the user to the second server, so that the second server responds to the second tracking request, acquires the recorded data under the one or more UIDs from the added alliance chain, determines a second tracking result corresponding to the second tracking request according to the acquired recorded data, and returns the second tracking result. In this process, since the recorded data on the federation chain cannot be tampered, the recorded data of the product acquired by the second server is relatively safe and reliable, and therefore, in the product tracking method provided by the embodiment of the application, the second tracking result of the product, which is output to the user by the terminal device, is relatively credible.

The embodiment of the application also provides a computer readable storage medium. In the computer-readable storage medium a computer program is stored which, when executed by a processor, performs method steps comprising:

method 1, a product tracking management method, applied to a first server enabled in each circulation link of a product; the first server started in each circulation link is a server of a non-individual main body of a management product in the circulation link, and the first servers started in each circulation link are all added into the same alliance chain; the method 1 comprises the following steps:

receiving recorded data sent by an RFID reader-writer started in the current circulation link, and uploading the received recorded data to a alliance chain; the recorded data is generated by an RFID reader-writer according to the unique identification of the product and the tracking information of the product to be recorded in the current circulation link; the unique identification is read by an RFID reader from an RFID tag on a minimum unit level package of the product;

acquiring record data related to the target product from the alliance chain in response to a first tracking request aiming at the target product; and determining a first tracking result corresponding to the first tracking request according to the acquired record data.

The method 2 is a tracking information recording method of a product, which is applied to an RFID reader-writer started in each circulation link of the product, and the method 2 comprises the following steps:

sending the generated recording data to a first server started in a current circulation link so that the first server uploads the received recording data to a federation chain joined by the first server;

Method 3, a product tracking method, applied to a terminal device, the method 3 comprising the steps of:

receiving a first tracking request for a target product input by a user; the first tracking request carries the unique identification of the target product;

sending the first tracking request to a first server in the product tracking management system, so that the first server responds to the first tracking request, acquires recorded data under the unique identifier from a alliance chain maintained by the product tracking management system, determines a first tracking result corresponding to the first tracking request according to the acquired recorded data, and returns the first tracking result; the product tracking management system is a system for tracking and managing information generated in each circulation link of a product by utilizing a alliance chain;

and outputting a first tracking result.

Method 4, a product tracking method, applied to a terminal device, the method 4 comprising the steps of:

sending the second tracking request to a second server in the product tracking management system, so that the second server responds to the second tracking request, acquires the recorded data under the one or more unique identifiers from a alliance chain maintained by the product tracking management system, determines a second tracking result corresponding to the second tracking request according to the acquired recorded data, and returns the second tracking result; the product tracking management system is a system for tracking and managing information generated in each circulation link of a product by utilizing a alliance chain;

and outputting a second tracking result.

Alternatively, the computer-readable storage medium may be a Non-Volatile Memory (NVM), such as at least one disk Memory.

Optionally, the computer readable memory may also be at least one memory device located remotely from the processor.

In a further embodiment of the present application, there is also provided a computer program product comprising instructions which, when run on a computer, cause the computer to perform the method steps of any of the methods described above.

The embodiment of the application also provides a product tracking management device, which is applied to a first server started in each circulation link of a product; the first server started in each circulation link is a server of a non-individual main body of a management product in the circulation link, and the first servers started in each circulation link are all added into the same alliance chain; the device comprises: a processor and a memory, the memory storing one or more computer programs, the processor when executing the computer programs implementing the steps of:

The embodiment of the present application further provides a product tracking information recording device, which is applied to an RFID reader enabled in each circulation link of a product, and the device includes: a processor and a memory, the memory storing one or more computer programs, the processor when executing the computer programs implementing the steps of:

The embodiment of the present application further provides a product tracking apparatus, which is applied to a terminal device, and the apparatus includes: a processor and a memory, the memory storing one or more computer programs, the processor when executing the computer programs implementing the steps of:

and outputting the first tracking result.

In the product tracking device, the mentioned product tracking management system may be the product tracking management system shown in fig. 1, fig. 9, fig. 16(a), fig. 17 or fig. 22.

and outputting the second tracking result.

The product tracking management system may be the product tracking management system shown in fig. 16(a), 17 or 22.

For the method/apparatus/storage medium/computer program product embodiment, since it is substantially similar to the system embodiment, the description is relatively simple, and for the relevant points, reference may be made to the partial description of the system embodiment.

It should be noted that the terms "first" and "second" are used for descriptive purposes only and are not to be construed as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more features. In the description of the present application, "a plurality" means two or more unless specifically limited otherwise.

In the description herein, reference to the description of the term "one embodiment," "some embodiments," "an example," "a specific example," or "some examples," etc., means that a particular feature or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the present application. In this specification, the schematic representations of the terms used above are not necessarily intended to refer to the same embodiment or example. Furthermore, the particular features or characteristics described may be combined in any suitable manner in any one or more embodiments or examples. Furthermore, various embodiments or examples described in this specification can be combined and combined by those skilled in the art.

While the present application has been described in connection with various embodiments, other variations to the disclosed embodiments can be understood and effected by those skilled in the art in practicing the claimed application, from a review of the drawings, the disclosure, and the appended claims. In the claims, the word "comprising" does not exclude other elements or steps, and the word "a" or "an" does not exclude a plurality. A single processor or other unit may fulfill the functions of several items recited in the claims. The mere fact that certain measures are recited in mutually different dependent claims does not indicate that a combination of these measures cannot be used to advantage.

The foregoing is a more detailed description of the present application in connection with specific preferred embodiments and it is not intended that the present application be limited to these specific details. For those skilled in the art to which the present application pertains, several simple deductions or substitutions may be made without departing from the concept of the present application, and all should be considered as belonging to the protection scope of the present application.

Claims

1. A product tracking management system, comprising: the RFID reader-writer and the first server are started in each circulation link of the product; the first server started in each circulation link is a server for managing the non-individual main body of the product in the circulation link, and the first servers started in each circulation link are all added into the same alliance chain;

2. The system of claim 1, further comprising: at least one second server joining the federation chain, the second server having a different principal than the first server;

3. The system according to claim 2, wherein each of the at least one second server is further configured to perform a data analysis task according to one or more predetermined data analysis rules according to the recorded data in the federation chain, so as to obtain a data analysis result corresponding to each data analysis rule.

4. A system according to any one of claims 1 to 3, wherein each circulation segment of the product comprises:

5. The system of claim 4, wherein each circulation segment further comprises:

6. The system of claim 4, wherein the tracking information of the product to be entered in each circulation segment comprises: current circulation state information of the product; the circulation state information is information representing a circulation link where the product is located.

7. The system of claim 4, wherein the tracking information of the product to be entered in the production link comprises:

8. The system according to claim 1, wherein one or more environmental parameter acquisition modules are integrated in the RFID reader;

9. The system of claim 1, wherein the first trace request responded by the first server enabled in each distribution link is initiated by a terminal device connected to the first server or an off-link server not joined in the federation chain and communicating with the first server;

10. The system of claim 1, wherein the enabled RFID reader in each circulation segment is further configured to:

11. The system of claim 1, 2 or 9, further comprising: a third server joining the federation chain;

12. The system of claim 1, wherein the RFID tag of each minimum unit level packaged product is affixed to a tamper evident location of an outer package for the product.

13. A product tracking management method is characterized in that the method is applied to a first server started in each circulation link of a product; the first server started in each circulation link is a server of a non-individual main body of a management product in the circulation link, and the first servers started in each circulation link are all added into the same alliance chain;

the method comprises the following steps:

14. A method for recording tracking information of a product, which is applied to an RFID reader enabled in each circulation link of the product, the method comprising:

15. A product tracking method is applied to a terminal device, and comprises the following steps:

and outputting the first tracking result.

16. A product tracking method is applied to a terminal device, and comprises the following steps:

and outputting the second tracking result.