CA2650436C - High-throughput channel operation in a mesh wireless local area network - Google Patents
High-throughput channel operation in a mesh wireless local area network Download PDFInfo
- Publication number
- CA2650436C CA2650436C CA2650436A CA2650436A CA2650436C CA 2650436 C CA2650436 C CA 2650436C CA 2650436 A CA2650436 A CA 2650436A CA 2650436 A CA2650436 A CA 2650436A CA 2650436 C CA2650436 C CA 2650436C
- Authority
- CA
- Canada
- Prior art keywords
- wtru
- wtrus
- configuration
- information
- channel
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Expired - Fee Related
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/02—Details
- H04L12/12—Arrangements for remote connection or disconnection of substations or of equipment thereof
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/0001—Systems modifying transmission characteristics according to link quality, e.g. power backoff
- H04L1/0009—Systems modifying transmission characteristics according to link quality, e.g. power backoff by adapting the channel coding
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
- H04L41/0806—Configuration setting for initial configuration or provisioning, e.g. plug-and-play
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
- H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
- H04L41/082—Configuration setting characterised by the conditions triggering a change of settings the condition being updates or upgrades of network functionality
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
- H04L41/084—Configuration by using pre-existing information, e.g. using templates or copying from other elements
- H04L41/0843—Configuration by using pre-existing information, e.g. using templates or copying from other elements based on generic templates
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
- H04L41/084—Configuration by using pre-existing information, e.g. using templates or copying from other elements
- H04L41/0846—Configuration by using pre-existing information, e.g. using templates or copying from other elements based on copy from other elements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/085—Retrieval of network configuration; Tracking network configuration history
- H04L41/0853—Retrieval of network configuration; Tracking network configuration history by actively collecting configuration information or by backing up configuration information
- H04L41/0856—Retrieval of network configuration; Tracking network configuration history by actively collecting configuration information or by backing up configuration information by backing up or archiving configuration information
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/12—Discovery or management of network topologies
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
- H04L43/0805—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
- H04L43/0817—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability by checking functioning
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L5/00—Arrangements affording multiple use of the transmission path
- H04L5/003—Arrangements for allocating sub-channels of the transmission path
- H04L5/0058—Allocation criteria
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W84/00—Network topologies
- H04W84/18—Self-organising networks, e.g. ad-hoc networks or sensor networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/02—Standardisation; Integration
- H04L41/0213—Standardised network management protocols, e.g. simple network management protocol [SNMP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W48/00—Access restriction; Network selection; Access point selection
- H04W48/16—Discovering, processing access restriction or access information
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W84/00—Network topologies
- H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
- H04W84/10—Small scale networks; Flat hierarchical networks
- H04W84/12—WLAN [Wireless Local Area Networks]
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D30/00—Reducing energy consumption in communication networks
- Y02D30/50—Reducing energy consumption in communication networks in wire-line communication networks, e.g. low power modes or reduced link rate
Abstract
High throughput channel operation in a mesh wireless local area network (WLAN) is disclosed. A mesh network comprises a plurality of mesh points and a network management entity (NME). The NME is configured to retrieve capability and configuration data from the mesh points. The NME configures at least one mesh point with respect to IEEE 802.11n channelization and legacy protection mode based on the capability and configuration data.
Description
[0001] HIGH-THROUGHPUT CHANNEL OPERATION
IN A MESH WIRELESS LOCAL AREA NETWORK
[0001] FIELD OF INVENTION
[00021 The present invention is related to wireless local area networks (WLANs). More specifically, the present invention is related to high throughput channel operation in a mesh WLAN.
IN A MESH WIRELESS LOCAL AREA NETWORK
[0001] FIELD OF INVENTION
[00021 The present invention is related to wireless local area networks (WLANs). More specifically, the present invention is related to high throughput channel operation in a mesh WLAN.
[0003] BACKGROUND
[0004] IEEE 802. l ls is a draft specification for providing a means to form a mesh wireless backhaul with IEEE 802.11 WLAN technology. Mesh networks are also known as multi-hop networks, since data packets may be relayed more than once in order to reach their destination. This presents a different paradigm as compared to the original WLAN standard, which addresses only star topologies for stations (STAs) to be connected to an access point (AP) effectively using single hop communications through a basic service set (BSS).
[0005] IEEE 802.11s only addresses network nodes that form a mesh network and the WLAN mesh operation in the backhaul that is transparent to all STAs. This means that, similar to legacy IEEE 802.11 WLAN, STAs still connect to an AP, (i.e., mesh AP having a mesh capability), through a BSS. The mesh AP
interfaces on its backhaul side to other mesh points which forward and route traffic through the mesh network to a destination. The destination may be a mesh portal which routes the traffic to the external network or may be another mesh AP attached to the mesh network. By choosing this approach, even legacy STAs may still operate in a mesh-enabled WLAN. The communication between STAs and a mesh AP in a BSS is completely independent from the mesh network.
The STAs are unaware of the presence of the mesh network in the backhaul.
interfaces on its backhaul side to other mesh points which forward and route traffic through the mesh network to a destination. The destination may be a mesh portal which routes the traffic to the external network or may be another mesh AP attached to the mesh network. By choosing this approach, even legacy STAs may still operate in a mesh-enabled WLAN. The communication between STAs and a mesh AP in a BSS is completely independent from the mesh network.
The STAs are unaware of the presence of the mesh network in the backhaul.
[0006] The IEEE 802.1ls WLAN mesh standard has been designed under the assumption that legacy IEEE 802.11a/b/g radio interface may be implemented on the mesh points. The IEEE 802.11s standard is mostly radio interface agnostic. For example, routing and forwarding of data packets are not dependent on the particularities of an IEEE 802. l la/b/g radio interfaces, (such as modulation scheme or channel coding).
[0007] IEEE 802.11s also allows different ways for simultaneous multi-channel operation. One way to implement multi-channel operation is to use multiple IEEE 802.11 radio devices on a mesh point in order to increase the available data throughput capability. Another possibility is to use a single radio device, (so-called common channel framework (CCF)), for more than one channel.
[0008] IEEE 802.1ln specification is another specification for providing a high throughput (HT) WLAN. Some of the IEEE 802.1 ln throughput-enhancing features are aggregation, enhanced block acknowledgement (BA), reverse direction grant, power save multiple poll (PSMP), and operational bandwidth.
In IEEE 802.11n, a data rate is increased by annexing or bonding two adjacent channels. The data rate increase is also achieved by using several more data tones with 802.11 40 MHz operation relative to 2x20 MHz channel occupancy with 802.11a/g. However, not all IEEE 802.11n devices may support 40 MHz operation and, therefore, the transition of operation from 20 MHz to 40 MHz should be managed efficiently. In order to achieve this, the IEEE 802.11n standard provides some channel management mechanisms.
In IEEE 802.11n, a data rate is increased by annexing or bonding two adjacent channels. The data rate increase is also achieved by using several more data tones with 802.11 40 MHz operation relative to 2x20 MHz channel occupancy with 802.11a/g. However, not all IEEE 802.11n devices may support 40 MHz operation and, therefore, the transition of operation from 20 MHz to 40 MHz should be managed efficiently. In order to achieve this, the IEEE 802.11n standard provides some channel management mechanisms.
[0009] In IEEE802.11n, three operating modes are allowed according to bandwidth and BSS capability: 20 MHz operation, 20/40 MHz operation and Phased Coexistence Operation (PCO). Each of these modes has associated rules of operation. In a 20 MHz operation, all STAs will operate only in a-20 MHz mode whether or not the STAs are 20 MHz or 20/40 MHz capable. In a 20/40 MHz operation, STAs choose the bandwidth by using a transmission channel width action message. In addition, a 40 MHz device will protect its transmission with legacy control frames such as request-to-send (RTS) or clear-to-send (CTS) frames, if the AP of its BSS indicates that there are 20 MHz and/or legacy STAs in the BSS. In the PCO mode, which is an optional mechanism, the BSS
alternates between 20 MHz and 40 MHz modes.
alternates between 20 MHz and 40 MHz modes.
[0010] Although the IEEE 802.11s WLAN mesh standard attempts to remain radio agnostic to the largest extent possible, integration of an IEEE
802.11n high-throughput radio, instead of an 802.11a/b/g, still poses several problems. For example, unlike previous IEEE 802.11a/b/g systems that operate only in 20 MHz bandwidth, IEEE 802.11n operates in both 20 MHz and 40 MHz bandwidths.
802.11n high-throughput radio, instead of an 802.11a/b/g, still poses several problems. For example, unlike previous IEEE 802.11a/b/g systems that operate only in 20 MHz bandwidth, IEEE 802.11n operates in both 20 MHz and 40 MHz bandwidths.
[0011] With Enhanced Distributed Channel Access (EDCA)-based mesh channel access mode, when a mesh point contends and gets an access to the channel, mesh points on a particular link or in a neighborhood have to agree either before the channel access or during the channel access about the specifics of the channelization scheme to be used, (i.e., 20 MHz vs. 40 MHz). Moreover, IEEE 802.11n uses a slightly altered sub-carrier configuration when using full MHz mode, (i.e., using a higher number of data tones when operating in 40 MHz mode compared to dual channel 2x20 MHz 802.11a radios). Dual 2x20 MHz channel operation is also possible for coexistence with legacy radios. Because current IEEE 802.11s technology only allows orthogonal frequency division multiplexing (OFDM) parameters to be communicated to advertise current channel identification to neighbor MPs, the use of IEEE 802.11n radios in an IEEE 802.11s WLAN mesh networks is severely limited due to the limitation with legacy 20 MHz mode even if an IEEE 802.11n radio is used.
[0012] Another problem with the current IEEE 802.11s WLAN mesh networks is the set-up and configuration of a particular mesh link, a neighborhood in the mesh or the entire mesh network with respect to high-throughput channelization modes and configurations to be used. For example, it is currently not possible to prevent or allow the use of 40 MHz access in either version (full 40 MHz or 2x20 MHz) on a particular link, in a mesh neighborhood, or for the entire mesh. This is a limitation with the current IEEE 802.11s technology in the sense that it constitutes an obstacle towards efficient use of 802.11n radios and all the proposed IEEE 802.11n enhancements with WLAN
mesh technology.
mesh technology.
[0013] Therefore, it would be desirable to have a scheme to overcome the above shortcomings and allow efficient integration of IEEE 802.11n radios into IEEE 802.11s WLAN mesh networks.
[0014] SUMMARY
[0015] The present invention is related to high throughput channel operation in a mesh WLAN. A mesh network comprises a plurality of mesh points and a network management entity (NME). The NME is configured to retrieve capability and configuration data from the mesh points. The NME
configures at least one mesh point with respect to IEEE 802.1 ln channelization and legacy protection mode based on the capability and configuration data.
configures at least one mesh point with respect to IEEE 802.1 ln channelization and legacy protection mode based on the capability and configuration data.
[0016] BRIEF DESCRIPTION OF THE DRAWING
[0017] A more detailed understanding of the invention may be had from the following description of a preferred embodiment, given by way of example and to be understood in con,junction with the accompanying drawing wherein:
[0018] Figure 1 is a diagram of a mesh network in accordance with the present invention.
[0019] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0020] When referred to hereafter, the terminology "STA" includes but is not limited to a wireless transmitJreceive unit (WTRU), a user equipment (UE), a fixed or mobile subscriber unit, a pager, a cellular telephone, a personal digital assistant (PDA), a computer, or any other type of user device capable of operating in a wireless environment. When referred to hereafter, the terminology "AP"
includes but is not limited to a Node-B, a site controller, a base station, or any other type of interfacing device capable of operating in a wireless environment.
includes but is not limited to a Node-B, a site controller, a base station, or any other type of interfacing device capable of operating in a wireless environment.
[0021] Figure 1 is a diagram of a mesh network 100 in accordance with the present invention. The mesh network 100 comprises a plurality of mesh points 102-118. The mesh network 100 may include a mesh portal 102. The mesh portal 102 is a mesh point that has a connection with an external network, (e.g., a wired network). Some of the mesh points may be mesh APs 112-118. Each of the mesh APs 112-118 is a mesh point that also works as an AP in its own BSS
132-138. On one side, the mesh AP 112-118 acts as a non-mesh AP to serve STAs 120-126 in its BSS, and on the other side, the mesh AP 112-118 acts as a wireless bridge to receive, forward and route packets through the mesh network 100. An NME 140 is provided to the mesh network 100. The NME 140 may be included in one or more mesh points 102-118 in the mesh network 100. For illustration purposes, Figure 1 shows only one NME 140 located in mesh point 104.
However, the NME may be located in any mesh point 102-118 and more than one NME may be provided to the mesh network 100. Alternatively, the NME 140 may be located out of the mesh network 100 and communicate with the mesh network 100 through the mesh portal 102. Among the mesh points 102-118, at least one mesh point is IEEE 802. 1 ln-capable.
132-138. On one side, the mesh AP 112-118 acts as a non-mesh AP to serve STAs 120-126 in its BSS, and on the other side, the mesh AP 112-118 acts as a wireless bridge to receive, forward and route packets through the mesh network 100. An NME 140 is provided to the mesh network 100. The NME 140 may be included in one or more mesh points 102-118 in the mesh network 100. For illustration purposes, Figure 1 shows only one NME 140 located in mesh point 104.
However, the NME may be located in any mesh point 102-118 and more than one NME may be provided to the mesh network 100. Alternatively, the NME 140 may be located out of the mesh network 100 and communicate with the mesh network 100 through the mesh portal 102. Among the mesh points 102-118, at least one mesh point is IEEE 802. 1 ln-capable.
[0022] The NME 140 retrieves capability and configuration data from the mesh points 102-118 and configures the mesh points 102-118 with respect to IEEE 802. l ln channelization mode, (i.e., 20 MHz, 2x20 MHz, or 40 MHz), legacy protection mode and any other configuration for a particular mesh link, a particular mesh point, a subset of mesh points in the mesh network 100, or the entire mesh network 100. The mesh points 102-118 may be divided into subsets based on a particular link or any other logical criteria. For example, if the NME
140 knows from capability and configuration data from the mesh points 102-118 that there is one or more mesh points that use the legacy physical layer transmission format, (e.g., IEEE 802.11a/b/g), and/or legacy STAs in the mesh network 100 or a subset of the mesh network 100, the NME 140 configures the mesh points in the vicinity of such mesh points and STAs to use legacy physical layer transmission format, (e.g., legacy RTS/CTS frames), to precede any transmissions from IEEE 802.11n-based mesh points. For example, a mesh point using a 40 MHz bandwidth, (i.e., an MP using IEEE 802.11n physical layer transmission format), will protect its transmission with legacy control frames, such as request-to-send (RTS) or clear-to-send (CTS) frames.
140 knows from capability and configuration data from the mesh points 102-118 that there is one or more mesh points that use the legacy physical layer transmission format, (e.g., IEEE 802.11a/b/g), and/or legacy STAs in the mesh network 100 or a subset of the mesh network 100, the NME 140 configures the mesh points in the vicinity of such mesh points and STAs to use legacy physical layer transmission format, (e.g., legacy RTS/CTS frames), to precede any transmissions from IEEE 802.11n-based mesh points. For example, a mesh point using a 40 MHz bandwidth, (i.e., an MP using IEEE 802.11n physical layer transmission format), will protect its transmission with legacy control frames, such as request-to-send (RTS) or clear-to-send (CTS) frames.
[0023] Exemplary capability and configuration data that may be retrieved by the NME 140 is shown in Table 1. The NME 140 configures the mesh points 102-118 such that either the mesh network 100is coherent and similar capabilities are supported across the whole mesh network 100 to support the minimum common parameter, or at least peer mesh points in a particular wireless link are configured coherently.
802.1 ln Enhancements Required Level of Support Physical (PHY) level Mandatory.
spoofing The length field of the legacy signal (L-SIG) field of a mixed mode packet shall have a value equivalent to the duration of the current physical level convergence procedure protocol data unit (PPDU) when L-SIG
transmission o rtuni (TXOP) protection is not used.
Mechanisms to manage Mandatory coexistence of 20 and 40 Both transmitter and receiver shall support MHz channels.
Channel management and Mandatory selection methods. Both transmitter and receiver shall support Reduced Inter-Frame Mandatory S acin (RIFS) Protection Green Field Protection Mandatory Space time block codes STBC Control Frames allow stations to associate beyond (STBC) Control Frames the non-STBC range.
L-SIG TXOP Protection Optional TXOP protection through L-SIG.
PCO (Phased Coexistence Optional Operation) PCO is an optional BSS mode with alternating 20 MHz phase and 40 MHz phase controlled by PCO AP. A PCO
capable STA may associate with the BSS as a PCO STA.
Table 1 [0024] The capability and configuration data of the mesh points 102-118 may be stored in a data base in a mesh point 102-118, or in the NME 140.
Alternatively, the database may reside outside the mesh network 100.
802.1 ln Enhancements Required Level of Support Physical (PHY) level Mandatory.
spoofing The length field of the legacy signal (L-SIG) field of a mixed mode packet shall have a value equivalent to the duration of the current physical level convergence procedure protocol data unit (PPDU) when L-SIG
transmission o rtuni (TXOP) protection is not used.
Mechanisms to manage Mandatory coexistence of 20 and 40 Both transmitter and receiver shall support MHz channels.
Channel management and Mandatory selection methods. Both transmitter and receiver shall support Reduced Inter-Frame Mandatory S acin (RIFS) Protection Green Field Protection Mandatory Space time block codes STBC Control Frames allow stations to associate beyond (STBC) Control Frames the non-STBC range.
L-SIG TXOP Protection Optional TXOP protection through L-SIG.
PCO (Phased Coexistence Optional Operation) PCO is an optional BSS mode with alternating 20 MHz phase and 40 MHz phase controlled by PCO AP. A PCO
capable STA may associate with the BSS as a PCO STA.
Table 1 [0024] The capability and configuration data of the mesh points 102-118 may be stored in a data base in a mesh point 102-118, or in the NME 140.
Alternatively, the database may reside outside the mesh network 100.
[0025] The NME 140 may request the capability and configuration data from the mesh points 102-118 during the association process, or shortly after the mesh point 102-118 undergoes an association process with the mesh network 100.
The retrieval of the capability and configuration data may be a part of the association process, or may be performed separately. The mesh points 102-118 may send the capability and configuration data in response to a request from the NME 140. Alternatively, the mesh points 102-118 may report the capability and configuration data to the NME 140 without solicitation from the NME 140.
Polling may be used to trigger the reporting of the capability and configuration data.
[00261 The NME 140 configures all or part of the mesh network 100 with respect to IEEE 802.11n channelization mode, (i.e., 20 MHz, 2x20 MHz, or 40 MHz), configuration, and legacy protection mode based on the capability and configuration data collected from the mesh points 102-118. The configuration may be coupled to a timer such that the configuration is valid for only a certain period of time. The timer may be triggered by a certain event, such as detection of a legacy STA. The configuration may be updated periodically. The NME 140 may configure a particular mesh link, a set of mesh link, a subset of mesh points, or the entire mesh network. The current configuration data, (i.e., IEEE
802.11n channelization mode, legacy protection mode, capability support, capability settings, configured conditions, (e.g., timers or events), and the like), of the mesh points 102-118 may be stored in a database, (e.g., management information base (MIB)), on the mesh points 102-118 or the NME 140.
[00271 The NME 140 may configure the mesh points 102-118 using a dedicated message exchange. Alternatively, the NME 140 may use multicast or broadcast messages to configure the mesh points 102-118. The signalling for the configuration may be performed using a conventional network signaling protocol at any layer of the protocol processing stack. For example, a simple network management protocol (SNMP) over user datagram protocol (UDP) over Internet Protocol (IP) may be used. Alternatively, layer 2 (L2) signalling frames of Eithertype or IEEE 802.3 or 802.11 type may be used.
[0028] IEEE 802.1 ln capable devices may use the 40 MHz option occupying another 20 MHz channel, (i.e., extension channel). In such case, a channel collision may occur on the extension channel. In order to avoid channel collision, the IEEE 802.1 ln-capable mesh points may block the extension channel for the 40 MHz operation from their channel map either by statically, semi-dynamically, or dynamically.
[0029] For the static configuration, the extension channel is marked as unavailable for IEEE 802.11n-capable mesh points during the start-up configuration. This may be pre-configured, for instance, by the service provider, through a subscriber identity module (SIM)-card-like configuration, or through a softwareldriver download.
[0030] For the semi-dynamic configuration, the extension channel may be marked as unavailable by exchanging specific configuration information, (e.g., management frames, SNMP to MIB, or the like), between the IEEE 802.11n-capable mesh points and other mesh points. The extension channel may be set unavailable when collisions are detected. Collisions may be detected based on collected statistics. By way of example, SNMP and MIB are conventional and associated mechanisms that can be used. This configuration changes may happen when an IEEE 802. 1 ln-capable mesh point joins the mesh network.
Alternatively, the allowed, disallowed, or recommended channel or channel width configuration, legacy protection mode may be communicated between the mesh points during the association process.
[0031] For the dynamic configuration, the extension channel may be blocked in real-time and for a limited time, (e.g., channel coordination window, or a specific period), by exchanging control or management frames. For example, a mesh point wishing to use the extension channel may send a control frame marking the extension channel as used for the current period.
[0032] A mesh point wishing to block the extension channel from being used by the IEEE 802.11n-capable mesh points may send control or management frames to other mesh points, (for example, when a collision is detected on the extension channel). For this purpose, a new control frame may be defined to declare collision in the extension channel. Alternatively, a conventional congestion control message may be used for this purpose.
[0033] Similarly and for both the CCF and the EDCA-based mesh access modes, mesh points may communicate through L2 messages their intention to use 20 MHz, 2x20 MHz, or 40 MHz operation to neighboring mesh points, a subset of the mesh points in the mesh network, or the entire mesh network that they intend to use a particular channel configuration, legacy protection mode during the upcoming TXOP, channel access window, or allocated channel access time.
[0034] The L2 messages may be unicast, multicast or broadcast messages.
The message may be management frames, control-frames, or any other type of frames. The L2 messages may be used either shortly preceding a channel access attempt, (such as when MRTS/MCTS is used), or be part of signalling frames exchanged during the channel access itself.
[0035] Mesh points may periodically send information about anticipated, advertised, or observed channel configuration through L2 messages to one or more neighboring mesh points, a subset of mesh points in the mesh network, or the entire mesh network. For example, a mesh point may inform one or more other mesh points that a particular channel configuration is valid for a particular TXOP, a period of time, or until occurrence of a certain event to another mesh point through the L2 messages.
[0036] A mesh point, upon learning channel configuration of a particular neighbor mesh point either through configuration by the NME 140 or from message exchange with other mesh points of the mesh network, establishes a database which maps the mesh points to specific IEEE 802.1ln channelization mode, (i.e., 20 MHz, 2 x 20 MHz, or 40 MHz), configuration, and legacy protection mode. The mesh point uses this database whenever the mesh point attempts to access a channel to choose an optimum channel and/or bandwidth. The database may also be used to determine routing or forwarding paths through the mesh network.
[0037] Embodiments.
[0038] 1. A mesh network comprising a plurality of mesh points.
[0039] 2. The mesh network of embodiment 1 further comprising an NME configured to retrieve capability and configuration data from the mesh points and configure at least one mesh point with respect to IEEE 802.11n channelization and legacy protection mode based on the capability and configuration data.
[0040] 3. The mesh network of embodiment 2 wherein the capability and configuration data includes information regarding at least one of PHY
level spoofing.
[0041] 4. The mesh network as in any one of embodiments 2-3, wherein the capability and configuration data includes information regarding mechanisms to manage coexistence of 20 MHz and 40 MHz channels.
[0042] 5. The mesh network as in any one of embodiments 2-4, wherein the capability and configuration data includes information regarding management and channel selection methods.
[0043] 6. The mesh network as in any one of embodiments 2-5, wherein the capability and configuration data includes information regarding RIFS
protection.
[0044] 7. The mesh network as in any one of embodiments 2-6, wherein the capability and configuration data includes information regarding green field protection.
[0045] 8. The mesh network as in any one of embodiments 2-7, wherein the capability and configuration data includes information regarding STBC
control frames.
[0046] 9. The mesh network as in any one of embodiments 2-8, wherein the capability and configuration data includes information regarding L-SIG
TXOP protection.
[0047] 10. The mesh network as in any one of embodiments 2-9, wherein the capability and configuration data includes information regarding PCO.
[0048] 11. The mesh network as in any one of embodiments 2-10, wherein the capability and configuration data of the mesh points is stored in a data base in the mesh points.
[0049] 12. The mesh network as in any one of embodiments 2-10, wherein the capability and configuration data of the mesh points is stored in a database outside the mesh network.
[0050] 13. The mesh network as in any one of embodiments 2-12, wherein the capability and configuration data is retrieved from the mesh points during or after an association process.
[0051] 14. The mesh network as in any one of embodiments 2-13, wherein the NME sends a request to the mesh points for retrieving the capability and configuration data.
[0052] 15. The mesh network as in any one of embodiments 2-13, wherein the mesh points send the capability and configuration data in response to the request.
[0053] 16. The mesh network as in any one of embodiments 2-13, wherein the mesh points report the capability and configuration data to the NME
without a request from the NME.
[0054] 17. The mesh network as in any one of embodiments 2-16, wherein configuration for the mesh points is coupled to a timer such that the configuration is valid for only a certain period of time.
[0055] 18. The mesh network of embodiment 17 wherein the timer is triggered by a predetermined event.
[0056] 19. The mesh network as in any one of embodiments 2-18, wherein configuration for the mesh points is updated periodically.
[0057] 20. The mesh network as in any one of embodiments 2-19, wherein the NME configures one of a particular mesh link.
[0058] 21. The mesh network as in any one of embodiments 2-19, wherein the NME configures a subset of the mesh points.
[0059] 22. The mesh network as in any one of embodiments 2-19, wherein the NME configures the entire mesh network.
[0060] 23. The mesh network as in any one of embodiments 2-22, wherein information regarding configuration of the mesh points is stored in a database on at least one of the NME and the mesh points.
[0061] 24. The mesh network as in any one of embodiments 2-23, wherein the NME configures the mesh points using a dedicated message exchange.
[0062] 25. The mesh network as in any one of embodiments 2-23, wherein the NME configures the mesh points using one of multicast messages and broadcast messages.
[0063] 26. The mesh network as in any one of embodiments 2-23, wherein the NME uses an SNMP to configure the mesh points.
[0064] 27. The mesh network as in any one of embodiments 2-23, wherein the NME uses L2 signalling frames to configure the mesh points.
[0065] 28. The mesh network as in any one of embodiments 2-27, wherein at least one mesh point blocks an extension channel for 40 MHz operation from its channel map.
[0066] 29. The mesh network of embodiment 28 wherein the extension channel is blocked statically during start-up configuration.
[0067] 30. The mesh network of embodiment of 28 wherein the extension channel is configured by a service provider.
[0068] 31. The mesh network of embodiment 28 wherein the extension channel is configured through a subscriber identity module (SIM)-card-like configuration.
[0069] 32. The mesh network of embodiment 28 wherein the extension channel is configured through a software/driver download.
[0070] 33. The mesh network of claim 28 wherein the extension channel is blocked semi-dynamically in accordance with a configuration message.
[0071] 34. The mesh network of embodiment 33 wherein the mesh points communicate information regarding channel configuration and legacy protection mode with another mesh points during an association process.
[0072] 35. The mesh network of embodiment 33 wherein the extension channel is blocked based on the information.
[0073] 36. The mesh network of embodiment 28 wherein the extension channel is blocked dynamically in real-time.
[0074] 37. The mesh network of embodiment 28 wherein the extension channel is blocked dynamically for a limited time.
[0075] 38. The mesh network of embodiment 28 wherein the mesh point blocks the extension channel based on a message from neighbor mesh points.
[0076] 39. The mesh network of embodiment 38 wherein a congestion control message is used for carrying the message.
[0077] 40. The mesh network of embodiment 38 wherein the mesh points communicate with each other through an L2 message.
[0078] 41. The mesh network of embodiment 40 wherein the L2 message is a unicast message.
[0079] 42. The mesh network of embodiment 40 wherein the L2 message is a multicast message.
[0080] 43. The mesh network as in any one of embodiments 40-42, wherein the L2 may is one of a management frame and a control frame.
[0081] 44. The mesh network as in any one of embodiments 40-43, wherein the L2 message is sent shortly preceding a channel access attempt.
[0082] 45. The mesh network of embodiment 44 wherein the L2 message is sent as a part of signalling frames for channel access.
[0083] 46. The mesh network as in any one of embodiments 2-45, wherein the mesh points are configured to establish a database which maps mesh points in the mesh network to specific IEEE 802.11n channelization and legacy protection mode.
[0084] 47. The mesh network of embodiment 46 wherein the mesh points use the database to choose an optimum channel and bandwidth.
[0085] 48. The mesh network as in any one of embodiments 46-47, wherein the mesh points use the database to determine routing and forwarding paths through the mesh network.
[0086] Although the features and elements of the present invention are described in the preferred embodiments in particular combinations, each feature or element can be used alone without the other features and elements of the preferred embodiments or in various combinations with or without other features and elements of the present invention. The methods or flow charts provided in the present invention may be implemented in a computer program, software, or firmware tangibly embodied in a computer-readable storage medium for execution by a general purpose computer or a processor. Examples of computer-readable storage mediums include a read only memory (ROM), a random access memory (RAM), a register, cache memory, semiconductor memory devices, magnetic media such as internal hard disks and removable disks, magneto-optical media, and optical media such as CD-ROM disks, and digital versatile disks (DVDs).
[0087) Suitable processors include, by way of example, a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) circuits, any other type of integrated circuit (IC), and/or a state machine.
[0088] A processor in association with software may be used to implement a radio frequency transceiver for use in a wireless transmit receive unit (WTRU), user equipment (UE), terminal, base station, radio network controller (RNC), or any host computer. The WTRU may be used in conjunction with modules, implemented in hardware and/or software, such as a camera, a video camera module, a videophone, a speakerphone, a vibration device, a speaker, a microphone, a television transceiver, a hands free headset, a keyboard, a Bluetooth module, a frequency modulated (FM) radio unit, a liquid crystal display (LCD) display unit, an organic light-emitting diode (OLED) display unit, a digital music player, a media player, a video game player module, an Internet browser, and/or any wireless local area network (WLAN) module.
* * *
The retrieval of the capability and configuration data may be a part of the association process, or may be performed separately. The mesh points 102-118 may send the capability and configuration data in response to a request from the NME 140. Alternatively, the mesh points 102-118 may report the capability and configuration data to the NME 140 without solicitation from the NME 140.
Polling may be used to trigger the reporting of the capability and configuration data.
[00261 The NME 140 configures all or part of the mesh network 100 with respect to IEEE 802.11n channelization mode, (i.e., 20 MHz, 2x20 MHz, or 40 MHz), configuration, and legacy protection mode based on the capability and configuration data collected from the mesh points 102-118. The configuration may be coupled to a timer such that the configuration is valid for only a certain period of time. The timer may be triggered by a certain event, such as detection of a legacy STA. The configuration may be updated periodically. The NME 140 may configure a particular mesh link, a set of mesh link, a subset of mesh points, or the entire mesh network. The current configuration data, (i.e., IEEE
802.11n channelization mode, legacy protection mode, capability support, capability settings, configured conditions, (e.g., timers or events), and the like), of the mesh points 102-118 may be stored in a database, (e.g., management information base (MIB)), on the mesh points 102-118 or the NME 140.
[00271 The NME 140 may configure the mesh points 102-118 using a dedicated message exchange. Alternatively, the NME 140 may use multicast or broadcast messages to configure the mesh points 102-118. The signalling for the configuration may be performed using a conventional network signaling protocol at any layer of the protocol processing stack. For example, a simple network management protocol (SNMP) over user datagram protocol (UDP) over Internet Protocol (IP) may be used. Alternatively, layer 2 (L2) signalling frames of Eithertype or IEEE 802.3 or 802.11 type may be used.
[0028] IEEE 802.1 ln capable devices may use the 40 MHz option occupying another 20 MHz channel, (i.e., extension channel). In such case, a channel collision may occur on the extension channel. In order to avoid channel collision, the IEEE 802.1 ln-capable mesh points may block the extension channel for the 40 MHz operation from their channel map either by statically, semi-dynamically, or dynamically.
[0029] For the static configuration, the extension channel is marked as unavailable for IEEE 802.11n-capable mesh points during the start-up configuration. This may be pre-configured, for instance, by the service provider, through a subscriber identity module (SIM)-card-like configuration, or through a softwareldriver download.
[0030] For the semi-dynamic configuration, the extension channel may be marked as unavailable by exchanging specific configuration information, (e.g., management frames, SNMP to MIB, or the like), between the IEEE 802.11n-capable mesh points and other mesh points. The extension channel may be set unavailable when collisions are detected. Collisions may be detected based on collected statistics. By way of example, SNMP and MIB are conventional and associated mechanisms that can be used. This configuration changes may happen when an IEEE 802. 1 ln-capable mesh point joins the mesh network.
Alternatively, the allowed, disallowed, or recommended channel or channel width configuration, legacy protection mode may be communicated between the mesh points during the association process.
[0031] For the dynamic configuration, the extension channel may be blocked in real-time and for a limited time, (e.g., channel coordination window, or a specific period), by exchanging control or management frames. For example, a mesh point wishing to use the extension channel may send a control frame marking the extension channel as used for the current period.
[0032] A mesh point wishing to block the extension channel from being used by the IEEE 802.11n-capable mesh points may send control or management frames to other mesh points, (for example, when a collision is detected on the extension channel). For this purpose, a new control frame may be defined to declare collision in the extension channel. Alternatively, a conventional congestion control message may be used for this purpose.
[0033] Similarly and for both the CCF and the EDCA-based mesh access modes, mesh points may communicate through L2 messages their intention to use 20 MHz, 2x20 MHz, or 40 MHz operation to neighboring mesh points, a subset of the mesh points in the mesh network, or the entire mesh network that they intend to use a particular channel configuration, legacy protection mode during the upcoming TXOP, channel access window, or allocated channel access time.
[0034] The L2 messages may be unicast, multicast or broadcast messages.
The message may be management frames, control-frames, or any other type of frames. The L2 messages may be used either shortly preceding a channel access attempt, (such as when MRTS/MCTS is used), or be part of signalling frames exchanged during the channel access itself.
[0035] Mesh points may periodically send information about anticipated, advertised, or observed channel configuration through L2 messages to one or more neighboring mesh points, a subset of mesh points in the mesh network, or the entire mesh network. For example, a mesh point may inform one or more other mesh points that a particular channel configuration is valid for a particular TXOP, a period of time, or until occurrence of a certain event to another mesh point through the L2 messages.
[0036] A mesh point, upon learning channel configuration of a particular neighbor mesh point either through configuration by the NME 140 or from message exchange with other mesh points of the mesh network, establishes a database which maps the mesh points to specific IEEE 802.1ln channelization mode, (i.e., 20 MHz, 2 x 20 MHz, or 40 MHz), configuration, and legacy protection mode. The mesh point uses this database whenever the mesh point attempts to access a channel to choose an optimum channel and/or bandwidth. The database may also be used to determine routing or forwarding paths through the mesh network.
[0037] Embodiments.
[0038] 1. A mesh network comprising a plurality of mesh points.
[0039] 2. The mesh network of embodiment 1 further comprising an NME configured to retrieve capability and configuration data from the mesh points and configure at least one mesh point with respect to IEEE 802.11n channelization and legacy protection mode based on the capability and configuration data.
[0040] 3. The mesh network of embodiment 2 wherein the capability and configuration data includes information regarding at least one of PHY
level spoofing.
[0041] 4. The mesh network as in any one of embodiments 2-3, wherein the capability and configuration data includes information regarding mechanisms to manage coexistence of 20 MHz and 40 MHz channels.
[0042] 5. The mesh network as in any one of embodiments 2-4, wherein the capability and configuration data includes information regarding management and channel selection methods.
[0043] 6. The mesh network as in any one of embodiments 2-5, wherein the capability and configuration data includes information regarding RIFS
protection.
[0044] 7. The mesh network as in any one of embodiments 2-6, wherein the capability and configuration data includes information regarding green field protection.
[0045] 8. The mesh network as in any one of embodiments 2-7, wherein the capability and configuration data includes information regarding STBC
control frames.
[0046] 9. The mesh network as in any one of embodiments 2-8, wherein the capability and configuration data includes information regarding L-SIG
TXOP protection.
[0047] 10. The mesh network as in any one of embodiments 2-9, wherein the capability and configuration data includes information regarding PCO.
[0048] 11. The mesh network as in any one of embodiments 2-10, wherein the capability and configuration data of the mesh points is stored in a data base in the mesh points.
[0049] 12. The mesh network as in any one of embodiments 2-10, wherein the capability and configuration data of the mesh points is stored in a database outside the mesh network.
[0050] 13. The mesh network as in any one of embodiments 2-12, wherein the capability and configuration data is retrieved from the mesh points during or after an association process.
[0051] 14. The mesh network as in any one of embodiments 2-13, wherein the NME sends a request to the mesh points for retrieving the capability and configuration data.
[0052] 15. The mesh network as in any one of embodiments 2-13, wherein the mesh points send the capability and configuration data in response to the request.
[0053] 16. The mesh network as in any one of embodiments 2-13, wherein the mesh points report the capability and configuration data to the NME
without a request from the NME.
[0054] 17. The mesh network as in any one of embodiments 2-16, wherein configuration for the mesh points is coupled to a timer such that the configuration is valid for only a certain period of time.
[0055] 18. The mesh network of embodiment 17 wherein the timer is triggered by a predetermined event.
[0056] 19. The mesh network as in any one of embodiments 2-18, wherein configuration for the mesh points is updated periodically.
[0057] 20. The mesh network as in any one of embodiments 2-19, wherein the NME configures one of a particular mesh link.
[0058] 21. The mesh network as in any one of embodiments 2-19, wherein the NME configures a subset of the mesh points.
[0059] 22. The mesh network as in any one of embodiments 2-19, wherein the NME configures the entire mesh network.
[0060] 23. The mesh network as in any one of embodiments 2-22, wherein information regarding configuration of the mesh points is stored in a database on at least one of the NME and the mesh points.
[0061] 24. The mesh network as in any one of embodiments 2-23, wherein the NME configures the mesh points using a dedicated message exchange.
[0062] 25. The mesh network as in any one of embodiments 2-23, wherein the NME configures the mesh points using one of multicast messages and broadcast messages.
[0063] 26. The mesh network as in any one of embodiments 2-23, wherein the NME uses an SNMP to configure the mesh points.
[0064] 27. The mesh network as in any one of embodiments 2-23, wherein the NME uses L2 signalling frames to configure the mesh points.
[0065] 28. The mesh network as in any one of embodiments 2-27, wherein at least one mesh point blocks an extension channel for 40 MHz operation from its channel map.
[0066] 29. The mesh network of embodiment 28 wherein the extension channel is blocked statically during start-up configuration.
[0067] 30. The mesh network of embodiment of 28 wherein the extension channel is configured by a service provider.
[0068] 31. The mesh network of embodiment 28 wherein the extension channel is configured through a subscriber identity module (SIM)-card-like configuration.
[0069] 32. The mesh network of embodiment 28 wherein the extension channel is configured through a software/driver download.
[0070] 33. The mesh network of claim 28 wherein the extension channel is blocked semi-dynamically in accordance with a configuration message.
[0071] 34. The mesh network of embodiment 33 wherein the mesh points communicate information regarding channel configuration and legacy protection mode with another mesh points during an association process.
[0072] 35. The mesh network of embodiment 33 wherein the extension channel is blocked based on the information.
[0073] 36. The mesh network of embodiment 28 wherein the extension channel is blocked dynamically in real-time.
[0074] 37. The mesh network of embodiment 28 wherein the extension channel is blocked dynamically for a limited time.
[0075] 38. The mesh network of embodiment 28 wherein the mesh point blocks the extension channel based on a message from neighbor mesh points.
[0076] 39. The mesh network of embodiment 38 wherein a congestion control message is used for carrying the message.
[0077] 40. The mesh network of embodiment 38 wherein the mesh points communicate with each other through an L2 message.
[0078] 41. The mesh network of embodiment 40 wherein the L2 message is a unicast message.
[0079] 42. The mesh network of embodiment 40 wherein the L2 message is a multicast message.
[0080] 43. The mesh network as in any one of embodiments 40-42, wherein the L2 may is one of a management frame and a control frame.
[0081] 44. The mesh network as in any one of embodiments 40-43, wherein the L2 message is sent shortly preceding a channel access attempt.
[0082] 45. The mesh network of embodiment 44 wherein the L2 message is sent as a part of signalling frames for channel access.
[0083] 46. The mesh network as in any one of embodiments 2-45, wherein the mesh points are configured to establish a database which maps mesh points in the mesh network to specific IEEE 802.11n channelization and legacy protection mode.
[0084] 47. The mesh network of embodiment 46 wherein the mesh points use the database to choose an optimum channel and bandwidth.
[0085] 48. The mesh network as in any one of embodiments 46-47, wherein the mesh points use the database to determine routing and forwarding paths through the mesh network.
[0086] Although the features and elements of the present invention are described in the preferred embodiments in particular combinations, each feature or element can be used alone without the other features and elements of the preferred embodiments or in various combinations with or without other features and elements of the present invention. The methods or flow charts provided in the present invention may be implemented in a computer program, software, or firmware tangibly embodied in a computer-readable storage medium for execution by a general purpose computer or a processor. Examples of computer-readable storage mediums include a read only memory (ROM), a random access memory (RAM), a register, cache memory, semiconductor memory devices, magnetic media such as internal hard disks and removable disks, magneto-optical media, and optical media such as CD-ROM disks, and digital versatile disks (DVDs).
[0087) Suitable processors include, by way of example, a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) circuits, any other type of integrated circuit (IC), and/or a state machine.
[0088] A processor in association with software may be used to implement a radio frequency transceiver for use in a wireless transmit receive unit (WTRU), user equipment (UE), terminal, base station, radio network controller (RNC), or any host computer. The WTRU may be used in conjunction with modules, implemented in hardware and/or software, such as a camera, a video camera module, a videophone, a speakerphone, a vibration device, a speaker, a microphone, a television transceiver, a hands free headset, a keyboard, a Bluetooth module, a frequency modulated (FM) radio unit, a liquid crystal display (LCD) display unit, an organic light-emitting diode (OLED) display unit, a digital music player, a media player, a video game player module, an Internet browser, and/or any wireless local area network (WLAN) module.
* * *
Claims (62)
1. An access point (AP) comprising:
a wireless receiver configured to receive, from each of a plurality of wireless transmit receive units (WTRUs), configuration information, wherein configuration information received from at least one of the plurality of WTRUs includes information regarding coexistence of a 20 MHz channel and a 40 MHz channel, green field protection information, space time block coding (STBC) information, and legacy signal field (L-SIG) transmission opportunity (TXOP) protection information; and a wireless transmitter configured to transmit, to at least one of the plurality of WTRUs, instructions for controlling operation of at least one of the plurality of WTRUs regarding IEEE 802.11n channelization and legacy protection, wherein a content of the instructions for controlling the operation of the at least one of the plurality of WTRUs regarding IEEE 802.11n channelization and legacy protection is based at least on the configuration information from each of the plurality of WTRUs.
a wireless receiver configured to receive, from each of a plurality of wireless transmit receive units (WTRUs), configuration information, wherein configuration information received from at least one of the plurality of WTRUs includes information regarding coexistence of a 20 MHz channel and a 40 MHz channel, green field protection information, space time block coding (STBC) information, and legacy signal field (L-SIG) transmission opportunity (TXOP) protection information; and a wireless transmitter configured to transmit, to at least one of the plurality of WTRUs, instructions for controlling operation of at least one of the plurality of WTRUs regarding IEEE 802.11n channelization and legacy protection, wherein a content of the instructions for controlling the operation of the at least one of the plurality of WTRUs regarding IEEE 802.11n channelization and legacy protection is based at least on the configuration information from each of the plurality of WTRUs.
2. The AP of claim 1, wherein the configuration information received from at least one of the plurality of WTRUs further includes information regarding at least one of physical layer spoofing, reduced inter-frame spacing (RIFS) protection and phased coexistence operation (PCO).
3. The AP of claim 1, wherein the wireless receiver is further configured to wirelessly receive the configuration information from each of the plurality of WTRUs during or after an association process.
4. The AP of claim 1, wherein the wireless transmitter is further configured to wirelessly transmit a request for configuration information to at least one of the plurality of WTRUs; and the wireless receiver is further configured to wirelessly receive the configuration information in response to the request.
5. The AP of claim 1, wherein the wireless receiver is configured to wirelessly receive periodic updates of the configuration information from each of the plurality of WTRUs and the wireless transmitter is further configured to wirelessly transmit periodic updates of the instructions for controlling operation of the at least one of the plurality of WTRUs to the at least one of the plurality of WTRUs.
6. The AP of claim 1, wherein the wireless transmitter is configured to transmit the instructions for controlling operation of the at least one of the plurality of WTRUs using at least one of a dedicated message exchange, a multicast message, or a simple network management protocol.
7. The AP of claim 1, wherein the AP is configured to receive a software/driver download comprising extension channel configuration data.
8. The AP of claim 1, wherein the instructions for controlling the operation of the at least one of the plurality of WTRUs comprises extension channel block command information, and the wireless transmitter is configured to wirelessly transmit the extension channel block command information during an association process.
9. The AP of claim 8, wherein the wireless transmitter is configured to wirelessly transmit a congestion control message, wherein the congestion control message includes the extension channel block command information.
10. The AP of claim 1, wherein the configuration information received from at least one of the plurality of WTRUs includes information regarding mechanisms to manage channel management and channel selection methods.
11. The AP of claim 1, wherein the wireless receiver and the wireless transmitter are configured to operate at a channel bandwidth of 20 MHz or 40 MHz.
12. An wireless transmit and receive unit (WTRU) comprising:
a wireless transmitter configured to transmit configuration information, wherein the configuration information includes information regarding coexistence of a 20 MHz channel and a 40 MHz channel, green field protection information, space time block coding (STBC) information, and legacy signal field (L-SIG) transmission opportunity (TXOP) protection information; and a wireless receiver configured to receive instructions for controlling operation of the WTRU regarding IEEE 802.11n channelization and legacy protection, wherein a content of the instructions for controlling the operation of the WTRU regarding IEEE 802.11n channelization and legacy protection is based at least on the configuration information.
a wireless transmitter configured to transmit configuration information, wherein the configuration information includes information regarding coexistence of a 20 MHz channel and a 40 MHz channel, green field protection information, space time block coding (STBC) information, and legacy signal field (L-SIG) transmission opportunity (TXOP) protection information; and a wireless receiver configured to receive instructions for controlling operation of the WTRU regarding IEEE 802.11n channelization and legacy protection, wherein a content of the instructions for controlling the operation of the WTRU regarding IEEE 802.11n channelization and legacy protection is based at least on the configuration information.
13. The WTRU of claim 12, wherein the configuration information further includes information regarding at least one of physical layer spoofing, reduced inter-frame spacing (RIFS) protection and phased coexistence operation (PCO).
14. The WTRU of claim 12, wherein the wireless transmitter is further configured to wirelessly transmit the configuration information during or after an association process.
15. The WTRU of claim 12, wherein the wireless receiver is further configured to wirelessly receive a request for the configuration information;
and the wireless transmitter is further configured to wirelessly transmit the configuration information in response to the request.
and the wireless transmitter is further configured to wirelessly transmit the configuration information in response to the request.
16. The WTRU of claim 12, wherein the wireless transmitter is configured to wirelessly transmit periodic updates of the configuration information and the wireless receiver is further configured to wirelessly receive periodic updates of the instructions for controlling operation of the WTRU.
17. The WTRU of claim 12, wherein the wireless receiver is configured to receive the instructions for controlling operation of the WTRU
from at least one of a dedicated message exchange, a multicast message, or a simple network management protocol.
from at least one of a dedicated message exchange, a multicast message, or a simple network management protocol.
18. The WTRU of claim 12, wherein the instructions for controlling the operation of the WTRU comprises extension channel block command information, and the wireless receiver is configured to wirelessly receive the extension channel block command information during an association process.
19. The WTRU of claim 18, wherein the wireless receiver is configured to wirelessly receive a congestion control message, wherein the congestion control message includes the extension channel block command information.
20. The WTRU of claim 12, wherein the configuration information includes information regarding mechanisms to manage channel management and channel selection methods.
21. The WTRU of claim 12, wherein the wireless transmitter and the wireless receiver are configured to operate at a channel bandwidth of 20 MHz or 40 MHz.
22. A wireless transmit/receive unit (WTRU) configured as a node on a mesh network, wherein the WTRU comprises:
a radio configured to operate at 20 Mhz or 40 Mhz, a receiver configured to retrieve a plurality of capability and configuration data from a plurality of WTRUs in a mesh network, wherein the capability and configuration data includes information regarding mechanisms to manage:
a coexistence of 20 Mhz and 40 Mhz channels;
channel management; and channel selection methods;
a memory unit configured to store the capability and configuration data;
and a transmitter configured to transmit to at least one of the plurality of WTRUs at least one set of node-specific configuration data comprising channelization and legacy protection data based on the capability and configuration data.
a radio configured to operate at 20 Mhz or 40 Mhz, a receiver configured to retrieve a plurality of capability and configuration data from a plurality of WTRUs in a mesh network, wherein the capability and configuration data includes information regarding mechanisms to manage:
a coexistence of 20 Mhz and 40 Mhz channels;
channel management; and channel selection methods;
a memory unit configured to store the capability and configuration data;
and a transmitter configured to transmit to at least one of the plurality of WTRUs at least one set of node-specific configuration data comprising channelization and legacy protection data based on the capability and configuration data.
23. The WTRU as in claim 22 wherein the capability and configuration data further includes information regarding at least one of:
physical (PHY) level spoofing;
reduced inter-frame spacing (RIFS) protection;
green field protection;
space time block coding (STBC) control frame;
legacy signal field (L-SIG) transmission opportunity (TXOP) protection; and phased coexistence operation (PCO).
physical (PHY) level spoofing;
reduced inter-frame spacing (RIFS) protection;
green field protection;
space time block coding (STBC) control frame;
legacy signal field (L-SIG) transmission opportunity (TXOP) protection; and phased coexistence operation (PCO).
24. The WTRU as in claim 22 wherein the WTRU is configured to retrieve the capability and configuration data during or after an association process.
25. The WTRU as in claim 22 wherein the WTRU is further configured to:
send a request to retrieve capability and configuration data to at least one of the plurality of WTRUs in a mesh network;
and receive capability and configuration data in response to the request.
send a request to retrieve capability and configuration data to at least one of the plurality of WTRUs in a mesh network;
and receive capability and configuration data in response to the request.
26. The WTRU as in claim 22 further comprising a timer wherein the timer is coupled to a mesh point configuration such that the mesh point configuration is valid for set period of time.
27. The WTRU as in claim 26 wherein the timer is triggered by a predetermined event.
28. The WTRU as in claim 22 wherein the WTRU is configured to receive periodic updates of the capability and configuration data.
29. The WTRU as in claim 22 wherein the WTRU is configured to transmit periodic updates of the capability and configuration data to the plurality of WTRUs in the mesh network.
30. The WTRU as in claim 22 wherein the WTRU is further configured to transmit to a mesh link, a set of mesh links, a mesh node, a set of mesh nodes and an entire mesh network .
31. The WTRU as in claim 22 wherein the WTRU is configured to transmit node-specific data using a dedicated message exchange.
32. The WTRU as in claim 22 wherein the WTRU is configured to transmit node-specific data in a multicast message.
33. The WTRU as in claim 22 wherein the WTRU is configured to transmit node-specific data using simple network management protocol (SNMP).
34. The WTRU as in claim 22 wherein the WTRU is configured to transmit node-specific data using layer 2 (L2) signaling frames.
35. The WTRU as in claim 22 wherein the WTRU is configured to block an extension channel for 40 MHz operation from its channel map.
36. The WTRU as in claim 35 wherein the WTRU is configured to block the extension channel statically during start-up configuration.
37. The WTRU as in claim 35 wherein the WTRU is configured to receive extension channel configuration data from a service provider.
38. The WTRU as in claim 35 wherein the WTRU is configured to retrieve extension channel configuration data from a subscriber identity module (SIM).
39. The WTRU as in claim 35 wherein the WTRU is configured to receive a software/driver download comprising extension channel configuration data.
40. The WTRU as in claim 22 wherein the node-specific configuration data comprises extension channel block command information and the WTRU
is configured to transmit the extension channel block command information during an association process.
is configured to transmit the extension channel block command information during an association process.
41. The WTRU as in claim 40 wherein the WTRU is configured to transmit a congestion control message wherein the congestion control message includes the extension channel block command information.
42. An access point (AP) comprising:
a wireless receiver configured to receive, from each of a plurality of wireless transmit receive units (WTRUs), information about at least one configuration of each of the plurality of WTRUs regarding coexistence of a 20 MHz channel and a 40 MHz channel; and a wireless transmitter configured to transmit, to at least one of the plurality of WTRUs, instructions for controlling operation of the at least one of the plurality of WTRUs regarding IEEE 802.11n channelization and legacy protection, wherein a content of the instructions for controlling the operation of the at least one of the plurality of WTRUs regarding IEEE 802.11n channelization and legacy protection is based at least on the information about the at least one configuration of each of the WTRUs regarding the coexistence of the 20 MHz channel and the 40 MHz channel.
a wireless receiver configured to receive, from each of a plurality of wireless transmit receive units (WTRUs), information about at least one configuration of each of the plurality of WTRUs regarding coexistence of a 20 MHz channel and a 40 MHz channel; and a wireless transmitter configured to transmit, to at least one of the plurality of WTRUs, instructions for controlling operation of the at least one of the plurality of WTRUs regarding IEEE 802.11n channelization and legacy protection, wherein a content of the instructions for controlling the operation of the at least one of the plurality of WTRUs regarding IEEE 802.11n channelization and legacy protection is based at least on the information about the at least one configuration of each of the WTRUs regarding the coexistence of the 20 MHz channel and the 40 MHz channel.
43. The AP of claim 42, wherein the information about the at least one configuration of each of the plurality of WTRUs further includes information regarding at least one of physical layer spoofing, reduced inter-frame spacing (RIFS) protection, green field protection, space time block coding (STBC) control frame, legacy signal field (L-SIG) transmission opportunity (TXOP) protection, and phased coexistence operation (PCO).
44. The AP of claim 42, wherein the wireless receiver is further configured to wirelessly receive the information about the at least one configuration of each of the plurality of WTRUs during or after an association process.
45. The AP of claim 42, wherein the wireless transmitter is further configured to wirelessly transmit a request for the instructions for controlling the operation of the at least one of the plurality of WTRUs to at least one of the plurality of WTRUs, and the wireless receiver is further configured to wirelessly receive the instructions for controlling the operation of the at least one of the plurality of WTRUs in response to the request.
46. The AP of claim 42, wherein the wireless receiver is further configured to wirelessly receive periodic updates of the information about the at least one configuration of each of the plurality of WTRUs, and the wireless transmitter is further configured to wirelessly transmit periodic updates of the instructions for controlling operation of the at least one of the plurality of WTRUs to the at least one of the plurality of WTRUs.
47. The AP of claim 42, wherein the wireless transmitter is further configured to transmit the instructions for controlling operation of the at least one of the plurality of WTRUs using at least one of a dedicated message exchange, a multicast message, or a simple network management protocol.
48. The AP of claim 42, wherein the wireless receiver is further configured to wirelessly receive a software/driver download comprising extension channel configuration data.
49. The AP of claim 42, wherein the instructions for controlling the operation of the at least one of the plurality of WTRUs comprises extension channel block command information, and the wireless transmitter is further configured to wirelessly transmit the extension channel block command information during an association process.
50. The AP of claim 49, wherein the wireless transmitter is further configured to wirelessly transmit a congestion control message, wherein the congestion control message includes the extension channel block command information.
51. The AP of claim 42, wherein the information about the at least one configuration of each of the plurality of WTRUs includes information regarding mechanisms to manage channel management and channel selection methods.
52. The AP of claim 42, wherein the wireless receiver and the wireless transmitter are configured to operate at a channel bandwidth of 20 Mhz or 40 Mhz.
53. A wireless transmit/receive unit (WTRU) comprising:
a transmitter configured to transmit, to an access point (AP), information about at least one configuration of the WTRU regarding coexistence of a 20 MHz channel and a 40 MHz channel; and a receiver configured to receive, from the AP, instructions for controlling operation of the WTRU regarding IEEE 802.11n channelization and legacy protection, wherein a content of the instructions for controlling the operation of the WTRU regarding IEEE 802.11n channelization and legacy protection is based at least on the information about the at least one configuration of the WTRU regarding the coexistence of the 20 MHz channel and the 40 MHz channel.
a transmitter configured to transmit, to an access point (AP), information about at least one configuration of the WTRU regarding coexistence of a 20 MHz channel and a 40 MHz channel; and a receiver configured to receive, from the AP, instructions for controlling operation of the WTRU regarding IEEE 802.11n channelization and legacy protection, wherein a content of the instructions for controlling the operation of the WTRU regarding IEEE 802.11n channelization and legacy protection is based at least on the information about the at least one configuration of the WTRU regarding the coexistence of the 20 MHz channel and the 40 MHz channel.
54. The WTRU of claim 53, wherein the information about the at least one configuration of the WTRU further includes information regarding at least one of physical layer spoofing, reduced inter-frame spacing (RIFS) protection, green field protection, space time block coding (STBC) control frame, legacy signal field (L-SIG) transmission opportunity (TXOP) protection, and phased coexistence operation (PCO).
55. The WTRU of claim 53, wherein the transmitter is further configured to transmit the information about the at least one configuration of the WTRU during or after an association process.
56. The WTRU of claim 53, wherein the transmitter is further configured to transmit a request for the instructions for controlling the operation of the WTRU to the AP, and the receiver is further configured to receive the instructions for controlling the operation of the WTRU from the AP
in response to the request.
in response to the request.
57. The WTRU of claim 53, wherein the transmitter is further configured to transmit periodic updates of the information about the at least one configuration of the WTRU to AP, and the receiver is further configured to receive periodic updates of the instructions for controlling operation of the WTRU from the AP.
58. The WTRU of claim 54, wherein the receiver is further configured to receive the instructions for controlling operation of the WTRU via at least one of a dedicated message exchange, multicast messaging, or a simple network management protocol.
59. The WTRU of claim 54, wherein the instructions for controlling the operation of the WTRU comprise extension channel block command information, and the receiver is further configured to receive the extension channel block command information during an association process.
60. The WTRU of claim 59, wherein the receiver is further configured to receive a congestion control message, wherein the congestion control message includes the extension channel block command information.
61. The WTRU of claim 54, wherein the information about the at least one configuration of the WTRU includes information regarding mechanisms to manage channel management and channel selection methods.
62. The WTRU of claim 54, wherein the transmitter and the receiver are configured to operate at a channel bandwidth of 20 Mhz or 40 Mhz.
Applications Claiming Priority (3)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US79460406P | 2006-04-25 | 2006-04-25 | |
| US60/794,604 | 2006-04-25 | ||
| PCT/US2007/010149 WO2007127312A2 (en) | 2006-04-25 | 2007-04-24 | High-throughput channel operation in a mesh wireless local area network |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CA2650436A1 CA2650436A1 (en) | 2007-11-08 |
| CA2650436C true CA2650436C (en) | 2013-12-17 |
Family
ID=38561595
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CA2650436A Expired - Fee Related CA2650436C (en) | 2006-04-25 | 2007-04-24 | High-throughput channel operation in a mesh wireless local area network |
Country Status (19)
| Country | Link |
|---|---|
| US (2) | US8542613B2 (en) |
| EP (3) | EP2207314B1 (en) |
| JP (5) | JP4751947B2 (en) |
| KR (8) | KR101517705B1 (en) |
| CN (2) | CN104917636A (en) |
| AR (1) | AR060818A1 (en) |
| AT (2) | ATE469482T1 (en) |
| AU (1) | AU2007243313B2 (en) |
| BR (1) | BRPI0710388A2 (en) |
| CA (1) | CA2650436C (en) |
| DE (1) | DE602007006785D1 (en) |
| DK (1) | DK2207314T3 (en) |
| ES (1) | ES2397675T3 (en) |
| IL (1) | IL194644A (en) |
| MX (1) | MX2008013679A (en) |
| MY (2) | MY140789A (en) |
| RU (1) | RU2400935C2 (en) |
| TW (3) | TWI454113B (en) |
| WO (1) | WO2007127312A2 (en) |
Families Citing this family (31)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2008046089A2 (en) * | 2006-10-13 | 2008-04-17 | Firetide, Inc. | Mesh node mobility across static and mobile mesh networks |
| JP4284354B2 (en) * | 2006-12-26 | 2009-06-24 | 株式会社東芝 | Wireless communication device |
| JP4517060B2 (en) * | 2007-10-25 | 2010-08-04 | 日本電気通信システム株式会社 | Wireless device and mesh network including the same |
| CN101849386B (en) * | 2007-11-01 | 2013-09-04 | Lg电子株式会社 | Procedure of setting up peer link in wireless mesh network and wireless station supporting the same |
| CN101911601B (en) * | 2007-11-08 | 2013-01-02 | Lg电子株式会社 | Data transmission method in wireless mesh network and A-MSDU format |
| US9253742B1 (en) * | 2007-11-29 | 2016-02-02 | Qualcomm Incorporated | Fine timing for high throughput packets |
| US9232389B2 (en) * | 2008-06-11 | 2016-01-05 | Marvell World Trade Ltd. | Mixed mode security for mesh networks |
| US8374080B2 (en) | 2009-01-14 | 2013-02-12 | Stmicroelectronics, Inc. | High throughput features in 11S mesh networks |
| KR101341192B1 (en) * | 2010-02-09 | 2013-12-12 | 엘지전자 주식회사 | Method and apparatus of channel access in wireless local area network |
| US9025544B2 (en) | 2010-02-10 | 2015-05-05 | Lg Electronics Inc. | Channel access method and apparatus in wireless local area network system |
| EP2589164B1 (en) * | 2010-06-29 | 2016-08-10 | LG Electronics Inc. | Method and apparatus for transmitting data frame in wlan system |
| WO2014005939A1 (en) * | 2012-07-05 | 2014-01-09 | Iminds Vzw | Methods for configuring a device for establishing a first wireless link with a network. |
| EP2936849B1 (en) * | 2012-12-20 | 2016-11-16 | Telefonaktiebolaget LM Ericsson (publ) | Integrating multi-hop mesh networks in mobile communication networks |
| US9271241B2 (en) | 2013-11-19 | 2016-02-23 | Intel IP Corporation | Access point and methods for distinguishing HEW physical layer packets with backwards compatibility |
| US9325463B2 (en) | 2013-11-19 | 2016-04-26 | Intel IP Corporation | High-efficiency WLAN (HEW) master station and methods to increase information bits for HEW communication |
| US9544914B2 (en) | 2013-11-19 | 2017-01-10 | Intel IP Corporation | Master station and method for HEW communication using a transmission signaling structure for a HEW signal field |
| CN106063146A (en) | 2013-11-19 | 2016-10-26 | 英特尔Ip公司 | HEW station and method for UL MU-MIMO HEW with improved receiver performance |
| BR112016008789B1 (en) | 2013-11-19 | 2022-12-27 | SOLiD, INC | MAIN STATION CONFIGURED FOR HIGH-EFFICIENCY WIRELESS LOCAL AREA NETWORK COMMUNICATION, METHOD PERFORMED BY A MAIN STATION, STORAGE MEDIA AND HIGH-EFFICIENCY WIRELESS LOCAL AREA NETWORK STATION |
| CN108494538B (en) | 2013-11-19 | 2021-11-16 | 英特尔公司 | Method, apparatus, and computer readable medium for multi-user scheduling in wireless local area networks |
| CN104735799B (en) * | 2013-12-24 | 2018-03-27 | 华为技术有限公司 | channel selecting method and device |
| US9591669B2 (en) | 2014-01-20 | 2017-03-07 | Qualcomm Incorporated | Methods and apparatus for signaling enhanced distributed channel access parameters for subsets of wireless devices |
| US20150236897A1 (en) * | 2014-02-20 | 2015-08-20 | Bigtera Limited | Network apparatus for use in cluster system |
| TWI572173B (en) * | 2014-04-01 | 2017-02-21 | 英特爾Ｉｐ公司 | Master station and method for high-efficiency wi-fi (hew) communication with a minimum ofdma bandwidth unit |
| US9680603B2 (en) | 2014-04-08 | 2017-06-13 | Intel IP Corporation | High-efficiency (HE) communication station and method for communicating longer duration OFDM symbols within 40 MHz and 80 MHz bandwidth |
| US9794867B2 (en) * | 2015-04-27 | 2017-10-17 | Apple Inc. | Reconfiguration of wireless devices for wireless network access |
| CN106255174B (en) * | 2016-07-25 | 2021-03-02 | 河南科技大学 | Method for direct communication between users in ultra-dense network |
| CN109906664B (en) * | 2016-11-03 | 2021-04-09 | 华为技术有限公司 | Method for determining BSS attribution, method for sending control frame and related equipment |
| JP6896449B2 (en) * | 2017-02-16 | 2021-06-30 | キヤノン株式会社 | Network equipment and its method |
| US10257769B2 (en) * | 2017-02-28 | 2019-04-09 | Hewlett Packard Enterprise Development Lp | Access point group transmissions |
| KR102331778B1 (en) * | 2017-03-10 | 2021-11-29 | 엘지전자 주식회사 | Method for transmitting and receiving a signal including a physical protocol data unit in a wireless LAN system and an apparatus therefor |
| KR102536586B1 (en) | 2018-09-20 | 2023-05-26 | 삼성전자주식회사 | Electronic device using a wifi communication and method of operating the same |
Family Cites Families (51)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6233626B1 (en) * | 1998-10-06 | 2001-05-15 | Schneider Automation Inc. | System for a modular terminal input/output interface for communicating messaging application layer over encoded ethernet to transport layer |
| US6615038B1 (en) * | 2000-04-28 | 2003-09-02 | Samsung Electronics Co., Ltd. | System and method for automatically creating and updating a mobile station configuration database in a wireless network |
| US6947963B1 (en) * | 2000-06-28 | 2005-09-20 | Pluris, Inc | Methods and apparatus for synchronizing and propagating distributed routing databases |
| EP1323288A4 (en) * | 2000-08-14 | 2007-03-21 | Main Net Comm Ltd | Power line communication system |
| US6973229B1 (en) * | 2001-02-28 | 2005-12-06 | Lambda Opticalsystems Corporation | Node architecture for modularized and reconfigurable optical networks, and methods and apparatus therefor |
| US20030206192A1 (en) * | 2001-03-31 | 2003-11-06 | Mingte Chen | Asynchronous message push to web browser |
| US20020174175A1 (en) * | 2001-04-23 | 2002-11-21 | Sony Corporation | IP-based architecture for mobile computing networks |
| EP1421814A1 (en) * | 2001-08-22 | 2004-05-26 | Nokia Corporation | Expansion planning for wireless network |
| JP3725070B2 (en) * | 2001-12-21 | 2005-12-07 | 株式会社東芝 | Network system, router, host, prefix management method and IP address management method |
| FR2834595A1 (en) * | 2002-01-08 | 2003-07-11 | Canon Kk | COMMUNICATION METHOD IN A NETWORK |
| EP1326386A1 (en) * | 2002-01-08 | 2003-07-09 | Canon Kabushiki Kaisha | Method and device for communication in a network |
| US6879574B2 (en) * | 2002-06-24 | 2005-04-12 | Nokia Corporation | Mobile mesh Ad-Hoc networking |
| US7698550B2 (en) | 2002-11-27 | 2010-04-13 | Microsoft Corporation | Native wi-fi architecture for 802.11 networks |
| US7414982B2 (en) | 2003-06-24 | 2008-08-19 | Raytheon Company | Distributed dynamic channel selection in a communication network |
| TWM261923U (en) * | 2003-07-16 | 2005-04-11 | Interdigital Tech Corp | Apparatus for transferring information between network management entities of a wireless communication system |
| JP2005065102A (en) * | 2003-08-19 | 2005-03-10 | Keio Gijuku | Radio communication equipment and ad hoc system |
| WO2005018161A1 (en) | 2003-08-19 | 2005-02-24 | Keio University | Radio communication device, ad hoc system, and communication system |
| BRPI0415422A (en) * | 2003-10-15 | 2006-12-05 | Qualcomm Inc | high speed media access control with legacy system interoperability |
| US7468969B2 (en) * | 2003-11-07 | 2008-12-23 | Interdigital Technology Corporation | Apparatus and methods for central control of mesh networks |
| TWI277322B (en) * | 2003-12-12 | 2007-03-21 | Via Tech Inc | Switch capable of controlling data packet transmission and related method |
| US20050143110A1 (en) * | 2003-12-30 | 2005-06-30 | Stephens Adrian P. | Method, apparatus and system for managing wireless network channel width capabilities |
| US7233773B2 (en) * | 2004-02-13 | 2007-06-19 | Broadcom Corporation | Configuring a MIMO communication |
| EP1759496A1 (en) * | 2004-06-09 | 2007-03-07 | Philips Intellectual Property & Standards GmbH | Wireless communication system, wireless communication device for use as a station in a wireless communication system, a method of communication within a wireless communication system |
| US7697893B2 (en) | 2004-06-18 | 2010-04-13 | Nokia Corporation | Techniques for ad-hoc mesh networking |
| JP4113160B2 (en) * | 2004-06-24 | 2008-07-09 | 株式会社東芝 | Wireless communication system and wireless communication method |
| JP4685501B2 (en) * | 2004-07-07 | 2011-05-18 | 株式会社エヌ・ティ・ティ・ドコモ | Channel assignment method |
| US7460489B2 (en) * | 2004-07-21 | 2008-12-02 | Tropos Networks, Inc. | Wireless mesh network timed commit provisioning |
| CN1728714B (en) * | 2004-07-27 | 2011-07-27 | 邓里文 | Method for mutual communication between IPv4 network and IPv6 network |
| JP3897034B2 (en) * | 2004-07-28 | 2007-03-22 | 日本電気株式会社 | Wireless LAN system, wireless LAN terminal, mobile network access server, and authentication method used therefor |
| US7339909B2 (en) * | 2004-07-30 | 2008-03-04 | Motorola Inc. | Apparatus and method for operating a communication device on two networks |
| KR100714680B1 (en) * | 2004-08-11 | 2007-05-07 | 삼성전자주식회사 | Method and network device for coexistence in wireless network between MIMO station and SISO station without collision |
| US8699525B2 (en) * | 2004-09-10 | 2014-04-15 | Interdigital Technology Corporation | Method for sending an acknowledgement to an ingress mesh point in a mesh network and a medium access control frame format |
| CN1248449C (en) * | 2004-09-30 | 2006-03-29 | 西安西电捷通无线网络通信有限公司 | Layered insertion identification method using third party additional identification |
| CN1260928C (en) * | 2004-09-30 | 2006-06-21 | 西安西电捷通无线网络通信有限公司 | Method for realizing NATD pass through using cut-in management entity in flexible IP network technology system |
| CN100415034C (en) * | 2004-09-30 | 2008-08-27 | 西安西电捷通无线网络通信有限公司 | Method for realizing self surrogate function for mobile node |
| US7983298B2 (en) * | 2004-10-20 | 2011-07-19 | Qualcomm Incorporated | Multiple frequency band operation in wireless networks |
| US8737189B2 (en) * | 2005-02-16 | 2014-05-27 | Broadcom Corporation | Method and system for compromise greenfield preambles for 802.11n |
| US7415278B2 (en) * | 2004-10-27 | 2008-08-19 | Azalea Networks | Method and system for creating and deploying a mesh network |
| US7940794B2 (en) * | 2004-12-22 | 2011-05-10 | Atheros Communications, Inc. | Dynamic channel bandwidth management |
| US20060193299A1 (en) * | 2005-02-25 | 2006-08-31 | Cicso Technology, Inc., A California Corporation | Location-based enhancements for wireless intrusion detection |
| US8134999B2 (en) * | 2005-04-05 | 2012-03-13 | Cisco Technology, Inc. | Generic provisioning of voice over internet protocol (VoIP) |
| US20060242457A1 (en) * | 2005-04-08 | 2006-10-26 | Interdigital Technology Corporation | Method and apparatus for coordinating seamless channel switching in a mesh network |
| US7796566B2 (en) * | 2005-06-22 | 2010-09-14 | Texas Instruments Incorporated | Methods and apparatus to perform dynamic channel management and dynamic bandwidth changes in wireless local area networks |
| US8081687B2 (en) * | 2005-11-11 | 2011-12-20 | Broadcom Corporation | Received signal determination based upon frame classification |
| KR100765776B1 (en) * | 2005-12-13 | 2007-10-12 | 삼성전자주식회사 | Method and apparatus for avoiding collision in medium access of WLAN |
| KR100782844B1 (en) * | 2006-01-12 | 2007-12-06 | 삼성전자주식회사 | Method and apparatus for transmitting data frame using channel bonding in wireless LAN |
| US20070173248A1 (en) * | 2006-01-20 | 2007-07-26 | Ramesh Sekhar | System and method for analyzing a wireless connection |
| JP4897831B2 (en) * | 2006-01-26 | 2012-03-14 | クゥアルコム・インコーポレイテッド | Physical layer repeater for selecting upper layer functions |
| US8451808B2 (en) * | 2006-02-18 | 2013-05-28 | Intel Corporation | Techniques for 40 megahertz (MHz) channel switching |
| US8948198B2 (en) * | 2006-03-02 | 2015-02-03 | Qualcomm Incorporated | Advanced wireless packet transmission scheme with enhancements to accommodate basic wireless packet transmission scheme |
| US7978725B2 (en) * | 2006-03-06 | 2011-07-12 | Cisco Technology, Inc. | Dynamic modification of contention-based transmission control parameters achieving load balancing scheme in wireless mesh networks |
-
2007
- 2007-04-24 MY MYPI20084086A patent/MY140789A/en unknown
- 2007-04-24 KR KR1020137005559A patent/KR101517705B1/en not_active IP Right Cessation
- 2007-04-24 CN CN201510276199.5A patent/CN104917636A/en active Pending
- 2007-04-24 DE DE602007006785T patent/DE602007006785D1/en active Active
- 2007-04-24 MY MYPI20093475A patent/MY145478A/en unknown
- 2007-04-24 MX MX2008013679A patent/MX2008013679A/en not_active Application Discontinuation
- 2007-04-24 ES ES11164085T patent/ES2397675T3/en active Active
- 2007-04-24 KR KR1020127017050A patent/KR101274346B1/en not_active IP Right Cessation
- 2007-04-24 EP EP10161177A patent/EP2207314B1/en not_active Not-in-force
- 2007-04-24 EP EP11164085A patent/EP2363983B1/en not_active Not-in-force
- 2007-04-24 AT AT07756066T patent/ATE469482T1/en not_active IP Right Cessation
- 2007-04-24 TW TW099114121A patent/TWI454113B/en not_active IP Right Cessation
- 2007-04-24 CA CA2650436A patent/CA2650436C/en not_active Expired - Fee Related
- 2007-04-24 KR KR1020127027479A patent/KR101326328B1/en not_active IP Right Cessation
- 2007-04-24 JP JP2009507803A patent/JP4751947B2/en not_active Expired - Fee Related
- 2007-04-24 BR BRPI0710388-3A patent/BRPI0710388A2/en not_active IP Right Cessation
- 2007-04-24 EP EP07756066A patent/EP2016709B1/en not_active Not-in-force
- 2007-04-24 KR KR1020137022339A patent/KR101517710B1/en not_active IP Right Cessation
- 2007-04-24 KR KR1020087027881A patent/KR101035937B1/en not_active IP Right Cessation
- 2007-04-24 RU RU2008146413/09A patent/RU2400935C2/en not_active IP Right Cessation
- 2007-04-24 KR KR20147030827A patent/KR20140133966A/en not_active Application Discontinuation
- 2007-04-24 CN CNA2007800148863A patent/CN101433018A/en active Pending
- 2007-04-24 AT AT10161177T patent/ATE521171T1/en not_active IP Right Cessation
- 2007-04-24 WO PCT/US2007/010149 patent/WO2007127312A2/en active Application Filing
- 2007-04-24 AU AU2007243313A patent/AU2007243313B2/en not_active Ceased
- 2007-04-24 TW TW096114506A patent/TWI434560B/en not_active IP Right Cessation
- 2007-04-24 KR KR1020097000766A patent/KR20090017701A/en active IP Right Grant
- 2007-04-24 DK DK10161177.0T patent/DK2207314T3/en active
- 2007-04-24 KR KR1020147005716A patent/KR101517740B1/en not_active IP Right Cessation
- 2007-04-24 TW TW103108831A patent/TWI581596B/en not_active IP Right Cessation
- 2007-04-25 US US11/740,018 patent/US8542613B2/en active Active
- 2007-04-25 AR ARP070101792A patent/AR060818A1/en active IP Right Grant
-
2008
- 2008-10-07 IL IL194644A patent/IL194644A/en active IP Right Grant
-
2011
- 2011-05-20 JP JP2011114104A patent/JP5324621B2/en not_active Expired - Fee Related
-
2013
- 2013-07-18 JP JP2013149445A patent/JP5572743B2/en not_active Expired - Fee Related
- 2013-09-23 US US14/033,909 patent/US20140022947A1/en not_active Abandoned
-
2014
- 2014-06-30 JP JP2014134674A patent/JP2014180054A/en active Pending
-
2016
- 2016-07-08 JP JP2016136004A patent/JP2016174436A/en not_active Ceased
Also Published As
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CA2650436C (en) | High-throughput channel operation in a mesh wireless local area network | |
| JP5680657B2 (en) | Scheduled access point for peer-to-peer communication | |
| KR20050065123A (en) | Method for establishing channel between user agent and wireless access point in public wireless local area network |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| EEER | Examination request | ||
| MKLA | Lapsed |
Effective date: 20190424 |