Product anti-counterfeiting repeated query system and anti-counterfeiting method

Abstract

The application discloses a kind of commodity anti-fake repeated query method, and stores relevant information by generating unique anti-fake code for commodity through anti-fake platform.The platform receives anti-fake code and user unique identity when user queries, judges whether it is first query.If it is first query, then bind user identity;If it is not first query, then verify whether user identity is consistent with binding, and terminate query if it is not consistent.In the query step, the platform calls commodity information and query record and returns to user.In the return step, the platform receives return request and verifies user identity, clears binding relationship and query record if it is consistent, resets anti-fake code state;If it is not consistent, the request is refused.The application improves the accuracy of anti-fake query, prevents anti-fake code from being reused, enhances user experience, improves system security, realizes query record tracking, effectively protects commodity information privacy and security, provides data support for cracking down on fake and inferior commodities.

Description

Technical Field

[0001] This invention relates to the fields of data processing and object identification coding, specifically to a product anti-counterfeiting duplicate query system and anti-counterfeiting method. Background Technology

[0002] Currently, most goods, especially mid-to-high-end items such as luxury goods and gifts, typically have unique anti-counterfeiting codes to prevent counterfeiting. Consumers scan these codes to verify authenticity when purchasing. Often, consumers only scan the codes to check product information without actually buying. Furthermore, luxury goods are frequently resold in the secondary market after initial purchase, while gifts are often given away by the buyer. (See the process for details.) Figure 1 .

[0003] Technical shortcomings of existing anti-counterfeiting codes:

[0004] a) Once the anti-counterfeiting code has been used for querying, when it is scanned and queried a second or subsequent time, the anti-counterfeiting page can only display the initial query time and the current number of queries. Figure 2 As shown.

[0005] b) Often, consumers will only scan the anti-counterfeiting code to check product information without making a purchase. Once the anti-counterfeiting code is checked by a consumer for the first time, subsequent consumers will find that the anti-counterfeiting code has already been checked when they scan the code to purchase the product, making it impossible for them to determine the authenticity of the product.

[0006] c) Anyone else can scan the same code multiple times, which gives counterfeiters the opportunity to produce counterfeits. Counterfeiters can copy the same anti-counterfeiting code and use it on counterfeit products. The copied anti-counterfeiting code can also be queried and used.

[0007] d) At the same time, when the recipient of the gift or the buyer of second-hand luxury goods scans the code to verify the product, what they see when scanning the anti-counterfeiting code is the first time the anti-counterfeiting code was scanned and the current number of scans. This does not determine whether the product is genuine.

[0008] If a gift recipient or a buyer of secondhand luxury goods receives a counterfeit product, the verification process will return the same information as the genuine product.

[0009] Currently, a technology has emerged that allows anti-counterfeiting codes to be transferred but not returned to their initial state. The transfer process is as follows:

[0010] (a) The transferee must first register their mobile phone number on the platform. After the transfer, the transferee uses their consumer scanning terminal to scan the product's QR code. The consumer anti-counterfeiting query module on the terminal sends the transferee's mobile phone number and the scanned product's unique identification code to the anti-counterfeiting platform's anti-counterfeiting query module; (b) The anti-counterfeiting platform's anti-counterfeiting query module receives the mobile phone number and the product's unique identification code and confirms whether it is a registered consumer scanning terminal. If yes, proceed to step (c); otherwise, prompt "Unauthorized User"; (c) The anti-counterfeiting platform's anti-counterfeiting query module queries the QR code record containing product information and the product's unique identification code, confirms whether the product's QR code exists, and finds that the product is not being scanned for the first time, and the uploaded mobile phone number is inconsistent with the mobile phone number currently bound to the product's unique identification code, then... (d) The transferee receives the transfer verification code from the original consumer and enters it into their consumer scanning terminal. The consumer transfer verification module then sends the information to the anti-counterfeiting platform's anti-counterfeiting query module for processing. (e) The anti-counterfeiting platform's anti-counterfeiting query module verifies whether the entered transfer verification code is correct. If yes, it proceeds to step (f); otherwise, it prompts "Verification code input is incorrect. Please carefully verify the source of the verification code." (f) The anti-counterfeiting platform's anti-counterfeiting query module sends product information to the transferee's consumer scanning terminal and binds the transferee's consumer scanning terminal's mobile phone number to the scanned product unique identification code.

[0011] However, there are several key points to consider when transferring the anti-counterfeiting code using the aforementioned technology: 1) There must be a transferor; without a transferor, the transfer is impossible; 2) The recipient must register their mobile phone number on the platform beforehand; without registration, the recipient cannot receive the code; 3) The recipient must scan the anti-counterfeiting code first; 4) The first person to scan the code must send a verification code to the recipient; without sending it, the transfer is impossible. In practical use, this method has significant problems. If the first consumer scans the code only to inquire about product information and does not purchase the goods, there is no transferor. However, the anti-counterfeiting code has already been bound, and subsequent consumers cannot scan it for inquiries. Even if the consumer who scanned the code wants to return it to the platform, it is not allowed. Summary of the Invention

[0012] The purpose of this invention is to overcome the shortcomings of the prior art and provide a product anti-counterfeiting repeated query system and anti-counterfeiting method to solve the anti-counterfeiting problems of multiple anti-counterfeiting queries and product transfer.

[0013] The objective of this invention is achieved through the following technical solution:

[0014] A method for repeated verification of product anti-counterfeiting features, including:

