TWI556598B - Acknowledgement (ack) type indication and deferral time determination (2) - Google Patents

Description

Confirmation (ACK) type indication and deferred time decision (2) [Priority claim based on patent law]

U.S. Provisional Patent Application No. 61/769,718 (Attorney Docket No. 131781 P2) filed on Feb. 26, 2013, and U.S. Provisional Patent Application No. 61 filed on March 26, 2013 U.S. Provisional Patent Application No. 61/809,716 (Attorney Docket No. 131781P4) filed on April 8, 2013, filed on April 10, 2013, filed on April 10, 2013. Provisional Patent Application No. 61/810,663 (Attorney Docket No. 131781P5), US Provisional Patent Application No. 61/820,133 filed on May 6, 2013 (Attorney Docket No. 131781P6), July 2013 US Provisional Patent Application No. 61/843,906 (Attorney Docket No. 131781USL07) filed on the 9th, and U.S. Provisional Patent Application No. 61/844,008 filed on July 9, 2013 (Attorney Docket No. 131781USL08) And the benefit of U.S. Provisional Patent Application Serial No. 61/866,991, the entire disclosure of which is hereby incorporated by reference.

Some aspects of the case are generally related to wireless communications, and in particular to the type of response indicated for identifying the agreed data unit.

Wireless communication networks are widely deployed to provide a variety of communication services such as voice, video, packet data, messaging, and broadcast. The wireless networks may be multiplexed networks capable of supporting multiple users by sharing available network resources. Examples of such multiplex networks include code division multiplex access (CDMA) networks, time division multiplex access (TDMA) networks, frequency division multiplex access (FDMA) networks, and orthogonal FDMA (OFDMA). Network and single carrier FDMA (SC-FDMA) networks.

In order to address the desire for greater coverage and increased communication range, various solutions are being developed. One such scheme is the sub-1 GHz frequency range being developed by the Institute of Electrical and Electronics Engineers (IEEE) 802.11ah task group (eg, operating in the 902-928 MHz range in the United States). Such development is driven by the desire to utilize a frequency range that has a greater wireless range than other IEEE 802.11 groups and has lower blocking losses.

The various aspects of the case are generally related to the type of response indicated in the agreement data unit for confirming the transmitted agreement data unit.

Some aspects of the present disclosure provide a first device for wireless communication. The first device generally includes a transmitter and a processing system configured to transmit a Physical Layer Convergence Protocol (PLCP) Protocol Data Unit (PPDU) to the second device, the processing system configured to set the PLCP header of the PPDU At least one bit is expected to come from the second device in response to the transmitted PPDU The type of response set.

Some aspects of the present invention provide a means for wireless communication. The apparatus generally includes a receiver and a processing system configured to receive a PPDU, the processing system configured to determine a type of response to be sent for the PPDU based on at least one bit in a PLCP header of the PPDU.

Certain aspects of the present disclosure provide a method for wireless communication by a first device. The method generally includes transmitting a PPDU to a second device and setting at least one bit in a PLCP header of the PPDU to indicate a type of response expected from the second device in response to the transmitted PPDU.

Certain aspects of the present invention provide a method for wireless communication by a device. The method generally includes receiving a PPDU and determining a type of response to be sent for the PPDU based on at least one bit in a PLCP header of the PPDU.

Certain aspects of the present invention provide a first device for wireless communication. The first device generally includes means for transmitting a PPDU to the second device and means for setting at least one bit in the PLCP header of the PPDU to indicate a type of response expected from the second device in response to the transmitted PPDU .

Some aspects of the present invention provide a device for wireless communication. The apparatus generally includes means for receiving a PPDU and means for determining a type of response to be sent for the PPDU based on at least one bit in a PLCP header of the PPDU.

Some aspects of the present invention provide a computer program product for wireless communication. The computer program product generally includes computer readable media having instructions that are generally executable to transmit a PPDU to a device and to set at least one bit in a PLCP header of the PPDU to indicate a response to the transmitted The PPDU expects the type of response from the device.

Some aspects of the present invention provide a computer program product for wireless communication. The computer program product generally includes a computer readable medium having instructions operable to receive a PPDU at a device and determine a type of response to be sent for the PPDU based on at least one bit in a PLCP header of the PPDU. .

Some aspects of the present disclosure provide a first wireless station for wireless communication. The first wireless station generally includes at least one antenna; a transmitter configured to transmit a PPDU to the second wireless station via the at least one antenna; and a processing system configured to set the PLCP header of the PPDU At least one bit of the indication is expected to be of a type of response from the second wireless station in response to the transmitted PPDU.

Some aspects of the present invention provide a wireless station for wireless communication. The wireless station generally includes at least one antenna; a receiver configured to receive a PPDU via the at least one antenna; and a processing system configured to be based on at least one bit in a PLCP header of the PPDU Determine the type of response to be sent for this PPDU.

Some aspects of the present disclosure provide a first device for wireless communication. The first device generally includes a transmitter and a processing system, the transmitter configured to transmit a Medium Access Control (MAC) Protocol Data Unit (MPDU) to the second device, the processing system configured to set the MAC header of the MPDU At least one bit in the Frame Control Field (FCF) to indicate an acknowledgment (ACK) type from the second device in response to the transmitted MPDU.

Some aspects of the present invention provide a means for wireless communication. The apparatus generally includes a receiver and a processing system configured to receive a MAC header FCF of an MPDU, the processing system configured to determine an ACK type to be transmitted for the MPDU based on at least one bit in the FCF.

Certain aspects of the present disclosure provide a method for wireless communication by a first device. The method generally includes transmitting an MPDU to a second device and setting at least one of the FCFs in a MAC header of the MPDU to indicate an ACK type expected from the second device in response to the transmitted MPDU.

Some aspects of the present invention provide a method for wireless communication. The method generally includes receiving a MAC header FCF of an MPDU and determining an ACK type to be sent for the MPDU based on at least one bit in the FCF.

Certain aspects of the present invention provide a first device for wireless communication. The first device generally includes means for transmitting an MPDU to the second device and at least one bit in the FCF in the MAC header for setting the MPDU to indicate that an ACK from the second device is expected in response to the transmitted MPDU Type of means.

Some aspects of the present invention provide a device for wireless communication. The apparatus generally includes means for receiving a MAC header FCF of an MPDU and means for determining an ACK type to be transmitted for the MPDU based on at least one bit in the FCF.

Some aspects of the present invention provide a computer program product for wireless communication. The computer program product generally includes computer readable media having instructions that are generally executable to transmit an MPDU to a device and to set at least one bit in an FCF in a MAC header of the MPDU to indicate a response to the transmitted The MPDU is expected to be of the ACK type from the device.

Some aspects of the present invention provide a computer program product for wireless communication. The computer program product generally includes a computer readable medium having instructions operable to receive a MAC header FCF of an MPDU and determine an ACK type to be sent for the MPDU based on at least one bit in the FCF.

Some aspects of the present case provide a first wireless station. The first wireless station generally includes at least one antenna; a transmitter configured to transmit an MPDU to the second wireless station via the at least one antenna; and a processing system configured to set the MAC header of the MPDU At least one bit in the FCF is expected to be of an ACK type from the second wireless station in response to the transmitted MPDU.

Some aspects of the present invention provide a wireless station. The wireless station generally includes at least one antenna; a receiver configured to receive a MAC header FCF of the MPDU via the at least one antenna; and a processing system configured to base at least one bit in the FCF To determine the type of ACK to send for this MPDU.

Some aspects of the present invention provide a means for wireless communication. The apparatus generally includes a receiver and a processing system configured to receive a PPDU that is not intended to be sent to the apparatus, the processing system configured to determine a delay time based on at least one bit in a PLCP header of the PPDU, Wherein the at least one bit indicates a type of response to be sent by a target recipient of the PPDU.

Certain aspects of the present invention provide a method for wireless communication by a device. The method generally includes receiving a PPDU that is not intended for the device and determining a postponement based on at least one bit in the PLCP header of the PPDU Time, wherein the at least one bit indicates a type of response to be sent by a target recipient of the PPDU.

Some aspects of the present invention provide a device for wireless communication. The apparatus generally includes means for receiving a PPDU that is not intended for the device and means for determining a delay time based on at least one bit in a PLCP header of the PPDU, wherein the at least one bit indicates The type of response sent by the target recipient of the PPDU.

Some aspects of the present invention provide a computer program product for wireless communication by a device. The computer program product generally includes computer readable media having instructions operable to receive a PPDU that is not intended to be sent to the device, and determining a delay time based on at least one bit in a PLCP header of the PPDU, wherein The at least one bit indicates the type of response to be sent by the target recipient of the PPDU.

Some aspects of the present invention provide a wireless station. The wireless station generally includes at least one antenna, a receiver, and a processing system configured to receive, via the at least one antenna, a PPDU that is not intended for the wireless station, the processing system being configured to be based on a PLCP header of the PPDU At least one of the bits determines a delay time, wherein the at least one bit indicates a type of response to be sent by the target recipient of the PPDU.

100‧‧‧Multiple Access Multiple Input Multiple Output System

110‧‧‧ access point

120‧‧‧User terminal

120m‧‧‧user terminal

120x‧‧‧user terminal

130‧‧‧System Controller

208‧‧‧Source

210‧‧‧TX data processor

220‧‧‧Transmission space processor

224a‧‧‧Antenna

224ap‧‧‧Antenna

228‧‧‧channel estimator

230‧‧‧ Controller

234‧‧‧ Scheduler

240‧‧‧RX Space Processor

242‧‧‧RX data processor

244‧‧‧ data slot

252ma‧‧‧Antenna

252mu‧‧‧Antenna

252xa‧‧‧Antenna

252xu‧‧‧Antenna

254‧‧‧transmitter unit

260‧‧‧ receiving space processor

270‧‧‧ Receiving data processor

278‧‧‧channel estimator

280‧‧‧ Controller

286‧‧‧Source

288‧‧‧Transmission data processor

290‧‧‧Transmission space processor

302‧‧‧Wireless equipment

304‧‧‧ processor

306‧‧‧ memory

308‧‧‧Shell

310‧‧‧transmitter

312‧‧‧ Receiver

314‧‧‧ transceiver

316‧‧‧ transmit antenna

318‧‧‧Signal Detector

320‧‧‧Digital Signal Processor

322‧‧‧ busbar system

700‧‧‧ operation

700A‧‧ means

702‧‧‧Steps

704‧‧‧Steps

800‧‧‧ operation

800A‧‧ means

802‧‧ steps

802A‧‧ means

804‧‧‧ steps

804A‧‧ means

1900‧‧‧ operation

1900A‧‧ means

1902‧‧‧Steps

1904‧‧‧Steps

2000‧‧‧ operation

2000A‧‧ means

2002‧‧‧Steps

2004 ‧ ‧ steps

2200‧‧‧ operation

2200A‧‧ means

2202‧‧‧Steps

2204‧‧‧Steps

To more clearly understand the manner in which the above-described features of the present disclosure are used, the above briefly summarized aspects may be more specifically described with reference to the various aspects, some of which are illustrated in the drawings. However, it should be noted that the drawings only illustrate some typical aspects of the case and should not be considered as limiting the scope of the case. This description allows for other equivalent valid aspects.

