Identification chain tracing method and system

Abstract

The present application is applied to the technical field of information. Disclosed are an identification chain tracing method and system. A service platform processes a query request from a management system of a target enterprise, and then coordinates management systems of other enterprises to provide target data of a target product that is related to upstream and downstream information of the product. In this way, the function of querying upstream and downstream information of a product is realized. In addition, by supporting progressive queries between a plurality of IDs by means of a chained query, multi-level tracing of products and components thereof and tracking of product flow can be implemented.

Description

Traceability methods and systems for identification chains Technical Field

[0001] This application relates to the field of information technology, and in particular to an identification chain traceability method and system. Background Technology

[0002] Existing product information query systems can only provide information about the product itself, but not about its upstream and downstream components. For example, after scanning a QR code on a refrigerator, a user can only obtain information such as the refrigerator's model, manufacturing date, and warranty period, but cannot obtain information about the individual components that make up the refrigerator (e.g., upstream products such as circuit boards and chips). Similarly, a user might want to know which downstream product a particular circuit board is integrated into and obtain information about that downstream product. Summary of the Invention

[0003] To enable the query function of upstream and downstream information of products, this application provides an identification chain traceability method and system.

[0004] In a first aspect, embodiments of this application provide an identifier chain tracing method. The method is executed by a service platform and includes: receiving a first upstream query request from the management system of a target enterprise; the first upstream query request being generated by the target enterprise's management system in response to an original upstream query request from a user terminal; the original upstream query request indicating a query for the association information of an upstream product of a target product, the original upstream query request carrying the ID of the target product; the first upstream query request indicating a query for the association information of the upstream product, the first upstream query request carrying the ID of the upstream product; determining the upstream enterprise to which the upstream product belongs based on the ID of the upstream product; sending a second upstream query request to the management system of the upstream enterprise; the second upstream query request indicating a query for the association information of the upstream product, the second upstream query request carrying the ID of the upstream product; receiving the association information of the upstream product returned by the management system of the upstream enterprise; and returning the association information of the upstream product to the user terminal. The management system is used to manage the association information of internal products; for internal products containing upstream products, the management system is also used to manage the composition information of the internal product, the composition information including the ID of the internal product and the IDs of each upstream product of the internal product.

[0005] In some embodiments, determining the upstream enterprise to which the upstream product belongs based on the ID of the upstream product includes: determining a first identification system to which the ID of the upstream product belongs, and determining a first identification resolution system corresponding to the first identification system; sending the ID of the upstream product to the first identification resolution system; and receiving a first resolution result from the first identification resolution system, wherein the first resolution result indicates the upstream enterprise to which the upstream product belongs.

[0006] Secondly, embodiments of this application provide an identifier chain tracing method. The method is executed by a service platform and includes: receiving a first downstream query request from the management system of a target enterprise; the first downstream query request is generated by the management system of the target enterprise in response to an original downstream query request from a user terminal; the original downstream query request indicates querying the ID of a downstream product of the target product, and the original downstream query request carries the ID of the target product; the first downstream query request indicates querying the ID of the downstream product, and the first downstream query request carries the ID of the target product; determining a second identifier system to which the ID of the target product belongs, and determining one or more enterprises using the second identifier system; sending a second downstream query request to the management systems of the one or more enterprises respectively; the second downstream query request indicates querying the ID of the downstream product, and the second downstream query request carries the ID of the target product; receiving the ID of the downstream product returned by the management system of the downstream enterprise to which the downstream product belongs, the downstream enterprise being one of the one or more enterprises; and returning the ID of the downstream product to the user terminal. Wherein, for an internal product containing upstream products, the management system is used to manage the composition information of the internal product, the composition information including the ID of the internal product and the IDs of each upstream product of the internal product.

[0007] In some embodiments, the original downstream query request, the first downstream query request, and the second downstream query request further indicate a query for the association information of the downstream product, and the management system is also used to manage the association information of internal products. The method further includes: receiving the association information of the downstream product returned by the management system of the downstream enterprise; and returning the association information of the downstream product to the user terminal.

[0008] Thirdly, embodiments of this application provide an identifier chain tracing method. The method is executed by a service platform and includes: receiving a third downstream query request from the management system of a target enterprise; the third downstream query request being generated by the target enterprise's management system in response to an original downstream query request from a user terminal; the original downstream query request indicating a query for the ID of a downstream product of the target product, the original downstream query request carrying the ID of the target product; the third downstream query request indicating a query for the ID of the downstream product from the management system of the downstream enterprise, the third downstream query request carrying the ID of the target product; sending a fourth downstream query request to the management system of the downstream enterprise, the fourth downstream query request indicating a query for the ID of the downstream product, the fourth downstream query request carrying the ID of the target product; receiving the ID of the downstream product returned by the management system of the downstream enterprise; and returning the ID of the downstream product to the user terminal. Wherein, for an internal product containing upstream products, the management system manages the composition information of the internal product, the composition information including the ID of the internal product and the IDs of each upstream product of the internal product.

[0009] In some embodiments, the original downstream query request, the third downstream query request, and the fourth downstream query request further indicate a query for the association information of the downstream product, and the management system is also used to manage the association information of internal products. The method further includes: receiving the association information of the downstream product returned by the management system of the downstream enterprise; and returning the association information of the downstream product to the user terminal.

[0010] Fourthly, this application provides an identification chain traceability system. The system is implemented in a service platform and includes a first receiving module, a first determining module, and a first sending module. The first receiving module is used to receive a first upstream query request from the management system of a target enterprise. The first upstream query request is generated by the target enterprise's management system in response to an original upstream query request from a user terminal. The original upstream query request indicates a query for the association information of upstream products of the target product, and carries the ID of the target product. The first upstream query request indicates a query for the association information of the upstream product, and carries the ID of the upstream product. The first determining module is used to determine the upstream enterprise to which the upstream product belongs based on the ID of the upstream product. The first sending module is further used to send a second upstream query request to the management system of the upstream enterprise, the second upstream query request indicating a query for the association information of the upstream product. The second upstream query request indicates a query for the association information of the upstream product, and carries the ID of the upstream product. The first receiving module is also used to receive the association information of the upstream product returned by the management system of the upstream enterprise. The first sending module is also used to return the association information of the upstream product to the user terminal. The management system is used to manage the association information of internal products. For internal products that include upstream products, the management system is also used to manage the composition information of the internal product, which includes the ID of the internal product and the IDs of each upstream product of the internal product.

