Protected AID Change Requests for Vendor-Specific PPDU Negotiation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Wi-Fi devices struggle to manage vendor-specific features when connecting to multiple networks due to conflicts in association identifier (AID) assignments, leading to confusion and incorrect application of proprietary features.
Innovation Solution
Client devices send an AID change request to network devices to resolve conflicts, using an AID List Veto element or a simple request for a new AID, ensuring unique AIDs are assigned to avoid confusion and enable proper communication of vendor-specific features across different networks.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a client device connects to multiple networks with vendor-specific features, then the device can access diverse network capabilities and optimize performance, but conflicts in AID assignments cause confusion and incorrect application of proprietary features
Solution Approach 1:
The patent applies preliminary action by having the client device check for AID conflicts before completing the association process. The device receives an AID from the network, checks whether it conflicts with existing AIDs, and only then proceeds with vendor-specific feature negotiation. This prevents confusion before it occurs rather than trying to resolve it afterward.
Solution Approach 2:
The patent implements feedback through the AID conflict checking mechanism. When a conflict is detected, the client device sends an AID change request back to the network device, which responds with a new AID assignment. This feedback loop ensures that the correct AID is established before feature negotiation proceeds, maintaining reliability across multiple networks.
2Productivity
If vendor devices introduce proprietary PHY-layer features, then competitive advantages and performance optimization are achieved, but conflicts arise when the same AID is assigned across different networks with different vendor-specific features
Solution Approach 1:
The patent applies preliminary action by checking for AID conflicts before completing the association process. The device receives an AID from the network, checks whether it conflicts with existing AIDs, and only then proceeds with vendor-specific feature negotiation. This prevents confusion before it occurs rather than trying to resolve it afterward.
Solution Approach 2:
The AID serves as an intermediary that links the client device to the correct vendor-specific features for each network. By ensuring unique AID assignments through the conflict checking mechanism, the system maintains a clear mapping between AIDs and their associated features, simplifying the management of multiple vendor-specific feature sets.
3Reliability
If the client device checks for AID conflicts before association, then correct feature negotiation is enabled, but additional processing steps and communication overhead are introduced
Solution Approach 1:
The patent applies preliminary action by having the client device check for AID conflicts immediately upon receiving an AID from the network, during the association process. This early detection prevents incorrect feature negotiation later, ensuring reliability without requiring separate verification steps after association is complete.
Solution Approach 2:
The client device performs self-service by autonomously checking for AID conflicts and initiating AID change requests when needed, without requiring external intervention or complex coordination with other networks. This self-managed approach maintains reliability while minimizing additional overhead.
Data Source
AI summary
The present disclosure provides techniques to avoid conflicts in vendor-specific negotiation by using a protected AID change request. A client device sends an association request to a network device. The client device receives an association identifier (AID) from the network device in response to the association request. The client device determines that the AID conflicts with one or more existing AIDs already assigned to the client device. In response to the determination, the client device sends an AID change request to the network device for a new AID. The client device receives the new AID from the network device, and confirms that the new AID does not conflict with the one or more existing AIDs. In response to the confirmation, the client devices complete a negotiation of one or more vendor-specific features with the network device using the new AID.