Patent Application
20050091357
This invention generally relates to the area of computer systems. More particularly, the present invention concerns methods for selecting and determining a configuration for network interfaces within computing devices, and even more particularly in computing devices supporting multiple network interfaces associated with multiple differing networking media.
Wireless networking has opened up a variety of doors to network connectivity. Today, through a combination of networking software and hardware, users are able to access network resources from virtually any location. In fact, in many instances users are able to select from a variety of communication media at any point in time. A communication medium, as used herein, refers to the physical as well as logical (protocol) means by which a user's computer communicates over a network. Examples of communication media include: cellular wireless wide area networks, personal area networks (e.g., Bluetooth), wireless local area networks (e.g., 802.11 (a/b/g)), wired local area networks, and wired wide area networks. Simultaneous availability of multiple communication media arises, for example, within an office environment that supports wireless local area network, wired local area network, wireless wide area network, and wired wide area network connectivity.
The presence of multiple networks potentially reachable via a variety of technologies (e.g., wireless local area networks, wireless wide area networks, hardwired local and wide area networks, personal computer area networks, etc.) introduces a need for network selection capabilities on a network-connectable computing device. In known computing systems, in particular computer systems executing WINDOWS XP, automated network selection is currently based on an order of identified networks in a preference list for a particular communications media—wireless LAN. In the preference list-based automated selection approach, for each network, the sole question when considering a current list entry is, “Can the computing device currently connect to the identified network?” If the answer is yes, then a connection is established. If the answer is no, then the next entry within the preference list is used (until a network connection is established). However, the preference list approach provides a somewhat limited degree of flexibility in configuring a computing device to automatically connect to a network.
The present invention comprises a framework and method for selecting a network and interface based upon selection rules and network interface capabilities information spanning multiple communication media. The framework includes a rules data store for maintaining network selection criteria. The criteria can take on a variety forms and support selection across potentially multiple media.
A media specific module interface facilitates acquiring network interface information associated with available network interfaces. The accumulated information potentially spans multiple communication media associated with a set of networks to which the computing system is capable of connecting via a set of network interfaces.
The network and interface selection framework also includes network selection logic. The network selection logic is applied to the accumulated information to designate one of the set of networks. Thus, the framework enables network and interface selection spanning multiple media.
The present invention is also directed to a method and computer-readable media for carrying out the functionality embodied in the above-summarized network and interface selection framework spanning multiple media types.
While the appended claims set forth the features of the present invention with particularity, the invention, together with its objects and advantages, may be best understood from the following detailed description taken in conjunction with the accompanying drawings of which:
The illustrative network and interface selection architecture disclosed herein facilitates highly flexible automated network and interface selection decision-making in a multiple communication media environment. The network and interface selection architecture supports decision-making by a programmable network and interface selection rules engine. Furthermore, the criteria applied by the programmable rules engine to a particular network interface associated with a particular communication media is potentially based upon capability/policy/status/network resource information associated with other network interfaces utilizing alternative communication media.
By way of example, the rules engine selects a particular network interface and network from a set of network interfaces and networks associated with media specific modules encompassing multiple communication media, based on a set of selection rules including: network preference order, resources available on particular networks, speed of the connections to the networks via the particular media, etc. In an exemplary embodiment, the rules applied by the rules engine are potentially specified by a variety of sources including users, network administrators (group policies), and network service providers. The rules are applied to network interface status/capabilities information provided by media specific modules associated with a variety of communications media (e.g., wireless LAN, wireless WAN, wireless PAN, wired LAN, wired WAN, etc.).
The rules engine facilitates universal network selections spanning multiple media supported by a set of network interfaces on the computing device. In the exemplary embodiment, the rules engine receives status/capabilities information regarding each of a set of network interfaces associated with potentially multiple communication media. The rules engine executes network and interface selection decision-making according to the received information and network and interface selection rules spanning potentially multiple media. Based upon the network/interface selection results rendered during the decision-making, the rules engine initiates configuring a selected network interface by, for example, issuing configuration instructions to media specific modules associated with particular ones of the network interfaces affected by the network and interface selection results. The media specific modules in turn issue instructions to drivers associated with the affected network interfaces.
The invention may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The invention is potentially incorporated within network nodes operating in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules are generally located in both local and remote computer storage media including memory storage devices.
With continued reference to
Computer 110 typically includes a variety of computer readable media. Computer readable media can be any available media that can be accessed by computer 110 and includes both volatile and nonvolatile media, removable and non-removable media. By way of example, and not limitation, computer readable media may comprise computer storage media and communication media. Computer storage media includes both volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can accessed by computer 110. Communication media typically embodies computer readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media. The term “modulated data signal” means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. By way of example, and not limitation, communication media includes wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media such as wireless PAN, wireless LAN and wireless WAN media. Combinations of the any of the above should also be included within the scope of computer readable media.
The system memory 130 includes computer storage media in the form of volatile and/or nonvolatile memory such as read only memory (ROM) 131 and random access memory (RAM) 132. A basic input/output system 133 (BIOS), containing the basic routines that help to transfer information between elements within computer 110, such as during start-up, is typically stored in ROM 131. RAM 132 typically contains data and/or program modules that are immediately accessible to and/or presently being operated on by processing unit 120. By way of example, and not limitation,
The computer 110 may also include other removable/non-removable, volatile/nonvolatile computer storage media. By way of example only,
The drives and their associated computer storage media discussed above and illustrated in
The computer 110 may operate in a networked environment using logical connections to one or more remote computers, such as a remote computer 180. The remote computer 180 may be a personal computer, a server, a router, a network PC, a peer device or other common network node, and typically includes many or all of the elements described above relative to the computer 110, although only a memory storage device 181 has been illustrated in
When used in a LAN networking environment, the computer 110 is connected to the LAN 171 through one or more wired/wireless network interfaces 170. Furthermore, the set of one or more wired/wireless network interfaces 170 support communications over the WAN 173, such as the Internet. While not shown in
The present invention is potentially incorporated into mobile and non-mobile computing devices/machines used in a variety of dynamic networking environments. In such environments, a preferred manner in which to communicate potentially changes as the set of available media changes, the quality of service on particular media changes, and/or the workload on various communication media changes. Turning to
The wireless transceiver 204 (also referred to as a wireless access point, or WAP), provides access to a variety of resources on the LAN 206. For example, the wireless transceiver 204 provides access by the notebook computer 200 to directories/files maintained on a file server 208. The LAN 206 also contains a gateway/firewall/modem 210 providing access by users of the LAN 206, including the user of the notebook computer 200, to the Internet 212. The gateway/firewall/modem 210 also provides access by users of the Internet 212 to the resources on the LAN 206.
The user of the notebook computer 200, as a result of the multiple supported network media, is able to access the Internet 212 and the file server 208 (through the Internet 212) via multiple communication media. For example, utilizing a WWAN network interface, the notebook computer 200 is able to access the Internet 212 via a cellular network including the cellular transmission tower 202. Alternatively, the notebook computer 200 accesses resources on the LAN 206 via the wireless transceiver 204. The LAN 206 in the illustrative example is assumed to include network access and proxy servers that enable a properly authenticated user of the notebook computer 200 to access resources of the Internet 212 and the LAN 206 via either of the two illustratively depicted wireless network media. The capability of the notebook computer to access a same resource via multiple media introduces the potential for selection of a particular one of the wireless network media based upon current conditions, needs, preferences, etc. of the user of the notebook computer 200. For example, other users of the network (e.g., PC 214 connected via wireless transceiver 204 and hardwired PCs 216) compete for limited network bandwidth and/or degrade quality of communications via a particular one of multiple network media. Furthermore, the PC 214, due to its use of wireless user interface devices (a mouse and keyboard), may create signal interference that degrades other wireless communications. In such instances, a relatively static preference list may not select the best connection available for meeting the particular needs of the notebook 200's current user under the current networking environment conditions.
A rules/roaming (network and interface selection) engine, incorporated within the notebook computer 200 embodying the present invention, applies criteria to information pertaining to multiple supported network media interfaces to select one or more of the notebook computer 200's set of network interfaces and associated networks to carry out current networking needs of the notebook computer 200. The roaming engine supports automated network and interface selection decision-making for each of its multiple network interfaces based upon status/capabilities information supplied by multiple network interfaces. The roaming engine is capable of taking into account information relating to the current status/capabilities of other network/media combinations when selecting a currently preferred network and interface combination with which to establish a connection. In addition to a preference list, the roaming engine can base its network interface/network selection decisions upon: availability of particular resources, network speed (maximum/actual), day/time as well as any other desired factor that can be obtained by the roaming engine. Thus, the scope of information and breadth of factors (each encompassing potentially multiple media) that determine the notebook computer 200's multiple network interface configuration is significantly enhanced in comparison to preference lists that merely descend a list of network interfaces for a single medium (e.g., WLAN), ordered by preference, until an available network interface for establishing a desired connection is identified.
Having described an exemplary wireless networking environment wherein the present invention is preferably incorporated, attention is directed to
Beginning at the physical network interface level, in the illustrative architecture, a set of N media specific drivers 302 of various media types (e.g., Bluetooth, WWAN, WLAN—e.g., 802.11a/b/g, etc.) are associated with a set of N currently present network interface cards (NICs) installed on the computer 200. In the illustrative example, each of the media specific drivers 302 communicates with a corresponding NIC. Such communications include, among other things, status/capabilities information provided by the NICs. Such status/capabilities information is obtained, for example, by periodic scanning performed by the NICs upon request by the drivers 302. Upon request, status/capabilities information gathered by the N media specific drivers 302 is passed to the rules engine 300. The rules engine 300, as an aggregator/repository of all the status/capabilities information for all the supported NICs, stores the received status/capabilities information provided by the N media specific drivers 302 within a dynamic rules data store 304. In addition to scanning commands, the NICs also receive configuration commands from the drivers 302.
It is noted that, in an embodiment of the invention, the aforementioned network interface status/capabilities information and notifications are accessible by applications, provisioning services 314 (e.g., a wireless ISP), group-policy services 312, and a user interface 310 via a common remote procedure call API 303. By way of example, the common RPC API 303 includes callable methods/operations/functions for querying and changing, via the user interface 310 or group policy services 312: preference lists, visible lists, media configurations, device states, user authentication data, and network configuration. In an embodiment of the invention, the provisioning services 314 are limited to creating and updating network configurations that are passed down to the rules engine 300, and creating user authentication data through calls to the common RPC API 303. The above-described functions are described herein below with reference to
The rules engine 300 accesses network and interface selection rules, potentially spanning multiple communication media, from the dynamic rules data store 304. The network and interface selection rules stored within the rules data store 304 can, as shown in
The network and interface selection rules specify guidelines for selecting, for connection, a network and interface that utilizes a particular medium for data communication. Users and network administrators, for example, specify network and interface selection rules based upon one or more of the following factors/parameters:
The rules engine 300 applies the set of selection rules to the accumulated status/capabilities information, associated with potentially multiple media, to make network and interface selection decisions for the N network interfaces. After making a selection regarding a particular one of the N network interface cards and a network to which the interface should connect, the rules engine 300 submits configuration instructions to a particular one of the N media specific drivers 302 that corresponds to the particular network interface. The media specific driver thereafter passes corresponding configuration instructions to the associated one of the N NICs.
In an embodiment of the invention, a set of media specific modules 320 support automatic network and interface selection relating to particular media types. In the illustrative example, the set of media specific modules 320 include: LAN module, a WLAN module, a WWAN module, and a personal area network (e.g., Bluetooth) module. The media specific modules 320 request capabilities/status information from the media specific drivers on behalf of the rules engine 300 and invoke scanning of network interfaces by associated media specific drivers of a supported media type. Upon request, the media specific modules pass the resulting acquired network information (e.g., presence, capabilities, status, etc.) to the rules engine 300.
After making a network/interface selection based upon the current set of rules and information, the rules engine passes network interface configuration commands to an appropriate one (or ones) of the media specific modules 320 to connect to a particular network or networks. In response to configuration instructions received from the rules engine 300, the media specific modules 320 initiate changes to connections associated with identified network interfaces via calls to associated media specific drivers. In the exemplary embodiment, each one of the media specific modules 320 incorporates a state machine for carrying out the above-described functionality. An exemplary set of states for the state machine are described herein below with reference to
The media specific modules 320 are associated with two interfaces. The media specific modules 320 communicate with the rules engine via a generalized interface incorporated into a media specific normalization module 322. The normalization module 322, a layer that sits between the rules engine 300 and the media specific modules 320, facilitates standardizing communications between the rules engine 300 and media specific modules 320 of many types. The normalization module 322 facilitates: providing network driver capabilities/status information from the media specific modules 320 to the rules engine 300, and (2) specifying, by the rules engine 300, network interface configuration commands to the media specific drivers 302 via the media specific modules 320. Furthermore, the user-mode media specific modules 320 communicate with the media specific drivers 302, for example, according to (kernel mode) network driver interface specification (NDIS) 340. While the illustrative embodiment provides a media specific module for a particular medium type or class of media types, it is contemplated that alternative embodiments of the invention include composite media specific modules that support multiple, unrelated media types (e.g., a WWAN/WLAN media specific module). Furthermore, while the normalization module 322 is shown as a separate entity from both the rules engine 300 and the media specific modules 320, in alternative embodiments of the invention the functionality of the normalization module is incorporated into either the rules engine 300 or the media specific modules 320.
The set of media specific modules 320 is extensible and the individual modules are loaded and unloaded as needed to accommodate installed network interfaces/drivers. In an embodiment of the invention, the rules engine 300 registers with a notification service provided by a data link layer (OSI layer two) module 324 that monitors installation/removal of devices from a computing device. In a particular embodiment such notifications are carried out through a callback routine registered by the rules engine 300 with the notification service of the data link layer module 324. Thereafter, upon receiving a notification from the notification service that a new network interface/device has been installed, a determination is made by the rules engine 300 whether to load a media specific module to handle a media type of the new network interface (e.g., the network interface is the first for the particular media type). If needed, the appropriate media specific module is loaded by the data link layer module 324 upon request by the rules engine 300, and a reference to a set of function pointers (e.g., an interface table) is provided to the rules engine 300 to facilitate calling normalization module 322 functionality associated with the newly installed media specific module. Thereafter, the rules engine 300 acquires a handle for referencing the media specific module to initiate configuration operations (e.g., scan, connect, disconnect, etc.) on a media specific driver associated with the new network interface. Conversely, upon receiving notification that a network interface is removed, the handles opened on the device are disconnected/closed. If all sessions and handles on the media specific module, which can support multiple interfaces, have been closed, then the number of network interfaces is determined. If no network interfaces remain, then an unload test is carried out (potentially delaying the removal for a period of time) prior to initiating unloading the media specific module.
Loading/unloading media specific modules can be managed in a variety of ways by a variety of management entities. In an embodiment of the invention, the loading and unloading of individual ones of the media specific modules 320 is performed by the data link layer services module 324 that is responsible for loading and managing the status of both the media specific modules 320 as well as the rules engine 300. Extensibility is supported through registration of additional media specific modules supporting particular identified media-types. However, such loading and unloading of program modules can occur in any of a variety of ways, by a variety of entities in accordance with various embodiments of the invention.
In summary, the automatic configuration architecture described herein above with reference to
Turning to
The set of methods exposed by the rules engine 300 to applications includes a set of methods for accessing/changing a list of available networks. A QueryVisibleList method 406 API enables the caller to request the rules engine 300 to provide a list of available devices/interfaces and their associated networks. An optional input GUID parameter, if specified, results in the query being executed only for that GUID's device, otherwise the call will be executed across all devices across all loaded media specific modules. An UpdateVisibleList method 408 causes a forced scan by the rules engine 300 to refresh the Visible list on either all devices, or if specified a particular device, and the rules engine 300 returns the resulting list of available networks.
The set of methods exposed by the rules engine 300 to applications includes a set of methods for accessing/changing a list of preferred networks. A QueryPreferredList method 410 queries the rules engine 300 for the list of preferred networks. If a GUID or Media Type are specified (by flags or setting values for those fields), then the returned list result is filtered for that GUID and/or Media Type, otherwise a global list will be returned. An AddToPreferredList method 412 is called to add an entry to the preferred list. The AddToPreferredList method 412 potentially fails if the preferred list has been modified from its last state by another caller. A RemoveFromPreferredList method 414 is called to remove an entry from the preferred list. This potentially fails if the preferred list has been modified from its last state by another caller.
A OneTimeConnect method 416 implements a one time connect functionality. In other words, a temporary state is established within the rules engine 300 for a specified entry. The connection is not persisted on any preferred list after the connection is completed.
A set of methods provide access to a current configuration for communication media. A QueryMediaConfiguration method 418 invokes the rules engine 300 to obtain and provide all parameters relating to a current media specific configuration. A SetMediaConfiguration method 420 invokes the rules engine 300 to initiate setting a media specific configuration.
A set of methods provide access to a device-specific configuration. A QueryDeviceState method 422 returns a set of parameters relating to a specified device-specific (e.g., network interface card) configuration. A SetDeviceState method 424 sets parameters associated with a particular device-specific configuration.
A set of methods provide access to authentication data associated with a particular user. A QueryUserAuthData method 426 returns authentication information for a user identified by a specified user authentication token. A SetUserAuthData method 428 sets authentication data corresponding to a specified user authentication token.
A set of methods provide access to authentication data associated with a particular network. A QueryNetworkAuthData method 430 returns network-specific authentication information for a network identified by a specified network authentication token and a provided user handle. A SetNetworkAuthData method 432 sets authentication data corresponding to a specified user authentication token.
The following three methods are supported by the common RPC API 303 of the rules engine for the provisioning services 214. A CreateNetworkConfiguration method 434 is similar to the above-described SetNetworkAuthData method 432; however, a network configuration is supplied in XML format via an input parameter. An UpdateNetworkConfiguration method 436 is similar to the CreateNetworkConfiguration method 434 except that a pre-existing configuration is assumed to exist for the identified network. A CreateUserAuthData method 438 is similar to the SetUserAuthData method 428 except the user data is supplied in a passed parameter in XML format.
Turning to
An Open method 500 creates a context handle for the rules engine 300 for a particular identified device/interface. A Close method 502 receives the handle previously created by the Open method 500 and closes the handle. A Close method 502 aborts all pending requests and frees all associated resources in the rules engine 300 associated with the handle previously created to service requests by the rules engine for the particular identified device.
An Event Listener method 504 establishes a callback (notification) reference for the rules engine 300 to receive identified notifications, from the normalization module 322. The Event Listener method 504 receives as input: an event notification code that identifies some event for which the rules engine desires notification, a pointer to the interface source of a notification, a pointer to the data of the notification, and user/context information.
The set of methods exposed by the normalization module 320 to the rules engine 300 includes a QueryVisibleList method 506 API that enables the rules engine 300 to request enumeration of a list of available networks for each device, media, or all devices—as specified by an input GUID parameter. Similarly, a QueryPreferredList method 508 facilitates querying, by the rules engine 300, a list of preferred networks. If a GUID or Media Type are specified (by flags or setting values for those fields), then the returned list result is filtered for that GUID and/or Media Type, otherwise a global list will be returned.
A set of methods provide access to the capabilities and current status of installed devices/interfaces. A GetDeviceCaps method 512 is called by the rules engine 300 to initiate obtaining device capabilities for an interface specified by the handle returned during a previous call to the Open method 500. Examples of such capabilities are described herein below. In addition, the capabilities include device type-specific definitions for the interfaces.
A set of AsyncGetxxx methods 514 and a set of AsynchSetxxx methods 516 facilitate obtaining and setting a variety of device-specific state/status parameters. The AsyncGetxxx methods 514 pass a device/interface handle that was provided for a device in response to the Open method 500. The AsyncGetxxx methods 514 also include an phAsync input/output parameter whereby the rules engine 300 passes in a pointer to a user context value for asynchronous notifications. The output returned via the phAsync parameter is a pointer to an asynchronous notification handle. The handle is subsequently used to access the retrieved information. Examples of the types of Getxxx methods 514 include: online/offline status, signal state, visible providers/networks, preferred providers, ready state, registration state, etc.
The AsynchSetxxx methods 516 pass a device/interface handle, a pointer to data to be provided for performing the particular set functionality, and a pointer to a user context handle for a returned notification. Upon completion, the pointer references a handle for the request. The pointer to the user context value/output handle is used as a notification mechanism to the rules engine 300 to signal completion or failure of the requested set function. The types of AsynchSetxxx methods 516 include for example instructions affecting the online/offline and connection status of the specified device/interface.
It is further noted that in embodiments of the invention a QueryDeviceState method 518 and a SetDeviceState method 520, generalized methods for determining the state of an interface and setting the state of an interface (corresponding to the QueryDeviceState method 422 and SetDeviceState method 424, respectively) are also supported in the normalization module 322 or any other suitable interface interposed between the rules engine 300 and the media specific modules 320.
The interface supported by the normalization module 322 also includes a SetUserAuthData method 522 and a SetNetworkAuthData method 524 corresponding in function to the SetUserAuthData method 428 and the SetNetworkAuthData method 432.
The rules engine 300, in carrying out a network interface configuration selection, submits instructions to establish/break connections via a connect method 526 and a disconnect method 528. The connect method 526 receives, by way of example, a network name (e.g., SSID for WLAN or Provider and APN for WWAN), logon/authentication information, a Pin (for WWAN), etc.
It is noted that, having described an exemplary set of interfaces incorporated into an illustrative embodiment of the invention, alternative embodiments of the invention are contemplated wherein the interfaces include differing call sets for facilitating acquiring information about, and configuring, network interfaces in accordance with the operation of a configuration selection rules engine/system as described, by way of example, herein.
The functionality of the media specific modules can be carried out in a variety of ways. Turning to
Upon receiving a call by the rules engine 300 to configure a particular network interface, a configure connection state 606 of the state machine issues connection configuration instructions to a particular media specific driver corresponding to the network interface identified in the call from the rules engine 300. In the case where a new connection is to be established based upon a request from the rules engine 300, after configuring a network interface at state 606, at connect to network state 608 the media specific module issues instructions to the media specific driver associated with the selected network and interface to establish an operational layer two (data-link) connection between the network interface and the identified network. During a report status state 610 the media specific state machine queries the driver and retrieves current connection status information for the specific network interface card (NIC) and thereafter presents the information to the rules engine 300.
A media specific functionality state 612 is a general state that is programmed according to the particular needs of a media with which a media specific state machine is associated. A manage network switching state 614 handles instances where a first network connection is discontinued and another one takes its place. The content/functionality of the manage network switching state 614 depends largely upon the particular media with which the media specific state machine is associated. In an embodiment of the invention, the switching operation is driven by the rules engine 300 through appropriate connect/disconnect instructions. However, in alternative embodiments the switching operation is driven at lower levels by, for example, the normalization module 322.
Turning briefly to
In an exemplary network interface descriptor, a descriptor handle field 700 stores a unique identification assigned to a particular instance of a descriptor for a network interface. The handle value provides a reference for a particular instance of the combination of status/capability information described herein below for a particular network interface. A network name field 702 stores a value uniquely identifying a network with which the network interface is associated. A resources field 704 generally identifies a network resource accessed via the network interface. The resource field 704 supports rules-based network and interface selection that is based upon a need to access a particular resource such as a corporate LAN, the Internet, etc. A speed field 706 stores a value indicating the maximum data rate currently supported by the particular network interface. A cost field 708 is used to specify a cost associated with using the particular network. The cost field 708, in a simplest case, merely states whether or not the network connection does not incur a cost on a per use basis. Alternatively, cost can be a weighted number used to compare the relative cost associated with particular ones of multiple networks. The cost field 708 supports rules-based decision making where cost is a factor when deciding whether or not to select a particular network interface (over other available network interfaces) for establishing a connection. A domain name field 710 specifies an optional domain name (e.g., Microsoft.com) It is noted that the present invention contemplates a broad spectrum of network interface description formats and thus the above-described example should not be construed as limiting the invention. The above set of descriptor fields is intended to be exemplary. Other potentially used fields include: wireless/wired media type, sub-types of a particular wireless media type (e.g. 802.11a/b/g subtypes for WLAN media), authentication mode, encryption mode, etc.
The following is an example of an accumulated set of network interface descriptors provided to the rules engine 300 by the 802.11 media specific module and the WWAN module. The first three descriptors were provided by the 802.11 module, the last descriptor was provided by the WWAN module. It is noted that a descriptor can specify a set of resources—as shown, by way of example, in the third descriptor identified by the handle “GUID3.”
Having described a general framework for a rules engine based automatic network connection configuration facility embodying the present invention, attention is directed to a table set forth in
In a first scenario set forth in the first row of the table, a rule applied by the rules engine 300 specifies one media over one or more others. Specific scenario examples include specifying: a media type (e.g., WLAN over WWAN), highest data transmission rate, a sub-type of media (e.g., 802.11a over 802.11b). Parameters used in such a rule scenario include: link speed, physical media (wire/wireless), 802.11 type (a/b/g), and cost.
In a second scenario set forth in the second row of the table, a rule applied by the rules engine 300 specifies one network over one or more others. A specific scenario example is specifying a corporate LAN over a public wireless LAN network provided by a wireless internet service provider (WISP). Parameters used in such a rule scenario include network identifier types (e.g., SSID for WLAN and APN for WISP).
In a third scenario set forth in the third row of the table, a rule applied by the rules engine 300 specifies a network preference order based upon current location. Specific scenario examples include specifying: WISP A over WISP B in the United States and WISP B over WISP A when located in Europe. A parameter used in such a rule scenario is location (e.g., home, work, physical location, etc.).
In yet another scenario, provided in the fourth row of the table, a rule applied by the rules engine 300 specifies a preference order comprising logical networks. A specific scenario example includes specifying: a corporate network over WISP A over WISP B. A network provider decides which physical network (WLAN over WWAN) to use based upon XML provisioning. Parameters used in such a rule scenario include: XML provisioning files from a wireless provider, business logic to facilitate dynamic network and interface selection.
In still yet another scenario, preferences are designated based upon a time of day. In instances where certain networks/interfaces are preferred based upon the time of day, a preference can be implemented based upon the currently detected time. For example, if a particular WWAN network provider is preferred on nights and weekends while another provider is preferred during weekdays, then a rule is submitted to, and applied by, the rules engine 300 to render a configuration selection (comprising a combination of a designated network and interface for establishing a connection to the network).
In general, the rules engine accesses rules to decide networks to select associated with potentially multiple media types. The rules are specified through a user interface (e.g., a dialog that accompanies the launch of a particular application or service), a group policy specified by an administrator, or a network provisioning service. These rules can be either one, or a combination, of:
Turning to
As a preliminary step to performing network and interface selection, during step 900 the rules engine 300 receives status/capability information arising from the set of network interfaces across multiple communication media (e.g., a WWAN interface and a WLAN interface). Such information is provided to the rules engine 300, by way of example, in a standardized format by one or more of the media specific modules 320 via the normalization module 322. In the case of a new device arrival, as an initial preliminary step, the rules engine 300 requests the data link layer services module 324 to load an associated media specific module (if not already loaded) and passes back appropriate references to the media specific module.
The status/capability information is accumulated/updated by the rules engine 300 in a variety of ways. In the illustrative embodiment of the invention, the information is acquired by the rules engine 300 by actively querying (polling) the media specific modules 320 in accordance with a scanning algorithm described, by way of example, herein below, as well as receiving unsolicited updates of the status/capabilities of network interfaces from the modules 320 that receive data from media drivers that potentially execute there own versions of a scanning algorithm.
The media specific modules 320, in turn, obtain the network interface status/capability information from the media specific drivers 302 in any suitable manner including either or both push and pull data acquisition procedures. In an embodiment of the invention, wireless media specific modules (either on their own initiative or in response to an asynchronous request from another entity associated with network interface configuration) pull the information from the drivers 302 based upon scanning algorithms that are formulated to take into account a variety of factors including: current power source (e.g., battery), current connection state (wired/wireless), duration of current connection, whether the computing device is presently moving, etc. In a particular wireless scanning arrangement, a scanning engine associated with a wireless media specific module applies a scanning algorithm based upon a set of scanning parameters including historical information maintained within a scanning history table to determine when to commence a next scan cycle for a network interface (or set of network interfaces). When the time for a next scanning period arrives, the media specific module commences scanning the affected network interfaces and stores the scan results.
During step 910 the rules engine 300 accesses a set of rules specified by either one or a combination of rules sources including: the user interface 310, group policy services 312 and the provisioning services 314. In the exemplary embodiment of the invention, the rules engine 300 retrieves the network interface configuration rules from the dynamic rules data store 304. As mentioned previously above, the rules potentially encompass multiple media.
Periodically or upon asynchronous request, at step 920 the rules engine 300 applies the network and interface selection rules, accessed during step 910 and spanning potentially multiple communications media, to the received information to select one or more network interfaces for connecting to one or more particular networks and render configuration instructions for each of the set of network interfaces corresponding to the set of media specific drivers 302 for the selected interface/network combinations. Selecting a particular network for a network interface is needed in situations where a single network interface, such as a wireless LAN transceiver, is capable of accessing multiple networks.
Thereafter at step 930, the rules engine 300 issues configuration commands to the media specific drivers 302 via the media specific modules 320. In the case where a network interface status is unchanged by the results of step 920, there is no need to issue a configuration command. However, in cases where status does change for a particular network interface, the rules engine 300 issues an appropriate configuration instruction to a corresponding media specific module to carry out the change and waits for confirmation by the media specific module that the instruction has been carried out.
Having described an exemplary set of steps for carrying out network interface configuration decision-making across multiple media, it is noted that the above steps are merely exemplary. As those skilled in the art will appreciate in view of the disclosure contained herein, the individual steps are intended to show a progression of data/processing flow that results in set of configuration instructions issued by the rules engine to appropriate ones of the media specific modules 320. Thus, by way of example, the acquisition of network interface information can occur while the rules engine is obtaining the configuration rules that are to be applied to the network interface information.
Turning now to
In summary of a general scanning algorithm implemented by the scanning engine 1000, when the wireless NIC 1020 is not associated with a wireless network, and has not been associated for a significant period, scanning frequency is reduced. Additionally, when the NIC 1020 has been associated with the same access point for a significant period of time with good signal strength, scanning frequency is again reduced because the client application relying upon the wireless connection associated with the NIC is less likely to need to roam/switch to another access point or network. This is especially true if a laptop or other battery powered computing device containing the NIC 1020 is not actively transmitting data packets. Reducing the scanning frequency, in accordance with the above scanning algorithm, conserves laptop battery power as the card can be powered down for longer periods of time between scans.
Referring now to
Having described an exemplary scan procedure, a general scan control scheme is described herein below. Initially, the power mode of the computing device will govern whether to enable the scan timing algorithm. By way of example, the scan timing algorithm is implemented when the computer is on battery power and the NIC is not in continuous access mode.
Scanning is intended to ensure that a computing device can roam successfully. By scanning regularly, the computing device should not be able to move too far from the currently associated access point without associating with another access point (roaming). In accordance with embodiments of the invention store responses to previous scans so that it can adaptively tune the scanning period. The scanning scheme addresses the following cases:
In cases 1 and 2, the interval between scans can be significantly longer than 60 seconds. The scanner timing scheme is implemented to increase the interval between scans to a set maximum based on the history of previous scans. The maximum is implemented as a failsafe device to prevent a complete shut down of the scanning procedure when there is no change in state.
In case 3, if it can be detected that the laptop has moved, then the scanning engine 1000 performs a scan to check for available networks or access points as it is possible that the user can move out of range of the current network. Movement can be detected either in a location awareness module or through, in the case of an 802.11 NIC, analysis of 802.11 statistics, such as received signal strength, retransmission counts and frame error rates.
In accordance with an exemplary scanning scheme, the computing device also detects when there is another NIC providing network access (such as through an Ethernet cable). In this case, all scanning on the wireless NIC is wasted power and the NIC should be disabled. Even if the NIC remains enabled, it should not be requested to perform scanning.
Furthermore, the scanning engine will detect when the NIC is actively sending traffic. This is an improper time to perform a scan and any scheduled scan should be delayed until traffic is sent. If the traffic is sent and the statistics are sufficiently good, a scanning period is skipped. Finally, with regard to an exemplary scanning control scheme, the user might want to request a scan before the next scanning interval arrives. The NIC will perform this scan on demand and adjust the scanning history, period, timer, and frequency accordingly.
It will be appreciated by those skilled in the art that a new and useful method and framework for facilitating/performing automated configuration/selection of network access has been described herein. More particularly, the rules-based network and interface selection architecture described herein facilitates automated selection of a particular mode of network access based upon status information provided by a set of media specific modules associated with multiple communication media. In view of the many possible computing environments to which the principles of this invention may be applied and the flexibility of carrying out automated network access configuration, it should be recognized that the embodiment described herein is meant to be illustrative and should not be taken as limiting the scope of invention. Those skilled in the art to which the present invention applies will appreciate that the illustrative embodiment can be modified in arrangement and detail without departing from the spirit of the invention. Therefore, the invention as described herein contemplates all such embodiments as may come within the scope of the following claims and equivalents thereof.