FIG. 1 illustrates an example wireless communication network in accordance with certain aspects of the present disclosure.

2 is a block diagram of an example access point and user terminal in accordance with certain aspects of the present disclosure.

3 is a block diagram of an example wireless device in accordance with certain aspects of the present disclosure.

4-6 illustrate example encodings of acknowledgment (ACK) indication fields in accordance with certain aspects of the present disclosure.

7 is a flow diagram of an example operation of wireless communication by a originator in accordance with certain aspects of the present disclosure.

FIG. 7A illustrates an example apparatus capable of performing the operations shown in FIG.

8 is a flow diagram of an example operation of wireless communication by a recipient in accordance with certain aspects of the present disclosure.

FIG. 8A illustrates an example means capable of performing the operations shown in FIG.

9 illustrates example inter-frame space (EIFS) values for different response types and modulation and coding scheme (MCS) values in accordance with certain aspects of the present disclosure.

FIG. 10 illustrates an example encoding of an ACK indication field in accordance with certain aspects of the present disclosure.

11 and 12 illustrate possible ways to indicate an MCS for transmitting a response, in accordance with certain aspects of the present disclosure.

13 illustrates an example encoding of an ACK indicator field for multi-user multiple input multiple output (MU-MIMO) in accordance with certain aspects of the present disclosure.

14 and 15 illustrate example uses and formats of response bandwidth indicators in accordance with certain aspects of the present disclosure.

16 illustrates an example frame control field (FCF) with ACK policy bits in accordance with certain aspects of the present disclosure.

FIG. 17 illustrates an example interpretation of the ACK policy bit of FIG. 16 in accordance with certain aspects of the present disclosure.

18 illustrates an example equivalent ACK indication for a null data encapsulation (NDP) media access control (MAC) frame in accordance with certain aspects of the present disclosure.

19 is a flow diagram of an example operation of wireless communication by a originator in accordance with certain aspects of the present disclosure.

FIG. 19A illustrates an example means capable of performing the operations illustrated in FIG.

20 is a flow diagram of an example operation of wireless communication by a recipient in accordance with certain aspects of the present disclosure.

FIG. 20A illustrates an example means capable of performing the operations illustrated in FIG.

21 is a table of example values for a RESPONSE_INDICATION parameter indicating a response type in a TXVECTOR (TX vector) in accordance with certain aspects of the present disclosure.

22 is a flow diagram of example operations for wirelessly communicating by a third party device that receives PPDUs intended for different devices, in accordance with certain aspects of the present disclosure.

FIG. 22A illustrates an example means capable of performing the operations illustrated in FIG.

Various aspects of the present invention are described more fully hereinafter with reference to the accompanying drawings. However, the present invention may be embodied in many different forms and should not be construed as being limited to any specific structure or function. Rather, these aspects are provided so that this disclosure will be thorough and complete, and the scope of the invention will be fully conveyed by those skilled in the art. Based on the teachings herein, those skilled in the art will appreciate that the scope of the present invention is intended to cover any aspect of the present invention disclosed herein, regardless of whether the aspect is implemented independently or in combination with any other aspect of the present invention. For example, any number of aspects set forth herein can be used to implement an apparatus or a method of practice. In addition, the scope of the present invention is intended to cover such an apparatus or method that is practiced as a supplement to the various aspects of the present invention as described herein or other structural, functional or structural and functional. It should be understood that any aspect of the present disclosure disclosed herein can be implemented by one or more elements of the claim.

The wording "exemplary" is used herein to mean "serving as an example, instance or description." Any aspect described herein as "exemplary" is not necessarily to be construed as preferred or advantageous.

Although specific aspects are described herein, numerous variations and permutations of such aspects are within the scope of the present disclosure. Although some benefits and advantages of the preferred aspects are mentioned, the scope of the present invention is not intended to be limited to a particular benefit, use, or objective. Specifically, the various aspects of the case are intended to be broadly applicable to different wireless technologies, system configurations, networks, and transport protocols, some of which are The examples are illustrated in the accompanying drawings and the following description of the preferred aspects. The detailed description and the drawings are merely illustrative of the present invention and are not to be construed as limiting the scope of the invention.

The acronyms listed below can be used in this document in accordance with generally accepted usage in the field of wireless communications. Other acronyms may also be used herein and, if not defined in the list below, are defined where the acronym first appears in this document.

ACK................Confirm

A-MPDU.....Aggregate MAC protocol data unit

AP.................... access point

BA........................block confirmation

BAR.................block confirmation request

CRC.................cyclic redundancy check

DCF.................Distributed coordination function

DIFS.................DCF Interframe Space

EOF..................End of the frame

EIFS.................Extension frame space

FCS..................frame check sequence

ID....................identifier

IEEE................... Institute of Electrical and Electronics Engineers

LTF.................long training field

MAC................media access control

MSB................the most significant bit

MIMO..................multiple input and multiple output

MPDU.............MAC agreement data unit

MU..............multiple users

MU-MIMO.....multi-user multi-input multi-output

NDP................empty data packet

OFDM.............Orthogonal frequency division multiplexing

OFDMA..........Orthogonal Frequency Division Multiple Access

PHY................... physical layer

PLCP...............solid layer aggregation agreement

PPDU..............PLCP Agreement Data Unit

PSDU..............PLCP Service Data Unit

QoS................service quality

RDG................reverse grant

S1G.................Asia 1GHz

SDMA.............subspace multiplex access

SIFS................short interframe space

SIG..................signal

STA....................

STBC..............space time block coding

STF.................short training field

SU..................single user

TCP................Transmission Control Protocol

VHT...............Ultra high throughput

WLAN...........Wireless Local Area Network

Example wireless communication system

The techniques described herein can be used in a variety of broadband wireless communication systems, including communication systems based on orthogonal multiplexing schemes. Examples of such communication systems include sub-space multiplex access (SDMA), time division multiplex access (TDMA), orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiplexing access (SC) -FDMA) system, etc. SDMA systems can utilize multiple different directions to simultaneously transmit data belonging to multiple user terminals. The TDMA system allows multiple user terminals to share the same frequency channel by dividing the transmission signals into different time slots, each time slot being assigned to a different user terminal. The OFDMA system utilizes orthogonal frequency division multiplexing (OFDM), which is a modulation technique that divides the overall system bandwidth into multiple orthogonal subcarriers. The secondary carriers may also be referred to as tones, frequency bands, and the like. Under OFDM, each subcarrier can be independently modulated with data. SC-FDMA systems can be transmitted over sub-carriers distributed across system bandwidth using interleaved FDMA (IFDMA), transmitted on blocks consisting of adjacent subcarriers using localized FDMA (LFDMA), or using enhanced FDMA (EFDMA) Transmitted on multiple blocks consisting of adjacent subcarriers. In general, modulation symbols are transmitted in the frequency domain under OFDM and in the time domain under SC-FDMA.

The teachings herein may be incorporated into (eg, implemented within or performed by) various wired or wireless devices (eg, nodes). In some aspects, a wireless node implemented in accordance with the teachings herein can include an access point or an access terminal.

An access point ("AP") may include, be implemented as, or be referred to as a Node B, a Radio Network Controller ("RNC"), an evolved Node B (eNB), a Base Station Controller ("BSC"), Base transceiver station ("BTS"), base station ("BS"), transceiver function ("TF"), radio router, radio transceiver, base This Service Set ("BSS"), Extended Service Set ("ESS"), Radio Base Station ("RBS") or some other term.

An access terminal ("AT") can include, be implemented as, or be referred to as a subscriber station, subscriber unit, mobile station (MS), remote station, remote terminal, user terminal (UT), user agent, User equipment, user equipment (UE), user station or some other terminology. In some implementations, the access terminal can include a cellular telephone, a wireless telephone, a Session Initiation Protocol ("SIP") telephone, a Wireless Area Loop ("WLL") station, a Personal Digital Assistant ("PDA"), and wireless connectivity. A handheld device, station ("STA") or some other suitable processing device connected to a wireless data modem. Accordingly, one or more aspects taught herein can be incorporated into a telephone (eg, a cellular or smart phone), a computer (eg, a laptop), a tablet, a portable communication device, A portable computing device (eg, a personal data assistant), an entertainment device (eg, a music or video device or satellite radio), a global positioning system (GPS) device, or any other suitable device configured to communicate via wireless or wired media. In some aspects, the node is a wireless node. Such wireless nodes may provide connectivity or provide connectivity to the network (e.g., a wide area network (such as the Internet) or a cellular network), such as via a wired or wireless communication link.

FIG. 1 illustrates a multiplexed access multiple input multiple output (MIMO) system 100 having an access point and a user terminal. For simplicity, only one access point 110 is illustrated in FIG. An access point is typically a fixed station that communicates with each user terminal and may also be referred to as a base station or some other terminology. The user terminal can be fixed or mobile and can also be referred to as a mobile station, a wireless device, or some other terminology. Access point 110 can be on the downlink and uplink at any given time Communication with one or more user terminals 120 is performed. The downlink (ie, the forward link) is the communication link from the access point to the user terminal, and the uplink (ie, the reverse link) is the communication from the user terminal to the access point. link. The user terminal can also perform peer-to-peer communication with another user terminal. System controller 130 is coupled to each access point and provides coordination and control of the access points.

Although portions of the disclosure below will describe user terminals 120 that are capable of communicating via sub-space multiplex access (SDMA), for some aspects, user terminal 120 may also include some user terminals that do not support SDMA. Thus, for this aspect, the AP 110 can be configured to communicate with both the SDMA user terminal and the non-SDMA user terminal. This approach may facilitate allowing older versions of user terminals ("legacy" stations) to still be deployed in the enterprise to extend their useful life while allowing the introduction of newer SDMA user terminals where deemed appropriate.

System 100 employs multiple transmit antennas and multiple receive antennas for data transmission on the downlink and uplink. Access point 110 is equipped with N _ap antennas and represents multiple inputs (MI) for downlink transmissions and multiple outputs (MO) for uplink transmissions. The set with K selected user terminals 120 collectively represents multiple outputs for downlink transmissions and multiple inputs for uplink transmissions. For pure SDMA, if the data symbol stream of K user terminals is not multiplexed in code, frequency or time by some means, it is expected to have N _ap K 1. K may be greater than N _ap if the data symbol stream can be multiplexed using TDMA techniques, using different code channels under CDMA, using disjoint sets of subbands under OFDM, and the like. Each selected user terminal transmits user-specific data to the access point and/or receives user-specific data from the access point. In general, each selected user terminal may be equipped with one or multiple antennas (i.e., N _ut 1). The K selected user terminals may have the same or different number of antennas.

System 100 can be a time division duplex (TDD) system or a frequency division duplex (FDD) system. For TDD systems, the downlink and uplink share the same frequency band. For FDD systems, the downlink and uplink use different frequency bands. The MIMO system 100 can also utilize single or multiple carriers for transmission. Each user terminal can be equipped with a single antenna (eg, to suppress cost) or multiple antennas (eg, where additional cost can be supported). The system 100 can also be a TDMA system if the user terminals 120 share the same frequency channel by dividing the transmission/reception into different time slots, each time slot being assigned to a different user terminal 120.

