OID_DOT11_WFD_DISCOVER_REQUEST

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 set, the OID_DOT11_WFD_DISCOVER_REQUEST object identifier (OID) requests that the miniport driver perform a device discovery operation and return the list of discovered devices and networks.

The data type for OID_DOT11_WFD_DISCOVER_REQUEST is the DOT11_WFD_DISCOVER_REQUEST structure.

The system may provide the miniport driver additional Information Elements (IEs) that it should insert into the probe request packets for Wi-Fi Direct (WFD) device discovery. If provided, the driver should include these in probe requests sent for WFD devices. If IEs are not provided, the miniport driver must use the default request IEs in the DOT11_WFD_ADDITIONAL_IE structure that was sent with OID_DOT11_WFD_ADDITIONAL_IE.

After the device discovery has started, the miniport must perform the following to complete the OID:

  • If the process started successfully, the OID must be completed with NDIS_STATUS_INDICATION_REQUIRED.

  • The completion of device discovery initiated by OID_DOT11_WFD_DISCOVER_REQUEST must be indicated to the system with a NDIS_STATUS_DOT11_WFD_DISCOVER_COMPLETE status indication.

When the WFD device port performs a device discovery operation, the miniport driver should cache the received beacon and probe response packets. The miniport driver returns the list of the cached beacon and probe response packets in the completion indication and when queried by OID_DOT11_WFD_ENUM_DEVICE_LIST. This list can contain devices discovered in other recent scans.

The miniport driver must not report about any devices that have sent only probe requests and have not sent beacons or probe responses. The DOT11_WFD_DEVICE_ENTRY structure for each discovered peer device should include the IEs from both the beacon and probe response packets.

While device discovery is in progress, the miniport may receive OID_DOT11_WFD_ENUM_DEVICE_LIST requests. It should return a device list that includes the devices found during the ongoing discovery, in addition to devices that have been discovered in other recent scans.

The miniport must handle the situation where a WFD device supports multiple concurrent groups and can respond to probe requests as a WFD device as well as one or more WFD direct Group Owners (GOs). The miniport can use the transmitter address or BSSID from the received packets to distinguish various responses from the same Peer-to-Peer (P2P) device address.

The miniport driver should delete stale entries from its cached device list. The rules for identifying stale entries is determined by miniport. Devices that have not been visible for more than five minutes must not be reported to the system. The miniport driver can also perform internal device discovery operations to add or update its cached device list.

While operating system-requested discovery is in progress, the miniport should not enter the listen state except during the Find phase. That is, the miniport should ignore the listen-state discoverability setting if it is set to a value other than DOT11_WFD_DEVICE_NOT_DISCOVERABLE.

Requirements

Version

Supported starting with Windows 8.

Header

Windot11.h (include Windot11.h)

See also

DOT11_WFD_ADDITIONAL_IE
DOT11_WFD_DEVICE_ENTRY
DOT11_WFD_DISCOVER_REQUEST
NDIS_STATUS_DOT11_WFD_DISCOVER_COMPLETE
OID_DOT11_WFD_ENUM_DEVICE_LIST

 

 

Send comments about this topic to Microsoft

Show: