RFID Event Tracking Database Models for Industry Verticals
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current RFID event tracking and management systems lack standardized data access control, leading to data loss and reliability issues, incomplete data handling, and industry-specific data model inflexibility, which complicates secure data visibility and accurate event interpretation across supply chains.
Innovation Solution
Implementing an RFID event tracking system with a standardized, object-oriented database approach using industry-specific data models generated from a common core data model, coupled with virtual private databases for role-based access control and event compensation mechanisms to ensure secure and accurate data handling.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of manufacture
If a common core data model is used for all industries, then system simplicity and ease of implementation are improved, but industry-specific data model flexibility and adaptability deteriorate
Solution Approach 1:
The patent segments the data model into two distinct layers: a common core data model that provides standardized RFID event tracking functionality, and industry-specific vertical data models that extend the core model with domain-specific attributes and relationships. This segmentation allows each layer to be developed and maintained independently, resolving the contradiction between implementation simplicity and industry adaptability.
Solution Approach 2:
The patent implements a nested data model structure where industry-specific vertical data models are built upon and contain the common core data model. The vertical models inherit from the core model and add industry-specific extensions, creating a nested hierarchy that combines the simplicity of a common foundation with the flexibility of specialized extensions.
2Reliability
If role-based access control is implemented, then data security and visibility control are improved, but system complexity and implementation difficulty deteriorate
Solution Approach 1:
The patent implements a universal role-based access control framework that can be applied across all industries and data types within the RFID event tracking system. The access control mechanism provides multi-functional capabilities including role definition, permission management, and dynamic visibility control, reducing the need for separate security implementations in different contexts.
Solution Approach 2:
The patent introduces an intermediary access control layer that sits between the data storage layer and the application layer. This intermediary framework handles authentication, authorization, and visibility control, shielding the underlying system complexity from end users while providing robust security controls.
3Measurement precision
If RFID tags provide unique information for each item instance, then tracking accuracy and data completeness are improved, but data management complexity and processing requirements deteriorate
Solution Approach 1:
The patent extracts and separates the identification function from the data management function. RFID tags provide unique identification information for each item instance, which is then extracted and processed through standardized event tracking mechanisms. This separation allows accurate tracking while managing data complexity through structured event processing rather than raw data handling.
Solution Approach 2:
The patent transforms the unique item identification data from RFID tags into standardized event parameters through the common core data model. By changing the parameter representation from raw RFID data to structured event objects with standardized attributes, the system maintains tracking accuracy while reducing data management complexity.
Data Source
AI summary
An RFID event tracking and management system provides a standardized approach that can be utilized by various industry verticals. A series of industry-specific data models can be built upon a common data model using an object-oriented database and relational mapping tool. Using the industry-specific data models, an object-oriented database is generated that can be used by all vertical applications that sit on top of the database. The data models can be defined using a data model service, such that query and capture interfaces can interact with the respective data model. Such an approach allows the data models to be dynamic, which is desirable as a single static data model is not appropriate for all industries.