Data network having a wireless local area network with a packet hopping wireless backbone

A wireless local area network (LAN) for data communications. The wireless LAN includes a packet hopping access terminal (PHAST) and a packet hopping gateway (PHG). The PHAST has a first transceiver for wirelessly communicating with a client device, and a second transceiver for wirelessly receiving data packets addressed to the client device and for wirelessly transmitting data packets received from the client device in accordance with a packet hopping protocol. The PHG has a transceiver for wirelessly receiving the data packets transmitted by the PHAST and for transmitting the data packets addressed to the client device in accordance with the packet hopping protocol, and a network interface for establishing communication with a server.

TECHNICAL FIELD

The present invention relates generally to the field of computer networking and, more particularly, to a wireless, packet hopping network that includes access points that wirelessly communicate with a gateway.

BACKGROUND

A pervasive trend in modern computing is to network multiple computing devices to one another so that the computing devices can share data in an electronic format. Computing devices that can be networked include, for example, fixed location computers (e.g., desktop computers and workstations), portable computers (e.g., laptop or notebook computers and personal digital assistants (PDAs)), input/output (I/O) devices (e.g., printers, scanners, and digital senders). However, the networked devices can also include devices that exchange voice data (e.g., mobile telephones or handheld radios).

Another trend in the networking of computing devices is to provide wireless data exchange between a client device and an access point. Multiple access points can be networked together to form a wireless local area network (WLAN). More specifically, the access points (also referred to as wireless access points, or WAPs) communicate via a hard wired infrastructure using a series of hubs and/or switches that are interconnected to form a local area network (LAN). Various servers (e.g., a web server, an e-mail server, a print server, a database server, a file server, and so forth) can be coupled to the LAN via one or more of the hubs and/or switches.

With reference toFIG. 1, a typical conventional network10that includes wireless communication to one or more client computing devices12is illustrated. The client computing devices12are provided with a communications protocol that can be executed by a processor of the computing device12and/or by dedicated communications hardware (e.g., a transceiver) coupled to the client computing device12. The communications hardware can include an antenna14. The antennas14exchange signals with the WAPs16. The WAPs16execute a communications protocol corresponding to the communication protocol executed by the client devices12. The WAPs16also include communications hardware (e.g., a transceiver with an antenna18) for broadcasting signals to the client devices12and receiving signals broadcast by the client devices12.

Each WAP16is placed in communication with a switch or, as illustrated, a hub20via a physical hard wired connection22. Each hub20is hard wired to at least one other hub20via a physical wired connection24. For example, the hubs20can be arranged in a hierarchical structure, a token ring configuration and so forth. It is noted that the hard wired connections22and24can be electrically conductive wires (e.g., twisted pair or coaxial cable) or can be another conductor medium (e.g., fiber optic cable). The hubs20, the WAPs16and the hardwired connections22and24make up a wired LAN30.

Various servers26and/or a network manager terminal28can be coupled to the wired LAN30via one or more of the hubs20. The wired LAN30can also be coupled to an external, or public network32(e.g., the Internet) via a firewall34. The firewall34provides information technology security between the external network32and the wired LAN30.

Although the conventional network10illustrated inFIG. 1is effective for exchanging data packets between the client computing devices12and the servers26, the conventional network10has at least two disadvantages. First, the hard wired connections22and24are difficult, time consuming and expensive to install. In a hard wired network, cables must be strung throughout a facility (e.g., a building). Wiring the network can include passing wires through walls, floors, above suspended ceilings panels, below raised floor panels, and so forth. Such installation work can prove difficult during construction of a new building and even more difficult in an existing building, especially in existing buildings that were built before computer networks were considered in the architectural plan.

A second disadvantage of the conventional network10is that information security of the conventional network10can be compromised if an unscrupulous user of a client device12establishes communication with one of the WAPs16. Such a client device12would be located on the local side of the firewall34and, assuming that the client device12has obtained proper authentication, can access various other devices on the local side of the firewall34, including the servers26.

Accordingly, there exists a need in the art for a communications network that reduces its reliance on hard wired connections and has enhanced security.

SUMMARY OF THE INVENTION

