When queried, the OID_DOT11_HOP_ALGORITHM object identifier (OID) requests that the miniport driver return the value of the IEEE 802.11d dot11HopAlgorithmAdopted management information base (MIB) object for the current PHY type on the 802.11 station.
The dot11HopAlgorithmAdopted MIB object specifies the type of algorithm that generates the hopping patterns used by the frequency-hopping spread spectrum (FHSS) PHY.
Note Support for OID_DOT11_HOP_ALGORITHM 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_HOP_ALGORITHM is the DOT11_HOP_ALGO_ADOPTED enumeration, which include the following algorithms:
The algorithm generates hopping patterns as defined in Clause 14 of the IEEE 802.11-2012 and IEEE 802.11d-2001 standards.
The algorithm generates hopping patterns through the hop index method as defined in Clause 18.104.22.168 of the IEEE 802.11d-2001 standard.
The 802.11 station must use the random table method to generate hopping patterns if the Flag field of the Hopping Pattern Table information element (IE) was set to one in the last received Beacon or Probe Response frame. Otherwise, the 802.11 station must use the hop index method.
For more information regarding the hop index and random table methods, see Clause 22.214.171.124 of the IEEE 802.11d-2001 standard
The algorithm generates hopping patterns using the hyperbolic congruence codes (HCC) or extended hyperbolic congruence codes (EHCC) methods. For more information about the HCC/EHCC methods, refer to Clause 126.96.36.199 of the IEEE 802.11d-2001 standard.
The miniport driver fails a query of OID_DOT11_HOP_ALGORITHM under the following conditions:
The dot11HopAlgorithmAdopted 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.|