[0015] The anti-counterfeiting platform generates a unique anti-counterfeiting code for each product and stores the anti-counterfeiting code and its associated product information in a database.

[0016] Receive anti-counterfeiting code information and the user's unique identification code sent by the user terminal;

[0017] Determine if this is the first time the anti-counterfeiting code has been queried:

[0018] If it is the first query, the anti-counterfeiting code will be automatically bound to the user's unique identifier, and the query process will begin.

[0019] If this is not the first query, determine whether the unique identifier of the user who initiated the query request is consistent with the currently bound user's identifier. If they are consistent, proceed with the query step; otherwise, terminate the query.

[0020] Query steps: Retrieve the product information and query records from the database and return them to the user terminal for display;

[0021] Return steps: Receive a return request from the user terminal containing the anti-counterfeiting code and the unique identifier of the bound user;

[0022] Verify whether the user identifier in the verification request matches the currently bound user identifier:

[0023] If they match, clear the binding relationship and historical query records of the anti-counterfeiting code, and reset the status of the anti-counterfeiting code to unbound;

[0024] If there is no discrepancy, the request for return will be rejected.

[0025] The anti-counterfeiting platform first generates a unique anti-counterfeiting code for each product and stores this code and its associated product information in a database. When a user wants to verify the authenticity of a product, they send the anti-counterfeiting code and their unique identifier to the anti-counterfeiting platform through their device.

[0026] After receiving this information, the anti-counterfeiting platform will first determine whether the anti-counterfeiting code has been queried for the first time. If it is the first time, the platform will automatically bind the anti-counterfeiting code to the user's unique identifier and then proceed with the query process. During the query, the platform will retrieve the product information associated with the anti-counterfeiting code and the query records from its database and return this information to the user's terminal for display.

[0027] If this anti-counterfeiting code is not being queried for the first time, the anti-counterfeiting platform will further check whether the unique identifier of the user who initiated the query matches the currently bound user identifier. If they match, the anti-counterfeiting platform will also proceed with the query process and return product information and the query record to the user. If they do not match, the anti-counterfeiting platform will terminate the query to prevent the anti-counterfeiting code from being misused by unauthorized users.

[0028] In addition, the anti-counterfeiting method includes an anti-counterfeiting code return step. When a consumer queries the product but no longer needs the anti-counterfeiting code, they can independently send a return request containing the anti-counterfeiting code and the unique identifier of the bound user to the anti-counterfeiting platform via their own terminal. The anti-counterfeiting platform will verify whether the user identifier in the request matches the currently bound user identifier. If they match, the anti-counterfeiting platform will clear the binding relationship and historical query records of the anti-counterfeiting code, reset the anti-counterfeiting code status to unbound and reset it to its initial state, so that other consumers can verify the authenticity of the product. If they do not match, the anti-counterfeiting platform will reject the return request to prevent the anti-counterfeiting code from being copied and counterfeited.

[0029] As a preferred method, the binding relationship is established as follows:

[0030] When a user scans the anti-counterfeiting code to access the anti-counterfeiting query page for the first time, the system automatically obtains the user's unique identifier and automatically binds it; or,

[0031] After the user scans the code for the first time and clicks the authorization button on the anti-counterfeiting query page, the user's unique identifier is automatically obtained and bound.

[0032] As a preferred method, the anti-counterfeiting code return request is triggered by the bound user independently clicking the return button or the gift button on the product anti-counterfeiting query interface on the user terminal.

[0033] As a preferred method, the query records include the historical query count and the first query time of the anti-counterfeiting code. Alternatively, after clearing the binding relationship and historical query records, the status of the anti-counterfeiting code in the database is updated to unbound; after the anti-counterfeiting code status is reset to unbound, the anti-counterfeiting code can be queried and bound again by other users.

[0034] As a preferred method, the anti-counterfeiting code may take the form of a QR code, barcode, or RFID chip.

[0035] As a preferred method, an administrator monitors the status reset operation and results of the anti-counterfeiting code via a management terminal. A product anti-counterfeiting duplicate query system includes an anti-counterfeiting platform, which comprises:

[0036] The anti-counterfeiting code generation module is used to generate an anti-counterfeiting code that uniquely corresponds to the product and store the anti-counterfeiting code and its associated product information in the database;

