Source: https://patents.google.com/patent/US8687521B1/en
Timestamp: 2019-09-22 07:04:13
Document Index: 210647180

Matched Legal Cases: ['Application No. 61', 'art 16', 'art 16', 'art 16', 'art 11', 'art 11', 'art 11', 'art 11', 'art 11', 'art 11', 'art 11', 'art 11', 'art 16', 'art 16', 'art 16', 'art 11', 'art 11']

US8687521B1 - Avoiding mesh path discovery in wireless mesh networks - Google Patents
Avoiding mesh path discovery in wireless mesh networks Download PDF
US8687521B1
US8687521B1 US13/346,177 US201213346177A US8687521B1 US 8687521 B1 US8687521 B1 US 8687521B1 US 201213346177 A US201213346177 A US 201213346177A US 8687521 B1 US8687521 B1 US 8687521B1
US13/346,177
2008-12-01 Priority to US11873108P priority Critical
2009-05-13 Priority to US12/464,958 priority patent/US8094637B1/en
2012-01-09 Application filed by Marvell International Ltd filed Critical Marvell International Ltd
2012-01-09 Priority to US13/346,177 priority patent/US8687521B1/en
2014-04-01 Publication of US8687521B1 publication Critical patent/US8687521B1/en
A network interface of a first mesh point device, the network interface including a memory and a medium access controller. In response to the first mesh point device receiving a frame, the medium access controller determines whether a mesh path for routing the frame from the first mesh point device to a second mesh point device is stored in the memory. In response to a mesh path not being stored in the memory, and prior to performing a mesh path discovery protocol, the medium access controller (i) determines whether the second mesh point device is one hop from the first mesh point device, and if so selects a one hop path for routing the frame to the second mesh point device, otherwise (ii) uses the mesh path discovery protocol to determine a mesh path for routing the frame to the second mesh point device.
This application is a continuation of U.S. patent application Ser. No. 12/464,958, filed on May 13, 2009, which claims benefit of U.S. Provisional Application No. 61/118,731, filed on Dec. 1, 2008. The disclosures of the above applications are incorporated herein by reference in their entirety.
A network interface of a first mesh point device is provided. The network interface includes a memory and a medium access controller. In response to the first mesh point device receiving a frame to be transmitted to a second mesh point device, the medium access controller is configured to determine whether a mesh path for routing the frame from the first mesh point device to the second mesh point device is stored in the memory. In response to a mesh path for routing the frame from the first mesh point device to the second mesh point device not being stored in the memory and prior to performing a mesh path discovery protocol to determine a mesh path for routing the frame from the first mesh point device to the second mesh point device, the medium access controller is configured to determine whether the second mesh point device is one hop from the first mesh point device. The medium access controller determines if the second mesh point device is one hop from the first mesh point device without using the mesh path discovery protocol. If the second mesh point device is one hop from the first mesh point device the medium access controller selects a one hop path for routing the frame from the first mesh point device to the second mesh point device, otherwise the medium access controller uses the mesh path discovery protocol to determine a mesh path for routing the frame from the first mesh point device to the second mesh point device.
In one aspect, an apparatus is provided and includes: a mesh path module adapted to select a mesh path between a first mesh point in a mesh network and a second mesh point in the mesh network, wherein the mesh path module includes a neighbor discovery module adapted to determine whether the second mesh point is one hop from the first mesh point, a one-hop mesh path module adapted to select a one-hop mesh path between the first mesh point and the second mesh point when the second mesh point is one hop from the first mesh point, and a multi-hop mesh path module adapted to discover a multi-hop mesh path between the first mesh point and the second mesh point only when it is determined that the second mesh point is not one hop from the first mesh point.
The apparatus may include one or more of the following features. In some implementations, the mesh path module further includes: a path loss module adapted to measure a path loss of the one-hop mesh path between the first mesh point and the second mesh point; wherein the multi-hop mesh path module is further adapted to discover a multi-hop mesh path between the first mesh point and the second mesh point when the path loss of the one-hop mesh path exceeds a predetermined threshold. Some implementations include a forwarding module adapted to forward frames received by the first mesh point and addressed to the second mesh point according to an entry for the second mesh point in a forwarding table; wherein the mesh path module is further adapted to generate the entry for the second mesh point in the forwarding table in order to establish the one-hop path between the first mesh point to the second mesh point. Some implementations include a path lifetime module adapted to determine when a path lifetime ends for the entry for the second mesh point in the forwarding table; wherein the neighbor discovery module is further adapted to determine whether the second mesh point is one hop from the first mesh point in response to an end of the path lifetime for the entry for the second mesh point in the forwarding table.
In one aspect, a method for finding a mesh path between a first mesh point in a mesh network and a second mesh point in the mesh network is provided. The method includes: determining whether the second mesh point is one hop from the first mesh point; establishing a one-hop mesh path between the first mesh point and the second mesh point when the second mesh point is one hop from the first mesh point; and discovering a multi-hop mesh path between the first mesh point and the second mesh point only when the second mesh point is not one hop from the first mesh point.
Implementations of the method can include one or more of the following features. Some implementations include measuring a path loss of the one-hop mesh path between the first mesh point and the second mesh point; and discovering a multi-hop mesh path between the first mesh point and the second mesh point when the path loss of the one-hop mesh path exceeds a predetermined threshold. Some implementations include measuring a one-hop path loss of the multi-hop mesh path between the first mesh point and the second mesh point; and selecting a one-hop mesh path between the first mesh point and the second mesh point when the one-hop path loss of the multi-hop mesh path falls below a predetermined threshold. Some implementations include forwarding frames received by the first mesh point and addressed to the second mesh point according to an entry for the second mesh point in a forwarding table; wherein establishing the one-hop path between the first mesh point and the second mesh point includes generating the entry for the second mesh point in the forwarding table. Some implementations include determining when a path lifetime ends for the entry for the second mesh point in the forwarding table; and determining whether the second mesh point is one hop from the first mesh point in response to an end of the path lifetime for the entry for the second mesh point in the forwarding table.
FIG. 2 shows elements of a mesh point of FIG. 1 according to the present disclosure.
FIG. 3 shows elements of the MAC device of FIG. 2 according to the present disclosure.
FIG. 4 shows a process for the mesh point of FIGS. 1-3 according to implementations where the mesh point receives a frame addressed to another mesh point.
FIG. 5 shows a process for the mesh point of FIGS. 1-3 according to implementations where the path lifetime for a mesh path ends.
FIG. 6 shows a process employing path loss for mesh point of FIGS. 1-3 according to the present disclosure.
By default each mesh point can use mesh path discovery protocols such as Hybrid Wireless Mesh Protocol (HWMP) or multi-hop routing. Implementations disclosed herein may include, before starting mesh path discovery, a mesh point determining whether the destination mesh point is a one-hop neighbor, and if so, sending frames directly to the destination mesh point instead of performing mesh path discovery. If the mesh point fails to deliver a frame in this manner, for example because the destination mesh point is no longer in direct communication range, the mesh point may perform mesh path discovery, for example using HWMP.
FIG. 2 shows elements of a mesh point 102 of FIG. 1. Although the elements of mesh point 102 are presented in one arrangement, other implementations may feature other arrangements, as will be apparent to one skilled in the relevant arts based on the disclosure and teachings provided herein. For example, the elements of mesh point 102 can be implemented in hardware, software, or combinations thereof. In some implementations, mesh point 102 is compliant with all or part of IEEE standard 802.11, including amendment 802.11s.
FIG. 3 shows elements of MAC device 210 of FIG. 2. Although the elements of MAC device 210 are presented in one arrangement, other implementations may feature other arrangements, as will be apparent to one skilled in the relevant arts based on the disclosure and teachings provided herein. For example, the elements of MAC device 210 can be implemented in hardware, software, or combinations thereof.
Multiple scenarios exist where a mesh point should select a mesh path. In one such scenario, a frame arrives that is addressed to a destination to which there is no existing mesh path. FIG. 4 shows a process 400 for mesh point 102 of FIGS. 1-3 where mesh point 102 receives a frame addressed to another mesh point 102. Although the elements of process 400 are presented in one arrangement, other implementations may feature other arrangements, as will be apparent to one skilled in the relevant arts based on the disclosure and teachings provided herein. For example, in various implementations, some or all of the steps of process 400 can be executed in a different order, concurrently, and the like. In some implementations, process 400 is compliant with all or part of IEEE standard 802.11, including amendment 802.11s.
However, if and when the frame is received, no mesh path exists for destination mesh point 102B (step 404), and destination mesh point 102B is not a one-hop neighbor of source mesh point 102A (step 408), then mesh path module 302 switches to mesh path discovery (step 412). That is, multi-hop mesh path module 310 discovers a multi-hop mesh path between source mesh point 102A and destination mesh point 102B only when destination mesh point 102B is not one hop from source mesh point 102A. Multi-hop mesh path module 310 can employ any process for discovering the multi-hop mesh path, for example including HWMP, multi-hop routing, and the like. Once the multi-hop mesh path has been discovered and recorded in forwarding table 316, forwarding module 304 forwards the received frame to destination mesh point 102B using the discovered mesh path (step 406).
In various implementations, to limit mesh path discovery overhead, HWMP can take advantage of the high probability that destination mesh point 102B has not moved far from source mesh point 102A by employing an expanding ring mesh time-to-live (TTL) search as follows. Mesh path discovery begins with a low TTL value, for example TTL=2. If no mesh path is found to destination mesh point 102B with the current TTL value, the TTL value is incremented by a TTL_INCR value, for example TTL_INCR=3, and mesh path discovery is repeated. This process can be repeated up to a predetermined maximum number of attempts, for example MAX_ROUTE_DISCOVERY_ATTEMPT=3. The parameters TTL, TTL_INCR, and MAX_ROUTE_DISCOVERY_ATTEMPT can be configurable.
Another scenario where a mesh point should select a mesh path occurs when an existing mesh path expires, that is, when the path lifetime for the mesh path ends. FIG. 5 shows a process 500 for mesh point 102 of FIGS. 1-3 where the path lifetime for a mesh path ends. Although the elements of process 500 are presented in one arrangement, other implementations may feature other arrangements, as will be apparent to one skilled in the relevant arts based on the disclosure and teachings provided herein. For example, in various implementations, some or all of the steps of process 500 can be executed in a different order, concurrently, and the like. In some implementations, process 500 is compliant with all or part of IEEE standard 802.11, including amendment 802.11s.
FIG. 6 shows a process 600 employing path loss for mesh point 102 of FIGS. 1-3. Although the elements of process 600 are presented in one arrangement, other implementations may feature other arrangements, as will be apparent to one skilled in the relevant arts based on the disclosure and teachings provided herein. For example, in various implementations, some or all of the steps of process 600 can be executed in a different order, concurrently, and the like. In some implementations, process 600 is compliant with all or part of IEEE standard 802.11, including amendment 802.11s.
At some later time, path loss module 312 measures a “one-hop path loss” of the multi-hop mesh path (step 610). Path loss module 312 can measure the one-hop path loss based on RSSI values of the frames received directly from destination mesh point 102B. However, in general, path loss is not same in both directions. Therefore, in some implementations, destination mesh point 102B measures the path loss, and reports the path loss to source mesh point 102A.
Various mesh point apparatuses and elements are disclosed herein and can be implemented in digital electronic circuitry, or in computer hardware, firmware, software, or in combinations of them. The mesh point apparatuses and elements can be implemented in a computer program product tangibly embodied in a machine-readable storage device for execution by a programmable processor; and method steps can be performed by a programmable processor executing a program of instructions to perform functions by operating on input data and generating output. The mesh point apparatuses and elements can be implemented in one or more computer programs that are executable on a programmable system including at least one programmable processor coupled to receive data and instructions from, and to transmit data and instructions to, a data storage system, at least one input device, and at least one output device. Each computer program can be implemented in a high-level procedural or object-oriented programming language, or in assembly or machine language if desired; and in any case, the language can be a compiled or interpreted language. Suitable processors include, by way of example, both general and special purpose microprocessors. Generally, a processor will receive instructions and data from a read-only memory and/or a random access memory. Generally, a computer will include one or more mass storage devices for storing data files; such devices include magnetic disks, such as internal hard disks and removable disks; magneto-optical disks; and optical disks. Storage devices suitable for tangibly embodying computer program instructions and data include all forms of non-volatile memory, including by way of example semiconductor memory devices, such as EPROM, EEPROM, and flash memory devices; magnetic disks such as internal hard disks and removable disks; magneto-optical disks; and CD-ROM disks. Any of the foregoing can be supplemented by, or incorporated in, ASICs (application-specific integrated circuits).
1. A network interface of a first mesh point device, the network interface comprising:
a medium access controller, wherein in response to the first mesh point device receiving a frame to be transmitted to a second mesh point device, the medium access controller is configured to determine whether a mesh path for routing the frame from the first mesh point device to the second mesh point device is stored in the memory,
wherein, in response to a mesh path for routing the frame from the first mesh point device to the second mesh point device not being stored in the memory, and prior to performing a mesh path discovery protocol to determine a mesh path for routing the frame from the first mesh point device to the second mesh point device, the medium access controller is configured to
(i) determine, without using the mesh path discovery protocol, whether the second mesh point device is one hop from the first mesh point device, and if so select a one hop path for routing the frame from the first mesh point device to the second mesh point device, otherwise
(ii) use the mesh path discovery protocol to determine a mesh path for routing the frame from the first mesh point device to the second mesh point device.
2. The network interface of claim 1, wherein the medium access controller is configured to use a neighbor discovery protocol to determine whether the second mesh point device is one hop from the first mesh point device.
3. The network interface of claim 1, wherein the medium access controller is configured to determine whether the second mesh point device is one hop from the first mesh point device by sending the frame to the second mesh point device.
4. The network interface of claim 1, wherein the mesh path discovery protocol comprises a hybrid wireless mesh protocol or a multi-hop routing protocol.
5. The network interface of claim 1, wherein the medium access controller is configured to employ a history of previously found mesh paths to determine whether the second mesh point device is one hop from the first mesh point.
6. The network interface of claim 1, wherein, in response to a mesh path for routing the frame from the first mesh point device to the second mesh point device being stored in the memory, the medium access controller is configured to select the mesh path for routing the frame from the first mesh point device to the second mesh point device.
7. The network interface of claim 1, wherein:
the memory is configured to store a forwarding table; and
the medium access controller is configured to determine whether a mesh path for routing the frame from the first mesh point device to the second mesh point device is stored in the memory by determining whether an entry corresponding to the second mesh point device exists in the forwarding table.
8. The network interface of claim 1, wherein the medium access controller comprises:
a path loss module configured to measure a one-hop path loss of a multi-hop mesh path between the first mesh point device and the second mesh point device; and
a mesh path module configured to select a one-hop mesh path between the first mesh point device and the second mesh point device when the one-hop path loss of the multi-hop mesh path decreases to a value less than a predetermined threshold.
9. The network interface of claim 1, wherein the medium access controller comprises:
a forwarding module configured to forward the frame according to an entry for the second mesh point device in a forwarding table, wherein the frame is addressed to the second mesh point device, and wherein the forwarding table is stored in the memory; and
a mesh path module configured to generate the entry in the forwarding table for the second mesh point device in order to establish a one-hop mesh path from the first mesh point device to the second mesh point device.
10. The network interface of claim 9, wherein the medium access controller comprises:
a lifetime module configured to determine when a path lifetime ends for the entry; and
a discovery module configured to determine whether the second mesh point device is one hop from the first mesh point device in response to the path lifetime for the entry ending.
11. The network interface of claim 10, wherein:
the first mesh point device comprises a desktop computer, a personal digital assistant (PDA), a mobile phone, a laptop, a personal computer (PC), a printer, a digital camera, or an internet protocol (IP) phone; and
the second mesh point device comprises a desktop computer, a personal digital assistant (PDA), a mobile phone, a laptop, a personal computer (PC), a printer, a digital camera, or an internet protocol (IP) phone.
receiving, at a first mesh point device, a frame to be forwarded to a second mesh point device; and
determining whether a mesh path for routing the frame from the first mesh point device to the second mesh point device is stored in a memory of the first mesh point device,
wherein, in response to a mesh path for routing the frame from the first mesh point device to the second mesh point device not being stored in the memory, and prior to performing a mesh path discovery protocol to determine a mesh path for routing the frame from the first mesh point device to the second mesh point device,
(i) determining, without using the mesh path discovery protocol, whether the second mesh point device is one hop from the first mesh point device, and if so selecting a one hop path for routing the frame from the first mesh point device to the second mesh point device, otherwise
(ii) using the mesh path discovery protocol to determine a mesh path for routing the frame from the first mesh point device to the second mesh point device.
13. The method of claim 12, wherein determining whether the second mesh point device is one hop from the first mesh point device comprises using a neighbor discovery protocol to determine whether the second mesh point device is one hop from the first mesh point device.
14. The method of claim 12, wherein determining whether the second mesh point device is one hop from the first mesh point device comprises sending the frame to the second mesh point device.
15. The method of claim 12, further comprising, wherein the mesh path discovery protocol comprises a hybrid wireless mesh protocol or a multi-hop routing protocol.
16. The method of claim 12, wherein determining whether the second mesh point device is one hop from the first mesh point device comprises employing a history of previously found mesh paths.
determining whether a mesh path for routing the frame from the first mesh point device to the second mesh point device is stored in the memory comprises determining whether an entry corresponding to the second mesh point device exists in the forwarding table.
the second mesh point device comprises a desktop computer, a personal digital assistant (PDA), a mobile phone, a laptop, a personal computer (PC), a printer, a digital camera, or an internet protocol (IP).
US13/346,177 2008-12-01 2012-01-09 Avoiding mesh path discovery in wireless mesh networks Active 2029-11-17 US8687521B1 (en)
US11873108P true 2008-12-01 2008-12-01
US12/464,958 US8094637B1 (en) 2008-12-01 2009-05-13 Avoiding mesh path discovery in wireless mesh networks
US13/346,177 US8687521B1 (en) 2008-12-01 2012-01-09 Avoiding mesh path discovery in wireless mesh networks
US12/464,958 Continuation US8094637B1 (en) 2008-12-01 2009-05-13 Avoiding mesh path discovery in wireless mesh networks
US8687521B1 true US8687521B1 (en) 2014-04-01
ID=45419157
US12/464,958 Active 2029-11-26 US8094637B1 (en) 2008-12-01 2009-05-13 Avoiding mesh path discovery in wireless mesh networks
US13/346,177 Active 2029-11-17 US8687521B1 (en) 2008-12-01 2012-01-09 Avoiding mesh path discovery in wireless mesh networks
US (2) US8094637B1 (en)
US20060256769A1 (en) 2005-05-11 2006-11-16 Samsung Electronics Co., Ltd. Method and apparatus for keeping information in routing tables consistent throughout wireless network
US20080084855A1 (en) 2006-10-05 2008-04-10 Rahman Shahriar I Upgrading mesh access points in a wireless mesh network
US20080298251A1 (en) 2007-05-29 2008-12-04 Bae Systems Information And Electronic Systems Integration Inc. INTEGRATING LOCAL CONGESTION AND PATH INTERFERENCE INTO QoS ROUTING FOR WIRELESS MOBILE AD HOC NETWORKS
US20080316997A1 (en) 2007-06-20 2008-12-25 Motorola, Inc. Multi-radio node with a single routing module which manages routing for multiple different radio modules
US20090003214A1 (en) 2007-06-15 2009-01-01 Silver Spring Networks, Inc. Load management in wireless mesh communications networks
US20090059934A1 (en) 2007-08-30 2009-03-05 Motorola, Inc. Method and device for providing a bridge in a network
US20090109870A1 (en) 2007-10-26 2009-04-30 Motorola, Inc. Method for intelligent merging of ad hoc network partitions
US20100097971A1 (en) 2008-10-16 2010-04-22 Nam-Hi Kang Method for configuring and managing multicast data delivery path in mobile ad-hoc network and multicast data delivery system using the same
US20100115272A1 (en) 2008-10-30 2010-05-06 Symbol Technologies, Inc. Communicating a packet from a mesh-enabled access point to a mesh portal in a multi-hop mesh network
US20100172249A1 (en) 2005-11-02 2010-07-08 Hang Liu Method for Determining a Route in a Wireless Mesh Network Using a Metric Based On Radio and Traffic Load
US20100278118A1 (en) 2009-04-30 2010-11-04 Motorola, Inc. Method for selecting communication links in a multi-radio wireless communication system
2009-05-13 US US12/464,958 patent/US8094637B1/en active Active
2012-01-09 US US13/346,177 patent/US8687521B1/en active Active
US20050078659A1 (en) 1999-12-23 2005-04-14 Ashwood Smith Peter J. Label selection for end-to-end label-switched traffic through a communications network
US7911962B2 (en) 2007-05-29 2011-03-22 Bae Systems Information And Electronic Systems Integration Inc. Integrating local congestion and path interference into QoS routing for wireless mobile AD HOC networks
802.16e(TM)-2005 and IEEE Std 802.16(TM)-2004/Cor1-2005 (Amendment and Corrigendum to IEEE Std 802.16-2004; IEEE Standard for Local and metropolitan area networks; Part 16: Air Interface for Fixed Broadband Wireless Access Systems; Amendment 2: Physical and Medium Access Control Layers for Combined Fixed and Mobile Operation in Licensed Bands and Corrigendum 1; IEEE Computer Society and the IEEE Microwave Theory and Techniques Society; Feb. 28, 2006; 864 pages.
802.16e™—2005 and IEEE Std 802.16™—2004/Cor1-2005 (Amendment and Corrigendum to IEEE Std 802.16-2004; IEEE Standard for Local and metropolitan area networks; Part 16: Air Interface for Fixed Broadband Wireless Access Systems; Amendment 2: Physical and Medium Access Control Layers for Combined Fixed and Mobile Operation in Licensed Bands and Corrigendum 1; IEEE Computer Society and the IEEE Microwave Theory and Techniques Society; Feb. 28, 2006; 864 pages.
IEEE 802.11n; IEEE 802.11-04/0889r6; IEEE P802.11 Wireless LANs; TGn Sync Proposal Technical Specification; Syed Aon Mujtaba; Agere System Inc.; May 18, 2005; 131 pages.
IEEE 802.16/2001; IEEE Standard for Local and metropolitan area networks; Part 16: Air Interface for Fixed Broadband Wireless Access Systems; IEEE Computer Society and the IEEE Microwave Theory and Techniques Society; Sponsored by the LAN/MAN Standards Committee; Apr. 8, 2002; 349 pages.
IEEE P802.11s(TM)/D2.0; Mar. 2008; Draft Standard for Information Technology-Telecommunications and information exchange between systems-Local and metropolitan area networks-Specific requirements-Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) specifications; Amendment : Mesh Networking; 263 pages.
IEEE P802.11s™/D2.0; Mar. 2008; Draft Standard for Information Technology—Telecommunications and information exchange between systems—Local and metropolitan area networks—Specific requirements—Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) specifications; Amendment <number>: Mesh Networking; 263 pages.
IEEE Std 802.11b-1999/Cor Jan. 2001 (Corrigendum to IEEE Std 802.11-1999); IEEE Standard for Information technology-Telecommunications and information exchange between systems-Local and metropolitan area networks-Specific requirements-Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) specifications; Amendment 2: Higher-Speed Physical Layer (PHY) extension in the 2.4 GHz band-Corrigendum 1; LAN/MAN Standards Committee of the IEEE Computer Society; Nov. 7, 2001; 23 pages.
IEEE Std 802.11b-1999/Cor Jan. 2001 (Corrigendum to IEEE Std 802.11-1999); IEEE Standard for Information technology—Telecommunications and information exchange between systems—Local and metropolitan area networks—Specific requirements—Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) specifications; Amendment 2: Higher-Speed Physical Layer (PHY) extension in the 2.4 GHz band-Corrigendum 1; LAN/MAN Standards Committee of the IEEE Computer Society; Nov. 7, 2001; 23 pages.
IEEE Std 802.11h(TM)-2003 [Amendment to IEEE Std 802.11(TM), 1999 Edition (Reaff 2003) as amended by IEEE Stds 802.11a(TM)-1999, 802.11b(TM)-1999, 802.11b(TM)-1999/Cor Jan. 2001, 802.11d(TM)-2001, 802.11g(TM)-2003]; IEEE Standard for Information technology-Telecommunications and information exchange between systems-Local and metropolitan area networks-Specific requirements; Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) specifications; Amendment 5: Spectrum and Transmit Power Management Extensions in the 5 GHz band in Europe; IEEE Computer Society; LAN/MAN Standards Committee; Oct. 14, 2003; 75 pages.
IEEE Std 802.11h™—2003 [Amendment to IEEE Std 802.11™, 1999 Edition (Reaff 2003) as amended by IEEE Stds 802.11a™—1999, 802.11b™—1999, 802.11b™—1999/Cor Jan. 2001, 802.11d™—2001, 802.11g™—2003]; IEEE Standard for Information technology—Telecommunications and information exchange between systems—Local and metropolitan area networks—Specific requirements; Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) specifications; Amendment 5: Spectrum and Transmit Power Management Extensions in the 5 GHz band in Europe; IEEE Computer Society; LAN/MAN Standards Committee; Oct. 14, 2003; 75 pages.
IEEE Std 802.11K(TM)-2008; (Amendment to IEEE Std 802.11(TM)-2007); IEEE Standard for Information technology-Telecommunications and information exchange between systems-Local and metropolitan area networks-Specific requirements-Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications; Amendment 1: Radio Resource Measurement of Wireless LANs; IEEE Computer Society; Sponsored by the LAN/MAN Standards Committee; Jun. 12, 2008; 244 pages.
IEEE Std 802.11K™—2008; (Amendment to IEEE Std 802.11™—2007); IEEE Standard for Information technology—Telecommunications and information exchange between systems—Local and metropolitan area networks—Specific requirements—Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications; Amendment 1: Radio Resource Measurement of Wireless LANs; IEEE Computer Society; Sponsored by the LAN/MAN Standards Committee; Jun. 12, 2008; 244 pages.
IEEE Std 802.16/2004 (Revision of IEEE Std 802.16-2001) IEEE Standard for Local and metropolitan area networks; Part 16: Air Interface for Fixed Broadband Wireless Access Systems; IEEE Computer Society and the IEEE Microwave Theory and Techniques Society; Oct. 1, 2004; 893 pages.
IEEE Std 802.16a(TM)-2003 (Amendment to IEEE Std 802.16(TM)-2001) IEEE Standard for Local and metropolitan area networks; Part 16: Air Interface for Fixed Broadband Wireless Access Systems; Amendment 2: Medium Access Control Modifications and Additional Physical Layer Specifications for 2-11 GHz; IEEE Computer Society and the IEEE Microwave Theory and Techniques Society; Apr. 1, 2003; 318 pages.
IEEE Std 802.16a™—2003 (Amendment to IEEE Std 802.16™—2001) IEEE Standard for Local and metropolitan area networks; Part 16: Air Interface for Fixed Broadband Wireless Access Systems; Amendment 2: Medium Access Control Modifications and Additional Physical Layer Specifications for 2-11 GHz; IEEE Computer Society and the IEEE Microwave Theory and Techniques Society; Apr. 1, 2003; 318 pages.
ISO/IEC 8802-11; ANSI/IEEE Std. 802.11; First Edition 1999-00-00; Information technology-Telecommunications and information exchange between systems-Local and metropolitan area networks-Specific requirements-Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) specifications; 531 pages.
ISO/IEC 8802-11; ANSI/IEEE Std. 802.11; First Edition 1999-00-00; Information technology—Telecommunications and information exchange between systems—Local and metropolitan area networks—Specific requirements—Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) specifications; 531 pages.
Path Discovery Mechanism: Sanity; From OLPC; Jun. 17, 2008; 13 pages.
US8094637B1 (en) 2012-01-10
US20080112340A1 (en) 2008-05-15 Wireless communication network and method of dynamic channel selection of a wireless communication network
EP1716674B1 (en) 2007-04-11 Method and arrangement in wireless ad hoc or multihop networks