2 illustrates a block diagram of an access point 110 and two user terminals 120m and 120x in a MIMO system 100. Access point 110 is equipped with N _t antennas 224a through 224t. User terminal 120m is equipped with N _{ut, m} antennas 252ma through 252mu, and user terminal 120x is equipped with N _{ut, x} antennas 252xa through 252xu. Access point 110 is the transmitting entity for the downlink and the receiving entity for the uplink. Each user terminal 120 is a transmitting entity for the uplink and a receiving entity for the downlink. As used herein, a "transport entity" is an independently operated device or device capable of transmitting data via a wireless channel, and a "receiving entity" is an independently operated device or device capable of receiving data via a wireless channel. In the following description, the subscript "dn " indicates the downlink, the subscript " up " indicates the uplink, N _up user terminals are selected for simultaneous transmission on the uplink, and N _dn user terminals are selected. For simultaneous transmission on the downlink, N _up may or may not be equal to N _dn , and N _up and N _dn may be static values or may vary with each scheduling interval. Beam steering or some other spatial processing technique can be used at the access point and user terminal.

On the uplink, at each user terminal 120 selected for uplink transmission, a transmit (TX) data processor 288 receives traffic data from data source 286 and control data from controller 280. The transmit data processor 288 processes (e.g., encodes, interleaves, and modulates) the traffic data of the user terminal and provides a stream of data symbols based on a coding and modulation scheme associated with the rate selected for the user terminal. The transmit spatial processor 290 performs spatial processing on data symbol streams to N _{ut, m} antennas provide N _{ut, m} transmit symbol streams. Each transmitter unit (TMTR) 254 receives and processes (e.g., converts to analog, amplifies, filters, and upconverts) respective transmit symbol streams to produce an uplink signal. N _{ut, m} transmitter units 254 provide N _{ut, m} uplink signals for transmission from N _{ut, m} antennas 252 to the access point.

N _up user terminals can be scheduled for simultaneous transmission on the uplink. Each of the user terminals performs spatial processing on its own data symbol stream and transmits its own set of transmitted symbol streams to the access point on the uplink.

At access point 110, N _ap antennas 224a through 224ap receive uplink signals from all N _up user terminals transmitting on the uplink. Each antenna 224 provides a received signal to a respective receiver unit (RCVR) 222. Each receiver unit 222 performs processing complementary to that performed by the transmitter unit 254 and provides a received symbol stream. The RX spatial processor 240 performs receiver spatial processing on the N _ap received symbol streams from the N _ap receiver units 222 and provides N _up recovered uplink data symbol streams. Receiver spatial processing is performed based on channel correlation matrix inversion (CCMI), minimum mean square error (MMSE), soft interference cancellation (SIC), or some other technique. Each recovered uplink data symbol stream is an estimate of the data symbol stream transmitted by the respective user terminal. RX data processor 242 processes (e.g., demodulates, deinterleaves, and decodes) the recovered uplink data symbol stream to obtain a rate based on the rate used for each recovered uplink data symbol stream. Decode the data. The decoded data for each user terminal can be provided to data slot 244 for storage and/or to controller 230 for further processing.

On the downlink, at access point 110, a transmit data processor 210 receives traffic data process number N _dn user terminal downlink transmission from a data source, then the discharge is to be 208, the controller 230 from Control data and possibly other information from scheduler 234. Various types of data can be sent on different transmission channels. TX data processor 210 processes (e.g., encodes, interleaves, and modulates) traffic data to the user terminal based on the rate selected for each user terminal. The transmit data processor 210 provides N _dn downlink data symbol streams for N _dn user terminals. The transmit spatial processor 220 performs spatial processing (such as precoding or beamforming, as described in the present case) for N _dn downlink data symbol streams and provides N _ap transmit symbol streams for the N _ap antennas. Each transmitter unit 222 receives and processes a respective transmit symbol stream to generate a downlink signal. The N _ap transmitter units 222 provide N _ap downlink signals for transmission from the N _ap antennas 224 to the user terminal.

At each user terminal _120, N _{ut, m} antennas 252 receive the N _ap downlink signals from access point 110. Each receiver unit 254 processes the received signal from the associated antenna 252 and provides a received symbol stream. Spatial processor 260 receives from the N _{ut, m} th receiver unit N _{ut 254, m} is a received symbol streams, and perform receiver spatial processing is supplied to the downlink data symbol stream is recovered user terminal . Receiver spatial processing is performed according to CCMI, MMSE, or some other technique. Receive data processor 270 processes (e.g., demodulates, deinterleaves, and decodes) the recovered downlink data symbol stream to obtain decoded data for the user terminal.

At each user terminal 120, channel estimator 278 estimates the downlink channel response and provides a downlink channel estimate, which may include channel gain estimates, SNR estimates, noise variances, and the like. Similarly, channel estimator 228 estimates the uplink channel response and provides an uplink channel estimate. Controller 280 for each user terminal typically based on the user terminal downlink channel response matrix H _{dn, m} derives the spatial filter matrix for the user terminal. The controller 230 response matrix H _up based on the effective uplink _{channel, eff} derives the spatial filter matrix for the access point. The controller 280 of each user terminal can send feedback information (eg, downlink and/or uplink feature vectors, eigenvalues, SNR estimates, etc.) to the access point. Controllers 230 and 280 also control the operation of various processing units at access point 110 and user terminal 120, respectively.

FIG. 3 illustrates various elements that may be utilized in wireless device 302 that may be employed within MIMO system 100. Wireless device 302 is an example of a device that can be configured to implement the various methods described herein. Wireless device 302 can be access point 110 or user terminal 120.

Wireless device 302 can include a processor 304 that controls the operation of wireless device 302. Processor 304 may also be referred to as a central processing unit (CPU). Can include Memory 306, both read only memory (ROM) and random access memory (RAM), provides instructions and data to processor 304. A portion of the memory 306 may also include non-volatile random access memory (NVRAM). The processor 304 typically performs logical and arithmetic operations based on program instructions stored in the memory 306. The instructions in memory 306 may be executable to implement the methods described herein.

The wireless device 302 can also include a housing 308 that can include a transmitter 310 and a receiver 312 to allow for the transfer and reception of data between the wireless device 302 and a remote location. Transmitter 310 and receiver 312 can be combined into transceiver 314. A single or a plurality of transmit antennas 316 can be attached to the housing 308 and electrically coupled to the transceiver 314. Wireless device 302 can also include (not shown) multiple transmitters, multiple receivers, and multiple transceivers.

The wireless device 302 can also include a signal detector 318 that can be used to attempt to detect and quantize the level of signals received by the transceiver 314. Signal detector 318 can detect signals such as total energy, energy per symbol per symbol, power spectral density, and other signals. Wireless device 302 can also include a digital signal processor (DSP) 320 for processing signals.

The various components of the wireless device 302 can be coupled together by a busbar system 322 that can include, in addition to the data busbars, a power busbar, a control signal busbar, and a status signal busbar.

Example ACK type indication and EIFS

IEEE 802.11ah, also known as HEW (High Efficiency WiFi or High Efficiency WLAN) or Sub 1 GHz (S1G), is a modification of the IEEE 802.11 standard that allows for longer ranges in 802.11 networks. The 802.11ah channel will only be dedicated to 802.11ah, which implies that legacy 802.11 devices are not present in these channels. This permission A third-party receiver that redesigns the PLCP header (also known as the PHY header) and resolves the PPDU does not currently know if there will be a response to the PPDU.

Certain aspects of the present disclosure provide techniques and apparatus for transmitting PPDUs (e.g., S1G PPDUs) that include an ACK indicator field (also referred to as a response indication field) in its PLCP header. The ACK indicator field may indicate the type of response (if any) to the PPDU. This type of response is used by a third party receiver (not the recipient of the MPDU in the PPDU or the recipient of the MPDU in the PPDU) to defer the possible response to the PPDU. The postponement can be based on restoring the inter-frame space (EIFS) time before the backoff. For some aspects, the delay may be based on a response indication delay (RID) procedure. If the MAC part cannot be decoded, the EIFS is started after the received PPDU.

According to some aspects, the ACK indicator field can be included in the Signal (SIG) field of the S1G PPDU. As used herein, the term "SIG field" may also refer to the Signal A field (SIG-A field) and/or the Signal B field (SIG-B field), for example, at a length greater than or equal to 2 MHz. In the preamble signal. The ACK indicator field can be a 2-bit size that specifies four possible response types (0-3). An exemplary encoding of the ACK indicator field is illustrated in FIG.

The convention in S1G is that the MPDU <512 bytes are indicated by the octet count in the SIG field and the packet 512 octets is indicated by the number of symbols of the PPDU. In the latter case, the A-MPDU is used in the MAC portion of the frame (this implies that the octet count of the MPDU is indicated by the MPDU delimiter and also implies that a block acknowledgment (block Ack) can be used). Whether the length field is interpreted as an octet count or a symbol count depends on the setting of the aggregated bit. For some aspects, the length, aggregate, and ACK indications are the SIG fields of the PLCP header. a part of. The End of Frame (EOF) field is part of the MPDU delimiter. When the first non-zero length MPDU delimiter has an EOF value equal to 1, this signal delivery notification informs that only a single MPDU exists in the PPDU and the response should be an ACK frame (normal or NDP format, where NDP usually contains only PLCP header, which is the real empty data packet). Otherwise, the response to the A-MPDU is block Ack (normal or NDP format). The normal block Ack frame is typically a 32-bit tuple compressed type that includes an MPDU header, a start sequence number (SSN), and a 64-bit block Ack bit map.

Reverse grant (RDG) generally refers to the mechanism used to grant the receiver the time to send a response frame other than ACK or block Ack. For RDG, the ACK indication is set to a long response (ACK indication = 3).

The exemplary ACK indication field code illustrated in FIG. 4 provides an indication of no response, NDP response, normal (control) response, and long response. There is no indication of a normal ACK combined with a very high throughput (VHT) single MPDU, since it is assumed that an NDP ACK can be used in this case instead of a normal ACK. It is possible to add a normal ACK indication for a VHT single MPDU, but this would require a fifth response type, which means that 3 bits are used for the ACK indication field. Currently only 2 bits are available, so this design choice omits the normal ACK option for VHT single MPDUs.

It is possible to use the ACK indication value 2 (normal response) to send a normal ACK as a response to a VHT single MPDU, but both the sender and the receiver of the normal ACK can observe the EIFS after ACK, and the EIFS after the ACK is equal to the block Ack (BA) Transmission time difference between ACK and ACK: ACK after ACK = BA transmission time - ACK transmission time

An exemplary encoding of an ACK indication field including an EIFS after ACK (for a VHT single MPDU) is illustrated in FIG.

Another solution is to send a block Ack frame instead of an ACK frame, where the SSN and block Ack bit maps are set to all 0s or some other reserved value. Yet another solution is to fill the 32-octet A-MPDU with a zero-length delimiter (4 octets non-zero MPDU delimiter, 14 octets ACK, 2 octets) The ACK is sent in the form of a bit group's A-MPDU padding and 3 zero length delimiters. 6 illustrates an exemplary encoding of an ACK indicator field for an ACK of 32 octets for a VHT single MPDU.

