Important The Native 802.11 Wireless LAN interface is deprecated in Windows 10 and later. Please use the WLAN Device Driver Interface (WDI) instead. For more information about WDI, see WLAN Universal Windows driver model.
When queried, the OID_DOT11_EHCC_NUMBER_OF_CHANNELS_FAMILY_INDEX object identifier (OID) requests that the miniport driver return the value of the IEEE 802.11d dot11EHCCNumberOfChannelsFamilyIndex management information base (MIB) object for the current PHY type on the 802.11 station.
This MIB object specifies the maximum value of the family index in the hyperbolic congruence codes (HCC) or extended hyperbolic congruence codes (EHCC) algorithms. A family index is an index within the code families generated by these algorithms. The frequency-hopping spread spectrum (FHSS) PHY generates its hopping patterns through these algorithms.
For more information about the HCC/EHCC algorithms, refer to Clause 126.96.36.199 of the IEEE 802.11d-2001 standard.
Note Support for OID_DOT11_EHCC_NUMBER_OF_CHANNELS_FAMILY_INDEX is mandatory if the NIC supports the dot11_phy_type_fhss PHY type and more than one regulatory domain. For more information about how the miniport driver specifies its list of supported PHY types, see OID_DOT11_SUPPORTED_PHY_TYPES.
The data type for OID_DOT11_EHCC_CAPABILITY_ENABLED is a ULONG value.
The value of the dot11EHCCNumberOfChannelsFamilyIndex MIB object depends on the value of the IEEE 802.11d dot11EHCCPrimeRadix MIB object and must be from ( dot11EHCCPrimeRadix- 1) through ( dot11EHCCPrimeRadix- 3).
For more information about the dot11EHCCPrimeRadix MIB object, see OID_DOT11_EHCC_PRIME_RADIX.
When queried by OID_DOT11_EHCC_NUMBER_OF_CHANNELS_FAMILY_INDEX, the miniport driver fails the request under the following conditions:
The dot11EHCCNumberOfChannelsFamilyIndex MIB object is valid for only the FHSS PHY type. If the current PHY type is not set to dot11_phy_type_fhss, the miniport driver must fail the request by returning NDIS_STATUS_INVALID_DATA from its MiniportOidRequest function.
If the IEEE 802.11d dot11MultiDomainCapabilityImplemented MIB object is FALSE, the miniport driver must fail the request by returning NDIS_STATUS_INVALID_DATA from its MiniportOidRequest function.
For more information about the dot11MultiDomainCapabilityImplemented MIB object, see OID_DOT11_MULTI_DOMAIN_CAPABILITY_IMPLEMENTED.
If the IEEE 802.11d dot11MultiDomainCapabilityEnabled MIB object is FALSE, the miniport driver must fail the request by returning NDIS_STATUS_INVALID_DATA from its MiniportOidRequest function.
For more information about the dot11MultiDomainCapabilityEnabled MIB object, see OID_DOT11_MULTI_DOMAIN_CAPABILITY_ENABLED.
If the miniport driver is operating in Extensible Station (ExtSTA) mode, the current PHY type is determined through the ExtSTA msDot11CurrentPhyID MIB object. This MIB object specifies the index of the current PHY type within the 802.11 station's list of supported PHY types. For more information about msDot11CurrentPhyID, see OID_DOT11_CURRENT_PHY_ID.
Note A Native 802.11 miniport driver that is designed to run on the Windows Vista or Windows Server 2008 operating systems must always reset this 802.11 MIB OID to its default value. This is the case regardless of the value of the bSetDefaultMIB member of the DOT11_RESET_REQUEST structure. This requirement applies to a miniport driver that, in a call to the NdisMSetMiniportAttributes function, sets MiniportAttributes -> Native_802_11_Attributes -> Header -> Revision to NDIS_MINIPORT_ADAPTER_802_11_ATTRIBUTES_REVISION_1.
Available in Windows Vista and later versions of the Windows operating systems.
|Windot11.h (include Ndis.h)|