Communication method and system for joint downlink and uplink transmissions

In a communication method to communicate between an access point (AP) and first and second communication stations (STAs) can include calculating joint transmission information based on the first and the second STAs, establishing an uplink communication between the AP and the first STA; and establishing a downlink communication between the AP and the second STA jointly with the uplink communication between the AP and the first STA based on the joint transmission information.

BACKGROUND

Field

Aspects described herein generally relate to joint download and upload transmissions, including half-duplex and full-duplex environments.

DETAILED DESCRIPTION

As an overview, advancements in self-interference cancellation has enabled wireless devices to communicate in full-duplex (FD)—to transmit and receive simultaneously at the same frequency band. Due to strong transmission (Tx) echo, wireless devices can transmit and receive over orthogonal frequency/time resource. Advances in echo cancellation can now successfully suppress Tx echo, including by more than 120 dB, which allows wireless devices to decode received data even when the same frequency/time resource is used for transmission. Although the FD transmission capability can potentially double-up data throughput, it requires extensive media access control (MAC) protocol designs to maximize FD gain.

In exemplary aspects, the WiFi MAC protocol is configured to take advantage of FD capable devices, including in scenarios where a FD-capable WiFi access point (AP) communicates with legacy half-duplex (HD) WiFi stations (STAs) and/or where a HD WiFi AP communicates with a FD capable STA. For the sake of brevity, exemplary aspect will be described for FD-capable APs communicating with HD-capable STAs, but are not limited thereto and can also apply to FD-capable STAs communicating with HD-capable APs and/or HD-capable STAs, ad-hoc networks (e.g., STA to STA communications), relay networks such as WiFi Direct systems (e.g., AP communicates with an FD-STA, which forwards communications to another STA), and/or other configurations as would be understood by one of ordinary skill in the relevant arts.

In exemplary aspects, AP FD capability is exploited through simultaneous joint downlink (DL) and uplink (UL) transmission with a pair of STAs that include a DL STA and an UL STA, including procedures and triggering criteria to enable such joint DL-UL transmissions.

Further, in exemplary aspects, communication methods enable a FD AP to jointly schedule DL and UL transmission of half-duplex WiFi STAs without requiring WiFi standard changes and/or require the AP to be capable of pre-decoding a MAC-header before receiving the entire packet (e.g., before receiving frame check sequence (FCS)).

As described herein, the communication methods can include when the AP wins the channel contention (source-based) and when the STA wins the channel contention (destination-based). Further, exemplary criteria to trigger joint DL-UL transmission procedures to increase joint DL-UL transmission probability are described.

For the purpose of this discussion, a source-based joint DL-UL transmission is when the AP wins the contention of channel access for DL transmission and triggers/polls another STA for FD-UL transmission. A destination-based joint DL-UL transmission is when the STA wins the contention of channel access for UL transmission and AP initiates a FD-DL transmission afterwards.

Exemplary aspects can include, for example: the utilization of block acknowledgement (ACK) to time-division multiplex (TDM) DL and UL ACK, which can enable a UL STA with a weaker link to the AP to transmit together with another DL transmission and avoid the general need to have the signal from the AP to the UL STA be sufficiently strong enough to combat DL STA to UL STA interference; the transmission of the FD-DL with a timing advance to protect the FD-DL preamble; and transmission of the UL in aggregated MAC protocol data unit (A-MPDU) and the trigger of the FD-DL transmission by the AP after detecting the first MPDU.

