Label Authentication System Using Segmented Code Databases
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current authentication systems for labels lack security during manufacturing and do not effectively prevent fraud, as they only focus on validation after labels are made available to the public, without considering potential fraud by authorized manufacturers.
Innovation Solution
An authentication system using a label with three codes, where each code is generated independently and stored in two separate databases, ensuring that no single database contains all necessary information for label reproduction, with secure access protocols to prevent unauthorized access and fraud.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If all code information is stored in a single database, then label verification is simplified, but the system becomes vulnerable to fraud during manufacturing
Solution Approach 1:
The authentication system divides the code information into multiple separate databases (first database, second database, third database), each storing different codes. This segmentation prevents any single point of failure or fraud during manufacturing, while still enabling complete verification when all databases are consulted together.
2Reliability
If security protocols are made more restrictive to prevent fraud, then manufacturing security is improved, but compliance complexity increases
Solution Approach 1:
By dividing security responsibilities across multiple independent databases with different access protocols, the system achieves strong overall security without requiring a single complex restrictive protocol. Each database can have simpler, more specialized access controls.
3Ease of operation
If a single database stores all codes, then data access is simplified, but the system cannot integrate multiple logistical stakeholders
Solution Approach 1:
The system assigns different databases to different stakeholders (first database to one entity, second database to another, third database to yet another), enabling multi-party integration. Each stakeholder manages their own database with appropriate access rights, facilitating collaborative logistics while maintaining security.
Data Source
Figure 1~1b
Figure 2a~4
Figure 5
AI summary
The invention relates to an authentication system comprising a label with at least three codes that are not known from a single database when the label is produced, but from at least two databases generated by independent processes, such that it is not possible, without consulting the different databases, to know whether a label is authentic, even if the three codes become accessible in the public domain. More particularly, the invention proposes an authentication system comprising a label with at least three codes for identifying and validating the authenticity of said label, characterised in that the system comprises: - at least two independent databases BD in which said at least three codes are entered, and in that each database BD comprises: - an unknown code from the other database, - a known code from the two databases, -said known code being paired with one of the unknown codes