Win.MBN.CDMA.TestCSConnectivityLongHaul

This test verifies that a Wireless WAN device on systems that support InstantGo delivers reliable connectivity while the system is in Connected Standby. The device seamlessly transitions between D0 and D3 warm states while in Connected Standby. The device maintains L2 connectivity while in Connected Standby. The device wakes up on matching wake patterns only. There are no spurious wakes while in Connected Standby. The wake packets are delivered without delay or buffering. Real Time Communication app stays connected while in Connection Standby for 12 hours.

Test details

Running the test

Before you run the test, complete the test setup as described in the test requirements: Mobile Broadband Testing Prerequisites.

Troubleshooting

For troubleshooting information, see Troubleshooting Device.Network Testing.

If Connected Standby exits too early, ensure that the device under test is left idle for the duration of the test.

If a system error occurs for a control channel trigger, the system could not plumb the wake pattern or protocol offload. Ensure that the network adapter complies with NDIS 6.30 requirements.

If an OID request for a network adapter fails, ensure that the network adapter complies with NDIS 6.30 requirements.

If a surprise network device removal is detected, ensure that the driver does not have an issue.

If the control channel trigger is detached, ensure that there is good reception and that the network adapter maintains L2 connectivity during Connected Standby.

If the network adapter disconnects, ensure that there is good reception.

If a push notification is received too early, ensure that the network adapter complies with NDIS 6.30 requirements and that the network adapter maintains L2 connectivity during Connected Standby.

If a push notification is received too late, ensure that the network adapter complies with NDIS 6.30 requirements and that the network adapter maintains L2 connectivity during Connected Standby.

If a push notification is not received when expected, ensure that the network adapter complies with NDIS 6.30 requirements and that the network adapter maintains L2 connectivity during Connected Standby.

If the network adapter did not enter the low power state within a certain number of seconds during Connected Standby, ensure that the driver is functioning correctly.

If the network adapter stays on a certain percentage of Connected Standby time, ensure that the driver is functioning properly.

If you receive the following error: Unable to install package [path: <path to appx file>] [err:<error description>], ensure that the device under test has the correct date and time. Check the error description for more details.

More information

Parameters

Send comments about this topic to Microsoft