AD HOC WIRELESS NETWORKING

• US 20090109995A1
• Filed: 10/26/2007
• Published: 04/30/2009
• Est. Priority Date: 10/26/2007
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Madhaven, Poovanpilli G., Stewart, John-Paul M., Deng, Zhong, Alam, Mohammad Shabbir, Mittal, Sharad, Agiwal, Ankur, Zan, Xinyan, Li, Frank
• Granted Patent: US 7,911,990 B2
• Time in Patent Office: Days
• US Class Current: 370/463
• CPC Class Codes: H04W 28/065 using assembly or disassembly of packets
• CPC Class Codes: H04W 80/06 Transport layer protocols, e.g. TCP [Transport Control Protocol] over wireless transmission control protocol/Internet protocol [TCP/IP] or user datagram protocol [UDP] H04L69/16
• CPC Class Codes: H04W 84/18 Self-organising networks, e.g. ad-hoc networks or sensor networks

Abstract

A software architecture providing ad hoc wireless networking capabilities. The software architecture may be compatible with wireless devices, such as UWB devices operating according to the WLP communication protocol. The software architecture may include user mode and kernel mode modules, and may include a multiplexing driver framework to enable system connection to multiple ad hoc networks.

Claims

1. A method of enabling a computer system to connect to a plurality of ad hoc wireless networks using a same physical adapter, the networks each implementing an ad hoc network protocol for communications, the method comprising:

binding a multiplexing network driver to the physical adapter, the physical adapter configured to receive data from each of a plurality of available ad hoc networks; and

using the multiplexing network driver to create an interface between the physical adapter and at least one upper layer networking stack for each of at least two of the available ad hoc networks simultaneously.

2. The method of claim 1, wherein at least one of the interfaces created by the multiplexing network is a virtual interface.

3. The method of claim 2, further comprising using the multiplexing driver to maintain mapping information mapping the at least one virtual interface to the physical adapter.

4. The method of claim 2, wherein the at least one virtual interface emulates an IEEE Ethernet connection to the at least one upper layer networking stack.

5. The method of claim 4, wherein the upper layer networking stack comprises a TCP/IP networking component.

6. The method of claim 1, wherein the multiplexing network driver is a kernel mode module, and wherein the method further comprises using the multiplexing driver to expose a set of private interfaces with which user mode modules interact.

7. The method of claim 1, further comprising sending an outgoing data packet from the at least one upper layer networking stack to the multiplexing network driver and using the multiplexing network driver to add a network protocol frame header to the outgoing data packet and forward the data packet over the physical adapter.

8. The method of claim 7, further comprising receiving an incoming network protocol data packet on the physical adapter and using the multiplexing network driver to examine a network protocol frame header on the incoming network protocol data packet and extract a network identification tag.

9. The method of claim 1, wherein the multiplexing network driver is a network driver interface specification (NDIS) multiplexing driver.

10. A computer-readable medium having computer-executable instructions for performing steps comprising:

binding a multiplexing network driver to a physical adapter in an ad hoc network computer system;

identifying a plurality of available ad hoc networks; and

using the multiplexing network driver to create an interface between the physical adapter and at least one upper layer networking stack for each of at least two of the identified available ad hoc networks simultaneously.

11. The computer-readable medium of claim 10, wherein at least one of the interfaces created by the multiplexing network is a virtual interface.

12. The computer-readable medium of claim 11, having further computer-executable instructions for performing the step of using the multiplexing driver to generate mapping information mapping the at least one virtual interface to the physical adapter.

13. The computer-readable medium of claim 12, wherein the at least one virtual interface emulates an IEEE Ethernet connection to the at least one upper layer networking stack.

14. The computer-readable medium of claim 10, having further computer-executable instructions for performing the step of sending an outgoing data packet from the at least one upper layer networking stack to the multiplexing network driver and using the multiplexing network driver to add a network protocol frame header to the outgoing data packet.

15. The computer-readable medium of claim 14, having further computer-executable instructions for performing the step of receiving an incoming network protocol data packet and extracting a network identification tag.

16. A computer system configured to connect to an ad hoc network, the computer system comprising at least one processor that, when loaded with computer-readable instructions, executes the instructions to perform steps of:

receiving on a physical adapter data from each of a plurality of available ad hoc networks;

binding a network driver to the physical adapter; and

using the network driver to create an interface between the physical adapter and at least one upper layer networking stack for each of at least two of the available ad hoc networks simultaneously.

17. The computer system of claim 16, wherein at least one of the interfaces created by the network driver is a virtual interface.

18. The computer system of claim 17, further configured to execute instructions for performing the step of using the driver to generate mapping information mapping the at least one virtual interface to the physical adapter.

19. The computer system of claim 16, further configured to execute instructions for performing the step of using the network driver to add a network protocol frame header to an outgoing data packet and forward the data packet over the physical adapter.

20. The computer system of claim 19, further configured to execute instructions for performing the step of receiving an incoming network protocol data packet and using the network driver to examine a network protocol frame header on the incoming network protocol data packet and extract a network identification tag.