WebRTC Peer-to-Peer RFID Data Acquisition
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional network-based RFID data acquisition systems face latency issues with real-time data and require server access, which can be problematic for immediacy and may not function when server access is unavailable, and they often need software updates when switching between different RFID reader manufacturers.
Innovation Solution
Implementing HTML5 and WebRTC-compatible devices for peer-to-peer communication between RFID data acquisition and access devices, allowing direct data transfer without server storage and enabling reader-agnostic software modules that maintain compatibility with different RFID readers, reducing the need for frequent software updates.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If data is transmitted through a network server for storage and retrieval, then data can be accessed by multiple devices, but latency increases and real-time data transfer is compromised
Solution Approach 1:
The patent extracts the data storage and relay function from the network server, allowing acquisition devices to transmit data directly to access devices without server intervention. This eliminates the server as an intermediate node in the data path, reducing latency while maintaining accessibility through direct peer-to-peer connections.
Solution Approach 2:
The patent introduces a peer-to-peer communication protocol as an intermediary mechanism that enables direct data transfer between acquisition and access devices. This intermediary layer replaces the traditional server-mediated communication model, allowing real-time data exchange while preserving the ability for multiple devices to access data through the network.
2Device complexity
If a traditional client/server architecture is used, then centralized data management is achieved, but bandwidth and energy efficiency are reduced due to server relays
Solution Approach 1:
The patent inverts the traditional client/server data flow model by allowing acquisition devices to directly communicate with access devices. Instead of all data flowing through the server, the architecture enables direct peer-to-peer transmission, eliminating unnecessary data routing through the server and improving bandwidth and energy efficiency.
3Reliability
If RFID reader software is manufacturer-specific, then compatibility with particular readers is ensured, but software updates are required when switching readers
Solution Approach 1:
The patent implements a universal software architecture where the acquisition device software can communicate with multiple RFID reader manufacturers through standardized interfaces. The software is designed to be reader-agnostic, supporting different reader types without requiring manufacturer-specific applications, thereby enabling flexibility while maintaining reliable communication.
Solution Approach 2:
The patent segments the software functionality into reader-specific communication modules and core acquisition logic. This modular approach allows the system to support multiple reader manufacturers through interchangeable communication adapters while preserving the core data acquisition and processing functions, enabling software updates without requiring complete software replacement.
Data Source
AI summary
In certain embodiments, a network-based data acquisition system has an acquisition device and an access device. The acquisition device has (a) a reader-specific module that (i) receives reader-specific data generated by a data reader (e.g., an RFID or other type of reader) and (ii) converts the data from the reader-specific format into reader-agnostic data in a reader-agnostic format and (b) at least one reader-agnostic module that (i) receives the reader-agnostic data from the reader-specific module and (ii) transmits the reader-agnostic data to the access device. In one implementation, the access device runs a web browser that accesses a web server on a controller of the acquisition device, and the reader-agnostic data is transmitted from the controller to the access device via a point-to-point communication path, such as a WebRTC data channel. The reader-specific module can be replaced/modified to support a new data reader without having to replace/modify any reader-agnostic module.