[0037] The binding management module is used to determine whether the anti-counterfeiting code is being queried for the first time when it receives the anti-counterfeiting code information and the user's unique identity identifier sent by the user terminal. If it is the first time, the module will automatically bind the user's unique identity identifier (including the user's mobile phone number and / or OpenID) to the anti-counterfeiting code.

[0038] The anti-counterfeiting query module is used to receive anti-counterfeiting query requests sent by user terminals, determine whether the anti-counterfeiting code is being queried for the first time, and if it is the first time, trigger the binding management module to bind it. If it is not the first time, verify whether the user identity identifier is consistent with the currently bound user identity identifier. If they are consistent, return the product information and query record. If they are inconsistent, return an error message and terminate the query.

[0039] The anti-counterfeiting code recycling module is used to receive anti-counterfeiting code return requests sent by user terminals, which contain anti-counterfeiting codes and user identification identifiers.

[0040] The anti-counterfeiting code initialization module is used to respond to the triggering of the anti-counterfeiting code recycling module, verify whether the user identity identifier in the return request is consistent with the currently bound user identity identifier. If they are consistent, the binding relationship and historical query records are cleared, the anti-counterfeiting code status is reset to unbound, and an initialization success confirmation is sent. If they are inconsistent, the request is rejected and an error message is returned.

[0041] As a preferred method, the binding management module automatically obtains the user's identity identifier and establishes a binding relationship with the anti-counterfeiting code when the user scans the anti-counterfeiting code for the first time; or obtains the user's identity identifier and establishes a binding relationship with the anti-counterfeiting code when the user clicks the authorization button after scanning the anti-counterfeiting code.

[0042] As a preferred method, the anti-counterfeiting code recycling module only receives the corresponding anti-counterfeiting code return request when the bound user scans the anti-counterfeiting code through the user terminal and clicks the return button or gift button on the user terminal interface.

[0043] This invention offers at least the following advantages: First, it improves the accuracy of anti-counterfeiting verification by binding the unique identifier of the first user to the verification, ensuring the uniqueness of the anti-counterfeiting code and the legitimacy of the query. Second, it prevents the anti-counterfeiting code from being copied by checking the unique identifier of the querying user, effectively avoiding repeated verification after the anti-counterfeiting code has been copied. Finally, through anti-counterfeiting code initialization, even if a consumer only queries product information without purchasing, subsequent consumers can still verify the authenticity of the product. This invention enhances system security by effectively preventing unauthorized users from querying and returning the anti-counterfeiting code through identity verification, protecting the privacy and security of product information. Attached Figure Description

[0044] To reveal the technical details of the embodiments of the present invention, the accompanying drawings involved in the embodiments will be briefly described below. It should be emphasized that these drawings only present several embodiments of the present invention and should not be considered as defining the scope of the invention. For those skilled in the art, other related drawings can still be derived based on these drawings without inventive effort.

[0045] Figure 1This is a flowchart illustrating the existing technology.

[0046] Figure 2 To prevent counterfeiting, the page can only display the first query time and the current number of queries as an illustration;

[0047] Figure 3 This is a flowchart illustrating an example. Detailed Implementation

[0048] The technical solution of the present invention will be further described in detail below with reference to the accompanying drawings, but the scope of protection of the present invention is not limited to the following description.

[0049] In the following description, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. However, it should be understood that the present disclosure is not limited to the specific forms shown herein. Rather, it should be understood to encompass various variations, equivalents, and / or alternatives to the embodiments of the present disclosure. In illustrating the drawings, the same reference numerals will be used to denote similar components.

[0050] In this disclosure, terminology is used to describe specific embodiments and does not constitute a limitation thereof. In this context, the use of the singular form also encompasses the plural form, unless otherwise expressly stated herein. In the course of description, terms such as “comprising” or “having” are intended to indicate the presence of features, quantities, steps, operations, structural components, parts, or combinations thereof, and do not preclude the possibility or addition of one or more other features, quantities, steps, operations, structural components, parts, or combinations thereof.

[0051] It should be clarified that while the following description provides detailed specific information to aid in a comprehensive understanding of the exemplary embodiments, those skilled in the art will recognize that the exemplary embodiments can be implemented even without these specific details. For example, the system may be illustrated using block diagrams to avoid excessive detail that could obscure the clarity of the example. In other cases, to maintain the clarity of the example, unnecessary details of well-known processes, structures, and techniques may be omitted.

[0052] A method for verifying the authenticity of goods through repeated verification includes:

[0053] The anti-counterfeiting platform generates a unique anti-counterfeiting code for each product and stores the anti-counterfeiting code and its associated product information in a database.

[0054] Receive anti-counterfeiting code information and the user's unique identification (including the user's mobile phone number and / or OpenID) sent by the user terminal;

[0055] Determine if this is the first time the anti-counterfeiting code has been queried:

[0056] If it is the first query, the anti-counterfeiting code will be automatically bound to the user's unique identifier, and the query process will begin.

[0057] If this is not the first query, determine whether the unique identifier of the user who initiated the query request matches the currently bound user's identifier. If they match, proceed with the query process; otherwise, terminate the query and return an error message to the user's terminal.

[0058] Query steps: Retrieve the product information and query records from the database and return them to the user terminal for display;

[0059] Return steps: Receive a return request from the user terminal containing the anti-counterfeiting code and the unique identifier of the bound user;

[0060] Verify whether the user identifier in the verification request matches the currently bound user identifier:

[0061] If they match, clear the binding relationship and historical query records of the anti-counterfeiting code, reset the status of the anti-counterfeiting code to unbound, and send an initialization success confirmation to the user terminal;

[0062] If there is a discrepancy, the return request will be rejected and an error message will be returned.

[0063] Existing technologies bind anti-counterfeiting codes to scanning terminals, but their methods require the scanning terminal to first submit a registration application to the anti-counterfeiting platform. After registration, the platform stores consumer information for identity verification during consumer inquiries. Consumers must be registered beforehand to inquire; if they don't know how to register, they cannot perform anti-counterfeiting inquiries. Upon first scan, the platform verifies if it's a registered mobile number; if so, it binds the mobile number and anti-counterfeiting code and provides inquiry information. This embodiment's method automatically binds the anti-counterfeiting code and mobile number the first time a consumer scans it, without requiring registration. Even if a consumer doesn't want to purchase the product after scanning, they can click the "return" or "exit inquiry" button, and the platform automatically initializes the anti-counterfeiting code, allowing subsequent consumers to continue using the inquiry service. In this embodiment, the system automatically binds the mobile number and Open ID (such as WeChat ID) of the person who scanned the anti-counterfeiting code the first time it is scanned.