Long response types potentially result in very long EIFS being initiated at third party recipients. To avoid unfairness, a PPDU with an ACK indication (=3) that is a long response may be followed by a PPDU with a different ACK indication (<3). The following PPDU truncates the EIFS or RID at the third party receiver and puts all the contenders back on the same schedule to resume the backoff.

In one embodiment, the initiator of the long response may truncate the EIFS by transmitting a transmission opportunity (TXOP) truncation frame as the last frame in the exchange. This TXOP truncation may be a contention free end (CF-End) frame or a CTS-to-Self (CTS addressed to itself) frame with the field value set to zero. In one embodiment, the CF-End or CTS-To-Self frame may be a null data packet (NDP) in which all control information is included in the SIG field of the NDP frame. In one embodiment, it is assumed that an NDP CTS frame acting as a TXOP truncation frame can be transmitted shorter and can be transmitted with the lowest modulation and coding scheme (MCS) than a normal CF-End frame and is therefore more efficient, Then the NDP CTS frame can replace CF-End in normal network operation. As an example, the NDP CTS frame Can be used by TXOP holders to re-determine the NAV of surrounding STAs when they no longer have data to transmit, or for release may have been granted to their peers using RDG-like protocols (such as speed frame exchange or reverse protocol) STA's TXOP. In such an embodiment, if the inter-sector STA does not access the media after a certain amount of time (eg, SIFS time), the TXOP holder may be at a certain amount of time (eg, Point Coordination Function (PCF). After the inter-frame space (PIFS) time, an NDP CTS frame with a duration of 0 is sent to reset the NAV and release the media.

In some aspects, the techniques provided herein generally provide a mapping of ACK indicator bits, which allows the receiver to perform a request for multiple frames (including NDP, normal control frame, and long frame) for the request frame. Select (and allow other STAs to detect this). The selection may be based on an ACK indication field in the PHY preamble signal and as described above, other information available at the PHY preamble signal (eg, aggregated bits) and some information at the MPDU delimiter (eg, EOF) may be used. . Certain aspects of the present invention are also generally related to calculating an EIFS or RID based on the indication.

In some cases, the new ACK indication may not have an explicit value for the "Block Ack" ACK policy from the QoS Control field, but only an implicit value. This can help the ACK indicate the bits in the field. In some cases, an implicit indication of the "block Ack" ACK policy can be provided via the following settings:

- ACK indication = 0 (no response)

- Aggregation = 1 (A-MPDU)

- The first non-zero length MPDU delimiter has EOF = 0 (ie no VHT single A-MPDU)

When the value is delimited between the PPDU header and the first non-zero length MPDU In the case of the symbol, the ACK policy is equal to "block Ack", which means that the status of the received MPDU is recorded (that is, the block Ack bitmap can be formed based on this), but no block Ack frame is followed by the PPDU. send.

Included in the SIG field as described above provides an indication of the NIP control response frame and the normal control response frame and the duration of the speed frame exchange and asymmetric BA in the SIG field. This allows third-party STAs to correctly predict the duration of the response, enabling dynamic EIFS calculations based solely on PLCP header information. The target recipient may then decide its ACK policy based on the rules described herein for the short MAC header or with the existing ACK policy field in the QoS Control field of the normal MAC header.

7 is a flow diagram of an example operation 700 for wireless communication by a start (transmit) device in accordance with certain aspects of the present disclosure. Operation 700 can begin at 702 where the initiating device transmits a PPDU to the receiving device. At 704, prior to the actual transmission at 702, the initiating device sets at least one bit in the PLCP header of the PPDU to indicate the type of response expected from the receiving device in response to the transmitted PPDU.

According to some aspects, the at least one bit is in a first portion of the PLCP header that can be decoded by the second device and also by other devices. For some aspects, the first portion of the PLCP header includes a signal (SIG) field if the PPDU is a 1 MHz PPDU or a signal A if the PPDU is a PPDU greater than or equal to 2 MHz (SIG- A) Field.

According to some aspects, operation 700 further includes the initiating device selecting an indication (i.e., a response type) from a group type comprising at least one type that allows the second device to send a response in a null data packet (NDP).

According to some aspects, operation 700 further includes the initiating device setting a bit in a signal (SIG) field or a media access control (MAC) protocol data unit (MPDU) delimiter of the PPDU to indicate that the PPDU comprises a single The value of the MPDU.

According to some aspects, operation 700 further includes the initiating device receiving an NDP block acknowledgment (BA) having a BA bit map. In this case, the processing system can be configured to interpret one or more bits of the BA bit meta-map as an extension of the acknowledgment identification (ACK ID).

According to some aspects, the at least one bit is set to a value indicating that a response is not expected.

According to some aspects, the at least one bit is at least two bits set to indicate an undesired response, a desired NIP response, a desired normal response, or a value expected to have a long response. For some aspects, operation 700 further includes the initiating device receiving a response to the PPDU and transmitting the second PPDU upon receiving a response to the previously transmitted PPDU. For some aspects, operation 700 can further include the initiating device setting at least one bit in the PLCP header of the second PPDU to indicate that a response from the second device is not expected in response to the transmitted second PPDU. For some aspects, operation 700 can further include transmitting a frame to truncate the EIFS if the at least two bits are set to indicate a value that is expected to have a long response. The frame can be a contention free (CF-End) frame or a clear to send (CTS) frame. As indicated above, the frame may be a null data packet (NDP).

According to some aspects, operation 700 can further include the initiating device setting the bit in the PLCP header of the PPDU (eg, in the SIG field) to the indication Whether the PPDU includes the value of the Aggregation MAC Protocol Data Unit (A-MPDU).

According to some aspects, operation 700 can further include the initiating device setting the end of frame (EOF) value of the first MPDU delimiter of the PPDU having a non-zero length field to zero. This EOF value further indicates the type of response expected from the second device in response to the transmitted PPDU.

According to some aspects, operation 700 can further include the initiating device setting the other bit in the PLCP header of the PPDU to indicate that the PPDU was transmitted as a multi-user multiple input multiple output (MU-MIMO) packet. value. In this case, the MU-MIMO packet may include different packets intended to be sent to users at different user locations, and the at least one bit in the PLCP header of the PPDU (the MU-MIMO packet) may indicate Only the type of response from the second device is desired, the second device corresponding to the user having a non-zero space-time stream number (Nsts) at the first user location. For some aspects, the first user location is based on a group identifier (GID). For some aspects, operation 700 can further include initiating the device to include the GID in the PLCP header. For some aspects, the MU-MIMO packet includes different packets intended to be sent to users at different user locations, and the at least one bit in the PLCP header indicates that only the desired and from the first user location The type of response of the second device corresponding to the user. In this case, the first device may not expect at least one of the users from the non-first user location or the non-zero space-time flow number (Nsts) at the non-first user location. Response. For some aspects, operation 700 can further include separately indicating one or more response types that are expected to come from one or more users at other user locations.

Operation 700 may further include initiating device settings, depending on certain aspects At least one other bit in the PLCP header of the PPDU to indicate the expected bandwidth of the response from the second device.

According to some aspects, operation 700 can further include initiating the device encoding in the PLCP header or otherwise providing a modulation and coding scheme (MCS) to be used by the second device to transmit the response.

According to some aspects, operation 700 can further include transmitting a frame control field (FCF) having at least one ACK policy bit, the at least one ACK policy bit indicating a response along with the at least one bit in the PLCP header The type of response from the second device is expected for the transmitted PPDU. In this case, the at least one ACK policy bit may include at least one of the type fields of the FCF. For other aspects, the PPDU can include a Quality of Service (QoS) control field having at least one ACK policy bit, the at least one ACK policy bit, along with the at least one bit in the PLCP header, in response to the transmitted The PPDU is expected to be the type of response from the second device.

According to some aspects, the PPDU further includes at least one of: at least one ACK policy bit in a Frame Control Field (FCF) or Quality of Service (QoS) control field; or Media Access Control (MAC) of the PPDU The End of Frame (EOF) field in the Protocol Data Unit (MPDU) delimiter. In this case, the at least one of the ACK policy bit or the EOF field along with the at least one bit in the PLCP header indicates the type of response expected from the second device. For some aspects, the type of the initiating PPDU indicates the type of response expected from the second device.

According to some aspects, the setting at 704 can include receiving from a medium access control (MAC) layer (or, more specifically, from a sublayer of the MAC layer) The parameter in the parameter set sets the at least one bit. The set of parameters may be a TX vector and the parameter may be a response indication (eg, RESPONSE INDICATION, also referred to as an ACK indication).

According to some aspects, the setting at 704 can include setting the at least one bit based on a set of parameters in a Media Access Control (MAC) header of the PPDU.

According to some aspects, if the initiating device does not receive a response to the PPDU after the point coordination function (PCF) inter-frame space (PIFS) time, operation 700 may further involve transmitting the second PPDU to reset the response indication delay ( RID) Counter or Network Allocation Vector (NAV) counter.

According to some aspects, the operations further include negotiating a bandwidth for the response with the second device.

8 is a flow diagram of an example operation 800 for wireless communication by a receiving device in accordance with certain aspects of the present disclosure. Operation 800 can begin at 802 where a receiving device receives a PPDU. At 804, the receiving device determines a type of response to be sent for the PPDU based on at least one bit in the PLCP header of the PPDU.

According to some aspects, the response type is selected from a group type comprising at least one type that allows the device to send a response in a null data packet (NDP). In this case, operation 800 may further involve the receiving device transmitting the type of response in the NDP based on the decision.

According to some aspects, the type of response decided is an empty data packet (NDP) block acknowledgment (BA). In this case, operation 800 can further include using one or more bits of the BA bit map to generate an extended acknowledgment identification (ACK ID) to be transmitted in the NDP BA.

Depending on certain aspects, determining the response type at 804 may involve determining that the at least one bit is set to a value indicating that no response is to be sent.

According to some aspects, operation 800 can further include the receiving device determining that a bit in the PLCP header (eg, SIG field) of the PPDU is set to indicate that the PPDU includes an aggregate media access control (MAC) protocol data unit ( The value of A-MPDU) and the block acknowledgment (BA) in response to the PPDU is transmitted based on the bit in the PLCP header (eg, SIG field). For some aspects, the decision can be based on the EOF field in the MPDU delimiter.

In accordance with certain aspects, operation 800 can further include the receiving device determining that a bit in the PLCP header of the PPDU is set to indicate that the PPDU was transmitted as a multi-user multiple input multiple output (MU-MIMO) packet. In this case, the MU-MIMO packet may include different packets intended to be sent to users at different user locations. For some aspects, the at least one bit in the PLCP header of the PPDU (the MU-MIMO packet) may indicate that only the response type from a single user at the first user location is desired, the receiving device may correspond The user at a location other than the first user location, and/or operation 800 can further include determining the type of response separately based on information other than the at least one bit in the PLCP header. For other aspects, the at least one bit in the PLCP header may indicate a response type from only a device corresponding to a user having a non-zero space-time flow number (Nsts) at the first user location.

