Multi-Static Sensing PPDU Format for Legacy EDMG Compatibility
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Legacy EDMG STAs are unable to decode payload data and understand the Sync field in EDMG multi-static sensing PPDUs, hindering coexistence and backward compatibility with new 802.11bf compliant STAs.
Innovation Solution
Generate an IEEE 802.11 multistatic sensing PPDU with specific settings for the PSDU Length field and other TXVECTOR parameters to allow legacy EDMG STAs to interpret the duration of the Data and Sync fields, ensuring compatibility and coexistence.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a legacy EDMG STA uses standard EDMG PPDU format, then it can maintain backward compatibility, but it cannot decode payload data and understand the Sync field in multi-static sensing PPDUs
Solution Approach 1:
The Sync field is segmented into multiple Sync subfields, each corresponding to a specific STA. This segmentation allows legacy STAs to process only their designated subfield while ignoring others, enabling partial decoding capability without breaking backward compatibility.
Solution Approach 2:
Different parts of the Sync field have different properties: each Sync subfield is tailored to a specific STA with STA-specific synchronization information. This local quality enables legacy STAs to interpret their specific subfield while the overall structure remains compatible with new 802.11bf compliant STAs.
2Reliability
If multi-static sensing PPDU includes Sync field for sensing functionality, then sensing performance is improved, but legacy EDMG STAs cannot interpret the duration and structure
Solution Approach 1:
The Sync field structure serves multiple functions: it provides sensing-specific synchronization information for 802.11bf compliant STAs while simultaneously maintaining compatibility with legacy EDMG STA duration interpretation through the PSDU Length field relationship.
Solution Approach 2:
The PSDU Length field parameter is configured such that its value equals the duration of Data field plus Sync field. This parameter change enables legacy STAs to correctly interpret the total duration without needing to understand the internal Sync field structure, while new STAs can parse the detailed Sync subfields.
3Loss of information
If PSDU Length field is set to include both Data and Sync field durations, then legacy STA can understand total duration, but individual field duration interpretation becomes ambiguous
Solution Approach 1:
The PSDU Length field is pre-configured with the sum of Data and Sync field durations before transmission. This preliminary action allows legacy STAs to calculate the expected total duration without needing to separately interpret each field's duration, simplifying their operation while maintaining accuracy.
Data Source
AI summary
Apparatus, methods and systems for communication and sensing in multi-static sensing may be provided. According to an aspect a method 800 for transmitting a multistatic sensing PPDU may be provided. The method 800 includes generating, by processing electronics in an initiator 801, a multistatic sensing PPDU 804. The multistatic sensing PPDU 804 may be an IEEE 802.11 multistatic sensing PPDU, e.g., PPDU 300. The IEEE 802.11 multistatic sensing PPDU may include a data field, a sync field following the data field, a training field (TRN) following the sync field, and a PSDU Length field included in an EDMG-Header-A of the PPDU. The PSDU Length field may be set by the apparatus to have a value according to particular described equations and specifications.