Source: http://www.google.com/patents/US20070287390?ie=ISO-8859-1&dq=7069184
Timestamp: 2015-03-31 18:58:15
Document Index: 554038499

Matched Legal Cases: ['art 300', 'art 300', 'art 300', 'art 300', 'art 300', 'art 300']

Patent US20070287390 - Untethered access point mesh system and method - Google PatentsSearch Images Maps Play YouTube News Gmail Drive More »Sign inAdvanced Patent SearchPatentsA technique for implementing an untethered access point (UAP) mesh involves enabling AP-local switching at one or more UAPs of the mesh. A system constructed according to the technique may include a wireless switch; an access point (AP) wire-coupled to the wireless switch; and a UAP mesh, wirelessly...http://www.google.com/patents/US20070287390?utm_source=gb-gplus-sharePatent US20070287390 - Untethered access point mesh system and methodAdvanced Patent SearchPublication numberUS20070287390 A1Publication typeApplicationApplication numberUS 11/801,964Publication dateDec 13, 2007Filing dateMay 11, 2007Priority dateJun 9, 2006Also published asCA2654827A1, CN101501451A, CN101501451B, EP2038609A2, EP2038609A4, EP2038609B1, US8818322, US20140364130, WO2007146274A2, WO2007146274A3, WO2007146275A2, WO2007146275A3Publication number11801964, 801964, US 2007/0287390 A1, US 2007/287390 A1, US 20070287390 A1, US 20070287390A1, US 2007287390 A1, US 2007287390A1, US-A1-20070287390, US-A1-2007287390, US2007/0287390A1, US2007/287390A1, US20070287390 A1, US20070287390A1, US2007287390 A1, US2007287390A1InventorsJames Murphy, Gary Morain, Stan ChesnuttOriginal AssigneeTrapeze Networks, Inc.Export CitationBiBTeX, EndNote, RefManReferenced by (4), Classifications (13), Legal Events (3) External Links: USPTO, USPTO Assignment, EspacenetUntethered access point mesh system and method
BRIEF DESCRIPTION OF THE DRAWINGS Embodiments of the invention are illustrated in the figures. However, the embodiments and figures are illustrative rather than limiting; they provide examples of the invention. FIG. 1 depicts an example of a system including an untethered access point (UAP) mesh. FIG. 2 depicts an example of a subtree of a UAP mesh. FIG. 3 depicts a flowchart of an example of a method for linking a UAP to an an anchoring access point (AAP). FIG. 4 depicts a diagram illustrating a UAP linking to an existing wireless network. FIG. 5 depicts an example of a system including a self-healing UAP mesh. DETAILED DESCRIPTION In the following description, several specific details are presented to provide a thorough understanding of embodiments of the invention. One skilled in the relevant art will recognize, however, that the invention can be practiced without one or more of the specific details, or in combination with other components, etc. In other instances, well-known implementations or operations are not shown or described in detail to avoid obscuring aspects of various embodiments, of the invention. FIG. 1 depicts an example of a system 100 including an untethered access point (UAP) mesh. In the example of FIG. 1, the system 100 includes a network 102, a wireless switch 104, one or more APs 106-1 to 106-N (referred to collectively as APs 106), and a UAP mesh 108. The network 102 may include an Internet protocol (IP) network. In an embodiment, the network 102 is a wired backbone to which the wireless switch 104 is coupled. However, the network 102 may alternatively represent the network, or any other network, to which a backbone network is coupled or which acts as an alternative to a backbone network. Thus, the network 102 could include, for example, the Internet. The wireless switch 104 is typically wire connected to the APs 106. Thus, the �wireless� switch could be thought of, depending upon the implementation, as a switch for wireless traffic to and/or from a wired network. The wireless switch 104 is not necessarily wirelessly connected to anything. Each of the APs 106 could be wire coupled to respective switches such that each switch is wire coupled to only a single AP. So, although the one or more APs 106 is depicted as a plurality in the example of FIG. 1, it should be understood that the number of APs per switch is implementation- and/or embodiment-specific. An AP and the wireless switch 104 could be combined into a single device. However, in this description, the functionality of an AP is differentiated from the functionality of a switch by acting as if the APs and the wireless switches are distinct devices. The wireless switch 104 may or may not have all of the tools to manage wireless stations and the UAP mesh locally. For example, there may be additional management (e.g., AAA servers) further upstream from the wireless switch 104. Since it is not critical where these services take place beyond the wireless switch 104, for illustrative simplicity, it is assumed that the wireless switch 104 handles all of these functions, either locally or by utilizing upstream components. For this reasons, the figures (other than FIG. 1) do not depict components further upstream from the wireless switch 104. Wireless data may include, by way of example but not limitation, station association data and RF environment data. The station and RF data is used by the wireless switches 104 to support features including, by way of example but not limitation, roaming, auto channel selection, rogue AP detection, intrusion detection and the launching of countermeasures. The wireless switch 104 may share wireless data with other wireless switches (not shown). The wireless switch 104 controls the APs 106 (and the APs in the UAP mesh 108). In an embodiment, the APs 106 include radio transmitters and receivers (e.g., transceivers) that are used to provide wireless network connectivity for users and station access to the functions of the wireless switch 104. Within an IEEE 802.11 context, a station is any IEEE 802.11 entity or the equivalent in other related standards, and it may be roaming or stationary. It should be noted that this definition may include APs. Each of the APs 106 anchors at least a portion of the UAP mesh 108 to the wired network. The APs 106 may be treated as border devices between the wireless switch 104 (or other upstream components of the system 100) and the UAP mesh 108. This enables more efficient use of wireless resources because proxy address resolution protocol (proxy ARP) may be used to enable the APs 106 to answer ARP requests on behalf of a remote device (e.g., a UAP for which an AP serves as an anchor to the wireless switch 104). In the example of FIG. 1, the UAP mesh 108 is intended to depict a plurality of potentially discrete APs that do not have a wired connection to the wireless switch 104 or to the APs 106. That is why the APs in the wireless mesh are referred to as �untethered.� Any station in the UAP mesh 108, whether a UAP or some other wireless station, is anchored to the wireless switch 104 by the AP 106 and zero or more UAPs that make up a chain of nodes from the station to the AP 106. An AP that is closer to the wireless switch 104 in the chain may be referred to as anchoring downstream stations. For any given station, the path from the station to the wireless switch 104 may be referred to as a spanning tree because the UAP mesh 108 should not allow loops for traffic passing between a station and the wireless switch 104. When a UAP in the UAP mesh 108 is brought online, it will attempt to reach the wireless switch 104 through a path that is optimal. (Note: Although an optimal path is desired, it may or may not be accomplished in practice, depending upon the implemented algorithm and/or environmental factors). There are multiple metrics for measuring the distance of a UAP from one of the APs 106. For example, the metric may be time. That is, the amount of time it takes for a packet to travel between the UAP and the AP anchoring the UAP. Although such a metric may work fine, it will typically vary depending upon environmental factors, such as traffic congestion or degraded received signal strength. For simplicity, the metric used herein is the number of hops between the UAP and the anchoring AP (AAP), with the understanding that this is but one of many potential metrics. Thus, if a UAP is one hop away from the AAP, the UAP may be referred to as a one-hop UAP. In general, a UAP may be referred to as an N-hop UAP where the UAP is N hops from the AAP. Advantageously, UAPs of the UAP mesh 108 may include an AP-local switching engine embodied in a computer-readable medium. An AP-local switching engine may make use of a station switching record (SSR) to determine how to switch a given message unit (e.g., a packet, frame, datagram, etc.). This enables at least some traffic to be efficiently switched within the UAP mesh 108. Moreover, advantageously, some traffic may be tunneled back to a switch, while other traffic is locally switched. Which traffic is tunneled back, and which traffic is locally switched, is an implementation-specific decision that becomes available by using the teachings described herein. It will be appreciated in light of the description provided herein that although aspects of the invention are described relative to IEEE 802.11 standards, and that certain embodiments have particular features that are implemented within the 802.11 context, the invention itself is not limited to 802.11 networks and may generally be applied to any applicable wireless network; and to the extent that future technological enhancements might obscure the distinctions between wireless switches, APs, and/or stations, the invention is understood to include components providing the features of such switches, APs, and stations independently of how they are packaged, combined, or labeled. In an illustrative embodiment, the UAP mesh 108 is created from a spanning tree. Each station in the UAP mesh 108 attempts to reach the wireless switch 104 along an optimal path. Assuming the optimal path is measured in the number of hops to the wire, if a first station's traffic passes through a UAP and along a path from there to the wire, a second station's traffic that passes through the UAP will take the same path from there to the wire. Since all stations take the optimal path, the stations may be represented as edge nodes of a tree where the AP at the wire is the root node. Thus, the AP mesh acts as a spanning tree for each station. It may be noted that the spanning tree is greedy at each node, which naturally results in an efficient (perhaps even optimized) tree flow. FIG. 2 depicts an example of a subtree 200 of a UAP mesh. The subtree 200 includes an anchor AP (AAP) 202, and one or more UAPs 204-1 to 204-N (referred to collectively as UAPs 204). The path upstream from the AAP 202 to the switch may include no hops, if the AAP 202 is a (tethered) AP; one hop, if the AAP 202 is wirelessly coupled directly to a (tethered) AP, or a chain of UAP nodes; or multiple hops, if the path from the AAP 202 to the switch includes a chain of UAPs. The path downstream from the UAP 204-2 may include multiple jumps, as well. However, it should be noted that if the stations are not wirelessly coupled directly to the UAP 204-2, the UAP 204-2 is actually an AAP (i.e., the UAP 204-2 would be anchoring downstream UAPs). In the example of FIG. 2, the AAP 202 includes a backhaul radio 210 and memory 212. The number of UAPs 204 that are anchored by the AAP 202 may be implementation- or embodiment-specific. For example, a particular installation may limit the number of UAPs 204 to, e.g., five. The backhaul radio 210 may be a radio that is dedicated to transmitting data associated with the UAPs 204. Whether the radio is dedicated to backhauling is an implementation-specific decision. Since there may be multiple radio and SSID configurations per radio-profile, the radio may be used to perform both the backhaul function and other, e.g., 802.11 services. However, it is expected that many customers who implement backhaul services will dedicate a radio to backhaul services because the backhaul link is an important one. In an illustrative embodiment, the backhaul radio 210 is capable of passive scan and active scan. However, it should be noted that in some implementations, best practice may advice against active scan. The channel and power settings are often hard configured so auto-tuning may not be available and may even be undesirable. The ability to change the backhaul channel and force all UAPs to do likewise without dropping any sessions would potentially make auto-tuning more viable. The AAP 202 may or may not include one or more radios (not shown) in addition to the backhaul radio 210. The memory 212 includes a plurality of modules, some of which are depicted in FIG. 2 for illustrative purposes. A processor (not shown) is coupled to the memory 212 in a manner that is well-known in the relevant arts. The memory 212 is intended to represent any of a plurality of known or convenient computer-readable mediums, including non-volatile storage, RAM, flash memory, cache, etc. Any applicable computer-readable medium may be used. In the example of FIG. 2, the memory 212 includes a backhaul radio and service profile module 214, a backhaul service set identifier (SSID) 216, and an authentication engine 218. The backhaul radio and service profile module 214 includes data to be used in association with the backhaul. The backhaul SSID 216 identifies the support network. The authentication engine 218 facilitates authentication of wireless stations (including UAPs). In an illustrative embodiment, the authentication engine 218 authenticates a station in concert with a switch or other upstream component. The station or upstream component may assist in the authentication �on the fly� when a wireless station attempts to associate with the AAP 202, or in advance for a pre-authorized wireless station. In an embodiment that does not have (or has more limited) centralized management, the authentication engine 218 could even be configured to authenticate without the assistance of a switch or other upstream component. The AAP 202 may be configured to beacon the backhaul SSID 216. The service profile is then associated to a radio profile and AP following known or convenient conventions. Since backhaul services will be applied to specific APs in at least one embodiment, general AP-configuration policies (such as auto-dap templates) that can apply to unspecific APs are not enabled in this embodiment. They may be enabled in other embodiments, however. In the example of FIG. 2, the UAP 204-2 includes a radio 220 and memory 222. Details of other ones of the UAPs 204 are omitted to avoid cluttering the figure. Each of the UAPs 204 may be identical to, similar to, or different from the UAP 204-2. The radio 220 may or may not be a dedicated backhaul radio. The value of making the radio 220 into a dedicated backhaul radio diminishes if the UAP 204-2 is at the edge of a UAP mesh (e.g., when there are no downstream UAPs), though the value may or may not be diminished to zero. The memory 222 includes regulatory domain information 224, a backhaul SSID 226, a bootable image 228, and an AAP selection engine 230. The regulatory domain information 224 provides information to the UAP about allowed broadcast parameters for a given region. The CLI to preconfigure a DAP for untethered operation may include the SSID of the anchor AP and a preshared key (not shown). When the UAP is configured with the backhaul SSID 226, the regulatory domain information 224 should probably be stored in, e.g., flash, as well (as shown). This prevents the UAP from operating outside of the regulatory limits before it receives its complete configuration from the switch. It must be clearly documented that when prestaging UAPs, the regulatory and antenna information is correct and reflects the actual deployment to avoid regulatory violations. The regulatory domain information may be updated with a running configuration. The bootable image 228 enables the UAP 204-2 to be deployed with the same services as the AAP 202 (though performance could be adversely impacted by the radio link). When the UAP 204-2 is up and running, the boot configuration associated with the bootable image 228 may be changed. When the boot configuration is changed, the UAP 204-2 must be reset for the changes to take effect. It is not always desirable to allow the boot configuration to change. For example, it is possible for a UAP to find a switch running a software version that does not support untethered APs. When the UAP sees than an older version of software is trying to manage it, the UAP may choose to reboot so as to protect its untethered-capable running image. (This may further require that the anchor AP generate a log message when a radio link is created or destroyed so that link flapping can be identified and, hopefully, remedied.) The AAP selection engine 230 enables the UAP 204-2 to select an AAP from a plurality of potential AAPs. Any known or convenient algorithm may be implemented to choose an AAP. For example, the AAP may be selected by comparing relative signal strengths and choosing the strongest. Alternatively or in addition, each AAP could broadcast an estimated time to wire, or number of hops to wire, which the AAP selection engine 230 can use to choose an optimal AAP. In a non-limiting embodiment, the implemented algorithm is greedy at the UAP 204-2. In a non-limiting embodiment, if the UAP 204-2 is unable to associate with the AAP 202, the UAP 204-2 may beacon an SOS signal, including its serial number. The beacon signal is (hopefully) received at an AP, and sent to the wired network for processing (e.g, at a wireless switch). If appropriate, the upstream component may provide the AAP 202 (or some other AP within range of the UAP 204-2) with data and/or instructions to facilitate an association. FIG. 3 depicts a flowchart 300 of an example of a method for linking a UAP to an AAP. In the example of FIG. 3, the flowchart 300 starts at module 302 where a UAP listens for a beacon with a correct SSID. To know whether an SSID is correct, the UAP must either have the SSID stored in memory, or be informed in some other manner. The UAP will associate to the AAP, at which point (or perhaps after authentication) the UAP will have layer 2 connectivity to the AAP. In order for the associated radio link to be established, the AAP acts as an anchor point and the UAP acts as a client device. In the example of FIG. 3, the flowchart 300 continues to module 304 where the AAP acts as an authenticator in concert with a switch to authenticate the UAP. Implementation of this technique may be based on wpa_supplicant under a BSD license including minimum eap methods. Although wpa_supplicant and WPA-PSK may be used to authenticate, this is an implementation-specific choice; any known or convenient technique that works for the intended purpose may be used. In the example of FIG. 3, the flowchart 300 continues to module 306 where DAP operations are carried out. This may include DAP+TAPA protocols, including optional switch-AP security. At this point, the flowchart 300 ends, though if the DAP operations end, the flowchart 300 could resume at any point (i.e., module 302, 304, or 306). FIG. 4 depicts a diagram 400 illustrating a UAP linking to an existing wireless network. The diagram 400 includes a switch 402, an AAP 404, and a UAP 406. The switch 402 may be similar to the wireless switch 104 (FIG. 1). The break 408 is intended to represent the case where the AAP 404 is untethered so that there are additional nodes (e.g., a tethered AP) between the AAP 404 and the switch 402. However, in an alternative, the AAP 404 may itself be a tethered AP wire connected to the switch 402. The UAP 406 is initially not linked to the AAP 404, but becomes linked as described below. The UAP 406 is 1) configured with a backhaul SSID. While this is not a strict requirement, it is a convenience for those who are responsible for installing or placing the UAP within a UAP mesh. Conceivably, the UAP could be configured to receive an SSID over the air or acquire an SSID in some other manner. The UAP 406 is powered up and 2) listens for a beacon with a backhaul SSID. Again, this is not a strict requirement. It is believed to be more convenient to have the UAP 406 listen for a beacon than to have the UAP initiate a link prior to or instead of receiving a beacon. This is at least in part due to standard practice in 802.11 systems, though such a practice may not be prevalent or even desired in other wireless systems. The AAP 404 3) broadcasts a beacon with the backhaul SSID. The backhaul SSID may be preconfigured at the AAP 404 or could be received at the AAP 404 from the switch at boot time or after. The UAP 406 4) attempts to associate with the AAP 404 upon matching the broadcast backhaul SSID with the backhaul SSID stored locally. It may be noted that the backhaul SSID of the UAP 406 is assumed to be the same as that of the broadcast backhaul SSID. However, there may be other UAPs that are within range of the AAP 404 that have different backhaul SSIDs (perhaps associated with a different AAP). Also, a single AAP could conceivably have multiple backhaul radios, each associated with a different backhaul SSID, or even a single backhaul radio associated with multiple backhaul SSIDs. The AAP 404 5) authenticates the UAP 406 in concert with the switch 402. The UAP 406 may be able to form a layer 2 connection with the AAP 404 when it associates, but the AAP 404 will likely not allow traffic to flow upstream until authentication is complete. While this is not a strict requirement, wireless resources are often relatively scarce, so, in an effort to conserve resources in the case where the UAP 406 is unable to be authenticated, it may be desirable to restrict traffic flow until authentication is complete. The switch 402 6) generates an SSR for the UAP 406. Since the AAP 404 authenticates the UAP 406 in concert with the switch 402, the switch 402 knows about the UAP 406. So the switch 402 is capable of producing an SSR for the UAP 406. In an embodiment, the SSR includes data associated with authorized stations and access control list (ACL) filters. An ACL refers to rules that typically detail service ports or the like that are available on a host or other layer 3 device, each with a list of hosts and/or networks permitted to use the service. ACLs can be configured to control upstream and downstream traffic. (In this context, they are similar to firewalls.) Typically, servers and routers have network ACLs, but in an illustrative embodiment, ACL rules are provided to APs. The SSR enables the UAP 406 to switch at least some traffic, thereby reducing the amount of traffic that has to be switched higher upstream. Advantageously, this pushes message filtering to the edges (or root) of the UAP mesh. The switch 402 7) forms a control channel 410 to the UAP 406. It should be noted that the control channel 410 may simply be a virtual �tunnel� in that tables at each hop along the path to the UAP 406 identify the next hop. This is advantageous because it avoids flooding the UAP mesh, which is wasteful of wireless resources. It should be noted that the control channel 410 is not a �tunnel� in the traditional sense because a tunnel is used to carry user data, which is not necessarily the case here. The switch 402 8) sends the SSR to the UAP 406 via the control channel 410. The AAP 404 9) unicasts the SSR to the UAP 406. In a non-limiting embodiment, this type of action actually occurs at each hop along the path. The SSR is �unicast� because the AAP 404 knows that the destination of the message is the UAP 406, and any other UAPs (now shown) that are listening to the AAP 404 know the destination is not them or downstream from them. The UAP 406 10) receives the SSR and propagates the SSR upstream. That is, the SSR is stored at the UAP 406, then sent to the next hop closer to the switch 402. Traffic associated with the UAP 406 can travel upstream as the SSR is propagated. The AAP 404 11) receives the SSR and propagates the SSR upstream. This occurs at other nodes along the UAP chain up to and including the anchoring (tethered) AP. FIG. 5 depicts an example of a system 500, including a self-healing UAP mesh. In the example of FIG. 5, the system 500 includes a switch 502, an AP 504, UAPs 506-1 and 506-2 (referred to collectively as �one-hop UAPs 506�), UAPs 508-1 and 508-2 (referred to collectively as �two-hop UAPs 508 �), UAPs 510-1 and 510-2 (referred to collectively as �three-hop UAPs 510�), a UAP 512, a station 520, and a station 522. Initially, it is assumed that each UAP is authenticated and has a valid SSR. The SSRs facilitate at least some switching capability within the UAP mesh. For example, if the station 520 sends a packet to the station 522, the packet travels upstream to the UAP 508-1, then to the UAP 506-1. The UAP 506-1 knows that the destination (station 522) is downstream. Accordingly, rather than sending the packet upstream to the switch 502, the UAP 506-1 makes use of the limited data included in the SSR to send the packet downstream to the UAP 508-2, which sends the packet to the UAP 510-2, which sends the packet to the UAP 512, which sends the packet to the station 522. The UAP mesh is self-healing in that if a node goes down, only the affected UAPs need to update. Specifically, say the UAP 510-2 goes down. (This is represented in the example of FIG. 5 by the shading of the UAP 510-2.) When the UAP 510-2 goes down, it causes several problems, including 1) the station 522 is no longer associated with a UAP that can forward messages to and from the station 522; 2) the UAP 508-2 and other upstream nodes (e.g., the UAP 506-1) have incorrect data. Problem 1) can be remedied in the following manner. 1.1) The UAP 512 detects a link failure between itself and the UAP 510-2 because, for the purpose of example, the UAP 510-2 is assumed to have gone down. 1.2) The UAP 512 establishes a link with the UAP 510-1. The new link is represented in the example of FIG. 5 as a dotted line 530. It may be noted that the UAP 512 may have multiple choices of UAPs, though in the example of FIG. 5, only the available UAP 510-1 is depicted. (Presumably, if one of the two-hop UAPs 508 were within range of the UAP 512, the UAP 512 would not have been linked with the UAP 510-2, which is a three-hop UAP. Accordingly, it is assumed that only the UAP 510-1 is in range of the UAP 512.) 1.3) The UAP 510-1 sends a message to the switch 502, alerting the switch 502 that a new SSR is needed because the station 522�and any other stations downstream from UAP 512 (not shown)�is now reachable via a new path. 1.4) The switch 502 sends an SSR downstream to the UAP 510-1. Relevant data from the SSR is propagated at each node, either as the SSR is passed down or by propagation upstream from the UAP 510-1, as has been described previously. Depending upon the implementation and/or embodiment, since the UAP 512 already knows about each station associated with it, and can update upstream routing data locally, the UAP 512 need not necessarily receive the newly sent SSR because the downstream paths remain unbroken, and the upstream path is established through the link to the UAP 510-1. It may be noted that part of problem 2 is already solved in addressing problem 1. Specifically, the UAP 506-1 has been updated correctly as the SSR is propagated at each node (if applicable). However, the UAP 508-2 still includes incorrect data. Problem 2 can be fully remedied in the following manner: 2.1) The UAP 508-2 detects a link failure between itself and the UAP 510-2. 2.2) The UAP 508-2 waits for a timeout period. Waiting for a timeout period may be important for ensuring that the station 522 maintains connectivity with the switch 502. Specifically, if the UAP 508-2 deletes the data associated with the UAP 510-2 (and therefore data associated with downstream nodes, including the UAP 512 and the station 522), and sends the update upstream, upstream nodes will also delete the data. Eventually the update will reach the switch 502, which will update records to show that stations downstream from the UAP 510-2, including the station 522, are now disassociated. By waiting for a timeout period, the UAP 510-1 can update appropriately, before any disassociation, to ensure continuous connectivity (and, e.g., a smooth handoff). 2.3) The UAP 508-2 deletes the data associated with the UAP 510-2 (necessarily including data associated with the station 522). Since the UAP 508-2 waited for a timeout period, the UAP 510-1 has presumably updated the switch 502, and an SSR and/or other data has been propagated along the path between the switch 502 and the UAP 512. Accordingly, the UAP 506-1-and, more generally, all APs on the path between the UAP 512 and the switch 502-will have current data. Therefore, it is not desirable for the update from the UAP 508-2 (deleting the UAP 510-2 and nodes downstream from UAP 510-2) to be implemented at any of the newly updated nodes because the update will or could (depending upon the implementation) delete good data. In an illustrative embodiment, sequence numbers for updates may be used. Specifically, the sequence number associated with the deletion of the data at the UAP 508-2 should be before the sequence number associated with the update at the UAP 510-1. In this way, when the UAP 506-1 receives an update from the UAP 508-2 to delete data, the UAP 506-1 can check the sequence number of the update and, noticing that the sequence number is before the sequence number associated with the latest update, ignore the update. Advantageously, when a UAP notices that the sequence number comes before a most recent update, the UAP can drop the old update; all upstream nodes will have the correct data so the update need not be passed upstream. After the UAP 512 is linked back into the UAP mesh via the link 530, the switching functionality of the mesh is also updated. So, if the station 520 sends a packet to the station 522, the packet may be sent up to the UAP 508-1, which recognizes that the station 522 is downstream. Then the UAP 508-1 sends the packet downstream to UAP 510-1, which sends the packet to the UAP 512, which sends the packet to the station 522. As used herein, an AP may refer to a standard (tethered) AP or to a UAP. Where a distinction should be drawn, an AP may be referred to as a �(tethered) AP� or a �UAP,� as appropriate. As used herein, the term �embodiment� means an embodiment that serves to illustrate by way of example but not limitation. It will be appreciated to those skilled in the art that the preceding examples and embodiments are exemplary and not limiting to the scope of the present invention. It is intended that all permutations, enhancements, equivalents, and improvements thereto that are apparent to those skilled in the art upon a reading of the specification and a study of the drawings are included within the true spirit and scope of the present invention. It is therefore intended that the following appended claims include all such modifications, permutations and equivalents as fall within the true spirit and scope of the present invention. Referenced byCiting PatentFiling datePublication dateApplicantTitleUS7844298 *Jun 12, 2006Nov 30, 2010Belden Inc.Tuned directional antennasUS7865213 *Dec 2, 2009Jan 4, 2011Trapeze Networks, Inc.Tuned directional antennasUS20140064101 *Sep 4, 2012Mar 6, 2014Cisco Technology, Inc.Dynamic Enabling of Wider Channel Transmissions with Radio MonitoringWO2010091634A1 *Feb 10, 2010Aug 19, 2010Huawei Technologies Co., Ltd.Method, apparatus and system for establishing local switch* Cited by examinerClassifications U.S. Classification455/85International ClassificationH04B1/40, H04W84/22, H04W12/06, H04W88/14, H04W84/18Cooperative ClassificationH04W84/22, H04W36/08, H04W12/06, H04W88/14, H04W84/18European ClassificationH04W84/22, H04W12/06Legal EventsDateCodeEventDescriptionNov 8, 2010ASAssignmentOwner name: TRAPEZE NETWORKS, INC., CALIFORNIAEffective date: 20101108Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:BELDEN INC.;REEL/FRAME:025327/0302Feb 25, 2010ASAssignmentOwner name: BELDEN INC.,MISSOURIFree format text: CHANGE OF NAME;ASSIGNOR:TRAPEZE NETWORKS, INC.;US-ASSIGNMENT DATABASE UPDATED:20100226;REEL/FRAME:23985/751Effective date: 20091221Free format text: CHANGE OF NAME;ASSIGNOR:TRAPEZE NETWORKS, INC.;US-ASSIGNMENT DATABASE UPDATED:20100318;REEL/FRAME:23985/751Free format text: CHANGE OF NAME;ASSIGNOR:TRAPEZE NETWORKS, INC.;US-ASSIGNMENT DATABASE UPDATED:20100427;REEL/FRAME:23985/751Free format text: CHANGE OF NAME;ASSIGNOR:TRAPEZE NETWORKS, INC.;US-ASSIGNMENT DATABASE UPDATED:20100429;REEL/FRAME:23985/751Free format text: CHANGE OF NAME;ASSIGNOR:TRAPEZE NETWORKS, INC.;US-ASSIGNMENT DATABASE UPDATED:20100513;REEL/FRAME:23985/751Free format text: CHANGE OF NAME;ASSIGNOR:TRAPEZE NETWORKS, INC.;US-ASSIGNMENT DATABASE UPDATED:20100525;REEL/FRAME:23985/751Free format text: CHANGE OF NAME;ASSIGNOR:TRAPEZE NETWORKS, INC.;REEL/FRAME:23985/751Free format text: CHANGE OF NAME;ASSIGNOR:TRAPEZE NETWORKS, INC.;REEL/FRAME:023985/0751Owner name: BELDEN INC., MISSOURIJul 30, 2007ASAssignmentOwner name: TRAPEZE NETWORKS, INC., CALIFORNIAFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:MURPHY, JAMES;MORAIN, GARY E.;CHESNUTT, STAN;REEL/FRAME:019622/0181;SIGNING DATES FROM 20070723 TO 20070730Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:MURPHY, JAMES;MORAIN, GARY E.;CHESNUTT, STAN;SIGNING DATES FROM 20070723 TO 20070730;REEL/FRAME:019622/0181RotateOriginal ImageGoogle Home - Sitemap - USPTO Bulk Downloads - Privacy Policy - Terms of Service - About Google Patents - Send FeedbackData provided by IFI CLAIMS Patent Services