WLAN Connected Standby End to End - Roaming
This automated test verifies that Wireless LAN device on systems that support InstantGo delivers reliable connectivity.
The device seamlessly transitions between D0 and D2 states while in CS. The device maintains L2 connectivity while in Connected Standby. If Wi-Fi access point goes out of range, the device roams to another access point. The device wakes up on matching wake patterns only. There are no spurious wakes in CS. The wake packets are delivered without delay or buffering. The RealTimeCommunication app stays connected in Connected Standby for 50 minutes.
Test details
Associated requirements |
Device.Network.WLAN.Base.MeetScanAndConnReq Device.Network.WLAN.CSBBase.MeetScanAndConnReq Device.Network.WLAN.CSBBase.ReliableCSConnectivity |
Platforms |
Windows RT (ARM-based) Windows 8 (x64) Windows 8 (x86) Windows RT 8.1 Windows 8.1 x64 Windows 8.1 x86 |
Expected run time |
~52 minutes |
Categories |
Optional |
Type |
Automated |
Running the test
Before you run the test, complete the test setup as described in the test requirements: Wireless LAN (802.11) Testing Prerequisites.
Troubleshooting
For troubleshooting information, see Troubleshooting Wireless LAN (802.11) Tests.
| Error | Description/Workaround |
|---|---|
Network adapter did not disconnect on time. |
Radio was turned off for Wi-Fi access point to which device was connected, but the miniport did not indicate media disconnect to NDIS. |
Network adapter disconnected too late. |
Radio was turned off for Wi-Fi access point to which device was connected, but the miniport did not indicate media disconnect to NDIS within the expected interval. |
Network adapter disconnected too early. |
Miniport indicated media disconnect to NDIS at an unexpected time. |
Network adapter reconnected too late. |
Radio was turned off for the Wi-Fi access point to which the device was connected, and the radio for another Wi-Fi access point was turned on. The device did not roam to the new access point within the expected interval. |
Network adapter did not reconnect on time. |
Radio was turned off for the Wi-Fi access point to which the device was connected, and the radio for another Wi-Fi access point was turned on. The device disconnected from the first access point, but did not reconnect to the second access point. |
Exited Connected Standby too early. |
The machine left Connected Standby earlier than expected. This can be caused by unexpected user activity, or it might indicate a software bug or driver bug. Make sure you leave the device under test idle while the test runs |
System error occurred for control channel trigger. Make sure NIC is AOAC-capable. |
System failed to plumb wake pattern or protocol offload. Make sure that the NIC complies with NDIS 6.30 requirements. |
OID request for network adapter failed. |
System failed to plumb wake pattern or protocol offload. Make sure that the NIC complies with NDIS 6.30 requirements. |
Surprise network device removal. |
NDIS detected surprise network device removal. This indicates that NIC driver has crashed. Fix driver issue. |
Control channel trigger is detached. |
TCP connection was torn down. Intermittent network connectivity issue or driver issue can cause this problem. Make sure there is good reception. Make sure NIC maintains L2 connectivity in Connected Standby. |
Network adapter disconnected. |
Network adapter is disconnected Make sure that there is good reception. |
Push notification fired too early. |
Application received push notification earlier than it was expected. This is usually caused by TCP RESET from the server side, which indicates L2/L3 connectivity issues. Make sure that the NIC complies with NDIS 6.30 requirements. Make sure that the NIC maintains L2 connectivity in Connected Standby. |
Push notification fired late. |
Application received push notification later than it was expected. This is either a result of buffering or an L2/L3 connectivity issue. Make sure that the NIC complies with NDIS 6.30 requirements. Make sure that the NIC maintains L2 connectivity in Connected Standby. |
Push notification did not fire on time. |
Application did not receive push notification when it was expected. This is either a result of buffering or an L2/L3 connectivity issue. Make sure that the NIC complies with NDIS 6.30 requirements. Make sure that the NIC maintains L2 connectivity in Connected Standby. |
Network adapter did not enter low power state within <number> sec since Connected Standby entry. |
NIC stays in D0 in Connected Standby. This can indicate a software bug. If there is driver bug (NIC does not complete power request), system will bugcheck in 10 minutes. |
Network adapter stayed on <number>% of Connected Standby time. |
NIC stays in D0 in Connected Standby longer than it is expected. This can indicate either a software bug or a device problem. |
Unable to install package [path:<path to appx file>] [err:<error description>]. |
Test could not install modern test application. Make sure that the device under test has the correct date/time. Check error description for more details. |
More information
Parameters
| Parameter | Description |
|---|---|
AP1Password |
The administrator password of the first access point. |
AP1IPAddress |
The IP address of the first access point. |
AP2Password |
The administrator password of the second access point. |
AP2IPAddress |
The IP address of the second access point. |
Related topics