According to one aspect of the invention, the invention is a wireless local area network (LAN) for data communications. The wireless LAN includes a packet hopping access terminal and a packet hopping gateway. The packet hopping access terminal has a first transceiver for wirelessly transmitting data packets addressed to a client device and for wirelessly receiving data packets from the client device, and a second transceiver for wirelessly receiving the data packets addressed to the client device and for wirelessly transmitting the data packets received from the client device in accordance with a packet hopping protocol, the packet hopping protocol including a data packet router/repeater function. The packet hopping gateway has a third transceiver for wirelessly receiving the data packets transmitted by the packet hopping access terminal and for wirelessly transmitting the data packets addressed to the client device in accordance with the packet hopping protocol, and a network interface for establishing communication with a server.

According to another aspect of the invention, the invention is a data communications network. The data communications network includes a packet hopping gateway (PHG) and at least one packet hopping access terminal (PHAST). The PHG includes a network interface for establishing communication with a server via a wide area network backbone and a transceiver for wirelessly receiving data packets originating from a client device and addressed to the server and wirelessly transmitting data packets originating from the server and addressed to the client device in accordance with a packet hopping protocol. The PHG is operatively arranged to dynamically configure a virtual private network between a firewall and the client device as the client device initiates communication with the data communications network, the firewall disposed between the wide area network backbone and the server. The at least one PHAST includes at least one transceiver operative arranged to act as an intermediate transmission node for the data packets sent from the client device to the server and the data packets sent from the server to the client device. The at least one PHAST is operatively arranged to route/repeat the data packets sent from the client device to the server and the data packets sent from the server to the client device in accordance with the packet hopping protocol.

According to yet another aspect of the invention, the invention is a wireless local area network (LAN) for data communications. The wireless LAN includes a plurality of packet hopping access terminals (PHASTs) and a packet hopping gateway (PHG). Each PHAST includes a local transceiver for wirelessly transmitting data packets addressed to an associated client device and for wirelessly receiving data packets from the associated client device; and a first switchable LAN transceiver for wirelessly receiving the data packets addressed to the associated client device and for wirelessly transmitting the data packets received from the associated client device to one of another PHAST and the PHG using a point-to-point protocol. The PHG includes a second switchable LAN transceiver for wirelessly receiving the data packets transmitted by any of the PHASTs and for wirelessly transmitting each data packet addressed to the associated client devices to a selected PHAST using a point-to-point protocol; and a network interface for establishing communication with a server.

DISCLOSURE OF INVENTION

In the detailed description that follows, similar components have been given the same reference numerals, regardless of whether they are shown in different embodiments of the present invention. To illustrate the present invention in a clear and concise manner, the drawings may not necessarily be to scale and certain features may be shown in somewhat schematic form.

Referring toFIG. 2, a network50according to the present invention is illustrated. The network50includes a wireless local area network (LAN)52. The wireless LAN52is coupled to a wide area network (WAN) backbone54. The WAN backbone54can represent, for example, an Ethernet or any other suitable wide area network infrastructure. In one example, the WAN backbone54includes a fiber optic medium with a bandwidth of 10 Gbps or higher.

The network50also includes a private LAN55coupled to the WAN backbone54via a firewall56. The private LAN55(sometimes referred to as a corporate LAN since the private LAN often provides core computing services to a corporate or other organized entity) can include various servers58. The servers58can include, for example, a world-wide-web server (also known as a “web” server or an Internet server), a database server, a file server, an electronic mail (“e-mail”) server, a print server and so forth. As one skilled in the art will appreciate, the illustration of a file server, an e-mail server and a database server is merely exemplary and other servers58can be coupled in similar fashion. As used herein, the term server refers to both hardware and software that performs a service, such as hosting web pages that can be viewed from another computing device using a browser, executing applications to carry out computing tasks for other computing devices, providing a centralized location for shared files, controlling the rendering of print files for printers coupled to the network50, and so forth. The private LAN55may also include a network manager terminal60which allows a network administrator to establish and control functionality of the private LAN55and/or the wireless LAN52, and, if appropriate, other portions of the network50, such as the firewall56and/or the WAN backbone54.

