AND METHODS FOR ACKNOWLEDGEMENTS DURING

SCHEDULED TRANSMISSION OPPORTUNITIES

PRIORITY CLAIM [0001] This patent application claims the benefit of priority to U.S.

Application Serial No. 14/563,406, filed December 8, 2014, which claims the benefit of priority to U.S. Provisional Patent Application Serial No. 62/024,813, entitled "ACKNOWLEDGEMENT IN 802.11," filed July 15, 2014, all of which are incorporated herein by reference in their entirety.

TECHNICAL FIELD

[0002] Some embodiments described herein generally relate to acknowledgement policies in wireless local-area networks (WLANs), some embodiments generally relate to acknowledgement policies for high-efficiency wireless communications including high-efficiency WLAN and high-efficiency wireless (HEW) communications, and some embodiments relate to

acknowledgement policies in 802.1 lax.

BACKGROUND

[0003] One issue with communicating data over a wireless network is acknowledging received packets. Often acknowledging received packets consumes bandwidth.

[0004] Thus, there are general needs for systems and methods that reduce signaling, bandwidth and/or delay associated with communicating acknowledgments of packets. BRIEF DESCRIPTION OF THE DRAWINGS

[0005] The present disclosure is illustrated by way of example and not limitation in the figures of the accompanying drawings, in which like references indicate similar elements and in which:

[0006] FIG. 1 illustrates a wireless network in accordance with some embodiments;

[0007] FIG. 2 is a method of acknowledgment in 802.11 in accordance with example embodiments;

[0008] FIG. 3 is a method of acknowledgment in 802.11 in accordance with example embodiments;

[0009] FIG. 4 is a method of acknowledgment in 802.11 in accordance with example embodiments;

[0010] FIG. 5 illustrates a schematic diagram of a packet, according to example embodiments; and

[0011] FIG. 6 illustrates a HEW device in accordance with some embodiments.

DETAILED DESCRIPTION

[0012] The following description and the drawings sufficiently illustrate specific embodiments to enable those skilled in the art to practice them. Other embodiments may incorporate structural, logical, electrical, process, and other changes. Portions and features of some embodiments may be included in, or substituted for, those of other embodiments. Embodiments set forth in the claims encompass all available equivalents of those claims.

[0013] FIG. 1 illustrates a wireless network in accordance with some embodiments. The wireless network may comprise a basis service set (BSS) 100 that may include an access point (AP) 102, a plurality of HEW devices 104 and a plurality of legacy devices 106. [0014] The AP 102 may be an access point (AP) using the Institute of

Electrical and Electronics Engineers (IEEE) 802.11 to transmit and receive. In example embodiments, the AP 102 may be a base station. The AP 102 may use other communications protocols as well as the 802.11 protocol. For example the AP 102 may use 802.16 or 802.15.1. The 802.11 protocol may be 802.11 ax.

The 802.11 protocol may include using Orthogonal Frequency-Division Multiple Access (OFDMA) and/or Space-Division Multiple Access (SDMA). The 802.11 may include using multi-user multiple-input and multiple-output (MU- MIMO). The HEW devices 104 may operate in accordance with 802.1 lax. The legacy devices 106 may operate in accordance with one or more of 802.11 a/g/ag/n/ac, or another legacy wireless communication standard. In example embodiments, the BSS 100 may include more than one AP 102.

[0015] The HEW devices 104 may be wireless transmit and receive devices such as cellular telephone, handheld wireless device, wireless glasses, wireless watch, wireless personal device, tablet, or another device that may be transmitting and receiving using the 802.11 protocol such as 802.1 lax or another wireless protocol.

[0016] The BSS 100 may operate on a primary channel and one or more secondary channels or sub-channels. The BSS 100 may include one or more APs 102. In accordance with embodiments, the AP 102 may communicate with one or more of the HEW devices 104 on one or more of the secondary channels or sub-channels or the primary channel. In example embodiments, the AP 102 communicates with the legacy devices 106 on the primary channel. In example embodiments, the AP 102 may be configured to communicate concurrently with one or more of the HEW devices 104 on one or more of the secondary channels and a legacy device 106 utilizing only the primary channel and not utilizing any of the secondary channels.

[0017] The AP 102 may communicate with legacy devices 106 in accordance with legacy IEEE 802.11 communication techniques. In example embodiments, the AP 102 may also be configured to communicate with HEW devices 104 in accordance with legacy IEEE 802.11 communication techniques. Legacy IEEE 802.11 communication techniques may refer to any IEEE 802.11 communication technique prior to IEEE 802.1 lax. [0018] In some embodiments, HEW frames may be configurable to have the same bandwidth or different bandwidths, and the bandwidth may be one of 20MHz, 40MHz, or 80MHz contiguous bandwidths or an 80+80MHz (160MHz) non-contiguous bandwidth, or another bandwidth. In some embodiments, a 320MHz contiguous bandwidth may be used. In some embodiments, bandwidths of 1 MHz, 1.25MHz, 2.5MHz, 5MHz, 10MHz, or another bandwidth, or a combination thereof may also be used. In these embodiments, a HEW frame may be configured for transmitting a number of spatial streams.

