Central Index for RFID Data with Privilege Control
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In multi-party supply chain transactions, controlling access to product code information is challenging due to the impracticality of a single repository managing data from all parties, and existing solutions fail to securely share data without pre-existing business relationships, leading to issues with data discovery and entitlement.
Innovation Solution
A central data repository that stores index information and permission data from all parties, allowing authorized access and enabling parties to retrieve product code information from specific data providers, even without prior business relationships, by using permission information to authenticate and authorize data access.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If a single repository is used to hold product code information from all parties, then data centralization and accessibility are improved, but data security and party control over their own data are worsened
Solution Approach 1:
The patent divides the centralized repository into distributed data providers, where each party maintains control of their own data while contributing to a collective system. Index information is segmented and distributed across multiple parties rather than consolidated in a single repository, allowing each party to manage their own data security while enabling system-wide accessibility.
Solution Approach 2:
The patent introduces an intermediary mechanism in the form of index information that mediates between data providers and data seekers. This intermediary layer allows parties to discover and access relevant data without direct exposure to each other's complete datasets, maintaining security while enabling accessibility.
2Reliability
If each party retains product code information in its own data repository, then data security and party control are improved, but data discovery and retrieval efficiency are worsened
Solution Approach 1:
The patent implements preliminary action by having data providers pre-publish index information about their data holdings before any retrieval request occurs. This index information includes identifiers and metadata that enable rapid discovery of relevant data providers, eliminating the need for time-consuming searches or negotiations when actual data retrieval is needed.
Solution Approach 2:
The patent establishes a feedback mechanism where the system learns from retrieval patterns and can optimize future data discovery. When parties query for product code information, the system uses the index to efficiently route requests and can refine its indexing strategy based on usage patterns, improving retrieval efficiency over time while maintaining the distributed security model.
3Reliability
If a distributed system is used where parties query each other for data, then data control and security are improved, but system complexity and authentication requirements are worsened
Solution Approach 1:
The patent applies universality by creating a standardized index information format and query protocol that works across all data providers and seekers in the system. This universal interface simplifies the distributed architecture by providing consistent methods for data discovery and retrieval, reducing the complexity that would otherwise arise from managing multiple different data access protocols.
4Reliability
If permission information is added to control access to index information, then data security and authorization are improved, but system complexity and processing overhead are worsened
Solution Approach 1:
The patent applies local quality by implementing fine-grained permission control where each data provider can specify different access rights for different types of information in the index. Rather than applying a single permission level system-wide, the system allows localized permission settings at the data provider level, enabling precise control over what index information can be disclosed to whom without requiring complex global permission management.
Data Source
AI summary
In one embodiment, a central data repository stores product code information. The central data repository can receive permissions from providers of the produce code information. The permissions can indicate whether the product code information can be provided to a third party.