The private LAN55can be coupled to the WAN backbone54via the firewall56. As is known in the art, the firewall56provides information technology security to the network50. That is, the firewall56minimizes the possibility of unauthorized access of the server58and/or network manager terminal60from devices connecting through the WAN backbone54. In addition, the firewall56may be configured to minimize the exportation of data from one or more of the servers58and/or the network manager terminal60. Also, additional computing devices, workstations and servers can be coupled to the network50on either a “secure” (or private) side of the firewall56or a “public” side of the firewall56. In the illustrated arrangement, devices illustrated on the left side of the firewall56inFIG. 2are located in a public area and devices illustrated on the right side of the firewall56inFIG. 2(e.g., the private LAN55) are located in a private or secure area.

Also coupled to the WAN backbone54can be an external network (or networks)62. For example, the external network can be the Internet or any other wide area network (WAN).

The wireless LAN52is configured to allow client computing devices64to exchange data with the devices of the private LAN55(e.g., the servers58and/or network manager terminal60) via the firewall56and WAN backbone54. The client computing devices64can include various types of computers (e.g., general purpose machines that processes data according to a set of instructions). Most computers include a memory (which can include one or more volatile memory components and one or more nonvolatile memory components) for storing logic instructions and a processor (or processors) for executing those logic instructions. Therefore, the client devices64can include general purpose computers such as desktop computer systems, workstations, terminals, laptop or notebook computers, personal digital assistants (PDAs), and so forth. In addition, the client devices64can include peripheral devices or other computer equipment, including, for example, input/output devices such as image rendering equipment (e.g., printers, plotters, copy machines, etc.), scanners, digital senders, and so forth. In one embodiment, the client devices64can also include devices that exchange voice data (e.g., mobile telephones or handheld radios).

The client devices64can communicate with the servers58, or with one another, by exchanging data packets. The data packets, as is known in the art, contain a message in electronic format along with header information used in delivering the data packet and ensuring the integrity of the data packet. A relatively large message can be broken down into multiple data packets depending on the “payload” capacity of the data packets. However, it should be noted that the invention is not correspondingly limited in scope and for the purposes herein, the term data packet can include other types of data or information exchanges including, for example, video signals, audio signals, and any other type of information-containing signal broadcast to or from the client devices64.

The wireless LAN52includes a wireless packet hopping network66(also referred to herein as a wireless packet hopping backbone for the wireless LAN52) that includes at least one packet hopping access terminal (PHAST)68and at least one packet hopping gateway (PHG)70. The client devices64communicate with the servers58via the wireless packet hopping LAN66, the WAN backbone54and the firewall56. More detailed operation of the PHAST device68and the PHG70will be described in greater detail below.

Each client device64can include a connectivity device, or transceiver72, for wireless, bidirectional communications with at least one of the PHAST devices68and/or the PHG70. For example, the transceiver72can be a network interface card (NIC) and associated antenna74. In one embodiment, the NIC can operate using a communications protocol such as an 802.11b standard protocol.

Referring briefly toFIG. 4, each PHAST device68includes a corresponding connectivity device for wireless, bidirectional data packet exchange with the client devices64. The corresponding connectivity device in the PHAST devices68can be a local transceiver. The local transceiver of the PHAST device68can include, for example, an interface card76(e.g., a standard 802.11b NIC card) and an associated antenna78.

As indicated, the client devices64can also wirelessly communicate directly with the PHG70. Referring briefly toFIG. 5, the PHG70can also be provided with a connectivity device for wireless, bidirectional communications with the client devices64. The corresponding connectivity device in the PHG70can be a local transceiver. The local transceiver of the PHG70can include, for example, an interface card80(e.g., a standard 802.11b NIC card) and an associated antenna82.

In general, each client device64communicates with a nearby PHAST device68according to a predetermined protocol for managing wireless communications. In most situations, the client devices64will communicate with the PHAST device68that is closest in proximity to the client device64, or with the PHAST device68with which the signal strength is the highest. Should the client device64be located closest to the PHG70, or share the highest signal strength with the PHG70, the client device64can exchange data packets directly with the PHG70instead of communicating with one of the PHAST devices68.