[0019] In other embodiments, the AP 102, HEW device 104, and/or legacy device 106 may implement one or more of different technologies such as code-division multiple-access (CDMA) 2000, CDMA2000 IX, CDMA2000 evolution data-optimized (EV-DO), Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Global System for Mobile communications (GSM), Enhanced Data rates for GSM Evolution (EDGE), GSM EDGE (GERAN), Long-Term Evolution (LTE), 802.15.1 , and IEEE 802.16 (i.e., Worldwide Interoperability for Microwave Access (WiMAX)).

[0020] In an OFDMA system such as 802.1 lax, an associated HEW device 104 may operate on different 20MHz sub-channel of the BSS 100. For example, the BSS 100 may operate on a 80MHz bandwidth with four subchannels of 20MHz each.

[0021] In example embodiments, an AP 102, HEW devices 104, and legacy devices 106 use carrier sense multiple access/collision avoidance (CSMA/CA). In some embodiments, the media access control (MAC) 606 layer (see FIG. 6) controls access to the wireless media.

[0022] In example embodiments, an AP 102, HEW devices 104, legacy devices 106, perform carrier sensing and can detect whether or not the channel is free. For example, an AP 102, HEW device 104, or legacy device 106 may use clear channel assessment (CCA) which may include a determination whether or not the channel is clear based on a Decibel-milliwatts (dBm) level of reception. In example embodiments, the physical layer (PHY) 604 (FIG. 6) is configured to determine a CCA for an AP 102, HEW devices 104, and legacy devices 106.

[0023] In example embodiments, an AP 102, HEW devices 104, legacy devices 106, access the channel in different ways. For example, in accordance with some IEEE 802.1 lax embodiments, an AP 102 may operate as a master station which may be arranged to contend for a wireless medium (e.g., during a contention period) to receive exclusive control of the medium for an HEW control period (i.e., a transmission opportunity (TXOP)). The AP 102 may transmit an HEW master-sync transmission at the beginning of the HEW control period. During the HEW control period, HEW devices 104 may communicate with the AP 102 in accordance with a non-contention based multiple access technique. This is unlike conventional 802.11 communications in which legacy devices 106 and, optionally, HEW devices 104 communicate in accordance with a contention-based communication technique, rather than a multiple access technique. During the HEW control period, the AP 102 may communicate with HEW devices 104 using one or more HEW frames. During the HEW control period, legacy devices 106 refrain from communicating. In some embodiments, the master-sync transmission may be referred to as an HEW control and schedule transmission.

[0024] In some embodiments, the multiple-access technique used during the HEW control period may be a scheduled OFDMA technique, although this is not a requirement. In some embodiments, the multiple access technique may be a time-division multiple access (TDMA) technique or a frequency division multiple access (FDMA) technique. In some embodiments, the multiple access technique may be a space-division multiple access (SDMA) technique.

[0025] The AP 102 may also communicate with legacy devices 106 in accordance with legacy IEEE 802.11 communication techniques. In some embodiments, the master station may also be configured to communicate with HEW stations outside the HEW control period in accordance with legacy IEEE 802.11 communication techniques, although this is not a requirement. HEW devices 104 may be termed HE (high-efficiency) devices. HEW devices 104 may be also / alternatively termed high-efficiency Wi-Fi® (HEW) devices.

[0026] In example embodiments, the HEW device 104 and AP 102 are configured to perform one or more of the functions and/or methods described herein for acknowledgements and block acknowledgements such as the methods, apparatuses, and functions described in conjunction with FIGS. 2 through 4, and in relation to packet 500. [0027] FIG. 2 is a method 200 of acknowledgment in 802.11 in accordance with example embodiments. Illustrated in FIG. 2 is time 266 along the horizontal axis and along the vertical axis are AP 102, HEW device 104.1, HEW device 104.2, and legacy device 106. In example embodiments, there may be one or more HEW devices 104.1, 104.2, one or more APs 102, and one or more legacy devices 106.

[0028] In example embodiments, the method 200 begins with the AP 102 transmitting during a contention period 201. The AP 102 contends for the wireless medium with other wireless devices: HEW device 104.1, HEW device 104.2, and legacy device 106. At the end of the contention period 201, the AP 102 has determined that the wireless medium may be free and determines to transmit. In each of the method operations, the AP 102 may transmit according to OFDMA, SDMA, and/or MU-MIMO.