[0064] The anti-counterfeiting duplicate query method is implemented through a centralized anti-counterfeiting platform, which is responsible for generating and managing the unique anti-counterfeiting codes of products. When a user queries an anti-counterfeiting code for the first time, the system binds the user's unique identifier to the anti-counterfeiting code, ensuring that each anti-counterfeiting code can only be queried once by the first user. If the user queries again, the system checks whether the queryer's identifier matches the identifier bound initially, thus preventing duplicate queries. Furthermore, users can request the restoration of the anti-counterfeiting code's binding relationship so that the anti-counterfeiting code can be rebound and queried by other users (applicable to scenarios such as product transfer and gifting).

[0065] This embodiment improves the accuracy of anti-counterfeiting verification, ensuring that each anti-counterfeiting code can only be queried once, effectively curbing the possibility of repeated use and counterfeiting. While preventing the reuse of anti-counterfeiting codes, it also allows consumers to independently release the code themselves after the initial query if they do not purchase the product or wish to give it away, making it available for querying by a new owner. Finally, this solution enhances system security by binding user identity identifiers to track query history, reducing the circulation of counterfeit and substandard goods, and providing strong data support for combating such products.

[0066] In one embodiment, such as Figure 3 As shown. In modern e-commerce and social media platforms, consumer identity verification and data binding are crucial steps, ensuring transaction security and enhancing user experience. The following is a detailed description of the process in this embodiment: Consumer A scans the anti-counterfeiting code to enter the anti-counterfeiting page. There are two binding methods: First, Consumer A clicks to authorize automatic binding of the anti-counterfeiting code and mobile phone number + OpenID; second, no authorization is required for automatic binding of OpenID (WeChat ID). Consumer A clicks the anti-counterfeiting query button to open the system's scanning function, scans the anti-counterfeiting code to enter the anti-counterfeiting page, and completes product verification.

[0067] When Consumer A simply inquires about a product, or needs to transfer or gift the product (Consumer A gifts the product to Consumer B), Consumer A scans the anti-counterfeiting code to access the anti-counterfeiting page, clicks the return button, and the backend automatically verifies the ownership of the anti-counterfeiting code based on the linked relationship. If it is confirmed to belong to Consumer A (or the user terminal held by Consumer A), the return process begins, and the system automatically resets the anti-counterfeiting code to its initial state. It's important to note that Consumer A's possession and inquiry records are still stored on the anti-counterfeiting platform and will not be deleted. After Consumer B receives the product, they can then access the anti-counterfeiting platform again, just like Consumer A, forming a closed loop. Throughout this closed loop, all possession and inquiry records are stored on the anti-counterfeiting platform.

[0068] In a preferred embodiment, the binding relationship is established as follows:

[0069] When a user scans the anti-counterfeiting code to access the anti-counterfeiting query page for the first time, the system automatically obtains and binds the user's unique identifier; or,

[0070] After the user scans the code for the first time, they can click the authorization button on the anti-counterfeiting query page to obtain and bind the user's unique identity.

[0071] When a user scans the anti-counterfeiting code and accesses the anti-counterfeiting query page for the first time, the system automatically captures and obtains the user's unique identifier, establishing a binding relationship based on this. Alternatively, after scanning the anti-counterfeiting code for the first time, the user needs to click the authorization button on the anti-counterfeiting query page. The system then obtains the user's unique identifier to complete the binding relationship. This embodiment improves the convenience of users accessing the anti-counterfeiting query page, automatically establishing a binding relationship without requiring users to register on the platform in advance or perform any additional operations. This optimizes the user experience, allowing users to enjoy the anti-counterfeiting query service more quickly and conveniently. This method is suitable for users who have signed information authorization agreements with platforms such as WeChat. On the other hand, by having the user actively click the authorization button to establish a binding relationship, the system can ensure that it has obtained the user's explicit authorization when obtaining the user's unique identifier. This not only respects the user's right to know and right to choose but also enhances the user's trust and satisfaction with the anti-counterfeiting query service. At the same time, this authorization method also helps to improve the security and reliability of the anti-counterfeiting query service, preventing unauthorized access and data leakage.

[0072] In a preferred embodiment, the anti-counterfeiting code return request is triggered by the bound user clicking the return button or the gift button on the user terminal interface. When the bound user performs an operation on the user terminal interface, clicking the return button indicates that the system recognizes that the user wishes to return the anti-counterfeiting code to its original state or to a specific object; clicking the gift button indicates that the system recognizes that the user wishes to gift the right to use the anti-counterfeiting code to another user. This embodiment not only provides a flexible anti-counterfeiting code management method, but also enhances the interactivity between users and the circulation of anti-counterfeiting codes, making the use of anti-counterfeiting codes more convenient and efficient, while also improving user satisfaction and participation.

[0073] In a preferred embodiment, the query record includes the historical number of queries for the anti-counterfeiting code and the time of the first query.

[0074] In a preferred embodiment, after clearing the binding relationship and historical query records, the status of the anti-counterfeiting code in the database is updated to unbound. After the anti-counterfeiting code status is reset to unbound, the anti-counterfeiting code can be queried and bound again by other users. After clearing the binding relationship and historical query records, the system updates the status of the corresponding anti-counterfeiting code in the database to unbound. Once the status of the anti-counterfeiting code is reset to unbound, it becomes available again, allowing other users to perform initial queries and binding operations on it. This mechanism improves the utilization rate of anti-counterfeiting codes. By allowing anti-counterfeiting codes to be reused after unbinding, resource waste is avoided, allowing each anti-counterfeiting code to play its due value. It enhances the flexibility of the system and the user experience. Users do not need to worry about the problem that anti-counterfeiting codes cannot be reused once bound; they can unbind and rebind at any time as needed, improving the flexibility of the system and preventing the anti-counterfeiting codes from being copied and counterfeited. By clearing historical query records and binding relationships in a timely manner, data redundancy and chaos can be avoided, ensuring the accuracy and integrity of the anti-counterfeiting code status in the database.