[0011] Fifthly, embodiments of this application provide an identification chain traceability system. The system is implemented in a service platform and includes a second receiving module, a second determining module, and a second sending module. The second receiving module receives a first downstream query request from the management system of a target enterprise. The first downstream query request is generated by the target enterprise's management system in response to an original downstream query request from a user terminal. The original downstream query request indicates a query for the ID of a downstream product of the target product, and carries the ID of the target product. The second determining module determines the second identification system to which the ID of the target product belongs, and determines one or more enterprises using the second identification system. The second sending module sends a second downstream query request to the management systems of the one or more enterprises respectively. The second downstream query request indicates a query for the ID of the downstream product, and carries the ID of the target product. The second receiving module also receives the ID of the downstream product returned by the management system of the downstream enterprise to which the downstream product belongs, where the downstream enterprise is one of the one or more enterprises. The second sending module also returns the ID of the downstream product to the user terminal. Specifically, for internal products that include upstream products, the management system is used to manage the composition information of the internal product, which includes the ID of the internal product and the IDs of each upstream product of the internal product.

[0012] In some embodiments, the original downstream query request, the first downstream query request, and the second downstream query request further indicate a query for the association information of the downstream product, and the management system is further configured to manage the association information of internal products. The second receiving module is further configured to receive the association information of the downstream product returned by the management system of the downstream enterprise. The second sending module is further configured to return the association information of the downstream product to the user terminal.

[0013] Sixthly, embodiments of this application provide an identification chain traceability system. The system is implemented in a service platform and includes a third receiving module and a third sending module. The third receiving module is used to receive a third downstream query request from the management system of a target enterprise. The third downstream query request is generated by the management system of the target enterprise in response to an original downstream query request from a user terminal. The original downstream query request indicates querying the ID of a downstream product of the target product, and carries the ID of the target product. The third downstream query request indicates querying the ID of the downstream product from the management system of the downstream enterprise, and carries the ID of the target product. The third sending module is used to send a fourth downstream query request to the management system of the downstream enterprise. The fourth downstream query request indicates querying the ID of the downstream product, and carries the ID of the target product. The third receiving module is also used to receive the ID of the downstream product returned by the management system of the downstream enterprise. The third sending module is also used to return the ID of the downstream product to the user terminal. Specifically, for an internal product that includes upstream products, the management system manages the composition information of the internal product, which includes the ID of the internal product and the IDs of each upstream product of the internal product.

[0014] In some embodiments, the original downstream query request, the third downstream query request, and the fourth downstream query request further indicate a query for the association information of the downstream product, and the management system is further configured to manage the association information of internal products. The third receiving module is further configured to receive the association information of the downstream product returned by the management system of the downstream enterprise. The third sending module is further configured to return the association information of the downstream product to the user terminal.

[0015] In a seventh aspect, embodiments of this application provide a service platform including a processor and a memory. The memory stores a computer program, and when the processor executes the computer program, it implements the identifier chain tracing method as described in the first, second, or third aspect.

[0016] The technical solution provided in this application has the following advantages compared with the prior art:

[0017] (1) The service platform processes query requests from the target company's management system, and then coordinates with the management systems of other companies to provide target data related to the upstream and downstream information of the target product. In this way, the query function for upstream and downstream product information is realized.

[0018] (2) By supporting progressive queries between multiple IDs through chained queries, multi-level traceability of products and their components and tracking of product flow can be realized.

[0019] (3) Under the coordination of the service platform, different enterprises (especially those without cooperative relationship) do not need to exchange internal sensitive data, which can not only avoid the leakage of data privacy (such as trade secrets), but also reduce system complexity (for example, no need to design cross-system authentication and access authorization). Attached Figure Description

[0020] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0021] Figure 1 is a schematic diagram of the application scenario for querying product upstream and downstream information.

[0022] Figure 2 is an exemplary flowchart of the identification chain tracing method provided in an embodiment of this application.

[0023] Figure 3 is an exemplary flowchart of the product ID parsing process provided in an embodiment of this application.

[0024] Figure 4 is an exemplary flowchart of the identification chain tracing method provided in the embodiments of this application.

[0025] Figure 5 is an exemplary flowchart of the identification chain tracing method provided in the embodiments of this application.

[0026] Figure 6 is an exemplary block diagram of the identification chain traceability system provided in an embodiment of this application.

[0027] Figure 7 is a first exemplary block diagram of the identification chain traceability system provided in an embodiment of this application.

[0028] Figure 8 is a second exemplary block diagram of the identification chain traceability system provided in an embodiment of this application.

[0029] Figure 9 is a schematic diagram of the composition of the service platform provided in the embodiments of this application. Detailed Implementation

[0030] To better understand the above-mentioned objectives, features, and advantages of this application, embodiments of this application will be further described below. It should be noted that, unless otherwise specified, the embodiments and features described herein can be combined with each other.

[0031] Numerous specific details are set forth in the following description to provide a thorough understanding of this application, but this application may also be implemented in other ways than those described herein. Clearly, the embodiments described in the specification are only a portion of, and not all, of the embodiments of this application.

[0032] Unless otherwise specified, the upstream products of the target product in this article refer to products that have a direct integration relationship with the target product. For example, if a refrigerator contains a circuit board, and a circuit board contains a chip, then the upstream product of the refrigerator refers to the circuit board, and the upstream product of the circuit board refers to the chip.

[0033] The products described in this application include specific commodities, components of those commodities, and integrated hardware and software.