Upon receiving a data packet form a client device64, each PHAST68will wirelessly retransmit (e.g., route/repeat) the data packet for delivery to the PHG70. As indicated, the PHAST devices68handles communications from the client devices64to the PHG70using a packet hopping technique. Similarly, data packets intended for delivery to a client device64and received from the WAN backbone54by the PHG70are transmitted through the wireless packet hopping LAN66using the packet hopping technique. It is noted that communications directly between the client devices64and the PHG70need not be routed through any of the PHAST devices68.

Briefly, the concept of packet hopping relates to the delivery of one or more data packets from a source to a destination via one or more intermediate stations. Features of the packet hopping protocol described herein are sometimes referred to in the art as ad hoc networking or ad hoc routing. In the illustrated embodiment, the client devices64can act as a source or destination and the PHG70acts as the corresponding destination or source. In the wireless LAN52, the PHAST devices68function as the intermediate points.

The packet hopping technique can be implemented by a packet hopping protocol executed by the devices of the wireless LAN52. The packet hopping protocol can include various networking features, such as a self-configuring features (also referred to as a self-discovery feature or a self-forming feature) where devices contained within the wireless LAN52determine the presence and functionality of the other devices contained within the wireless LAN52. Upon discovery of the other devices (e.g., by tracking the transmission of data packets and acknowledgment signals), the packet hopping protocol can efficiently deliver data packets through the wireless LAN52. Efficient delivery of data packets can include sending data packets through a minimum number of intermediate points (i.e., PHAST devices68) before reaching an intended destination and using self-healing functionality (e.g., delivery of data packets to avoid congested nodes, compensate for a device that has lost power or otherwise is malfunctioning, etc.). The self configuring nature of the wireless LAN52allows for easy installation of the wireless LAN52since databases of logical device location and capabilities can be self populating and need not be configured by a network installer.

Once discovered, the components of the wireless packet hopping LAN66(the PHAST devices68and/or the PHG70) maintain information indicating the network locations of each client device64, or the PHAST device68or PHG70that each client device64is in direct communication with. It is noted that the functionality described herein is in the context of data communications between the client device64and the servers58or the network manager60. However, peer-to-peer (i.e., client device64to client device64) communications can be handled in the same manner (i.e., using the same packet hopping protocol).

Data packets received from the client device64by a particular PHAST68will be routed to the PHG70(for delivery to the appropriate server58) using an available pathway through the wireless packet hopping LAN66. For example, if the subject PHAST device68that receives the data packet from the client device64is within direct communication proximity with the PHG70, the subject PHAST device68can wirelessly transmit the received data packet directly to the PHG70. However, routing of the data packet to the PHG70via an additional PHAST device(s)68is contemplated, as depending on wireless LAN architecture, load, interference, etc.

Referring briefly toFIG. 4, transmission of a data packet from the PHAST device68to the PHG70or another PHAST device68can be carried out using a connectivity device such as a LAN transceiver. The LAN transceiver can also be configured to receive data packets from the PHG70or other PHAST devices68. The LAN transceiver can include, for example, an interface card84(e.g., a standard 802.11a NIC) and an associated antenna86. Referring briefly toFIG. 5, the PHG70is also provided with a corresponding connectivity device to receive data packets transmitted by the PHAST devices68and to transmit data packets to the PHAST devices68. The connectivity device of the PHG70can be a LAN transceiver, such as an interface card88(e.g., a standard 802.11a NIC) and associated antenna90.

In situations where the PHAST device68that receives data packets from the client device64is outside direct communications proximity with the PHG70, the data packets are forwarded to the PHG70via one or more of the other PHAST devices68in the wireless packet hopping LAN66. Depending on LAN66usage, buffer resources, external interference, signal strength and so forth, the packet hopping protocol determines a path for the data packet from the receiving PHAST device68to the PHG70(e.g., self-conforming functionality). As should be apparent, the delivery of data packets through the wireless LAN52, and specifically the wireless packet hopping LAN66is carried out to make efficient use of the resources contained therein and to ease installation of the wireless LAN52. The wireless packet hopping LAN66is logically configured as a “mesh,” with no set delivery path for data packets. Data packets can be delivered through the wireless packet hopping LAN66by “hopping” (or skipping) one or more PHAST devices68, even if the “hopped” device(s) is physically closer that the next device addressed to receive the data packet.

