RFID Tag Counting via Local-Remote Segmentation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current RFID tag counting systems face delays and inefficiencies due to large database downloads, memory limitations, and excessive bandwidth usage, especially in large-scale environments with millions of tags, leading to difficulties in monitoring progress, preventing duplicate counting, and handling exclusions.
Innovation Solution
Implementing a system where handheld RFID readers perform tag read operations, process new tag information locally, and communicate only newly detected tags to a remote server, which then updates records in batches, reducing bandwidth traffic and eliminating the need for large initial database downloads, and allowing for immediate start of tag reading without prior list transfer.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the entire database of RFID tag identifiers is downloaded into each handheld RFID reader, then duplicate counting can be prevented, but the system experiences large delays at the start of cycle counting and exceeds RFID reader memory capabilities
Solution Approach 1:
The system segments the database management function between the handheld RFID reader and the remote server. Instead of downloading the entire database to each reader, the reader maintains a local list of recently read tags for immediate duplicate detection, while the server maintains the comprehensive database and handles duplicate detection for tags read by multiple readers. This segmentation eliminates the need for large database downloads to each device while still preventing duplicate counting.
Solution Approach 2:
The system extracts the heavy database storage and processing burden from the handheld RFID reader and relocates it to the remote server. The reader only stores essential local information (recently read tags and exclusion lists), while the server handles the complete database operations. This extraction allows the system to scale to millions of tags without exceeding reader memory capabilities.
2Reliability
If RFID tag read information is distributed to each RFID reader to prevent duplicate counting, then duplicate prevention is achieved, but bandwidth traffic is multiplied by the number of RFID readers
Solution Approach 1:
The system merges the duplicate detection function into a centralized server that receives tag read information from all readers. Instead of each reader receiving and processing information from every other reader (N×N communication), all readers send their data to the server, which consolidates and processes it centrally (N×1 communication). This merging dramatically reduces network bandwidth consumption while maintaining duplicate prevention capability.
Solution Approach 2:
The remote server acts as an intermediary that receives tag read information from all RFID readers and coordinates duplicate detection. Rather than readers directly communicating with each other, the server mediates the information flow, consolidating data from multiple readers and preventing duplicates centrally. This intermediary role eliminates the need for multiply-distributed data transmission.
3Adaptability or versatility
If a large list of RFID tag identifiers is sent to RFID readers for exclusions, then exclusion functionality is provided, but the time to send the list delays the start of tag reading process
Solution Approach 1:
The system applies local quality by providing exclusion functionality only where needed - the handheld RFID reader receives a localized exclusion list containing only tags that should be excluded in the reader's specific operating context. The comprehensive exclusion database remains on the server, but each reader gets only the relevant subset, enabling fast startup while maintaining exclusion capability.
4Loss of information
If the system monitors cycle counting progress in real-time, then completion status can be tracked, but the complexity of synchronizing multiple RFID readers increases
Solution Approach 1:
The remote server implements a feedback mechanism that automatically tracks and monitors cycle counting progress by receiving tag read information from all readers and comparing it against the master database. The server maintains real-time knowledge of counting status, completion percentage, and duplicate detection results without requiring complex synchronization protocols between readers. This centralized feedback approach simplifies the system while enabling comprehensive monitoring.
Data Source
AI summary
Systems and methods for operating a tag reader. The methods comprise: performing tag read operations by the tag reader to read tags; processing first information received from the read tags to identify which tags are newly detected tags; adding entries for the newly detected tags in a local list stored in a local memory of the tag reader; communicating second information at least identifying the newly detected tags from the tag reader to a remote computing device; receiving, by the tag reader, feedback information generated by the remote computing device which specifies at least a count of entries added to a remote list stored in a remote datastore based on the second information; and selectively outputting a notification from the tag reader based on the value of the count.