[0075] In a preferred embodiment, the anti-counterfeiting code may take the form of a QR code, barcode, or RFID chip.

[0076] In a preferred embodiment, an administrator monitors the status reset operation and results of the anti-counterfeiting code via a management terminal. This monitoring improves management efficiency: administrators can view the progress and results of the anti-counterfeiting code status reset in real time, eliminating the need for manual queries or waiting for feedback, thus significantly improving management efficiency. It also enhances data security: the management terminal provides comprehensive monitoring of the anti-counterfeiting code status reset operation, ensuring that every operation is authorized and recorded, effectively preventing unauthorized tampering and data leakage, and enhancing data security. Furthermore, it optimizes user experience: administrators can quickly respond to abnormal anti-counterfeiting code statuses and promptly perform reset operations, ensuring users can use the anti-counterfeiting codes normally, improving user experience. It facilitates troubleshooting: when problems occur with the anti-counterfeiting code status, administrators can quickly locate the problem through the management terminal, conduct targeted troubleshooting and repairs, and shorten troubleshooting time. Finally, it supports data analysis: the management terminal records historical data of the anti-counterfeiting code status reset operation, providing administrators with a basis for data analysis, which helps optimize the anti-counterfeiting code management process and improve overall operational efficiency.

[0077] In a preferred embodiment, the unique identifier is preferably OpenID.

[0078] In a preferred embodiment, the error message includes "No query permission" or "Authentication failed". Furthermore, this embodiment sets up an anti-counterfeiting code generation and verification mode (process).

[0079] The process of generating anti-counterfeiting codes:

[0080] 1. Generate unique product identifier information S:

[0081] The anti-counterfeiting platform generates a unique identifier S for each product, such as the product's serial number or batch number.

[0082] 2. Obtain the user's unique identifier U:

[0083] Users provide their unique identifier U during their first query, such as a mobile phone number or OpenID.

[0084] 3. Generate dynamic factor R:

[0085] The anti-counterfeiting platform generates a dynamic factor R, such as a random number or a timestamp.

[0086] 4. Determine the key K:

[0087] The anti-counterfeiting platform generates a key K based on the product's unique identifier S or other preset rules.

[0088] 5. Generate anti-counterfeiting code C:

[0089] Using the hash function H and the XOR operation ⊕, combined with S, U, K, and R, an anti-counterfeiting code C is generated:

[0090] C=H(S⊕U⊕K⊕R)

[0091] 6. Store relevant information:

[0092] The anti-counterfeiting platform stores the generated anti-counterfeiting code C, dynamic factor R, and user unique identifier U in the database and associates them with the product unique identifier information S.

[0093] The process for verifying the anti-counterfeiting code:

[0094] 1. User scans anti-counterfeiting code C:

[0095] Users send the anti-counterfeiting code C on the product to the anti-counterfeiting platform.

[0096] 2. User inputs unique product identifier information S:

[0097] Users enter the unique identifier S of a product when making a query.

[0098] 3. Retrieve dynamic factor R and user unique identifier U from the database:

[0099] The anti-counterfeiting platform retrieves the dynamic factors R generated at the time of product creation and the user's unique identity identifier U from the database based on the product's unique identifier S.

[0100] 4. Determine the key K:

[0101] The anti-counterfeiting platform extracts the key K based on the product's unique identifier S or other preset rules. The extraction method for key K is the same as that used during its generation.

[0102] 5. Regenerate anti-counterfeiting code C ′ :

[0103] The anti-counterfeiting platform uses the same hash function H, key K, dynamic factor R, and user unique identifier U to regenerate the anti-counterfeiting code C. ′ :

[0104] C′=H(S⊕U⊕K⊕R)

[0105] 6. Compare anti-counterfeiting codes C and C ′ :

[0106] The anti-counterfeiting platform compares the generated anti-counterfeiting code C ′ And the anti-counterfeiting code C provided by the user:

[0107] If C = C ′ If so, the anti-counterfeiting code is valid.

[0108] If C≠C ′ If not, the anti-counterfeiting code will be invalid.

[0109] To outsiders, users may only know the product's unique identifier S, unaware that the generation of the anti-counterfeiting code also involves the user's unique identifier U, dynamic factors R, and a key K. This concealment of information increases the difficulty of counterfeiting, because even if an attacker obtains S, they cannot completely reconstruct all the parameters required to generate the anti-counterfeiting code, and therefore cannot gain access to our anti-counterfeiting platform. The use of the hash algorithm and the specific generation formula are kept secret, further enhancing the system's security. Even if an attacker knows S, they cannot reverse engineer the anti-counterfeiting code generation process.

[0110] By combining the product's unique identifier S, the user's unique identifier U, dynamic factors R, and a key K, and using a hash algorithm to generate an anti-counterfeiting code, this anti-counterfeiting code verification process not only improves system security but also enhances user experience. This embodiment makes the anti-counterfeiting code difficult to forge or tamper with, while ensuring that only specific users can verify the anti-counterfeiting code, thereby effectively protecting the authenticity of the product and the rights of the user.

