Proximity Discovery System with Segmented Data Exchange
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Proximity detection technologies in computing systems are limited by the restricted amount of information that can be exchanged, hindering functionalities such as user identification and data communication between devices, as seen in scenarios like hotel lobby systems where insufficient data in proximity messages prevents user information from being displayed on employee terminals.
Innovation Solution
A system where a mobile device receives a proximity message with a unique identifier, sends a notification to a server, which determines the device's proximity and sends user metadata to associated computing systems, enabling more comprehensive operations based on the user's location.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Quantity of substance
If proximity messages contain only minimal data necessary for proximity detection, then the message size is reduced and transmission efficiency is improved, but the usefulness of the messages is hindered as they cannot support two-way communication or include sufficient information for additional functionalities
Solution Approach 1:
The message exchange process is segmented into multiple stages: initial proximity detection messages with minimal data, followed by subsequent data exchange phases where additional information is transmitted. This allows the system to start with small messages for quick proximity detection, then progressively exchange more comprehensive data including user identifiers, device information, and operational parameters in separate transmission phases.
Solution Approach 2:
The system performs preliminary proximity detection using minimal message data first, establishing the basic communication channel and confirming device proximity before initiating more comprehensive data exchange. This preliminary action enables the system to determine whether further communication is necessary, avoiding unnecessary transmission of large data sets when devices are not in proximity.
2Loss of energy
If messages are designed to contain only data necessary for proximity detection, then transmission bandwidth is conserved and energy consumption is reduced, but the messages cannot be used for functionality other than determining proximity
Solution Approach 1:
Energy-efficient segmented communication where proximity detection uses minimal energy-consuming messages, and additional functionality data is transmitted only when proximity is confirmed and further interaction is required. The system divides communication into essential proximity detection phase and optional data exchange phase, allowing energy consumption to be proportional to actual functionality needs.
Solution Approach 2:
The system transmits only the partial amount of data necessary for the current operational context. Instead of always transmitting complete device profiles or capability sets, messages include only the data currently needed for the specific interaction, whether that's basic proximity confirmation or extended functionality data, thereby optimizing energy usage based on actual requirements.
Data Source
AI summary
A first computing system can receive a proximity message from a source device, the proximity message comprising a device identifier and a network address. The first computing system can further determine that the first computing system is within a particular distance of the source device based, at least in part, on the proximity message. In response, the first computing system can send a proximity notification to a second computing system. The proximity notification can comprise the device identifier and a user identifier. The second computing system can receive the proximity notification. The second computing system can further determine user metadata associated with the user identifier. The second computing system can further determine a third computing system based, at least in part, on a mapping between the device identifier and a computing system identifier. The second computing system can further send the user metadata to the third computing system.