Distributed Hash Table Client Device Information Storage
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing WLAN systems face challenges in efficiently managing client device information across multiple access points, particularly in maintaining seamless network access and multicast subscriptions when a client device switches between access points, due to the lack of a centralized and efficient data storage and retrieval mechanism for client device state information.
Innovation Solution
A distributed set of nodes, such as a Distributed Hash Table (DHT), is used to store client device information keyed by client device identifiers, allowing access points to quickly retrieve and update authentication, multicast, and encryption information by applying a hash function to the client device's MAC address, enabling concurrent creation of encryption keys and resumption of multicast subscriptions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Speed
If a centralized storage mechanism is used for client device information, then data retrieval efficiency is improved, but system complexity and single point of failure risk increase
Solution Approach 1:
The patent segments the centralized storage system into multiple distributed nodes forming a Distributed Hash Table (DHT). Each node stores a portion of client device information, eliminating the single point of failure while maintaining efficient retrieval through hash-based addressing. The segmentation transforms a monolithic centralized system into a scalable distributed architecture.
Solution Approach 2:
The patent introduces a hash function as an intermediary mechanism that maps client device identifiers (MAC addresses) to specific nodes in the distributed storage system. This intermediary enables efficient data location and retrieval without requiring direct access to all nodes, resolving the complexity issue while maintaining speed.
2Speed
If client device information is stored locally at each access point, then access speed is improved, but data consistency and roaming capability deteriorate
Solution Approach 1:
The distributed hash table serves multiple functions simultaneously: it stores client device information for fast access, maintains data consistency across the network through its distributed architecture, and enables seamless roaming by allowing any access point to retrieve client information via the hash-based addressing system. This universal structure resolves the trade-off between local access speed and network-wide reliability.
3Measurement precision
If sequential processing is used for encryption key creation and multicast subscription resumption, then processing accuracy is improved, but network performance and client roaming speed deteriorate
Solution Approach 1:
The patent retrieves client device information from the distributed hash table in advance, before the client actually needs to roam or before encryption key creation and multicast subscription resumption are required. This preliminary retrieval enables subsequent operations to proceed in parallel without compromising accuracy, as all necessary data is already available when needed.
Solution Approach 2:
The distributed hash table maintains continuous availability of client device information, allowing encryption key creation and multicast subscription resumption to occur concurrently and continuously without sequential waiting. The system ensures data consistency while enabling parallel processing, maintaining both accuracy and high network performance during client roaming operations.
Data Source
AI summary
A method includes identifying a first node in a plurality of nodes based on a client device identifier for a client device, the client device being associated with a first network device; storing, information for the client device, on the first node; responsive to the client device associating with a second network device, retrieving the information for the client device by: identifying the first node based on the client device identifier for the client device and obtaining the information from the first node.