[0034] Figure 1 illustrates an application scenario for querying upstream and downstream product information. As shown in Figure 1, application scenario 100 includes one or more user terminals 110, a management system 120 for one or more enterprises, and a service platform 130. In some embodiments, the management system 120 includes an OT (Operational Technology) system and / or an IT (Information Technology) system. For illustrative purposes only, Figure 1 shows only one user terminal 110 and the management system 120 for three enterprises (Enterprise A, Enterprise B, and Enterprise C).

[0035] User terminal 110 can send a query request to management system 120 to obtain target data for the target product. Target data for the target product includes, but is not limited to, the associated information of the target product, the ID of the upstream product (e.g., circuit board) of the target product (e.g., a refrigerator), the associated information of the upstream product (e.g., circuit board) of the target product (e.g., a refrigerator), the ID of the downstream product of the target product, and the associated information of the downstream product of the target product. In some embodiments, the associated information mentioned herein includes static data and historical events, wherein static data has long-term stability (does not change over a long period), and historical events refer to associated events that have occurred. Specifically, static data may include name, model, serial number, production date, place of production, warranty period, etc., and historical events may include factory release events, inspection events, repair events, etc.

[0036] The management system 120 is used to manage the association information of internal products. For an internal product that includes upstream products (e.g., a refrigerator includes a circuit board), the management system 120 is also used to manage the composition information of that internal product (e.g., the refrigerator), which includes the ID of the internal product (e.g., the refrigerator) and the IDs of each upstream product (e.g., the circuit board). As an example, assuming the refrigerator's ID is IDa and the circuit board's ID is IDb, the refrigerator's composition information can be represented as IDa-IDb. If product a contains multiple components, the IDs of these components can be separated by specific symbols (usually characters disabled in the ID). For example, if product a contains product b1 and product b2, with product b1's ID being IDb1 and product b2's ID being IDb2, then product a's composition information can be represented as IDa-IDb1;IDb2.

[0037] The management system 120 can store the association information and composition information (if any) of internal products locally, or it can store the association information and composition information (if any) of internal products to a remote server, such as a private cloud server.

[0038] The management system 120 is also used to process query requests from user terminal 110.

[0039] For query requests that do not involve upstream or downstream product information, assuming the target product is an internal product of the target company, the target company's management system 120 can directly retrieve the target product's associated information upon receiving the query request. As an example, a user can scan the target product's QR code using a user terminal 110. The QR code can be displayed on the product itself or through other means (e.g., product manual, warranty card, etc.). After parsing the QR code, the user terminal 110 obtains the access address for the target product's associated information, which may include the target product's ID. Then, the user terminal 110 generates a query request based on this access address and sends it to the target company's management system 120. Upon receiving the query request, the target company's management system 120 returns the target product's associated information to the user terminal 110.

[0040] For query requests involving upstream / downstream product information, if the upstream / downstream products of the target product are not internal products of the target enterprise, the target enterprise's management system 120 will be unable to find the upstream / downstream information (e.g., upstream product association information, downstream product ID and association information) after receiving the query request. In this case, the target enterprise's management system 120 can send a query request to the service platform 130, which will then coordinate with the management systems 120 of other enterprises to provide the target data involving upstream / downstream product information.

[0041] The service platform 130 is used to process query requests from the management system 120 of the target enterprise, and then coordinate the management systems 120 of other enterprises to provide target data involving upstream and downstream information of the target product, such as the ID of the upstream product (such as a circuit board) of the target product (such as a refrigerator), the association information of the upstream product (such as a circuit board) of the target product (such as a refrigerator), the ID of the downstream product (such as a circuit board and a refrigerator) of the target product (such as a chip), and the association information of the downstream product (such as a circuit board and a refrigerator) of the target product (such as a chip).

[0042] In some embodiments, the service platform 130 is also configured to provide the parsing result of the product ID, the parsing result indicating the enterprise to which the corresponding product belongs. It is understood that some identification systems have the ability to identify the enterprise to which a product belongs; correspondingly, a specific field of the product ID using such an identification system represents the enterprise to which the product belongs.

[0043] The ID (Identifier) ​​mentioned in this document refers to an alphanumeric string containing IAC, CIN, and other fields used to identify physical or virtual objects. The IAC field represents the Issuing Agency Code assigned according to the ISO / IEC 15459 standard, and the CIN represents the Company Identification Number, used to identify a specific company. When the IAC is MA, it indicates that the issuer of the identifier is ZIIOT; when the IAC is 0-9, it indicates that the issuer of the identifier is GS1; when the IAC is "J", it indicates that the issuer of the identifier is UPU (Universal Postal Union). In some embodiments, application scenario 100 further includes one or more identifier resolution systems 140, each corresponding to one or more identifier systems. For product IDs using a specific identifier system, the service platform 130 can obtain the resolution result of the product ID by accessing the corresponding identifier resolution system 140. As an example only, Figure 1 shows three identifier resolution systems 140, namely the MA resolution system corresponding to the MA system, the GS1 resolution system corresponding to the GS1 system, and the UPU resolution system corresponding to the UPU system.

[0044] In an alternative embodiment, the service platform 130 itself has identifier resolution capabilities, which is equivalent to the service platform 130 having one or more identifier resolution systems built in.

[0045] For more details about the user terminal 110, management system 120, service platform 130 and identifier resolution system 140, please refer to Figures 2 to 9 and their related descriptions.

[0046] Figure 2 is an exemplary flowchart of the identifier chain tracing method provided in this application embodiment. Process 200 is executed by the service platform 130. As shown in Figure 2, process 200 includes the following steps.

[0047] Step 210: Receive the first upstream query request from the target company's management system.

[0048] The first upstream query request is generated by the target company's management system in response to the original upstream query request from the user terminal. The original upstream query request indicates a query for the association information of the target product's upstream products (hereinafter referred to as upstream products), and carries the ID of the target product. The first upstream query request indicates a query for the association information of the upstream products, and carries the ID of the upstream products.

[0049] Upon receiving the original upstream query request, the target company's management system first determines the upstream product ID based on the target product's ID and its component information. Then, the management system determines whether the upstream product is an internal product based on its ID. If the upstream product is determined to be an internal product, the management system returns the upstream product's association information to the user terminal. If the upstream product is determined not to be an internal product, the management system sends a first upstream query request to the service platform.

