RFID Transponder Event Notification via Edited Identifier
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The low bandwidth of the RF link in RFID systems hampers the efficient transfer of large data, such as firmware updates, and prioritization of event notifications, leading to delayed action responses due to inability to set priority for event notifications.
Innovation Solution
A system where a transponder stores an event identifier in its memory to form an edited identifier, allowing the transponder to set priority for data transmission and ensure timely event notification by querying the transponder reader with a masking query that includes the event identifier.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Speed
If data is transmitted via the RF link between RFID transponder and reader, then wireless communication is achieved, but transfer speed is slow due to low bandwidth
Solution Approach 1:
The identifier is divided into multiple portions, with different portions stored in different memory locations (EPC memory and TID memory). This segmentation allows selective transmission of critical event notification portions via RF link while other data can be transferred through higher bandwidth backhaul connections, effectively bypassing the RF bandwidth limitation for non-critical data.
Solution Approach 2:
The event notification information is extracted from the full identifier and placed in a specific memory location that can be quickly accessed and transmitted. By separating the event notification portion from other identifier data, the system can prioritize transmission of time-critical event information through the RF link without waiting for complete data transfer.
2Loss of time
If all data is transmitted equally via RF link, then simple transmission protocol is maintained, but event notifications are delayed due to lack of prioritization
Solution Approach 1:
Different memory locations within the transponder are assigned different qualities or priorities for data storage. The EPC memory location is designated specifically for event notification data, giving it higher priority for RF transmission. This local differentiation allows the system to prioritize event notifications without complex global priority management mechanisms.
Solution Approach 2:
Event notification data is pre-positioned in a specific memory location (EPC memory) before transmission is needed. This preliminary placement ensures that when an event occurs, the notification data is already in the optimal position for immediate RF transmission, eliminating delays associated with data retrieval and prioritization during transmission.
3Productivity
If large amounts of data are transferred via backhaul connection, then data completeness is ensured, but transfer time increases due to processing requirements
Solution Approach 1:
Data is segmented into critical event notifications (stored in EPC memory) and non-critical data (stored in TID memory or other storage). Critical event notifications can be transmitted immediately via RF link, while non-critical data such as firmware updates are transferred through the backhaul connection at more convenient times, improving overall system productivity without compromising data completeness.
Data Source
AI summary
A system for event notification based on editing a transponder identifier is disclosed herein. The system may include a sensor system, a transponder, a transponder reader, and a controller. The system may detect an event associated with a sensor. The system may identify a transponder associated with the sensor. The system may cause the transponder to store an event identifier in a memory location of an identifier, of the transponder, to form an edited identifier. The event identifier may be associated with the event. The system may determine that the transponder responded to the query from the transponder reader. The system may store a confirmation that the event identifier was provided to the transponder reader via the transponder.