According to some aspects, operation 800 can further include determining a bandwidth of the response based on at least one other bit in the PLCP header of the PPDU. In this case, operation 800 can also include determining an EIFS based at least in part on the at least one other bit. For other aspects, operation 800 can further include based on the indication The ability to determine the bandwidth of the response (eg, indicating support for S1G capability elements that operate with bandwidth).

Operation 800 may further involve determining a modulation and coding scheme (MCS) for transmitting a response based on one or more other bits in the PLCP header, in accordance with certain aspects.

According to some aspects, operation 800 can further include the receiving device determining that the first non-zero length MPDU delimiter has an End of Frame (EOF) value set to zero and transmitting a block acknowledgment in response to the PPDU based on the EOF value (BA). If the at least one bit in the PLCP header indicates a null data packet (NDP) response, the processing system can be configured to determine that the type of response to be sent is an NDP BA. If the at least one bit in the PLCP header indicates a normal response, the processing system can be configured to decide that the type of response to be sent is a normal BA.

According to some aspects, operation 800 can further include the receiving device determining that the first non-zero length MPDU delimiter has an End of Frame (EOF) value set to one and transmitting an acknowledgment responsive to the PPDU based on the EOF value ( ACK). If the at least one bit in the PLCP header indicates a null data packet (NDP) response, the processing system can be configured to determine that the type of response to be sent is an NDP ACK. If the at least one bit in the PLCP header indicates a normal response, the processing system is configured to determine that the type of response to be sent is a normal ACK.

Operation 800 may, in accordance with certain aspects, further cause the receiving device to transmit a response of the determined type.

According to some aspects, the type of response to be transmitted is determined at 804 based on at least one of: an aggregated bit in the PLCP header, and at least one Media Access Control (MAC) Protocol Data Unit (MPDU) delimitation in the PPDU. Message in the symbol End of box (EOF) value or at least one ACK policy bit in the Frame Control Field (FCF) or Quality of Service (QoS) control field of the PPDU.

According to some aspects, the at least one bit is set to a value indicating that a long response is to be sent. In this case, operation 800 can further include determining an EIFS based on the long response and receiving a frame to truncate the EIFS. For some aspects, the frame is a contention free (CF-End) frame or a clear to send (CTS) frame.

According to some aspects, operation 800 further involves receiving a frame control field (FCF) including at least one ACK policy bit, wherein the determining at 804 further comprises determining a response to send based on the at least one ACK policy bit Types of. For some aspects, the at least one ACK policy bit includes at least one of the type fields of the FCF. For other aspects, operation 800 further involves receiving a quality of service (QoS) control field including at least one ACK policy bit, wherein the determining at 804 further comprises determining a type of response to send based on the at least one ACK policy bit .

According to some aspects, the decision at 804 can further include determining a type of response to send based on parameters sent in a parameter set of the MAC layer (or more specifically, the MAC sublayer). The set of parameters can be based on the at least one bit in the PLCP header. For some aspects, the parameter set can be an RX vector and the parameter can be a response indication (eg, RESPONSE_INDICATION). For some aspects, operation 800 can further include setting a RID counter based on the parameter.

As illustrated in Figure 9 and as mentioned above, the device detecting the packet format described above may be capable of being based, at least in part, on the PLCP header. The indicated expected response type is used to calculate the EIFS. However, depending on certain aspects, an asymmetric BA response can be supported in which the BA is transmitted at a different bandwidth and rate than the request packet. As a result, the EIFS can also be calculated based, at least in part, on the bandwidth of the response frame. As shown in the "Dynamic EIFS" column of Figure 9, the EIFS can vary significantly for different response types and different bandwidths. The ACK indication allows all STAs to correctly calculate the EIFS based on the information available in the PLCP header of the received packet. The table in Figure 9 is for transmission with MCS0 at 1 MHz, MCS0 at 2 MHz, and MCS4 for both 1 MHz and 2 MHz.

As illustrated in the ACK indication overview of Figure 10, the ACK indication = 0 in the SIG field of the received message indicates no response, where no immediate response is requested. Aggregate bit=0 indicates no Ack policy. Aggregation bit = 1 (or MU) along with the first non-zero EOF = 1 also indicates no Ack policy, while the first non-zero EOF = 0 indicates the block Ack policy. In the case of ACK indication = 0 (no response), the third party receiving STA can calculate EIFS = DIFS. This calculation may be based only on the value indicated by the ACK, so the MAC header of the received frame does not need to be decoded.

The ACK indication in the SIG field of the received frame indicates that the NDP responds. Aggregate bit=0 indicates NDP ACK or NDP CTS. Aggregation bit = 1 (or MU) along with the first non-zero EOF = 1 indicates NDP ACK, while the first non-zero EOF = 0 indicates NDP BA. In the NDP response scenario, the third party receiving STA may calculate the EIFS=aSIFSTime+DIFS+_NDP transmission time. This calculation can be based only on the value indicated by the ACK.

The ACK indication in the SIG field of the received frame = 2 indicates a normal response. Aggregate bit=0 indicates a 14-byte response (ACK or CTS). Aggregate bit = 1 (or MU) indicates a 32-bit tuple response (BA, block acknowledgment TWT (BAT) ) or A-MPDU ACK, TWT acknowledgment (TACK), where "TWT" stands for "target wake time"). The first non-zero EOF=1 indicates the A-MPDU padding ACK or TACK (again, the short TWT acknowledgment (STACK) will be padded to 32 bytes by the A-MPDU), while the first non-zero EOF=0 indicates the BA Or BAT. In a normal response scenario, the third party receiving STA may calculate the EIFS depending on the aggregation bit. In the case of aggregate bit = 0, EIFS = aSIFSTime + DIFS + _ACK transfer time, and in the case of aggregate bit = 1, EIFS = aSIFSTime + DIFS + _BA transfer time. The response MCS can be determined based on the PHY mandatory MCS set.

For long response types (eg, ACK indication = 3), aggregation = 0 can be substantially equivalent to the "no explicit Ack" policy, regardless of the EOF value, and the speed frame response type can be transmitted. Similarly, aggregation = 1 along with EOF = 1 can be substantially equivalent to the "no explicit Ack" policy, and the speed frame response type can be transmitted. In another aspect, aggregation = 1 and EOF = 0 can be substantially equivalent to the "block Ack" policy, and the recipient can respond with a speed frame that updates the block Ack policy accordingly.

According to some aspects, an ACK indication can be provided in the PLCP header of the MU-MIMO packet. In such cases, the ACK indication (eg, in the SIG-A field of the MU-MIMO Packet PLCP header) may be applied to only a single user. For example, the ACK indication in the SIG-A field may only be applied to users with user position = 0, while users with other locations (user location > 0) may all have ACK indication = 0. For MU-MIMO packets, this aggregate bit can always be set to one. FIG. 13 illustrates an example encoding for a MU-MIMO ACK indication, and FIG. 13 illustrates an equivalent ACK strategy based on an EOF value, a desired response frame, and a response length.

In some cases, the MCS may not be present in the MU SIG-A field (eg, the MCS is in the SIG-B field), which may result in a MU packet for a specified normal response (eg, ACK indication = 2). The decision to respond to the MCS has become complicated. In such cases, the MCS to be used for the response can be encoded in the PLCP header of the packet. For example, there are currently two reserved bits in the MU SIG-A field, which can be used to encode a response MCS (eg, a 2-bit response MCS field). The bits can also be used in the SU SIG-A field, which can be used to make the response more deterministic. As an example, the response MCS field can be reserved for ACK indication ≠ 2 (normal response) as follows: ACK indication = 0 (no response)

ACK indication = 1 (NDP response)

ACK indication = 3 (long response) The possible encoding of this response MCS field (using these two reserved bits) can be: response MCS = 0: MCS0

Response MCS=1: MCS2

Respond to MCS=2: MCS4

Response MCS=3: MCS6 Figures 11 and 12 further illustrate how such (general) reserved bits can be used to incorporate such a response MCS field value into the 2 MHz SIG-A field.

In some cases, one of the SU SIG-A field and/or the MU SIG-A field (any one of the two bits that can be reserved) can be used by the sender to receive The party indicates whether the PLCP header of the response frame can be a lower bandwidth (BW) (for example, this document is called a response BW indicator field, as shown in the figure Shown in 14). For example, a transmitter of a 2 MHz PPDU may indicate that the receiver should transmit a 1 MHz response frame by the bit (eg, set to 1). The type of response frame may depend on the ACK indication field and/or the EOF field as well as other methods described herein. In this embodiment, the third party STA may use this information to correctly calculate the EIFS value based on this additional indication in the SU (MU) SIG-A information. For example, based on the response BW indicator bit, the third party station can determine if the response frame can be a 1 MHz frame (and therefore have a different PLCP header and MCS rate). In this embodiment, the EIFS calculation rules may take into account the type of PLCP header to calculate the EIFS depending on the ACK indication field present in the SIG-A field. In another embodiment, the reply BW indicator bit may be located in another field of the PPDU (having a subfield with a reserved value).

As an example, the response BW indicator can be located in the service field of the PPDU. In another embodiment, the one of the service fields of the PPDU may be used to indicate to the target receiver that the received frame is a relay frame (ie, one of the service fields of the received PPDU) The bit can be a relay frame bit). The relay frame bit can be used by the STA to indicate that during the TXOP sharing procedure in the relay mode, the relay can respond to the received frame with an ACK or whether the relay can directly forward the received PPDU to the next One hop (for example, AP). Similarly, the relay frame bit can also be used in the downlink (i.e., for transmission from the AP to the STA by relay). In this embodiment, if the target receiver (relay STA) can forward the PPDU to the next hop STA (eg, AP) sharing the same TXOP initiated by the STA that initiated the PPDU, the relay frame bit can be Is set to 1. Otherwise, the relay frame bit can be set to 0 and indicate that the STA generating the PPDU can expect to forward the frame to the next hop (eg, AP) by the receiver (ie, relay) before There is an ACK from this relay.

As an example, the ACK indication in the 2 MHz PPDU is set to 1 along with the response BW indicator being set to 1 (eg, indicating a 1 MHz response PPDU) and the EOF field is set to 1 to provide the following indication: (1) Receiver STA Responding with a 1 MHz NDP ACK frame and (2) the third party STA calculates the EIFS=aSIFSTime+DIFS+NDP transmission time, where the NDP transmission time depends on the NDP type, in this example the NDP type is a 1 MHz NDP ACK with 560 μs duration . If the response BW indicator would otherwise be 0 (referring to an instance such as a 2 MHz response PPDU), then the recipient would have responded with an NDP ACK of 240 μs, and similarly, the third party STA would have accounted for this value (240 μs) Calculate the corresponding EIFS. In another embodiment, the one (or more) reserved bits of the service field may be used to indicate additional control information to the target recipient of the PPDU (additional control information otherwise would be included in the MAC header of the PPDU Or in the PLCP header), this additional control information enables additional MAC or PHY features or functionality.