[0029] The method 200 continues with the AP 102 transmitting the schedule (SCH) 202 to HEW device 104.1 , HEW device 104.2, and legacy device 106 as shown by arrows 250.1, 250.2, 270. In example embodiments, the SCH 202 may include a legacy header that the legacy device 106 can decode. In example embodiments, the SCH 202 includes an indication for how long the legacy device 106 should set a network allocation vector (NAV), which indicates how long not to try to access the wireless medium. In example embodiments, the legacy device 106 sets the NAV 271 based on a received legacy header from the AP 102. In example embodiments, the SCH 202 is an indication of a stream and time when a HEW device 104 is scheduled for uplink transmission. In example embodiments, the SCH 202 may be a separate packet. In example embodiments, the schedule (SCH) 202 is included in a SIG 204 packet, a management packet such as a beacon or any appropriate packet that is transmitted from the AP 102 to the HEW devices 104.1, 104.2. In example embodiments, the SCH 202 includes a schedule for two or more HEW devices 104.1, 104.2. In example embodiments, the SCH 202 includes a schedule for only one HEW device 104.1, 104.2. In some embodiments, the SCH 202 may indicate when the AP 102 is scheduled to transmit and receive. In example embodiments, the SCH 202 is configured according to one or more standards such as 802.1 lax. [0030] In example embodiments, the SCH 202 includes a schedule for both HEW device 104.1 and HEW device 104.2. In example embodiments, the AP 102 transmits simultaneously a separate SCH 202 to each HEW device 104.1, 104.2 as shown by arrows 250.1, 250.2. For example, the AP 102 may transmit on one sub-channel a first SCH (not illustrated), and simultaneously transmit on a second sub-channel a second SCH (not illustrated). In example embodiments, the AP 102 may transmit on one spatial stream a first SCH, and simultaneously transmit on a second sub-channel a second SCH. In example embodiments, the SIG 204 is part of a Physical Layer Convergence Procedure (PLCP) Packet Protocol Data Unit (PPDU). In example embodiments, the PPDU may be a multi-user (MU) PPDU.

[0031] In example embodiments, one or more of the SCH 202, SIG 204,

BA 206, DATA 208, a MAC field, or another frame may indicate a policy for acknowledgement such as a beacon frame or probe response frame. In example embodiments, the policy for acknowledgement may be per PPDU basis. In example embodiments, the policy for acknowledgement may indicate that the block acknowledgement (BA) 210, 214 is to be used in a next scheduled MU- PPDU. In example embodiments, the policy for acknowledgement may be pre- setup by the AP 102 and HEW devices 104.1, 104.2 exchanging a new MAC management frame. For example, an ACK setup management frame for MU transmission may be either unicast or multicast and may carry an

acknowledgement policy for multiple HEW devices 104 and/or APs 102.

[0032] The AP 102 may, in some example embodiments, announce a new acknowledgement policy in a beacon or probe. The acknowledgement policy may be for data and/or management frames. There may be more than one AP 102. There may be only one HEW device 104.1 , 104.2 or more than two, and there may be more than one legacy device 106.

[0033] The method 200 continues with the AP 102 transmitting a SIG

204 to the HEW devices 104.1, 104.2 as shown by arrows 250.3, 250.4. In example embodiments, the SIG 204 may be a signal field that includes information regarding the transmission such as a data rate or other information that may indicate information regarding the transmission and/or the AP 102. In example embodiments, the AP 102 transmits the same SIG 204 to the HEW devices 104.1, 104.2. In example embodiments, the AP 102 transmits different SIGs 204 to the HEW devices 104.1, 104.2.

[0034] In example embodiments, the AP 102 transmits the SIG 204 according to a standard such as 802.1 lax. In example embodiments, the SIG 204 is part of a management frame. In example embodiments, the SIG 204 is part of a Physical Layer Convergence Procedure (PLCP) Protocol Data Unit (PPDU). The PPDU may be a multi-user PPDU.

[0035] Optionally, in example embodiments, the method 200 continues with the AP 102 transmitting BA 206.1 and BA 206.2 to HEW device 104.1 and HEW device 104.2 as shown by arrows 250.5, 250.6, respectively. The AP 102 may transmit the BAs 206 simultaneously. The AP 102 may transmit the BAs 206 on different frequencies for MU or may transmit the BAs 206 using spatial diversity on the same frequency. In example embodiments, the BAs 206 are block acknowledgements (BA) that acknowledge previously transmitted data from the HEW devices 104.1, 104.2.

[0036] The method 200 continues with the AP 102 transmitting data

208.1, 208.2 as shown by arrows 250.7, 250.8, respectively. In example embodiments the AP 102 transmits (arrows 250.7, 250.8) the data 208.1 and data 208.2 simultaneously. The data 208.1 and data 208.2 may be data intended for HEW device 104.1 and HEW device 104.2, respectively.

[0037] The method 200 continues with HEW device 104.1 and HEW device 104.2 transmitting BA 210 and BA 214 as shown by arrows 252.1, 252.2, respectively. As illustrated, HEW device 104.1 may have received SCH 202, SIG 204, BA 206.1, and data 208.1, and HEW device 104.2 may have received SCH 202, SIG 204, BA 206.2, and data 208.2.