The present disclosure is directed to transmission procedures and pairing criteria for joint DL-UL transmission for various types of WiFi STAs, including: non-quality of service (non-QoS) STA (i.e., legacy STAs capable of Institute of Electrical and Electronics Engineers' (IEEE) 802.11a/b/g); QoS STAs (STAs that also include functions set forth in IEEE 802.11e); and high throughput (HT) STAs (i.e., STAs that also include IEEE 802.11n or more advanced 802.11 capabilities). The present disclosure is not limited to these example types of STAs and can be other types of STAs having different wireless capabilities as would be understood by one of ordinary skill in the relevant arts.

The capability of WiFi STAs are defined as follows:Non-QoS STA: The STA cannot support 802.11e but can support the 802.11a, 802.11b and/or 802.11g standard.QoS STA: In addition to 802.11a, 802.11b and/or 802.11g, the STA can also support the 802.11e standard.High throughput (HT) STA: In addition to 802.11a, 802.11b and/or 802.11g, the STA can also support 802.11n and 802.11e standard. The HT STA is also a QoS STA. In one or exemplary aspects, a HT STA can also support more advanced 802.11 standard(s), such as the 802.11ac.

Exemplary aspects can include:Block Acknowledgment (ACK) (BlockACK) for FD-DL transmission of QoS STAs to avoid Acknowledgement (ACK) collision.Trigger FD-DL transmission after decoding first UL A-MPDU sub-frame of UL A-MPDU for UL QoS STA.Start FD-DL transmission before (e.g., several micro-seconds) expected FD-UL transmission to improve FD-DL preamble detection success rate.Adopt Hybrid coordination function (HCF) controlled channel access (HCCA) for QoS STA to enable source-based joint DL-UL transmission.Adopt Point coordination function (PCF) for non-QoS CF-pollable STA to enable source-based joint DL-UL transmission.

FIG. 1illustrates an example communication environment100that includes a radio access network (RAN) and a core network. The RAN includes a wireless access point (AP)120and two or more wireless stations (STAs)140. The core network includes backhaul communication network105that is communicatively coupled to the AP120. The backhaul communication network105can include one or more well-known communication components—such as one or more network switches, one or more network gateways, and/or one or more servers. The backhaul communication network105can include one or more devices and/or components configured to exchange data with one or more other devices and/or components via one or more wired and/or wireless communications protocols. In exemplary aspects, the AP120communicates with one or more service providers and/or one or more other APs120via the backhaul communication network105. In an exemplary aspect, the backhaul communication network105is an internet protocol (IP) backhaul network.

In an exemplary aspect, the AP120can support one or more wireless communication protocols including, for example, wireless local access networks (WLAN) conforming to Institute of Electrical and Electronics Engineers' (IEEE) 802.11 Wi-Fi specification. In this example, the AP120can be referred to as a WLAN or WiFi Access Point (AP).

The AP120and STAs140are not limited to IEEE 802.11 protocols, and the AP120and STA140can support one or more other protocols in addition to (or in the alternative to) the IEEE 802.11 standards described herein as would be understood by one of ordinary skill in the relevant arts. Further, the number of APs120, mobile devices140, and/or networks105are not limited to the exemplary quantities illustrated inFIG. 1, and the communication environment100can include any number of the various components as would be understood by one of ordinary skill in the relevant art(s).

In operation, the STA140can be configured to wirelessly communicate with the AP120. For example, the STA140receives signals on one or more downlink (DL) channels and transmits signals to the AP120on one or more respective uplink (UL) channels. As illustrated inFIG. 1, in an exemplary aspect, the AP120is a full-duplex (FD) capable AP and the STAs140are half-duplex (HD) capable STAs, where the FD AP120is configured to jointly schedule DL and UL transmission with HD STAs140. Although examples are described that include a FD AP to HD STA relationship, it should be appreciated that the converse is also considered in the present disclosure, where the AP120is a HD AP while the STAs140are FD STAs.

In an exemplary aspect, the AP120and/or STAs140includes processor circuitry that is configured to control the corresponding device to communicate via one or more wireless technologies. The AP120and the STAs140can be configured to support HD and/or FD transmissions. The STAs140and the AP120can each include one or more transceivers configured to transmit and/or receive wireless communications via one or more wireless technologies within the communication environment100.

Examples of the STA140include (but are not limited to) a mobile computing device—such as a laptop computer, a tablet computer, a mobile telephone or smartphone, a “phablet,” a personal digital assistant (PDA), and mobile media player; an internet of things (IOT) device, and a wearable computing device—such as a computerized wrist watch or “smart” watch, and computerized eyeglasses. In one or more aspects of the present disclosure, the STA140may be a stationary device, including, for example, a stationary computing device—such as a personal computer (PC), a desktop computer, a computerized kiosk, and an automotive/aeronautical/maritime in-dash computer terminal, and/or a smart device/appliance—such as, for example, smart lighting device, smart door lock, smart home security system, smart refrigerator, etc.

FIG. 2illustrates an exemplary aspect of the access point (AP)120. For example, the AP120can include one or more transceivers200and a network interface280, each communicatively coupled to controller240. In an exemplary aspect, the AP120is a FD-capable WiFi AP configured to jointly communicate with two or more half-duplex (HD) WiFi stations (STAs) such as STAs140. For example, the FD AP120is configured to perform concurrent/simultaneous joint downlink (DL) and uplink (UL) transmission with a pair of STAs140, where one STA140is a DL STA and another STA140is an UL STA. The AP120is configured to jointly schedule DL and UL transmission of half-duplex WiFi STAs140without requiring WiFi standard changes and/or pre-decoding a MAC-header before receiving the entire packet (e.g., before receiving frame check sequence (FCS)).

The transceiver200includes processor circuitry that is configured to transmit and/or receive wireless communications via one or more wireless technologies within the communication environment100. For example, the transceiver200can include one or more transmitters210and one or more receivers220that configured to transmit and receive wireless communications, respectively, via one or more antennas230. In an exemplary For example, the transceiver200can include a transmitter210and receiver220that are configured for transmitting and receiving IEEE 802.11 communications via one or more antennas235.

In an exemplary aspect, the transceiver200can be configured to support one or more wireless communication protocols including, for example, wireless local access networks (WLAN) conforming to the IEEE 802.11 Wi-Fi specification. One of ordinary skill in the relevant art(s) will understand that the transceiver200is not limited to IEEE 802.11 communications, and can be configured for communications that conform to one or more other protocols in addition (or in the alternative) to the IEEE 802.11 communications. In exemplary aspects where the AP120includes two or more transceivers200, the transceivers200can be configured to communicate using the same or different communication protocols/standards.

Those skilled in the relevant art(s) will recognize that the transceiver200can also include (but is not limited to) a digital signal processer (DSP), modulator and/or demodulator, a digital-to-analog converter (DAC) and/or an analog-to-digital converter (ADC), and/or a frequency converter (including mixers, local oscillators, and filters) to provide some examples. Further, those skilled in the relevant art(s) will recognize that the antenna230may include an integer array of antennas, and that the antenna230may be capable of both transmitting and receiving wireless communication signals. For example, the AP120can be configured for wireless communication utilizing a Multiple-input Multiple-output (MIMO) configuration.

The network interface280includes processor circuitry that is configured to transmit and/or receive communications via one or more wired technologies to/from the backhaul communication network105. Those skilled in the relevant art(s) will recognize that the network interface280can also include (but is not limited to) a digital signal processer (DSP), modulator and/or demodulator, a digital-to-analog converter (DAC) and/or an analog-to-digital converter (ADC), and/or a frequency converter (including mixers, local oscillators, and filters) to provide some examples. Further, those skilled in the relevant art(s) will understand that the network interface280is not limited to wired communication technologies and can be configured for communications that conform to one or more well-known wireless technologies in addition to, or alternatively to, one or more well-known wired technologies.

The controller240can include processor circuitry250that is configured to carry out instructions to perform arithmetical, logical, and/or input/output (I/O) operations of the AP120, and/or one or more components of the AP120such as the transceiver200and/or network interface280. The processor circuitry250can be configured control the operation of the transceiver200—including, for example, transmitting and/or receiving of wireless communications via the transceiver200, and/or perform one or more baseband processing functions (e.g., media access control (MAC), encoding/decoding, modulation/demodulation, data symbol mapping, error correction, etc.); and/or to the operation of the network interface280including, for example, transmitting and/or receiving of wired and/or wireless communications via the network interface280, and/or perform one or more baseband processing functions (e.g., media access control (MAC), encoding/decoding, modulation/demodulation, data symbol mapping, error correction, etc.).

The controller240can further include a memory260that stores data and/or instructions, where when the instructions are executed by the processor circuitry250, controls the processor circuitry250to perform the functions described herein. In an exemplary aspect, the memory260stores (SINR), time alignment and/or efficiency criteria. The memory260can be any well-known volatile and/or non-volatile memory, including, for example, read-only memory (ROM), random access memory (RAM), flash memory, a magnetic storage media, an optical disc, erasable programmable read only memory (EPROM), and programmable read only memory (PROM). The memory260can be non-removable, removable, or a combination of both.

As described in more detail below, in exemplary aspects, the controller240is configured to perform FD-capable communications. The controller240can be configured to control the AP120to communicate with two or more HD WiFi STAs such as STAs140. In an exemplary aspect, the controller240is configured to perform simultaneous joint DL and UL transmission via the transceiver200with a pair of STAs140, where one STA140is a DL STA and another STA140is an UL STA. The controller240is configured to jointly schedule DL and UL transmission of half-duplex WiFi STAs140without requiring WiFi standard changes and/or pre-decoding a MAC-header before receiving the entire packet (e.g., before receiving frame check sequence (FCS)). Operations of the controller240according to exemplary aspects are described with reference toFIGS. 4A-12below.

FIG. 3illustrates an exemplary aspect of a STA140. The STA140can include controller340communicatively coupled to one or more transceivers300configured to transmit and/or receive wireless communications via one or more wireless technologies within the communication environment100.

The transceiver(s)300can each include processor circuitry that is configured for transmitting and/or receiving wireless communications conforming to one or more wireless protocols. For example, the transceiver300can include a transmitter310and receiver320that are configured for transmitting and receiving IEEE 802.11 communications via one or more antennas335.

The transceiver300can include a transmitter310and receiver320that are configured for transmitting and receiving IEEE 802.11 communications, respectively, via one or more antennas335. In this example, the transceiver300can be referred to as WLAN or Wi-Fi transceiver300. Those skilled in the relevant art(s) will understand that the transceiver300is not limited to WLAN communications, and can be configured for communications that conform to one or more other protocols in addition (or in the alternative) to the IEEE 802.11 communications.

In exemplary aspects, the transceiver(s)300can each include (but are not limited to) a digital signal processer (DSP), modulator and/or demodulator, a digital-to-analog converter (DAC) and/or an analog-to-digital converter (ADC), and/or a frequency converter (including mixers, local oscillators, and filters) that can be utilized in transmitting and/or receiving of wireless communications. Further, those skilled in the relevant art(s) will recognize that antenna335may include an integer array of antennas, and that the antennas may be capable of both transmitting and receiving wireless communication signals.

The controller340can include processor circuitry350that is configured to control the overall operation of the STA140, such as the operation of the transceiver300—including, for example, transmitting and/or receiving of wireless communications via the transceivers300, perform one or more baseband processing functions (e.g., media access control (MAC), encoding/decoding, modulation/demodulation, data symbol mapping, error correction, etc.); perform one or more interference estimations; the running of one or more applications and/or operating systems; power management (e.g., battery control and monitoring); display settings; volume control; and/or user interactions via one or more user interfaces (e.g., keyboard, touchscreen display, microphone, speaker, etc.).

The controller340can further include a memory360that stores data and/or instructions, where when the instructions are executed by the processor circuitry350, controls the processor circuitry350to perform the functions described herein. In an exemplary aspect, the memory360can store (SINR), time alignment and/or efficiency criteria. The memory360can be any well-known volatile and/or non-volatile memory, and can be non-removable, removable, or a combination of both.

In an exemplary aspect, the STA140is a HD capable STA, and the processor circuitry350is configured to control the STA140to communication with a FD capable AP120. Although exemplary aspects are discussed for HD STA and FD AP configurations, the STA140can be configured for the converse operation (FD STA and HD AP/STA) when the STA is a FD STA communicating with a HD AP and/or a HD STA. The STA140can be one of a pair of STAs simultaneously communicating with the AP120, where one STA140is a DL STA and another STA140is an UL STA.

Destination-based joint DL-UL transmission operations and source-based joint DL-UL transmission operations are described with reference toFIGS. 4A to 12. In particular, destination-based joint DL-UL transmission operations are described with reference toFIGS. 4A to 8, while source-based joint DL-UL transmission operations are described with reference toFIGS. 9A to 12.

Exemplary aspects of both destination-based joint DL-UL transmission operations and source-based joint DL-UL transmission operations include Signal-to-interference-plus-noise ratio (SINR), time alignment and/or efficiency criteria to trigger joint DL-UL transmissions. In exemplary aspects, the operations can include BlockACK for FD-DL transmission to avoid ACK collision and/or using A-MPDU to enhance joint DL-UL transmission opportunities. In exemplary aspects where transmission procedures allow for FD-DL to start earlier than FD-UL, the FD-DL start time can be offset to protect preamble detection.

In one or more exemplary aspects, it can be assumed that a list of pair-able DL STAs for an UL STA and the corresponding FD-DL data rate are available at the AP. Procedures to identify pair-able DL-STA and UL-STA can include, for example, using past joint transmission success rates, sending test-purpose measurement packets, and/or one or more other operations as would be understood by one of ordinary skill in the art.

Example Destination-Based Joint DL-UL Transmission Operations

As described above, in destination-based joint DL-UL transmission, the STA wins the channel contention process and sends packet(s) to AP first. Upon detecting UL data from the STA, the FD-capable AP can send a DL packet to a pair-able DL STA.

In a destination-based joint DL-UL transmission operation in which the STA140transmits data directly without utilizing Request-to-Send (RTS)/Clear-to-send (CTS) protocols, the DL transmission can be triggered after the AP120successfully decodes the Destination Address (DA) field of the MAC header. In this example, the AP120may only trigger the FD-DL transmission after confirming the AP120is the targeted recipient of UL data (e.g., using the decoded DA field).

In an exemplary aspect, if the DL STA120can detect the PHY preamble of the UL transmission, the DL STA140will lock to the UL transmission and will not decode DL data from the AP120. In exemplary aspects of the present disclosure, one or more of the following conditions are satisfied:1. A link from the UL STA to the DL STA is sufficiently weak that the DL STA is unable to detect the UL preamble.2. The DL STA is configured to attempt to sync with another transmit signal after detecting that the recipient of current UL transmissions is not itself. In this case, the SINR requirement when the signal arrives after interference will be higher.3. The hardware for the DL STA is configured to detect the preamble of another transmission while receiving a packet. If the other transmission is stronger, the DL can sync to the new transmission and abort the previous reception process. In this example, the SINR requirement for preamble detection may be high.
In exemplary aspects, the AP120can be configured to schedule DL STAs140satisfying one of the above three conditions for FD-DL transmission.

In an exemplary aspect, the destination-based joint DL-UL transmission operations and source-based joint DL-UL transmission operations include Signal-to-interference-plus-noise ratio (SINR), time alignment and/or efficiency criteria to trigger joint DL-UL transmissions. For the purpose of this disclosure, each of these criteria are referred to as the baseline criteria for the corresponding type.

For example, various SINR conditions to trigger joint DL-UL transmission are shown below in Equations 1(a) to 1(e):

In an exemplary aspect, for timing alignment, the AP120can be configured to estimate the start time of UL-ACK after decoding the PHY header of the UL data.

In this example, the DL packet length is short enough to be completely transmitted before the start time of UL-ACK. In addition, the DL data transmission ensure DL ACK do not collide with UL data reception (e.g., in the IEEE 802.11 standard, after successfully reception of a frame requiring acknowledgement, transmission of the ACK frame shall commence after a short interframe space (SIFS) period, without regard to the busy/idle state of the medium). In an exemplary aspect, when the DL packet is so short that DL data transmission ends SIFS before the end of UL data transmission, dummy data is padded to the DL data to ensure no overlap between reception of the DL-ACK and the UL data.

In an exemplary aspect, with respect to the efficiency of the joint DL-UL transmission, where the communication system includes a pair-able DL-STA with packet size satisfying all the above constraints, scheduling the FD-DL is more efficient than transmissions using extra resource to send the DL packet in HD.

In exemplary aspects described below with reference toFIGS. 4A-12, the criteria to trigger joint DL-UL transmission is reduced. For example, the above criteria generally includes that the AP is capable of pre-decoding MAC header before the final FCS check; a higher SINR requirement to pre-decoding MAC header without final FCS checking than the SINR required to decode the whole packet (e.g., THMCSx,no FCS>THMCSxwhere x is the MCS mode used for UL data transmission); and a part of the UL-ACK having been interfered with by the DL-ACK. In this example, pair-able DL-UL STAs require not only

SAP→DLIUL→DL+N≥THMCSxDL,
but also

SAP→ULIDL→UL+N≥THMCS⁢⁢0
(i.e., the AUK is typically transmitted in MCS 0). Further, in cases where the transmit power of STAs are the same, both the signal strength from AP to DL STA and from AP to UL STA are to be considered when scheduling joint DL-UL transmission.

In exemplary aspects of the present disclosure, QoS STAs can be configured to relax the constraints above to increase joint DL-UL probability. Further, the initial joint DL-UL transmission can be offset to protect preamble detection.

Adoption of BlockACK for FD-DL Transmission with QoS DL STA

FIGS. 4A-4Cillustrate destination-based joint DL-UL transmission operations according to exemplary aspects of the present disclosure. In the exemplary aspect, the joint DL-UL transmissions can adopt BlockACK for the FD-DL transmission with a QoS DL STA.

In an exemplary aspect and with reference toFIG. 4A, the AP120can be configured to communicate with the DL STA140in a block transmission mode for a DL QoS STA140. For example, when the DL STA140is scheduled for joint transmission with another UL STA, each MPDU410for the FD-DL can have its ACK policy field set to Block ACK (BA). In this example, the DL ACK420can be delayed until the AP120sends out a Block ACK Request (BAR)415. The AP120can delay the BAR415until the completion of UL ACK425that acknowledges the data430. As a result, the UL ACK425can avoid intra-cell STA-to-STA interference. As illustrated, the transmission of the BlockAck420occurs after a short interframe space (SIFS) period. Similarly, the transmission of the ACK425occurs after a SIFS period.

With reference toFIG. 4B, a similar BlockACK procedure for an HT STA is illustrated. In an exemplary aspect, the BAR415can be replaced with transmitting another MPDU416having its ACK policy set to Normal ACK. In this example, DL STA will be triggered to transmit Block ACK420for all previously unacknowledged MPDUs410.

FIG. 4Cillustrates a BlockACK procedure according to an exemplary aspect that is similar to the operations shown inFIG. 4B. In this example, for an HT DL-STA140, the AP120may choose to aggregate MPDUs410more aggressively. As shown inFIG. 4C, once the AP120detects that the UL transmission ends and the on-going DL MPDU417cannot be finished within the SIFS period, the AP120can terminate transmission of last MPDU417immediately. The AP120can then retransmit the MPDU417with Normal ACK setting after UL-ACK425transmission as shown by the MPDU416. In an exemplary aspect, the BlockACK procedure ofFIG. 4Ccan used when the AP120is not aware of the UL transmission duration. If known, the situation in which the incomplete MPDU417will be avoided because the AP120will know that the DL MPDU417will not be able to finish in time.

In an exemplary aspect, the BlockACK procedures illustrated inFIGS. 4A-4Ccan be utilized to trigger joint DL-UL transmission. In this example, the transmission can be triggered when the SINR conditions in Equations 1(a) to 1(d) are satisfied. That is, different from the baseline transmission criteria above, the utilization of the BlockAck procedures reduces the SINR conditions for triggering the trigger joint DL-UL transmission and thereby increasing the availability of the AP120to perform such transmissions.

Further, for timing alignment, after decoding the PHY header of UL data, the AP120can estimate the start time of UL-ACK425. The AP120can schedule as many MPDUs410for FD-DL transmission so that the last MPDU411(FIGS. 4A and 4B) ends before the UL-ACK425start time. In this example, if less than one MPDU can be scheduled, the AP120can be configured to not trigger the FD-DL transmission. Advantageously, concern for DL-ACK collisions with UL-data430can be avoided because all DL-ACK420will be triggered by BAR415after the UL ACK425.

In an exemplary aspect, in determining whether it is more efficient to use FD-DL transmissions for BlockACK procedures illustrated inFIG. 4A, scheduling FD-DL is more efficient when more than one MPDU are scheduled for FD-DL or when DL STA cannot support the IEEE 802.11n protocol because block ACK will be triggered by BAR even in HD-DL.

For a FD-DL transmission with only one MPDU to an HT-STA, the MPDU may as well be transmitted in HD with Normal ACK setting. In an exemplary aspect, the AP120can be configured to check whether transmission in HD is less efficient based on Equation 2 below:

THD⁢-⁢DL=LDL⁢-⁢MPDUR⁡(SINRHD⁢-⁢DL⁢-⁢data)>TBAR+δ
where THD-DLis the time duration required to transmit the MPDU (with LDL-MPDUbits) in HD mode, R is the function to map SINR to data rate, and δ is a channel sensing overhead constant that approximates channel sensing overhead and the offset time difference in BA and ACK transmissions.

If transmitting the DL MPDU410in HD (with Normal ACK setting) takes longer than transmitting BAR, the AP120can trigger FD-DL for single DL MPDU as it will be more efficient.

In an exemplary aspect, if SINRFD-UL-ACK≥THMCS0is satisfied in addition to Equation 3, the AP120can be configured to choose to send BAR415right before UL-ACK425(where the AP120adjusts the number of FD-DL MPDU accordingly) and have DL-Block-ACK420transmission overlaps with UL-ACK425.

In an exemplary aspect, when transmitting FD-DL using an aggregated MPDU (A-MPDU), if the UL transmission aborts early, the AP120can advantageously choose to terminate FD-DL transmission early and retransmit the un-sent MPDUs with higher modulation and coding scheme (MCS) because there would be little to no UL-DL interference.

Decoding of First MPDU Triggers FD-DL Transmission with HT UL STA

FIG. 5illustrates destination-based joint DL-UL transmission operations according to exemplary aspects of the present disclosure. In the exemplary aspect, for HT UL STAs, the AP120can confirm that the AP120is the recipient of following MPDUs511-512by decoding the first MPDU510. For example, when the HT UL STA is sending data in A-MPDU, the AP120can wait until successfully decoding the first MPDU510to confirm that the AP120is the recipient of following MPDUs511-512to trigger the FD-DL transmission.

In an exemplary aspect, the procedure illustrated inFIG. 5can be utilized to trigger joint DL-UL transmission. In this example, the transmission can be triggered when the SINR conditions in Equations 1(b) to 1(e) are satisfied. That is, different from the general transmission criteria above, the utilization of the waiting until after the first MPDU510is decoded reduces the SINR conditions for triggering the trigger joint DL-UL transmission and thereby increasing the availability of the AP120to perform such transmissions. In this example, the SINR condition of Equation 1(a) is not applicable because the triggering is not based only on the MAC header.

In an exemplary aspect, for timing alignment, the AP120can be configured to estimate the start time of UL-ACK520after decoding the PHY header509of the UL data530.

In an exemplary aspect, with respect to the efficiency of the joint DL-UL transmission, scheduling the FD-DL is more efficient than transmissions using extra resource to send the DL packet in HD.

In an exemplary aspect, when the AP120is configured to pre-decode the MAC header and when UL HD SINR is high enough for early MAC header decoding (without FCS check), the AP120can be configured to choose to trigger FD-DL transmission early. In this example, the chance for triggering joint DL-UL transmission can be advantageously increased by allowing initiation of the FD-DL transmission even when UL HD SINR is not high enough for early MAC header decoding.

Delaying FD-UL Transmission to Protect FD-DL Preamble Detection

In an exemplary aspect, with reference toFIG. 5, when the signal preamble is received before the interference, the required SINR for detection can be reduced. Further, interference that arrives during Legacy Short Training Field (L-STF) can have less impact than interference that arrives during Legacy Long Training Field (L-LTF) or Legacy Signal field (L-SIG). Therefore, in an exemplary aspect, to improve joint DL-UL transmission performance, FD-UL transmission can be delayed to protect FD-DL preamble detection. For example, additional time alignment can be added to ensure DL-ACK starts after UL-ACK (e.g., 4˜8 μs) to protect preamble detection for UL-ACK. In an exemplary aspect, this additional time can be realized by padding dummy tone (e.g., dummy bits) in the end of DL data transmission.

FIG. 6illustrates destination-based joint DL-UL transmission operations according to exemplary aspects of the present disclosure.

In an exemplary aspect, if DL STA is a QoS STA and the UL HT STA sends data in A-MPDU, a combination of the aspects of procedures illustrated inFIGS. 4A-4CandFIG. 5can further increase joint DL-UL transmission availability. In this example, althoughFIG. 6illustrates the adoption of the BlockACK procedures ofFIG. 4C, all the DL-ACK procedures described with reference toFIGS. 4A-4Ccan be applied to the current exemplary aspect.

With reference toFIG. 6, the DL MPDU630can be transmitted after the AP120decodes the first UL MPDU610. If the AP120detects that the UL transmission ends and the on-going DL MPDU635cannot be finished, the AP120can terminate transmission of last MPDU635immediately. The AP120can then retransmit the MPDU635with Normal ACK setting after UL-ACK620transmission as shown by the MPDU640.

In an exemplary aspect, procedure illustrated inFIG. 6can be utilized to trigger joint DL-UL transmission. In this example, the transmission can be triggered when the SINR conditions in Equations 1(b) to 1(d) are satisfied. That is, different from the transmission criteria above, the combination of the aspects of procedures illustrated inFIGS. 4A-4CandFIG. 5can further increase joint DL-UL transmission availability by reducing the SINR conditions for triggering the trigger joint DL-UL transmission. This increases the availability of the AP120to perform such transmissions.

In this exemplary aspect, the timing alignment criteria is similar to the time alignment criteria for the aspect illustrated with reference toFIGS. 4A-4C. Further, in an exemplary aspect, the efficiency to use FD-DL transmissions is similar to the aspects illustrated inFIG. 4A-4C.

UL STA Transmits with RTS

FIGS. 7A-7B and 8illustrate destination-based joint DL-UL transmission operations utilizing Request-to-sent (RTS) communications according to exemplary aspects of the present disclosure. When the UL STA starts transmission with RTS, the AP120can begin to prepare for FD-DL transmission after decoding the destination address (DA) field of the RTS communication. In an exemplary aspect, the DL STA140can be configured to receive and decode DL data from AP120during non-zero network allocation vector (NAV).

FIGS. 7A-7Billustrate destination-based joint DL-UL transmission operations utilizing Request-to-sent (RTS) communications according to exemplary aspects of the present disclosure. In this example, the FD DL transmission starts after the clear-to-send (CTS) communication.

Based on the aspects described with reference toFIG. 5, in an exemplary aspect shown inFIG. 7A, the FD-DL transmission725can start before the FD-UL transmission715to protect FD-DL preamble. In a non-limiting example, the FD-DL transmission725can start, for example, 4˜8 μs before the FD-UL transmission715. In an exemplary aspect, by starting the transmission of the FD-DL725before the FD-UL transmission715, the SINR condition illustrated in Equation 1(c) can be omitted. The FD-DL transmission can start at other time periods before the FD-UL transmission715as would be understood by one of ordinary skill in the relevant arts. In an exemplary aspect, the AP120can utilize RTS/CTS procedures to ensure that the FD-DL transmission725start before the FD-UL transmission715. In this example, the AP120can be configured to send a CTS communication710to the UL STA140in response to a RTS communication705from the UL STA140. As shown inFIG. 7A, a short interframe space (SIFS) period occurs between the DL data725and the DL ACK730, between the RTS705and CTS710, between the CTS710and the UL data715, and between the UL data715and the UL ACK720.

In an exemplary aspect, if the DL ACK730and UL ACK720overlapped in time as illustrated inFIG. 7A, extra bits can be padded to the DL data725so that FD-UL ACK720starts before (e.g., 4˜8 μs) the FD-DL ACK730. In an exemplary aspect, althoughFIG. 7Billustrates a similar adoption of the BlockACK procedures ofFIG. 4A, for DL QoS STAs, all the DL-ACK procedures described with reference toFIGS. 4A-4Ccan be applied to the destination-based joint DL-UL transmission operations utilizing RTS communications.

As shown inFIG. 7B, the RTS705and CTS710procedure ensures that the transmission of the UL data740occurs after the DL data transmission using MPDUs750-752. A BlockAck procedure can also be used to acknowledge the DL data. In this example, the BAR760is transmitted by the AP120after the UL ACK745is received by the AP120to ensure that the UL ACK745and DL ACK (i.e., BlockACK765) do not conflict with each other. That is, the DL ACK and the UL ACK745are time-domain multiplexed so as to not overlap using the BAR760.

In an exemplary aspect, the RTS/CTS procedures illustrated inFIGS. 7A-7Bcan be utilized to trigger joint DL-UL transmission when the SINR conditions in Equations 1(b) and 1(d) are satisfied. If the DL ACK730and the UL ACK720overlap as shown inFIG. 7A, the SINR conditions can also include Equation 1(e). In an exemplary aspect, if the FD-DL (e.g.,725,750) is started before the FD-UL transmission (e.g.,715,750), the SINR condition illustrated in Equation 1(c) can be omitted. That is, different from the transmission criteria above, the aspects of procedures illustrated inFIGS. 7A-7Bcan further increase joint DL-UL transmission availability by reducing the SINR conditions for triggering the trigger joint DL-UL transmission. This increases the availability of the AP120to perform such transmissions.

In this exemplary aspect, the timing alignment criteria is similar to the time alignment criteria for the aspect illustrated with reference toFIGS. 4A-4Cwhen using BlockACK procedures for the DL operations. Otherwise, extra bits can be padded to the DL data725so that FD-UL ACK720starts before the FD-DL ACK730.

In an exemplary aspect, with respect to the efficiency of the joint DL-UL transmission, the efficiency is similar to the efficiency criteria for the aspect illustrated with reference toFIGS. 4A-4Cwhen using BlockACK procedures for the DL operations. Otherwise, the scheduling the FD-DL is more efficient than transmissions using extra resource to send the DL packet in HD where the communication system includes a pair-able DL-STA with packet size satisfying the above constraints.

FIG. 8illustrates destination-based joint DL-UL transmission operations utilizing a fast RTS-CTS procedure after decoding of the RTS DA field according to exemplary aspects of the present disclosure. In this example, the FD DL transmission starts after the clear-to-send (CTS) communication.

In an exemplary aspect, a fast RTS-CTS can be inserted before DL transmission to add extra protection at the DL STA140from interference from hidden nodes. For example, the RTS822is generated by the AP120and sent to the DL STA140. In an exemplary aspect, to end the DL-RTS822transmission before the start of UL-CTS810, the DL-RTS822can be sent in a higher Modulation and Coding Scheme (MCS). For example, the AP120can be configured to immediately transmit the DL RTS822after decoding the RTS DA field. In this example, the available time for completing the RTS transmission is can be, for example, 16 μs (time to transmit Source Address (SA) & frame check sequence (FCS))+SIFS, but is not limited thereto. In an exemplary aspect, the AP120is configured to decode the MAC header without FCS check and includes a sufficiently high UL SINR for early MAC header decoding.

In exemplary aspects, where the DL-CTS823overlaps with the UL-CTS810, the AP120can be configured to have an SINR for the UL CTS810that is sufficient to compensate for the interference from the DL CTS823. In this example, this SINR value is similar to the SINR requirement when the DL and UL ACKs overlap.

In an exemplary aspect, when operating at 2.4 GHz and where SIFS is, for example, 10 μs, the AP120can be configured to transmit the DL-RTS822within 26 μs and with a data rate greater than 48 Mbps. When operating at 5 GHz and where SIFS is 16 μs, the AP120can be configured to transmit the DL-RTS822at data rate greater than 18 Mbps. The SIFS value and data rates are not limited to these exemplary values and can be other values as would be understood by one of ordinary skill in the relevant arts.

In an exemplary aspect, if the DL STA140fails to decode the FD-RTS822, the AP120can be configured to schedule the FD-DL transmission at a later time with a lower MCS. Further, because the UL CTS810may interfered with the DL CTS823, the AP120can be configured to not start the DL-RTS822transmission unless it has a high confidence from one or more past measurements that the DL STA to UL STA interference will not affect the CTS reception.

In an exemplary aspect, the fast RTS/CTS procedures illustrated inFIG. 8can be utilized to trigger joint DL-UL transmission when the SINR conditions in Equations 1(a) to 1(e) are satisfied. Further, the timing alignment criteria and the efficiency criteria is similar to the baseline time alignment criteria and the baseline efficiency criteria.

Example Source-Based Joint DL-UL Transmission Operations

As described above, in sourced-based joint DL-UL transmission, the AP wins the channel contention process for DL transmission and triggers another STA for FD-UL transmission.

In source-based joint DL-UL transmissions, the AP120is granted channel access to send the first packet. As described above, source-based transmissions can include when the AP120wins the contention period, and can include a distributed coordination function (DCF) and the QoS-STA with UL traffic can be polled. In exemplary aspects, the AP120can be configured to implement HCF (hybrid coordination function) controlled channel access (HCCA) to poll a QoS-STA for UL transmission and then schedule concurrent DL transmissions with a pair-able STA140.

In exemplary aspects, QoS Contention-Free-Poll (CF-Poll) can be used to achieve source-based joint DL-UL transmission. Further, the polling operations can also be used for Point coordination function (PCF) contention free (CF)-pollable UL STAs.

HCCA to Poll QoS UL STA

FIGS. 9A-9Billustrate sourced-based joint DL-UL transmission operations utilizing HCCA to poll the QoS-STA according to exemplary aspects of the present disclosure. In an exemplary aspect, the AP120can be configured to use QoS and CF-Poll operations to poll an UL QoS STA140for uplink transmission. The AP120can then transmit to a pair-able DL STA140simultaneously while receiving UL data.

In an exemplary aspect, when the AP120wins channel contention, the AP120can be configured to trigger a QoS STA140to send an UL packet915by sending a CF-Poll frame910to STA901. After transmitting the CF-Poll frame910, the AP120can start a DL transmission925to a STA902pair-able to the polled UL STA901. In an exemplary aspect, the DL transmission is performed concurrently with the UL transmission915from the polled UL STA901. The AP120can then send a CF-ACK920to the STA901to acknowledge the UL transmission915. Similarly, the AP can receive an ACK930to acknowledge that the STA902has received the data925.

In an exemplary aspect, the AP120includes knowledge of a queue-size for the UL traffic915obtained from, for example, a QoS STA queue report, a high layer message exchange, and/or other queue information procedures as would be understood by one of ordinary skill in the relevant arts. The AP120can be configured to poll a QoS STA901with UL data and announce a Transmit Opportunity (TXOP) duration in the QoS CF-Poll message910based on the queue-size information of the UL QoS STA901. Based on the TXOP information, the AP120can schedule DL transmissions accordingly with the STA902.

As shown inFIG. 9A, the DL ACK930overlaps with the UL ACK920. In an exemplary aspect, if the DL STA902is a QoS STA, then the Block ACK operations illustrated inFIGS. 4A-4Ccan be applied to the current sourced-based joint DL-UL transmission operations. For example, a BlockACK operation similar to the operation illustrated inFIG. 4Ais shown inFIG. 9B. In an exemplary aspect, the FD-DL transmission starts before (e.g., 4-8 μs) the UL transmission similar to the aspects described above with reference toFIG. 7Ato increase DL preamble detection.

In an exemplary aspect, the procedures illustrated inFIGS. 9A-9Bcan be utilized to trigger joint DL-UL transmission when the SINR conditions in Equations 1(b) and 1(d) are satisfied. If the DL ACK930and the CF ACK920overlap as shown inFIG. 9A, the SINR conditions can also include Equation 1(e). That is, different from the transmission criteria above, the aspects of procedures illustrated inFIGS. 9A-9Bcan further increase joint DL-UL transmission availability by reducing the SINR conditions for triggering the trigger joint DL-UL transmission. This increases the availability of the AP120to perform such transmissions.

In this exemplary aspect, for the timing alignment criteria, the AP120can be configured to start the DL data925before (e.g., 1-8 μs) the UL data915. In an exemplary aspect, for QoS DL STAs, the AP120can perform BlockACK operations similar to those illustrated inFIGS. 4A-4C. For example, the AP120can estimate the start time of the QoS CF-ACK920. The AP120can schedule as many MPDUs951-952for the FD-DL transmission so that the last MPDU952ends before the QoS CF-ACK920start time. In this example, if less than one MPDU can be scheduled, the AP120can be configured to not trigger the FD-DL transmission. Advantageously, concern for DL-ACK collisions with UL-data915can be avoided because the DL-ACK will be triggered by BAR960after the QoS CF-ACK920. The BlockACK965can then acknowledge BAR960.

For non-QoS DL STAs, the AP120can be configured to determine (e.g., estimate) a DL transmission duration based on the TXOP setting in the QoS CF-Poll frame910. If the DL transmission925ends early, the AP120can pad dummy bits to the end of the data925as suggested above.

In exemplary aspects where the DL data925takes longer than the UL data915, the AP120can be configured to discard one of the DL and UL transmissions. Also, where the UL data915is transmitted without requiring ACK, there is no constraint on the DL transmit duration of the DL data925.

In an exemplary aspect, with respect to the efficiency of the joint DL-UL transmission, it is more efficient to transmit in FD if the joint DL-UL transmission can be aligned as described above. In exemplary aspects where the DL transmission may end after the start of CF-ACK, the AP120can determine which transmit direction to drop based on the following: (1) if the retransmission of the DL in HD is more efficient than to complete the ongoing DL transmission and retransmit the UL in HD, the AP120can stop the DL transmission and prepare for the UL CF-ACK; or (2) the AP120can continue transmitting DL data and the UL STA will retransmit the un-acknowledged data at a later time.

FIG. 10illustrates a sourced-based joint DL-UL transmission operations utilizing HCCA to poll the QoS-STA according to exemplary aspects of the present disclosure.

In an exemplary aspect where the AP120has no knowledge of whether a QoS STA has UL traffic to send, the UL STA can be configured to reply to the QoS CF Poll1002with a QoS Null1003after the QoS CF-Poll1002. In this example, the DL transmission1025is triggered after the AP120detects that the UL PHY preamble indicates a longer packet length. That is, the AP120can be configured to trigger the UL transmission1015via a QoS CF-Poll1010and start FD-DL transmission1025after the AP120detects that the UL packet size is longer than QoS Null1003.

In this example, the AP120can be configured to initiate the DL data transmission1025after the AP120detects that the received packet QoS CF-Poll1010is coming is coming from a UL STA that has data to send and is not a null packet1003coming from a UL STA with no data to send. The DL data1025can be acknowledged by the DL STA using an ACK1030sent to the AP120. The QoS data1015is acknowledged by the AP120using the QoS CF ACK1020.

In an exemplary aspect, the procedures illustrated inFIG. 10can be utilized to trigger joint DL-UL transmission when the SINR conditions in Equations 1(b) to 1(d) are satisfied. In this example, the Equation 1(c) is used because the UL interference may start before the DL signal. If the DL ACK1030and the CF ACK102overlap as shown inFIG. 10, the SINR conditions can also include Equation 1(e). In an exemplary aspect, the BlockACK procedures illustrated inFIG. 4A,FIG. 4B, and/orFIG. 4Ccan be adopted to the aspects illustrated inFIG. 10to further increase joint DL-UL transmission availability by reducing the SINR conditions for triggering the trigger joint DL-UL transmission.

In an exemplary aspect, the efficiency criteria is similar to the aspects described above with referenceFIGS. 9A-9B. For the time alignment, the criteria is similar to the alignment operations according to the aspects described above with referenceFIGS. 9A-9B, but also include that the DL transmission1025should start after decoding the UL PHY preamble in an exemplary aspect.

FIG. 11illustrates a sourced-based joint DL-UL transmission operations utilizing HCCA to poll the QoS-STA according to exemplary aspects of the present disclosure. This configuration is similar to the aspects illustrated inFIGS. 9A-10, but the AP120can be configured to send a RTS communication1122to the DL STA and the DL STA can reply with a CTS communication1123. In this aspect, the DL STA can be advantageously protected from hidden nodes by utilizing the RTS/CTS procedures (RTS1122and CTS1123).

In an exemplary aspect, the AP120can be configured to send the QoS CF-Poll1110to UL STA with the additional DL STA to UL STA interference.

In this example, the AP120can select appropriate MCS for QoS CF-Poll transmission such that the transmission time for the QoS CF-Poll1110is shorter than a CTS transmission time plus two SIFS periods.

In an exemplary aspect, the UL STA can be configured such that the UL STA will reset its NAV setting if the UL STA receives another packet from the same source that sets the previous NAV.

In an exemplary aspect, the procedures illustrated inFIG. 11can be utilized to trigger joint DL-UL transmission when the SINR conditions in Equations 1(b) to 1(d) are satisfied similar to the aspects illustrated inFIG. 10, but also include Equation 1(e)

In an exemplary aspect, for the operations illustrated inFIG. 11, the efficiency criteria and the alignment operations are similar to the aspects described above with referenceFIGS. 9A-9B.

Source-Based Joint DL-UL TX Using PCF to Poll Non-QoS CF-Pollable UL STA

FIG. 12illustrates a sourced-based joint DL-UL transmission operations utilizing polling for non-QoS STAs according to exemplary aspects of the present disclosure.

In an exemplary aspect, for non-QoS STAs, if the STAs are CF-pollable, the AP120can be configured to send CF-poll1210to trigger their UL transmission based on a Point coordination function (PCF). This aspect is similar to the operations of the aspects described with reference toFIG. 10, but include the following variations. First, the CF-poll is sent during contention free period (CFP) of PCF operation. The contention free period starts with AP120broadcasting beacons1201,1205and ends with the AP broadcasting CF-End1220. Second, the CF-poll does not contain a QoS field and therefore there is no TXOP duration defined. In some cases, the non-QoS UL STA is unable to report queue size information.

In an exemplary aspect, for the operations illustrated inFIG. 12, the SINR, efficiency, and alignment criteria are similar to the aspects described above with referenceFIG. 10.

Examples

Example 1 is a method adapted for establishing joint communications between an access point (AP) and first and second communication stations (STAs), the method comprising: calculating joint transmission information based on the first and the second STAs; establishing a first communication between the AP and the first STA; and establishing a second communication between the AP and the second STA based on the joint transmission information.

In Example 2, the subject matter of Example 1, wherein calculating the joint transmission information comprises: calculating interference information associated with the AP and the first and the second STAs; calculating communication alignment information for communications between the AP and the first and the second STAs; and calculating efficiency information for the communications between the AP and the first and the second STA.

In Example 3, the subject matter of Example 2, wherein the interference information includes signal-to-noise ratio information between the AP and the first and the second STAs.

In Example 4, the subject matter of Example 1, wherein the AP is configured to communicate in a full-duplex operation and the first and the second STAs are configured to communicate in a half-duplex operation.

In Example 5, the subject matter of Example 1, wherein the first communication is an uplink communication from the first STA to the AP, and the second communication is a downlink communication from the AP to the second STA.

In Example 6, the subject matter of Example 1, wherein establishing the second communication comprises: delaying an acknowledgement from the second STA to the AP until after an acknowledgment from the AP is received by the first STA.

In Example 7, the subject matter of Example 1, wherein establishing the second communication comprises: transmitting, by the AP, a first protocol data unit (PDU) comprising an acknowledge policy set to block acknowledgment; and transmitting, by the AP, a block acknowledgment request (BAR) to the second STA to delay an acknowledgement from the second STA to the AP until after an acknowledgment from the AP is received by the first STA.

In Example 8, the subject matter of Example 1, wherein establishing the second communication comprises: transmitting, by the AP, a first protocol data unit (PDU) comprising an acknowledge policy set to block acknowledgment; and transmitting, by the AP, a second PDU comprising an acknowledgment policy set to a normal acknowledgment to delay an acknowledgement from the second STA to the AP until after an acknowledgment from the AP is received by the first STA.

In Example 9, the subject matter of Example 1, wherein establishing the second communication comprises: decoding a first protocol data unit (PDU) received by the AP from the first STA; and establishing the second communication based on the decoded first PDU.

In Example 10, the subject matter of Example 1, wherein establishing the second communication comprises: padding a data block of the second communication with one or more dummy bits to delay an acknowledgement from the second STA to the AP until after transmission of an acknowledgment from the AP to the first STA has been initiated by the AP.

In Example 11, the subject matter of Example 1, wherein establishing the second communication comprises: transmitting a clear-to-send (CTS) packet to the first STA in response to a request-to-send (RTS) packet from the first STA to initiate a transmission of a data block from the AP to the second STA before reception of a data block from the first STA to the AP.

In Example 12, the subject matter of Example 11, wherein establishing the second communication further comprises: transmitting, by the AP, a block acknowledgment request (BAR) to the second STA to delay an acknowledgement from the second STA to the AP until after an acknowledgment from the AP is received by the first STA; or padding the data block of the second communication with one or more dummy bits to delay reception of the acknowledgement from the second STA by the AP until after transmission of an acknowledgment from the AP to the first STA has been initiated by the AP, wherein the acknowledgment from the second STA acknowledges reception of the data block of the second communication by the second STA and the acknowledgment from the AP acknowledges reception of the data block of the first communication from the first STA by the AP.

In Example 13, the subject matter of Example 1, wherein establishing the first communication comprises: transmitting, by the AP, a poll frame to the first STA to trigger transmission of a data block from the first STA to the AP.

Example 14 is an access point (AP) operable to establish joint communications with first and second communication stations (STAs), comprising: a transceiver configured to communicate with the first and the second STAs; and a controller coupled to the transceiver and is configured to: calculate joint transmission information based on the first and the second STAs; control the transceiver to establish a first communication with the first STA; and control the transceiver to establish a second communication with the second STA based on the joint transmission information.

In Example 15, the subject matter of Example 14, wherein calculating the joint transmission information comprises: calculating interference information associated with the AP and the first and the second STAs; calculating communication alignment information for communications between the AP and the first and the second STAs; and calculating efficiency information for the communications between the AP and the first and the second STA.

In Example 16, the subject matter of Example 14, wherein the first communication is an uplink communication from the first STA to the AP, and the second communication is a downlink communication from the AP to the second STA.

In Example 17, the subject matter of Example 14, wherein establishing the second communication comprises: delaying reception of an acknowledgement by the AP from the second STA until after an acknowledgment from the AP is received by the first STA.

In Example 18, the subject matter of Example 14, wherein the establishing the second communication comprises: transmitting, by the transceiver, a first protocol data unit (PDU) comprising an acknowledge policy set to block acknowledgment; and transmitting, by the transceiver, a block acknowledgment request (BAR) to the second STA to delay reception of an acknowledgement from the second STA by the AP until after an acknowledgment from the AP is received by the first STA.

In Example 19, the subject matter of Example 14, wherein establishing the second communication comprises: transmitting, by the transceiver, a first protocol data unit (PDU) comprising an acknowledge policy set to block acknowledgment; and transmitting, by the AP, a second PDU comprising an acknowledgment policy set to a normal acknowledgment to delay an acknowledgement from the second STA to the AP until after an acknowledgment from the AP is received by the first STA.

In Example 20, the subject matter of Example 14, wherein establishing the second communication comprises: decoding a first protocol data unit (PDU) received by the AP from the first STA; and establishing the second communication based on the decoded first PDU.

In Example 21, the subject matter of Example 14, wherein establishing the second communication comprises: padding a data block of the second communication with one or more dummy bits to delay reception of an acknowledgement from the second STA by the AP until after transmission of an acknowledgment from the AP to the first STA has been initiated by the AP.

In Example 22, the subject matter of Example 14, wherein establishing the second communication comprises: transmitting a clear-to-send (CTS) packet to the first STA in response to a request-to-send (RTS) packet from the first STA to initiate a transmission of a data block by the transceiver to the second STA before reception of a data block from the first STA to the AP.

In Example 23, the subject matter of Example 22, wherein establishing the second communication further comprises: transmitting, by the transceiver, a block acknowledgment request (BAR) to the second STA to delay reception of an acknowledgement from the second STA by the AP until after an acknowledgment from the AP is received by the first STA; or padding the data block of the second communication with one or more dummy bits to delay the reception of the acknowledgement from the second STA by the AP until after transmission of the acknowledgment from the AP to the first STA has been initiated, wherein the acknowledgment from the second STA acknowledges reception of the data block of the second communication by the second STA and the acknowledgment from the AP acknowledges reception of the data block of the first communication from the first STA by the AP.

In Example 24, the subject matter of Example 14, further comprising a memory that stores the joint transmission information.

In Example 25, the subject matter of Example 15, further comprising a memory that stores the interference information, the communication alignment information, and the efficiency information.

Example 26 is a communication method to communicate between an access point (AP) and first and second communication stations (STAs), comprising: calculating joint transmission information based on the first and the second STAs, the joint transmission information comprising: interference information associated with the AP and the first and the second STAs; communication alignment information for communications between the AP and the first and the second STAs; and efficiency information for the communications between the AP and the first and the second STA; establishing an uplink communication between the AP and the first STA; and establishing a downlink communication between the AP and the second STA jointly with the uplink communication between the AP and the first STA based on the joint transmission information.

In Example 27, the subject matter of Example 26, wherein establishing the downlink communication comprises: delaying reception of an acknowledgement from the second STA by the AP until after an acknowledgment from the AP is received by the first STA.

Example 28, is an access point (AP) configured to perform the method of any of claims 1-13, 26, and 27.

Example 29 is a communication station (STA) configured to perform the method of any of claims 1-13, 26, and 27.

Example 30 is an apparatus comprising means to perform the method as claimed in any of claims 1-13, 26, and 27.

Example 31 is a computer program product embodied on a computer-readable medium comprising program instructions, when executed, causes a machine to perform the method of any of claims 1-13, 26, and 27.

Example 32 is an apparatus substantially as shown and described.

Example 33 is a method substantially as shown and described.

CONCLUSION

References in the specification to “one aspect,” “an aspect,” “an exemplary aspect,” etc., indicate that the aspect described may include a particular feature, structure, or characteristic, but every aspect may not necessarily include the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same aspect. Further, when a particular feature, structure, or characteristic is described in connection with an aspect, it is submitted that it is within the knowledge of one skilled in the art to affect such feature, structure, or characteristic in connection with other aspects whether or not explicitly described.

The exemplary aspects described herein are provided for illustrative purposes, and are not limiting. Other exemplary aspects are possible, and modifications may be made to the exemplary aspects. Therefore, the specification is not meant to limit the disclosure. Rather, the scope of the disclosure is defined only in accordance with the following claims and their equivalents.

For the purposes of this discussion, the term “processor circuitry” shall be understood to be circuit(s), processor(s), logic, or a combination thereof. For example, a circuit can include an analog circuit, a digital circuit, state machine logic, other structural electronic hardware, or a combination thereof. A processor can include a microprocessor, a digital signal processor (DSP), or other hardware processor. The processor can be “hard-coded” with instructions to perform corresponding function(s) according to aspects described herein. Alternatively, the processor can access an internal and/or external memory to retrieve instructions stored in the memory, which when executed by the processor, perform the corresponding function(s) associated with the processor, and/or one or more functions and/or operations related to the operation of a component having the processor included therein.

In one or more of the exemplary aspects described herein, processor circuitry can include memory that stores data and/or instructions. The memory can be any well-known volatile and/or non-volatile memory, including, for example, read-only memory (ROM), random access memory (RAM), flash memory, a magnetic storage media, an optical disc, erasable programmable read only memory (EPROM), and programmable read only memory (PROM). The memory can be non-removable, removable, or a combination of both.

As will be apparent to a person of ordinary skill in the art based on the teachings herein, exemplary aspects are not limited to the IEEE 802.11 standards. The exemplary aspects can be applied to other wireless communication protocols/standards (e.g., Long-term Evolution—LTE) as would be understood by one of ordinary skill in the relevant arts.