In one embodiment, based on the response BW indicator, the transmitter may determine the transmitter's aPHY-RX-start-delay parameter based on the desired response PPDU (this parameter may be different for different types of PPDUs). As an example, as illustrated in FIG. 15, if the response BW indicator is set to indicate a desired PPDU of 1 MHz, the aPHY-RX-start-delay parameter may be set to approximately 600 [mu]s (eg, 606 [mu]s), which is for 1 MHz A PPDU response (such as a 1 MHz ACK or NDP ACK frame) is a suitable value. In another embodiment, the aPHY-RX-start-delay parameter may be relative to the frame normal control response frame frame for a 1 MHz NDP ACK frame (generally, for a 1 MHz NDP frame). Smaller value.

In another example, if the response BW indicator is set to the desired PPDU indicating ≧ 2 MHz, the aPHY-RX-start-delay parameter can be set to approximately 280 μs (eg, 286 μs), which responds to a MHz 2 MHz PPDU (such as , ACK or NDP ACK frame) is a suitable value. In another embodiment, the aPHY-RX-start-delay parameter can be made for a 2 MHz NDP ACK frame (generally, for a 2 MHz NDP frame) relative to its normal control response frame counterpart. Smaller value.

In one embodiment, the transmitter and receiver may have previously agreed upon by negotiating or indicating operational capabilities in such settings (eg, by associating a request/response or by managing a message frame). For example, the bandwidth used for the response can be based on the S1G capability element.

In one embodiment, an ACK policy field that employs at least one bit may be added to the Frame Control Field (FCF) of the MAC header. Such an ACK policy field may have similar functionality to the EOF bit in the MPDU delimiter. As an example, the 1-bit ACK policy field in the FCF of the received frame can be set to 0 to indicate to the target recipient that no confirmation of the received frame is requested. Similarly, setting the value of the ACK policy field bit to 1 may indicate that the request is acknowledged for the received frame. In general, the ACK policy field in the FCF can be used to indicate a different ACK policy along with the ACK indicator field and the aggregate bit in the SIG field. As an example, if the aggregate bit is set to 1 and the ACK policy of the FCF is set to 1, the receiver interprets the combination as a block Ack policy. For example, the receiver may record the status of the received frame and may not send an acknowledgment if the ACK indication field in the SIG field indicates "no response". Similar rules as described above and can be applied to this new Instructions. As an additional example, if the ACK indicator field has a value indicating "NDP Response", if the aggregation bit is set to 1 and if the ACK policy bit is set to 1, the equivalent ACK policy that the target receiver will follow may be "Implicit BAR", this may require a response from the NDP BA after the SIFS time of the initiating frame (received frame) (or a normal BA if the ACK indicates the normal control response frame is specified).

In some cases, the following options may also exist: For a VHT single MPDU whose ACK indication is set to an NDP response, the recipient may send a BA with an "Extended ACK ID". For example, the recipient can extend the general ACK ID using the BA bit map bits of the partial FCS set to the request frame. This approach effectively adds extra bit map size bits to the ACK ID (note that in this case, there may be no duration or more information, etc.). According to some aspects, one or more bits (eg, a single bit in an MPDU delimiter) may be used to indicate a BA policy or no ACK policy (reserved bits). According to some aspects, as described above, one or more bits in the frame control field (FCF) of the request frame can be used to indicate an ACK policy. According to some aspects, one bit can be used to indicate an ACK policy. According to some aspects, the ACK policy bit may be the LSB (Least Significant Bit) bit of the type field of the frame control field, or the ACK policy bit may be located in the same type field as the frame control field. s position. In the latter case, the type field can be reduced by 1 bit (eg, from 4 bits to 3 bits) to release a bit that can be used to indicate an ACK policy for the frame.

In some cases, the ACK policy bit in the FCF may function separately (or synergistically) from the ACK indication provided via the bits in the SIG field. ACK The policy bit identifies the acknowledgment policy that is followed at the time of MPDU delivery. The ACK policy bit (or set of bits) can generally be located anywhere in the FCF. Figure 16 illustrates an example format of an FCF where the ACK policy bit is the last bit in the FCF. The table in Figure 17 indicates how such an ACK policy bit can be interpreted.

In some embodiments, the response type is determined based on the Ack policy field in the PPDU-initiated QoS control field and/or the frame control field, and the frame format of the response may be based on a response indication (also known as ACK). Indicate) the TX vector parameter to determine. In other words, the Ack policy field determines the Ack policy indicated by the transmitter, and the response indication determines the response type (normal ACK frame instead of NDP ACK frame, etc.).

For some aspects, multi-user MIMO (MU-MIMO) can be used to send PPDUs to multiple recipients. In this case, the initial portion of the PLCP header is omnidirectional and specifies a group identifier (group ID) that identifies which STA group is addressed as part of the MU PPDU and the number of space-time streams for each receiver ( Nsts). The STAs in the group have an order called a user location. The user location determines which of the Nsts values in the Nsts field of the omnidirectional portion of the PLCP header. The Nsts for a particular user may be 0, which means that the MU PPDU will not contain PPDUs destined for that user in the group. For MU PPDUs, the ACK indication in the PLCP header is applied to the first user with non-zero Nsts. Other users with non-zero Nsts implicitly have a no response ACK indication.

In some cases, a PPDU transmitted to multiple recipients using MU-MIMO may include a 2-bit ACK policy for each user specifying a per-user ACK policy in the SIG-B field of the PLCP header. The encoding of the ACK policy field is in the QoS control field located in the normal IEEE 802.11 MAC header. The ACK policy subfields are similar or identical, for example, for each no Ack, BA policy, normal ACK or implicit block Ack request (BAR), no explicit acknowledgment or PMPPAck, and block Ack.

Figure 13 illustrates an example mapping of bits for ACK indication provided in the SIG-A field of MU-MIMO. Generally, for MU-MIMO, each user can have an indication of an ACK policy, so only one user (referred to herein as the primary user) can respond, while other users suppress the response. Only the primary user can inherit the ACK policy indicated in the SIG-A field.

There are a number of options that indicate which user is the primary user. One option is to have the user at position 0 as the primary user, as mentioned above. Another option is to use the single ("primary user") bit in the SIG-B field to indicate the primary user. For example, the primary user bit in the primary user's SIG-B field can be set to 1, while the other user's primary user bit is set to zero. As mentioned above, the primary user is the only user who can inherit the ACK policy from the SIG-A field. All other users may have an ACK indication of 0 (ie, no response).

19 is a flow diagram of an example operation 1900 for wireless communication in accordance with certain aspects of the present disclosure. Operation 1900 can be performed by a first device, such as a transmitting station (eg, an AP). The operation may begin at 1902, where the first device transmits a Medium Access Control (MAC) Protocol Data Unit (MPDU) to a second device (e.g., a STA). At 1904, the first device can set at least one bit in a Frame Control Field (FCF) in the MAC header of the MPDU to indicate an acknowledgment (ACK) type expected from the second device in response to the transmitted MPDU. .

According to some aspects, the at least one bit in the FCF indicates whether a normal ACK or a block from the second device is expected in response to the transmitted MPDU ACK. For some aspects, operation 1900 can further involve at least one bit in a PLCP header of the first device setup PPDU (including the MPDU) to indicate an ACK type expected from the second device in response to the transmitted MPDU. In this case, the at least one bit in the PLCP header may include at least two bits set to indicate a value of at least one of: (1) no response is expected, (2) an NDP response is expected, (3) Expect a normal response, or (4) expect a long response.

20 is a flow diagram of an example operation 2000 for wireless communication in accordance with certain aspects of the present disclosure. Operation 2000 can be performed by a receiving device, such as a STA. Operation 2000 can begin at 2002 where the device receives the FCF in the MAC header of the MPDU. In 2004, the device may determine the type of ACK to be sent for the MPDU based on at least one bit in the FCF. According to some aspects, operation 2000 can further include the device transmitting the ACK of the type based on the decision at 2004.

According to some aspects, the at least one bit in the FCF indicates whether a normal ACK or a block ACK is to be transmitted. For some aspects, the decision at 2004 may involve determining the type of ACK to send based on at least one bit in the PLCP header of the PPDU (including the MPDU). In this case, the at least one bit in the PLCP header may include at least two bits set to indicate a value of: (1) no response is to be sent, (2) NDP response is to be sent (3) A normal response is to be sent, or (4) a long response is to be sent.

While the above description has focused on the calculation of EIFS values, those skilled in the art will appreciate that the rules presented herein can be applied to or assist in following different deferral mechanisms, such as Network Allocation Vector (NAV) or Response Indication Delay (RID). Third party station (STA). According to some aspects, you can press this article about EIFS A similar (or identical) way of describing the RID is described. This effectively provides a postponement mechanism based on the PLCP header and different mechanisms based on frame check sequence (FCS) failure.

In some cases, the device may wish to decide what ACK type is indicated based on the type of NDP MAC frame. An example indication is illustrated in FIG. In addition to the illustrated indications, combinations of the indicated indications (eg, for NDP clear transmission (CTS) or NDP power saving (PS)-polling) may also be supported.

The RID can be considered as a virtual carrier sense (CS) mechanism for S1G STAs. The mechanism for setting and resetting the RID is described below. For non-S1G STAs, the CS mechanism can combine the NAV state and the transmitter state of the STA with the entity CS to determine the busy/idle state of the media. For S1G STAs, the CS mechanism can combine the NAV state, the RID state, and the STA's transmitter state with the entity CS to determine the busy/idle state of the media. NAV and RID can be treated as counters, and the counter counts down to zero at a uniform rate. For non-S1G STAs, when the NAV counter is 0, the virtual CS indicates that the media is idle; when it is non-zero, the indication is busy. For S1G STAs, when both the NAV and RID counters are zero, the virtual CS indication is media idle; when either of the NAV and RID counters is non-zero, the indication is busy. When the STA is transmitting, the media is most likely to be determined to be busy.

In order to set and reset the RID for the S1G STA, the RID counter is most likely to be set to 0 each time a PHY-RXSTART (PHY-Receive Start) indication primitive is received. S1G that receives a frame whose PHY-RXEND indication primitive does not contain an error (or provides an RX vector (RXVECTOR) parameter) The STA may be most likely based on the PREMBLE_TYPE of the RX vector parameter of the received frame, the RESPONSE_INDICATION, the AGGREGATION, the MCS, and the CH_BANDWIDTH (channel bandwidth) (as in IEEE 802.11ah). The value of the) is used to update the RID counter of the S1G STA. For some aspects, if the S1G STA is the target recipient of any frame within the received PSDU or if the current PPDU includes at least one MPDU with a valid duration field, the S1G STA may not update the RID counter of the S1G STA. The RID counter is most likely to be updated at the time the PHY-RXEND indication primitive is issued for the current PPDU.

