Vendor-Specific PPDU Format for Wi-Fi 8 Interoperability
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing IEEE 802.11 network protocols face challenges in managing vendor-specific Physical Layer (PHY) features without confusing third-party stations, as reserved bits in the PHY header are non-robust and prone to haphazard use, leading to network confusion.
Innovation Solution
Incorporating a vendor-specific signal field (VS-SIG) in the Physical Layer Protocol Data Unit (PPDU) with bits indicating its presence and language, allowing vendors to include proprietary data in a standardized format that can be understood by themselves and partners without affecting third-party stations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If vendors use reserved bits in the PHY header to add proprietary PHY features, then vendors can include vendor-specific features in PPDUs, but different vendors using reserved bits in different ways leads to network confusion and reduced reliability
Solution Approach 1:
The patent segments the PPDU structure by introducing a dedicated vendor-specific signal field (VS-SIG) separate from the standard PHY header. This field is positioned between the EHT-SIG and EHT-STF fields, allowing vendor-specific information to be isolated from the standard protocol fields. The VS-SIG contains specific subfields including vendor-specific data and language identification, enabling vendors to include proprietary features while maintaining clear separation from standard IEEE 802.11 fields, thus preventing network confusion.
Solution Approach 2:
The patent introduces an intermediary mechanism - the VS-SIG field with language identification subfield - that acts as a mediator between vendor-specific implementations and the standard protocol. The language identification subfield enables receiving stations to identify whether vendor-specific data is present and how to interpret it, allowing third-party stations to skip or ignore vendor-specific portions while vendor-aware stations can process them appropriately. This intermediary structure resolves the contradiction by enabling vendor adaptability without compromising network-wide reliability.
2Ease of manufacture
If vendors utilize reserved bits in the PHY header, then implementation is simple and requires minimal structural changes, but the reserved bits are non-robust and prone to haphazard use leading to confusion
Solution Approach 1:
Rather than attempting to extend existing reserved bits in the PHY header, the patent creates a dedicated VS-SIG field segment within the preamble structure. This segmentation provides a robust, standardized container for vendor-specific data with clearly defined subfields. The VS-SIG includes specific structure with vendor-specific data subfield and language identification subfield, ensuring that vendor features are implemented in a controlled, non-haphazard manner while maintaining ease of implementation through a standardized template.
Solution Approach 2:
The patent changes the structural parameters of the PPDU by introducing a new field (VS-SIG) with specific subfields rather than modifying existing reserved bits. The language identification subfield parameter enables receiving stations to determine how to process the vendor-specific data, adding a layer of control and robustness. This parameter change approach ensures that vendor-specific features are implemented with proper identification and handling mechanisms, improving reliability while maintaining implementation ease through standardized field definitions.
3Reliability
If a standardized vendor-specific signal field is introduced in the PPDU, then network interoperability and stability are maintained, but the device complexity and PPDU structure become more complex
Solution Approach 1:
The VS-SIG field is designed with multi-functionality to justify its addition to the PPDU structure. The field can be present or absent depending on whether vendor-specific features are needed, making it universally applicable across different scenarios. When present, it contains standardized subfields (vendor-specific data and language identification) that can accommodate various vendor implementations without requiring different structural approaches. This universal design maintains reliability by providing a consistent mechanism for vendor-specific features while managing complexity through optional presence and standardized internal structure.
Solution Approach 2:
The patent implements partial action by making the VS-SIG field optional rather than mandatory in all PPDUs. Stations can choose to process or ignore the VS-SIG based on their capabilities and the presence indicator. The language identification subfield enables partial processing where third-party stations can skip vendor-specific portions while vendor-aware stations process them fully. This partial action approach maintains network interoperability without requiring all stations to handle the full complexity of vendor-specific features, effectively managing device complexity while preserving reliability.
Data Source
AI summary
A format for a Physical layer Protocol Data Unit (PPDU) that can be transmitted over a network is disclosed. The PPDU includes a field having one or more bits identifying whether a vendor-specific signal field (VS-SIG) is present in the PPDU. When present, the VS-SIG includes one or more bits identifying a vendor-specific language in which vendor-specific data is presented. The VS-SIG also includes one or more bits representing the vendor-specific data in the vendor-specific language.