OID_WWAN_CONNECT activates or deactivates a particular packet context and reads the activation state of a context.
Miniport drivers must process set and query requests asynchronously, initially returning NDIS_STATUS_INDICATION_REQUIRED to the original request, and later sending an NDIS_STATUS_WWAN_CONTEXT_STATE status notification containing an NDIS_WWAN_CONTEXT_STATE structure that indicates the Packet Data Protocol (PDP) context state of the MB device regardless of completing set or query requests.
Callers requesting to set the Packet Data Protocol (PDP) context state of the MB device provide an NDIS_WWAN_SET_CONTEXT_STATE structure to the miniport driver with the appropriate information.
For more information about using this OID, see WWAN Packet Context Management.
This object activates or deactivates a particular packet context and reads the activation state of a context. The miniport driver must send appropriate event notifications whenever the activation state changes.
This object is called only if the miniport driver is in a register state of WwanRegisterStateHome, WwanRegisterStatePartner, or WwanRegisterStateRoaming. When packet service is active, the device must also be in an attach state of WwanPacketServiceStateAttached.
Both set and query operations are supported for this object.
Processing of a set request requires network access but not SIM access.
Processing of a query request does not require access to network or the SIM.
The data structure for this OID is NDIS_WWAN_SET_CONTEXT_STATE. The miniport driver issues a status indication of NDIS_STATUS_WWAN_CONTEXT_STATE for both set and query requests.
In this version of the driver model, the miniport driver attempts context activation only as instructed by the MB Service. (Miniport drivers may activate a context initiated by the network in later versions.) Miniport drivers must not automatically activate a context even after losing registration or a signal. If the access string is not provided in the activation request, a miniport driver should not attempt to provide a default string. Instead, it must proceed with activating the context with a blank access string.
On the other hand, the miniport driver may deactivate a context as instructed by the MB service. This may occur when network connectivity has been lost for a period that exceeds the threshold of temporary loss of signal, or as part of a graceful shutdown or state cleanup.
Since only one activated context is supported in this version, activating or deactivating a particular context amounts to setting up or tearing down the layer-2 MB connection.
On set requests, the MB service furnishes both ConnectionId and ActivationCommand parameters in the WWAN_CONTEXT_STATE data structure. It instructs the miniport driver to activate or deactivate a packet context identified by ConnectionId, based on the ActivationCommand parameter value WwanActivationCommandActivate or WwanActivationCommandDeactivate.
If the service or subscription requires activation, the miniport driver should return error code WWAN_STATUS_SERVICE_NOT_ACTIVATED. The PDP-activation may not happen until the service or subscription is activated. All the emergency services might be available subject to the support from the device and the operator. The operating system might call the OID_WWAN_SERVICE_ACTIVATION in response to this error code.
If the miniport driver receives a context activation request while another packet context is currently activated, it returns error code WWAN_STATUS_MAX_ACTIVATED_CONTEXTS.
If the miniport driver receives a context deactivation request but the context identified by ConnectionId is not currently activated, it returns error code WWAN_STATUS_CONTEXT_NOT_ACTIVATED.
The miniport driver uses the following logic to determine the validity of AccessString, UserName, and Password settings from a set request:
If ActivationCommand is WwanActivationCommandDeactivate, the miniport driver should ignore the settings of these three parameters. The rest of the cases only consider the case when ActivationCommand is WwanActivationCommandActivate.
Context activation persists across user logon and logoff. It is not per logon user.
On query requests, the MB Service uses this object to find out the activation state.
For response to query requests, miniport driver sends the NDIS_STATUS_WWAN_CONTEXT_STATE notification.
In rare, but specific circumstances, the MB Service on Windows 7 may attempt to auto-connect before connectivity to the Internet has been determined for pre-existing connections or during a momentary disruption in Internet connectivity of pre-existing connections. This could result in simultaneous MB and WLAN/Ethernet connections. For example, this can occur during system boot when MB and other connections are attempted simultaneously and the Network List Manager service is still attempting to determine the Internet connectivity of other connections using active and passive methods. It could also occur due to temporary outages in network infrastructure like a corporate proxy server or an ISP network. Thus, the MB Service may attempt to auto-connect to the internet regardless of whether the "Auto-connect only if no alternate Internet connection is available" option is selected.
|Available in Windows 7 and later versions of Windows.|