[0038] In example embodiments, BAs 210, 214 are block

acknowledgements of the data 208.1, 208.2, respectively. In example embodiments, the BAs 210, 214 are to be returned in the first scheduled multiuser Physical Layer Convergence Procedure (PLCP) Physical Data Unit (MU- PPDU) from HEW device 104.1 and HEW device 104.2, respectively. In example embodiments, if only one packet was transmitted by the AP 102, then an acknowledgment or block acknowledgment may be transmitted by the HEW devices 104. In example embodiments, an acknowledgment may refer to both an acknowledgment frame and block acknowledgment frame. In example embodiments, a previous packet from the AP 102 indicates that the data 208.1, 208.2 are to be block acknowledged as part of the next multi-user MU-PPDU from the HEW device 104.1 and HEW device 104.2, respectively. In some embodiments, an acknowledgement policy indicates that the block

acknowledgement may be part of a subsequent transmission such as the second MU-PPDU.

[0039] In some embodiments, the BA 210 and BA 214 are transmitted based on a schedule received from the AP 102. In example embodiments, the HEW devices 104.1, 104.2 do not wait as part of a contention period. In example embodiments, the HEW devices 104.1, 104.2 begin transmitting in accordance with a schedule.

[0040] Optionally, the method 200 continues with the HEW devices

104.1, 104.2 transmitting data 212, 216 as shown by arrows 252.3, 252.4, respectively. In some embodiments, the data 212, 216 are transmitted as part of a schedule during an up-link period for the HEW devices 104.1, 104.2 that may be OFDMA and/or MU-MIMO. In example embodiments, the data 212, 216 are transmitted simultaneously. The size of data 212, 216 may be different. In example embodiments, the BA 210 and BA 214 may be part of the data 212, 216 respectively. In example embodiments, the BAs 210, 214 and data 212, 216 may be reversed. In example embodiments, the HEW devices 104.1, 104.2 transmit additional packets such as a management packet such as a probe request or response.

[0041] A transmit opportunity (TXOP) 260 may end. The TXOP 260 may be a period set by the AP 102 in a MAC packet that indicates how long other wireless device such as legacy device 106 should defer accessing the wireless medium before attempting to transmit again. The TXOP 260 may include a duration for the HEW devices 104 to transmit an acknowledgment.

[0042] Optionally, the method 200 continues with the AP 102 transmitting during a contention period 217. The AP 102 contends for the wireless medium with other wireless devices: HEW device 104.1, HEW device

104.2, and legacy device 106. At the end of the contention period 217 the AP 102 has determined that the wireless medium may be free and determines to transmit. During the contention period 217 other wireless communication devices such as APs 102, HEW devices 104, and legacy devices 106 may have used the wireless medium.

[0043] Optionally, the method 200 continues with the AP 102 transmitting schedule (SCH) 218 to HEW device 104.1 and HEW device 104.2 as shown by arrows 254.1, 254.2, respectively. The TXOP 264 may be similar or the same as a TXOP 260 as described above. In example embodiments, the SCH 218 is a schedule as described for SCH 202. The legacy device 106 may set NAV 273 in a similar fashion as NAV 271 is set.

[0044] Optionally, the method 200 continues with the AP 102 transmitting a SIG 220 to the HEW devices 104.1, 104.2 as shown by arrows 254.3, 254.4. In example embodiments, the SIG 220 is a signal field as described for SIG 204.

[0045] Optionally, the method 200 continues with the AP 102 transmitting BAs 222.1 , 222.2 to HEW device 104.1 and HEW device 104.2 as shown by arrows 254.5, 254.6, respectively. In example embodiments the BAs 222.1, 222.2 are block acknowledges of the data 212, 216, respectively. In example embodiments, the BAs 222.1, 222.2 are transmitted after the data 224.

[0046] Optionally, the method 200 continues with the AP 102 transmitting data 224.1, 224.2 as shown by arrows 254.7, 254.8, respectively. In example embodiments, the data 224.1, 224.2 is data as described for data 208.

[0047] Optionally, the method 200 continues with the HEW devices

104.1, 104.2 transmitting BAs 226, 230 as shown by arrows 256.1, 256.2, respectively, to the AP 102. The BAs 226, 230 may be block acknowledgements as described for BAs 210, 214.

[0048] Optionally, the method 200 continues with the HEW devices

104.1, 104.2 transmitting data 228, 240 as shown by arrows 256.3, 256.4, respectively, to the AP 102. In example embodiments, the data 228, 240 may be data as described for data 212, 216. The method 200 may end.

