System and method of dynamically switching between 802.11b client and access point in MS-Windows environment

FIELD OF THE INVENTION

[0001] The present invention relates to local wireless networks based on IEEE 802.11b wireless LAN standards and more particularly to its infrastructure and Ad-Hoc connectivity models.

ART BACKGROUND

[0002] With the advent of the Internet, people have become accustomed to accessing information from remote sources through the Internet. However, the “on-ramp” to the Internet, and the World Wide Web, has been confined to only locations equipped with dial-up, DSL, cable modem or T1 connections. Without a connection to the Internet, a user's notebook computer is virtually useless, as far as being able to reach out is concerned. Although mobile phones had become part of our everyday routine, the once-promising cellular-based Web surfing turned out to be quite a disappointment, in large part due to the slow connection speed and the cost associated therewith. Nevertheless, as more and more computer users become “road worriers,” thanks to progress in notebook computing and cell phone technology, they expect being able to connect to the Internet at just about any place they can turn on their computers—at the airport, in the hotel lobby or even at the nearest Starbucks® Coffee.

[0003] A wireless LAN communications standard, known as the IEEE 802.11(b) WLAN standard, is the industry's answer to their prayers. By using technology based on the 802.11(b) standard, Access Points (“AP”) can be created, where clients within a radius of about 300 ft can gain wireless access to the Internet by using their notebook computer with an 802.11(b) card. Each AP, at the other end, is connected through wired lines to the backbone network.

[0004] As is well known to those in the art, the 802.11(b) Wireless LAN standard defines several Wireless LAN connectivity models, including Infrastructure mode, Ad-Hoc mode, Bridging mode, etc. Currently the most commonly used mode in home/office/school/corporation environment is the Infrastructure mode, which requires an AP, instead of Ad-Hoc operation. The Infrastructure mode, as illustrated in FIG. 1, defines two different wireless nodes. As shown in FIG. 1, one node is AP node A<b>05</b>, which can accept wireless association request and redirect network traffic to backbone network A<b>00</b>. The other node is Wireless Client (“WC”) node A<b>10</b>, A<b>20</b>, A<b>30</b>, which can provide each client system (e.g. laptop, PDA, desktop, etc.) wireless connectivity to AP node A<b>05</b>.

[0005] Usually an AP is an embedded system with wireless components and an Ethernet port. The Ethernet port is further connected to backbone network in order to redirect 802.3 packets to associated WCs. The AP also receives packets from WCs and route them to the Ethernet port. Most conventional AP embedded systems are implemented with a CPU or special-designed ASIC chips, and semiconductor components, such as Flash, RAM, Network Interface Card, etc., to implement IEEE 802.11b AP protocol functions and Ethernet port functions.

[0006] As can be appreciated by those skilled in the art, the cost of setting up an AP system, including the gateway and the AP, is relatively high, especially when the AP set-up is a stand-alone system, dedicated to providing access point functionality only.

[0007] Additionally, such AP implementations have other drawbacks in SOHO (Small Office/Home Office) and school environment, where people share one Internet connection, e.g. V.90 dial-up, cable modem or DSL, and would use the AP as a wireless connectivity hub. FIG. 2 illustrates an exemplary Internet-sharing network topology in such an environment. In this set-up, extra devices, such as IP-sharing (such as Network Address Translation) routers B<b>25</b>, are further required to provide IP-sharing connections to the WCs B<b>40</b>, B<b>45</b> and B<b>50</b>. However, such NAT routers have no place in the simple AP-Infrastructure mode.

[0008] Therefore, both situations, as illustrated by FIG. 1 and FIG. 2, require dedicated up-front investment in systems. For users who prefer flexibility and affordability between the modes, such a dedicated single set-up does not render itself very attractive.

[0009] Therefore, it is desirable to provide an affordable connectivity solution to users for both AP and Internet-sharing.

[0010] It is also desirable to provide the affordable solution with flexibility and simplicity for AP and Internet-sharing.

[0011] It is further desirable to do so by utilizing built-in capability provided in the user's own PC environment.

[0012] Some have attempted to address the above needs. A PC-AP from Zoom® Telephonics, Inc. of Boston, Mass., (www.zoom.com) presents AP software running in Windows environment. Together with IP-sharing software from SyGate Technologies (www.sygate.ca), such as SyGate® Home™ v. 4.2, they provide a solution that is based in Windows. However, since it is a software implementation of AP functions in the host side, the performance of the AP system tends to be compromised as the number of connections from WCs grows.

SUMMARY OF THE INVENTION

[0013] Therefore, it is an object of the present invention to provide flexible connectivity AP or WC modes without the need for stand-alone AP in SOHO/school environment.