[0050] Of course, the target company's management system can also send the first upstream query request directly to the service platform after determining the ID of the upstream product.

[0051] Step 220: Determine the upstream enterprise to which the upstream product belongs based on the upstream product ID.

[0052] In some embodiments, the service platform can obtain the resolution results of the upstream product's ID using an external identifier resolution system; the specific resolution process is shown in Figure 3 and its related description. In alternative embodiments, the service platform can resolve the upstream product's ID itself.

[0053] Step 230: Send a second upstream query request to the upstream enterprise's management system.

[0054] The second upstream query request instructs the user to query the association information of an upstream product, and carries the ID of the upstream product. Since the upstream product is an internal product of the upstream enterprise, the upstream enterprise's management system can retrieve the association information of the upstream product upon receiving the second upstream query request. Therefore, the upstream enterprise's management system returns the association information of the upstream product to the user terminal.

[0055] Step 240: Receive the upstream product association information returned by the upstream enterprise's management system, and return the upstream product association information to the user terminal.

[0056] Referring to the foregoing embodiments, the management system is used to manage the association information of internal products. For internal products that include upstream products, the management system is also used to manage the composition information of the internal product, which includes the ID of the internal product and the IDs of each upstream product of the internal product.

[0057] At this point, with the coordination of the service platform, the user terminal obtains the upstream product association information of the target product.

[0058] As an example, assume that product a and product b are internal products of company A and company B respectively (denoted as IDa and IDb). Product a contains product b, with product a as the target product and product b as the upstream product. For example, a refrigerator contains a circuit board. Users can view the association information of product a and its upstream products by scanning a QR code. Specifically, the user terminal generates an original upstream query request carrying IDa based on the QR code parsing result and sends it to company A's management system. After receiving the original upstream query request carrying IDa, company A's management system determines IDb based on IDa and the composition information of product a (denoted as IDa-IDb). Company A can then determine whether product b is an internal product based on IDb. If product b is determined not to be an internal product, company A's management system sends a second upstream query request carrying IDb to the service platform. The service platform determines company B to which product b belongs based on IDb and sends a second upstream query request carrying IDb to company B. After receiving the second upstream query request carrying IDb, company B returns the association information of product b to the service platform. Finally, the service platform returns the associated information of product b to the user's terminal.

[0059] To enable multi-level upstream product queries, the service platform can repeatedly execute process 200. For example, assume: products a, b, and c are internal products of companies A, B, and C respectively (denoted as IDa, IDb, and IDc). Product a contains product b (e.g., a refrigerator contains a circuit board), and product b contains product c (e.g., a circuit board contains a chip). After receiving a second upstream query request carrying IDb, company B's management system determines IDc based on IDb and the composition information of product b (denoted as IDb-IDc). Company B can then determine whether product c is an internal product based on IDc. If product c is determined not to be an internal product, company B's management system sends a first upstream query request carrying IDc to the service platform. The service platform determines the company C to which product c belongs based on IDc and sends a second upstream query request carrying IDc to company C. After receiving the second upstream query request carrying IDc, company C returns the association information of product c to the service platform. Finally, the service platform returns the association information of product c to the user terminal. It is worth noting that in the above multi-level upstream product query process, the target product changes from product a to product b, and correspondingly, the target company changes from company A to company B, and the upstream company changes from company B to company C.

[0060] It is understandable that the service platform can continue to search until there are no upstream products for the target product, and then package and send the associated information of the initial target product (such as product a) and its various levels of components (such as product b and product c) to the user terminal.

[0061] With the help of query process 200, the chained query supports progressive queries between multiple IDs, enabling multi-level traceability of products and their components, which helps enterprises analyze and locate quality problems.

[0062] Figure 3 is an exemplary flowchart of the product ID parsing process provided in an embodiment of this application. As shown in Figure 3, step 220 includes the following sub-steps.

[0063] Step 221: Determine the first identification system to which the ID of the upstream product belongs, and determine the first identification resolution system corresponding to the first identification system.

[0064] The service platform can determine the identification system to which an ID belongs by identifying specific fields of the ID (e.g., the first field). For example, according to the ISO / IEC 15459 standard, the upstream product ID can be determined to belong to the MA identification system based on the IAC field (Issuing Agency Code) "MA" of the ID; when the IAC is 0 to 9, it means that the corresponding identification belongs to the GS1 identification system; when the IAC is "J", it means that the corresponding identification belongs to the UPU identification system.

[0065] Step 222: Send the ID of the upstream product to the first identifier resolution system.

[0066] The first identifier resolution system can generate a first resolution result based on the ID of the upstream product and return the first resolution result to the service platform. The first resolution result indicates the upstream enterprise to which the upstream product belongs.

[0067] Step 223: Receive the first resolution result from the first identifier resolution system.

[0068] Referring to Figure 1, assuming the upstream product's ID belongs to the MA system, the service platform 130 sends the upstream product's ID to the MA resolution system 140. That is, the first identifier resolution system is the MA resolution system. Subsequently, the service platform receives the first resolution result from the MA resolution system 140.

[0069] Figure 4 is an exemplary flowchart of the identifier chain tracing method provided in this application embodiment. Process 300 is executed by the service platform 130. As shown in Figure 4, process 300 includes the following steps.

[0070] Step 310: Receive the first downstream query request from the target company's management system.

[0071] The first downstream query request is generated by the target company's management system in response to the original downstream query request from the user terminal. The original downstream query request indicates that the target product's downstream product ID (hereinafter referred to as downstream product) is being queried, and the original downstream query request carries the target product ID. The first downstream query request indicates that the target product's ID is being queried, and the first downstream query request carries the target product ID.

[0072] Upon receiving the original downstream query request, the target company's management system first checks the composition information of its internal products to determine whether the target product's downstream products are internal products. If the downstream products are determined to be internal products, the target company's management system returns the downstream product's association information to the user terminal. If the downstream products are determined not to be internal products, the target company's management system sends a first downstream query request to the service platform.

