Patent 11334918
Derivative works
Defensive disclosure: derivative variations of each claim designed to render future incremental improvements obvious or non-novel.
Active provider: Google · gemini-2.5-flash
Derivative works
Defensive disclosure: derivative variations of each claim designed to render future incremental improvements obvious or non-novel.
The USPTO database search for patent number 11334918 confirms the patent is active.
Here's a comprehensive "Defensive Disclosure" document for US Patent 11334918, based on the provided framework:
Defensive Disclosure for US Patent 11334918: Exchanging identifiers between wireless communication to determine further information to be exchanged or further services to be provided
This defensive disclosure aims to broaden the prior art landscape surrounding US Patent 11334918, making future incremental advancements by competitors obvious or non-novel. The original patent describes a system and method for brokering information exchange and transactions between proximate wireless devices via a central server, utilizing both short-range and wide area wireless communication. The core innovation lies in the dynamic assignment and server-side management of device identifiers for enhanced security and policy enforcement, preventing direct peer-to-peer identity correlation over time.
Core Claim 1: Method for exchanging information between wireless devices using a central server
Claim 1 Summary: A method involving a first device detecting a unique identifier from a second device via short-range wireless, sending this identifier to a central server via a wide area network, the server retrieving and applying policies to relevant information about the second device/entity, and transmitting that information back to the first device. The identifiers are dynamically updated and centrally managed for anonymity and security.
Derivative Variations for Claim 1:
1. Material & Component Substitution: Low-Power, Long-Range Identifier Transmission with Directional Antennas
Enabling Description: This variation utilizes ultra-low-power, long-range wireless protocols such as LoRaWAN (Long Range Wide Area Network) or NB-IoT (Narrowband-IoT) for the initial identifier transmission, instead of traditional Bluetooth (IEEE 802.15.1) or Wi-Fi (IEEE 802.11). The short-range detection is achieved by employing highly directional antennas (e.g., phased array antennas or switched-beam antennas) on the first device. These directional antennas can dynamically adjust their beamforming to precisely pinpoint the direction of the incoming identifier signal from the second device, effectively creating a "virtual proximity" based on angular resolution rather than signal strength attenuation alone. The second device would broadcast its dynamically assigned identifier at a minimal power output to conserve energy. The first device, equipped with a low-power LoRaWAN/NB-IoT transceiver and a multi-element directional antenna array, scans for these directional identifier broadcasts. Upon detection and angular localization within a predefined threshold, the identifier is relayed to the central server via an existing wide area network connection (e.g., LTE-M or standard LTE for NB-IoT/LoRaWAN backhaul). The server then processes the identifier as per the original patent.
graph TD
A[Second Device (LoRa/NB-IoT Tx)] -- Low-Power ID Broadcast --> B{Directional Antenna Array (First Device)};
B -- Angular Localization --> C[First Device (LoRa/NB-IoT Rx & LTE-M/LTE Tx)];
C -- Detected ID + Angle --> D[Central Server];
D -- Policy Application & Info Retrieval --> E[First Device (Info Display)];
style A fill:#f9f,stroke:#333,stroke-width:2px;
style C fill:#ccf,stroke:#333,stroke-width:2px;
2. Operational Parameter Expansion: Hyper-Local, High-Density Nano-Scale Proximity Detection for Industrial Automation
Enabling Description: This derivative focuses on hyper-local proximity detection (e.g., within 1-100 nanometers) in high-density environments, such as semiconductor fabrication plants or advanced manufacturing lines. The "devices" are microscopic sensors or actuators embedded within components or tools. The "short-range wireless" utilizes near-field communication (NFC) at extremely low power or even quantum-entanglement-based communication principles (theoretical). The identifiers are unique quantum signatures or nano-scale resonant frequencies. The "wide area network" is a localized, ultra-low-latency industrial Ethernet network (e.g., EtherCAT or PROFINET) with specialized gateways for secure server communication. The central server, a high-performance edge computing cluster, manages millions of these nano-scale identifiers, dynamically reassigning quantum signatures to maintain anonymity and track the "life cycle" of individual molecules or atomic structures during manufacturing processes. This allows for real-time quality control, defect detection at an unprecedented scale, and dynamic reconfiguration of assembly lines based on immediate component proximity and state.
graph TD
A[Nano-Sensor/Actuator (Second Device)] -- Quantum/NFC ID --> B(Nano-Scale Proximity Detector (First Device));
B -- Detected ID + Position --> C[Edge Compute Cluster (Central Server)];
C -- Policy & Process Control --> D[Industrial Control System (First Device Application)];
style A fill:#ffb,stroke:#333,stroke-width:2px;
style C fill:#bbf,stroke:#333,stroke-width:2px;
3. Cross-Domain Application: Smart Retail Shelf Management (Agri-Tech)
Enabling Description: In an Agri-Tech context, imagine intelligent shelving units within a vertical farm or greenhouse (First Device) that need to monitor individual plant pots or trays (Second Device). Each plant pot/tray is equipped with a low-cost, short-range RFID tag or a custom low-power, short-range RF beacon emitting a unique, dynamically changing identifier. The shelving unit has integrated RFID readers or RF transceivers. When a new plant pot is placed on a shelf, its identifier is detected. This identifier, along with location data (shelf ID, position on shelf), is sent to a central farm management server (via Wi-Fi IEEE 802.11 or Zigbee over a local mesh network). The server, based on the plant's species, growth stage, and current environmental conditions (retrieved from its account associated with the identifier), provides real-time care instructions, nutrient delivery schedules, or alerts for optimal growth to the shelving unit. The server can dynamically update the identifier of the plant pot over time to prevent unauthorized tracking or "spoofing" of plant conditions.
graph TD
A[Plant Pot/Tray (RFID/RF Beacon)] -- ID Broadcast --> B(Smart Shelf Unit (RFID Reader/RF Rx));
B -- Detected ID + Shelf Pos --> C[Farm Management Server];
C -- Care Instructions/Alerts --> B;
style A fill:#aaffaa,stroke:#333,stroke-width:2px;
style C fill:#ffaacc,stroke:#333,stroke-width:2px;
4. Cross-Domain Application: Predictive Maintenance for Aerospace Components
Enabling Description: In aerospace, individual aircraft components (e.g., engine parts, landing gear actuators) are equipped with miniaturized, robust short-range Ultra-Wideband (UWB) transceivers emitting a unique, dynamically changing identifier and a minimal health status beacon. These components are the "Second Devices". Maintenance crews or automated drone inspection systems carry "First Devices" with UWB receivers. When a First Device is brought into proximity of a component, it detects the UWB identifier and health beacon. This data, along with GPS coordinates and timestamps, is transmitted to a central Predictive Maintenance Server (PMS) via satellite communication (e.g., Inmarsat, Iridium) or a secure airport-wide Wi-Fi 6 (IEEE 802.11ax) network. The PMS, leveraging AI and historical data linked to the dynamically assigned component identifier, analyzes the component's health, predicts potential failure points, schedules preventative maintenance, and updates digital logbooks. The dynamic identifier assignment ensures component anonymity during routine operations and mitigates unauthorized tracking in sensitive environments.
graph TD
A[Aircraft Component (UWB Tx)] -- UWB ID + Health --> B(Maintenance Drone/Crew Device (UWB Rx, SatCom/Wi-Fi 6 Tx));
B -- Detected ID + Geo-data --> C[Predictive Maintenance Server (PMS)];
C -- Maintenance Schedule/Alerts --> B;
style A fill:#ccf,stroke:#333,stroke-width:2px;
style C fill:#ffcc99,stroke:#333,stroke-width:2px;
5. Cross-Domain Application: Immersive Theme Park Experience Personalization
Enabling Description: Within an immersive theme park, guest wearables (e.g., smart wristbands, interactive badges) act as "Second Devices," continuously broadcasting a short-range Bluetooth Low Energy (BLE) identifier (IEEE 802.15.1). Interactive displays, animatronics, or ride entry points throughout the park serve as "First Devices," equipped with BLE receivers. As guests approach an interactive element, their BLE identifier is detected. This identifier is sent to a central Experience Personalization Server (EPS) via the park's dedicated Wi-Fi 6E (IEEE 802.11ax operating in 6GHz) network. The EPS, linked to the guest's profile (associated with the dynamically assigned BLE identifier), triggers personalized greetings from animatronics, adjusts ride experiences, or offers relevant digital content (e.g., augmented reality overlays) to the guest's mobile application. The dynamic identifiers prevent persistent tracking of guest movements by unauthorized third parties within the park.
graph TD
A[Guest Wearable (BLE Tx)] -- BLE ID --> B(Interactive Display/Ride Entry (BLE Rx, Wi-Fi 6E Tx));
B -- Detected ID + Context --> C[Experience Personalization Server (EPS)];
C -- Personalized Content/Triggers --> B;
style A fill:#e0b2e0,stroke:#333,stroke-width:2px;
style C fill:#cceeff,stroke:#333,stroke-width:2px;
6. Integration with Emerging Tech: AI-Driven Contextual Information Exchange with IoT Sensor Fusion
Enabling Description: The first device incorporates multiple IoT sensors (e.g., temperature, humidity, light, accelerometer, gyroscope, microphone) and uses AI for real-time contextual analysis. When the first device detects an identifier from a second device via ultra-low-power Bluetooth 5.x (IEEE 802.15.1), it not only sends the identifier to the central server but also a rich dataset of fused sensor readings and an AI-derived "environmental context" (e.g., "noisy, humid, 25°C, accelerating"). The central server, leveraging machine learning models, uses this contextual information, in addition to the second device's identity, to provide highly nuanced information or services. For instance, if the second device is a smart environmental monitor, and the first device (a drone) detects it in a "high vibration" context, the server might prioritize delivering diagnostic information about potential structural issues rather than routine temperature readings. Dynamic identifiers are crucial for privacy in sensor-rich environments.
graph TD
subgraph Second Device
D1[Bluetooth 5.x Tx]
D1 -- Dynamic ID --> F;
end
subgraph First Device
F[Bluetooth 5.x Rx]
G[Multiple IoT Sensors]
H[AI Contextual Processor]
I[WWAN Transceiver]
F --> H;
G --> H;
H -- Fused Sensor Data + AI Context + Dynamic ID --> I;
end
I -- WWAN --> J[Central Server (ML/AI)];
J -- Contextual Info/Services --> I;
style D1 fill:#ffe0b2,stroke:#333,stroke-width:2px;
style F fill:#e6ffe6,stroke:#333,stroke-width:2px;
style G fill:#e6ffe6,stroke:#333,stroke-width:2px;
style H fill:#e6ffe6,stroke:#333,stroke-width:2px;
style I fill:#e6ffe6,stroke:#333,stroke-width:2px;
style J fill:#cceeff,stroke:#333,stroke-width:2px;
7. Integration with Emerging Tech: Blockchain-Verified Identity and Supply Chain Tracking
Enabling Description: This variation integrates blockchain technology for enhanced trust and verifiable identity. The dynamically assigned identifiers (e.g., cryptographic hashes) broadcast by the second device via short-range communication (e.g., NFC, secure element communication) are linked to a blockchain-based decentralized identity system. When the first device detects an identifier, it sends it to the central server. The central server then interacts with a distributed ledger (blockchain) to verify the authenticity and current status of the second device's identity and its associated supply chain provenance (e.g., manufacturing date, location, ownership history). This provides an immutable record of proximity interactions. The central server acts as an oracle to the blockchain, ensuring that only verified information, compliant with predefined smart contract policies, is returned to the first device. The dynamic identifiers prevent replay attacks and enhance the privacy of physical asset tracking.
graph TD
subgraph Second Device
A[NFC/Secure Element Tx]
A -- Cryptographic Hash ID --> B;
end
subgraph First Device
B[NFC/Secure Element Rx]
C[WWAN Transceiver]
B -- Detected ID --> C;
end
C -- WWAN --> D[Central Server (Blockchain Oracle)];
D -- Verify ID/Provenance --> E(Blockchain/Distributed Ledger);
E -- Verified Data --> D;
D -- Policy & Verified Info --> C;
style A fill:#d9ead3,stroke:#333,stroke-width:2px;
style B fill:#d9ead3,stroke:#333,stroke-width:2px;
style C fill:#d9ead3,stroke:#333,stroke-width:2px;
style D fill:#fce5cd,stroke:#333,stroke-width:2px;
style E fill:#c2e0f4,stroke:#333,stroke-width:2px;
8. The "Inverse" or Failure Mode: Proximity-Activated Emergency Beacon with Limited Functionality
Enabling Description: This derivative describes a "fail-safe" or "limited-functionality" mode for critical situations. The second device is an emergency beacon (e.g., in a life raft, a downed aircraft, or a medical alert pendant). When this second device detects an external condition (e.g., immersion in water, impact, loss of vital signs), it switches to a low-power, intermittent broadcast mode, transmitting a specific "emergency identifier" via a robust, frequency-hopping spread spectrum (FHSS) short-range radio (e.g., a modified BLE or custom sub-GHz radio). The "First Device" (e.g., a search and rescue drone, a personal emergency responder device) detects this emergency identifier. Instead of requesting full information, the First Device immediately relays the identifier, its own GPS coordinates, and the received signal strength indication (RSSI) of the emergency beacon to a central emergency services server via a resilient satellite uplink (e.g., Iridium SBD) or a dedicated public safety LTE network. The server then initiates emergency protocols, prioritizing location and resource deployment, without attempting to retrieve extensive personal information from the emergency beacon's associated account. The dynamic identifiers, in this context, are rotated less frequently or are public-facing but cryptographically secured to prevent false alarms while maintaining anonymity of the distressed party until rescue.
graph TD
A[Emergency Beacon (Second Device)] -- Emergency ID (FHSS, Low Power) --> B(SAR Drone/Responder Device (First Device));
B -- Emergency ID + GPS + RSSI --> C[Emergency Services Server];
C -- Trigger Emergency Protocols --> D(Rescue Operations);
style A fill:#ffcccc,stroke:#333,stroke-width:2px;
style C fill:#cc99ff,stroke:#333,stroke-width:2px;
9. The "Inverse" or Failure Mode: Anonymous Public Space Access Control with Privacy-Preserving Identifier Revelation
Enabling Description: In this "limited functionality" mode, the system focuses on privacy by default for public spaces (e.g., public transportation, event venues). The second device (a user's mobile phone) broadcasts a highly anonymized, frequently rotating short-range identifier (e.g., a transient MAC address for Wi-Fi or a random Bluetooth address). The first device (an access gate, turnstile) detects this anonymized identifier. Instead of requesting full user information, the first device sends the identifier to a central access control server. The server's policy is to only verify if the anonymized identifier is associated with an active, valid ticket or access credential without revealing the user's personal identity. If valid, the server sends a simple "Access Granted" signal back to the first device. If more information is needed (e.g., for age-restricted access), a multi-step process is initiated where the user is prompted on their device to explicitly grant temporary, specific data disclosure, and a new, unique, single-use identifier is generated for that specific transaction. This ensures minimal information revelation by default.
graph TD
A[User Mobile (Anonymized ID Tx)] -- Anonymized ID --> B(Access Gate/Turnstile (ID Rx));
B -- Anonymized ID --> C[Central Access Control Server];
C -- Check Valid Credential (No PII) --> D{Credential Database};
D -- Valid/Invalid --> C;
C -- Access Granted/Denied --> B;
alt If more info needed (e.g., age verification)
C -- Prompt User for Disclosure --> A;
A -- Grant Disclosure (New Single-Use ID) --> C;
end
style A fill:#d0f0c0,stroke:#333,stroke-width:2px;
style C fill:#aaddff,stroke:#333,stroke-width:2px;
style D fill:#ffcc99,stroke:#333,stroke-width:2px;
Combination Prior Art Scenarios
US11334918 + IEEE 802.15.4 (Zigbee/Thread): The patent's core mechanism of short-range identifier detection and server-brokered communication is combined with the low-power, mesh networking capabilities of IEEE 802.15.4 standards, such as Zigbee or Thread. This allows for distributed detection of identifiers across a broad area (e.g., a smart city block or a large agricultural field) where each Zigbee/Thread node acts as a "First Device," detecting identifiers from nearby "Second Devices" (e.g., smart waste bins, environmental sensors). The mesh network aggregates these detections and relays them to a central server via a single gateway. The server still manages the dynamic identifiers and applies policies.
US11334918 + DSRC (IEEE 802.11p): The patent's principle is applied to Vehicular Ad-hoc Networks (VANETs) using Dedicated Short Range Communications (DSRC) based on IEEE 802.11p. Vehicles (First Devices) detect identifiers from other vehicles or roadside units (Second Devices) using DSRC. This detected identifier, along with vehicle telemetry (speed, direction, braking status), is sent to a central traffic management server via a cellular wide area network (e.g., 5G NR). The server processes the identifiers and vehicle data, applying policies for collision avoidance alerts, traffic flow optimization, or personalized road hazard warnings. Dynamic identifiers can be used to prevent unauthorized vehicle tracking.
US11334918 + LoRaWAN (IEEE 802.15.4g/e): This combines the patent's server-brokered communication with LoRaWAN's long-range, low-power capabilities for widespread, sparse deployments. LPWAN gateways (First Devices) detect identifiers from numerous LoRaWAN-enabled sensors or asset trackers (Second Devices) spread over several square kilometers. The identifiers are transmitted over the LoRaWAN network to a central cloud server. The server then uses these identifiers to track asset locations, monitor environmental conditions across a large area, or manage inventory, dynamically updating the LoRaWAN device identifiers for security and privacy.
Generated 5/19/2026, 12:46:54 AM