[0111] A product anti-counterfeiting duplicate query system includes an anti-counterfeiting platform, wherein the anti-counterfeiting platform includes:

[0112] The anti-counterfeiting code generation module is used to generate an anti-counterfeiting code that uniquely corresponds to the product and store the anti-counterfeiting code and its associated product information in the database;

[0113] The binding management module is used to determine whether the anti-counterfeiting code is being queried for the first time when it receives the anti-counterfeiting code information and the user's unique identity identifier sent by the user terminal. If it is the first time, the module will automatically bind the user's unique identity identifier (including the user's mobile phone number and / or OpenID) to the anti-counterfeiting code.

[0114] The anti-counterfeiting query module is used to receive anti-counterfeiting query requests sent by user terminals, determine whether the anti-counterfeiting code is being queried for the first time, and if it is the first time, trigger the binding management module to bind it. If it is not the first time, verify whether the user identity identifier is consistent with the currently bound user identity identifier. If they are consistent, return the product information and query record. If they are inconsistent, return an error message and terminate the query.

[0115] The anti-counterfeiting code recycling module is used to receive anti-counterfeiting code return requests sent by user terminals, which contain anti-counterfeiting codes and user identification identifiers.

[0116] The anti-counterfeiting code initialization module is used to respond to the triggering of the anti-counterfeiting code recycling module, verify whether the user identity identifier in the return request is consistent with the currently bound user identity identifier. If they are consistent, the binding relationship and historical query records are cleared, the anti-counterfeiting code status is reset to unbound, and an initialization success confirmation is sent. If they are inconsistent, the request is rejected and an error message is returned.

[0117] By generating a unique anti-counterfeiting code corresponding to each product and binding it to the user's identity, the system ensures the uniqueness and accuracy of each query, improving the reliability of product anti-counterfeiting. Simultaneously, the system can determine whether the anti-counterfeiting code is being queried for the first time and verifies the user's identity during subsequent queries, effectively avoiding duplicate queries. After the user's first query, the system automatically binds the user's identity, simplifying subsequent query processes and improving user experience. Furthermore, through the anti-counterfeiting code recycling and initialization modules, users can return anti-counterfeiting codes. After confirming the user's identity, the system can reset the anti-counterfeiting code's status, preventing misuse. The system verifies the user's identity, ensuring that only legitimate users can perform query and return operations, enhancing system data security. Finally, the system can record the historical record of each query, helping to track the circulation of goods and providing data support for product authenticity verification and market monitoring.

[0118] In a preferred embodiment, the binding management module automatically obtains the user's identity identifier and establishes a binding relationship with the anti-counterfeiting code when the user scans the anti-counterfeiting code for the first time; or obtains the user's identity identifier and establishes a binding relationship with the anti-counterfeiting code when the user clicks the authorization button after scanning the anti-counterfeiting code.

[0119] The binding management module automatically captures the user's identity information when the user scans the anti-counterfeiting code for the first time and instantly establishes a one-to-one binding relationship with the anti-counterfeiting code. Additionally, the system offers a user-authorized option; after scanning the anti-counterfeiting code, the user can click the authorization button on the interface, and the system will similarly obtain the user's identity information and establish a binding relationship with the anti-counterfeiting code accordingly. Both automatic and user-authorized binding greatly simplify the operation process, allowing users to easily and quickly complete anti-counterfeiting verification and product binding. This enhances the security of anti-counterfeiting code usage; by binding user identity information, it effectively prevents the abuse and forgery of anti-counterfeiting codes, providing strong technical support for product authenticity verification. It also facilitates subsequent tracking and management; if a product problem occurs, the company can quickly trace the product's flow and usage through the bound user information, providing accurate data support for after-sales service and product recalls.

[0120] In a preferred embodiment, the anti-counterfeiting code recycling module only receives the corresponding anti-counterfeiting code return request when the bound user scans the anti-counterfeiting code through the user terminal and clicks the return button or gift button on the user terminal interface.

[0121] The anti-counterfeiting code recycling module is a specific functional module within the product anti-counterfeiting code system. Its main function is to receive and process anti-counterfeiting code return requests under specific conditions. These specific conditions are that the user scans the anti-counterfeiting code on the product using a user terminal (such as a smartphone or tablet) and performs the corresponding operation on the user terminal interface.

[0122] Specifically, after a user scans the anti-counterfeiting code, their terminal will display information related to the code, such as product information and authenticity verification results. If the user wishes to return or give away the anti-counterfeiting code, they can click the "Return" or "Give Away" button on the terminal interface. This action will trigger a signal that is sent to the anti-counterfeiting code system.

[0123] Upon receiving this signal, the anti-counterfeit code recycling module will begin processing the corresponding anti-counterfeit code return request. It will first verify the validity of the request, including confirming whether the request originates from a bound user and whether the anti-counterfeit code is in a returnable state. Once verification is successful, the anti-counterfeit code recycling module will mark the anti-counterfeit code as returned or gifted from the system and update the relevant records. In addition, the anti-counterfeit code recycling module may also have some additional functions, such as recording detailed information about returns or gifts, and counting the number of returns or gifts, for subsequent data analysis and processing.

[0124] In summary, the anti-counterfeiting code recycling module works based on the interaction between the user and the anti-counterfeiting code system. By receiving and processing user return requests, it enables the reuse and management of anti-counterfeiting codes. This helps improve the efficiency and reliability of the product anti-counterfeiting code system, while providing users with a more convenient and flexible user experience. In a preferred embodiment, the query records returned by the anti-counterfeiting query module include the historical query count and the first query time of the anti-counterfeiting code. Through the record of the historical query count, consumers can intuitively understand whether the anti-counterfeiting code has been queried multiple times, thus making a preliminary judgment on the authenticity of the product. If the historical query count is abnormally high, it may mean that the anti-counterfeiting code has been copied or abused by criminals, thus reminding consumers to be cautious when purchasing. Secondly, the record of the first query time provides consumers with an important reference. Consumers can compare the first query time with their purchase time. If there is a significant time difference, it may indicate that the product has been queried or used by others before purchase, further increasing consumers' vigilance regarding the authenticity of the product.

[0125] In summary, the anti-counterfeiting query module effectively enhances consumers' ability to distinguish genuine products from counterfeits by providing query records such as the number of historical queries and the time of the first query, thus providing consumers with a safer and more reliable shopping guarantee.

[0126] In a preferred embodiment, the anti-counterfeiting code is in the form of a QR code, barcode, or RFID chip. The anti-counterfeiting code takes various forms, including but not limited to QR codes, barcodes, and RFID chips. These anti-counterfeiting technologies greatly improve the accuracy and reliability of product anti-counterfeiting. By scanning or reading these anti-counterfeiting codes, consumers and relevant departments can quickly and accurately verify the authenticity of products, effectively combating counterfeit and substandard products and protecting consumer rights. Secondly, the use of anti-counterfeiting codes also facilitates product tracking and management. Enterprises can use the anti-counterfeiting code system to track the flow and sales of products in real time, promptly identify and address potential problems, and improve the efficiency and accuracy of product management. Furthermore, these anti-counterfeiting technologies have advantages such as ease of operation and low cost, making them easy to widely apply to various products and providing strong technical support for combating counterfeit and substandard products and maintaining market order.

[0127] Based on the above description, the technical advantages of this invention are as follows: Compared to existing technologies, this invention offers the following advantages: a) The human-code binding technology ensures that only the bound person can query the anti-counterfeiting code after its initial use. Counterfeiters cannot copy the anti-counterfeiting code to use by others, thus preventing counterfeiters from creating fake codes. b) The human-code binding technology also allows for multiple queries and anti-counterfeiting measures. c) The new technology enables anti-counterfeiting queries after goods are given as gifts or after luxury goods have been resold multiple times.