[0073] It should be noted that Process 300 applies to situations where the downstream product is not an internal product of the target company and useful information about the downstream product is unavailable (such as the downstream company to which the downstream product belongs).

[0074] Step 320: Determine the second identification system to which the ID of the target product belongs, and identify one or more enterprises using the second identification system.

[0075] Referring to the relevant description of step 221, the service platform can determine the second identification system to which the ID of the target product belongs by identifying specific fields of the target product's ID (e.g., IAC).

[0076] In some embodiments, the service platform may pre-store multiple enterprise groups corresponding to multiple identification systems, wherein each enterprise group corresponding to any identification system includes the IDs of multiple enterprises using that identification system. In some embodiments, the service platform may query one or more enterprises using a second identification system through an external system.

[0077] Step 330: Send a second downstream query request to the management systems of the one or more enterprises respectively.

[0078] The second downstream query request indicates the downstream products of the target product, and the second downstream query request carries the ID of the target product.

[0079] Step 340: Receive the ID of the downstream product returned by the management system of the downstream enterprise to which the downstream product belongs, and return the ID of the downstream product to the user terminal.

[0080] Referring to the foregoing embodiments, for an internal product that includes upstream products, the management system is used to manage the composition information of the internal product, which includes the ID of the internal product and the IDs of each upstream product of the internal product.

[0081] The downstream enterprise to which the downstream product belongs is one of the aforementioned enterprises. Since the downstream product is an internal product of the downstream enterprise, the downstream enterprise's management system can determine the downstream product's ID based on the target product's ID and a combination of information containing the target product's ID.

[0082] In some embodiments, the original downstream query request, the first downstream query request, and the second downstream query request also indicate the query for the association information of downstream products. The management system is also used to manage the association information of internal products. Accordingly, process 300 also includes step 350.

[0083] Step 350: Receive the downstream product association information returned by the downstream enterprise's management system, and return the downstream product association information to the user terminal.

[0084] As an example, assume that product b and product c are internal products of companies B and C respectively (denoted as IDb and IDc), and product b contains product c, for example, a circuit board contains a chip. A user can scan the QR code of product c to view the ID (i.e., IDb) of its downstream product b. Specifically, the user terminal generates an original downstream query request carrying product c based on the QR code parsing result and sends the original downstream query request to company C's management system. Since product b, the downstream product of product c, is not an internal product of company C, company C cannot obtain the composition information of product b. Therefore, company C sends a first downstream query request carrying IDc to the service platform. The service platform determines the second identification system to which IDc belongs and identifies one or more companies (including company B) using the second identification system. The service platform sends a second downstream query request carrying IDc to the management systems of the one or more companies respectively. Since product b, the downstream product of product c, is an internal product of company B, company B's management system can find the composition information of product c as an upstream product (denoted as IDb-IDc), and therefore returns the association information of IDb and product b to the service platform. Finally, the service platform returns the association information between IDb and product b to the user's terminal.

[0085] To enable multi-level downstream product queries, the service platform can repeatedly execute process 300. For example, assume: products a, b, and c are internal products of companies A, B, and C respectively (denoted as IDa, IDb, and IDc). Product a contains product b (e.g., a refrigerator contains a circuit board), and product b contains product c (e.g., a circuit board contains a chip). After receiving a second downstream query request carrying IDb, company B's management system searches for composition information (e.g., IDa-IDb) with product b as an upstream product to determine if product b's downstream product is an internal product. If it determines that product b's downstream product is not an internal product, company B's management system sends a first downstream query request carrying IDb to the service platform. The service platform determines the second identification system to which IDb belongs and identifies one or more companies (including company A) using the second identification system. The service platform sends second downstream query requests carrying IDb to the management systems of these companies respectively. Since product b's downstream product a is company A's internal product, company A's management system can find the composition information (denoted as IDa-IDb) with product b as an upstream product, and therefore returns the association information between IDa and product a to the service platform. Finally, the service platform returns the association information between IDa and product a to the user's terminal. It is worth noting that in the above multi-level downstream product query process, the target product changes from product c to product b; correspondingly, the target company changes from company C to company B, and the downstream company changes from company B to company A.

[0086] It is understandable that the service platform can continue to query until the target product has no downstream products, and then package and send the flow of the target product (such as IDC→IDb→IDa) and a series of downstream product (such as product b and product a) related information to the user terminal.

[0087] Figure 5 is an exemplary flowchart of the identifier chain tracing method provided in this application embodiment. Process 400 is executed by the service platform 130. As shown in Figure 5, process 400 includes the following steps.

[0088] Step 410: Receive a third-party downstream query request from the target company's management system.

[0089] The third downstream query request is generated by the target company's management system in response to the original downstream query request from the user terminal. The original downstream query request instructs the query for the ID of the target product's downstream product (hereinafter referred to as the downstream product), and carries the ID of the target product. The third downstream query request instructs the query for the ID of the downstream product from the downstream company's management system, and carries the ID of the target product.

[0090] Upon receiving the original downstream query request, the target company's management system first checks the composition information of its internal products to determine whether the target product's downstream products are internal products. If the downstream products are determined to be internal products, the target company's management system returns the downstream product's association information to the user terminal. If the downstream products are determined not to be internal products, the target company's management system sends a third-party downstream query request to the service platform.

[0091] It should be noted that Process 400 applies to situations where the downstream product is not an internal product of the target company, but the downstream company to which the downstream product belongs can be identified.

[0092] Step 420: Send the fourth downstream query request to the management system of the downstream enterprise.

[0093] The fourth downstream query request indicates that the ID of the downstream product is being queried, and the fourth downstream query request carries the ID of the target product.

[0094] Step 430: Receive the downstream product ID returned by the downstream enterprise's management system and return the downstream product ID to the user terminal.

[0095] Referring to the foregoing embodiments, for an internal product that includes upstream products, the management system is used to manage the composition information of the internal product, which includes the ID of the internal product and the IDs of each upstream product of the internal product.

