Stable Device ID Synchronization for RCM Network Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In multi-AP networks, the use of Randomized Change MAC (RCM) by non-AP stations (STAs) complicates network topology management, client steering decisions, and Quality of Service (QoS) management, leading to incorrect network topology, unsuitable client steering, and outdated QoS policies.
Innovation Solution
Implementing a device identification synchronization mechanism across APs and STAs in the network, where a unique device identification is assigned during association and propagated throughout the network, allowing for accurate tracking and management of STAs with RCM, even across multiple APs.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Object-affected harmful factors
If RCM is used by STAs to protect privacy, then privacy protection is improved, but network topology management accuracy deteriorates
Solution Approach 1:
The patent introduces an intermediary mapping mechanism where a stable device identifier (not the changing MAC address) is used as a key to map to the current RCM. The controller maintains a mapping table that associates the stable device identifier with the current randomized MAC address. This intermediary mapping allows the system to protect privacy through RCM while maintaining accurate network topology management by using the stable identifier as the true key for tracking devices.
Solution Approach 2:
The system performs preliminary actions by establishing a mapping relationship between the stable device identifier and the RCM before the RCM changes. When a device first associates with an AP, the controller creates and stores the mapping between the device's stable identifier and its current MAC address. This preliminary mapping enables subsequent tracking even as the MAC address randomizes, resolving the contradiction between privacy protection and topology accuracy.
2Object-affected harmful factors
If RCM is used by STAs, then client steering decision accuracy deteriorates, but privacy protection is improved
Solution Approach 1:
The system implements feedback mechanisms where APs report device metrics and status to the controller using the stable device identifier as the key. The controller uses this feedback information, associated with the stable identifier rather than the changing RCM, to make accurate client steering decisions. The feedback loop maintains consistency between the identifier and the device it represents, enabling accurate steering decisions while preserving privacy through RCM.
Solution Approach 2:
The stable device identifier acts as an intermediary that bridges the gap between the changing RCM and the need for consistent client steering decisions. By using this intermediary identifier to track and evaluate device performance metrics across different APs, the system can make accurate steering decisions without exposing the actual device identity, thus maintaining both privacy protection and decision accuracy.
3Object-affected harmful factors
If RCM is used by STAs, then QoS management effectiveness deteriorates, but privacy protection is improved
Solution Approach 1:
The stable device identifier serves as a reliable intermediary for QoS management, decoupling the QoS policy application from the changing RCM. The controller maintains QoS policies associated with the stable identifier, ensuring consistent and effective QoS management regardless of MAC address randomization. This intermediary approach maintains reliability in QoS delivery while preserving user privacy through RCM.
Solution Approach 2:
The system performs preliminary setup of QoS policies based on the stable device identifier before the RCM changes affect service delivery. By establishing the QoS policy framework using the stable identifier in advance, the system ensures continuous and effective QoS management even as the MAC address randomizes, resolving the contradiction between privacy protection and QoS reliability.
4Measurement precision
If device identification is propagated across all APs, then network topology management accuracy is improved, but device complexity increases
Solution Approach 1:
The stable device identifier acts as a simplified intermediary that propagates across APs without requiring complex synchronization mechanisms. Each AP maintains a local mapping between the stable identifier and current RCM, but the identifier itself propagates simply through the network. This approach improves topology management accuracy while minimizing device complexity by using a straightforward propagation mechanism for the stable identifier.
Solution Approach 2:
The system performs preliminary distribution of the stable device identifier to relevant APs during the device association process. This preliminary action ensures that all necessary APs have the identifier before it is needed for topology management, simplifying subsequent operations and reducing the complexity of real-time synchronization while maintaining accurate topology information across the network.
Data Source
AI summary
Embodiments of the present disclosure relate to a communication device, method, and apparatus, and a computer-readable medium. In one aspect, a first access point (AP) device assigns a device identification to a station (STA) device during performing an association process with the STA device. In addition, the first AP device transmits the device identification assigned to the STA device to at least one of a second AP device or a control device. In this way, the performance of a communication network can be improved. For example, an EasyMesh network with improved performance can be achieved.