[0049] FIG. 3 is a method 300 of acknowledgment in 802.11 in accordance with example embodiments. Illustrated in FIG. 3 is time 366 along the horizontal axis and along the vertical axis are AP 102, HEW device 104.1, HEW device 104.2, and legacy device 106. [0050] In example embodiments, the method 300 begins with the AP 102 transmitting during a contention period 301. The AP 102 contends for the wireless medium with other wireless devices such as HEW device 104.1, HEW device 104.2, and legacy device 106. At the end of the contention period 301, the AP 102 has determined that the wireless medium may be free and determines to transmit. In each of the method operations, the AP 102 may transmit according to OFDMA, SDMA, and/or MU-MIMO.

[0051] The method 300 continues with the AP 102 transmitting schedule

(SCH) 302 to HEW device 104.1, HEW device 104.2, and legacy device 106 as shown by arrows 350.1, 350.2, 370, respectively. The SCH 302 may be transmitted separately on different bandwidths or spatial streams and/or the SCH 302 may be transmitted on a primary channel so that the legacy device 106 will receive the SCH 302.

[0052] In example embodiments, the SCH 302 may be a schedule as described for SCH 202 (FIG. 2). The legacy device 106 may set a NAV 371 based on a legacy header that indicates how long the wireless medium will be used by the AP 102. The period of time the AP 102 has reserved may be called a TXOP 360.

[0053] The method 300 continues with the AP 102 transmitting SIG 304 to the HEW device 104.1 and HEW device 104.2 as shown by arrows 350.3, 350.4, respectively. The SIG 304 may be a signal as described for SIG 204 (FIG. 2).

[0054] The method 300 continues with the AP 102 transmitting management frames (MGMT) frames 308.1, 308.2 as shown by arrows 350.5, 350.6, respectively. The MGMT frames 308.1 , 308.2 may be management frames such as probe responses and probe requests. In example embodiments, the AP 102 may transmit additional packets either before or after the MGMT frames 308.1, 308.2.

[0055] The method 300 continues with HEW device 104.1 and HEW device 104.2 transmitting ACKs 310, 314 as shown by arrows 352.2, 352.1, respectively. In example embodiments, the HEW devices 104.1, 104.2 are configured to respond to acknowledge the MGMT frames 308.1, 308.2 in a scheduled MU PPDU. In example embodiments, the HEW devices 104.1, 104.2 are configured to respond to acknowledge the MGMT frames 308.1, 308.2 in a next scheduled MU PPDU. The method 300 may end.

[0056] FIG. 4 is a method 400 of acknowledgment in 802.11 in accordance with example embodiments. Illustrated in FIG. 4 is time 466 along the horizontal axis and along the vertical axis are AP 102, HEW device 104.1, HEW device 104.2, and legacy device 106.

[0057] The method 400 begins with HEW device 104.1 and HEW device

104.2 transmitting management (MGMT) frames 410, 414 as shown by arrows 452.2, 452.1, respectively. In example embodiments, the HEW devices 104.1, 104.2 may transmit the MGMT frames 410, 414 in a TXOP 460 in which the AP 102 may have reserved time for the HEW devices 104.1, 104.2 to transmit the MGMT frames 410, 414. In example embodiments, the HEW devices 104.1, 104.2 transmit packets before and/or after the MGMT frames 410, 414, respectively.

[0058] In example embodiments, the method 400 continues with the AP

102 transmitting during a contention period 401. The method 400 continues with the AP 102 transmitting (indicated by arrows 450.1, 450.2, 470) the SCH 402 to the HEW device 104.1, the HEW device 104.2, and the legacy device 106, respectively.

[0059] In example embodiments, the SCH 402 may be a schedule as described for SCH 202 (FIG. 2). The legacy device 106 may set a NAV 471 based on a legacy header that indicates how long the wireless medium will be used by the AP 102. The period of time the AP 102 has reserved may be called a TXOP 460.

[0060] The method 400 continues with the AP 102 transmitting SIG 404 to the HEW device 104.1 and the HEW device 104.2 as shown by arrows 450.3, 450.4, respectively. The SIG 404 may be a signal as described for SIG 204 (FIG. 2).

[0061] The method 400 continues with the AP 102 transmitting ACKs 408.1, 408.2 of the MGMT frames 410, 414 as shown by arrows 450.5, 450.6, respectively. In example embodiments, the AP 102 may transmit additional packets either before or after the ACKs 408.1, 408.2. In example embodiments, the AP 102 is configured to acknowledge the MGMT frames 410, 414 in a next scheduled PPDU. In example embodiments, the AP 102 is configured to acknowledge the MGMT frames 410, 414 in a next transmit opportunity of the AP 102. In example embodiments, the AP 102 is configured to acknowledge the MGMT frames 410, 414 before sending any data packets (not illustrated). The method 400 may end.

[0062] FIG. 5 illustrates a schematic diagram of a packet, according to example embodiments. Illustrated in FIG. 5 is a packet 500 and field 502. In example embodiments, the packet 500 may be a new MAC management frame for multi-user operation that indicates an ACK policy. In example

