US 7,284,268 B2Grant
System and method for a routing device to securely share network data with a host utilizing a hardware firewall
Issue Date:2007-10-16
•21 Claims
•4 Drawing Sheets
Abstract
A system and method for providing the ability to selectively share data in a network routing device with an associated host. The system and method employs a hardware firewall in the routing device which restricts the host such that it can only access areas in shared memory which contains data destined for the host. The routing device CPU notifies the host of pending data and the location of that data in the shared memory. The hardware firewall is also notified of the location in shared memory which the host may access. When the host attempts to read the data, the firewall ensures that only the stated memory area or areas are accessed by the host. Once the data has been read by the host, the firewall is notified to cancel the host's ability to access the shared memory until such time as a new packet destined for the host arrives in the routing device.
Metadata
Assignee
- Meshnetworks, Inc.
Inventors
- Jeffrey C. Schmidt
- Philip A. Gutierrez
- Charles R. Barker, Jr.
Application Information
Application Number:US 10/255,608
Filing Date:2002-09-27
Priority Date:2002-05-16
Art Unit:2131
Classifications
IPC:
H04L29/00H04L29/02
Patent Drawings (4 sheets)
Description
[0001] This application claims the benefit of U.S. Provisional Patent Application No. 60/378,055 entitled “A System And Method For A Routing Device To Securely Share Network Data With A Host Utilizing A Hardware Firewall”, filed May 16, 2002, the entire contents of which being incorporated herein by reference.
Background of the Invention
[0002] 1. Field of the Invention
[0003] The present invention relates to a system and method for selectively sharing data contained in a network routing device with an associated host device. More particularly, the invention relates to a system and method for enabling routing device hardware to provide selective access by a host device to shared memory within the routing device, thus restricting the host's ability to access data not intended for use by the host.
[0004] 2. Description of the Related Art
[0005] In recent years, a type of mobile communications network known as an “ad-hoc” network has been developed. In this type of network, each user terminal is capable of operating as a base station or router for other mobile nodes, thus eliminating the need for a fixed infrastructure of base stations. Accordingly, data packets being sent from a source mobile node to a destination mobile node are typically routed through a number of intermediate mobile nodes before reaching the destination node.
[0006] More sophisticated ad-hoc networks are also being developed which, in addition to enabling mobile nodes to communicate with each other as in a conventional ad-hoc network, further enable the mobile nodes to access a fixed network and communicate with other types of user terminals, such as those on the public switched telephone network (PSTN) and on other networks, such as the Internet. Details of these types of ad-hoc networks are described in U.S. Pat. No. 7,072,650 entitled “Ad Hoc Peer-to-Peer Mobile Radio Access System Interfaced to the PSTN and Cellular Networks”, issued on Jul. 4, 2006, U.S. Pat. No. 6,807,165 entitled “Time Division Protocol for an Ad-Hoc, Peer-to-Peer Radio Network Having Coordinating Channel Access to Shared Parallel Data Channels with Separate Reservation Channel”, issued on Oct, 19, 2004, and in U.S. Pat. No. 6,873,839 entitled “Prioritized-Routing for an Ad-Hoc, Peer-to-Peer, Mobile Radio Access System”, issued on Mar. 29, 2005, the entire content of each being incorporated herein by reference.
[0007] Generally, all nodes in a wireless ad-hoc peer-to-peer network provide similar core services and functionality, although their specific functionality can depend on their intended purposes, such as use as an access point, fixed router or mobile terminal. Although each node can provide similar services, the workload is typically distributed across many nodes rather than centralized at a single location in the peer-to-peer network. Therefore peer-to-peer networks distinguish themselves from infrastructure networks where one or more nodes offer a superset of the functionality of the rest of the network. Infrastructure nodes in these networks typically can handle Dynamic Host Configuration Protocol (DHCP), Address Resolution Protocol (ARP), as well as other services that depend on broadcast traffic. Dynamic Host Configuration Protocol is defined by IETF RFC 2131 and 2132, which are incorporated herein by reference, and is used by a client node to automatically obtain network settings from a central server. These network settings include the client's IP address, the address of Domain Name Servers (DNS), the IP address of default gateways, and many other network settings. Address Resolution Protocol is defined by STD 0037 and RFC 0826, which are incorporated herein by reference, and is used by a network node to map IP addresses to MAC addresses so IP traffic can be delivered to specific hardware. Such infrastructure nodes are normally discovered by broadcast traffic advertisements from their client nodes in a network.
[0008] As can be appreciated by one skilled in the art, traffic in such networks includes direct and indirect communications, in which nodes can be used as routers while both stationary or mobile. A mobile node typically includes a host, such as a personal computer (PC) or personal digital assistant (PDA), with an attached transceiver and a controller. A mobile node can further include a network interface device coupled to a host device, which allows the host device communication access with the network. The transceiver of the mobile node receives data packets, such as voice, data or multimedia data packets, from other nodes, and the controller determines which data packets are intended for it's associated host. If a data packet is intended for the associated host, the host is notified to retrieve the packet. If the packet is not intended for the associated host, the controller determines the next node to which the data packet should be sent based on routing table or similar information, and controls the transceiver of the mobile node to send the data packet to the next node.
[0009] In traditional networks where the user nodes do not re-route traffic, the network interface device will inspect an incoming packet header and store packet data only if it is destined for the host device associated with the network interface device. Therefore, the host never has the opportunity to examine data which is intended for other devices. However, once a device is required to reroute packets to a destination device other than the associated host as in an ad-hoc network, all packets must be captured and evaluated by the routing device. Once a packet is captured by a network interface device, it then may become susceptible to unauthorized access by the associated host device.
[0010] However, the ability to selectively share data between a routing device and an associated host, such as a personal computer, is necessary in a wireless ad-hoc network. This allows a subscriber to have an access point for extracting or sending data through the network. Because the vast majority of routing resources or nodes that exist in a multihopping, ad-hoc network each route data that is not intended for its associated host, precautions must be taken to insure that only data intended for the node's associated host can be extracted from the routing device in the node. However, many of the methods for achieving this are either inefficient in their ability to route data, require use of multiple memories, or are insecure.
[0011] Accordingly, a need exists for a system and method for protecting data traveling through a network by ensuring that a host device may only access data that was intended for access by that host device.
Summary of the Invention
[0012] An object of the present invention is to provide a system and method for restricting a host device from accessing network data which is not intended for host access.
[0013] Another object of the present invention is to provide a hardware implemented firewall internal to a routing device in a communication network, such as an ad-hoc network, to prevent unauthorized access by a host device to data stored in shared memory on the routing device.
[0014] A further object of the present invention is to restrict host access to the shared memory such that there may be no access, access to a single area, or access to multiple areas in the shared memory when required.
[0015] Another objective of the present invention is to disallow host access to the shared memory once the host has retrieved the data it is permitted to retrieve.
[0016] These and other objects are substantially achieved by providing a system and method to securely share data between a routing device and an associated host by utilizing a hardware firewall which restricts the host's access to a shared memory area on the routing device. The system and method employs a hardware firewall in the routing device which restricts the host such that it can only access areas in shared memory which contains data destined for the host. The routing device CPU notifies the host of pending data and the location of that data in the shared memory. The hardware firewall is also notified of the location in shared memory which the host may access. When the host attempts to read the data, the firewall ensures that only the stated memory area or areas are accessed by the host. Once the data has been read by the host, the firewall is notified to cancel the host's ability to access the shared memory until such time as a new packet destined for the host arrives in the routing device.
Brief Description of the Drawings
[0017] These and other objects, advantages and novel features of the invention will be more readily appreciated from the following detailed description when read in conjunction with the accompanying drawings, in which:
[0018] FIG. 1 is a conceptual block diagram of an example of an ad-hoc wireless communications network including a plurality of nodes employing an embodiment of the present invention;
[0019] FIG. 2 is a conceptual block diagram of an example of components of a wireless node as shown in FIG. 1 , including firewall hardware elements in accordance with an embodiment of the present invention; and
[0020] FIG. 3 is a flow diagram illustrating an example of the logic of a secure data transaction from the routing device of a node as shown in FIGS. 1 and 2 to the host associated with that routing device in accordance with an embodiment of the present invention.
Detailed Description of the Preferred Embodiments
[0021] FIG. 1 is a block diagram illustrating an example of an ad-hoc packet-switched wireless communications network 10 employing an embodiment of the present invention. Specifically, the network 10 includes a plurality of mobile wireless user terminals 102-1 through 102-n (referred to generally as nodes or mobile nodes 102), and a fixed network 104 having a plurality of access points 106-1, 106-2, . . . 106-n (referred to generally as nodes or access points 106), for providing the nodes 102 with access to the fixed network 104. The fixed network 104 includes, for example, a core local access network (LAN), and a plurality of servers and gateway routers, to provide the nodes 102 with access to other networks, such as other ad-hoc networks, the public switched telephone network (PSTN) and the Internet.
[0022] The network 10 further includes a plurality of fixed routers 107-1 through 107-n (referred to generally as nodes or fixed routers 107) for routing data packets between other nodes 102, 106 or 107. As can be appreciated by one skilled in the art, the nodes 102, 106 and 107 are capable of communicating directly with each other, or via one or more other nodes operating as routers for data packets being sent between nodes, as described in U.S. Pat. No. 5,943,322 to Mayor and in U.S. Pat. Nos. 7,072,650 and 6,807,165, referenced above. The data packets can include voice, data or multimedia.
[0023] Specifically, as shown in FIG. 2 , any of the nodes 102, 106 or 107 and, in particular, each mobile node 102, includes a routing device 1000 and a host device 100. The host 100 is typically a personal computer (PC) or personal digital assistant (PDA), used by a subscriber to gain access to the network 10 shown in FIG. 1 , but can be any number of devices, such as a notebook computer terminal, mobile telephone unit, mobile data unit, or any other suitable device. In this example, routing device 1000 includes two external interfaces. The host interface 200 allows a host device 100 and the routing device 1000 to communicate. The radio frequency (RF) interface 910 allows the RF signal 920 to be either received by or transmitted from the routing device 1000. The embodiment shown in FIG. 2 utilizes an RF signal as the medium in the physical layer, as defined in the OSI model, ISO/IEC 7498-1 (1994), the entire contents being incorporated herein by reference. However, any type of medium, such as infrared, fiber optics, or wire, could be used by the physical layer to send the data packets between the nodes 102, 106 and 107.
[0024] As further shown in FIG. 3 , the routing device 1000 of FIG. 3 includes an internal hardware firewall 300, a mailbox 400, a packet buffer 500, a routing device CPU 600, a modem interconnect bus 700, a baseband modem 800 and an RF section 900. The hardware firewall 300 provides selective read and write access to the packet buffer 500 by the host 100. The configuration and control of the hardware firewall 300 is controlled solely by the routing device CPU 600 in this example.
[0025] The mailbox 400 of the routing device 1000 in FIG. 3 provides a common set of registers, shared by the host 100 and routing device CPU 600, which are used to exchange small amounts of data and messages. The packet buffer 500 of the routing device 1000 is a memory device also shared by the routing device CPU 600 and the host 100. The routing device CPU 600 includes a processor capable of executing instructions that control the functions of the modem 800, execute routing algorithms, and perform data movement transactions. The CPU 600 and modem 800 also include the appropriate hardware and software to provide IP, ARP, admission control (AC), traffic control (TC), ad-hoc routing (AHR), logic link control (LLC) and media access control (MAC). The transceiver 110 further includes the appropriate hardware and software for IAP association (IA), UDP, simple network management protocol (SNMP), data link (DL) protocol and dynamic host configuration protocol (DHCP) relaying.
[0026] The modem interconnect bus 700 of the routing device 1000 in FIG. 3 is used to interconnect the elements of the modem transceiver. Further details of an example of this type of bus are described in U.S. patent application publication No. 20030043790A1 entitled “Multi-Master Bus Architecture for System-On-Chip Designs” filed on Sep. 6, 2001, the entire content being incorporated herein by reference.
[0027] The baseband modem 800 of the routing device 1000 in FIG. 3 modulates the outgoing signals to analog format, and demodulates incoming signals to digital format. The RF section 900 upconverts the modulated baseband signal for RF propagation and downconverts the received RF signal for demodulation by the modem 800, and the RF signal 920 provides the physical layer for communicating between routing devices in the nodes 102, 106 and 107.
[0028] In FIG. 3 , a flow diagram illustrating an example of the logic of a secure data transaction from the routing device 1000 to the host 100 in accordance with an embodiment of the present invention is shown. In step 1010 shown in FIG. 3 , data received at the routing device 1000 is transferred from the physical layer, such as an RF signal sent from another node 102, 106 or 107, to the modem 800 where it is converted to digital format. In the embodiment shown in FIG. 3 , an RF signal is used as the medium in the physical layer, however as pointed out above, any type of medium could be used by the physical layer, such as infrared, fiber optics, or wire.
[0029] In step 1020, the digital format packet is transferred from the baseband modem 800 to the packet buffer 500 by the routing device CPU 600. In step 1030, the routing device CPU 600 determines if the local host 100 needs access to the data, and then notifies the hardware firewall 300 of the specific packet buffer 500 area which the host 100 is to be allowed access. If the packet is not destined for the associated host 100, the host is not notified of the new packet.
[0030] In step 1040, the routing device CPU 600 places the address range of the data to be delivered to the host 100 in the mailbox 400 and then signals the host 100 to retrieve the message from the mailbox. In step 1050, the host 100 reads the message in the mailbox 400 and discovers what part of the packet buffer 500 it is to access, and in step 1060, the host 100 reads the data in the designated area of the packet buffer 500.
[0031] The hardware firewall 300 ensures that only the designated area is accessed by the host 100. In Block 1070 the host 100 writes a message to the mailbox 400 indicating that the read action has been completed and signals the routing device CPU 600. Finally, in Block 1080, the routing device CPU 600 notifies the hardware firewall 300 that the host 100 no longer has access to the designated area of the packet buffer 500.
[0032] The embodiment of the present invention described provides a single memory resource that is utilized by the routing device and the associated host. Since each routing device in the network must temporarily store data in a memory for either access by the host or retransmission to another routing resource or destination, a common memory is used. The use of a shared memory resource, such as a “packet buffer” 500, has the advantage of reducing the number of separate memories required to store data and reduces the number of transactions that a processor must perform in order to transfer data to it's intended destination.
[0033] The embodiment described above provides selective access by the host to the shared memory or “packet buffer” 500 on the routing device 1000. The selective access by the host is implemented solely by hardware in the routing device such that no security protocol or encryption is required to protect data not intended to be accessed by the host. Host access to the packet buffer can be configured to allow multiple windows of different memory ranges, or alternatively, host access to the packet buffer can be eliminated entirely. Additionally, the embodiment includes a mechanism to communicate to the host which areas it is allowed to access in the packet buffer.
[0034] Furthermore, data movement is minimized between memories because the host 100 and routing device CPU 600 have direct access to the shared packet buffer 500. By securely using a single shared memory, cost is minimized and data transfer efficiency is maximized in the routing device while maintaining the integrity of the network data. Furthermore, by implementing the firewall 300 in the routing device hardware, it is not susceptible to hacking from the host computer 100.
[0035] Although network routers and bridges reroute network traffic, they typically do not have associated hosts. While security issue addressed by the embodiment of the present invention described above could potentially apply to any communications device with an associated host, they specifically apply to devices which support multi-hopping. The embodiment of the present invention described above restricts a host from reading data not intended for it, however it does not deal with restrictions on the ability of the host to write data to the routing device.
[0036] Although only a few exemplary embodiments of the present invention have been described in detail above, those skilled in the art will readily appreciate that many modifications are possible in the exemplary embodiments without materially departing from the novel teachings and advantages of this invention. Accordingly, all such modifications are intended to be included within the scope of this invention as defined.
Claims
What is claimed is:
1. A node for use in a wireless ad-hoc communications network, said node comprising:
a host device for processing one or more data packets intended for said node; and
a routing device for routing one or more other data packets to and from one or more other nodes in said wireless ad-hoc network, said routing device comprising:
a memory for storing said one or more data packets and said one or more other data packets,
an internal hardware firewall, adapted to provide access by said host device to said one or more data packets stored in said memory, and further adapted to prevent access by said host device to said one or more other data packets, and
a controller, adapted to configure said internal hardware firewall to provide or prevent said access,
wherein said memory comprises:
a register mailbox, and
a packet buffer which has a plurality of addresses, and
wherein said memory is adapted to provide a common set of registers to said host device and said controller.
2. A node as claimed in claim 1, further comprising:
a modem, adapted to modulate an outgoing signal into an analog format, and demodulate an incoming signal into a digital format packet; and
wherein said controller is further adapted to direct modem control functions to demodulate an incoming signal into a digital format packet.
3. A node as claimed in claim 1, wherein:
said controller is further adapted to retrieve a completion reply from said host device and in response, to configure said internal hardware firewall to prohibit said host device to access said register mailbox and said packet buffer.
4. A node as claimed in claim 2, wherein:
said controller is further adapted to direct routing functions to transfer a digital format packet from said modem to an address range of said packet buffer.
5. A node as claimed in claim 2, wherein:
said controller is further adapted to determine if said host device requires access to said incoming signal digital format packet and in response, to configure said internal hardware firewall to allow said host device access to said register mailbox via a host interface.
6. A node as claimed in claim 2, wherein:
said controller is further adapted to determine an address range in said packet buffer which contains said digital format packet and to place a message containing said address range in said register mailbox, and to signal said host device to access said register mailbox to retrieve said message.
7. A node as claimed in claim 4, wherein:
said controller is further adapted to configure said internal hardware firewall to allow said host device to access said address range of said packet buffer.
8. A method of managing access to data stored within a node in a wireless ad-hoc network, wherein said node comprises a host device and a routing device, wherein said routing device includes a memory, an internal hardware firewall, and a controller, said method comprising:
storing one or more data packets intended for said node within said memory;
storing one or more other data packets intended for one or more other nodes in said wireless ad-hoc network;
controlling said internal hardware firewall to:
provide access by said host device to said one or more data packets stored in said memory, and
prevent access to said one or more other data packets stored in said memory,
wherein said memory includes a register mailbox and a packet buffer which has a plurality of addresses,
said method further comprising providing a common set of registers to said host device and said controller.
9. A method as claimed in claim 8, further comprising:
controlling a modem to modulate an outgoing signal into an analog format, and to demodulate an incoming signal into a digital format packet; and
directing one or more modem control functions to demodulate an incoming signal into a digital format packet.
10. A method as claimed in claim 8, further comprising:
retrieving a completion reply from said host device and in response, to configure said internal hardware firewall to prohibit said host device to access said register mailbox and said packet buffer.
11. A method as claimed in claim 9, further comprising:
controlling routing functions to transfer a digital format packet from said modem to an address range of said packet buffer.
12. A method as claimed in claim 9, further comprising:
determining if said host device requires access to said incoming signal digital format packet and in response, to configure said internal hardware firewall to allow said host device access to said register mailbox via a host interface.
13. A method as claimed in claim 9, further comprising:
determining an address range in said packet buffer which contains said digital format packet and to place a message containing said address range in said register mailbox, and to signal said host device to access said register mailbox to retrieve said message.
14. A method as claimed in claim 11, further comprising:
configuring said internal hardware firewall to allow said host device to access said address range of said packet buffer.
15. A computer-readable medium of instructions for managing access to data stored within a node in a wireless ad-hoc communications network, wherein said node comprises a host device and a routing device, wherein said routing device includes a memory, an internal hardware firewall, and a controller, said computer-readable medium of instructions comprising:
a first set of instructions, adapted to control an internal hardware firewall at said node to provide access by said host device to a portion of said memory containing one or more data packets intended for said node, and to prevent access to an other portion of said memory containing one or more other data intended for one or more other nodes in said wireless ad-hoc network; and
a second set of instructions, adapted to control a router device central processing unit (CPU) to configure said internal hardware firewall to provide or prevent said access, wherein:
said second set of instructions is adapted to control said memory, including a register mailbox and a packet buffer which has a plurality of addresses, to provide a common set of registers to said host device and said controller.
16. A computer-readable medium of instructions as claimed in claim 15, wherein:
said second set of instructions is adapted to control a modem to modulate an outgoing signal into an analog format, and to demodulate an incoming signal into a digital format packet; and
wherein said second set of instructions is further adapted to direct modem control functions to demodulate an incoming signal into a digital format packet.
17. A computer-readable medium of instructions as claimed in claim 15, wherein:
said second set of instructions is adapted to retrieve a completion reply from said host device and in response, to configure said internal hardware firewall to prohibit said host device to access said register mailbox and said packet buffer.
18. A computer-readable medium of instructions as claimed in claim 16, wherein:
said second set of instructions is adapted to direct routing functions to transfer a digital format packet from said modem to an address range of said packet buffer.
19. A computer-readable medium of instructions as claimed in claim 16, wherein:
said second set of instructions is adapted to determine if said host device requires access to said incoming signal digital format packet and in response, to configure said internal hardware firewall to allow said host device access to said register mailbox via a host interface.
20. A computer-readable medium of instructions as claimed in claim 16, wherein:
said second set of instructions is adapted to determine an address range in said packet buffer which contains said digital format packet and to place a message containing said address range in said register mailbox, and to signal said host device to access said register mailbox to retrieve said message.
21. A computer-readable medium of instructions as claimed in claim 18, wherein:
said second set of instructions is adapted to configure said internal hardware firewall to allow said host device to access said address range of said packet buffer.
Patent Citations (126)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US4494192(A) | 1985-01-01 | Lew et al. | Applicant |
| US4617656(A) | 1986-10-01 | Kobayashi et al. | Applicant |
| US4736371(A) | 1988-04-01 | Tejima et al. | Applicant |
| US4742357(A) | 1988-05-01 | Rackley | Applicant |
| US4747130(A) | 1988-05-01 | Ho | Applicant |
| US4910521(A) | 1990-03-01 | Mellon | Applicant |
| US5034961(A) | 1991-07-01 | Adams | Applicant |
| US5068916(A) | 1991-11-01 | Harrison et al. | Applicant |
| US5231634(A) | 1993-07-01 | Giles et al. | Applicant |
| US5233604(A) | 1993-08-01 | Ahmadi et al. | Applicant |
| US5241542(A) | 1993-08-01 | Natarajan et al. | Applicant |
| US5317566(A) | 1994-05-01 | Joshi | Applicant |
| US5392450(A) | 1995-02-01 | Nossen | Applicant |
| US5412654(A) | 1995-05-01 | Perkins | Applicant |
| US5424747(A) | 1995-06-01 | Chazelas et al. | Applicant |
| US5502722(A) | 1996-03-01 | Fulghum | Applicant |
| US5517491(A) | 1996-05-01 | Nanni et al. | Applicant |
| US5555425(A) | 1996-09-01 | Zeller et al. | Applicant |
| US5555540(A) | 1996-09-01 | Radke | Applicant |
| US5572528(A) | 1996-11-01 | Shuen | Applicant |
| US5615212(A) | 1997-03-01 | Ruszczyk et al. | Applicant |
| US5618045(A) | 1997-04-01 | Kagan et al. | Applicant |
| US5621732(A) | 1997-04-01 | Osawa | Applicant |
| US5623495(A) | 1997-04-01 | Eng et al. | Applicant |
| US5627976(A) | 1997-05-01 | McFarland et al. | Applicant |
| US5631897(A) | 1997-05-01 | Pacheco et al. | Applicant |
| US5638448(A) | 1997-06-01 | Nguyen | Applicant |
| US5644576(A) | 1997-07-01 | Bauchot et al. | Applicant |
| US5652751(A) | 1997-07-01 | Sharony | Applicant |
| US5680392(A) | 1997-10-01 | Semaan | Applicant |
| US5684794(A) | 1997-11-01 | Lopez et al. | Applicant |
| US5687194(A) | 1997-11-01 | Paneth et al. | Applicant |
| US5696903(A) | 1997-12-01 | Mahany | Applicant |
| US5701294(A) | 1997-12-01 | Ward et al. | Applicant |
| US5706428(A) | 1998-01-01 | Boer et al. | Applicant |
| US5717689(A) | 1998-02-01 | Ayanoglu | Applicant |
| US5727142(A) | 1998-03-01 | Chen | Examiner |
| US5745483(A) | 1998-04-01 | Nakagawa et al. | Applicant |
| US5774876(A) | 1998-06-01 | Wooley et al. | Applicant |
| US5781540(A) | 1998-07-01 | Malcolm et al. | Applicant |
| US5787080(A) | 1998-07-01 | Hulyalkar et al. | Applicant |
| US5794154(A) | 1998-08-01 | Bar-On et al. | Applicant |
| US5796732(A) | 1998-08-01 | Mazzola et al. | Applicant |
| US5796741(A) | 1998-08-01 | Saito et al. | Applicant |
| US5805593(A) | 1998-09-01 | Busche | Applicant |
| US5805842(A) | 1998-09-01 | Nagaraj et al. | Applicant |
| US5805977(A) | 1998-09-01 | Hill et al. | Applicant |
| US5809518(A) | 1998-09-01 | Lee | Applicant |
| US5822309(A) | 1998-10-01 | Ayanoglu et al. | Applicant |
| US5844905(A) | 1998-12-01 | McKay et al. | Applicant |
| US5845097(A) | 1998-12-01 | Kang et al. | Applicant |
| US5857084(A) | 1999-01-01 | Klein | Applicant |
| US5870350(A) | 1999-02-01 | Bertin et al. | Applicant |
| US5877724(A) | 1999-03-01 | Davis | Applicant |
| US5881095(A) | 1999-03-01 | Cadd | Applicant |
| US5881372(A) | 1999-03-01 | Kruys | Applicant |
| US5886992(A) | 1999-03-01 | Raatikainen et al. | Applicant |
| US5896561(A) | 1999-04-01 | Schrader et al. | Applicant |
| US5903559(A) | 1999-05-01 | Acharya et al. | Applicant |
| US5909651(A) | 1999-06-01 | Chander et al. | Applicant |
| US5936953(A) | 1999-08-01 | Simmons | Applicant |
| US5943322(A) | 1999-08-01 | Mayor et al. | Applicant |
| US5987011(A) | 1999-11-01 | Toh | Applicant |
| US5987033(A) | 1999-11-01 | Boer et al. | Applicant |
| US5991279(A) | 1999-11-01 | Haugli et al. | Applicant |
| US6028853(A) | 2000-02-01 | Haartsen | Applicant |
| US6029217(A) | 2000-02-01 | Arimilli et al. | Applicant |
| US6034542(A) | 2000-03-01 | Ridgeway | Applicant |
| US6044062(A) | 2000-03-01 | Brownrigg et al. | Applicant |
| US6047330(A) | 2000-04-01 | Stracke, Jr. | Applicant |
| US6052594(A) | 2000-04-01 | Chuang et al. | Applicant |
| US6052752(A) | 2000-04-01 | Kwon | Applicant |
| US6064626(A) | 2000-05-01 | Stevens | Applicant |
| US6067291(A) | 2000-05-01 | Kamerman et al. | Applicant |
| US6073005(A) | 2000-06-01 | Raith et al. | Applicant |
| US6078566(A) | 2000-06-01 | Kikinis | Applicant |
| US6104712(A) | 2000-08-01 | Robert et al. | Applicant |
| US6108738(A) | 2000-08-01 | Chambers et al. | Applicant |
| US6115580(A) | 2000-09-01 | Chuprun et al. | Applicant |
| US6122690(A) | 2000-09-01 | Nannetti et al. | Applicant |
| US6130881(A) | 2000-10-01 | Stiller et al. | Applicant |
| US6132306(A) | 2000-10-01 | Trompower | Applicant |
| US6147975(A) | 2000-11-01 | Bowman-Amuah | Applicant |
| US6163699(A) | 2000-12-01 | Naor et al. | Applicant |
| US6178337(B1) | 2001-01-01 | Spartz et al. | Applicant |
| US6192053(B1) | 2001-02-01 | Angelico et al. | Applicant |
| US6192230(B1) | 2001-02-01 | Van Bokhorst et al. | Applicant |
| US6208870(B1) | 2001-03-01 | Lorello et al. | Applicant |
| US6223240(B1) | 2001-04-01 | Odenwald et al. | Applicant |
| US6240294(B1) | 2001-05-01 | Hamilton et al. | Applicant |
| US6246875(B1) | 2001-06-01 | Seazholtz et al. | Applicant |
| US6249516(B1) | 2001-06-01 | Brownrigg et al. | Applicant |
| US6275707(B1) | 2001-08-01 | Reed et al. | Applicant |
| US6285892(B1) | 2001-09-01 | Hulyalkar | Applicant |
| US6304556(B1) | 2001-10-01 | Haas | Applicant |
| US6304973(B1) | 2001-10-01 | Williams | Examiner |
| US6321337(B1) | 2001-11-01 | Reshef et al. | Applicant |
| US6327300(B1) | 2001-12-01 | Souissi et al. | Applicant |
| US6341309(B1) | 2002-01-01 | Vaid et al. | Examiner |
| US6349091(B1) | 2002-02-01 | Li | Applicant |
| US6349210(B1) | 2002-02-01 | Li | Applicant |
| US6363065(B1) | 2002-03-01 | Thornton et al. | Applicant |
| US6584508(B1) | 2003-06-01 | Epstein et al. | Examiner |
| US6754188(B1) | 2004-06-01 | Garahi et al. | Examiner |
| US6925069(B2) | 2005-08-01 | Koos et al. | Examiner |
| US7072650(B2) | 2006-07-01 | Stanforth | Examiner |
| US2001/0053699(A1) | 2001-12-01 | McCrady et al. | Applicant |
| US2002/0078377(A1) | 2002-06-01 | Chang et al. | Examiner |
| US2002/0120755(A1) | 2002-08-01 | Gomes et al. | Examiner |
| CA2132180 | 1996-03-01 | Applicant | |
| EP513841(A2) | 1992-11-01 | Applicant | |
| EP627827(A2) | 1994-12-01 | Applicant | |
| EP924890(A2) | 1999-06-01 | Applicant | |
| FR2683326 | 1993-07-01 | Applicant | |
| WO9608884 | 1996-03-01 | Applicant | |
| WO9724005 | 1997-07-01 | Applicant | |
| WO9839936 | 1998-09-01 | Applicant | |
| WO9912302 | 1999-03-01 | Applicant | |
| WO34932 | 2000-06-01 | Applicant | |
| WO110154 | 2001-02-01 | Applicant | |
| WO133770 | 2001-05-01 | Applicant | |
| WO135567 | 2001-05-01 | Applicant | |
| WO137481 | 2001-05-01 | Applicant | |
| WO137482 | 2001-05-01 | Applicant | |
| WO137483 | 2001-05-01 | Applicant | |
| WO235253 | 2002-05-01 | Applicant |
Non-Patent Literature (18)
- Wong et al., “Soft Handoffs in CDMA Mobile Systems”, Dec. 1997, IEEE Personal Communications.Applicant
- Wong et al., “A Pattern Recognition System for Handoff Algorithms”, Jul. 2000, IEEE Journal on Selected Areas in Communications, vol. 18, No. 7.Applicant
- Andras G. Valko, “Cellular IP: A New Approach to Internet Host Mobility”, Jan. 1999, ACM Computer Communication Review.Applicant
- Richard North, Dale Bryan and Dennis Baker, “Wireless Networked Radios: Comparison of Military, Commercial, and R&D Protocols”, Feb. 28-Mar. 3, 1999, 2nd Annual UCSD Conference on Wireless Communications, San Diego CA.Applicant
- Benjamin B. Peterson, Chris Kmiecik, Richard Hartnett, Patrick M. Thompson, Jose Mendoza and Hung Nguyen, “Spread Spectrum Indoor Geolocation”, Aug. 1998, Navigation: Journal of the Institute of Navigation, vol. 45, No. 2, summer 1998.Applicant
- Josh Broch, David A. Maltz, David B. Johnson, Yih-Chun Hu and Jorjeta Jetcheva, “A Performance Comparison of Multi-Hop Wireless Ad Hoc Network Routing Protocols”, Oct. 25-30, 1998, Proceedings of the 4th Annual ACM/IEEE International Conference on Mobile Computing and Networking.Applicant
- C. David Young, “USAP: A Unifying Dynamic Distributed Multichannel TDMA Slot Assignment Protocol”, 1996.Applicant
- Chip Elliott and Bob Heile, “Self-Organizing, Sef-Healing Wireless Networks”, 2000 IEEE.Applicant
- J.J. Garcia-Luna-Aceves and Asimakis Tzamaloukas, “Reversing the Collision-Avoidance Handshake in Wireless Networks”, 1999.Applicant
- J.J. Garcia-Luna-Aceves and Marcelo Spohn, “Transmission-Efficient Routing in Wireless Networks Using Link-State Information”, 2001.Applicant
- J.J. Garcia-Luna-Aceves and Ewerton L. Madruga, “The Core-Assisted Mesh Protocol”, Aug. 1999, IEEE Journal on Selected Areas in Communications, vol. 17, No. 8.Applicant
- Ad Kamerman and Guido Aben, “Net Throughput with IEEE 802.11 Wireless LANs”, IEEE, 2000.Applicant
- J.R. McChesney and R.J. Saulitis, “Optimization of an Adaptive Link Control Protocol for Multimedia Packet Radio Networks”, MILCOM, 1999.Applicant
- Ram Ramanathan and Regina Rosales-Hain, “Topology Control of Multihop Wireless Networks using Transmit Power Adjustment”, IEEE, 2000.Applicant
- Ram Ramanathan and Martha E. Steenstrup, “Hierarchically-Organized, Multihop Mobile Wireless Networks for Quality-of-Service Support”, 1998.Applicant
- Martha E. Steenstrup, “Dynamic Multipoint Virtual Circuits for Multimedia Traffic in Multihop Mobile Wireless Networks”, 1999.Applicant
- Zhenyu Tang and J.J. Garcia-Luna-Aceves, “Collision-Avoidance Transmission Scheduling for Ad-Hoc Networks”, IEEE ICC, 2000.Applicant
- George Vardakas and Wendell Kishaba, “QoS Networking With Adaptive Link Control and Tactical Multi-Channel Software Radios”, IEEE MILCOM, 1999.Applicant