If the value of the response indication is a long response, the RID counter can be set to MaxPPDU transmission time + aSIFSTime, where the MaxPPDU transmission time is the maximum duration in microseconds of the S1G PPDU, as defined in IEEE 802.11ah. If the value of the response indication is a normal response, the RID counter can be set to the normal transmission time + aSIFSTime, wherein the normal transmission time is calculated based on the RX vector parameter preamble signal type, aggregation, MCS, and channel bandwidth according to IEEE 802.11ah. of. If the value of the response indication is an NDP response, the RID counter can be set to NDP transmission time + aSIFSTime, wherein the NDP transmission time is calculated based on the RX vector parameter preamble signal type and is equal to the NDP MAC frame for transmitting 1 MHz. (if the preamble signal type is 1MHz preamble signal) or ≧ 2MHz NDP MAC frame (if the preamble signal type is ≧2MHz short/long preamble signal) in microseconds. If the value of the response indication is no response, the RID counter can be set to zero.

If the received PPDU is an NDP MAC frame, the S1G STA is most likely to be available. The RID counter can be set by using the response indication value according to the NDP MAC frame type as described in the table of FIG. 18, and FIG. 18 illustrates an equivalent response indication. The NDP MAC frame, including the calendar field that sets the NAV, may have an "no response" equivalent response indication to reset the RID counter because such a frame sets the NAV anyway.

As mentioned above, in some cases, the techniques described herein can be applied to various delay mechanisms, such as Network Allocation Vector (NAV), EIFS, or Response Indication Delay (RID). In order to set a counter for any of these mechanisms, the STA may signal other STAs to the new counter value. As an example of a situation with respect to RID, the STA may distribute the RID information to protect the response frame after the desired SIFS time of the frame initiating the response. In order to do so, according to certain aspects of the present disclosure, the STA may set according to a response indication (also referred to as an ACK indication) parameter in a parameter set (eg, a TX vector parameter) received from a MAC sublayer for each PPDU. One or more bits. FIG. 21 illustrates example values of response indication parameters that can be set based on the type of response that the S1G STA desires to receive. The RX vector sent to the MAC sublayer may have a corresponding value in the response indication parameter.

22 is a flow diagram of an example operation 2200 for wireless communication in accordance with certain aspects of the present disclosure. Operation 2200 can be performed by a third party receiving device (eg, an STA that is not the target recipient). Operation 2200 can begin at 2202, where the device receives a PPDU that is not intended to be sent to the device. At 2204, the apparatus can determine a delay time (for accessing wireless media) based on at least one bit in a PLCP header of the PPDU, wherein the at least one bit indicates a target recipient to be sent by the PPDU Response type.

According to some aspects, operation 2200 can further include the device being based on The determined delay time is set to set the response indication delay (RID) counter. For some aspects, the apparatus can determine a carrier sense (CS) indication based at least in part on the value of the RID counter and the value of the Network Allocation Vector (NAV) counter. For some aspects, the RID counter is updated when a PHY-RXEND indication primitive is issued for the received PPDU. For other aspects, the RID counter is updated at the time when it is expected that the PHY-RXEND indication primitive will be issued for the received PPDU.

According to some aspects, the at least one bit in the PLCP header includes at least two values set to indicate that no response is to be sent, an NDP response is to be sent, a normal response is to be sent, or a long response is to be sent. Bit. For some aspects, the delay time is determined to be zero if the at least two bits indicate that no response is to be sent. For other aspects, if the at least two bits indicate that a long response is to be sent, the delay time is determined to include the maximum PPDU duration plus inter-frame space (SIFS). For some aspects, the decision to delay the time at 2204 is further based on at least one of a preamble signal type, an aggregate bit in the PLCP header, a channel bandwidth, or a modulation and coding scheme (MCS). For some aspects, if the at least two bits indicate that a normal response is to be sent, the delay time can be determined to include the normal transmission time plus SIFS. In this case, the normal transmission time may be calculated based on at least one of a preamble signal type, an aggregate bit in the PLCP header, a channel bandwidth, or an MCS. For some aspects, if the at least two bits indicate that no response is to be sent, then at 2204 the decision to delay is based on the preamble signal type. In this case, the delay time can be determined to include the NDP transmission time plus SIFS, where the NDP transmission time is equal to the time in microseconds used to transmit the following frames: (A) if the preamble signal type is 1 MHz preamble Signal, 1MHz NDP Media Access Control (MAC) frame Or (B) if the preamble signal type is ≧2MHz short/long preamble signal, then ≧2MHz NDP MAC frame.

According to some aspects, the PPDU is an Empty Data Encapsulation (NDP) Media Access Control (MAC) frame. In this case, the decision to delay the time at 2204 may be based on the at least one bit indicating the type of response and based on the type of NDP MAC frame.

The various operations of the methods described above can be performed by any suitable means capable of performing the corresponding functions. Such means may include various hardware and/or software components and/or modules including, but not limited to, circuits, special application integrated circuits (ASICs) or processors. In general, where there are operations illustrated in the figures, such operations may have corresponding pairing means functional elements with similar numbers. For example, operations 700 and 800 illustrated in Figures 7 and 8 correspond to means 700A and 800A illustrated in Figures 7A and 8A, respectively. Similarly, operations 1900 and 2000 illustrated in Figures 19 and 20 correspond to means 1900A and 2000A illustrated in Figures 19A and 20A, respectively. Similarly, operation 2200 illustrated in Figure 22 corresponds to means 2200A illustrated in Figure 22A.

For example, the means for transmitting may include the transmitter (e.g., transmitter unit 222) and/or antenna 224 of the access point 110 illustrated in FIG. 2, the transmission of the user terminal 120 illustrated in FIG. (e.g., transmitter unit 254) and/or antenna 252 or transmitter 310 and/or antenna 316 illustrated in FIG. Means for receiving may include a receiver (eg, receiver unit 222) and/or antenna 224 of access point 110 illustrated in FIG. 2, a receiver of user terminal 120 illustrated in FIG. 2 (eg, Receiver unit 254) and/or antenna 252 or receiver 312 and/or antenna 316 illustrated in FIG. Means for processing, for setting Means, means for selection, means for interpretation, means for inclusion, means for (individual) indication, means for encoding, means for providing, means for generating and/or The means for (individual) decision may include a processing system that may include one or more processors, such as RX data processor 242, TX data processor 210, and/or access point 110 illustrated in FIG. Or controller 230, RX data processor 270, TX data processor 288 and/or controller 280 of user terminal 120 illustrated in FIG. 2, or processor 304 and/or DSP illustrated in FIG. 320.

According to some aspects, such means may be implemented by a processing system configured to perform various functions by implementing various algorithms (eg, by hardware or by executing software instructions). For example, an algorithm for setting a bit to indicate a type of response desired for transmission (eg, an MPDU or PPDU) may receive as input a transmission type and conditional input to be sent, which may or may not be determined for the transmission What kind of response type is expected as a consideration. Based on this input, the algorithm can set the appropriate bits to indicate the desired type of response. Similarly, an algorithm for determining which type of response is desired based on the bits in the received transmission can receive (as input) the bit and decide which type of response to expect based on the value of the bit.

As used herein, the term "decision" encompasses a wide variety of actions. For example, a "decision" may include calculations, calculations, processing, derivation, research, inspection (eg, viewing in a table, database, or other data structure), detection, and the like. Moreover, "decision" may include receiving (eg, receiving information), accessing (eg, accessing data in memory), and the like. Moreover, "decision" may also include analysis, selection, selection, establishment, and the like.

As used herein, a phrase referring to "at least one of" a list of items refers to any combination of the items, including the individual members. As an example, "at least one of a , b or c " is intended to cover: a , b , c , ab , ac , bc, and abc .

Various illustrative logic blocks, modules, and circuits described in connection with the present disclosure may be implemented by general purpose processors, digital signal processors (DSPs), special application integrated circuits (ASICs), field programmable gate arrays (FPGAs), or other programmable Design logic devices (PLDs), individual gate or transistor logic, individual hardware components, or any combination thereof designed to perform the functions described herein are implemented or executed. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any commercially available processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

The steps of the method or algorithm described in connection with the present invention can be implemented directly in hardware or in a software module executed by a processor or in a combination of the two. The software modules can reside in any form of storage medium known in the art. Some examples of storage media that may be used include random access memory (RAM), read only memory (ROM), flash memory, EPROM memory, EEPROM memory, scratchpad, hard disk, removable magnetic Disc, CD-ROM, and more. The software module can include a single instruction or a majority of instructions, and can be distributed over several different code segments, distributed among different programs, and distributed across multiple storage media. The storage medium can be coupled to the processor such that the processor can read and write information from/to the storage medium. Alternatively, the storage medium can be integrated into the processor.

The methods disclosed herein comprise one or more steps or actions for achieving the methods described. The method steps and/or actions may be interchanged without departing from the scope of the claimed invention. In other words, the order and/or use of specific steps and/or actions may be modified without departing from the scope of the claims.

The functions described can be implemented in hardware, software, firmware, or any combination of the above. If implemented in hardware, the example hardware settings can include a processing system in the wireless node. The processing system can be implemented with a bus architecture. The bus bar can include any number of interconnect bus bars and bridges depending on the particular application of the processing system and overall design constraints. The bus bar connects various circuits including the processor, machine readable media, and bus interface. The bus interface can be used to connect a network interface card or the like to a processing system via a bus bar. The network interface card can be used to implement the signal processing function of the PHY layer. In the case of user terminal 120 (see FIG. 1), a user interface (eg, a keypad, display, mouse, joystick, etc.) can also be connected to the busbar. The busbars can also be coupled to various other circuits, such as timing sources, peripherals, voltage regulators, power management circuits, and the like, which are well known in the art and will therefore not be further described.

The processor is responsible for managing the bus and general processing, including executing software stored on machine readable media. The processor can be implemented with one or more general purpose and/or special purpose processors. Examples include microprocessors, microcontrollers, DSP processors, and other circuitry that can execute software. Software should be interpreted broadly to mean any combination of instructions, materials or instructions, materials, whether referred to as software, firmware, media, microcode, hardware description language, or other . As an example, the machine readable medium may include RAM (random access memory), flash memory, ROM (read only memory), PROM (programmable read only memory), EPROM (erasable program) Design read-only memory), EEPROM (Electrically Erasable Programmable Read Only Memory), scratchpad, diskette, compact disc, hard drive or any other suitable storage medium or any combination thereof. Machine readable media can be implemented in a computer program product. The computer program product can include packaging materials.

In a hardware implementation, the machine readable medium can be part of the processing system separate from the processor. However, as will be readily appreciated by those skilled in the art, any portion of the machine readable medium or machine readable medium can be external to the processing system. By way of example, a machine readable medium can include a transmission line, a carrier modulated by the data, and/or a computer product separate from the wireless node, all of which can be accessed by the processor via the bus interface. Alternatively or additionally, any portion of the machine readable medium or machine readable medium may be integrated into the processor, such as cache memory and/or general purpose register files.

The processing system can be configured as a general purpose processing system having one or more microprocessors providing processor functionality and external memory providing at least a portion of machine readable media, a microprocessor and external memory The body is connected to other supporting circuits via an external bus structure. Alternatively, the processing system may use an ASIC with a processor integrated in a single chip, a bus interface, a user interface (in the case of an access terminal), a support circuitry, and at least a portion of machine readable media (special Apply integrated circuit), or use one or more FPGAs (field programmable gate array) Columns, PLDs (programmable logic devices), controllers, state machines, gated logic, individual hardware components or any other suitable circuitry or any combination of circuits capable of performing the various functionalities described throughout this document to realise. Those skilled in the art will recognize how best to implement the functions described with respect to the processing system, depending on the particular application and the overall design constraints imposed on the overall system.