embodiments, the packet 500 may be an existing packet with a new or modified field 502. For example, the packet 500 may be a beacon frame, probe response, signal frame, probe request, or another frame suitable to include field 502.

[0063] The field 502 may indicate how the HEW devices 104 and/or AP

102 are to acknowledge or block acknowledge frames.

[0064] In example embodiments, the field 502 indicates that the HEW device 104 is to acknowledge or block acknowledge frames received in a next scheduled MU PPDU. In example embodiments, the field 502 indicates that the HEW device 104 is to acknowledge or block acknowledge frames received in a next transmitted MU PPDU.

[0065] In example embodiments, the field 502 indicates that the HEW devices 104 are to acknowledge or block acknowledge frames received in a next scheduled packet. For example, in one embodiment, the field 502 indicates that the HEW device 104 is to acknowledge frames received in a next packet. In example embodiments, the field 502 indicates that the HEW device 104 is to acknowledge a received management frame in a next transmission opportunity that the HEW device has. In example embodiments, the field 502 indicates that the HEW device 104 is to acknowledge a received management frame in a next MU PPDU transmitted by the HEW device 104.

[0066] In example embodiments, the field 502 indicates that the HEW device 104 is to acknowledge or block acknowledge frames in the current transmission opportunity, or if there is not a current transmission opportunity, in a next transmission opportunity. For example, in example embodiments the HEW device 104 can acknowledge or block acknowledge frames after sending data frames.

[0067] In example embodiments, the HEW device 104 acknowledging or block acknowledging frames in a next scheduled transmission opportunity has the technical effect of reducing the use of the wireless medium because the HEW device 104 does not have to contend for the wireless medium in order to acknowledge or block acknowledge frames.

[0068] In example embodiments, the HEW device 104 acknowledging or block acknowledging frames in a next scheduled MU PPDU has the technical effect of reducing the use of the wireless medium because the HEW device 104 does not have to contend for the wireless medium in order to acknowledge or block acknowledge frames and because the HEW device 104 acknowledges or block acknowledges the received frames concurrently with one or more other HEW devices 104.

[0069] In example embodiments, the HEW device 104 acknowledging or block acknowledging frames in a next scheduled MU PPDU has the technical effect of reducing the buffer sizes needed by the AP 102 and HEW device 104 because the HEW device 104 and AP 102 will receive an acknowledge or block acknowledgement sooner and thus will be able to free up buffers sooner.

[0070] FIG. 6 illustrates a HEW device 600 in accordance with some embodiments. HEW device 600 may be a HEW-compliant device that may be arranged to communicate with one or more other HEW devices, such as HEW devices 104 (FIG. 1) or access point 102 (FIG. 1) as well as communicate with legacy devices 106 (FIG. 1). HEW devices 104 and legacy devices 106 may also be referred to as HEW stations (STAs) and legacy STAs, respectively.

HEW device 600 may be suitable for operating as access point 102 (FIG. 1) or a HEW device 104 (FIG. 1). In accordance with embodiments, HEW device 600 may include, among other things, a transmit/receive element 601 (for example an antenna), a transceiver 602, physical layer circuitry (PHY) 604 and medium- access control layer circuitry (MAC) 606. PHY 604 and MAC 606 may be HEW-compliant layers and may also be compliant with one or more legacy IEEE 802.11 standards. MAC 606 may be arranged to configure PPDUs and arranged to transmit and receive PPDUs, among other things. HEW device 600 may also include other hardware circuitry 608 and memory 610 configured to perform the various operations described herein. The hardware circuitry 608 may be coupled to the transceiver 602, which may be coupled to the

transmit/receive element 601. While FIG. 6 depicts the hardware circuitry 608 and the transceiver 602 as separate components, the hardware circuitry 608 and the transceiver 602 may be integrated together in an electronic package or chip.

[0071] In example embodiments, the HEW device 104 is configured to perform one or more of the functions and/or methods described herein such as the methods, apparatuses, and functions described in conjunction with FIGS. 2 through 4, and in relation to packet 500.

[0072] The PHY 604 may be arranged to transmit the HEW PPDU. The

PHY 604 may include circuitry for modulation/demodulation,

upconversion/downconversion, filtering, amplification, etc. In some

embodiments, the hardware circuitry 608 may include one or more processors. The hardware circuitry 608 may be configured to perform functions based on instructions being stored in a RAM or ROM, or based on special purpose circuitry. In some embodiments, the hardware circuitry 608 may be configured to perform one or more of the functions described herein for sending and receiving BARs and BAs.

[0073] In some embodiments, two or more antennas may be coupled to the PHY 604 and arranged for sending and receiving signals including transmission of the HEW packets. The HEW device 600 may include a transceiver 602 to transmit and receive data such as HEW PPDU and packets that include an indication that the HEW device 600 should adapt the channel contention settings according to settings included in the packet. The memory 610 may store information for configuring the other circuitry to perform operations for one or more of the functions and/or methods described herein for acknowledgements and block acknowledgements such as the methods, apparatuses, and functions described in conjunction with FIGS. 2 through 4, and in relation to packet 500.