Without intending to be bound by theory, packet hopping is an efficient technique for re-transmitting data packets form a source to a destination through a series of intermediate points. An exemplary packet hopping protocol is available from MeshNetworks of 485 North Keller Road, Suite 250, Maitland, Fla. 32751 under the designation “MeshLAN” and under the designation “MultiHopping.” The protocol available from MeshNetworks transforms wireless LAN cards (e.g., a standard 802.11 card) into a router/repeater to enhance the wireless reach of each subscriber (e.g., a client device64) in the network.

In one implementation, the packet hopping protocol executed by the PHAST devices68and the PHG70adds multi-hopping peer-to-peer (e.g., PHAST device68to PHAST device68or PHAST device68to PHG70) capabilities to off-the-shelf 802.11 cards. Such a packet hopping protocol can automatically shift transmissions from congested access points (i.e., PHAST devices68) to uncongested ones to ease bottlenecks with the LAN and to improve overall network performance.

The transmission of data packets from the PHG70to the client devices64is carried out in the same manner, but in reverse direction. More particulary, if the destination client device64is in direct communication proximity to the PHG70, the data packets will be transmitted to the client device64via the local transceiver (e.g., interface card80and antenna82). If the destination client device64is in communication with one of the PHAST devices68, the data packet is transmitted by the PHG70via the LAN transceiver (e.g., the interface card88and antenna90) and routed through the wireless packet hopping LAN66to the desired PHAST device68using the packet hopping protocol. Once the desired PHAST device68receives the data packet, the data packet is transmitted to the client device64via the local transceiver of the PHAST device68.

The configuration of the wireless LAN52allows for the wireless LAN52to be installed with relative ease in buildings of all types, including new construction and old buildings that were built with or without consideration for the networking of computing devices. The wireless LAN52can be deployed, for example, in an office environment where the PHAST devices68are placed strategically throughout the facility to interact with nearby client devices64and to relay data packets to and from the PHG70. The PHG70can be located in an appropriate proximity to the WAN backbone54to that connection thereto can be established.

It is noted that the PHAST devices68and the PHG70will typically require a power source. In one embodiment, the PHAST devices68and the PHG70are connected to an available standard power source such as a conventional power outlet (e.g., in the United States, a 110 volt, 60 Hertz power source). In another embodiment, the PHAST devices68can be provided with their own power source such as a battery pack or solar power cell.

Since the PHAST devices68are not coupled to one another or to the PHG70with any hard-wired connections, the PHAST devices68can be quickly and easily deployed in desired locations without the need to run cables through walls, ceilings, floors and so forth. It should be apparent to one skilled in the art, that installation of the wireless packet hopping LAN66will result in a large time and economic savings. It is also noted that with the use of appropriate wireless transceivers and protocols, that no line of sight configuration is needed between the client devices64and the PHAST devices68, between one PHAST device68and the other PHAST devices68, or between the PHAST devices68and the PHG70.

In one embodiment of the invention where 802.11b interface cards are used for communication between the client devices64and the PHAST devices68(or PHG70), the bandwidth between the client devices64and the PHAST devices68(or PHG70) can be approximately 11 Mbps. In an alternative configuration, the example the exemplary 802.11b interface card can be replaced with an 802.11g interface hardware and/or software. When 802.11a interface cards are used for communication among the PHAST devices68and the PHG70, the bandwidth between each PHAST device68and the other PHAST devices68and/or the PHG70can be approximately 100 Mbps. As one skilled in the art will appreciate, the foregoing interface connection standards (e.g., the use of 802.11) and bandwidths are exemplary and can vary as different hardware and communication protocols are selected for these communication links.

With additional reference toFIG. 3, an expanded data communications network50′ is illustrated. Similar to the network50ofFIG. 2, the network50′ is provided with a WAN backbone54, a first private LAN55a(including a firewall56a, various servers58a, and a network manager workstation60a) and a connection to an external network62(e.g., the Internet) via the WAN backbone54. The expanded network50′ also includes multiple wireless LANs designated by reference numerals52athrough52n. Optionally, the network50′ can include at least one additional private LAN55(illustrated as a second private LAN55bthat includes a firewall56b, various servers58band a network manager workstation60b).