[0096] In some embodiments, the original downstream query request, the third downstream query request, and the fourth downstream query request also indicate the query for the association information of downstream products. The management system is also used to manage the association information of internal products. Accordingly, process 400 also includes step 440.

[0097] Step 440: Receive the downstream product association information returned by the downstream enterprise's management system, and return the downstream product association information to the user terminal.

[0098] Since the downstream products are internal products of the downstream enterprises, the downstream enterprises' management systems can provide the IDs and associated information of the downstream products.

[0099] As an example, assume that product b and product c are internal products of companies B and C respectively (denoted as IDb and IDc), and product b contains product c, for example, a circuit board contains chips. A user can scan the QR code of product c to view the ID (IDb) of its downstream product b. Specifically, the user terminal generates an original downstream query request carrying product c based on the QR code parsing result and sends it to company C's management system. Since product b is not an internal product of company C, company C cannot obtain the composition information of product b, but it can know that product c flows to company B. Therefore, company B sends a third downstream query request to the service platform. The service platform sends a fourth downstream query request to company B. Since product b is an internal product of company B, company B's management system can find the composition information with product c as the upstream product (denoted as IDb-IDc), and therefore returns the association information of IDb and product b to the service platform. Finally, the service platform returns the association information of IDb and product b to the user terminal.

[0100] To enable multi-level downstream product queries, the service platform can repeatedly execute process 400. For example, assume: products a, b, and c are internal products of companies A, B, and C respectively (denoted as IDa, IDb, and IDc). Product a contains product b (e.g., a refrigerator contains a circuit board), and product b contains product c (e.g., a circuit board contains a chip). After receiving a second downstream query request carrying IDb, company B's management system searches for composition information with product b as an upstream product (e.g., IDa-IDb) to determine if product b's downstream product is an internal product. If it determines that product b's downstream product is not an internal product, and if company B can determine that product b flows to company A, then company B's management system sends a third downstream query request carrying IDb to the service platform. The service platform then sends a fourth downstream query request carrying IDb to company A's management system. Since product b's downstream product a is company A's internal product, company A's management system can find composition information with product b as an upstream product (denoted as IDa-IDb), and therefore returns the association information between IDa and product a to the service platform. Finally, the service platform returns the association information between IDa and product a to the user's terminal. It is worth noting that in the above multi-level downstream product query process, the target product changes from product c to product b; correspondingly, the target company changes from company C to company B, and the downstream company changes from company B to company A.

[0101] It is understandable that the service platform can continue to query until the target product has no downstream products, and then package and send the flow of the target product (such as IDC→IDb→IDa) and the association information of these downstream products (such as product b and product a) to the user terminal.

[0102] By leveraging query processes 300 or 400, and supporting progressive queries between multiple IDs through chained queries, product flow can be tracked, thereby analyzing and locating the impact of upstream issues on downstream processes.

[0103] It is worth noting that query processes 200 and 300 (or 400) can be used to obtain upstream and downstream information throughout the entire lifecycle of the target product. Therefore, this technology can be applied to Digital Product Passport (DPP). In some embodiments, the service platform can write historical query results into a cache. These historical query results include the flow of the queried target product and the association information between the target product and its upstream and downstream products. The flow of the target product is described by product ID (e.g., IDc→IDb→IDa). Furthermore, upon receiving a new query request involving upstream and downstream product information (e.g., a new first upstream query request / first downstream query request / third downstream query request), the service platform can first query the upstream and downstream information of the currently queried target product in the persistent cache. If the upstream and downstream information of the currently queried target product is found in the persistent cache, it is returned to the user terminal. Otherwise, the enterprise's internal management system is coordinated to provide the upstream and downstream information of the currently queried target product according to the aforementioned processes 200 / 300 / 400. In this way, the query efficiency of upstream and downstream product information can be effectively improved.

[0104] As an example, let's assume the service platform first receives an upstream query request for product A and a downstream query request for product C. After querying, it obtains the association information for product A, product B, and product C, as well as the flow of product C: IDc→IDb→IDa. Subsequently, if the service platform receives an upstream or downstream query request for product B, it can directly retrieve the upstream and downstream information of product B from the cache, such as the association information for upstream product C and the ID and association information for downstream product A. Compared to directly querying upstream and downstream information according to the 200 / 300 / 400 process, the introduction of cached information significantly improves query efficiency.

[0105] Figure 6 is an exemplary block diagram of the identification chain traceability system provided in an embodiment of this application. The system 500 is implemented in the service platform 130. As shown in Figure 6, the system 500 includes a first receiving module 510, a first determining module 520, and a first sending module 530.

[0106] The first receiving module 510 is configured to receive a first upstream query request from the target enterprise's management system. The first upstream query request is generated by the target enterprise's management system in response to an original upstream query request from a user terminal. The original upstream query request indicates a query for the association information of upstream products of the target product, and the original upstream query request carries the ID of the target product. The first upstream query request indicates a query for the association information of the upstream product, and the first upstream query request carries the ID of the upstream product.

[0107] The first determining module 520 is used to: determine the upstream enterprise to which the upstream product belongs based on the ID of the upstream product.

[0108] The first sending module 530 is further configured to: send a second upstream query request to the management system of the upstream enterprise, the second upstream query request indicating a query for the association information of the upstream product. The second upstream query request indicates a query for the association information of the upstream product, and the second upstream query request carries the ID of the upstream product.

[0109] The first receiving module 510 is also used to receive the association information of the upstream product returned by the management system of the upstream enterprise.

[0110] The first sending module 530 is also used to return the association information of the upstream product to the user terminal.

[0111] The management system is used to manage the association information of internal products. For internal products that include upstream products, the management system is also used to manage the composition information of the internal product, which includes the ID of the internal product and the IDs of each upstream product of the internal product.

[0112] For more details about System 500 and its modules, please refer to Figure 2 and its related descriptions.

[0113] Figure 7 is a first exemplary block diagram of the identification chain traceability system provided in an embodiment of this application. The system 600 is implemented in the service platform 130. As shown in Figure 7, the system 600 includes a second receiving module 610, a second determining module 620, and a second sending module 630.