[0074] In some embodiments, the HEW device 600 may be configured to communicate using OFDM communication signals over a multicarrier communication channel. In some embodiments, HEW device 600 may be configured to communicate in accordance with one or more specific

communication standards, such as the Institute of Electrical and Electronics Engineers (IEEE) standards including IEEE 802.1 1-2012, 802.11n-2009, 802.1 lac-2013, 802.1 lax, standards and/or proposed specifications for WLANs, although the scope of the example embodiments is not limited in this respect as they may also be suitable to transmit and/or receive communications in accordance with other techniques and standards. In some embodiments, the HEW device 600 may use 4x symbol duration of 802.1 In or 802.1 lac.

[0075] In some embodiments, a HEW device 600 may be part of a portable wireless communication device, such as a personal digital assistant

(PDA), a laptop or portable computer with wireless communication capability, a web tablet, a wireless telephone, a smartphone, a wireless headset, a pager, an instant messaging device, a digital camera, an access point, a television, a medical device (e.g., a heart rate monitor, a blood pressure monitor, etc.), an access point, a base station, a transmit/receive device for a wireless standard such as 802.11 or 802.16, or other device that may receive and/or transmit information wirelessly. In some embodiments, the mobile device may include one or more of a keyboard, a display, a non-volatile memory port, multiple antennas, a graphics processor, an application processor, speakers, and other mobile device elements. The display may be an LCD screen including a touch screen.

[0076] The transmit/receive element 601 may comprise one or more directional or omnidirectional antennas, including, for example, dipole antennas, monopole antennas, patch antennas, loop antennas, microstrip antennas or other types of antennas suitable for transmission of RF signals. In some multiple-input multiple-output (MIMO) embodiments, the antennas may be effectively separated to take advantage of spatial diversity and the different channel characteristics that may result.

[0077] Although the device 600 is illustrated as having several separate functional elements, one or more of the functional elements may be combined and may be implemented by combinations of software-configured elements, such as processing elements including digital signal processors (DSPs), and/or other hardware elements. For example, some elements may comprise one or more microprocessors, DSPs, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), radio-frequency integrated circuits (RFICs) and combinations of various hardware and logic circuitry for performing at least the functions described herein. In some embodiments, the functional elements may refer to one or more processes operating on one or more processing elements.

[0078] Example embodiments have the technical effect of increasing the efficiency of the wireless medium by acknowledging or block acknowledging packets during a next transmission opportunity. In example embodiments, the HEW devices do not use the wireless medium for contention, but rather wait for a next transmission opportunity before acknowledging or block acknowledging the packets.

[0079] Example embodiments have the technical effect of increasing the efficiency of the wireless medium by acknowledging management packets during a next transmission opportunity. In example embodiments, the HEW devices do not use the wireless medium for contention, but rather wait for a next transmission opportunity before acknowledging the management packets.

[0080] Embodiments may be implemented in one or a combination of hardware, firmware and software. Embodiments may also be implemented as instructions stored on a computer-readable storage device, which may be read and executed by at least one processor to perform the operations described herein. A computer-readable storage device may include any non-transitory mechanism for storing information in a form readable by a machine (e.g., a computer). For example, a computer-readable storage device may include read- only memory (ROM), random-access memory (RAM), magnetic disk storage media, optical storage media, flash-memory devices, and other storage devices and media. Some embodiments may include one or more processors and may be configured with instructions stored on a computer-readable storage device.

[0081] The following examples pertain to further embodiments.

Example 1 is a high-efficiency wireless local-area network (HEW) device. The HEW device may include circuitry configured to: receive one or more packets in a transmit opportunity (TXOP) from an access point (AP), wherein the one or more packets indicate a schedule for the HEW device to transmit a multi-user physical-layer convergence procedure protocol data unit (MU PPDU); and transmit an acknowledgement of the one or more packets in the MU PPDU.

[0082] In Example 2, the subject matter of Example 1 can optionally include where the acknowledgement is one from the following group: a block acknowledgement frame and acknowledgment frame.

[0083] In Example 3, the subject matter of Examples 1 and 2 can optionally include where the circuitry is further to: transmit the

acknowledgement frame and the block acknowledgement frame in a first scheduled PPDU.

[0084] In Example 4, the subject matter of any of Examples 1 through 3 can optionally include where the one or more packets from the AP comprise a management frame, and wherein the circuitry is further configured to: transmit the acknowledgement of the management frame in a first scheduled MU PPDU.

[0085] In Example 5, the subject matter of any of Examples 1-4 can optionally include where the circuitry is further to: transmit one or more data packets to the AP.

[0086] In Example 6, the subject matter of any of Examples 1-5 can optionally include where the circuitry is further to: transmit the one or more data packets to the AP in the TXOP after the transmission of the acknowledgement of the one or more packets from the AP.