Machine readable media can include several software modules. The software modules include instructions that, when executed by the processor, cause the processing system to perform various functions. The software modules can include a transmission module and a receiving module. Each software module can reside in a single storage device or be distributed across multiple storage devices. As an example, when a trigger event occurs, the software module can be loaded into the RAM from the hard drive. During execution of the software module, the processor can load some instructions into the cache to increase access speed. One or more cache memory lines can then be loaded into the general purpose scratchpad file for execution by the processor. In the following discussion of the functionality of a software module, it will be appreciated that such functionality is implemented by the processor when the processor executes instructions from the software module.

If implemented in software, each function can be stored as one or more instructions or codes on a computer readable medium or on a computer readable medium. Computer readable media includes both computer storage media and communication media, including any media that facilitates the transfer of a computer program from one location to another. The storage medium can be any available media that can be accessed by the computer. By way of example and not limitation, such computer readable medium may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, disk storage or other magnetic storage device or can be used to carry or store instructions or data structures. Any other medium that expects code and can be accessed by a computer. Any connection is also properly referred to as computer readable media. For example, if the software is transmitted from a web site, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared (IR), radio, and microwave. The coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies (such as infrared, radio, and microwave) are included in the definition of the media. As used herein, a disk (Disk) and disc (Disc), includes compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray ^® disc where disks (Disk) magnetically often The data is reproduced, and the disc uses laser to optically reproduce the data. Thus, in some aspects, computer readable media can include non-transitory computer readable media (eg, tangible media). Additionally, for other aspects, computer readable media can include transient computer readable media (eg, signals). The above combinations should be included in the scope of computer readable media.

Accordingly, certain aspects may include a computer program product for performing the operations provided herein. For example, such computer program products can include computer readable media having stored thereon (and/or encoded) instructions executable by one or more processors to perform the operations described herein. For some aspects, computer program products may include packaging materials.

In addition, it should be appreciated that modules and/or other suitable means for performing the methods and techniques described herein can be downloaded and/or otherwise obtained by a user terminal and/or base station where applicable. For example, such a device can be coupled to a server to facilitate the transfer of means for performing the methods described herein. Alternatively, the various methods described herein can be via a storage device (eg, RAM, ROM, physical storage medium such as a compact disc (CD) or floppy disk) The device is provided such that upon coupling or providing the storage device to the user terminal and/or the base station, the device can obtain various methods. Moreover, any other suitable technique suitable for providing the methods and techniques described herein to a device can be utilized.

It should be understood that the scope of the patent application is not limited to the precise arrangements and elements described above. Various modifications, changes and variations can be made in the arrangement, operation and details of the methods and apparatus described above without departing from the scope of the claims.

2200‧‧‧ operation

2202‧‧‧Steps

2204‧‧‧Steps

Claims (32)

An apparatus for wireless communication, comprising: a receiver configured to receive a Physical Layer Convergence Protocol (PLCP) Protocol Data Unit (PPDU) that is not intended to be sent to the apparatus; and a processing system, the processing The system is configured to: determine a delay time based on at least one bit in a PLCP header of the PPDU, wherein the at least one bit indicates a type of response to be sent by a target recipient of the PPDU; The delay time determined by this is to delay the transmission of a signal. The apparatus of claim 1, wherein the processing system is further configured to set a response indication delay (RID) counter based on the determined delay time. The apparatus of claim 2, wherein the RID counter is updated at a time when it is expected to issue a PHY-RXEND indication primitive for the received PPDU. The apparatus of claim 1, wherein the at least one bit in the PLCP header is set to indicate that no response is to be sent, a null data packet (NDP) response is to be sent, a normal response is to be sent, or A long response to at least two bits of a value to be sent. The device as recited in claim 4, wherein the processing system is configured to: Determining that the delay time is 0 if the at least two bits indicate that no response is to be sent; and determining that the delay time includes a maximum PPDU duration plus if the at least two bits indicate that the long response is to be sent A short inter-frame space (SIFS). The apparatus of claim 4, wherein the processing system is configured to determine that the delay time comprises a normal transmission time plus a short inter-frame space (SIFS if the at least two bits indicate that the normal response is to be transmitted) And wherein the normal transmission time is calculated based on at least one of a preamble signal type, an aggregation bit in the PLCP header, a channel bandwidth, or a modulation and coding scheme (MCS). The apparatus of claim 4, wherein the processing system is configured to determine the delay time based on a preamble signal type if the at least two bits indicate that the NDP response is to be sent. The apparatus of claim 7, wherein the processing system is configured to determine that the delay time comprises an NDP transmission time plus an inter-frame space (SIFS), and wherein the NDP transmission time is equal to for transmitting the following frame A time in microseconds: if the preamble signal type is a 1 MHz preamble signal, it is an NDP media access control (MAC) frame of 1 MHz; or if the preamble signal type is ≧2MHz, a short/ The long preamble signal is an NDPMAC frame of ≧2MHz. The apparatus of claim 1, wherein the processing system is further configured to be based on a preamble signal type, an aggregate bit in the PLCP header, a channel bandwidth, or a modulation and coding scheme (MCS) At least one of them decides the delay time. The apparatus of claim 1, wherein the PPDU comprises a null data packet (NDP) medium access control (MAC) frame, and wherein the processing system is further configured to determine the delay based on a type of the NDPMAC frame time. A method for wireless communication by a device, the method comprising the steps of: receiving a Physical Layer Convergence Protocol (PLCP) Protocol Data Unit (PPDU) that is not intended to be sent to the device; based on a PLCP header of the PPDU At least one bit determines a delay time, wherein the at least one bit indicates a type of response to be sent by a target recipient of the PPDU; and delays transmission of a signal based on the determined delay time. The method of claim 11, the method further comprising the step of setting a response indication delay (RID) counter based on the determined delay time. The method of claim 12, wherein the RID counter is updated at a time when it is expected to issue a PHY-RXEND indication primitive for the received PPDU. The method of claim 11, wherein the at least one bit in the PLCP header is set to indicate that no response is to be sent, a null data packet (NDP) response is to be sent, a normal response is to be sent, or A long response to at least two bits of the value to be sent. The method of claim 14, wherein: if the at least two bits indicate that no response is to be sent, the delay time is determined to be 0; and if the at least two bits indicate that the long response is to be sent, The delay time is then determined to include a maximum PPDU duration plus an inter-frame space (SIFS). The method of claim 14, wherein if the at least two bits indicate that the normal response is to be sent, the delay time is determined to include a normal transmission time plus a short inter-frame space (SIFS), and The normal transmission time is calculated based on at least one of a preamble signal type, an aggregation bit in the PLCP header, a channel bandwidth, or a modulation and coding scheme (MCS). The method of claim 14, wherein the at least two bits indicate the If the NDP response is to be sent, it is determined that the delay time is based on a preamble signal type. The method of claim 17, wherein the delay time is determined to include an NDP transmission time plus an inter-frame space (SIFS), and wherein the NDP transmission time is equal to one microsecond for transmitting the following frame One time: if the preamble signal type is a 1MHz preamble signal, it is a 1MHz NDP media access control (MAC) frame; or if the preamble signal type is ≧2MHz, a short/long preamble signal Then it is an NDPMAC frame of ≧2MHz. The method of claim 11, wherein determining the delay time is further based on at least one of a preamble signal type, an aggregate bit in the PLCP header, a channel bandwidth, or a modulation and coding scheme (MCS). By. The method of claim 11, wherein the PPDU comprises a null data packet (NDP) medium access control (MAC) frame, and wherein determining the delay time is further based on a type of the NDPMAC frame. An apparatus for wireless communication, comprising: means for receiving a Physical Layer Convergence Protocol (PLCP) Protocol Data Unit (PPDU) that is not intended to be sent to the apparatus; for at least one of a PLCP header based on the PPDU a bit to determine a means of delaying the time, wherein the at least one bit indicates that the PPDU is to be a type of response sent by a target recipient; and means for delaying transmission of a signal based on the determined delay time. The apparatus as recited in claim 21, further comprising means for setting a response indication delay (RID) counter based on the determined delay time. The device as recited in claim 22, wherein the RID counter is updated at a time when it is expected to issue a PHY-RXEND indication primitive for the received PPDU. The device of claim 21, wherein the at least one bit in the PLCP header is set to indicate that no response is to be sent, a null data packet (NDP) response is to be sent, a normal response is to be sent, or A long response to at least two bits of the value to be sent. The device as recited in claim 24, wherein the means for determining is configured to: if the at least two bits indicate that no response is to be sent, determine that the delay time is 0; and if the at least two bits Instructing the long response to be sent, it is determined that the delay time includes a maximum PPDU duration plus an inter-frame space (SIFS). The device as recited in claim 24, wherein the means for determining is configured If the at least two bits indicate that the normal response is to be sent, determining that the delay time comprises a normal transmission time plus a short inter-frame space (SIFS), and wherein the normal transmission time is based on a preamble signal type Calculated by at least one of an aggregate bit, a channel bandwidth, or a modulation and coding scheme (MCS) in the PLCP header. The device as recited in claim 24, wherein the means for determining is configured to determine the delay time based on a preamble signal type if the at least two bits indicate that the NDP response is to be sent. The device as recited in claim 27, wherein the means for determining is configured to determine that the delay time comprises an NDP transmission time plus an inter-frame space (SIFS), and wherein the NDP transmission time is equal to for transmitting The time of the following frame in microseconds: if the preamble signal type is a 1 MHz preamble signal, then an NDP media access control (MAC) frame of 1 MHz; or if the preamble signal type is ≧2 MHz A short/long preamble signal is an NDPMAC frame of ≧2 MHz. The apparatus of claim 21, wherein the means for determining is further configured to be based on a preamble signal type, an aggregate bit in the PLCP header, a channel bandwidth, or a modulation and coding scheme (MCS) At least one of them determines the delay time. The device as recited in claim 21, wherein the PPDU includes an empty data packet (NDP) Medium Access Control (MAC) frame, and wherein the means for determining is further configured to determine the delay time based on a type of the NDPMAC frame. A computer program product comprising a computer readable medium for wireless communication by a device, the computer readable medium having instructions executable to: receive a physical layer that is not intended to be sent to the device a convergence agreement (PLCP) protocol data unit (PPDU); determining a delay time based on at least one bit in a PLCP header of the PPDU, wherein the at least one bit indicates that a target recipient is to be sent by the PPDU a type of response; and delaying the transmission of a signal based on the determined delay time. A wireless station comprising: at least one antenna; a receiver configured to receive, via the at least one antenna, a Physical Layer Convergence Protocol (PLCP) Protocol Data Unit (PPDU) that is not intended to be sent to the wireless station; A processing system configured to: determine a delay time based on at least one bit in a PLCP header of the PPDU, wherein the at least one bit indicates a target recipient to be sent by the PPDU a type of response; and delaying the transmission of a signal based on the determined delay time.