RFID Data Interface for Non-Redundant Event Cycle Processing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current RFID data processing systems face challenges in efficiently aggregating and providing non-redundant RFID data to applications, particularly in managing event cycles, boundary specifications, and report outputs, which can lead to data redundancy and inconsistent access control.
Innovation Solution
A computer interface to RFID data that receives event cycle specifications, including RFID sources, boundary definitions, and report specifications, to provide non-redundant RFID data, while allowing for concurrent processing and access control based on application requests, ensuring data integrity and security.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If RFID data is continuously collected from multiple sources, then data completeness is improved, but data redundancy increases
Solution Approach 1:
The system segments RFID data collection into discrete event cycles with defined boundaries. Each event cycle collects data from multiple RFID sources (readers, antennas, logical readers) but processes it as a distinct unit, allowing complete data aggregation within each cycle while managing redundancy through cycle-based processing rather than continuous streams.
Solution Approach 2:
The interface performs preliminary actions by collecting and buffering RFID data during event cycles before providing it to applications. This preliminary data aggregation ensures completeness by capturing all events within the cycle boundary, while the structured approach to cycle management prevents uncontrolled redundancy accumulation.
2Speed
If multiple applications request RFID data concurrently, then system responsiveness is improved, but access control consistency deteriorates
Solution Approach 1:
The system segments concurrent data requests into distinct event cycles with clear boundaries. Each application receives data according to its specific subscription to event cycles, allowing concurrent processing while maintaining access control consistency through the structured cycle framework that tracks which applications should receive which data.
Solution Approach 2:
The RFID interface acts as an intermediary between RFID sources and applications, managing concurrent requests by buffering data during event cycles and distributing it appropriately. This intermediary role allows the system to respond to multiple applications concurrently while maintaining consistent access control through the event cycle specification mechanism.
3Measurement precision
If event cycle boundaries are strictly enforced, then data processing accuracy is improved, but processing flexibility deteriorates
Solution Approach 1:
The system implements dynamic event cycle boundaries that can be configured differently for different applications and scenarios. The boundary specifications allow flexible definition of when cycles start and end, enabling accurate data processing for specific use cases while maintaining the ability to adapt to different processing requirements through configuration rather than rigid fixed boundaries.
Data Source
AI summary
An interface to radio-frequency identification (RFID) data provides RFID data in response to an event cycle specification received from an application. The interface is configured to receive the event cycle specification that identifies one or more RFID sources. The event cycle specification also includes a boundary specification that defines a boundary for an event cycle and a report specification that defines a requested output of a non-redundant RFID data. The interface to RFID data, in response to receiving the event cycle specification, provides an output of non-redundant RFID data conforming to the event cycle specification.