[0087] In Example 7, the subject matter of Examples 5 or 6 can optionally include where the circuitry is further to: receive an acknowledgement from the AP to the transmitted one or more data packets in a next TXOP.

[0088] In Example 8, the subject matter of any of Examples 1-7 can optionally include where the schedule includes a bandwidth for the HEW device to transmit and an indication of a duration for how long the HEW device can transmit.

[0089] In Example 9, the subject matter of any of Examples 1-8 can optionally include where the circuitry is further to: wait a short interface space and then transmit the acknowledgement of the one or more packets in the TXOP.

[0090] In Example 10, the subject matter of any of Examples 1-9 can optionally include where the circuitry is further to: receive an indication to use a new acknowledgement policy in at least one of a signal (SIG) field, in a media access control (MAC) field, in a beacon field, probe response, or a MAC management frame; and wherein the circuitry is further configured to: transmit an acknowledgement of the one or more packets in the scheduled MU PPDU, if the indication of the new acknowledgement policy is received, otherwise transmit the acknowledgement of the one or more packets according to a legacy protocol.

[0091] In Example 11, the subject matter of any of Examples 1-10 can optionally include where the one or more data packets are transmitted using orthogonal frequency division multiple access (OFDMA) and multi-user multiple-input multiple-output (MU-MIMO) and in accordance with 802.11 ax.

[0092] In Example 12, the subject matter of any of Examples 1-11 can optionally include where the schedule includes a duration for the

acknowledgment of the one or more packets.

[0093] In Example 13, the subject matter of any of Examples 1-12 can optionally include memory and a transceiver coupled to the circuitry.

[0094] In Example 14, the subject matter of Example 13 can optionally include one or more antennas coupled to the transceiver.

[0095] Example 15 is a method for acknowledgement performed on a high-efficiency wireless local-area network (HEW) device. The method may include receiving one or more packets in a transmit opportunity (TXOP) from an access point (AP), wherein the one or more packets indicate a schedule for the HEW device to transmit a multi-user physical-layer convergence procedure protocol data unit (MU PPDU); and transmitting an acknowledgement of the one or more packets in the MU PPDU.

[0096] In Example 16, the subject matter of Example 15 can optionally include where the acknowledgement is one from the following group: an acknowledgement frame and block acknowledgement frame.

[0097] In Example 17, the subject matter of Examples 15 and 16 can optionally include where the transmitting the acknowledgement further comprises: transmitting the acknowledgement in a first scheduled PPDU.

[0098] In Example 18, the subject matter of Examples 16 or 17 can optionally include where the schedule includes a duration for the

acknowledgment of the one or more packets. [0099] Example 19 is an access point (AP) including circuitry configured to: transmit one or more packets in a transmit opportunity (TXOP) to each of one or more high-efficiency wireless local-area network (HEW) devices, wherein the one or more packets indicate a schedule for each of the one or more HEW devices to transmit a multi-user physical-layer convergence procedure protocol data unit (MU PPDU); and receive an acknowledgement from each of the one or more HEW devices of the corresponding MU PPDU.

[00100] In Example 20, the subject matter of Example 19 can optionally include memory; a transceiver coupled to the circuitry; and one or more antennas coupled to the transceiver.

[00101] In Example 21, the subject matter of Examples 19 and 20 can optionally include where the acknowledgment is one from the following group: acknowledgement frame and block acknowledgement frame.

[00102] In Example 22, the subject matter of Example 21 can optionally include where the schedule includes a duration for each of the one or more HEW devices to transmit the acknowledgment of the one or more packets.

[00103] In Example 23, the subject matter of any of Examples 19-22 can optionally include where the circuitry is further configured to: receive a management frame from at least one of the one or more HEW devices; and transmit an acknowledgement of the management frame to each of the at least one of the one or more HEW devices in a next scheduled MU-PPDU.

[00104] Example 24 is a non-transitory computer-readable storage medium that stores instructions for execution by one or more processors to perform operations for high-efficiency wireless local-area network (HEW), where the instructions configure the one or more processors to: receive one or more packets in a transmit opportunity (TXOP) from an access point (AP), wherein the one or more packets indicate a schedule for to transmit a multi-user physical-layer convergence procedure protocol data unit (MU PPDU); and transmit an acknowledgement of the one or more packets in the scheduled MU PPDU.

[00105] In Example 25, the subject matter of Example 24 can optionally include herein the acknowledgement is one from the following group: an acknowledgment frame and block acknowledgment frame. [00106] The Abstract is provided to comply with 37 C.F.R. Section

1.72(b) requiring an abstract that will allow the reader to ascertain the nature and gist of the technical disclosure. It is submitted with the understanding that it will not be used to limit or interpret the scope or meaning of the claims. The following claims are hereby incorporated into the detailed description, with each claim standing on its own as a separate embodiment.