[0128] This invention includes the following inventive techniques:

[0129] a) Automatic Binding of Code User Without Registration: New technology automatically binds each product's unique code to a specific user during the verification process. Users do not need to register their mobile phone number on the platform beforehand.

[0130] When consumers scan the anti-counterfeiting code on a product to check its authenticity, they only need to click the "Allow" or "Authorize" button on the anti-counterfeiting query page. The anti-counterfeiting system will automatically bind the anti-counterfeiting code on the product to the consumer's mobile phone number and OpenID (WeChat ID).

[0131] Consumers can also bypass the authorization button by having the system automatically bind the anti-counterfeiting code on the product to the consumer's OpenID (WeChat ID) when scanning the code to check the authenticity of the product.

[0132] The bound anti-counterfeiting code can only be queried by the bound mobile phone number and OpenID; other people and mobile phones cannot query it.

[0133] b) The person who binds the account can independently recycle the anti-counterfeiting code:

[0134] The anti-counterfeiting system empowers users to independently query the anti-counterfeiting code and return it to the system.

[0135] Consumers whose anti-counterfeiting codes are linked to their mobile phone numbers by the system can scan the anti-counterfeiting code themselves to enter the anti-counterfeiting page, and click the return or gift button to return the anti-counterfeiting code to the system themselves, without the need for other people to participate.

[0136] Alternatively, if the user clicks the "Exit Query" button, the anti-counterfeiting code will be automatically returned to the system.

[0137] c) Initialization of anti-counterfeiting code without assignee:

[0138] The backend automatically verifies the ownership of the retrieved anti-counterfeiting codes based on the bound relationships.

[0139] The anti-counterfeiting system automatically verifies whether the return meets the return rules: whether it was returned by the person who registered the account.

[0140] If the rules are met, the system will automatically clear the scanning information of this anti-counterfeiting code and reclaim the anti-counterfeiting code to its initial state.

[0141] The same anti-counterfeiting code can be queried and verified by other consumers.

[0142] d) Unbinding the anti-counterfeiting code:

[0143] During the initialization of the anti-counterfeiting code, there is no need for the system to register the transferee; the system automatically removes the previous binding relationship and clears the information of the bound person.

[0144] The person who unbinds the code no longer has the authority to query the unbound anti-counterfeiting code.

[0145]

[0146] Although the preferred embodiments of the present invention have been described in detail, those skilled in the art, upon understanding the basic inventive concept, can make various changes and modifications thereto. Therefore, the appended claims are intended to cover these preferred embodiments as well as all changes and modifications falling within the scope of the present invention. It should be noted that the present invention is not limited to the above-described preferred embodiments; any modifications, equivalent substitutions, and improvements within the spirit and principles of the present invention should be included within the scope of protection of the present invention.

Claims

