1. Field of the Invention
The present invention relates to a state machine for switching between ad-hoc and infrastructure modes to allow concurrent, multiplexed, service of both wireless networking modes.
2. Description of the Related Art
Wireless networking technology has quickly become a widespread method for maintaining network connectivity in both the office and the home. The convenience of being able to maintain connectivity to the network while moving around the office has been the driving force of wireless networking adoption. The first phase of wireless technology adoption was targeted at products that were expected to have connectivity and/or synchronizing capabilities to the network. Personal computers (PCs), laptops, and handheld organizers (i.e., PDAs) are examples of early wireless adoption. However, with competition and proliferation, the cost of wireless technology has dropped tremendously. Now, it is economically feasible to add wireless network capabilities to products that previously have not had such capabilities.
Wireless networking technology uses radio or microwaves to communicate between multiple computers or peripherals connected to the network, whereas wired networks use copper or fiber optic wires. Using wireless technology, a user can transfer files, share an already existing Internet connection, or remotely control or configure another computer or peripheral in the same network without the need for physical wires. Not having to wire an office or a home is an advantage of wireless networking. Another advantage is giving users the ability to use their computers and PDA's while being able to move around a home, office, or public hot spot without having to be plugged into a network. These wireless network devices communicate with the each other via wireless network cards or access points.
Using this architecture, wireless network cards currently operate in two modes. The first mode is peer-to-peer or Ad-hoc mode, which allows peer-to-peer networking. In ad-hoc mode, multiple computers or peripherals can network without the need for network credentials, an access point, or other similar wireless networking equipment.
The second mode is LAN or Infrastructure mode. This mode gives a network administrator more control over the wireless network by allowing the wireless channel to be locked down and secure. Infrastructure mode typically requires the user to specify user credentials in order to use the wireless network.
Both wireless networking modes are viable and useful. However, there are scenarios where having both modes available provides a convenient method for using wireless networking resources. For example, a user can be an unsecured ad-hoc user of a network system while at the same time, the system may require intranet infrastructure to operate the system.
A scenario where both modes of wireless networking may be needed is networked computer projectors. For example, having ad-hoc mode available would allow peer-to-peer networking, which is convenient when a visitor to a company needs to use a projector connected to the company's internal network. The visitor, who has no network credentials, can send presentations to the projector as long has he has his PC wireless card in ad-hoc mode. At the same time, infrastructure mode would allow employees of the company to operate and manage the projector as a networked resource.
Another scenario where dual mode wireless technology may be utilized is in wireless networked printing. For example, in a company, a visitor may need to print documents to a wireless printer. The ideal method of printing would be ad-hoc mode, since it would allow the user to easily send a print job to a printer without network credentials. In the same scenario, infrastructure mode would allow employees of the company, such as a network administrator to securely configure and update the printer as a networked resource.
Yet another scenario where both wireless networking modes are needed is a wireless Internet café. Currently, intranet tracking by the café owner is done using wired methods, while wireless access is offered to the public via ad-hoc mode. Thus, in this setup, existing wireless Internet café's are not completely wireless. The wired side of the network connects to a full service, fixed location PC.
In a 100% wireless Internet café, customer access to the Internet should be via ad-hoc mode for the purposes of allowing easy access to the networking resources. However, the café owner needs to monitor network traffic for charging purposes. Because of security reasons, these activities should be via infrastructure mode. This would enable the café owner to securely track wireless networks from a central wireless computer within the wireless infrastructure.
Currently, most manufacturers of networking products requiring two physical network links will include the capability for either two wired connections or one wired connection and one wireless connection. It may be possible that two wireless connections are supported. In the case of having two wireless connections, one connection would be configured for infrastructure mode and the other for ad-hoc mode.
Some manufacturers have provided two PCMCIA slots for two wireless network cards, with one card operating in ad-hoc mode and the other operating in infrastructure mode. However, as discussed in U.S. Pat. No. 6,665,269, interference and crosstalk from two wireless network cards which are in close proximity from each other present a problem. Since both wireless cards are transmitting at full duplex to the same frequency band, an increase in signal-to-noise ratio results. This is due to the fact that because there are two wireless network cards transmitting at the same time, the physical layer components of each card are essentially noise interferences to the other card. The close physical proximity of the cards' antennae result in the transmissions of the cards colliding with one another. In addition to this, the receiving channels of cards may conflict with each other.
Current wireless cards and antennae were designed to deal with multi-path interference, hence the work to develop the diversity switch antenna model. In this model, when the radio is in receive mode, it will constantly switch between antennae to listen for a valid radio packet. After hearing the beginning sync of a valid packet, the radio will evaluate the sync signal of the packet on that particular antenna, and then switch to and evaluate the other antenna. After evaluating both antennae, the radio will select the best antenna to receive the remaining portion of the packet. While transmitting a packet, the radio will reuse the same antenna that received the packet. If there is a packet failure, the radio will switch to the other antenna.
However, placing two diversity switch antennae within close proximity to each other causes over-correction and unusual interference. In addition, the problem of having two reception antennae is a classic dipole reflection electromagnetic problem. Using two wireless network cards near each other would see noise and interference at each stage of processing, from the antennae to the MAC layer.
To overcome the previously stated problem, it would be preferable to provide concurrent service between the two wireless networking modes using a single, modified, wireless network card. It would be preferable to use a state machine to switch between the two wireless networking modes. It would also be preferable to have a dual MAC core in the single wireless card that can concurrently support both wireless networking modes.
The present invention addresses the foregoing problems by providing a state machine which has an ad-hoc wait state and an infrastructure wait state. Each wait state waits for their respective RTS or CTS signals to be received or sent. If the RTS or CTS signals are received or sent within a predetermined timeout, the wait state will transition to the processing state which executes the process.
If both types of RTS or CTS signals are received or sent within a short time period from each other, or if, for example, an ad-hoc RTS is received or a CTS sent while the MAC core is executing an infrastructure process, the state machine will transition to the dual process state, which concurrently executes both types of processes.
The dual process state may be achieved by having a radio control port that can detect and handle both types of wireless signals and a dual MAC core that concurrently executes both types of wireless processes. In one embodiment of the dual MAC core, one MAC core may be assigned to execute ad-hoc processes while the other may be assigned to execute infrastructure processes. In another embodiment of the dual MAC core, the primary MAC core may be assigned to execute an ad-hoc or an infrastructure process, whichever process arrives first, while the secondary MAC core may be assigned to process the other type of process. In another embodiment of the dual MAC core, the MAC core runs at a normal clocked rate while executing either an ad-hoc or an infrastructure process. If, for example, the MAC core is currently executing an ad-hoc process and then receives an infrastructure process, the MAC core will concurrently execute both processes at an over-clocked rate, to compensate for the increased load of processes. In yet another embodiment of the dual MAC core, all the embodiments previously stated may be executed using a MAC core implemented in a software program.
Other features and advantages of the present invention will be apparent from the following description taken in conjunction with the accompanying drawings, in which like reference characters designate the same or similar parts throughout the figures thereof.
The accompanying drawings, which are incorporated in and constitute a part of the specification, illustrate embodiments of the invention and, together with the description, serve to explain the principles of the invention.
If the state machine is at ad-hoc process state 32 and an infrastructure RTS or CTS is received or sent, ad-hoc process state 32 transitions to dual process state 38 for concurrent execution of both processes. After dual process 38 executes the infrastructure process, the state machine transitions back to ad-hoc process state 32. If the state machine is at infrastructure process state 36 and an ad-hoc RTS or CTS is received or sent, infrastructure process state 36 transitions to dual process state 38 for concurrent execution of both processes. After dual process state 38 executes the ad-hoc process, the state machine transitions back to infrastructure process state 36.
Ad-hoc wait state 30 waits for ad-hoc RTS or CTS signals for a predetermined timeout labeled TOWS1 (Time Out for Ad-hoc Wait State.) If an ad-hoc signal is not detected within TOWS1, ad-hoc wait state 30 transitions to infrastructure wait state 34 to listen for infrastructure signals. If an ad-hoc signal is detected within TOWS1, the ad-hoc wait state 30 transitions to the ad-hoc process state 32, which executes the ad-hoc process. After ad-hoc process state 32 executes the ad-hoc process, ad-hoc process state 32 transitions back to ad-hoc wait state 30 to wait for additional ad-hoc signals.
Conversely, infrastructure wait state 34 waits for infrastructure RTS or CTS signals for a predetermined timeout labeled TOWS2 (Time Out for Infrastructure Wait State.) If an infrastructure signal is not detected within TOWS2, infrastructure wait state 34 transitions to ad-hoc wait state 30 to listen for ad-hoc signals. If an infrastructure signal is detected within TOWS2, the infrastructure wait state 34 transitions to infrastructure process state 36, which executes the infrastructure process. After infrastructure process state 36 executes the infrastructure process, infrastructure process state 36 transitions back to infrastructure wait state 34 to wait for additional infrastructure signals.
As stated earlier, TOWS1 and TOWS2 are predetermined timeouts for ad-hoc and infrastructure signals respectively, however, such timeouts can be changed to fit the needs of the user. If the majority of the traffic in the wireless network is ad-hoc mode, a user can increase TOWS1 in comparison to TOWS2 to allow a longer timeout to listen to ad-hoc requests, thus improving the efficiency of the wireless state machine. Conversely, TOWS2 can be increased in comparison to TOWS1 for networks which primarily use infrastructure mode. Such change in TOWS1 and TOWS2 may be manually configured or may be changed dynamically by using a mechanism to count the number of ad-hoc verses infrastructure requests, and to adjust the values of TOWS1 and TOWS2 accordingly.
This switching between listening for ad-hoc and infrastructure signals, and the features of dual process state 38 allows the present invention to concurrently support both types of wireless networking modes. Although ad-hoc and infrastructure wireless networking modes are mentioned in the application, the present invention is not limited to these wireless networking modes.
Dual process state 38 may require dual MAC 26b, 26c, 26d, or 26e, that can process both types of wireless networking modes. Current wireless cards which use MAC core 26a (
Assigned Dual MAC
In one embodiment of the present invention, assigned dual MAC 26b preferably contains MAC primary core 50a and MAC secondary core 50b (
Radio data interface 40 receives radio data from the baseband processor 24. Radio control port 42 receives data from radio data interface 40 and detects and processes both ad-hoc and infrastructure requests from the radio data. Serial control (1) 44 takes the data from radio control port 42, converts the data into serial data, and sends the serial data to MAC primary core 50a. Serial control (2) 48 takes data from radio control port 42, converts the data into serial data, and sends the serial data to MAC secondary core 50b.
Each MAC core is assigned to execute either ad-hoc processes or infrastructure processes. For example, MAC primary core 50a may be assigned to execute ad-hoc processes while MAC secondary core 50b may be assigned to execute infrastructure processes. Assigned dual MAC 26b incorporates the state diagram illustrated in
First-In First-Out (FIFO) Dual MAC
If, for example, MAC primary core 50a is executing an ad-hoc process and an infrastructure request is detected by radio control port 42, auxiliary mode control 47 will activate MAC secondary core 50b, set MAC secondary core 50b to infrastructure mode, and MAC secondary core 50b will proceed to execute the infrastructure process. If, for example, MAC primary core 50a is executing an infrastructure process and an ad-hoc request is received at radio data interface 40, auxiliary mode control 47 will activate MAC secondary core 50b, set MAC secondary core 50b to ad-hoc mode, and MAC secondary core 50b will proceed to execute the ad-hoc process.
Full-Time Dual MAC
This embodiment includes many of the features of the assigned dual MAC 26b and the FIFO dual MAC 26c discussed above. In this embodiment of the present invention, either an ad-hoc or an infrastructure process is executed using parallel processing over both MAC primary core 50a and MAC secondary core 50b if only one network mode is detected by radio control port 42. If, for example, MAC primary core 50a and MAC secondary core 50b are currently executing an ad-hoc process, and radio control port 42 detects an infrastructure process, both processes will be executed using either the FIFO dual MAC 26c or the assigned dual MAC 26b as previously discussed. The same will hold true if MAC primary core 50a and MAC secondary core 50b are currently executing an infrastructure process and radio control port 42 detects an ad-hoc process.
Over-Clocking MAC
Yet another embodiment of the present invention is over-clocking MAC 26d, illustrated by
Software MAC
Current MACs are implemented in a hardware chipset as illustrated in
While the invention is described above with respect to what is currently its preferred embodiment, it is to be understood that the invention is not limited to that described above. To the contrary, the invention is intended to cover various modifications and equivalent arrangements within the spirit and scope of the appended claims.
Number | Name | Date | Kind |
---|---|---|---|
5702425 | Wickham | Dec 1997 | A |
6665269 | Schmitz | Dec 2003 | B1 |
6665311 | Kondylis et al. | Dec 2003 | B2 |
6925378 | Tzamaloukas | Aug 2005 | B2 |
6978023 | Dacosta | Dec 2005 | B2 |
7103314 | Li | Sep 2006 | B2 |
7221667 | Hori et al. | May 2007 | B2 |
7233603 | Lee | Jun 2007 | B2 |
7274911 | Li | Sep 2007 | B2 |
7522551 | Giaimo et al. | Apr 2009 | B2 |
20020176366 | Ayyagari et al. | Nov 2002 | A1 |
20030053437 | Bahl et al. | Mar 2003 | A1 |
20030054818 | Bahl et al. | Mar 2003 | A1 |
20030063589 | Haines | Apr 2003 | A1 |
20030080992 | Haines | May 2003 | A1 |
20030081561 | Hsiao | May 2003 | A1 |
20030142652 | Ting et al. | Jul 2003 | A1 |
20030229816 | Meynard | Dec 2003 | A1 |
20040004973 | Lee | Jan 2004 | A1 |
20040063458 | Hori et al. | Apr 2004 | A1 |
20040103278 | Abhishek et al. | May 2004 | A1 |
20040127240 | Li | Jul 2004 | A1 |
20040156351 | Kim | Aug 2004 | A1 |
20040163000 | Kuhlmann et al. | Aug 2004 | A1 |
20040214539 | Rajamani et al. | Oct 2004 | A1 |
20040264425 | Nishikawa | Dec 2004 | A1 |
20050048961 | Ribaudo et al. | Mar 2005 | A1 |
20050063348 | Donovan | Mar 2005 | A1 |
20050122940 | Nian | Jun 2005 | A1 |
20050147071 | Karaoguz et al. | Jul 2005 | A1 |
20050165916 | Cromer et al. | Jul 2005 | A1 |
20050215266 | Tsien et al. | Sep 2005 | A1 |
20050216726 | Dellmo et al. | Sep 2005 | A1 |
20050256937 | Lewis | Nov 2005 | A1 |
20060135209 | Nakakita et al. | Jun 2006 | A1 |
20060153133 | Zhong | Jul 2006 | A1 |
20070055870 | Bruti et al. | Mar 2007 | A1 |
20080025501 | Sato et al. | Jan 2008 | A1 |
20080133716 | Rao et al. | Jun 2008 | A1 |
20080305738 | Khedouri et al. | Dec 2008 | A1 |
20090161643 | Ihori et al. | Jun 2009 | A1 |
Number | Date | Country | |
---|---|---|---|
20060050729 A1 | Mar 2006 | US |