[0014] It is also an object of the present invention to be able to utilize the IP-sharing features in Windows to set up an Infrastructure network with minimal user setting.

[0015] The present invention is directed to a configurable application driver, for an 802.11 (b) device such as PC card/PCI wireless AP, that can provide both the WC and AP functions in one module. The application driver is designed to perform as either WC or AP driver, according to current setting. The AP is a firmware-based AP, as is typically provided by chipmakers, so as to avoid performance degradation. The application driver also functions as a regular WC driver to put the device into the WC mode. It can then connect to other APs and act as a client network device.

[0016] When the application driver is switched from WC mode to AP mode, the driver downloads the AP firmware to the 802.11 (b) device and turn the device into an AP device. The system will now receive connection requests from other WCs to facilitate wireless network connections. The driver can also handle the network packets to comply with AP function requirements instead of complying with WC requirements.

[0017] After the wireless AP mode is enabled from the driver, Windows IP-sharing protocol can also be enabled to provide unique IP addresses to all the WCs connecting to this AP.

[0018] If the driver is switched back from AP mode to WC mode, the driver resets the device and restore running firmware function from AP to WC. The driver then changes its internal state accordingly. The system then becomes a wireless client network connection device.

BRIEF DESCRIPTION OF THE DRAWINGS

[0019]FIG. 1 is an exemplary topology of a conventional Wireless LAN infrastructure mode.

[0020]FIG. 2 illustrates an exemplary Internet-sharing network topology in a conventional wired and wireless LAN.

[0021]FIG. 3(<i>a</i>) illustrates an exemplary Internet-sharing topology with external Ethernet/USB modems in accordance with one embodiment of the present invention.

[0022]FIG. 3(<i>b</i>) illustrates an exemplary Internet-sharing topology with external V.90 modems in accordance with one embodiment of the present invention.

[0023]FIG. 3(<i>c</i>) illustrates an exemplary Internet-sharing topology with internal V.90 modems in accordance with one embodiment of the present invention.

[0024]FIG. 4 illustrates a simplified software block diagram in accordance with one embodiment of the present invention.

[0025]FIG. 5 illustrates an exemplary flow diagram of the methodology in accordance with one embodiment of the present invention.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT

[0026] A method and system for dynamically switching between 802.11(b) client and access point in Windows® environment is disclosed. In the following detailed description, numerous specific details are set forth to provide a full understanding of the present invention. It will be obvious, however, to one ordinarily skilled in the art that the present invention may be practiced without some of these specific details. In other instances, well-known structures and techniques have not been shown in detail so as to avoid unnecessarily obscuring the present invention

[0027] The present invention is directed to a Windows®-based application driver for providing Wireless LAN 802.11(b) AP functionality without actual AP hardware. When installed into the host system, e.g. a notebook or desk-top computer running Windows operating system, the driver can dynamically convert a Windows 802.11(b) station into an AP with IP-sharing by facilitating Windows built-in NAT capability (Internet Connection Sharing). The driver can also be used in conjunction with any other available NAT software packages (from SyGate® or WinGate) to provide Internet sharing function, while the host system can still be used as an Internet client. It can further be combined with any bridge-function package to provide dedicated AP functionality.

[0028] Reference is now directed to FIG. 3(<i>a</i>), where an exemplary Internet-sharing topology with external Ethernet/USB modems in accordance with one embodiment of the present invention is shown. The application driver in accordance with one embodiment of the present invention can now reside in notebook computer C<b>30</b>, which is connected to modem C<b>10</b> through Ethernet or USB connection C<b>15</b>. Modem C<b>10</b>, which can be a cable, DSL or satellite modem, is further connected to the Internet C<b>20</b>. Notebook C<b>30</b>, which preferably operates on Windows 2000 operating system with TCP/IP protocol, is installed with an 802.11(b) device, which communicates as an AP with other 802.11(b) devices in wireless clients C<b>40</b>, C<b>45</b>, and C<b>50</b>.

[0029] The application driver in one embodiment of the present invention also works with other Internet connections, such as V.90 modem, an exemplary topology of which is illustrated in FIG. 3(<i>b</i>). Instead of connecting to the Internet C<b>20</b> through a high speed digital modem, a V.90 dial-up modem C<b>12</b> is used to provide the link. V.90 modem C<b>12</b> is connected to notebook computer C<b>30</b> through its UART serial cable C<b>22</b>. Notebook computer C<b>30</b>, which is equipped with an 802.11(b) device and the application driver of one embodiment of the present invention, can now operate as an AP for other wireless clients C<b>40</b>, C<b>45</b> and C<b>50</b>, if the user desires it to be in AP mode.