1. A method for repeated verification of counterfeit goods, characterized in that, include: The anti-counterfeiting platform generates a unique anti-counterfeiting code for each product and stores the anti-counterfeiting code and its associated product information in a database. Receive anti-counterfeiting code information and the user's unique identification code sent by the user terminal; Determine if this is the first time the anti-counterfeiting code has been queried: For first-time queries, no prior registration or additional steps are required from the user. The anti-counterfeiting code is automatically bound to the user's unique identifier, and the query process begins. The user's unique identifier is automatically obtained by the anti-counterfeiting platform when the user first scans the anti-counterfeiting code to access the anti-counterfeiting query page; or, it is obtained by the anti-counterfeiting platform after the user clicks the authorization button on the anti-counterfeiting query page after the first scan. If this is not the first query, determine whether the unique identifier of the user who initiated the query request is consistent with the currently bound user's identifier. If they are consistent, proceed to the query step. If there is no match, the query will be terminated; Query steps: Retrieve the product information and query records from the database and return them to the user terminal for display; Return steps: Receive a return request for the anti-counterfeiting code sent by the user terminal, which includes the anti-counterfeiting code and the unique identifier of the bound user; the anti-counterfeiting code return request is triggered by the bound user independently clicking the return button or the gift button on the anti-counterfeiting query interface of the user terminal. Verify whether the user identity in the verification request matches the currently bound user identity: If they match, clear the binding relationship and historical query records of the anti-counterfeiting code, and reset the anti-counterfeiting code status to unbound; so that the anti-counterfeiting code can be queried and bound by other users again. If there is no discrepancy, the request for return will be rejected; When a user operates on the user terminal interface, clicking the "Return" button indicates that the user wishes to return the anti-counterfeiting code to its original state or to a specific object; clicking the "Gift" button indicates that the user wishes to gift the right to use the anti-counterfeiting code to another user. After clearing the binding relationship and historical query records, the status of the anti-counterfeiting code in the database is updated to unbound; after the anti-counterfeiting code status is reset to unbound, the anti-counterfeiting code can be queried and bound by other users again.

2. The product anti-counterfeiting duplicate query method according to claim 1, characterized in that, The binding relationship is established in the following way: When a user scans the anti-counterfeiting code to access the anti-counterfeiting query page for the first time, the system automatically obtains and binds the user's unique identifier; or, After the user scans the code for the first time, they can click the authorization button on the anti-counterfeiting query page to obtain and bind the user's unique identity.

3. The product anti-counterfeiting duplicate query method according to claim 1 or 2, characterized in that, The request to return the anti-counterfeiting code is completed independently by the bound user; it is triggered by the bound user clicking the return button or the gift button on the product anti-counterfeiting page on the user terminal interface; the bound user automatically unbinds the relationship through the above return steps.

4. The product anti-counterfeiting duplicate query method according to claim 1, characterized in that, The query records include the historical number of queries for the anti-counterfeiting code and the time of the first query.

5. The product anti-counterfeiting duplicate query method according to claim 1, characterized in that, After clearing the binding relationship and historical query records, the status of the anti-counterfeiting code in the database is updated to unbound; after the anti-counterfeiting code status is reset to unbound, the anti-counterfeiting code can be queried and bound by other users again.

6. The product anti-counterfeiting duplicate query method according to claim 1, characterized in that, The anti-counterfeiting code can take the form of a QR code, barcode, or RFID chip.

7. The method for repeated anti-counterfeiting verification of goods according to claim 1, characterized in that, The management terminal allows administrators to monitor the status reset operations and results of the anti-counterfeiting codes.

8. A product anti-counterfeiting duplicate query system, applied to the product anti-counterfeiting duplicate query method according to any one of claims 1-7, characterized in that, Includes an anti-counterfeiting platform, wherein the anti-counterfeiting platform includes: The anti-counterfeiting code generation module is used to generate an anti-counterfeiting code that uniquely corresponds to the product and store the anti-counterfeiting code and its associated product information in the database; The binding management module is used to determine whether the anti-counterfeiting code is being queried for the first time when it receives the anti-counterfeiting code information and the user's unique identity identifier sent by the user terminal. If it is the first time, the module will automatically bind the user's unique identity identifier with the anti-counterfeiting code. The anti-counterfeiting query module is used to receive anti-counterfeiting query requests sent by user terminals, determine whether the anti-counterfeiting code is being queried for the first time, and if it is the first time, trigger the binding management module to bind it. If it is not the first time, verify whether the user identity identifier is consistent with the currently bound user identity identifier. If they are consistent, return the product information and query record. If they are inconsistent, return an error message and terminate the query. The anti-counterfeiting code recycling module is used to receive anti-counterfeiting code return requests sent by user terminals, which contain anti-counterfeiting codes and user identification identifiers. The anti-counterfeiting code initialization module is used to respond to the triggering of the anti-counterfeiting code recycling module, verify whether the user identity identifier in the return request is consistent with the currently bound user identity identifier. If they are consistent, the binding relationship and historical query records are cleared, the anti-counterfeiting code status is reset to unbound, and an initialization success confirmation is sent. If they are inconsistent, the request is rejected and an error message is returned.

9. A product anti-counterfeiting duplicate query system according to claim 8, characterized in that, The binding management module automatically obtains the user's identity identifier and establishes a binding relationship with the anti-counterfeiting code when the user scans the anti-counterfeiting code for the first time; or it obtains the user's identity identifier and establishes a binding relationship with the anti-counterfeiting code when the user clicks the authorization button after scanning the anti-counterfeiting code.

10. The product anti-counterfeiting duplicate query system according to claim 8 or 9, characterized in that, The anti-counterfeiting code recycling module only receives the corresponding anti-counterfeiting code return request when the bound user scans the anti-counterfeiting code through the user terminal and clicks the return button or gift button on the user terminal interface.

Images