EP3005816A1 - Transmit opportunity (txop) based channel reuse - Google Patents
Transmit opportunity (txop) based channel reuseInfo
- Publication number
- EP3005816A1 EP3005816A1 EP14733817.2A EP14733817A EP3005816A1 EP 3005816 A1 EP3005816 A1 EP 3005816A1 EP 14733817 A EP14733817 A EP 14733817A EP 3005816 A1 EP3005816 A1 EP 3005816A1
- Authority
- EP
- European Patent Office
- Prior art keywords
- reuse
- message
- txop
- transmitter
- cca threshold
- 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.)
- Withdrawn
Links
- 238000000034 method Methods 0.000 claims abstract description 111
- 238000004891 communication Methods 0.000 claims description 21
- 230000004044 response Effects 0.000 claims description 14
- 230000005540 biological transmission Effects 0.000 description 85
- 238000010586 diagram Methods 0.000 description 32
- 238000013459 approach Methods 0.000 description 17
- 230000006870 function Effects 0.000 description 6
- 238000012545 processing Methods 0.000 description 6
- 230000003111 delayed effect Effects 0.000 description 4
- 238000001514 detection method Methods 0.000 description 4
- 238000005259 measurement Methods 0.000 description 4
- 230000011664 signaling Effects 0.000 description 4
- 230000000737 periodic effect Effects 0.000 description 3
- 230000008901 benefit Effects 0.000 description 2
- 230000010363 phase shift Effects 0.000 description 2
- 101100172132 Mus musculus Eif3a gene Proteins 0.000 description 1
- 101100545229 Saccharomyces cerevisiae (strain ATCC 204508 / S288c) ZDS2 gene Proteins 0.000 description 1
- 101100114859 Schizosaccharomyces pombe (strain 972 / ATCC 24843) crk1 gene Proteins 0.000 description 1
- 101100113084 Schizosaccharomyces pombe (strain 972 / ATCC 24843) mcs2 gene Proteins 0.000 description 1
- 101100022564 Schizosaccharomyces pombe (strain 972 / ATCC 24843) mcs4 gene Proteins 0.000 description 1
- 102100024470 Stabilin-2 Human genes 0.000 description 1
- 101100167209 Ustilago maydis (strain 521 / FGSC 9021) CHS8 gene Proteins 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000008569 process Effects 0.000 description 1
- 238000012552 review Methods 0.000 description 1
- 230000001052 transient effect Effects 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W74/00—Wireless channel access
- H04W74/08—Non-scheduled access, e.g. ALOHA
- H04W74/0808—Non-scheduled access, e.g. ALOHA using carrier sensing, e.g. carrier sense multiple access [CSMA]
- H04W74/0816—Non-scheduled access, e.g. ALOHA using carrier sensing, e.g. carrier sense multiple access [CSMA] with collision avoidance
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W74/00—Wireless channel access
- H04W74/08—Non-scheduled access, e.g. ALOHA
-
- 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]
Definitions
- TRANSMIT OPPORTUNITY BASED CHANNEL REUSE CROSS-REFERENCE TO RELATED APPLICATIONS
- Provisional Pat. App. No. 61/827,480 filed May 24, 2013 and entitled “SYSTEMS AND METHODS FOR PACKET IN PACKET DETECTION IN A WIRELESS COMMUNICATION NETWORK" (Atty. Dkt. No. 132988P1), U.S. Provisional Pat. App. No. 61/843,315 filed July 5, 2013 and entitled “METHODS AND APPARATUS FOR CLEAR CHANNEL ASSESSMENT" (Atty. Dkt. No. 133764P1), U.S.
- Provisional Pat. App. No. 61/869,546 filed August 23, 2013 and entitled “SYSTEMS, METHODS, AND APPARATUS FOR INCREASING REUSE IN WIRELESS COMMUNICATIONS" (Atty. Dkt. No. 134512P1), U.S. Provisional Pat. App. No. 61/926,205 filed January 10, 2014 and entitled “TRANSMIT OPPORTUNITY (TXOP) BASED CHANNEL REUSE” (Atty. Dkt. No. 141289P1), U.S. Provisional Pat. App. No.
- the present disclosure is generally related to transmit opportunity (TXOP) based channel reuse.
- wireless computing devices such as portable wireless telephones, personal digital assistants (PDAs), and paging devices that are small, lightweight, and easily carried by users.
- portable wireless telephones such as cellular telephones and Internet protocol (IP) telephones
- IP Internet protocol
- wireless telephones can communicate voice and data packets over wireless networks.
- many such wireless telephones include other types of devices that are incorporated therein.
- a wireless telephone can also include a digital still camera, a digital video camera, a digital recorder, and an audio file player.
- such wireless telephones can process executable instructions, including software applications, such as a web browser application, that can be used to access the Internet. As such, these wireless telephones can include significant computing capabilities.
- Wi-Fi Institute of Electrical and Electronics Engineers 802.11, commonly referred to as "Wi-Fi," is a standardized set of wireless local area network (WLAN) communication protocols.
- Wi-Fi protocols a transmitter station may transmit a preamble prior to transmitting a physical layer protocol data unit (PPDU) to a receiver.
- the preamble may identify a transmit opportunity (TXOP) and may be detectable by other stations.
- Stations that detect the preamble corresponding to the PPDU may defer to the transmitter station for a duration associated with the transmit opportunity (TXOP).
- TXOP transmit opportunity
- multiple wireless devices may be densely deployed (e.g., deployed fairly close to each other).
- a first device transmits data during a TXOP established by the first device
- a second device in close proximity to the first device may not perform a transmission during the TXOP.
- the present disclosure presents techniques and protocols for enabling TXOP based channel reuse. Instead of a device in a wireless system deferring (e.g., not transmitting) during a TXOP of another device in the wireless system, the device may transmit during the TXOP (e.g., the device may "reuse" the TXOP). To mitigate the possibility of interference caused by the TXOP reuse, the present disclosure describes various notification and interference measurement protocols.
- the wireless system may include a first transmitter (TX), a first receiver (RX), a reuse TX, and a reuse RX.
- TX first transmitter
- RX first receiver
- RX reuse TX
- RX reuse TX
- RX reuse RX
- Each of the first TX, the first RX, the reuse TX, and the reuse RX may be a device configured to transmit data and/or receive data from one or more other devices included in the wireless system.
- the first TX is configured to transmit a first message associated with a first TXOP to the first RX.
- the reuse TX is configured to transmit a second message associated with a second TXOP to the reuse RX.
- the second message is transmitted by the reuse TX during the first TXOP, and the second TXOP occurs during the first TXOP.
- a period of time during which the reuse TX is transmitting during the first TXOP is referred to as a "reuse TXOP.” Accordingly, the reuse TX is permitted to transmit during the first TXOP.
- the wireless devices may be in the same wireless network or in different wireless networks, as further described herein.
- the first TX and/or the first RX may transmit control information associated with the first message.
- the control information may be detectable by one or more other devices included in the wireless system, such as the reuse TX and/or the reuse RX.
- the control information may indicate that one or more other devices may "reuse" the first TXOP.
- the control information may indicate that the reuse TX is permitted to transmit the second message during the first TXOP, may indicate one or more parameters (e.g., such as clear channel access (CCA) threshold) to be used by the reuse TX and/or the reuse RX, or a combination thereof.
- the reuse TX may determine whether to reuse the first TXOP to send the second message. For example, the reuse TX may determine to reuse the first TXOP when an interference level between different devices (e.g., between the first TX and the reuse TX) is low, such as when a particular interference level between two devices is below a threshold value.
- the first TX and the first RX may perform a handshake exchange.
- the handshake exchange may include the first TX sending a request to send (RTS) message to the first RX and may include the first RX sending a clear to send (CTS) message to the first TX.
- RTS request to send
- CTS clear to send
- the handshake exchange (e.g., the RTS message and/or the CTS message) may indicate whether reuse of the first TXOP is permitted, may indicate one or more parameters (e.g., one or more CCA thresholds), or a combination thereof.
- the handshake exchange may be detectable by one or more other devices included in the wireless system, such as the reuse TX and/or the reuse RX.
- a method includes determining, at a first transmitter, a clear channel access (CCA) threshold associated with reuse of a first transmit opportunity (TXOP) of a message. The method further includes sending, from the first transmitter to a first receiver, at least a portion of the message, wherein the portion of the message indicates the CCA threshold.
- CCA clear channel access
- a method in another particular embodiment, includes detecting, at a reuse transmitter, a portion of a message sent by a first transmitter.
- the message is associated with a first transmit opportunity (TXOP).
- the message further includes determining, based on the portion, a clear channel access (CCA) threshold associated with reuse of the first TXOP.
- CCA clear channel access
- a method in another particular embodiment, includes determining, at a reuse transmitter, that reuse of a first transmit opportunity (TXOP) associated with a first message is permitted.
- the first message is transmitted from a first transmitter to a first receiver.
- the method further includes determining whether to reuse the first TXOP based on a receiver (RX) clear channel access (CCA) threshold associated with the first receiver.
- RX receiver
- CCA clear channel access
- a method in another particular embodiment, includes detecting, at a reuse transmitter, a portion of a message sent by a first receiver. The method further includes determining, based on the portion, a receiver (RX) clear channel access (CCA) threshold associated with reuse of a first TXOP.
- RX receiver
- CCA clear channel access
- One particular advantage provided by at least one of the disclosed embodiments is a channel access efficiency of the wireless system may be improved and a capacity the wireless system may be increased. For example, by enabling reuse of a TXOP, more data may be transmitted during a given time interval.
- FIG. 1 is a block diagram of a first illustrative embodiment of a system that permits reuse of a transmit opportunity (TXOP);
- FIG. 2 is a timing diagram of a first illustrative example of reuse of a TXOP
- FIG. 3 is a timing diagram of a second illustrative example of reuse of a TXOP
- FIG. 4 is a timing diagram of a third illustrative example of reuse of a TXOP
- FIG. 5 is a timing diagram of a fourth illustrative example of reuse of a TXOP
- FIG. 6 is a timing diagram of a fifth illustrative example of reuse of a TXOP
- FIG. 7 is a timing diagram of a sixth illustrative example of reuse of a TXOP
- FIG. 8 is a timing diagram to illustrate an example of a deferral/backoff period associated with reuse of a TXOP
- FIG. 9 is a timing diagram to illustrate examples of handling block acknowledgements (BAs) associated with reuse of a TXOP;
- FIG. 10 is a block diagram of a second illustrative embodiment of a system that permits reuse of a transmit opportunity (TXOP);
- FIG. 11 is a flow diagram of an illustrative method of operating a first transmitter
- FIG. 12 is a flow diagram of an illustrative method of operating a reuse transmitter
- FIG. 13 is a flow diagram of an illustrative method of operating a first transmitter
- FIG. 14 is a flow diagram of an illustrative method of operating a reuse transmitter
- FIG. 15 is a flow diagram of an illustrative method of operating a first transmitter
- FIG. 16 is a flow diagram of an illustrative method of operating a first receiver
- FIG. 17 is a flow diagram of an illustrative method of operating a reuse transmitter
- FIG. 18 is a flow diagram of an illustrative method of operating a reuse transmitter
- FIG. 19 is a flow diagram of an illustrative method of operating a reuse transmitter
- FIG. 20 is a flow diagram of an illustrative method of operating a reuse transmitter.
- FIG. 21 is a diagram of a wireless device that is operable to support various embodiments of one or more methods, systems, apparatuses, and/or computer-readable media disclosed herein.
- the system 100 includes a first transmitter (TX) 1 10, a first receiver (RX) 130, a reuse TX 140, and a reuse RX 160.
- the first TX 110 e.g., a first TX device
- the reuse TX 140 is configured to transmit a second message 150 associated with a second TXOP to the reuse RX 160.
- the second message 150 is transmitted by the reuse TX 140 during the first TXOP, and the second TXOP occurs during the first TXOP.
- a period of time during which the reuse TX 140 is transmitting during the first TXOP is referred to as a "reuse TXOP.” Accordingly, the reuse TX 140 is permitted to transmit the second message 150 during the first TXOP.
- the reuse TX 140 may be permitted to transmit the second message 150 during the first TXOP on a same channel, partially on the same channel, or on a different channel than a channel on which the first message 120 is communicated by the first TX 110.
- the system 100 may include or correspond to a wireless system, which may include one or more wireless networks.
- the first TX 110, the first RX 130, the reuse TX 140, and the reuse RX 160 may be part of the same wireless network.
- the system 100 may include multiple networks, such as a first network that includes the first TX 1 10 and the first RX 130 and a second network that includes the reuse TX 140 and the reuse RX 160.
- the first network may be associated with a first basic service set (BSS) having a first BSS identification (BSSID) and the second network may be associated with a second BSS having a second BSSID.
- BSS basic service set
- BSSID BSS identification
- the system 100 may include Institute of Electrical and Electronics Engineers (IEEE) 802.11 wireless network(s) (e.g., a Wi-Fi network).
- IEEE Institute of Electrical and Electronics Engineers
- the system 100 may operate in accordance with an IEEE 802.1 1 standard.
- the system 100 includes an 802.11 high efficiency Wi-Fi (HEW) network.
- the system 100 may support transmissions according to one or more of the IEEE 802.1 1a, 802.11 ⁇ , 802.1 lac, or 802.1 lax standards, as illustrative, non-limiting examples.
- Each of the first TX 110, the first RX 130, the reuse TX 140, and the reuse RX 160 may be a device configured to transmit data and/or receive data from one or more other devices included in the system 100.
- each of the first TX 110, the first RX 130, the reuse TX 140, and the reuse RX 160 may include processor (e.g., a central processing unit (CPU), a digital signal processor (DSP), a network processing unit (NPU), etc.), a memory (e.g., a random access memory (RAM), a read-only memory (ROM), etc.), and/or a wireless interface configured to send and receive data via a wireless network, as described further with reference to FIG. 21.
- processor e.g., a central processing unit (CPU), a digital signal processor (DSP), a network processing unit (NPU), etc.
- a memory e.g., a random access memory (RAM), a read-only memory (ROM), etc.
- a wireless interface configured to send
- Each of the first TX 110, the first RX 130, the reuse TX 140, and the reuse RX 160 may be an access point (AP) or a station (STA).
- Each of the first TX 110, the first RX 130, the reuse TX 140, and the reuse RX 160 may be configured to operate in compliance with one or more standards, such as one or more IEEE 802.1 1 standards.
- the first TX 1 10 may be configured to generate the first message 120 and to transmit the first message 120 to the first RX 130.
- the first message 120 may be transmitted via a channel (e.g., a channel having a corresponding frequency band) to the first RX 130.
- the first message 120 may be associated with a data packet having one or more fields.
- the first message 120 may be associated with a first TXOP and reuse of the first TXOP may be permitted by another device in the system 100. For example, an indication that reuse of the first TXOP is permitted may be provided to one or more devices included in the system 100, as described further with reference to FIGS. 2 and 5.
- the indication may be provided as a management message (e.g., included in a beacon) provided from a particular device, such as the first TX 1 10, may be provided part of the first message 120, as described further with reference to FIG. 2, and/or may be provided as part of a handshake exchange between the first TX 1 10 and the first RX 130, as described with reference to FIG. 5, as illustrative, non-limiting examples.
- the first message 120 may represent a request to send (RTS) message, a control message, a data message, a physical layer (PHY) preamble, a media access control (MAC) layer message, etc. or a portion thereof.
- RTS request to send
- PHY physical layer
- MAC media access control
- the reuse TX 140 may determine whether reuse of the first TXOP is permitted. If reuse of the first TXOP is permitted and the reuse TX 140 is ready to transmit a message, such as the second message 150, the reuse TX 140 may determine whether to reuse the first TXOP. When the reuse TX 140 determines that reuse of the first TXOP is not permitted, or if the reuse TX 140 determines not to reuse the first TXOP, the reuse TX 140 defers to the first TXOP and does not transmit the second message 150 during the first TXOP. For example, the reuse TX 140 may queue the second message 150 to be transmitted after expiration of the first TXOP (e.g., after the first message 120 is transmitted).
- a second TXOP of the second message 150 may not be permitted to be reused by another device (e.g., TXOP reuse nesting may not be permitted).
- the reuse TX 140 may determine whether one or more conditions are satisfied. For example, the reuse TX 140 may determine whether a mutual interference between one or more devices in the system 100 satisfies (e.g., is less than) one or more thresholds. For example, the reuse TX 140 may determine whether a first mutual interference between the first TX 1 10 and the reuse RX 160 is less than or equal to a first threshold, as described further with reference to FIG. 2. When the reuse TX 140 determines to reuse the first TXOP (e.g., because the mutual interference is less than the first threshold), the reuse TX 140 may transmit the second message 150 during the first TXOP. A transmission (e.g., a duration) of the second message 150 may not exceed an end of the first TXOP.
- a transmission e.g., a duration
- transmission of the first message 120 and the second message 150 may at least partially overlap.
- more traffic e.g., more data
- the reuse TX 140 may determine whether a second mutual interference between the reuse TX 140 and the first RX 130 satisfies a second threshold, as described further with reference to FIG. 5, and/or may determine whether a third mutual interference between the reuse RX 160 and the first RX 130 satisfies a third threshold.
- determining whether to reuse a TXOP may include considering interference (or potential interference) between one or more of the first TX 1 10, the first RX 130, the reuse TX 140, and/or the reuse RX 160.
- the reuse TX 140 may determine whether the first message 120 is addressed to the reuse TX 140, whether a destination of the first message 120 is the same as a destination of the second message 150, whether the second message 150 is addressed to the first TX 110 or to the first RX 130, and/or whether a signal strength of the first TX 110 satisfies a clear channel access (CCA) threshold, as illustrative, non-limiting examples.
- CCA clear channel access
- the reuse TX 140 may reuse the first TXOP based on a determination that the first message 120 is not addressed to the reuse TX 140, based on a determination that the destination (e.g., the first RX 130) of the first message 120 is different than the destination (e.g., the reuse RX 160) of the second message 150, based on a determination that the second message 150 is not addressed to the first TX 1 10 or to the first RX 130, and/or based on a determination that the signal strength of the first TX 110 satisfies the CCA threshold, as illustrative, non-limiting examples.
- the reuse TX 140 may determine whether to reuse the first TXOP based on whether the NAV was set by the first TX 1 10. When the NAV is determined to be set by a frame sent from a device other than the first TX 1 10, the reuse TX 140 may defer to the first TXOP and may not transmit the second message 150 during the first TXOP.
- NAV network allocation vector
- the reuse TX 140 may transmit the second message 150 during the first TXOP.
- the first TX 110 may indicate that reuse of the first TXOP is permitted (or may indicate one or more CCA thresholds, as described further with reference to FIGS. 2 and 5) by setting one or more bits in a signal (SIG) field of the first message 120.
- SIG signal
- the message 120 includes physical layer convergence protocol (PLCP) data and a physical layer protocol data unit (PPDU)
- PLCP physical layer convergence protocol
- PPDU physical layer protocol data unit
- at least one bit in a SIG field of the PLCP data may be used to indicate that reuse of the first TXOP is permitted, to indicate a CCA threshold, or a combination thereof.
- the SIG field may include a SIG-A field and/or a SIG-B field of an IEEE 802.1 lac preamble and one or more reserved bits may be set to indicate that reuse of the first TXOP is permitted, to indicate a CCA threshold, or a combination thereof.
- the first TX 110 may indicate that reuse of the first TXOP is permitted and/or may indicate one or more CCA thresholds by setting one or more bits included in a preamble of the message 120.
- the message 120 may include a HEW preamble and the SIG field may be included in the HEW preamble.
- signaling associated with TXOP reuse may be included in a "new" type of preamble (e.g., a "new" HEW preamble) that includes a physical (PHY) layer structure that is distinct from one or more preambles defined in one or more IEEE 802.1 lac standards.
- the "new" preamble may include one or more bits to indicate that TXOP reuse is permitted, to indicate at least a partial BSSID associated with a transmitting device, to indicate at least a partial BSSID associated with a receiving device, to indicate at least a partial transmitter address associated with a transmitting device, to indicate a least a partial receiver address associated with a receiving device, or a combination thereof, as illustrative, non-limiting examples.
- signaling information described herein such as a PLCP preamble, a MAC layer preamble, a SIG-A field, a SIG-B field, a HEW preamble, etc.
- Signaling associated with TXOP reuse may also be included in other structures, such as other physical layer structures or MAC layer structures, as illustrative, non-limiting examples.
- the first TX 110 may indicate that reuse of the first TXOP is permitted and/or may indicate one or more CCA thresholds by using a SIG field of an 802.1 lac preamble.
- a SIG field of an 802.1 lac preamble For example, one or more reserved bits of the 802.1 lac SIG-A field may be set to a particular value that causes the 802.1 lac SIG-A filed to be interpreted as a HEW SIG field (e.g., a format of the 802.1 lac SIG-A field may be redefined based on the particular value of the one or more reserved bits).
- the PLCP data of the first message 120 may include at least a portion of a BSSID associated with the first TX 1 10 or the first RX 130.
- a BSSID associated with the first TX 1 10 or the first RX 130.
- an 802.1 lac partial association identifier may include multiple bits, such as 9 bits, to identify at least a portion of the BSSID.
- the multiple bits of the 802.1 lac PAID used for the uplink communication may be sufficient to enable a device, such as the reuse TX 140 or the reuse RX 160, to identify a receiver of the first message 120 (e.g., the first RX 130).
- the BSSID may be hashed with an AID in the 802.1 lac PAID.
- an access point of a network may assign AIDs which result in a PAID from which the BSSID may be easily extracted.
- the access point of the network may selectively determine and assign AID numbers so that for a given PAID, the PAID and the BSSID may be extracted (e.g., because a device extracting the PAID and the BSSID may already know the BSSID from one or more beacons transmitted by the access point).
- the access point may assign AID numbers that have zero values in certain bit positions or that have a particular bit pattern which the BSSID does not have. Accordingly, a device that receives (e.g., detects) the 802.1 lac PAID may use the PAID and the BSSID to extract the AID information. Stated another way, the device that detects the 802.1 lac PAID of a downlink transmission may be able to identify the access point that transmits the downlink transmission and a station that is designated to receive the downlink transmission. Additionally or alternatively, the access point may avoid assigning AIDs that would result in a PAID that matches the partial BSSID, so that UL and DL can be discerned.
- the reuse TX 140 may be able to determine that the first message 120 was sent by the first TX 1 10 to the first RX 130.
- a portion of a packet e.g., a portion of an IEEE 802.1 lac packet
- the reuse TX 140 may reinterpret at least a portion of a field based on a value of one or more bits, such as one or more reserved bits.
- the reuse TX 140 may receive an IEEE 802.1 lac PLCP preamble and identify one or more reserved bits or one or more reserved group ID (GID) field values that indicate that a PAID field is encoded in a manner other than defined by one or more IEEE 802.1 lac specifications.
- the PAID field (having 9 bits) may be encoded to represent a partial BSSID in the 5 most significant bits (MSBs) of the PAID field and to represent a partial first TX AID or a partial first RX AID in the remaining 4 least significant bits (LSBs), as an illustrative, non-limiting example.
- the reuse TX 140 may "reinterpret" the PAID field based on the one or more reserved bits or the one or more reserved GID field values to determine the partial BSSID, the partial first TX AID, the partial first RX AID, or a combination thereof.
- an access point of a BSS may enable one or more devices of an overlapping BSS (OBSS) to map each received (e.g., detected) PAID from the BSS to a corresponding BSSID (e.g., of the access point).
- OBSS overlapping BSS
- the access point of the BSS may piggyback, to a beacon transmitted by the access point, all PAIDs used by the access point.
- the access point (e.g., the first TX 110, the first RX 130, the reuse TX 140, or the reuse RX 160) of the BSS may enable or disable reuse of TXOPs or may provide reuse parameters (e.g., one or more CCA thresholds, MCSs for reuse, or reuse transmission power levels) to one or more devices included in the BSS.
- the access point may enable or disable reuse of TXOPs or may provide reuse parameters using a beacon broadcast by the access point.
- TXOP reuse may be applied to peer-to- peer (P2P) transmissions, such as in a system that supports WiFi-Direct transmission or a tunneled direct link setup (TDLS) transmission.
- P2P transmission is a WiFi-Direct transmission
- a device that is a group owner (GO) may be associated with a corresponding BSSID. Accordingly, when the GO includes the first TX 1 10 or the first RX 130, other stations may identify the GO based on the BSSID.
- the GO is a cross connecting device (e.g., the GO operates in one direction as part of a P2P network and operates in another direction as a STA coupled to an AP)
- additional information may be included in transmissions to and from the GO to make the GO identifiable to one or more other devices.
- a transmission to or from the GO may include transmitter address/ receiver address (TA/RA) information in a SIG field of the transmission.
- TA/RA transmitter address/ receiver address
- TA/RA transmitter address/ receiver address
- TA/RA transmitter address/ receiver address
- a handshake exchange including a request to send (RTS) message and a clear to send (CTS) message may be performed prior to a transmission to or from the GO.
- RTS request to send
- CTS clear to send
- TA/RA information (e.g., at least partial address information) may be provided in addition to a BSSID and a "reuse allowed" indication to enable reuse of a TXOP of a particular message communicated using the TDLS transmission.
- a device e.g., the first TX 1 10
- a handshake exchange e.g., including an RTS message and a CTS message
- the particular message may indicate that the particular message is a TDLS transmission.
- a particular value of a group ID (GID) field may indicate that the particular message is part of a TDLS transmission.
- the TA/RA information (or at least partial address information) may be included in or signaled (as a parameter associated with TXOP reuse) using one or more fields, such as a SIG field, an IEEE 802.1 lac field, a reinterpreted IEEE 802.1 lac field, a HEW preamble, etc., as illustrative, non-limiting examples.
- a device may provide TA/RA information in a SIG field.
- one or more reserved bits of an 802.11 ac SIG filed may be set to a particular value that causes the 802.1 lac to be interpreted as a HEW SIG field that identifies the TA/RA information.
- the reuse TX 140 may align the second TXOP (associated with the second message 150) with the first TXOP (associated with the first message 120) such that the second TXOP does not exceed the first TXOP.
- the reuse TX 140 may align the second TXOP (in time) with the first TXOP so that an end of the second TXOP occurs prior to or at the same time as an end of the first TXOP, as described with reference to FIG. 2.
- one or more deferral rules and/or one or more backoff rules may be applied at the reuse TX 140, as described with reference to FIG. 8.
- one or more approaches may be implemented to handle block acknowledgements (BAs) associated with the first message 120 and the second message 150, as described with reference to FIG. 9.
- BAs block acknowledgements
- an overall throughput of the system 100 may be increased. Further, by transmitting the second message 150 during the first TXOP, a channel access efficiency of the system 100 may be improved and a capacity the system 100 may be increased, as compared to systems that do not permit reuse of TXOPs. Additionally, by enabling (e.g., permitting) reuse of TXOPs in the system 100, an improved signal-to-interference- plus-noise ratio (SINR) may be achieved as compared to systems that do not permit reuse of TXOPS. Accordingly, an overall throughput of the system may be increased when TXOPs can be reused.
- SINR signal-to-interference- plus-noise ratio
- TXOP duration may be greater than in a system that does not support TXOP reuse.
- a system that does not support TXOP reuse may permit a TXOP duration up to 3 milliseconds.
- the system 100 may support TXOP durations greater than 3 milliseconds (e.g., 5 or 6 milliseconds, as illustrative, non-limiting examples).
- the first TX 110 may have enhanced distributed channel access (EDCA) parameter settings (e.g., arbitration inter-frame space (AIFS), minimum contention window (CWmin), maximum contention window (CWmax), etc.) based on TXOP reuse being supported by the system 100.
- EDCA distributed channel access
- an EDCA access category e.g., a "reuse" category
- the data in the reuse category may be put in the corresponding queue depending on quality of service (QoS) requirements of the data or based on past TXOP reuse gain performance.
- QoS quality of service
- an access point and devices having a P2P link may coordinate to make reuse decisions without having to perform handshake exchanges.
- handshake exchanges e.g. RTS/CTS messaging
- an amount of overhead in a system may be reduced.
- FIG. 2 is a timing diagram to illustrate an example of reuse of a TXOP and is generally designated 200.
- a horizontal axis from left-to-right corresponds to time.
- the timing diagram 200 illustrates communication between the first TX 110 and the first RX 130 and between the reuse TX 140 and the reuse RX 160 of FIG. 1.
- the first TX 110 may begin transmitting the first message 120 to the first RX 130.
- the first message 120 may include or correspond to a protocol data unit (PDU), such as a physical layer PDU (PPDU), as described with reference to FIG. 10.
- PDU protocol data unit
- PPDU physical layer PDU
- the first message 120 may be associated with a first TXOP 222.
- the first message 120 may include a first control portion 224 and first data 226.
- the first control portion 224 may be a portion of the first message 120 that is detectable (and decodable) by one or more devices, such as the first RX 130, the reuse TX 140, and/or the reuse RX 160, as described further herein.
- the first control portion 224 may be associated with a preamble or PLCP data of the first message 120.
- the first control portion 224 may be associated with a MAC header of the first message 120, and the MAC header may be sent at a transmission rate that is decodable by one or more devices, such as the first RX 130, the reuse TX 140, the reuse RX 160, or one or more other devices, as illustrative, non-limiting examples.
- the first data 226 may include data (e.g., a data payload) to be communicated from the first TX 1 10 to an intended destination device (e.g., the first RX 130).
- the first data 226 may be encrypted so that the first data 226 may not be detectable by devices other than an intended device.
- the first control portion 224 may indicate a device (e.g., the first RX 130) to which the first message 120 is addressed, a device (e.g., the first TX 140) that transmits the first message 120, a duration of the first TXOP 222, whether reuse of the first TXOP 222 is permitted, and/or one or more CCA thresholds (associated with the first TX 1 10 and/or the first RX 130), as illustrative, non-limiting examples.
- one or more bits in a signature (SIG) field associated with the first message 120 may be set to indicate such information, as described further with reference to FIG. 10.
- the first TX 1 10 may begin transmitting the first data 226 to the first RX 130.
- a transmission of the first data 226 may coincide with a beginning of the first TXOP 222, as shown.
- the reuse TX 140 may determine whether the reuse TX 140 is permitted to reuse the first TXOP 222. For example, the reuse TX 140 may determine that reuse is permitted based on the first control portion 224, based on a management message received from a device (e.g., the first TX 110, the first RX 130, or another device), based on a header associated with the first message 120, or based on a handshake exchange between the first TX 110 and the first RX 130, as described with reference to FIG. 5, as illustrative, non-limiting embodiments.
- a device e.g., the first TX 110, the first RX 130, or another device
- the reuse TX 140 may defer to the first TXOP 222 (e.g., may not second the second message 150 during the first TXOP 222.
- the reuse TX 140 may determine whether to reuse the first TXOP.
- the reuse TX 140 may transmit the second message 150 at a third time (ta3) during the first TXOP.
- the reuse TX 140 and the reuse RX 160 may optionally perform a handshake exchange to determine whether the reuse TX 140 should reuse the first TXOP 222.
- the reuse TX 140 may transmit a request to send (RTS) message 262 to the reuse RX 160 and the reuse RX 160 may transmit a clear to send (CTS) message 264 to the reuse TX 140, as described further herein.
- RTS request to send
- CTS clear to send
- the RTS message 262 may indicate that the reuse TX 140 requests to reuse the first TXOP 22 and the reuse RX 160 may transmit the CTS message 264 to indicate that the reuse TX 140 may reuse the first TXOP 222.
- the reuse RX 160 may not send the CTS message 264 to the reuse TX 140, and the reuse TX 140 may interpret the absence of the CTS message 264 as a sign that the reuse RX 160 is restricting/preventing reuse of the first TXOP 222.
- the reuse RX 160 may determine not to permit TXOP reuse based on one or more conditions (e.g., one or more rules) and may not send the CTS message 264 based on a determination not to permit TXOP reuse.
- the one or more conditions may include whether a NAV honored by the reuse RX 160 is set by the first TXOP 110, whether the reuse RX 160 received an indication that TXOP reuse is permitted, based on measured or estimated interference levels, based on historical data, based on previously detected packets (e.g., previously detected RTS and/or CTS messages), etc..
- the reuse RX 160 may indicate that TXOP reuse is not permitted by setting a particular value of one or more bits in the CTS message 264.
- a NAV associated with RTS/CTS (e.g., a NAV set by the reuse TX 140) may be aligned to an end of the first TXOP 222, such that the NAV does not exceed the first TXOP 222.
- the reuse TX 140 may initiate transmission of the second message 150.
- the second message 150 may include a second control portion 254 and second data 256.
- the second control portion 254 may be a portion of the second message 150 that is detectable (and decodable) by one or more devices, such as the first TX 110, the first RX 130, and/or the reuse RX 160.
- the second control portion 254 may be associated with a preamble or PLCP data of the second message 150 and may indicate a device (e.g., the reuse RX 160) to which the second message 150 is addressed, a device (e.g., the reuse TX 140) that transmits the second message 150, a duration of a second TXOP 272, and/or whether reuse of the second TXOP 272 is permitted, as illustrative, non-limiting examples.
- the reuse TX 140 may begin transmitting the second data 256 to the reuse RX 160.
- the second data 256 may begin at the same time as or after the second TXOP 272 begins.
- the second data 256 may be encrypted so that the second data 256 may not be detectable by devices other than an intended device (e.g., the reuse RX 160).
- transmission of the first message 120 and the second message 150 may end.
- first message 120 and the second message 150 e.g., the first TXOP 222 and the second TXOP 272
- the first message 120 and the second message 150 may end at different times, such that the second message 150 does not end after the first TXOP 222 ends.
- the first TXOP 222 and the second TXOP 272 may be aligned so that the second TXOP 272 does not exceed the first TXOP 222.
- the reuse TX 140 may set the second TXOP 272 (e.g., a duration of the second TXOP 272) to occur during the first TXOP 222, but not to exceed the first TXOP 222.
- a time period during which the reuse TX 140 is communicating (e.g., transmitting the second message 150) during the first TXOP 222 may be referred to as a reuse TXOP 270.
- the reuse TXOP 270 is illustrated in FIG. 2 as beginning at the third time (ta3), the reuse TXOP 270 may include the handshake exchange between the reuse TX 140 and the reuse RX 160 and may being at a time between the second time (ta2) and the third time (ta3).
- the reuse TXOP 270 may be based on a NAV set by the reuse TX 140.
- the first TX 110 may determine whether to permit reuse of the first TXOP 222 based on whether a link associated with the first TX 1 10 can tolerate interference from another link. For example, when the first TX 1 10 is included in a BSS, the first TX 110 may determine whether a link associated with the BSS can tolerate one or more other links associated with a different network, such as an overlapping BSS (OBSS) or a peer-to-peer (P2P) network, as illustrative, non-limiting examples. The first TX 110 may determine whether the link associated with the first TX 110 can tolerate interference from another link based on a signal level of the link, such as a signal level between the first TX 110 and the first RX 130.
- OBSS overlapping BSS
- P2P peer-to-peer
- the signal level of the link may be determined at the first TX 1 10 based on an uplink signal, a downlink signal, a signal to noise ratio (SNR), or a received signal strength indication (RSSI), as illustrative, non-limiting examples.
- the first TX 1 10 may compare the signal level to a threshold associated with an amount of acceptable (e.g., tolerable) interference.
- the first TX 110 may determine whether the link associated with the first TX 1 10 can tolerate interference from another link based on a difference between the signal level of the link and an interference level associated with the other link.
- the first TX 110 may permit reuse of the first TXOP 222 in an opportunistic manner.
- the first TX 1 10 may permit reuse of the first TXOP 222 based on historical data regarding previous TXOP reuse permitted by the first TX 110.
- the first TX 1 10 may determine (e.g., measure) an interference level during the reuse.
- the first TX 110 may store the determined interference level (e.g., a transmission performance) at a memory of the first TX 1 10 for later use. Accordingly, the first TX 1 10 may determine whether to permit reuse of the first TXOP 222 based on a history of past transmission performance.
- the first TX 1 10 may calculate the CCA threshold based on one or more margins, such as one or more margins associated with channel dynamics and CCA measurement uncertainties.
- the one or more margins may be adjusted based on the historical data maintained at the first TX 110.
- the first TX 110 may generate and maintain the historical data based on data transmitted or received by the first TX 1 10.
- the reuse TX 140 may adjust the CCA threshold indicated by the first TX 1 10 based on a transmit power of the reuse TX 140 relative to a default transmit power, such as a difference of the transmit power of the reuse TX 140 and the default transmit power.
- the reuse TX 140 can adjust the CCA threshold based on the formula:
- CCA threshold adj CCA threshold FirstControlPortion - (TXPower_reuseTX - Default TX Power),
- CCA threshold adj is the adjusted CCA threshold
- FirstControlPortion is the CCA threshold indicated by the first control portion 224 (e.g., the first message 120), TXPower_reuseTX is the transmit power of the reuse TX 140, and Default TX Power is the default transmit power.
- the first TX 110 may determine whether to define a reuse CCA threshold for use by the reuse TX 140.
- the reuse TX 140 may use a default CCA threshold to determine whether to reuse the first TXOP 222.
- the reuse TX 140 may be configured to use a default CCA threshold having a value defined by a standard, such as a value of -62 dBm or -82 dBm (where dBm is a power ratio in decibels (dB) of a measured power referenced to one milliwatt (mW)).
- the first control portion 224 may indicate the reuse CCA threshold (e.g., as an absolute reuse CCA threshold value or as an offset (e.g., delta) value to be added to or subtracted from a default CCA threshold value).
- the default CCA threshold may be associated with a default transmit power used by the first TX 110 and the first TX 110 may define a different (e.g., lower) reuse CCA threshold when the first TX 110 uses less power than the default transmit power.
- the first TX 1 10 may (dynamically) determine the reuse CCA threshold to be used by the reuse TX 140. For example, the first TX 110 may select the reuse CCA threshold by determining how much interference a link associated with the first TX 110 can tolerate, such as a link between the first TX 110 and the first RX 130. The first TX 1 10 may select the reuse CCA threshold based on how much interference a link associated with the first TX 1 10 can tolerate.
- the first TX 1 10 may determine whether a link associated with the first TX 110 can tolerate one or more other links of a different network, such as an overlapping BSS (OBSS) or a peer- to-peer (P2P) network.
- the first TX 1 10 may determine whether the link associated with the first TX 110 can tolerate interference from another link based on a signal level associated with the link, such as a link between the first TX 110 and the first RX 130.
- OBSS overlapping BSS
- P2P peer- to-peer
- the signal level of the link may be determined at the first TX 1 10 based on an uplink signal, a downlink signal, a signal to noise ratio (SNR), or a received signal strength indication (RSSI), as illustrative, non-limiting examples.
- the first TX 1 10 may compare the signal level to one or more thresholds that each correspond to a different reuse CCA threshold. Additionally or alternatively, the first TX 110 may select the reuse CCA threshold based on a difference between the signal level of the link and an interference level based on another network.
- the reuse CCA threshold may be determined in an opportunistic manner.
- the first TX 1 10 may determine the reuse CCA threshold based on a previous reuse CCA threshold, such as the default CCA threshold, one or more defined reuse CCA thresholds, or a combination thereof.
- the first TX 1 10 may specify a particular reuse CCA threshold to be used by the reuse TX 140.
- the first TX 1 10 may determine whether the particular CCA threshold resulted in satisfactory performance in the past (e.g., an amount of interference that is less than an acceptable threshold). If the particular reuse CCA resulted in satisfactory performance, the first TX 110 may selected the particular reuse CCA threshold to be used again.
- the first TX 1 10 may adjust the particular reuse CCA threshold and provided the adjusted reuse CCA threshold to be used by the reuse TX 140.
- the first TX 110 may determine the CCA threshold based on a MCS, a link budget (e.g., an expected received signal to noise ratio between the first TX 1 10 and the first RX 130), or a combination thereof.
- a transmit power level used by the first TX 110 may be taken into account when the first TX 110 determines the CCA threshold.
- the first TX 110 may determine an initial CCA threshold and may adjust the initial CCA threshold based on the transmit power level of the first TX 110 to determine the CCA threshold.
- the first TX 1 10 may determine the initial CCA threshold based on a default transmit power value and may adjust the initial CCA threshold based on the (actual) transmit power level used to transmit the first message 120.
- the reuse TX 140 may determine whether to reuse the first TXOP based on whether the first message 120 (e.g., a PPDU) is addressed to the reuse TX 140, whether a destination (e.g., a destination address) of the first message 120 (e.g., the PPDU) is the same as a destination of the second message 150, whether the second message 150 is addressed to the first TX 110 or to the first RX 130, whether a signal strength of the first message 120 sent by the first TX 110 and measured by the reuse TX 140 satisfies (e.g., is less than or equal to) a reuse clear channel access (CCA) threshold, or, if there is an honored network allocation vector (NAV), may determine whether the NAV was set by a frame sent by the first TX 1 10, as illustrative, non-limiting examples.
- CCA reuse clear channel access
- NAV network allocation vector
- the destination of the first message 120 may be determined by the reuse TX 140 based on the first control portion 224.
- the first control portion 224 may indicate a transmitter address (TA) associated with the first TX 1 10, may indicate a receiver address (RA) associated with the first RX 130, or may identify the first TX 1 10 or the first RX 130, as described with reference to FIG. 10.
- the reuse CCA threshold may be indicated by the first control portion 224 or may be the default CCA threshold.
- the reuse TX 140 may determine whether the first control portion 224 identifies the reuse CCA threshold. When the first control portion 224 does not identify the reuse CCA threshold, the reuse TX 140 may use the default CCA threshold.
- the reuse TX 140 may compare a signal strength of the first TX 110 to the reuse CCA threshold indicated by the first control portion 224. To illustrate, the reuse TX 140 may determine the signal strength of the first TX 1 10 based on the first control portion 224 and may determine to reuse the first TXOP 222 when the signal strength of the first TX 110 is less than the reuse CCA threshold.
- the reuse TX 140 may determine whether to reuse the first TXOP 222 based on whether a transmission, such as the second message 150, from the reuse TX 140 can tolerate interference from the first TX 1 10. For example, the reuse TX 140 may determine an interference level associated with the first TX 110. The interference level associated with the first TX 110 may be based on the first control portion 224, the first data 226, or another transmission by the first TX 1 10. To illustrate, the first TX 1 10 and the first RX 130 may be in a first BSS and the reuse TX 140 and the reuse RX 160 may be in a second BSS that is an overlapping BSS (OBSS) with respect to the first BSS. Accordingly, the reuse TX 140 may determine whether the second message 150 transmitted in the OBSS can tolerate interference caused by the first TX 1 10 in the first BSS, such as interference caused by transmission of the first message 120.
- OBSS overlapping BSS
- the reuse TX 140 may determine whether the transmission, such as the second message 150, can tolerate interference from the first TX 110 based on a physical proximity of the reuse TX 140 to the reuse RX 160.
- the reuse TX 140 may determine how close the reuse TX 140 is to the reuse RX 160 based on signal level of a link between the reuse TX 140 and the reuse RX 160.
- the reuse TX 140 may determine the signal level of the link between the reuse TX 140 and the reuse RX 160 based on an uplink signal, a downlink signal, a signal to noise ratio (SNR), or a received signal strength indication (RSSI), as illustrative, non-limiting examples.
- SNR signal to noise ratio
- RSSI received signal strength indication
- the reuse TX 140 may compare the signal level to one or more thresholds to determine whether the reuse TX 140 and the reuse RX 160 are physically close enough so that the transmission from the reuse TX 140 to the reuse RX 160 can tolerate interference from the first TX 110.
- the reuse TX 140 may refrain from performing TXOP reuse if the message to be transmitted by the reuse TX 140 during the proposed TXOP reuse is addressed to the first TX 1 10 or the first RX 130 (e.g., based on BSSID/PAID checks).
- the reuse TX 140 may reuse the TXOP to send a message addressed to a device other than the first TX 1 10 or the first RX 130.
- the reuse TX 140 determine whether the reuse TX 140 can tolerate interference from the first TX 110 in an opportunistic manner based on a history of reusing TXOPs. Each time the reuse TX 140 performs a TXOP reuse, the reuse TX 140 may determine (e.g., measure) a performance of the reuse. For each reuse, the reuse TX 140 may determine and record one or more performances parameters (e.g., historical data), such as an interference level during the reuse, whether the message transmitted during the reuse was successful, or another performance parameter, as illustrative, non-limiting examples. The reuse TX 140 may store the performance parameters at a memory of the reuse TX 140 for later use.
- performances parameters e.g., historical data
- the reuse TX 140 may calculate a number of successful transmissions, a rate of successful transmissions, and/or an average interference level based on the stored performance parameters.
- the reuse TX 140 may determine whether the reuse TX 140 can tolerate interference from the first TX 1 10 based on the stored performance parameters. If the reuse TX 140 determines, based on the stored performance data, that the reuse TX 140 can tolerate the interference, and the reuse TX 140 may reuse the first TXOP 222 to transmit the second message 150. If the reuse TX 140 determines, based on the stored performance data, that the reuse TX 140 cannot reuse the TXOP, the reuse TX 140 may refrain from reusing of the first TXOP 222.
- the reuse TX 140 may perform a handshake exchange to determine whether the reuse TX 140 can tolerate interference from the first TX 110.
- the reuse TX 140 may initiate the handshake exchange and send the RTS message 262 based on a determination that the reuse TX 140 can tolerate interference from the first TX 1 10.
- the RTS message 262 may include a bit (or multiple bits) having a value that indicates that the reuse TX is considering reusing the first TXOP 222.
- the handshake exchange may provide the reuse RX 160 an opportunity to allow or not allow the reuse TX 140 to reuse the first TXOP 222.
- the reuse RX 160 may allow or not allow the reuse TX 140 to reuse the first TXOP 222 by setting a value of a bit (or multiple bits) of the CTS message 264.
- the reuse RX 160 may allow the reuse TX 140 to reuse the first TXOP 222 by sending the CTS message 264, and may not allow the reuse TX 140 to reuse the first TXOP 222 by refraining from sending the CTS message 264 to the reuse TX 140.
- the reuse RX 160 may determine to not allow the reuse TX 140 to reuse the first TXOP 222 if the reuse RX 160 honored a particular NAV that was not set by the first TX 110. Additionally or alternatively, the reuse RX 160 may determine to not allow the reuse TX 140 to reuse the first TXOP 222 based on a level of interference detected at the reuse RX 160 or based on one or more CCA thresholds applied at the reuse RX 160.
- the reuse TX 140 aligns an end of the reuse TXOP 270 (e.g., an end of the second TXOP 272) with an end of the first TXOP 222.
- the reuse TX 140 may align the end of the reuse TXOP 270 (e.g., the end of the second TXOP 272) to not exceed the end of the first TXOP 222.
- the reuse TX 140 may prevent out-of-sync transmissions which could lead to collisions in one or more subsequent transmissions, such as one or more subsequent transmission by the first TX 1 10, the first RX 130, the reuse TX 140, or the reuse RX 160.
- the reuse TX 140 may determine a duration of the first TXOP 222.
- the reuse TX 140 may determine the duration of the first TXOP 222 based on an L-SIG field associated with the first message 120, such as a legacy signal (L-SIG) field included in PLCP data of the first message 120.
- L-SIG legacy signal
- the reuse TX 140 may determine the duration of the first TXOP 222 based on a difference between a NAV associated with the handshake exchange and a constant value, such as a constant equal to a sum of a short interframe space (SIFS) and a block acknowledgement (BA) time.
- SIFS short interframe space
- BA block acknowledgement
- the first RX 130 may transmit a first block acknowledgement (BA) associated with the first message 120 to the first TX 1 10
- the reuse RX 160 may transmit a second BA associated with the second message to the reuse TX 140, or a combination thereof.
- the first TX 110 or the reuse TX 140 may indicate a time (or a time period) when the second BA is to be communicated (e.g., indicate how the first BA and the second BA are arranged), as described further with reference to FIG. 9.
- FIG. 2 thus illustrates various protocol implementations for TXOP reuse.
- Multiple levels of protection may be built into the protocol to prevent the reuse TX 140 from reusing the first TXOP 222 if the proposed communication during the reuse TXOP 270 would cause interference to data being communicated during the first TXOP 222.
- the first TX 1 10 and/or the first RX 130 may elect to not permit TXOP reuse based on interference tolerance, historical data, etc.
- the reuse TX 140 may nonetheless elect not to reuse the first TXOP 222 based on interference levels, CCA thresholds, historical data, etc.
- the reuse RX 160 may override the reuse TX (e.g., via the CTS message 264).
- the reuse TX 140 may override the reuse TX (e.g., via the CTS message 264).
- the reuse RX 160 may override the reuse TX (e.g., via the CTS message 264).
- the reuse TX 140 may override the reuse TX (e.g., via the CTS message 264).
- the reuse TX 140 may override the reuse TX (e.g., via the CTS message 264).
- FIG. 3 is a timing diagram 300 to illustrate a first illustrative example of reuse of a TXOP as described with reference to FIG. 2.
- a reusability of the first TXOP 222 may be signaled, at 302.
- reuse of the first TXOP 222 may be signaled based on one or more bits included in the first control portion 224, such as one or more bits of a preamble of the first message 120.
- the first time period (1) is illustrated as beginning at the first time (tbl), the first time period (1) may begin prior to the first time (tbl).
- reuse of the first TXOP 222 may be signaled by a management message sent (e.g., broadcast) by the first TX 1 10 prior to a transmission of the first message 120.
- reuse of the first TXOP 222 may be signaled by another device (e.g., a control device, such as an access point of the system 100).
- a reusability determination may be made by the reuse TX 140, at 304.
- the reusability determination may include determining whether reuse of the first TXOP 222 is permitted, determining whether the reuse TX 140 is going to reuse the first TXOP 222, or a combination thereof.
- the second time period (2) is illustrated as beginning at the first time (tbl) and ending at the second time (tb2), the second time period (2) may begin prior to the first time (tbl) or may end subsequent to the second time (tb2).
- one or more reuse deferral rules may be applied by the reuse TX 140, at 306.
- the reuse deferral rules may enable the reuse TX 140 to defer reuse of the first TXOP 222 to another device, as described further with reference to FIG. 8.
- the third time period (3) is illustrated as beginning at the second time (tb2) and ending at the third time (tb3), the third time period (3) may begin before or after the second time (tb2), may end prior to the third time (tb3), or a combination thereof.
- a fourth time period (4) between the third time (tb3) and a fourth time (tb4) the reuse TXOP 270 may occur.
- a fifth time period (5) between the fourth time (tb4) and a fifth time (tb5) one or more block acknowledgements (BAs) may be communicated, at 308.
- a first BA 318 associated with the first message 120 may be received by the first TX 1 10
- a second BA 328 associated with the second message 150 may be received by the reuse TX 140, or a combination thereof.
- the first BA 318 and the second BA 328 may be aligned in time, as shown in FIG. 3, or may be offset, as described further with reference to FIG. 9.
- FIG. 4 is a timing diagram 400 to illustrate a second illustrative example of reuse of a TXOP as described with reference to FIG. 2.
- a reusability of the first TXOP 222 may be signaled, at 302.
- a reusability determination may be made by the reuse TX 140, at 404.
- the reusability determination may include determining whether reuse of the first TXOP 222 is permitted, determining whether the reuse TX 140 is going to reuse the first TXOP 222, or a combination thereof.
- first portion of the second time period (2a) is illustrated as beginning at the first time (tcl) and ending at the second time (tc2), the first portion of the second time period (2) may begin prior to the first time (tcl), may end subsequent to the second time (tc2), or a combination thereof.
- a third time period (3) between the second time (tc2) and a third time (tc3) one or more reuse deferral rules may be applied by the reuse TX 140, at 406. Application of deferral rules is described further with reference to FIG. 8. Although the third time period (3) is illustrated as beginning at the second time (tc2) and ending at the third time (tc3), the third time period (3) may begin before or after the second time (tc2), may end prior to the third time (tc3), or a combination thereof.
- one or more additional reusability determinations may be made by the reuse TX 140, at 414.
- determinations may include determining whether reuse of the first TXOP 222 is allowed by the reuse RX 160.
- the reuse TX 140 may initiate a handshake exchange that includes the RTS message 262 and the CTS message 264. Receipt of the CTS message 264 and/or a value of one or more bits in the CTS message 264 may indicate that the reuse RX 160 is allowing reuse of the first TXOP 222.
- the reuse TXOP 270 may occur.
- a fifth time period (5) between the fifth time (tc5) and a sixth time (tc6) one or more block acknowledgements (BAs) may be received, at 308, as described further with reference to FIG. 9.
- BAs block acknowledgements
- FIG. 5 is a timing diagram to illustrate a second example of reuse of a TXOP and is generally designated 500.
- the first TX 1 10 may begin a handshake exchange with the first RX 130.
- the handshake exchange may be associated with and precede transmission of the first message 120.
- the first TX 1 10 may send a RTS message 532 to the first RX 130 and the first RX 130 may send a clear to send (CTS) message 534 to the first TX 1 10.
- the CTS message 534 may be responsive to the RTS message 532 and may include protection information associated with the first message 120.
- the RTS message 532 and the CTS message 534 may be detectable (and decodable) by one or more devices, such as the first RX 130, the reuse TX 140, the reuse RX 160, or a combination thereof.
- the handshake exchange (e.g., the RTS message 532 and the CTS message 534) may be associated with a network allocation vector (NAV) that is aligned with an end of the first TXOP 222.
- the NAV may be set by the first TX 1 10 and may be honored by one or more other devices, such as the first receiver 130, the reuse TX 140, the reuse RX 160, or a combination thereof.
- the RTS message 532 may include an RX indicator, a modulation and coding scheme (MCS) indicator, or a combination thereof.
- the RX indicator may dictate whether the first RX 130 is to generate an RX CCA threshold, as described further herein.
- the RX CCA threshold may be associated an amount of interference that the first RX 130 can tolerate, such as an amount of interference that can be tolerated during the transmission of the first message 120.
- the MCS indicator may be an index value that identifies a MCS to be used during transmission of the first message 120.
- the RX indicator, the MCS indicator, or a combination thereof may be indicated by one or more bits of the RTS message 532, as described further herein.
- the CTS message 534 may include an RX CCA threshold indicator, an MCS indicator, or a combination thereof.
- the CTS message 534 may include one or more bits that indicate a value of the RX CCA threshold, an MCS index, or a combination thereof.
- the RX CCA threshold may be determined by the first RX 130 and may be associated with an amount of inference (e.g., an interference level) that the first RX 130 can tolerate.
- the RX CCA threshold may be determined by the first RX 130 responsive to the RTS message 532 (e.g., responsive to the RX indicator).
- the first RX 130 may receive the RTS message 532 and determine whether a value of the RX indicator requests that the first RX 130 determines the RX CCA threshold.
- the RX CCA threshold determined by the first RX 130 may be based on a MCS, such as a particular MCS to be used by the first TX 1 10.
- the first RX 130 may identify the MCS.
- the MCS may be identified as a default MCS (as defined by a standard, such as an IEEE 802.1 1 standard), may be based on the MCS indicator included in the RTS message 532, or may be determined by the first RX 130 based on historical data (e.g., past performance data) stored at the first RX 130.
- the first RX 130 may determine the RX CCA threshold. To illustrate, the first RX 130 may be able to tolerate more interference when the MCS is low.
- the first TX 110 may begin transmitting the first message 120 to the first RX 130.
- the first TX 1 10 may begin transmitting the first data 226 to the first RX 130.
- a transmission of the first data 226 may coincide with a beginning of the first TXOP 222.
- the reuse TX 140 may determine whether to reuse the first TXOP 222 to transmit the second message 150, as described further herein. For example, the reuse TX 140 may determine whether to reuse the first TXOP 222 prior to the first TXOP 222 beginning or during the first TXOP 222. When the reuse TX 140 determines not to reuse the first TXOP 222, the reuse TX 140 may defer to the first TXOP 222 (e.g., may not send the second message 150 during the first TXOP 222). When the reuse TX 140 determines to reuse of the first TXOP 222, the reuse TX 140 may transmit the second message 150 at a fourth time (td4).
- td4 fourth time
- the reuse TX 140 may determine to reuse the first TXOP 222 based on whether reuse of the first TXOP 222 is permitted, based on whether a CCA level of the CTS message 564 is less than the RX CCA threshold, based on whether a CCA level of first TX 1 10 is less than the reuse CCA threshold indicated by the first TX 110, based on whether the first message 120 is addressed to the reuse TX 140 or the reuse RX 160, based on whether the second message 150 is addressed to the first TX 1 10 or the first RX 130, or if there is honored an NAV, whether the NAV was sent by the first TX 1 10 or the first RX 130, as illustrative, non-limiting examples.
- the reuse TX 140 may not reuse the first TXOP 222 when reuse of the first TXOP 222 is not permitted, when the CCA level of the CTS message 564 is greater than or equal to the RX CCA threshold, when the CCA level of the first TX 110 is greater than or equal to the reuse CCA threshold, when the first message 120 is addressed to the reuse TX 140 or the reuse RX 160, when the second message 150 is addressed to the first TX 1 10 or the first RX 130, or when there is an honored NAV that was send by a device other than the first TX 110 or the first RX 130.
- the CTS message 564 may indicate whether the reuse TX 140 may reuse the first TXOP 222.
- the reuse RX 160 may indicate that reuse TX 140 can reuse the first TXOP based on whether the reuse RX 160 can tolerate interference from the first TX 110 or the first RX 130.
- the reuse RX 160 can determine whether the reuse RX 160 can tolerate interference from the first TX 110 based on the reuse CCA threshold (e.g., a default CCA threshold or a particular CCA threshold indicated by the first control portion 224).
- the reuse RX 160 can determine whether the reuse RX 160 can tolerate interference from the first RX 130 based on whether a CCA level of the CTS message 534 satisfies the RX CCA threshold associated with the first RX 130 (e.g., the RX CCA threshold indicated by the CTS message 534).
- the reuse RX 160 may indicate that reuse TX 140 may reuse the first TXOP 222 by sending the CTS message 564 to the reuse TX 140 (e.g., by setting a value of one or more bits of the CTS message 564 to indicate that the reuse TX 140 may reuse the first TXOP 222).
- the reuse RX 160 may indicate that reuse TX 140 may reuse the first TXOP 222 by not sending the CTS message 564 to the reuse TX 140 or by sending the CTS message 564 to the reuse TX and setting a value of the one or more bits to indicate that the reuse TX 140 may not reuse the first TXOP 222.
- the reuse TX 140 may initiate transmission of the second message 150.
- transmission of the first message 120 and the second message 150 may end.
- the first message 120 and the second message 150 e.g., the first TXOP 222 and the second TXOP 272
- the first message 120 and the second message 150 may end at different times, such that the second message 150 does not end after the first TXOP 222 ends.
- the first TXOP 222 and the second TXOP 272 may be aligned so that the second TXOP 272 does not exceed the first TXOP 222.
- the reuse TX 140 may set the second TXOP 272 (e.g., a duration of the second TXOP 272) to occur during the first TXOP 222, but not to exceed the first TXOP 222.
- the first TX 110 may determine whether or not to permit reuse of the first TXOP 222 based on historical data. For example, the first TX 110 may generate and maintain the historical data based on one or more messages transmitted by the first TX 110 (e.g., one or more messages having TXOP reuse permitted). The first TX 1 10 can disable the reuse if the historical data indicates that reuse is causing too much interference during the one or more transmissions from the first TX 1 10.
- the first TX 110 may indicate that TXOP reuse is permitted by sending a management message, by setting a value of the RX indicator included in the RTS message 532 to indicate that that the first RX 130 is to determine the RX CCA threshold, or by setting a value of the first control portion 224 to indicate TXOP reuse is permitted, as illustrative, non-limiting examples.
- the CTS message 534 may be "bound" to the first message 120 (e.g., bound to the first data 226 of the first message 120), such that information included in the CTS message 534 is applied to the first message 120 (and not to another message).
- any data that occurs after a short interframe space (SIFS) from the CTS message 534 may be used for binding.
- the data may include timing information that correlates the CTS message 534 to the first message 120.
- an occurrence of the first message 120 a SIFS time after the CTS message 534 may be interpreted as an implicit indication of the binding.
- the first message 120 (e.g., the first control portion 224, such as PLCP data) may include at least a portion of a transmitter address (TA) that may be used to match with a receiver address (RA) included in the CTS message 534 to correlate the first message 120 and the CTS message 534.
- TA transmitter address
- RA receiver address
- a particular RTS message (e.g., the RTS message 532 or the RTS message 562) or a particular CTS message (e.g., the CTS message 534 or the CTS message 564) may include (or indicate) information, such as the RX indicator, the MCS indicator, or the RX CCA threshold, as illustrative, non- limiting examples.
- the information may be included in (or indicated by) one or more bits in a MAC header, such as one or more bits of a service field of the MAC header.
- the information may be included in (or indicated by) one or more bits in a SIG filed of the particular RTS message or the particular CTS message.
- the first RX 130 may calculate the RX CCA threshold based on one or more margins, such as one or more margins associated with channel dynamics and CCA measurement uncertainties.
- the one or more margins may be adjusted based on the historical data maintained at the first RX 130.
- the first RX 130 may generate and maintain the historical data based on data transmitted or received by the first RX 130.
- the first RX 130 may determine the RX CCA threshold based on a MCS, a link budget (e.g., an expected received signal to noise ratio between the first TX 1 10 and the first RX 130), or a combination thereof. Additionally or alternatively, a transmit power level used by first RX 130 may be taken into account when the first RX determines the RX CCA threshold. For example, the first RX 130 may determine an initial RX CCA threshold and may adjust the initial RX CCA threshold based on the transmit power level of the first RX 130 to determine the RX CCA threshold.
- the first RX 130 may determine the initial RX CCA threshold based on a default transmit power value and may adjust the initial RX CCA threshold based on the (actual) transmit power level used to transmit the CTS message 534. For example, if the CTS message 534 is transmitted at 5 decibels (dB) higher than a default transmit power value, the RX CCA threshold may be determined by increasing the initial RX CCA threshold by 5dB.
- dB decibels
- the RTS message 532 transmitted by the first TX 110 may not indicate a MCS.
- the CTS message 534 sent by the first RX 130 may indicate a particular MCS to be used by the first TX 110 to transmit the first message 120, may indicate the RX CCA threshold, or a combination thereof.
- the particular MCS may be selected by the first RX 130.
- the CTS message 534 may indicate the RX CCA threshold, which may be determined based on a default MCS (as defined by a standard).
- the reuse TX 140 may adjust the RX CCA threshold based on a particular MCS associated with the first message 120 (e.g., the particular MCS indicated by the first control portion 224 or the first data 226).
- the CTS message 534 may indicate that the RX CCA threshold is -80 dBm, based on a default MCS index of zero.
- MCS tables may be defined by a standard, such as an 802.11 standard.
- Each MCS index may correspond to a particular combination of modulation and coding parameters.
- a MCS index of zero e.g., MCS0
- MCS0 may correspond to binary phase shift keying (BPSK) modulation with a coding rate of 1/2.
- BPSK binary phase shift keying
- the reuse TX 140 may determine that an actual MCS used by the first TX 1 10 to transmit at least a portion of the first message 120 corresponds to an adjustment of 10 dB relative to the default MCS.
- the reuse TX 140 may adjust the RX CCA threshold by adding 10 dB to generate an adjusted RX CCA threshold of -70 dBm.
- the reuse TX 140 may compare a signal level of the CTS message 534 received at the reuse TX 140 to the adjusted RX CCA threshold and, when the signal level is greater than the adjusted RX CCA threshold (e.g., -70 dBm), the reuse TX 140 may decide not to reuse the first TXOP 222 because the reuse TX 140 would create too much interference at the first RX 130.
- the adjusted RX CCA threshold e.g., -70 dBm
- the reuse TX 140 may adjust the RX CCA threshold indicated in the CTS message 534 based on a transmit power of the reuse TX 140 relative to a default transmit power, such as a difference of the transmit power of the reuse TX 140 and the default transmit power.
- the reuse TX 140 can adjust the RX CCA threshold based on the formula:
- RX CCA threshold_adj RX CCA threshold_CTSmessage - (TXPower_reuseTX - Default TX Power),
- RX CCA threshold_adj is the adjusted RX CCA threshold
- RX CCA threshold_CTSmessage is the RX CCA threshold indicated by the CTS message 534
- TXPower_reuseTX is the transmit power of the reuse TX 140
- Default TX Power is the default transmit power.
- the reuse TX 140 may determine that reuse of a TXOP is permitted based on the first control portion 224, based on a management message received from a device, such as the first TX 1 10, the first RX 130, or another device, based on a header associated with the first message 120, or based on the handshake exchange between the first TX 1 10 and the first RX 130, as illustrative, non- limiting embodiments.
- the reuse TX 140 may determine whether the RX indicator included in the RTS message 532 requests (e.g., dictates) the first RX 130 to determine the RX CCA threshold.
- the reuse TX 140 may determine that reuse of the first TXOP 222 is not permitted. Alternatively or additionally, the reuse TX 140 may determine whether reuse is permitted based on the handshake exchange by determining whether the CTS message 534 indicates the RX CCA threshold. If the CTS message 534 does not indicate the RX CCA threshold, the reuse TX 140 may determine that reuse of the first TXOP 222 is not permitted.
- a NAV associated with the first message 120 may be set according to an RTS/CTS message exchange between the first TX 110 and the first RX 130.
- reuse of the first TXOP 222 may not be allowed (e.g., permitted) if a NAV is set.
- a packet e.g., a RTS message, a CTS message, a PPDU, a
- the reuse TX 140 may update the NAV.
- the reuse TX 140 may also update the NAV in response to a packet that is silent regarding TXOP reuse.
- the reuse TX 140 may maintain (e.g., not update) the NAV.
- the reuse TX 140 may update or maintain the NAV in response to determining whether TXOP reuse is permitted; the determination that the reuse is permitted may be based on a SIG field indication, a CCA threshold, etc., as described herein. If a NAV was previously set for a time exceeding a time of reception of the packet, the NAV may be maintained.
- a packet may indicate whether reuse is allowed during its own duration, independent of the existence of a following (e.g., subsequent) TXOP, and TXOP reuse determination may be performed without maintaining state information (associated with TXOP reuse) other than the NAV.
- the reuse TX 140 may maintain a (e.g., previously set) NAV in response to the RTS message, update the NAV in response to the CTS message, and refrain from reusing the first TXOP 222 based on the updated NAV, which may begin at the time of the CTS message and continue during the first TXOP 222).
- a NAV e.g., previously set
- the reuse TX 140 may update a NAV in response to the RTS message, maintain the updated NAV in response to the CTS message, and refrain from reusing the first TXOP 222 based on the updated NAV, which may begin at the time of the RTS message and may continue during the first TXOP 222).
- the reuse TX 140 may maintain a (e.g., previously set) NAV and may determine whether to reuse the first TXOP 222 based on the NAV.
- the reuse TX 140 may determine whether TXOP reuse is permitted and/or a duration of the first TXOP 222 based on the first message 120 (e.g., based on the first control portion 224). If the RTS message 532 is detected and the CTS message 534 is not detected, the reuse TX 140 may determine whether TXOP reuse is permitted and/or may determine a duration of the first TXOP 222 based on the first message 120 (e.g., based on the first control portion 224).
- the reuse TX 140 may determine not to reuse the first TXOP 222.
- the reuse TX 140 may determine whether TXOP reuse is permitted and/or may determine a duration of the first TXOP 222 based on the first message 120 (e.g., based on the first control portion 224).
- the reuse TX 140 may determine whether TXOP reuse is permitted and/or may determine a duration of the first TXOP 222 based on the CTS message 534.
- the CTS message 534 may indicate that TXOP reuse is permitted, timing information associated with the first message 120, and/or a NAV value.
- the reuse TX 140 may determine not to reuse the first TXOP 222.
- TXOP reuse permission and duration may be determined even when one or more of the RTS message 532, the CTS message 534, and the first control portion 224 are not detected.
- the reuse TX 140 may determine that the reuse TX 140 did not detect the CTS message 534 because the first RX 130 is too far away from the reuse TX 140. To enable such a determination, the reuse TX 140 may keep track of relative positions and distances of other devices, based on measuring and tracking communications associated with the other devices. To illustrate, if the reuse TX 140 determines that a packet is sent to the first RX 130 and that an acknowledgement from the first RX 130 has a low signal strength, the reuse TX 140 may infer that the first RX 130 is far away.
- the reuse TX 140 may determine to reuse the first TXOP 222 based on a determination that the reuse RX 160 can tolerate interference generated by the first TX 110. For example, the reuse TX 140 may determine that the reuse RX 160 can tolerate interference generated by the first TX 1 10 based on a physical proximity of the reuse TX 140 to the reuse RX 160. The reuse TX 140 may determine how close the reuse TX 140 is to the reuse RX 160 based on signal level of a link between the reuse TX 140 and the reuse RX 160.
- the reuse TX 140 may determine the signal level of the link between the reuse TX 140 and the reuse RX 160 based on an uplink signal, a downlink signal, a signal to noise ratio (SNR), or a received signal strength indication (RSSI), as illustrative, non-limiting examples.
- the reuse TX 140 may compare the signal level to one or more thresholds to determine whether the reuse TX 140 and the reuse RX 160 are physically close enough so that the transmission from the reuse TX 140 to the reuse RX 160 can tolerate interference.
- the reuse TX 140 may determine that the reuse RX 160 can tolerate interference generated by the first TX 1 10 in an opportunistic manner based on a history of reusing TXOPs.
- the reuse TX 140 may determine a performance of the reuse and record one or more
- the one or more performance parameters may include an interference level during the reuse, whether the message transmitted during the reuse was successful, or another performance parameter, as illustrative, non-limiting examples.
- the reuse TX 140 may determine whether the reuse RX 160 can tolerate interference from the first TX 1 10 based on the stored performance parameters, such as based on successful transmissions, a rate of successful transmissions, or an average interference level, as illustrative, non- limiting examples. If the reuse TX 140 determines, based on the stored performance data, that the reuse TX 140 can tolerate the interference, and the reuse TX 140 may reuse the first TXOP 222 to transmit the second message 150.
- the reuse TX 140 may perform a handshake exchange to determine whether the reuse RX 160 can tolerate interference generated by the first TX 110.
- the reuse TX 140 may initiate the handshake exchange and send the RTS message 562 based on a determination that the reuse RX 160 can tolerate interference from the first TX 110.
- the RTS message 562 may include a bit (or multiple bits) having a value that indicates that the reuse TX 140 is considering reusing the first TXOP 222.
- the handshake exchange may provide the reuse RX 160 an opportunity to allow or not allow the reuse TX 140 to reuse the first TXOP 222.
- the reuse RX 160 may allow or not allow the reuse TX 140 to reuse the first TXOP 222 by setting a value of a bit (or multiple bits) of the CTS message 564.
- the reuse RX 160 may allow the reuse TX 140 to reuse the first TXOP 222 by sending the CTS message 564, and may not allow the reuse TX 140 to reuse the first TXOP 222 by refraining from sending the CTS message 564 to the reuse TX 140.
- the reuse RX 160 may determine to not allow the reuse TX 140 to reuse the first TXOP 222 if the reuse RX 160 honored a particular NAV that was not set by the first TX 110. Additionally or alternatively, the reuse RX 160 may determine to not allow the reuse TX 140 to reuse the first TXOP 222 based on a level of interference detected at the reuse RX 160 (e.g., such as an interference level from the first TX 110) or based on one or more CCA thresholds, such as the RX CCA threshold as compared to a CCA level of the first RX 130 (e.g., the CCA level of the first RX 130 detected at the reuse RX 160 based on the CTS message 534).
- a level of interference detected at the reuse RX 160 e.g., such as an interference level from the first TX 110
- CCA thresholds such as the RX CCA threshold as compared to a CCA level of the first RX 130 (e.g., the CCA level of the first RX 130
- the first RX 130 may communicate the RX CCA threshold (associated with the first message 120) to one or more devices without using the handshake exchange with the first TX 1 10 (e.g., without sending the CTS message 534).
- the reuse TX 140 may be able to determine an interference level (based on a transmission of the reuse TX 140) at the first RX 130 without the handshake exchange between the first TX 110 and the first RX 130.
- each packet transmitted by the first TX 1 10, the first RX 130, the reuse TX 140, or the reuse RX 160 may identify a transmit device and a receiver device associated with the packet, and may indicate whether a TXOP associated with the packet may be reused.
- each packet may identify the transmit device and the receive device and/or may indicate that the TXOP associated with the packet may be reused based on one or more bits included in a SIG field of the packet.
- the reuse TX 140 may generate historical statistics (e.g., historical data, such as performance parameters) by tracking the transmitter device and the receiver device of the packet and/or by tracking whether reuse of the TXOP associated with the packet is permitted. If the reuse TX 140 does not have sufficient historical statistics for the first TX 110 and the first RX 130, then the reuse TX 140 may not reuse the first TXOP 222.
- historical statistics e.g., historical data, such as performance parameters
- the RX CCA threshold may be indicated by a SIG field associated with the first message 120.
- the first RX 130 may indicate the RX CCA threshold in a block acknowledgement (BA) transmitted by the first RX 130 (e.g., indicated based on one or more bits included in the BA).
- the first RX 130 may indicate the RX CCA threshold using one or more management messages sent by the first RX 130 to one or more devices within a transmission range of the first RX 130.
- the first RX 130 may periodically perform a handshake exchange with the first TX 110 to communicate the RX CCA threshold in a CTS message. For example, the periodic handshake exchange may be used once out of every ten transmissions.
- the RX CCA threshold communicated in the CTS message may be used until a new RX CCA threshold is communicated in a subsequent CTS message.
- the first RX 130 may provide interference information (e.g., an amount of interference detected at the first RX 130 due to a particular device, such as the reuse TX 140) using one or more management messages sent by the first RX 130 to one or more devices within a transmission range of the first RX 130.
- the reuse TX 140 may determine a CCA level of the first RX 130 based on one or more transmissions from the first RX 130, such as a block acknowledgement (BA) transmission.
- BA block acknowledgement
- the reuse TX 140 may also determine an interference level of the reuse TX 140 at the first RX 130 based on a periodic handshake exchange between the first TX 110 and the first RX 130. For example, the periodic handshake exchange may be used once out of every ten transmissions.
- FIG. 5 thus illustrates various protocol implementations for TXOP reuse.
- the reuse TX 140 may receive the RX CCA threshold or may determine the interference level cause by the reuse TX 140 at the first RX 130.
- the use of the handshake exchange e.g., RTS/CTS messages
- the first RX 130 to provide (e.g., communicate) the RX CCA threshold to one or more devices.
- the handshake exchange between the first TX 1 10 and the first RX 130 may enable the reuse TX 140 to determine an interference level caused by the reuse TX 140 at the first RX 130.
- the RX CCA threshold may be provided and the interference level caused by the reuse TX 140 at the first RX 130 may be determined without use of the handshake exchange between the first TX 110 and the first RX 130.
- the reuse TX 140 may have more information to enable the reuse TX 140 to make decide whether or not to reuse the first TXOP 222.
- FIG. 6 is a timing diagram 600 to illustrate a first illustrative example of reuse of a TXOP as described with reference to FIG. 5.
- a reusability of the first TXOP 222 may be signaled, at 602.
- reusability of the first TXOP 222 may be signaled based on one or more bits included in the RTS message 532, one or more bits included in the CTS message 534, or one or more bits included in the first control portion 224.
- the first time period (1) is illustrated as beginning at the first time (tel), the first time period (1) may begin prior to the first time (tel).
- reusability of the first TXOP 222 may be signaled by a management message sent (e.g., broadcast) by the first TX 1 10 prior to a transmission of the RTS message 532 (e.g., prior to the first message 120).
- reuse of the first TXOP 222 may be signaled by another device (e.g., a control device, such as an access point of the system 100).
- a reusability determination may be made by the reuse TX 140, at 604.
- the reusability determination may include determining whether reuse of the first TXOP 222 is permitted, determining whether the reuse TX 140 is going to reuse the first TXOP 222, or a combination thereof.
- the second time period (2) is illustrated as beginning at the first time (tel) and ending at the second time (te2), the second time period (2) may begin prior to the first time (tel) or may end subsequent to the second time (te2).
- a third time period (3) between the second time (te2) and a third time (te3) one or more reuse deferral rules may be applied by the reuse TX 140, at 606.
- the third time period (3) is illustrated as beginning at the second time (te2) and ending at the third time (te3), the third time period (3) may begin before or after the second time (te2) and may end prior to the third time (te3).
- the reuse TXOP 270 may occur.
- a fifth time period (5) between the fourth time (te4) and a fifth time (te5) one or more block acknowledgements (BAs) may be communicated, at 608.
- the first BA 318 associated with the first message 120 may be received by the first TX 1 10 and a second BA 328 associated with the second message 150 may be received by the reuse TX 140.
- the first BA 318 and the second BA 328 may be aligned in time, as shown in FIG. 6, or may be offset, as described further with reference to FIG. 9.
- FIG. 7 is a timing diagram 700 to illustrate a second illustrative example of reuse of a TXOP as described with reference to FIG. 5.
- a reusability of the first TXOP 222 may be signaled, at 602.
- a reusability determination may be made by the reuse TX 140, at 704.
- the reusability determination may include determining whether reuse of the first TXOP 222 is permitted, determining whether the reuse TX 140 is going to reuse the first TXOP 222, or a combination thereof.
- first portion of the second time period (2a) is illustrated as beginning at the first time (tfl) and ending at the second time (tf2), the first portion of the second time period (2a) may begin prior to the first time (tfl) or may end subsequent to the second time (tf2).
- a third time period (3) between the second time (tf2) and a third time (t ) one or more reuse deferral rules may be applied by the reuse TX 140, at 706.
- the third time period (3) is illustrated as beginning at the second time (tf2) and ending at the third time (tf3), the third time period (3) may begin before or after the second time (tf2) or may end prior to the third time (tf3).
- one or more additional reusability determinations may be made by the reuse TX 140, at 714.
- determinations may include determining whether reuse of the first TXOP 222 is allowed by the reuse RX 160.
- the reuse TXOP 270 may occur.
- a fifth time period (5) between the fifth time (tf5) and a sixth time (tf6) one or more block acknowledgements (BAs) may be received, at 608, as described further with reference to FIG. 9.
- BAs block acknowledgements
- FIG. 8 is a timing diagram 800 to illustrate an illustrative example of reuse of a TXOP, including a deferral/backoff period. It should be noted that handling of deferral rules or backoff rules, as described with reference to FIG. 8, may be applicable to any embodiment described herein (e.g., independent of whether TXOP reuse is RX- controlled, TX-controlled, involves one or more CCA thresholds, involves one or more RTS/CTS exchanges, etc.).
- the reuse TX 140 Prior to a first time (tgl), the reuse TX 140 may receive an indication that the reuse TX 140 is permitted to reuse the first TXOP 222.
- the reuse TX 140 may experience a processing delay, at 804.
- the processing delay may associated with the reuse TX 140 making a determination whether the reuse TX 140 can reuse the first TXOP 222 or making a determination whether the reuse TX 140 is going to reuse the first TXOP 222.
- the reuse TX 140 may apply, at 806, one or more deferral rules and/or one or more backoff rules.
- the one or more deferral/backoff rules may be applied during a backoff window having a size illustrated between the second time (tg2) and a third time (tg3).
- the reuse TX 140 may apply the one or more deferral/backoff rules to prevent multiple devices from reusing the first TXOP 222 at the same time. For example, only one reuse of a TXOP may be permitted.
- the one or more deferral/backoff rules may include "reuse" CCA rules, such as a CCA energy detection (ED) threshold rule, a CCA preamble detection (PD) threshold rule, or a combination thereof.
- the CCA ED threshold rule may set a CCA ED threshold to a value equal to or greater than a signal level from the first TX 110 detected at the reuse TX 140. Accordingly, data transmitted during the first TXOP 222 may not cause a positive CCA ED indication at the reuse TX 140.
- the CCA PD threshold rule may set a CCA PD threshold based on standard (e.g., an IEEE 802.11 standard). In a particular embodiment, the CCA PD threshold used by the reuse TX 140 may be the same regardless of whether or not the reuse TX 140 may reuse the first TXOP 222.
- the one or more backoff rules may include one or more rules to cause the reuse TX 140 to refrain from reusing the first TXOP 222.
- the reuse TX 140 may stop reusing (or attempting to reuse) the first TXOP 222 if a preamble transmitted from another device is detected during a deferral/backoff period (e.g., during the backoff window), at 806.
- the reuse TX 140 may resume its backoff procedure, which was suspended by the reception of the first control portion 224.
- the size of the backoff window may be a default size or may be adjustable based on one or more parameters.
- the size of the backoff window may or may not include the processing delay indicated at 804.
- the size of the backoff window may be determined as a function of an interference level from the reuse TX 140 to the first RX 130, as a function of an expected channel reuse gain, or as a function of an amount of data stored in a queue at reuse TX 140 (e.g., an amount of data to be transmitted by the reuse TX 140), as illustrative, non-limiting examples.
- the reuse TX 140 may reuse the first TXOP 222 and may initiate transmission of the second message 150 after the deferral/backoff period, as shown.
- the reuse TX 140 determines prior to the first time (tgl) whether the reuse TX 140 can reuse the first TXOP 222 and whether the reuse TX 140 is going to reuse the first TXOP 222.
- the reuse TX 140 may not experience the processing delay at 804.
- FIG. 9 is a timing diagram 900 to illustrate examples of handling block acknowledgements (BAs) associated with the first message 120 and the second message 150. It should be noted that handling of BAs, as described with reference to FIG. 9, may be applicable to any embodiment described herein (e.g., independent of whether TXOP reuse is RX-controlled, TX-controlled, involves one or more CCA thresholds, involves one or more RTS/CTS exchanges, etc.).
- the first TX 110 may initiate communication of the first message at a first time (thl).
- a time (th2) the first data 226 of the first message 120 may be transmitted.
- the first data 226 may be transmitted during the first TXOP 222 associated with the first message 120.
- a duration of the first TXOP 222 may end at a third time (th3).
- the first RX 130 may transmit a first block acknowledgement (BA) 928 to the first TX 1 10.
- the first BA 928 may include or correspond to the BA 318 of FIGs. 3-4 and 6-7.
- the first BA 928 is illustrated as being transmitted at the third time (th3), the first BA 928 may be transmitted at any time after the third time (th3).
- the reuse TX 140 may reuse the first TXOP 222 and may transmit the second message 150 during the first TXOP 222. Based on the second message 150, the reuse RX 160 may send a second BA 958 to the reuse TX 140.
- the second BA 958 may include or correspond to the BA 328 of FIGs. 3-4 and 6-7.
- Several approaches may be used to arrange (in time) the second BA 958 transmitted by the reuse RX 160 with respect to the first BA 928 transmitted by the first RX 130.
- the second BA 958 may be delayed with respect to the first BA 928 and may be requested by the reuse TX 140 using a BA request (BAR) 956.
- BAR BA request
- the reuse RX 160 may transmit the second BA 958 during the first TXOP 222.
- the reuse TX 140 may determine that the second BA 958 may be interfered with by the first TX 1 10 and the reuse RX 160 may determine that the first RX 130 can tolerate interference caused by the reuse RX 160.
- a handshake exchange may be performed between the first TX 1 10 and the first RX 130 prior to transmission of the first message 120, between the reuse TX 140 and the reuse RX 160 prior to transmission of the second message 150, or a combination thereof.
- one or more policies may be used for BA transmission by the reuse RX 160.
- the reuse RX 160 may follow a BA policy specified by the reuse TX 140, such as the BA policy specified by one or more requests provided by the reuse TX 140.
- the reuse RX 160 may always follow the BA policy specified by the reuse TX 140. For example, when an "immediate BA" (e.g., following a transmission of the second message 150) is requested from the reuse TX 160 by the reuse TX 140, the reuse RX 160 may send the BA 958 without checking if a transmission of the BA 958 may interfere with the first RX 130.
- the reuse RX 160 may have flexibility (e.g., discretion) to not transmit the BA 958 when requested to do so by the reuse TX 140, such as flexibility based on one or more rules.
- the reuse RX 160 may use one or more of the same rules used by the reuse TX 140 to determine whether a transmission of the BA 958 by the reuse RX 160 may interfere with the first RX 130.
- the reuse RX 160 may apply the RX CCA threshold associated with the first RX 130.
- the reuse RX 160 may determine the RX CCA threshold based on one or more management messages sent by the first RX 130 to one or more devices within a transmission range of the first RX 130, based on a handshake exchange (e.g., a RTS/CTS exchange) between the first TX 110 and the first RX 130 or between the reuse TX 140 and the reuse RX 160, or based on the first control portion 224 of the first message 120, as illustrative, non-limiting examples.
- a handshake exchange e.g., a RTS/CTS exchange
- the RX CCA threshold may be based on a default MCS, based on a first MCS set by the first TX 1 10 (e.g., the first MCS indicated by the first control portion 224 or the RTS message 532), or based on a second MCS set by the first RX 130 (e.g. the second MCS indicated by one or more management messages, such as the first control portion 224 or the CTS message 534, as illustrative, non-limiting examples).
- the reuse RX 160 may adjust the RX CCA threshold (e.g., indicated in the CTS message 534) based on a transmit power of the reuse RX 160 relative to a default transmit power, such as a difference of the transmit power of the reuse RX 160 and the default transmit power.
- the reuse RX 160 applies one or more rules to determine whether the transmission of the BA 958 by the reuse RX 160 interferes with the first RX 130, immediate transmission of the BA 958 may occur if the transmission of the BA 958 does not cause interference at the first RX 130.
- the reuse TX 140 may be aware that the reuse RX 160 may make a determination of whether or not to immediately send the BA 958.
- the reuse TX 140 may send a BAR 956 to obtain the BA 958 before the reuse TX 140 infers that data needs to be retransmitted.
- the reuse TX 140 may set a BA policy to "immediate BA" (e.g., following a transmission of the second message 150) if the BA 958 from reuse RX 160 can be reliably received.
- a decision by the reuse TX 140 to set the BA policy to "immediate BA” may be based on historic data, such as signal to interference information for transmitted BAs based on network topology information.
- the reuse TX 140 may also use a handshake exchange (e.g., a RTS/CTS exchange) to determine if the BA 958 can be reliably received by the reuse TX 140. For example, if a CTS message (e.g., the CTS message 264 of FIG. 2 or the CTS message 564 of FIG. 5) from the reuse RX 160 is properly received, then the reuse TX 140 may infer that the BA 958 can also be received during the first TXOP 222.
- a CTS message e.g., the CTS message 264 of FIG. 2 or the CTS message 564
- the first BA 928 and the second BA 958 may be transmitted such that the first BA 928 and the second BA 958 at least partially overlapping (in time).
- a determination may be made (e.g., based on handshake exchange(s)) that the first BA 928 and the second BA 958 will not excessively interfere with each other.
- one or more approaches may be used for BA transmission by the reuse RX 160.
- the reuse RX 160 may follow a BA policy specified by the reuse TX 140, such as the BA policy specified by one or more requests provided by the reuse TX 140.
- the reuse RX 160 may always follow the BA policy specified by the reuse TX 140. For example, when an "immediate BA" (e.g., following a transmission of the second message 150) is requested from the reuse TX 160 by the reuse TX 140, the reuse RX 160 may send the BA 958 without checking if a transmission of the BA may interfere with the first RX 130.
- the reuse RX 160 may have flexibility (e.g., discretion) to not transmit a BA when requested to do so by the reuse TX 140.
- the reuse RX 160 may not transmit the BA 958 if the reuse RX 160 determines that the BA 958 may interfere with BA reception at the first TX 1 10 (e.g., the reuse RX 160 may apply one or more rules to determine whether or not to send the BA 958 based on a request from the reuse TX 140).
- the reuse RX 160 may not send a BA if the received signal level from the first TX 1 10 is greater than a CCA threshold indicated by the first TX 140.
- the reuse TX 140 may be aware that the reuse RX 160 may make a determination of whether or not to immediately send the BA 958. When the BA 958 is not immediately received, the reuse TX 140 may send a BAR 956 to obtain the BA 958 before the reuse TX 140 infers that data needs to be retransmitted.
- the second BA 958 may be transmitted a SIFS after the first BA 928.
- the reuse TX 140 may protect the second BA 958 by setting a sufficiently long duration in an L-SIG field of the first message 120.
- policies e.g., rules
- one or more policies described with a specific BA approach may also be applied to another BA approach described herein.
- one or more policies described with reference to the "BA within the first TXOP" approach may also be applicable to the "delayed BA” approach, the "overlapped BA” approach, and/or the "staggered BA” approach.
- one or more policies described with reference to the "overlapped BA” approach may also be applicable to the "delayed BA” approach, the "BA within the first TXOP” approach, and/or the "staggered BA” approach.
- the system 1000 includes a first network 1010 and a second network 1020.
- the system 1000 may include one or more Institute of Electrical and Electronics Engineers (IEEE) 802.11 wireless networks (e.g., one or more Wi-Fi networks).
- IEEE Institute of Electrical and Electronics Engineers
- the system 1000 may operate in accordance with an IEEE 802.1 1 standard.
- the system 1000 includes one or more 802.1 1 high efficiency Wi-Fi (HEW) networks.
- IEEE Institute of Electrical and Electronics Engineers
- the first network 1010 may include one or more wireless devices, such as a first access point (APA) 1012, a first station (STAA2)1016, and a second station (STAAI) 1014.
- the second network 1020 may also include one or more wireless devices, such as a second access point (APB) 1022, a third station (STABI) 1024, and a fourth station (STAB2) 1026.
- the one or more devices of the first network 1010 and the one or more devices of the second network 1020 may include or correspond to the first TX 1 10, the first RX 130, the reuse TX 140, or the reuse RX 160 of FIG. 1.
- the first network 1010 may be associated with a first basic service set (BSS) having a first BSS identification (BSSID) and the second network 1020 may be associated with a second BSS having a second BSSID.
- BSS basic service set
- BSSID BSS identification
- the first BSSID may be defined by a MAC address of the first access point 1012
- the second BSSID may be defined by a MAC address of the second access point 1022.
- the first network 1010 and the second network 1020 may be an overlapping BSS with respect to each other, as shown.
- the first network 1010 or the second network 1020 may include a peer-to-peer communication network using Wi-Fi Direct communication or a tunneled direct link setup communication, as illustrative, non- limiting embodiments.
- the first access point 1012 may transmit a preamble ("PRE") associated with a transmission of a first message from the first access point 1012 to the second station 1016.
- the second access point 1022 may detect the preamble transmitted by the first access point 1012 and may determine whether or not to reuse the corresponding first TXOP associated with the first message from the first access point 1012 to the second station 1016.
- the second access point 1022 may be ready to transmit a second message to the third station 1024 and may determine whether to transmit the second message to the third station 1024 during the first TXOP associated with the first message.
- the second access point 1022 may decide, based on one or more channel conditions, that the second access point 1022 is not going to reuse the first TXOP associated with the first message. Accordingly, the second access point 1022 may defer to the first access point 1012 and may queue the second message for transmission at a subsequent point in time.
- the second access point 1022 may send a preamble associated with the second message.
- the first access point 1012 may detect the preamble associated with the second message and may determine whether or not to reuse the corresponding second TXOP associated with the second message.
- the first access point 1012 may decide, based on one or more channel conditions, to reuse the second TXOP associated with the second message transmitted by the second access point 1022. Accordingly, the first access point 1012 may transmit a third message from the first access point 1012 to the first station 1014 during the second TXOP associated with the second message. Further, the first access point 1012 may align a third TXOP associated with the third message with the second TXOP associated with the second message such that both TXOPs end at a third time (ti3), as shown.
- a particular embodiment of a method 1100 of operating a first transmitter is described and designated 1 100.
- the method 1100 may be performed using the first transmitter 110 of FIG. 1, one of the access points 1012, 1022, or one of the stations 1014, 1016, 1024, 1026 of FIG. 10.
- the method 1100 may include determining whether to permit reuse of a first transmit opportunity (TXOP), at 1102.
- TXOP transmit opportunity
- the first TXOP may include or correspond to the first TXOP 222 of FIG. 2.
- a first transmit opportunity may include or correspond to the first TXOP 222 of FIG. 2.
- the determination of whether to permit reuse of the first TXOP is based on a signal strength of a link between a first transmitter and a first receiver in a first basic service set (BSS). For example, the determination may be based on a difference between the signal strength and an overlapping basic service set (OBSS) interference level. In another particular embodiment, a determination of whether to permit reuse of the first TXOP is based on a comparison of the OBSS interference level to a transmission history of the first transmitter.
- BSS basic service set
- the method 1100 may further include sending a message associated with the first TXOP, where the message indicates whether reuse, by a reuse transmitter, of the first TXOP is permitted, at 1104.
- the message may include or correspond to the first message 120 of FIG. 1 or the RTS message 532 of FIG. 5 (or a portion thereof, such as a preamble or PLCP data).
- the message may indicate that reuse of the first TXOP is permitted based on one or more values in a signal (SIG) field of the message. Additionally or alternatively, the SIG field may indicate a transmitter address associated with the first transmitter or may indicate a receiver address associated with the first receiver.
- SIG signal
- the SIG field may be an Institute of Electrical and Electronics Engineers (IEEE) 802.1 lac SIG-A field.
- IEEE Institute of Electrical and Electronics Engineers
- the SIG field is included in a preamble of the message, such as a high efficiency wireless (HEW) preamble.
- the preamble indicates a basic service set identification (BSSID) of the first transmitter.
- BSSID basic service set identification
- the first transmitter and the first receiver are included in a peer-to-peer network.
- the reuse transmitter is included in a peer-to-peer network with a reuse receiver.
- the method 1100 may enable the first transmitter to indicate to one or more other devices that a TXOP of a message transmitted by the first transmitter is permitted to be reused.
- a reuse TX may automatically determine whether to reuse a TXOP without receiving or detecting such an explicit indication (that TXOP reuse is permitted) from the first TX or the first RX.
- an explicit indication e.g., an allowance and/or threshold indication
- a reuse TX may automatically determine whether to reuse a TXOP without receiving or detecting such an explicit indication (that TXOP reuse is permitted) from the first TX or the first RX.
- the first TX may transmit a first message, such as an RTS message, a CTS message, a PPDU, etc. under "normal" contention (e.g., CSMA or another contention resolution mechanism), where the first message is associated with a first TXOP.
- the first message (or at least a portion thereof) may include information that is useable by the reuse TX to identify a source and a destination of the first message.
- the first message may include one or more bits in a PHY SIG field that can be used to identify the first TX as the source of the first message and/or identify the first RX as the destination of the first message.
- the reuse TX may determine not to reuse the first TXOP to send a second message during the first TXOP when the first message is addressed to the reuse TX, when the destination of the first message is the same as a destination of the second message, when the second message is addressed to the first TX or to the first RX, or any combination thereof.
- the reuse TX may determine whether to reuse a particular TXOP (associated with a particular message sent by the first transmitter) based on data associated with prior TXOP (associated with a prior message sent by the first transmitter).
- the data be included in historical data and may indicate whether the reuse transmitter received an express permission to reuse the prior TXOP.
- the reuse TX may determine whether to reuse the particular TXOP based a previous express permission that corresponds to reuse of the previous TXOP.
- the first TX and/or the first RX may be identified based on a partial BSSID, such as a partial BSSID included in the first message, as described with reference to FIG. 1 regarding uplink (UL) transmissions, downlink (DL) transmissions, and P2P transmissions.
- a partial BSSID such as a partial BSSID included in the first message
- the reuse TX may determine to reuse the first TXOP (to send a second message during the first TXOP) when the first message (e.g., PPDU) is not addressed to the reuse TX, when a destination of the first message is not the same as a destination of the second message, when the second message is not addressed to the first TX or to the first RX, when a signal strength of the first message satisfies (e.g., is less than or equal to) reuse clear channel access (CCA) threshold(s) and/or RX CCA threshold(s), and/or when a network allocation vector (NAV) has not already been set, as illustrative, non-limiting examples.
- CCA reuse clear channel access
- NAV network allocation vector
- the reuse CCA threshold may be a function of a MCS of the first message, a TX power at which the reuse TX will transmit the second message, the type of preamble (1 ln/1 lac/1 lax), one or more other indications included in the first message (e.g., in a SIG field), such as a duration, a short guard interval (GI), a long GI, a coding (e.g., an indication of binary convolutional coding (BCC) or low- density parity check (LDPC) in an 802.1 lac or 802.1 In packet), a number of spatial streams, a bandwidth, or any combination thereof.
- the reuse TX may determine to reuse the first TXOP to transmit the second message if the following inequality is true:
- RSSIfirst_messa g e ⁇ CCA threshold + (Default TX power - TXPower_reuseTX),
- RSSIfkst message is a signal strength associated with the first message
- Default TX power is a default transmit power of the reuse TX (e.g., as defined in an industry standard, such as an IEEE 802.1 1 standard)
- TXPower_reuseTX is the intended transmit power at which the reuse TX will transmit the second message.
- an intended TX Bandwidth (e.g., used during transmission of the second message during reuse of the first TXOP) may also be used to compute an offset for the CCA threshold, such as:
- RSSIfirst_messa g e ⁇ CCA threshold + Offset(TXBandwidth_reuseTX / Default Bandwidth),
- TXBandwidth reuseTX is the intended TX Bandwidth and the Default Bandwidth may be a value defined by an industry standard or a value corresponding to a bandwidth (BW) associated with a received PPDU.
- BW bandwidth
- the CCA threshold may be a default (e.g., industry standard) CCA threshold, such as -62 dBm or -82dBm.
- the CCA threshold may be adjusted by one or more offsets that are determined based on one or more indicators associated with the first message, such as an offset based on a MCS of the first message, an offset based on a SIG field indicator of the first message, or a combination thereof, as illustrative, non-limiting examples.
- the CCA threshold may be determined based on the following:
- CCA Threshold -62 (or -82) - offset(MCS) + offset(SIG_indication),
- offset(MCS) is an offset based on a MCS of the first message and offset(SIG_indication) is an offset based on a SIG field indicator of the first message.
- the offset may be 0 for MCS0 (corresponding to BPSK modulation, 1/2 coding rate).
- the offset may be 5 for MCS1 (corresponding to quadrature phase shift keying (QPSK), 1/2).
- the offset may be 10 for MCS2
- the offset may be 15 for MCS4 (corresponding to 64-point QAM (64QAM), 2/3).
- the offset may be 20 for MCS5 (corresponding to 64QAM, 2/3).
- the offset may be 25 for MCS6 (corresponding to 64QAM, 3/4) or MCS7 (corresponding to 64QAM, 5/6).
- different offsets values may correspond to different MCS indexes.
- a reuse allowance (e.g., permission) and/or a CCA threshold used to determine whether to reuse the first TXOP may be a function of the type of the first message instead of or in addition to the content of a portion (e.g., SIG field) of the first message.
- the reuse TX may determine a type of the first message prior to decoding the SIG field. For example, if the reuse TX receives an 802.1 In or 802.1 lac packet, the reuse TX may automatically determine that reuse of the first TXOP is not permitted, independent of the value of any specific field(s) in the 802.1 In or 802.1 lac packet. As another example, if the reuse TX receives an 802.1 lax packet, the reuse TX may automatically determine that reuse of the first TXOP is permitted, independent of the value of any specific field(s) in the 802.1 lax packet.
- FIG. 12 a particular embodiment of a method of operating a reuse transmitter is described and designated 1200.
- the method 1200 may be performed using the reuse transmitter 140 of FIG. 1, one of the access points 1012, 1022, or one of the stations 1014, 1016, 1024, 1026 of FIG. 10.
- the method 1200 may include detecting a portion of a message sent by a first transmitter, at 1202.
- the message may include or correspond to the first message 120 of FIG. 1.
- the method 1200 may further include determining, based on the portion, whether reuse of a first transmit opportunity (TXOP) associated with the message is permitted, at 1204.
- TXOP transmit opportunity
- the first TXOP may include or correspond to the first TXOP 222 of FIG. 2.
- the reuse transmitter may determine whether to reuse the first TXOP.
- a determination to reuse the first TXOP may be based on whether the message is addressed to the reuse transmitter, whether a second message to be transmitted by the reuse transmitter during reuse of the first TXOP is addressed to a first receiver of the message, or a combination thereof.
- a determination to reuse the first TXOP may be based on whether a network allocation vector (NAV) honored by the reuse transmitter was set by the first transmitter, based on a physical proximity of the reuse transmitter to a reuse receiver, based on historical data stored at the reuse transmitter, or a combination thereof.
- NAV network allocation vector
- a determination to reuse the first TXOP is based on a handshake exchange between the reuse transmitter and a reuse receiver.
- the handshake exchange may include a request to send (RTS) message or a clear to send (CTS) message.
- RTS request to send
- CTS clear to send
- the RTS message may include the RTS message 262 of FIG. 2 or the RTS message 562 of FIG. 5.
- the CTS message may include the CTS message 264 of FIG. 2 or the CTS message 564 of FIG. 5.
- the handshake exchange may be associated with a network allocation vector (NAV) that is set to be aligned with an end of the first TXOP.
- NAV network allocation vector
- the reuse transmitter determines a duration of the first TXOP based on a legacy signal (L-SIG) field in a preamble associated with the message or based on a network allocation vector (NAV) associated with the first transmitter.
- L-SIG legacy signal
- NAV network allocation vector
- a second message may be sent from the reuse transmitter during the first TXOP.
- the second message may include or correspond to the second message 150 of FIG. 1.
- the second message may be associated with a second TXOP, such as the reuse TXOP 270 or the second TXOP 272 of FIG. 2, that ends prior to or at the same time as the first TXOP.
- the reuse transmitter may receive a block acknowledgement (ACK) associated with the second message from the second receiver.
- the reuse transmitter may send a block ACK request (BAR) to the second receiver and receive the block ACK in response to the block ACK request.
- BAR block ACK request
- the block ACK may also be received during the first TXOP, may be at least a partially received at the same time as the first transmitter receives a block ACK associated with the first message, or may be received at least a short interframe space (SIFS) interval after the first transmitter receives a block ACK associated with the first message, as illustrative, non-limiting examples.
- the block ACK may include or correspond to the block ACK 328 of FIG. 3 or the block ACK 958 of FIG. 9.
- the reuse transmitter in response to a determination to reuse the first TXOP, may apply one or more deferral rules during a backoff window time period.
- the reuse transmitter may determine a signal value of the first transmitter and may set a clear channel access (CCA) energy detection (ED) threshold of the reuse transmitter to a value greater than or equal to the determined signal value.
- CCA clear channel access
- ED energy detection
- the method 1200 may enable the reuse transmitter to determine that a TXOP of a message transmitted by the first transmitter is permitted to be reused.
- FIG. 13 a particular embodiment of a method of operating a first transmitter is described and designated 1300.
- the method 1300 may be performed using the first transmitter 110 of FIG. 1, one of the access points 1012, 1022, or one of the stations 1014, 1016, 1024, 1026 of FIG. 10.
- the method 1300 may include determining a clear channel access (CCA) threshold associated with reuse of a first transmit opportunity (TXOP), at 1302.
- the CCA threshold may be dynamically determined by the first transmitter.
- the first TXOP may include or correspond to the first TXOP 222 of FIG. 2.
- the method 1300 may further include sending at least a portion of a message associated with the first TXOP, where portion indicates the CCA threshold associated with reuse of the first TXOP, at 1304.
- the message may include or correspond to the first message 120 of FIG. 1.
- the portion of the message may indicate the CCA threshold based on a value (e.g., a value of one or more bits) in a signal (SIG) field, such as a SIG field included in a preamble of the message.
- the CCA threshold indicated by the portion of the message is less than a standard-based CCA threshold associated with reuse of the first TXOP.
- the portion of the message may further indicate that reuse of the first TXOP is permitted.
- the portion of the message indicates that reuse of the first TXOP is allowed based on a value (e.g., a value of one or more bits) in a signal (SIG) field.
- the CCA threshold is determined prior to sending the message.
- the CCA threshold may be determined based on a signal strength of a link between the first transmitter and the first receiver in a basic service set (BSS) or based on an interference level of an overlapping basic service set (OBSS), as illustrative, non-limiting examples.
- BSS basic service set
- OBSS overlapping basic service set
- the CCA threshold is determined based on a previous CCA threshold used in association with a particular message communicated by the first transmitter prior to the message.
- the previous CCA threshold may be adjusted, based on a performance assessment associated with communication of the particular message, to generate the CCA threshold.
- the method 1300 may enable the first transmitter to specify the CCA threshold to be used by one or more devices. Accordingly, the one or more devices may use the CCA threshold to determine whether to reuse the first TXOP associated with the message transmitted by the first transmitter.
- FIG. 14 a particular embodiment of a method of operating a reuse transmitter is described and designated 1400.
- the method 1400 may be performed using the reuse transmitter 140 of FIG. 1, one of the access points 1012, 1022, or one of the stations 1014, 1016, 1024, 1026 of FIG. 10.
- the method 1400 may include detecting a portion of a message sent by a first transmitter, where the message is associated with a first transmit opportunity (TXOP), at 1402.
- TXOP transmit opportunity
- the message and the first TXOP may include or correspond to the first message 120 of FIG. 1 and the first TXOP 222 of FIG. 2, respectively.
- the method 1400 may further include determining, based on the portion, a clear channel access (CCA) threshold associated with reuse of the first TXOP, at 1404.
- the reuse transmitter may send a second message, such as the second message 150 of FIG. 1, based on the CCA threshold.
- the second message may be sent during the first TXOP.
- the reuse transmitter may perform a performance assessment associated with CCA
- the reuse transmitter may determine whether or not to reuse a second TXOP that is subsequent to the first TXOP.
- the reuse transmitter determines whether to reuse the first TXOP. For example, the reuse transmitter may determine to reuse the first TXOP based on whether a CCA level of the first transmitter is less than or equal to the CCA threshold, based on whether the message is addressed to the reuse transmitter, based on whether a second message to be transmitted by the reuse transmitter during reuse of the first TXOP is addressed to a first receiver of the message, or based on whether a network allocation vector (NAV) that is honored by the reuse transmitter was set by the first transmitter, as illustrative, non- limiting examples.
- NAV network allocation vector
- the reuse transmitter may determine to reuse the first TXOP is based on a physical proximity of the reuse transmitter to a reuse receiver or based on a handshake exchange between the reuse transmitter and a reuse receiver.
- the handshake exchange may include a request to send (RTS) message or a clear to send (CTS) message and the reuse transmitter may set a network allocation vector (NAV) associated with the handshake exchange to be aligned with an end of the first TXOP.
- RTS request to send
- CTS clear to send
- the method 1400 may enable the reuse transmitter to determine whether to reuse a TXOP of a message transmitted by the first transmitter based on a CCA threshold dictated by the first transmitter.
- the method 1500 may be performed using the first transmitter 1 10 of FIG. 1, one of the access points 1012, 1022, or one of the stations 1014, 1016, 1024, 1026 of FIG. 10.
- the method 1500 may include sending, to a first receiver, a request to send (RTS) message associated with a first transmit opportunity (TXOP), where the RTS message requests the first receiver to indicate whether reuse of the first TXOP is permitted, at 1502.
- RTS request to send
- TXOP transmit opportunity
- MCS modulation and coding scheme
- the RTS message may include or correspond to the RTS message 532 of FIG. 5, and the first TXOP may include or correspond to the first TXOP 222 of FIG. 2.
- a request to indicate whether reuse of the first TXOP is permitted may be included in a media access control (MAC) portion of the RTS message or may be included in a signal (SIG) field of the RTS message, as illustrative, non-limiting embodiments.
- the first transmitter may align a network allocation vector (AV) of the RTS message with an end of the first TXOP.
- the method 1500 may further include receiving, from the first receiver, a clear to send (CTS) message responsive to the RTS message, at 1504.
- CTS clear to send
- the CTS message may include or correspond to the CTS message 534 of FIG. 5.
- the first transmitter may determine whether the reuse of the first TXOP is permitted based on the CTS message received from the receiver. When the first transmitter determines to permit reuse of the first TXOP, the first transmitter may send a portion, such as a preamble, of a message (associated with the first TXOP) to indicate that reuse of the first TXOP is permitted.
- the first transmitter determines, based on the CTS message, a receiver clear channel access (RX CCA) threshold associated with the first receiver.
- RX CCA receiver clear channel access
- the RX CCA threshold may be indicated by one or more bits included in CTS message.
- the CTS message indicates a modulation and coding scheme (MCS) to be used during communication of a subsequent message between the first transmitter and the first receiver.
- MCS modulation and coding scheme
- the CTS message includes a particular RX CCA threshold of the first receiver.
- the particular RX CCA threshold may be associated with a first modulation and coding scheme (MCS), such as a default MCS, and the first transmitter may adjust the particular RX CCA threshold to generate the RX CCA threshold.
- MCS modulation and coding scheme
- the first transmitter may adjust of the particular RX CCA threshold based on a second MCS (used by the first transmitter) that is different than the first MCS.
- the method 1500 may enable the first transmitter to request the first receiver whether or not the first transmitter should permit reuse of the first TXOP, thereby providing control of the reuse of the first TXOP to the first receiver.
- FIG. 16 a particular embodiment of a method of operating a first receiver is described and designated 1600.
- the method 1600 may be performed using the first receiver 130 of FIG. 1, one of the access points 1012, 1022, or one of the stations 1014, 1016, 1024, 1026 of FIG. 10.
- the method 1600 may include receiving a request to send (RTS) message send by a first transmitter, at 1602.
- RTS request to send
- the RTS message may include or correspond to the RTS message 532 of FIG. 5.
- the method 1600 may further include sending, to the first transmitter, a clear to send (CTS) message associated with a first transmit opportunity (TXOP), where the CTS message indicates whether reuse of the first TXOP is permitted, at 1604.
- CTS clear to send
- TXOP first transmit opportunity
- the CTS message may include or correspond to the CTS message 534 of FIG. 5, and the first TXOP may include or correspond to the first TXOP 222 of FIG. 2.
- a media access control (MAC) portion or a SIG field of the CTS message may indicate that reuse of the first TXOP is permitted, may indicate a receiver (RX) clear channel access (CCA) threshold, may indicate a modulation and coding scheme (MCS), or a combination thereof.
- RX receiver
- MCS modulation and coding scheme
- the first receiver may determine a modulation and coding scheme (MCS) based on the RTS message. Based on the MCS, the first receiver may determine a receiver (RX) clear channel access (CCA) threshold associated with the first receiver. Alternatively, the first receiver may determine the RX CCA threshold based on a default MCS. The CTS message sent by the first receiver may indicate the RX CCA threshold determined by the first receiver.
- MCS modulation and coding scheme
- CCA clear channel access
- the first receiver determines the RX CCA threshold based on a transmit power value associated with the CTS message.
- the first receiver may determine a particular RX CCA threshold of the first receiver and may determine a transmit power value associated with the CTS message. Based on the transmit power value, the first receiver may adjust the particular RX CCA threshold to generate the RX CCA threshold.
- the RX CCA threshold may be determined based on one or more channel dynamics, a CCA measurement uncertainty, or historical statistics, as illustrative, non-limiting examples.
- the method 1600 may enable the first receiver to dictate whether reuse of the first TXOP should be permitted by the first transmitter. By having control of whether reuse of the first TXOP is permitted, the first receiver may not permit the first TXOP to be reused when the first receiver determines that reuse of the first TXOP would cause an amount of interference that would impede reception of a message associated with the first TXOP.
- FIG. 17 a particular embodiment of a method of operating a reuse transmitter is described and designated 1700.
- the method 1700 may be performed using the reuse transmitter 140 of FIG. 1, one of the access points 1012, 1022, or one of the stations 1014, 1016, 1024, 1026 of FIG. 10.
- the method 1700 may include detecting a portion of a message sent by a first receiver, at 1702.
- the portion of the message may be included in a clear to send (CTS) message sent by the first receiver.
- CTS clear to send
- the CTS message may be responsive to a request to send (RTS) sent by the first transmitter to the first receiver.
- RTS request to send
- the message may include the CTS message 534 of FIG. 5.
- the method 1700 may further include determining, based on the portion, a receiver (RX) clear channel access (CCA) threshold associated with reuse of a first transmit opportunity (TXOP), at 1704.
- RX receiver
- CCA clear channel access
- TXOP first transmit opportunity
- the reuse transmitter may determine whether to reuse the first TXOP based on the RX CCA threshold.
- the reuse transmitter adjusts the RX CCA threshold.
- the reuse transmitter may identify a modulation and coding scheme (MCS) associated with the message and may adjust the RX CCA threshold based on the MCS.
- MCS modulation and coding scheme
- the reuse transmitter may determine a transmit power value associated with the reuse transmitter and may adjust the RX CCA threshold based on the transmit power value.
- the RX CCA threshold may be adjusted based on a difference between the transmit power value and a default transmit power value.
- the reuse transmitter may determine to reuse the first TXOP based on whether a first CCA level of the portion is less than or equal to the adjusted RX CCA threshold.
- the reuse transmitter determines whether to reuse the first TXOP. For example, a determination to reuse the first TXOP may be based on whether a first CCA level of the portion is less than or equal to the RX CCA threshold.
- a determination to reuse the first TXOP may be based on whether a second CCA level of the first transmitter is less than or equal to a CCA threshold associated with the first TXOP, whether the message is addressed to the reuse transmitter, whether a second message to be transmitted by the reuse transmitter during reuse of the first TXOP is addressed to the first receiver to receive the message during the first TXOP, or whether a network allocation vector (NAV) that is honored by the reuse transmitter was set by the first TX, as illustrative, non-limiting examples.
- NAV network allocation vector
- the reuse transmitter may perform a performance assessment associated with communication of the second message. Based on the performance assessment, the reuse transmitter may determine whether to reuse a second TXOP that occurs subsequent to the first TXOP and that is permitted to be reused.
- the reuse transmitter may make a determination to reuse the first TXOP to send a second message during the first TXOP.
- the reuse transmitter may determine to reuse the first TXOP based on a physical proximity of the reuse transmitter to a reuse receiver.
- the reuse transmitter may determine to reuse the first TXOP based on a handshake exchange between the reuse transmitter and a reuse receiver.
- the handshake exchange may include a request to send (RTS) message and a clear to send (CTS) message, and the reuse transmitter may set a network allocation vector (NAV) associated with the handshake exchange to be aligned with an end of the first TXOP.
- RTS request to send
- CTS clear to send
- NAV network allocation vector
- the method 1700 may enable the reuse transmitter to determine whether to reuse the first TXOP based on an amount of interference caused by the reuse transmitter at the first receiver.
- FIG. 18 a particular embodiment of a method of operating a reuse transmitter is described and designated 1800.
- the method 1800 may be performed using the reuse transmitter 140 of FIG. 1, one of the access points 1012, 1022, or one of the stations 1014, 1016, 1024, 1026 of FIG. 10.
- the method 1800 may include determining whether reuse of a first transmit opportunity (TXOP) associated with a first message is permitted, where the first message is transmitted from a first transmitter to a first receiver, at 1802.
- TXOP transmit opportunity
- the first message and the first TXOP may include or correspond to the first message 120 of FIG. 1 and the first TXOP 222 of FIG. 2, respectively.
- the method 1800 may further include determining whether to reuse the first TXOP based on an interference level of the reuse transmitter at the first receiver, at 1804.
- the reuse transmitter may determine the interference level. For example, the reuse transmitter may determine the interference level based on a management message received from the first receiver. As another example, the reuse transmitter may determine the interference level based on a clear channel access (CCA) level associated with first receiver. To illustrate, the reuse transmitter may determine the CCA level based on a block acknowledgement (BA) transmitted by the first receiver. As another example, the reuse transmitter may determine the interference level based on a request to send (RTS) message or a clear to send (CTS) message transmitted from the first receiver. The RTS message or the CTS message may be associated with a particular message transmitted that is prior to the first message.
- RTS request to send
- CTS clear to send
- the method 1800 may enable the reuse transmitter to determine whether to reuse the first TXOP based on an amount of interference caused by the reuse transmitter at the first receiver.
- FIG. 19 a particular embodiment of a method of operating a reuse transmitter is described and designated 1900.
- the method 1900 may be performed using the reuse transmitter 140 of FIG. 1, one of the access points 1012, 1022, or one of the stations 1014, 1016, 1024, 1026 of FIG. 10.
- the method 1900 may include determining whether reuse of a first transmit opportunity (TXOP) associated with a first message is permitted, where the first message is transmitted from a first transmitter to a first receiver, at 1902.
- TXOP transmit opportunity
- the first message and the first TXOP may include or correspond to the first message 120 of FIG. 1 and the first TXOP 222 of FIG. 2, respectively.
- the method 1900 may further include determining whether to reuse the first TXOP based on a receiver (RX) clear channel access (CCA) threshold associated with the first receiver, at 1904.
- the reuse transmitter may determine the RX CCA threshold.
- the reuse transmitter may determine the RX CCA threshold based on one or more bits included in a signal (SIG) field associated with the first message or based on a management message received from the first receiver.
- the reuse transmitter may determine the RX CCA threshold based on a block acknowledgement (BA) transmitted by the first receiver, such as a BA that is responsive to a particular message transmitted prior to the first message.
- BA block acknowledgement
- the reuse transmitter may determine the RX CCA threshold based on a request to send (RTS) message or a clear to send (CTS) message transmitted from the first receiver.
- RTS request to send
- CTS clear to send
- the RTS message or the CTS message may be associated with a particular message that was transmitted prior to the first message.
- the method 1900 may enable the reuse transmitter to determine whether to reuse the first TXOP based on an RX CCA threshold determined by the first receiver.
- FIG. 20 a particular embodiment of a method of operating a reuse transmitter is described and designated 2000.
- the method 2000 may be performed using the reuse transmitter 140 of FIG. 1, one of the access points 1012, 1022, or one of the stations 1014, 1016, 1024, 1026 of FIG. 10.
- the method 2000 may include detecting a portion of a message sent by a first transmitter, where the portion does not include an indication of whether reuse of a first transmit opportunity (TXOP) associated with the message is permitted, at 2002.
- the method 2000 may further include determining whether to reuse the first TXOP associated with the message, at 2004.
- the method 2000 may enable the reuse transmitter to determine whether to reuse the first TXOP.
- FIG. 21 a block diagram of a particular illustrative embodiment of a wireless communication device is depicted and generally designated 2100.
- the device 2100 includes a processor 2110, such as a digital signal processor, coupled to a memory 2132.
- the device 2100, or components thereof may correspond to the first transmitter 1 10, the first receiver 130, the reuse transmitter 140, or the reuse receiver 160 of FIG. 1, or components thereof.
- the processor 21 10 may be configured to execute software (e.g., a program of one or more instructions 2168) stored in the memory 2132. Additionally or alternatively, the processor 21 10 may be configured to implement one or more instructions stored in a memory of a wireless interface 2140 (e.g., an IEEE 802.1 1 wireless interface). In a particular embodiment, the processor 21 10 may be configured to operate in accordance with one or more of the methods of FIGS. 1 1-20. For example, the processor 2110 may include TXOP reuse logic 2164 to execute one or more of the methods of FIGS. 1 1-20. The processor 21 10 may also be configured to determine and store historical data 2170 associated with devices or data transmissions associated with one or more networks, such as one or more wireless networks. In an illustrative embodiment, the historical data 2170 includes data associated with TXOP reuse.
- the wireless interface 2140 may be coupled to the processor 21 10 and to an antenna 2142.
- the wireless interface 2140 may be coupled to the antenna 2142 via a transceiver 2146, such that wireless data received via the antenna 2142 and may be provided to the processor 21 10.
- a coder/decoder (CODEC) 2134 can also be coupled to the processor 21 10.
- a speaker 2136 and a microphone 2138 can be coupled to the CODEC 2134.
- a display controller 2126 can be coupled to the processor 2110 and to a display device 2128.
- the processor 2110, the display controller 2126, the memory 2132, the CODEC 2134, and the wireless interface 2140 are included in a system- in- package or system-on-chip device 2122.
- an input device 2130 and a power supply 2144 are coupled to the system-on-chip device 2122.
- the display device 2128, the input device 2130, the speaker 2136, the microphone 2138, the antenna 2142, and the power supply 2144 are external to the system-on-chip device 2122.
- each of the display device 2128, the input device 2130, the speaker 2136, the microphone 2138, the antenna 2142, and the power supply 2144 can be coupled to one or more components of the system-on-chip device 2122, such as one or more interfaces or controllers.
- a first apparatus includes means for determining whether to permit reuse of a first transmit opportunity (TXOP).
- TXOP transmit opportunity
- the means for determining may include the first transmitter 1 10 of FIG. 1, the access points 1012, 1022, the stations 1014, 1016, 1024, 1026 of FIG. 10, the wireless interface 2140, the processor 2110 programmed to execute the instructions 2168, the TXOP reuse logic 2164 of FIG. 21, one or more other devices, circuits, modules, or instructions to determine whether to permit reuse of the first TXOP, or any combination thereof.
- the first apparatus also includes means for sending a message associated with the first TXOP, where the message indicates whether reuse, by a reuse transmitter, of the first TXOP is permitted.
- the means for sending may include the first transmitter 1 10 of FIG. 1, the access points 1012, 1022, the stations 1014, 1016, 1024, 1026 of FIG. 10, the wireless interface 2140, the transceiver 2146, the processor 2110 programmed to execute the instructions 2168, the TXOP reuse logic 2164 of FIG. 21, one or more other devices, circuits, modules, or instructions to send the message, or any combination thereof.
- a second apparatus includes means for detecting a portion of a message sent by a first transmitter.
- the means for detecting may include the reuse transmitter 140 of FIG. 1, the access points 1012, 1022, the stations 1014, 1016, 1024, 1026 of FIG. 10, the wireless interface 2140, the transceiver 2146, the processor 2110 programmed to execute the instructions 2168, the TXOP reuse logic 2164 of FIG. 21, one or more other devices, circuits, modules, or instructions to detect the portion, or any combination thereof.
- the second apparatus also includes means for determining, based on the portion, whether reuse of a first transmit opportunity (TXOP) associated with the message is permitted.
- TXOP transmit opportunity
- the means for determining may include the reuse transmitter 140 of FIG. 1, the access points 1012, 1022, the stations 1014, 1016, 1024, 1026 of FIG. 10, the wireless interface 2140, the processor 2110 programmed to execute the instructions 2168, the TXOP reuse logic 2164 of FIG. 21, one or more other devices, circuits, modules, or instructions to determine whether reuse of the first TXOP is permitted, or any combination thereof.
- a third apparatus includes means for determining a clear channel access (CCA) threshold associated with reuse of a first transmit opportunity (TXOP).
- the means for determining may include the first transmitter 1 10 of FIG. 1, the access points 1012, 1022, the stations 1014, 1016, 1024, 1026 of FIG. 10, the wireless interface 2140, the processor 21 10 programmed to execute the instructions 2168, the TXOP reuse logic 2164 of FIG. 21, one or more other devices, circuits, modules, or instructions to determine the CCA threshold, or any combination thereof.
- the third apparatus also includes means for sending at least a portion of a message associated with the first TXOP, where the portion indicates the CCA threshold associated with reuse of the first TXOP.
- the means for sending may include the first transmitter 1 10 of FIG. 1, the access points 1012, 1022, the stations 1014, 1016, 1024, 1026 of FIG. 10, the wireless interface 2140, the transceiver 2146, the processor 2110 programmed to execute the instructions 2168, the TXOP reuse logic 2164 of FIG. 21, one or more other devices, circuits, modules, or instructions to send the portion, or any combination thereof.
- a fourth apparatus includes means for detecting a portion of a message sent by a first transmitter, where the message is associated with a first transmit opportunity (TXOP).
- the means for detecting may include the reuse transmitter 140 of FIG. 1, the access points 1012, 1022, the stations 1014, 1016, 1024, 1026 of FIG. 10, the wireless interface 2140, the transceiver 2146, the processor 21 10 programmed to execute the instructions 2168, the TXOP reuse logic 2164 of FIG. 21, one or more other devices, circuits, modules, or instructions to detect the portion, or any combination thereof.
- the fourth apparatus also includes means for determining, based on the portion, a clear channel access (CCA) threshold associated with reuse of the first TXOP.
- the means for determining may include the reuse transmitter 140 of FIG. 1, the access points 1012, 1022, the stations 1014, 1016, 1024, 1026 of FIG. 10, the wireless interface 2140, the processor 21 10 programmed to execute the instructions 2168, the TXOP reuse logic 2164 of FIG. 21, one or more other devices, circuits, modules, or instructions to determine the CCA threshold, or any combination thereof.
- a fifth apparatus includes means for sending, to a first receiver, a request to send (RTS) message associated with a first transmit opportunity (TXOP), where the RTS message request the first receiver to indicate whether reuse of the first TXOP is permitted.
- the means for sending may include the first transmitter 110 of FIG. 1, the access points 1012, 1022, the stations 1014, 1016, 1024, 1026 of FIG. 10, the wireless interface 2140, the transceiver 2146, the processor 21 10 programmed to execute the instructions 2168, the TXOP reuse logic 2164 of FIG. 21, one or more other devices, circuits, modules, or instructions to send the RTS message, or any combination thereof.
- the fifth apparatus also includes means for receiving, from the first receiver, a clear to send (CTS) message responsive to the RTS message.
- the means for receiving may include the first transmitter 110 of FIG. 1, the access points 1012, 1022, the stations 1014, 1016, 1024, 1026 of FIG. 10, the wireless interface 2140, the transceiver 2146, the processor 21 10 programmed to execute the instructions 2168, the TXOP reuse logic 2164 of FIG. 21, one or more other devices, circuits, modules, or instructions to receive the CTS message, or any combination thereof.
- a sixth apparatus includes means for receiving a request to send (RTS) message sent by a first transmitter.
- the means for receiving may include the first receiver 130 of FIG. 1, the access points 1012, 1022, the stations 1014, 1016, 1024, 1026 of FIG. 10, the wireless interface 2140, the transceiver 2146, the processor 21 10 programmed to execute the instructions 2168, the TXOP reuse logic 2164 of FIG. 21, one or more other devices, circuits, modules, or instructions to receive the RTS message, or any combination thereof.
- the sixth apparatus also includes means for means for sending, to the first transmitter, a clear to send (CTS) message associated with a first transmit opportunity (TXOP), where the CTS message indicates whether reuse of the first TXOP is permitted.
- the means for sending may include the first receiver 130 of FIG. 1, the access points 1012, 1022, the stations 1014, 1016, 1024, 1026 of FIG. 10, the wireless interface 2140, the transceiver 2146, the processor 21 10 programmed to execute the instructions 2168, the TXOP reuse logic 2164 of FIG. 21, one or more other devices, circuits, modules, or instructions to send the CTS message, or any combination thereof.
- a seventh apparatus includes means for detecting a portion of a message sent by a first receiver.
- the means for detecting may include the reuse transmitter 140 of FIG. 1, the access points 1012, 1022, the stations 1014, 1016, 1024, 1026 of FIG. 10, the wireless interface 2140, the transceiver 2146, the processor 2110 programmed to execute the instructions 2168, the TXOP reuse logic 2164 of FIG. 21, one or more other devices, circuits, modules, or instructions to detect the portion, or any combination thereof.
- the seventh apparatus also includes means for determining, based on the portion, a receiver (RX) clear channel access (CCA) threshold associated with reuse of a first transmit opportunity (TXOP).
- the means for determining may include the reuse transmitter 140 of FIG. 1, the access points 1012, 1022, the stations 1014, 1016, 1024, 1026 of FIG. 10, the wireless interface 2140, the processor 21 10 programmed to execute the instructions 2168, the TXOP reuse logic 2164 of FIG. 21, one or more other devices, circuits, modules, or instructions to determine the RX CCA threshold, or any combination thereof.
- an eighth apparatus includes means for determining whether reuse of a first transmit opportunity (TXOP) associated with a first message is permitted, where the first message is transmitted from a first transmitter to a first receiver.
- TXOP transmit opportunity
- the means for determining whether reuse of the first TXOP is permitted may include the reuse transmitter 140 of FIG. 1, the access points 1012, 1022, the stations 1014, 1016, 1024, 1026 of FIG. 10, the wireless interface 2140, the processor 2110 programmed to execute the instructions 2168, the TXOP reuse logic 2164 of FIG. 21, one or more other devices, circuits, modules, or instructions to determine whether reuse of the first TXOP is permitted, or any combination thereof.
- the eighth apparatus also includes means for determining whether to reuse the first TXOP based on an interference level of a reuse transmitter at the first receiver.
- the means for determining whether to reuse the first TXOP may include the reuse transmitter 140 of FIG. 1, the access points 1012, 1022, the stations 1014, 1016, 1024, 1026 of FIG. 10, the wireless interface 2140, the processor 2110 programmed to execute the instructions 2168, the TXOP reuse logic 2164 of FIG. 21, one or more other devices, circuits, modules, or instructions to determine whether to reuse the first TXOP, or any combination thereof.
- a ninth apparatus includes means for determining whether reuse of a first transmit opportunity (TXOP) associated with a first message is permitted, where the first message is transmitted from a first transmitter to a first receiver.
- TXOP transmit opportunity
- the means for determining whether reuse of the first TXOP is permitted may include the reuse transmitter 140 of FIG. 1, the access points 1012, 1022, the stations 1014, 1016, 1024, 1026 of FIG. 10, the wireless interface 2140, the processor 2110 programmed to execute the instructions 2168, the TXOP reuse logic 2164 of FIG. 21, one or more other devices, circuits, modules, or instructions to determine whether reuse of the first TXOP is permitted, or any combination thereof.
- the ninth apparatus also includes means for determining whether to reuse the first TXOP based on a receiver (RX) clear channel access (CCA) threshold associated with the first receiver.
- the means for determining whether to reuse the first TXOP may include the reuse transmitter 140 of FIG. 1, the access points 1012, 1022, the stations 1014, 1016, 1024, 1026 of FIG. 10, the wireless interface 2140, the processor 2110 programmed to execute the instructions 2168, the TXOP reuse logic 2164 of FIG. 21, one or more other devices, circuits, modules, or instructions to determine whether to reuse the first TXOP, or any combination thereof.
- FIGS. 1-21 may illustrate systems, apparatuses, and/or methods according to the teachings of the disclosure, the disclosure is not limited to these illustrated systems, apparatuses, and/or methods.
- One or more functions or components of any of FIGS. 1-21 as illustrated or described herein may be combined with one or more other portions of another of FIGS. 1-21. Accordingly, no single embodiment described herein should be construed as limiting and embodiments of the disclosure may be suitably combined without departing form the teachings of the disclosure.
- a software module may reside in random access memory (RAM), flash memory, read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), registers, hard disk, a removable disk, a compact disc read-only memory (CD-ROM), or any other form of non-transient (e.g., non-transitory) storage medium known in the art.
- RAM random access memory
- ROM read-only memory
- PROM programmable read-only memory
- EPROM erasable programmable read-only memory
- EEPROM electrically erasable programmable read-only memory
- registers hard disk, a removable disk, a compact disc read-only memory (CD-ROM), or any other form of non-transient (e.g., non-transitory) storage medium known in the art.
- An exemplary storage medium is coupled to the processor such that the processor can read information from, and write information to, the storage medium.
- the storage medium may be integral to the processor.
- the processor and the storage medium may reside in an application-specific integrated circuit (ASIC).
- the ASIC may reside in a computing device or a user terminal.
- the processor and the storage medium may reside as discrete components in a computing device or user terminal.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Applications Claiming Priority (7)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US201361827480P | 2013-05-24 | 2013-05-24 | |
US201361843315P | 2013-07-05 | 2013-07-05 | |
US201361869546P | 2013-08-23 | 2013-08-23 | |
US201461926205P | 2014-01-10 | 2014-01-10 | |
US201461936872P | 2014-02-07 | 2014-02-07 | |
US14/268,855 US9622262B2 (en) | 2013-05-03 | 2014-05-02 | Transmit opportunity (TXOP) based channel reuse |
PCT/US2014/039384 WO2014190284A1 (en) | 2013-05-24 | 2014-05-23 | Transmit opportunity (txop) based channel reuse |
Publications (1)
Publication Number | Publication Date |
---|---|
EP3005816A1 true EP3005816A1 (en) | 2016-04-13 |
Family
ID=51934218
Family Applications (3)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP14733817.2A Withdrawn EP3005816A1 (en) | 2013-05-24 | 2014-05-23 | Transmit opportunity (txop) based channel reuse |
EP14735729.7A Active EP3005820B1 (en) | 2013-05-24 | 2014-05-23 | Transmit opportunity (txop) based channel reuse |
EP14734988.0A Active EP3005818B1 (en) | 2013-05-24 | 2014-05-23 | Transmit opportunity (txop) based channel reuse |
Family Applications After (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP14735729.7A Active EP3005820B1 (en) | 2013-05-24 | 2014-05-23 | Transmit opportunity (txop) based channel reuse |
EP14734988.0A Active EP3005818B1 (en) | 2013-05-24 | 2014-05-23 | Transmit opportunity (txop) based channel reuse |
Country Status (9)
Country | Link |
---|---|
EP (3) | EP3005816A1 (ja) |
JP (3) | JP6479773B2 (ja) |
KR (3) | KR101812153B1 (ja) |
CN (3) | CN105325048B (ja) |
DK (1) | DK3005818T3 (ja) |
ES (2) | ES2750605T3 (ja) |
HU (2) | HUE042080T2 (ja) |
SI (1) | SI3005818T1 (ja) |
WO (3) | WO2014190275A1 (ja) |
Families Citing this family (28)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9706534B2 (en) * | 2014-12-03 | 2017-07-11 | Intel IP Corporation | Apparatus, method, and computer readable media for uplink transmission opportunity in a high-efficiency wireless local-area network |
US20160374009A1 (en) * | 2015-02-17 | 2016-12-22 | Telefonaktiebolaget L M Ericsson (Publ) | Operation of a Communication Unit in a Wireless Local Area Network, WLAN, Environment |
EP3264834B1 (en) * | 2015-02-26 | 2020-04-01 | Sharp Kabushiki Kaisha | Terminal device, base station device, communication method, and communication system |
EP3294032B1 (en) | 2015-05-07 | 2021-03-10 | Kabushiki Kaisha Toshiba, Inc. | Wireless communication terminal and wireless communication method |
KR102328669B1 (ko) * | 2015-05-07 | 2021-11-19 | 삼성전자주식회사 | 비인가 대역을 지원하는 무선 통신 시스템에서 신호 송/수신 장치 및 방법 |
JP6568584B2 (ja) | 2015-05-07 | 2019-08-28 | 株式会社東芝 | 無線通信装置、無線通信端末および無線通信方法 |
CN106304375B (zh) * | 2015-05-28 | 2019-12-13 | 上海诺基亚贝尔股份有限公司 | 一种无线通信方法 |
US20160360397A1 (en) * | 2015-06-02 | 2016-12-08 | Qualcomm Incorporated | Color coding for data confirmation signals |
WO2017012182A1 (zh) * | 2015-07-17 | 2017-01-26 | 华为技术有限公司 | 无线通信系统中nav设置方法及相关设备 |
WO2017026824A1 (ko) * | 2015-08-12 | 2017-02-16 | 엘지전자 주식회사 | 무선랜 시스템에서 nav 동작 방법 및 이를 위한 스테이션 장치 |
US10117106B2 (en) * | 2015-08-20 | 2018-10-30 | Qualcomm Incorporated | Backoff mechanism techniques for spatial reuse |
JP6441486B2 (ja) * | 2015-08-21 | 2018-12-19 | 日本電信電話株式会社 | 無線通信システムおよび無線通信方法 |
WO2017034446A1 (en) * | 2015-08-25 | 2017-03-02 | Telefonaktiebolaget Lm Ericsson (Publ) | Wlan nodes, and methods therein for efficient usage of wlan resources |
CN112491521B (zh) | 2015-10-20 | 2022-08-19 | 华为技术有限公司 | 传输数据的方法和装置 |
CN106656428B (zh) * | 2015-10-28 | 2020-05-22 | 中兴通讯股份有限公司 | 竞争窗调整方法和装置 |
JP2017123585A (ja) * | 2016-01-08 | 2017-07-13 | ソニー株式会社 | 情報処理装置、通信システム、情報処理方法およびプログラム |
CN106961733B (zh) * | 2016-01-11 | 2020-11-10 | 华为技术有限公司 | 传输数据的方法和装置 |
WO2017162005A1 (zh) * | 2016-03-22 | 2017-09-28 | 中兴通讯股份有限公司 | 功率参数调整方法及装置、计算机存储介质 |
CN108886696A (zh) * | 2016-04-01 | 2018-11-23 | 华为技术有限公司 | 一种发送信号、接收信号的方法及装置 |
CN105813094B (zh) * | 2016-04-08 | 2019-03-08 | 西安电子科技大学 | 无线局域网中txop机制冗余nav的截短方法 |
US10952095B2 (en) * | 2016-12-07 | 2021-03-16 | Sony Corporation | Communication device, communication method, and program |
JP2018098604A (ja) * | 2016-12-12 | 2018-06-21 | 国立研究開発法人情報通信研究機構 | 無線通信システム及び方法 |
WO2018117723A1 (ko) * | 2016-12-22 | 2018-06-28 | 엘지전자 주식회사 | 무선랜 시스템에서 공간 재사용을 기반으로 프레임을 송신하는 방법 및 이를 이용한 무선 단말 |
US10123358B2 (en) * | 2016-12-22 | 2018-11-06 | Qualcomm Incorporated | Priority management for new radio-spectrum sharing (NR-SS) |
EP3590297B1 (en) | 2017-03-01 | 2023-06-28 | Apple Inc. | Txop with continued lbt after a pause |
CN108738153B (zh) * | 2017-04-17 | 2023-11-10 | 华为技术有限公司 | 一种通信方法及发射端设备 |
US20240284491A1 (en) * | 2021-05-25 | 2024-08-22 | Electronics And Telecommunications Research Institute | Method and device for direct communication in wireless lan |
WO2023209604A1 (en) * | 2022-04-26 | 2023-11-02 | Lenovo (Singapore) Pte Limited | Sidelink request/grant protocol for wireless networks |
Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20130017794A1 (en) * | 2011-07-15 | 2013-01-17 | Cisco Technology, Inc. | Mitigating Effects of Identified Interference with Adaptive CCA Threshold |
Family Cites Families (32)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP3774469B2 (ja) * | 2001-09-28 | 2006-05-17 | 株式会社東芝 | 無線通信装置及びフレーム送信方法 |
US7639658B2 (en) * | 2005-03-18 | 2009-12-29 | Qualcomm Incorporated | Efficient wireless transmission opportunity handoff |
WO2006120651A2 (en) | 2005-05-12 | 2006-11-16 | Koninklijke Philips Electronics N.V. | Distributed medium access protocol for wireless mesh networks |
CN101248687A (zh) * | 2005-06-08 | 2008-08-20 | 阿瓦雅技术公司 | 在无线局域网中避免暴露节点问题 |
US20070060155A1 (en) * | 2005-08-31 | 2007-03-15 | Emanuel Kahana | System and method to dynamically adapt a CCA threshold |
US8681810B2 (en) * | 2006-04-13 | 2014-03-25 | Qualcomm Incorporated | Dynamic carrier sensing thresholds |
KR101312903B1 (ko) * | 2006-04-24 | 2013-09-30 | 인터디지탈 테크날러지 코포레이션 | 무선 메시 네트워크에서의 송신 기회 이용을 위한 방법 및 시그널링 프로시저 |
US7720440B2 (en) | 2006-05-18 | 2010-05-18 | Intel Corporation | Distributed coordination of a clear channel assessment (CCA) threshold |
KR100874002B1 (ko) * | 2006-06-14 | 2008-12-17 | 한국전자통신연구원 | 이동통신 시스템에서 상향링크 동기화 요청 방법, 그에따른 cdma 할당 정보 요소 구조 및 그에 따른 장치 |
US8305948B2 (en) * | 2006-11-15 | 2012-11-06 | Qualcomm Incorporated | Transmissions to multiple stations in wireless communication systems |
JP5173526B2 (ja) * | 2008-03-28 | 2013-04-03 | 株式会社東芝 | 無線システム、無線基地局および無線端末 |
US20090252116A1 (en) * | 2008-04-04 | 2009-10-08 | Nokia Siemens Networks Gmbh & Co. Kg | Multiple Action Times in Mobile WiMAX Fast Handover |
US8743793B2 (en) * | 2008-07-14 | 2014-06-03 | Qualcomm Incorporated | Systems and methods for providing a separate contention window allowing allocations for pending uplink SDMA transmission opportunities |
CN101656644A (zh) * | 2008-08-18 | 2010-02-24 | 清华大学 | 接入点装置、移动终端、无线通信系统及其控制方法 |
CN101657017B (zh) * | 2008-09-22 | 2012-09-05 | 华为技术有限公司 | 一种资源调度方法、基站以及通信系统 |
DE102009018393B4 (de) * | 2009-04-22 | 2017-05-24 | Atotech Deutschland Gmbh | Verfahren, Haltemittel, Vorrichtung und System zum Transportieren eines flächigen Behandlungsgutes und Be- oder Entladeeinrichtung |
US8498275B2 (en) * | 2009-10-30 | 2013-07-30 | Qualcomm Incorporated | Deterministic backoff with dynamic adaptation |
EP2506450A4 (en) * | 2009-11-24 | 2012-11-07 | Korea Electronics Telecomm | METHODS OF TRANSMITTING A FRAME IN A WIRELESS COMMUNICATION SYSTEM ON A MULTI-USER BASIS |
JP5709323B2 (ja) * | 2010-02-10 | 2015-04-30 | マーベル ワールド トレード リミテッド | 無線通信の送信保護 |
US9357565B2 (en) * | 2010-03-09 | 2016-05-31 | Qualcomm Incorporated | Multi-user uplink communication using EDCA with polling |
US8355389B2 (en) * | 2010-03-12 | 2013-01-15 | Nokia Corporation | Simultaneous transmissions during a transmission opportunity |
US8787385B2 (en) * | 2010-06-11 | 2014-07-22 | Marvell World Trade Ltd. | Method and apparatus for determining channel bandwidth |
US20120142268A1 (en) * | 2010-12-06 | 2012-06-07 | Industrial Technology Research Institute | Signal transmission method,base station and wireless communication device |
JP5269925B2 (ja) * | 2011-01-31 | 2013-08-21 | 株式会社東芝 | 無線通信装置及び無線通信方法 |
US20120207074A1 (en) * | 2011-02-10 | 2012-08-16 | Nokia Corporation | Transmitting multiple group-addressed frames in a wireless network |
US8767570B2 (en) * | 2011-02-14 | 2014-07-01 | Nokia Corporation | Indicating status of radio resources in wireless network |
EP2732669B1 (en) * | 2011-07-15 | 2015-09-09 | Marvell World Trade Ltd. | Coexistence of a normal-rate physical layer and a low-rate physical layer in a wireless network |
US20130036013A1 (en) * | 2011-08-05 | 2013-02-07 | ChannelAdvisor Corporation | Methods and apparatus for dynamically providing advertisements |
US8842692B2 (en) * | 2011-09-06 | 2014-09-23 | Qualcomm Incorporated | Methods and apparatus for enabling multiple devices to share a data transmission period |
CN103002591B (zh) * | 2011-09-15 | 2015-09-30 | 华为技术有限公司 | 一种对节点进行nav控制的方法、装置、系统及节点 |
JP5899545B2 (ja) * | 2012-02-24 | 2016-04-06 | 株式会社国際電気通信基礎技術研究所 | 通信装置、通信方法、及びプログラム |
US9125214B2 (en) | 2012-09-04 | 2015-09-01 | Cisco Technology, Inc. | Dynamic enabling of wider channel transmissions with radio monitoring |
-
2014
- 2014-05-23 SI SI201431154T patent/SI3005818T1/sl unknown
- 2014-05-23 EP EP14733817.2A patent/EP3005816A1/en not_active Withdrawn
- 2014-05-23 KR KR1020157036336A patent/KR101812153B1/ko active IP Right Grant
- 2014-05-23 CN CN201480029501.0A patent/CN105325048B/zh active Active
- 2014-05-23 KR KR1020157036338A patent/KR102161170B1/ko active IP Right Grant
- 2014-05-23 DK DK14734988.0T patent/DK3005818T3/da active
- 2014-05-23 WO PCT/US2014/039370 patent/WO2014190275A1/en active Application Filing
- 2014-05-23 KR KR1020157036330A patent/KR101686579B1/ko active IP Right Grant
- 2014-05-23 JP JP2016515124A patent/JP6479773B2/ja active Active
- 2014-05-23 HU HUE14734988A patent/HUE042080T2/hu unknown
- 2014-05-23 ES ES14735729T patent/ES2750605T3/es active Active
- 2014-05-23 HU HUE14735729A patent/HUE045345T2/hu unknown
- 2014-05-23 JP JP2016515117A patent/JP6162328B2/ja active Active
- 2014-05-23 EP EP14735729.7A patent/EP3005820B1/en active Active
- 2014-05-23 EP EP14734988.0A patent/EP3005818B1/en active Active
- 2014-05-23 WO PCT/US2014/039395 patent/WO2014190290A1/en active Application Filing
- 2014-05-23 ES ES14734988T patent/ES2726829T3/es active Active
- 2014-05-23 JP JP2016515121A patent/JP6400681B2/ja active Active
- 2014-05-23 WO PCT/US2014/039384 patent/WO2014190284A1/en active Application Filing
- 2014-05-23 CN CN201480029486.XA patent/CN105393629B/zh active Active
- 2014-05-23 CN CN201480029424.9A patent/CN105230110A/zh active Pending
Patent Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20130017794A1 (en) * | 2011-07-15 | 2013-01-17 | Cisco Technology, Inc. | Mitigating Effects of Identified Interference with Adaptive CCA Threshold |
Non-Patent Citations (1)
Title |
---|
See also references of WO2014190284A1 * |
Also Published As
Publication number | Publication date |
---|---|
JP2016519550A (ja) | 2016-06-30 |
KR102161170B1 (ko) | 2020-09-29 |
CN105393629A (zh) | 2016-03-09 |
KR101812153B1 (ko) | 2017-12-26 |
KR101686579B1 (ko) | 2016-12-14 |
JP6479773B2 (ja) | 2019-03-06 |
KR20160013962A (ko) | 2016-02-05 |
EP3005818B1 (en) | 2019-02-20 |
EP3005820B1 (en) | 2019-07-17 |
ES2750605T3 (es) | 2020-03-26 |
KR20160013961A (ko) | 2016-02-05 |
CN105325048B (zh) | 2021-10-08 |
JP6162328B2 (ja) | 2017-07-12 |
CN105230110A (zh) | 2016-01-06 |
HUE045345T2 (hu) | 2019-12-30 |
EP3005820A1 (en) | 2016-04-13 |
CN105325048A (zh) | 2016-02-10 |
KR20160013960A (ko) | 2016-02-05 |
CN105393629B (zh) | 2019-07-16 |
WO2014190290A1 (en) | 2014-11-27 |
HUE042080T2 (hu) | 2019-06-28 |
JP6400681B2 (ja) | 2018-10-03 |
ES2726829T3 (es) | 2019-10-09 |
SI3005818T1 (sl) | 2019-05-31 |
JP2016519549A (ja) | 2016-06-30 |
WO2014190275A1 (en) | 2014-11-27 |
EP3005818A1 (en) | 2016-04-13 |
WO2014190284A1 (en) | 2014-11-27 |
DK3005818T3 (da) | 2019-05-13 |
JP2016519548A (ja) | 2016-06-30 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US9408230B2 (en) | Transmit opportunity (TXOP) based channel reuse | |
EP3005820B1 (en) | Transmit opportunity (txop) based channel reuse | |
US11997712B2 (en) | Techniques of improving EDCA mechanism in spatial reuse | |
US9749967B2 (en) | Spatial reuse parameters for opportunistic adaptive TPC and CCA | |
EP3358776B1 (en) | Method and device for transmitting data | |
US9622189B2 (en) | Techniques for fast delivery of radio information | |
US10375731B2 (en) | Dynamic forbiddance of wireless transmissions by overlapping basic service sets | |
TW201541915A (zh) | 用於wi-fi裝置之虛擬空閒頻道評估機制 | |
EP3427532B1 (en) | Methods for reducing interference in a wireless communications network | |
US20170064695A1 (en) | Transmission parameter control for immediate response frames | |
WO2020178302A1 (en) | Controlling downlink spatial reuse in wlan through rts/cts |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PUAI | Public reference made under article 153(3) epc to a published international application that has entered the european phase |
Free format text: ORIGINAL CODE: 0009012 |
|
17P | Request for examination filed |
Effective date: 20151109 |
|
AK | Designated contracting states |
Kind code of ref document: A1 Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR |
|
AX | Request for extension of the european patent |
Extension state: BA ME |
|
DAX | Request for extension of the european patent (deleted) | ||
17Q | First examination report despatched |
Effective date: 20180621 |
|
GRAP | Despatch of communication of intention to grant a patent |
Free format text: ORIGINAL CODE: EPIDOSNIGR1 |
|
INTG | Intention to grant announced |
Effective date: 20190404 |
|
RIN1 | Information on inventor provided before grant (corrected) |
Inventor name: YONGE, LAWRENCE WINSTON III Inventor name: BARRIAC, GWENDOLYN DENISE Inventor name: ZHU, HAO Inventor name: CHERIAN, GEORGE Inventor name: MERLIN, SIMONE Inventor name: ZOU, CHAO Inventor name: KATAR, SRINIVAS Inventor name: ABRAHAM, SANTOSH PAUL Inventor name: SAMPATH, HEMANTH |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: THE APPLICATION IS DEEMED TO BE WITHDRAWN |
|
18D | Application deemed to be withdrawn |
Effective date: 20190815 |