[0030] In recent years, V.90 modems have become internal within a desk-top computer or a notebook computer. This arrangement is shown in FIG. 3(<i>c</i>), which represents a further reduction of hardware from the exemplary topology of FIG. 3(<i>b</i>). As shown, notebook C<b>30</b>, equipped with an 802.11(b) device, can provide an AP to reach the Internet C<b>20</b>, for its wireless clients W<b>40</b>, W<b>45</b>, and W<b>50</b>.

[0031] Reference is now turned to FIG. 4, where a simplified functional diagram of the application driver in accordance with one embodiment of the present invention is illustrated. Implemented within the application driver, client software components are symbolically shown within Box D<b>01</b>, which functions are typically provided by 802.11(b) chip vendors, such as INTERSIL or ATMEL. As can be appreciated by those skilled in the art, these functional components are needed for a client card to act as a wireless client. Initialization D<b>10</b> is to initialize Windows-related parameter set-up and hardware initialization. Client code D<b>15</b> is to implement 802.11(b) protocol standards for the wireless client. Transmitter and Receiver D<b>20</b> provides a transmitter and receiver handler routine from the host side to a wireless adapter, which for example may be a PCMCIA or PCI card. Interrupt Service Routine D<b>25</b> provides a software routine to handle hardware response event, such as hardware interrupt. User Interface (UI) D<b>30</b> is provided as a Windows graphical user-interface (GUI) program for the user to manipulate lower-level driver and hardware parameters to adapt to different wireless environments.

[0032] The functionality of an AP, which can be dynamically switched on, and downloaded upon selection by the user, is provided in Box D<b>02</b> of the application driver. The shared UI D<b>30</b> allows the user to set itself up as an AP, which upon activation will recognize and allow the user to choose a mode of operation. If a default mode AP is selected, firmware image is dynamically generated for downloading to the 802.11 (b) device, for example the PC card of the user's host computer. Upon completion, the 802.11(b) device, in conjunction with the host computer, can operate as an AP for the wireless clients.

[0033] Referring to Box D<b>02</b> portion of the application driver, AP firmware D<b>35</b> provides the access point firmware image which had been prepared to be downloaded onto the 802.11 (b) device, which for example may be a PCMCIA or PCI card. AP firmware download module D<b>40</b> provides the capability to change the hardware adapter firmware image. Access control D<b>45</b> is provided in the driver so that client MAC address matching can be performed to control incoming client connection request. AP client management D<b>50</b> provides a systematic way to manage and monitor client activities. AP package processing D<b>55</b> is provided to recognize both packet formats so that it can act as an AP. This functionality is provided since the 802.11(b) protocol standard specifies different packet formats from the wireless side, depending on whether it is client mode or AP mode.

[0034] Outside of Box D<b>02</b>, Window GUI D<b>60</b> is an enhanced Windows GUI program so that the user can control and monitor client activity when in AP mode.

[0035] Reference is now turned to FIG. 5, where an exemplary flow diagram of the methodology in accordance with one embodiment of the present invention is illustrated in conjunction with FIG. 4. Upon activation of the driver (block E<b>00</b>), the user is first recognized (block E<b>10</b>) with AP mode set as the default mode. At this step E<b>10</b>, client code module D<b>15</b> and interrupt service routine D<b>25</b> can tell the user the current mode and function accordingly.

[0036] At block E<b>20</b>, UI module D<b>30</b> and Windows GUI D<b>60</b> detect the user's settings and require the other components to run the designated mode.

[0037] The user may decide not to operate as an AP. If this is the case, the driver continues to operate the host computer as a WC, by running WC code on the 802.11 (b) device. At step E<b>35</b>, when in client mode, only initialization module D<b>10</b>, client code module D<b>15</b>, Tx &amp; Rx module D<b>20</b>, interrupt service routine D<b>25</b> and UI D<b>30</b> will be activated for providing client functions (block E<b>38</b>).

[0038] However, if AP mode is set (block E<b>30</b>), AP firmware image module D<b>35</b> and AP firmware download module D<b>40</b> will be used to download AP firmware to the adapter.

[0039] If the user desires to use the 802.11(b) device as an AP, then the AP firmware is downloaded such that the driver now functions as an AP driver (E<b>40</b>) for the 802.11(b) device and can process and handle the AP packets (E<b>50</b>) between AP and WCs. Here, codes for AP mode will be activated, which preferably include access control module D<b>45</b>, AP client management D<b>50</b>, AP packet processing DS<b>5</b> and Windows GUI for AP processing D<b>60</b>. Requests from other client cards will now be accepted. At block E<b>50</b>, access control D<b>45</b>, AP client management D<b>50</b> and Windows GUI D<b>60</b> are used to administer the packet processing and generate statistics. As should be appreciated by those skilled in the art, there are differences between the ways to process Client packet and to process AP packet. Also, it should be noted that the packet format for AP has been specified by the IEEE 802.11 protocol specifications and such formatting is now implemented in the application driver.

