[HE phy]

前导码

5G OFDM分为两部分,前导码Legacy preamble和数据data
在这里插入图片描述
前导码类型:
其中前导码Legacy preamble分为:Legacy Short Traing (L-STF), L_LTF, L-SIG。
如果数据是HT/VHT/HE,则还有其对应格式的前导码。

各类型作用:
L-STF:信号检测、AGC、接收天线选择
L-LTF(Long Training Field):用于频率选择和信道估计
L-SIG:计算分包的持续时间

HE 前导码

he phy描述
在这里插入图片描述
HE-GI:支持三种类型 0.8 μs、1.6 μs 和 3.2 μs
HE-LTF: 支持三种3.2 μs(1x)、6.4 μs(2x)和 12.8 μs(4x)
在这里插入图片描述

空口数据

GI=1.6us ;LTF=2X
在这里插入图片描述
GI=3.2us ;LTF=4X
在这里插入图片描述

问题

对端设备是否支持同样的GI+LTF组合,有些设备不能全部支持
在这里插入图片描述

UL/DL

DL:ap->sta
UL:sta->ap

空口数据

UL/DL=1 :STA->AP
UL/DL=0: ap->sta
在这里插入图片描述

问题

ul/dl方向配置错误会导致对端设备无法正确识别接收

IEEE 802.11 Wireless Management Fixed parameters (12 bytes) Timestamp: 175718698 Beacon Interval: 0.102400 [Seconds] Capabilities Information: 0x1521 Tagged parameters (289 bytes) Tag: SSID parameter set: "CU_PS_5G" Tag Number: SSID parameter set (0) Tag length: 8 SSID: "CU_PS_5G" Tag: Supported Rates 6(B), 9, 12(B), 18, 24(B), 36, 48, 54, [Mbit/sec] Tag Number: Supported Rates (1) Tag length: 8 Supported Rates: 6(B) (0x8c) Supported Rates: 9 (0x12) Supported Rates: 12(B) (0x98) Supported Rates: 18 (0x24) Supported Rates: 24(B) (0xb0) Supported Rates: 36 (0x48) Supported Rates: 48 (0x60) Supported Rates: 54 (0x6c) Tag: DS Parameter set: Current Channel: 36 Tag Number: DS Parameter set (3) Tag length: 1 Current Channel: 36 Tag: Traffic Indication Map (TIM): DTIM 0 of 1 bitmap Tag Number: Traffic Indication Map (TIM) (5) Tag length: 4 DTIM count: 0 DTIM period: 1 Bitmap control: 0x00 Partial Virtual Bitmap: 00 Tag: Power Constraint: 0 Tag Number: Power Constraint (32) Tag length: 1 Local Power Constraint: 0 Tag: TPC Report Transmit Power: 25, Link Margin: 0 Tag Number: TPC Report (35) Tag length: 2 Transmit Power: 25 Link Margin: 0 Tag: RM Enabled Capabilities (5 octets) Tag Number: RM Enabled Capabilities (70) Tag length: 5 RM Capabilities: 0x03 (octet 1) RM Capabilities: 0x02 (octet 2) RM Capabilities: 0x00 (octet 3) RM Capabilities: 0x00 (octet 4) RM Capabilities: 0x00 (octet 5) Tag: Vendor Specific: Microsoft Corp.: WMM/WME: Parameter Element Tag Number: Vendor Specific (221) Tag length: 24 OUI: 00:50:f2 (Microsoft Corp.) Vendor Specific OUI Type: 2 Type: WMM/WME (0x02) WME Subtype: Parameter Element (1) WME Version: 1 WME QoS Info: 0x0c Reserved: 00 Ac Parameters ACI 0 (Best Effort), ACM no, AIFSN 3, ECWmin/max 3/4 (CWmin/max 7/15), TXOP 0 Ac Parameters ACI 1 (Background), ACM no, AIFSN 7, ECWmin/max 4/10 (CWmin/max 15/1023), TXOP 0 Ac Parameters ACI 2 (Video), ACM no, AIFSN 2, ECWmin/max 3/4 (CWmin/max 7/15), TXOP 94 Ac Parameters ACI 3 (Voice), ACM no, AIFSN 2, ECWmin/max 2/3 (CWmin/max 3/7), TXOP 47 Tag: QBSS Load Element 802.11e CCA Version Tag Number: QBSS Load Element (11) Tag length: 5 QBSS Version: 2 Station Count: 1 Channel Utilization: 9 (3%) Available Admission Capacity: 31250 (1000000 us/s) Tag: HT Capabilities (802.11n D1.10) Tag Number: HT Capabilities (802.11n D1.10) (45) Tag length: 26 HT Capabilities Info: 0x09ef A-MPDU Parameters: 0x03 Rx Supported Modulation and Coding Scheme Set: MCS Set HT Extended Capabilities: 0x0000 Transmit Beam Forming (TxBF) Capabilities: 0x00000000 Antenna Selection (ASEL) Capabilities: 0x00 Tag: HT Information (802.11n D1.10) Tag Number: HT Information (802.11n D1.10) (61) Tag length: 22 Primary Channel: 36 HT Information Subset (1 of 3): 0x05 HT Information Subset (2 of 3): 0x0015 HT Information Subset (3 of 3): 0x0000 Rx Supported Modulation and Coding Scheme Set: Basic MCS Set Tag: Extended Capabilities (10 octets) Tag Number: Extended Capabilities (127) Tag length: 10 Extended Capabilities: 0x00 (octet 1) Extended Capabilities: 0x00 (octet 2) Extended Capabilities: 0x08 (octet 3) Extended Capabilities: 0x00 (octet 4) Extended Capabilities: 0x00 (octet 5) Extended Capabilities: 0x00 (octet 6) Extended Capabilities: 0x00 (octet 7) Extended Capabilities: 0x0040 (octets 8 & 9) Extended Capabilities: 0x40 (octet 10) Tag: VHT Capabilities Tag Number: VHT Capabilities (191) Tag length: 12 VHT Capabilities Info: 0x039979f2 .... .... .... .... .... .... .... ..10 = Maximum MPDU Length: 11 454 (0x2) .... .... .... .... .... .... .... 00.. = Supported Channel Width Set: Neither 160MHz nor 80+80 supported (0x0) .... .... .... .... .... .... ...1 .... = Rx LDPC: Supported .... .... .... .... .... .... ..1. .... = Short GI for 80MHz/TVHT_MODE_4C: Supported .... .... .... .... .... .... .1.. .... = Short GI for 160MHz and 80+80MHz: Supported .... .... .... .... .... .... 1... .... = Tx STBC: Supported .... .... .... .... .... .001 .... .... = Rx STBC: 1 Spatial Stream Supported (0x1) .... .... .... .... .... 1... .... .... = SU Beamformer Capable: Supported .... .... .... .... ...1 .... .... .... = SU Beamformee Capable: Supported .... .... .... .... 011. .... .... .... = Beamformee STS Capability: 4 (0x3) .... .... .... .001 .... .... .... .... = Number of Sounding Dimensions: 2 (0x1) .... .... .... 1... .... .... .... .... = MU Beamformer Capable: Supported .... .... ...1 .... .... .... .... .... = MU Beamformee Capable: Supported .... .... ..0. .... .... .... .... .... = TXOP PS: Not supported .... .... .0.. .... .... .... .... .... = +HTC-VHT Capable: Not supported .... ..11 1... .... .... .... .... .... = Max A-MPDU Length Exponent: 1 048 575 (0x7) .... 00.. .... .... .... .... .... .... = VHT Link Adaptation: No Feedback (0x0) ...0 .... .... .... .... .... .... .... = Rx Antenna Pattern Consistency: Not supported ..0. .... .... .... .... .... .... .... = Tx Antenna Pattern Consistency: Not supported 00.. .... .... .... .... .... .... .... = Extended NSS BW Support: 0x0 VHT Supported MCS Set Rx MCS Map: 0xfffa ...0 0001 1100 0010 = Rx Highest Long GI Data Rate (in Mb/s, 0 = subfield not in use): 0x01c2 000. .... .... .... = MaX NSTS Total: 0 Tx MCS Map: 0xfffa ...0 0001 1100 0010 = Tx Highest Long GI Data Rate (in Mb/s, 0 = subfield not in use): 0x01c2 ..1. .... .... .... = VHT Extended NSS BW Capable: Capable 00.. .... .... .... = Reserved: 0x0 Tag: VHT Operation Tag Number: VHT Operation (192) Tag length: 5 VHT Operation Info Basic MCS Map: 0xfffa Ext Tag: HE Capabilities Ext Tag length: 21 (Tag len: 22) Ext Tag Number: HE Capabilities (35) HE MAC Capabilities Information: 0x58940e081805 HE PHY Capabilities Information Supported HE-MCS and NSS Set Ext Tag: HE Operation Ext Tag length: 6 (Tag len: 7) Ext Tag Number: HE Operation (36) HE Operation Parameters: 0x003fe4 BSS Color Information: 0x01 Basic HE-MCS and NSS Set: 0xfffc Ext Tag: Spatial Reuse Parameter Set Ext Tag length: 2 (Tag len: 3) Ext Tag Number: Spatial Reuse Parameter Set (39) SR Control: 0x05 Non-SRG OBSS PD Max Offset: 0 Ext Tag: MU EDCA Parameter Set Ext Tag length: 13 (Tag len: 14) Ext Tag Number: MU EDCA Parameter Set (38) QoS Information (AP): 0x00 MUAC_BE Parameter Record MUAC_BK Parameter Record MUAC_VI Parameter Record MUAC_VO Parameter Record Ext Tag: UORA Parameter Set Ext Tag length: 1 (Tag len: 2) Ext Tag Number: UORA Parameter Set (37) UL OFDMA-based Random Access Parameter SET: 0x2a Ext Tag: NDP Feedback Report Parameter Set Ext Tag length: 1 (Tag len: 2) Ext Tag Number: NDP Feedback Report Parameter Set (41) Resource Request Buffer Threshold Exponent: 8 Tag: Vendor Specific: Huawei Technologies Co.,Ltd Tag Number: Vendor Specific (221) Tag length: 8 OUI: ac:85:3d (Huawei Technologies C Vendor Specific OUI Type: 130 Vendor Specific Data: 8201000000 Tag: Vendor Specific: Huawei Technologies Co.,Ltd Tag Number: Vendor Specific (221) Tag length: 5 OUI: ac:85:3d (Huawei Technologies C Vendor Specific OUI Type: 189 Vendor Specific Data: bd00 Tag: Vendor Specific: Huawei Technologies Co.,Ltd Tag Number: Vendor Specific (221) Tag length: 8 OUI: ac:85:3d (Huawei Technologies C Vendor Specific OUI Type: 32 Vendor Specific Data: 2073220000 Tag: Vendor Specific: Huawei Technologies Co.,Ltd Tag Number: Vendor Specific (221) Tag length: 8 OUI: 00:e0:fc (Huawei Technologies C Vendor Specific OUI Type: 129 Vendor Specific Data: 81f15e0500 Tag: Vendor Specific: Huawei Technologies Co.,Ltd Tag Number: Vendor Specific (221) Tag length: 27 OUI: 00:e0:fc (Huawei Technologies C Vendor Specific OUI Type: 160 Vendor Specific Data: a00000000101030101010100040100020200000b00070100 这是一个Beacon帧的报文信息,分析是否能够添加CSA元素
07-17
### Linux PHY Driver Implementation and Working Principle In the context of network interfaces, a PHY (Physical Layer Device) is responsible for handling low-level communication over physical media such as twisted pair or fiber optics. The PHY driver in Linux serves as an intermediary between higher-layer protocols like Ethernet and the actual hardware. The core functionality of a PHY driver includes initializing the device, configuring it according to system requirements, monitoring its status, and managing power states. In Linux, this interaction occurs through standardized APIs provided by the kernel's networking subsystem[^1]. #### Initialization Process When booting up with Xen support, after displaying information about itself and underlying hardware, control eventually reaches the domain 0 operating environment where standard drivers including those interfacing with network devices are loaded into memory. For non-Xen environments, similar initialization processes apply but without specific mentions related directly here since no direct citation covers that aspect explicitly within given references. For PHY-specific operations during startup: - **Probing**: Detects available PHCs on bus systems. - **Configuration Register Access**: Sets parameters via MDIO interface commands. ```c static int phy_probe(struct platform_device *pdev) { struct phy_device *phydev; /* Allocate new instance */ phydev = devm_phy_create(&pdev->dev); if (!phydev) return -ENOMEM; // Additional setup... } ``` #### Interaction Mechanisms Communication between software layers and the PHY typically happens using Management Data Input/Output (MDIO). This protocol allows reading from/write-to configuration registers inside the PHY chip which controls various aspects ranging from speed settings down to diagnostic features. PCI Express technology further enhances efficiency when dealing with multiple concurrent requests due to implementing split transactions; enabling interleaved command processing across different peripherals connected along shared lanes[^3]: ```c int mdio_read(struct mii_bus *bus, int addr, u8 regnum) { unsigned long timeout = jiffies + HZ / 10; do { // Read operation logic ... if ((readl(bus->base + MII_STATUS_REG) & BUSY_BIT) == 0) break; msleep(1); } while (time_before(jiffies, timeout)); return readl(bus->base + DATA_REG); } ``` #### Rate Adaptation Algorithms Integration Rate adaptation algorithms play crucial roles especially under wireless contexts ensuring optimal throughput based upon varying channel conditions dynamically adjusting transmission rates accordingly. One example mentioned previously involves `OnoeWifiManager`, developed specifically targeting WiFi scenarios though limited applicability exists outside legacy standards lacking HT/VHT/HE capabilities[^2]. --related questions-- 1. How does the MDIO protocol facilitate register access in PHY management? 2. What challenges arise integrating advanced rate adaptation schemes supporting modern Wi-Fi amendments beyond traditional methods? 3. Can you provide examples demonstrating how PCI Express architecture benefits overall performance concerning I/O intensive applications involving numerous peripheral interactions?
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值