The multiple wireless LANs52are used to provide connectivity for a large number of client devices64and/or throughout a physically large facility. For example, one of the wireless LANs52may be used to provide data networking for one floor of an office building or for a section of an office building that could span across more than one floor (e.g., a wing of a building). To increase the number of wireless LANs52that can be coupled to the WAN backbone54a multiplexing device, such as an Ethernet switch92, can be used to couple one or more PHGs70to the WAN backbone54.

Each wireless LAN52athrough52ncan operate using different channels and/or frequencies to minimize interference from one wireless LAN52to an adjacent wireless LAN52. However, a channel or frequency can be used by one of the LANS52and the same channel or frequency can be used by another of the LANs52when the another of the LANs52is located sufficiently far enough from the first LAN52to avoid interference.

In one embodiment, the client devices64of each of the wireless LANs52athrough52npresent in the network50′ can communicate with the devices (e.g., the servers58aand58b) of multiple private LANs55aand55b(or, if present, additional private LANs55). In an alternative arrangement, the client devices64of each wireless LAN52athrough52nare limited to communication with a corresponding private LAN55aor55b(or, if present, additional private LANs55). For instance, a landlord of a building in which the network50′ is deployed may provide the WAN backbone54. Multiple tenants could use the WAN backbone54to form the network50′ by each tenant establishing at least one wireless LAN52and at least one private network55.

Referring now toFIG. 4, an example embodiment of one of the PHAST devices68is schematically illustrated in greater detail. As indicated above, the PHAST device68includes a first wireless connectivity device (e.g., a local transceiver) for communicating with client devices64and a second wireless communications device (e.g., a LAN transceiver) for wirelessly communicating with other PHAST devices68and/or the PHG70. In one embodiment, the local transceiver includes the interface card76(e.g., a standard 802.11b NIC) and associated antenna78. In one embodiment, the LAN transceiver includes the interface card84(e.g., a standard 802.11a NIC) and associated antenna86.

The PHAST device68also includes components for executing logic instructions for facilitating the data communications described herein. For example, the PHAST devices68can include circuitry94(e.g., a processor) that executes code containing the logic instructions. The PHAST device68can also include memory for storing the code/logic instructions. One skilled in the art will appreciate that multiple processors and/or memory components can be used for such purposes. In addition, all or a portion of such functionality can be implemented as part of the interface card76and/or interface card84.

The PHAST device68can execute a wireless access point (WAP) protocol96and a packet hopping protocol98. The WAP protocol96is responsible for managing and maintaining communications between the PHAST device68and the client devices64. WAP protocols96are generally well known in the art and will not be described in greater detail. Briefly, the WAP protocol96allows the PHAST68to function as an access point for the client devices64. The WAP protocol96can be executed directly by the interface card76. The packet hopping protocol98, as indicated above, manages the exchange of data packets among the PHAST devices68and between the PHAST device68and the PHG70. The packet hopping protocol98can be executed directly by the interface card84.

In an alternative embodiment of the PHAST68, the local and LAN network transceivers can be implemented with the same hardware (e.g., the same interface card and antenna) and/or can share protocol functionality. In another example, the local and LAN networks can use the same frequency channel, but operate using different protocols, or vice versa (share the same protocol, but use different frequency channels).

Referring now toFIG. 5, an example embodiment of the PHG70is illustrated in greater detail. As indicated above, the PHG70can include a device (e.g., a local transceiver) circuit for wirelessly communicating directly with one or more client devices64. Such a transceiver can include an interface card80(e.g., a standard 802.11b NIC) and an associated antenna82. The PHG70also includes a communications device (e.g., a LAN transceiver) for establishing wireless communications with PHAST devices68of the wireless LAN52. Such a LAN transceiver can include the interface card88(e.g., a standard 802.11a NIC) and the associated antenna90. In addition, the PHG70can include an interface device99, such as a network interface card, for communicating with the WAN backbone54

In an alternative embodiment of the PHG70, the local and LAN network transceivers can be implemented with the same hardware (e.g., the same interface card and antenna) and/or can share protocol functionality. In another example, the local and LAN networks can use the same frequency channel, but operate using different protocols, or vice versa (share the same protocol, but use different frequency channels).