[0114] The second receiving module 610 is configured to receive a first downstream query request from the target enterprise's management system. The first downstream query request is generated by the target enterprise's management system in response to an original downstream query request from a user terminal. The original downstream query request indicates a query for the ID of a downstream product of the target product, and the original downstream query request carries the ID of the target product. The first downstream query request indicates a query for the ID of the downstream product, and the first downstream query request carries the ID of the target product.

[0115] The second determining module 620 is used to determine the second identification system to which the ID of the target product belongs, and to determine one or more enterprises using the second identification system.

[0116] The second sending module 630 is configured to send a second downstream query request to the management systems of the one or more enterprises respectively. The second downstream query request indicates a query for the ID of the downstream product, and carries the ID of the target product.

[0117] The second receiving module 610 is further configured to receive the ID of the downstream product returned by the management system of the downstream enterprise to which the downstream product belongs, wherein the downstream enterprise is one of the one or more enterprises. The second sending module 630 is further configured to return the ID of the downstream product to the user terminal.

[0118] Specifically, for internal products that include upstream products, the management system is used to manage the composition information of the internal product, which includes the ID of the internal product and the IDs of each upstream product of the internal product.

[0119] In some embodiments, the original downstream query request, the first downstream query request, and the second downstream query request further indicate a query for the association information of the downstream product, and the management system is also used to manage the association information of internal products. The second receiving module 610 is also used to receive the association information of the downstream product returned by the management system of the downstream enterprise. The second sending module 630 is also used to return the association information of the downstream product to the user terminal.

[0120] For more details about System 600 and its modules, please refer to Figure 4 and its related descriptions.

[0121] Figure 8 is a second exemplary block diagram of the identification chain traceability system provided in an embodiment of this application. System 700 is implemented in service platform 130. As shown in Figure 8, system 700 includes a third receiving module 710 and a third sending module 720.

[0122] The third receiving module 710 is used to receive a third downstream query request from the target enterprise's management system. The third downstream query request is generated by the target enterprise's management system in response to an original downstream query request from a user terminal. The original downstream query request indicates a query for the ID of a downstream product of the target product, and carries the ID of the target product. The third downstream query request indicates a query for the ID of the downstream product from the downstream enterprise's management system, and carries the ID of the target product.

[0123] The third sending module 720 is used to send a fourth downstream query request to the management system of the downstream enterprise. The fourth downstream query request indicates that the ID of the downstream product is to be queried, and the fourth downstream query request carries the ID of the target product.

[0124] The third receiving module 710 is also used to receive the ID of the downstream product returned by the management system of the downstream enterprise.

[0125] The third sending module 720 is also used to return the ID of the downstream product to the user terminal.

[0126] Specifically, for internal products that include upstream products, the management system is used to manage the composition information of the internal product, which includes the ID of the internal product and the IDs of each upstream product of the internal product.

[0127] In some embodiments, the original downstream query request, the third downstream query request, and the fourth downstream query request further indicate a query for the association information of the downstream product, and the management system is further configured to manage the association information of internal products. The third receiving module 710 is also configured to receive the association information of the downstream product returned by the management system of the downstream enterprise. The third sending module 720 is also configured to return the association information of the downstream product to the user terminal.

[0128] For more details about System 700 and its modules, please refer to Figure 5 and its related descriptions.

[0129] It should be noted that the above division of functional modules is only an example. For those skilled in the art, after understanding the system principle, they can arbitrarily combine, split, or replace the modules, as well as add or omit one or more modules, without violating the system principle.

[0130] Figure 9 is a schematic diagram of the service platform provided in an embodiment of this application. As shown in Figure 9, the service platform 800 includes a processor 810 and a memory 820. The memory 820 stores a computer program. When the processor 810 executes the computer program, it implements the identification chain tracing method provided in any embodiment of this application (e.g., process 200, process 300, or process 400).

[0131] Further details regarding the identification chain tracing method can be found in Figures 2, 4, and 5 and their related descriptions, and will not be repeated here.

[0132] It should be noted that, in this document, relational terms such as "first" and "second" are used merely to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to the process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes the element.

[0133] The above are merely embodiments of this application, which enable those skilled in the art to understand and implement this application. Various modifications to the embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of this application. Therefore, this application is not to be limited to the embodiments herein, but is to be accorded the widest scope consistent with the principles and features disclosed herein.

Claims

1. A chain-of-identity traceability method, characterized in that, The method is executed by the service platform, and the method includes: The system receives a first upstream query request from the target enterprise's management system; the first upstream query request is generated by the target enterprise's management system in response to an original upstream query request from a user terminal; the original upstream query request indicates a query for the association information of the target product's upstream products, and the original upstream query request carries the ID of the target product; the first upstream query request indicates a query for the association information of the upstream products, and the first upstream query request carries the ID of the upstream products. Based on the ID of the upstream product, determine the upstream enterprise to which the upstream product belongs; Send a second upstream query request to the management system of the upstream enterprise; the second upstream query request indicates that the association information of the upstream product be queried, and the second upstream query request carries the ID of the upstream product; Receive the association information of the upstream products returned by the management system of the upstream enterprise; Return the associated information of the upstream products to the user terminal; The management system is used to manage the association information of internal products; for internal products that include upstream products, the management system is also used to manage the composition information of the internal product, which includes the ID of the internal product and the IDs of each upstream product of the internal product.

2. The method according to claim 1, characterized in that, Based on the ID of the upstream product, determine the upstream enterprise to which the upstream product belongs, including: Determine the first identification system to which the ID of the upstream product belongs, and determine the first identification resolution system corresponding to the first identification system; Send the ID of the upstream product to the first identifier resolution system; The system receives a first resolution result from the first identifier resolution system, and the first resolution result indicates the upstream enterprise to which the upstream product belongs.