[0040] In contrast to the conventional solutions, where the AP functionality is implemented in the driver, the dynamically downloadable AP driver in accordance with one embodiment of the present invention will not compromise the CPU time.

[0041] When enabled as an access router, the Windows-based wireless access router (“AR”) in accordance with one embodiment of the present invention can achieve the following features. It provides AR function without the hardware AR cost, such that the user's cost is reduced. Also, the Windows-based AR, which operates as an AP with IP sharing functionality, fully utilizes Windows 2000/XP/98SE/Me built-in IP sharing NAT capability. Further, in terms of user interface, users can perform AR configuration using the UI that is similar to the client UI. For non-broadband devices, the Windows-based AR provides AR functionality to USB-based cable modem/DSL, adapter-based cable modem/DSL, or internal/external V.90 analog modem. Finally, it achieves flexible hardware platform support based on 802.11 (b) PCMCIA or PCI adapters. A simplified comparison between an exemplary Windows-based AR in accordance with one embodiment of the present invention and a hardware wireless router is illustrated below: <tables id="TABLE-US-00001" num="1"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="3"><colspec colname="OFFSET" colwidth="42PT" align="left" /><colspec colname="1" colwidth="91PT" align="left" /><colspec colname="2" colwidth="84PT" align="left" /><thead><row>&lt;entry /&gt;&lt;entry /&gt;</row><row>&lt;entry /&gt;<entry namest="OFFSET" nameend="2" align="center" rowsep="1" /></row><row>&lt;entry /&gt;<entry>Win-AR</entry><entry>Hardware Wireless Router</entry></row><row>&lt;entry /&gt;<entry namest="OFFSET" nameend="2" align="center" rowsep="1" /></row></thead><tbody valign="top"><row>&lt;entry /&gt;</row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="3"><colspec colname="1" colwidth="42PT" align="left" /><colspec colname="2" colwidth="91PT" align="left" /><colspec colname="3" colwidth="84PT" align="left" /><tbody valign="top"><row><entry>Platform</entry><entry>Win2000/XP Windows-based</entry><entry>High cost embedded system</entry></row><row><entry>Environment</entry><entry>AR solution</entry><entry>provides the router</entry></row><row>&lt;entry /&gt;&lt;entry /&gt;<entry>functionality</entry></row><row><entry>Requirement</entry><entry>Require only existing</entry><entry>Require power line and</entry></row><row>&lt;entry /&gt;<entry>wireless LAN client device</entry><entry>dedicated Ethernet ports</entry></row><row><entry>Configur-</entry><entry>Windows-based utility for</entry><entry>Web or Windows-based</entry></row><row><entry>ation</entry><entry>real-time access control</entry><entry>utility</entry></row><row><entry>Network</entry><entry>Switch between client</entry><entry>Router only</entry></row><row><entry>mode</entry><entry>and AR</entry></row><row><entry>Region</entry><entry>Depending on adapter</entry><entry>Fixed at one region</entry></row><row><entry>Channels</entry><entry>region</entry></row><row><entry>WEP</entry><entry>Open, 40-bit, 128-bit</entry><entry>Open, 40-bit, 128-bit</entry></row><row><entry>security</entry><entry>encryption</entry><entry>encryption</entry></row><row><entry>Access</entry><entry>Real-time, MAC-address</entry><entry>Limited</entry></row><row><entry>control</entry><entry>based access control</entry></row><row><entry>Status</entry><entry>Real-time</entry><entry>Snapshot</entry></row><row><entry>Report</entry></row><row><entry>Bridging</entry><entry>Ethernet, USB, PCI, IEEE</entry><entry>Ethernet only</entry></row><row><entry>Device</entry><entry>1394, Gigabit, Dial-up</entry></row><row>&lt;entry /&gt;<entry>modem, etc.</entry></row><row><entry>IP-sharing</entry><entry>Windows built-in</entry><entry>Wireless router model</entry></row><row>&lt;entry /&gt;&lt;entry /&gt;<entry>only; wireless AP does</entry></row><row>&lt;entry /&gt;&lt;entry /&gt;<entry>not support.</entry></row><row><entry namest="1" nameend="3" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

[0042] Although the invention is described herein with reference to the preferred embodiment, one skilled in the art will readily appreciate that other applications may be substituted for those set forth herein without departing from the scope of the present invention. Accordingly, the invention should only be limited by the claims included below.