Similar to the PHAST device68, the PHG70can include circuitry100(e.g., a processor) for executing code to maintain and manage data communications with the client devices64and the PHAST devices68. For example, the circuitry100can include a processor or processors and a memory or memories for respectively executing and storing code containing the logic instructions. As one skilled in the art will appreciate, the execution and/or storage of such code can be implemented by the interface cards80and/or88, or by general purpose components.

The PHG70can execute protocols having a variety of functions. For example, the PHG70can execute a WAP protocol102, a packet hopping protocol104, various network management modules106and a virtual private network (VPN) protocol108. Similar to the WAP protocol96, the WAP protocol102manages communications with client devices64via the PHG's local transceiver (e.g., the interface card80and antenna82) such that the PHG70can Function as a wireless access point for client devices64. As one skilled in the art will appreciate, the WAP protocol96and102contain functionality for opening and maintaining data communication sessions between the client devices64and the PHAST devices68or the PHG70.

Similar to the packet hopping protocol98, the packet hopping protocol104maintains and manages the exchange of data packets between the PHG70and the PHAST devices68via the LAN transceiver (e.g., the interface card88and associated antenna90). The packet hopping protocols98and104contain functionality for opening and maintaining sessions among the PHAST devices68and between the PHAST devices68and the PHG70. As indicated, the packet hopping protocols98and104provide a router/repeater function such that data packets transmitted by a client device64to a PHAST device68are relayed to the PHG70(for ultimate delivery to the appropriate sever58) or another client device64in an efficient manner. Similarly, data packets addressed for delivery to the client devices64are transmitted through the wireless packet hopping LAN66. Such delivery of data packets can include directing the data packets through one or more PHAST devices68according to the packet hopping protocol.

Additional logic can be executed by the PHG70to establish communications with other network50components (e.g., the servers58, the network manager60) via the network interface device99and WAN backbone54.

The network management functions106can include, for example, a domain name service (DNS). The DNS maintains a database of devices by name (in some networks, the names can be domain names) and logical addresses (in some networks, the addresses can be IP addresses). The network management functions106can also include a dynamic host configuration protocol (DHCP) that, in conjunction with the DNS, assigns addresses to the client devices64upon log-in to the wireless LAN52. The DHCP functions to minimize the need to manually and/or permanently assign addresses to each device. Rather, the DHCP assigns an address from a pool of addresses to each client device64and/or each PHAST device68upon connection to the wireless LAN52in a dynamic fashion. The DHCP dynamically updates the DNS following any changes to the assigned addresses for each device. The information stored by the DNS may also be transmitted to the PHAST devices68to assist in the efficient handling of data packets through the LAN52. Additional network information used by the PHG70and the PHAST devices68can include the “location” of each client device64(the “location” being the PHAST device68or the PHG70with which the client device64communicates). Alternatively, the DHCP can be arranged statically such that each device on the network has an assigned address that does not change from log-in to log-in (also referred to as start up to start up) with the network.

The network management functionality106can also include a directory service (such as a light weight directory protocol (LDAP)) to assist other devices (e.g., the PHAST devices68) in the access a directory listings stored by the PHG70. Such a network management function would allow devices in the network50to query a directory stored by the PHG to provide a common method of searching for network50configuration information (e.g., domain names, addresses, etc.).

The network management functionality106can also include a simple network management protocol (SNMP) for monitoring and controlling the wireless LAN52. In a typical network (e.g., the network10ofFIG. 1) that runs SNMP, data concerning the activity of each network device (e.g., the hubs20, the WAPs16, and other devices that are apart of the network10, such as bridges, routers, etc.) are transmitted to a network manager terminal (e.g., the network manager28) that oversees the network. The network manager terminal executes an agent which assembles information for a management information base (MIB) that contains a data structure of obtainable functionality for each device deployed in the network, as well as the identify of the functions that can be controlled by the network manager terminal.

According to one embodiment of the present invention, the foregoing functionality of a network control workstation can be carried out by the PHG70as part of the network management functions106of the wireless LAN52. In this embodiment, a MIB and complete SNMP are stored and executed on the PHG70. Thus, these tasks are removed from a separate device (e.g., the network manager60). In addition, the DNS, DHCP and LDAP functions can be hosted by the PHG70and removed from another device (e.g., the network manager60). Accordingly, control over the wireless LAN52is centralized in the PHG70. Hosting these functions in the PHG70reduces the tasks required to be carried out by the network manager60and reduces the amount of information that needs to be transmitted over the WAN backbone54and through the firewall56. In the expanded communications network50′, each PHG70hosts the network management functions106for each corresponding wireless LAN52. Therefore, the processing associated with network management can be distributed to reduce the processing burden of the network manager60and reduce the traffic over the WAN backbone54. The network manager functions106can also include additional tasks such as provisioning, administration, traffic control, statistics, billing, and so forth.