3. A chain of identification traceability method, characterized in that, The method is executed by the service platform, and the method includes: The system receives a first downstream query request from the target enterprise's management system; the first downstream query request is generated by the target enterprise's management system in response to an original downstream query request from a user terminal; the original downstream query request indicates that the ID of a downstream product of the target product is being queried, and the original downstream query request carries the ID of the target product; the first downstream query request indicates that the ID of the downstream product is being queried, and the first downstream query request carries the ID of the target product. Determine the second identification system to which the ID of the target product belongs, and identify one or more enterprises using the second identification system; Send a second downstream query request to the management systems of the one or more enterprises respectively; the second downstream query request indicates that the ID of the downstream product is queried, and the second downstream query request carries the ID of the target product; Receive the ID of the downstream product returned by the management system of the downstream enterprise to which the downstream product belongs, wherein the downstream enterprise is one of the one or more enterprises; Return the ID of the downstream product to the user terminal; Specifically, for internal products that include upstream products, the management system is used to manage the composition information of the internal product, which includes the ID of the internal product and the IDs of each upstream product of the internal product.

4. The method according to claim 3, characterized in that, The original downstream query request, the first downstream query request, and the second downstream query request also indicate querying the association information of the downstream products, and the management system is also used to manage the association information of internal products; The method further includes: Receive the association information of the downstream products returned by the management system of the downstream enterprise; The association information of the downstream products is returned to the user terminal.

5. A chain of identification traceability method, characterized in that, The method is executed by the service platform, and the method includes: The system receives a third downstream query request from the target enterprise's management system; the third downstream query request is generated by the target enterprise's management system in response to an original downstream query request from a user terminal; the original downstream query request indicates querying the ID of a downstream product of the target product, and the original downstream query request carries the ID of the target product; the third downstream query request indicates querying the ID of the downstream product from the downstream enterprise's management system, and the third downstream query request carries the ID of the target product. A fourth downstream query request is sent to the management system of the downstream enterprise. The fourth downstream query request indicates that the ID of the downstream product is to be queried. The fourth downstream query request carries the ID of the target product. Receive the ID of the downstream product returned by the management system of the downstream enterprise; Return the ID of the downstream product to the user terminal; Specifically, for internal products that include upstream products, the management system is used to manage the composition information of the internal product, which includes the ID of the internal product and the IDs of each upstream product of the internal product.

6. The method according to claim 5, characterized in that, The original downstream query request, the third downstream query request, and the fourth downstream query request also indicate querying the association information of the downstream products, and the management system is also used to manage the association information of internal products; The method further includes: Receive the association information of the downstream products returned by the management system of the downstream enterprise; The association information of the downstream products is returned to the user terminal.

7. A chain-of-identification traceability system, characterized in that, The system is implemented in a service platform and includes a first receiving module, a first determining module, and a first sending module. The first receiving module is configured to receive a first upstream query request from the target enterprise's management system; the first upstream query request is generated by the target enterprise's management system in response to an original upstream query request from a user terminal; the original upstream query request indicates querying the association information of the target product's upstream products, and the original upstream query request carries the ID of the target product; the first upstream query request indicates querying the association information of the upstream products, and the first upstream query request carries the ID of the upstream products; The first determining module is used to: determine the upstream enterprise to which the upstream product belongs based on the ID of the upstream product; The first sending module is further configured to: send a second upstream query request to the management system of the upstream enterprise, the second upstream query request indicating a query for the association information of the upstream product; the second upstream query request indicating a query for the association information of the upstream product, the second upstream query request carrying the ID of the upstream product; The first receiving module is also used to receive the association information of the upstream product returned by the management system of the upstream enterprise; The first sending module is also used to return the association information of the upstream product to the user terminal; The management system is used to manage the association information of internal products; for internal products that include upstream products, the management system is also used to manage the composition information of the internal product, which includes the ID of the internal product and the IDs of each upstream product of the internal product.

8. A chain-of-identification traceability system, characterized in that, The system is implemented in a service platform, and the system includes a second receiving module, a second determining module, and a second sending module. The second receiving module is used to receive a first downstream query request from the target enterprise's management system; The first downstream query request is generated by the target enterprise's management system in response to an original downstream query request from a user terminal; the original downstream query request indicates a query for the ID of a downstream product of the target product, and the original downstream query request carries the ID of the target product; the first downstream query request indicates a query for the ID of the downstream product, and the first downstream query request carries the ID of the target product; The second determining module is used to determine the second identification system to which the ID of the target product belongs, and to determine one or more enterprises using the second identification system; The second sending module is used to send a second downstream query request to the management systems of the one or more enterprises respectively; The second downstream query request indicates a query for the ID of the downstream product, and the second downstream query request carries the ID of the target product; The second receiving module is further configured to receive the ID of the downstream product returned by the management system of the downstream enterprise to which the downstream product belongs, wherein the downstream enterprise is one of the one or more enterprises; The second sending module is also used to return the ID of the downstream product to the user terminal; Specifically, for internal products that include upstream products, the management system is used to manage the composition information of the internal product, which includes the ID of the internal product and the IDs of each upstream product of the internal product.

9. A chain-of-identification traceability system, characterized in that, The system is implemented in a service platform, and the system includes a third receiving module and a third sending module. The third receiving module is used to receive a third downstream query request from the target enterprise's management system; The third downstream query request is generated by the target enterprise's management system in response to the original downstream query request from the user terminal; the original downstream query request indicates querying the ID of the downstream product of the target product, and the original downstream query request carries the ID of the target product; the third downstream query request indicates querying the ID of the downstream product from the downstream enterprise's management system, and the third downstream query request carries the ID of the target product. The third sending module is used to send a fourth downstream query request to the management system of the downstream enterprise. The fourth downstream query request indicates that the ID of the downstream product is to be queried. The fourth downstream query request carries the ID of the target product. The third receiving module is also used to receive the ID of the downstream product returned by the management system of the downstream enterprise; The third sending module is also used to return the ID of the downstream product to the user terminal; Specifically, for internal products that include upstream products, the management system is used to manage the composition information of the internal product, which includes the ID of the internal product and the IDs of each upstream product of the internal product.

10. A service platform, characterized in that, It includes a processor and a memory, wherein the memory stores a computer program, and when the processor executes the computer program, it implements the identification chain tracing method as described in any one of claims 1 to 6.

Images