The wireless LAN52provides flexibility in the physical location of the client devices64without the need for reconfiguring the client device64or the network50if one of the client devices64moves from one location in the wireless LAN52to another location, or to another wireless LAN52(FIG.3). For example, a person using a laptop computer in their office may regularly communicate with one particular nearby PHAST device68. However, that person may take their laptop computer to a meeting room that could be located in close proximity to a different PHAST device68located within the same wireless LAN52or on a different wireless LAN52. When communication with the network50or50′ is re-established, the network management functions106of the PHG70act to establish a session with the client device64. Such log-in to the wireless LAN52is transparent to the client device64and is without the need for interaction by the user of the client device64.

As indicated above, the wireless LAN52is on a public side of the firewall56. Accordingly, it can be beneficial to provide some level of security for the exchange of data over the wireless LAN52. As part of a security scheme for the network50, the PHG70can be provided with the VPN protocol108. The VPN protocol108is configured to dynamically set up and tear down virtual private networks between the client devices64and the private LAN55(using VPN protocols as interpreted by the client devices64and the firewall56) servers58so that information is exchanged using a security mechanism, such as encryption. In one embodiment, the PHG70brokers and manages the logical encryption link between the client devices64and the firewall56. The firewall56decrypts encrypted data packets sent by the client devices64to the servers58and places corresponding unencrypted data packets on the private LAN55. Similarly, the client devices64decrypts incoming encrypted data packets to make the data packets available for local use by the applications and protocols executed by the receiving client device64.

Traditionally, VPNs involved a logically static connection between a host device and a client device. However, VPN protocol108contemplated herein dynamically configures the VPNs in the network50in a similar way to the way the DHCP assigns addresses to the client devices64. For example, VPN encryption keys can be provided to authorized client devices64at log-in. It is noted that additional security schemes can be added to the client devices64, the wireless LAN52and the network50to minimize security risks when exchanging data between peer client devices64, or with the external network62.

In the foregoing embodiment, the PHG70can be used to assist in establishing the VPN communication links between the client devices64and the firewall56as each client device initiates communication with the wireless LAN52. With additional reference toFIG. 3, an alternative arrangement for coupling a wireless LAN52′ to the private LAN55is illustrated. In this arrangement, the network interface99couples a PHG70′ to the private LAN55. Accordingly, communications between the client devices64of the wireless LAN52′ and the servers58of the private network55are not directed through the WAN backbone54and/or the firewall56. The PHG70′ can be configured to dynamically set up and tear down VPN connections, or logical encryption links, between the client devices64of the wireless LAN52′ and the PHG70′ itself. The PHG7′ decrypts encrypted data packets sent by the client devices64to the servers58and places corresponding unencrypted data packets on the private LAN55. Similarly, the PHG70′ encrypts data packets to be delivered from a device on the private LAN55to one or more of the client devices64.

Although particular embodiments of the invention have been described in detail, it is understood that the invention is not limited correspondingly in scope, but includes all changes, modifications and equivalents coming within the spirit and terms of the claims appended hereto.

For example, the wireless packet hopping LAN66can be implemented using an asynchronous transfer mode (ATM) embodiment where the LAN transceiver and associated packet hopping protocol of each PHAST68and the PHG70is replaced with a point-to-point transceiver. Switches can be deployed at each node (i.e., each PHAST68and the PHG70) to establish the mesh back-haul network arrangement of the wireless packet hopping LAN66described above. In such an embodiment, data packets can be delivered to hop from PHAST68(or PHG70) to PHAST68(or PHG70). However, since ATM protocols are configured in a point-to-point implementation (i.e., the source and the destination of data packet transfer links are static), this modified embodiment may not include the dynamic, self-configuring routing of the packet hopping implementation described above.