Feedback enhancement in 802.11 to enhance performance of link adaptation, delay sensitive traffic and in-device coexistence

Abstract

The present disclosure relates to feedback enhancements in 802.11 for enhancing performance of link adaptation, delay-sensitive traffic, and in-device coexistence. An improved solution for providing performance of latency sensitive traffic, multi-link operation, link adaptation, and in-device coexistence is disclosed. An apparatus having a Wi-Fi transceiver and a second transceiver sharing at least one antenna can detect that a communication burst received by the second transceiver exceeds a time period allocated to a second communication. The apparatus is capable of communicating with a Wi-Fi AP to receive Wi-Fi communications. The device can determine, in response to the detection, a schedule for the AP to transmit Wi-Fi communications to the device, the schedule including a burst limit for a first time period based on a periodicity of a second time period. The apparatus can communicate the schedule to the access point.

Description

[0001] Cross-reference to related patent applications

[0002] This application claims the benefit and priority of Indian Provisional Patent Application No. 202321041989 filed on June 23, 2023 and U.S. Provisional Patent Application No. 63 / 573093 filed on April 2, 2024, both of which are incorporated herein by reference in their entirety and for all purposes. Technical Field

[0003] The present disclosure generally relates to systems and methods for communicating in a wireless local area network, including implementing link adaptation, traffic delay, and coexistence between different wireless technologies. Background Art

[0004] The wireless communication device may utilize various network communication chipsets or subsystems that may be configured to implement different wireless communication technologies, such as wireless local area network (WLAN) technology, cellular communication technology, Bluetooth, ultra-wideband (UWB), or any other wireless communication technology. The wireless communication device may operate in a variety of environments and situations. Summary of the invention

[0005] The technical solutions of the present disclosure provide enhancements to feedback mechanisms that are intended to reduce in-device coexistence (IDC) problems in wireless communication systems, such as those encountered by 802.11 Wi-Fi communications. These enhancements can improve link adaptation, reduce latency, and optimize IDC between Wi-Fi and other wireless features that share the resources (e.g., antennas) of a host device. When a burst of non-Wi-Fi wireless communications exceeds the time allocated for its use of shared resources, the technical solution can provide a Wi-Fi access point with a timed and synchronized schedule for its transmission to avoid overlap with the extended burst. For example, non-Wi-Fi communications can use shared resources at a time point that occurs periodically or is not previously known to the Wi-Fi module. The solution can customize the scheduling of Wi-Fi communications to avoid overlap with non-Wi-Fi communications without adversely affecting the fidelity of Wi-Fi communications. When a Wi-Fi access point receives notification from a device about an IDC problem between two technologies on the device, the technical solution can configure the AP to delay confirmation of data frames that have already been transmitted without marking them as failed. The solution can also use frame confirmations to provide transmission information even in the case of failure, allowing more intelligent adjustments to be made by the access point. For example, when a low latency packet is identified during the transmission of a previous frame, a solution may include the low latency packet in the ongoing frame transmission, thereby improving throughput and communication efficiency.

[0006] Aspects of the technical solution relate to a method. The method may include detecting, by a device including a Wi-Fi transceiver and a second wireless transceiver sharing at least one antenna, a communication burst. A communication burst that exceeds a time period allocated for a second wireless communication may be received by the second wireless transceiver. The device may communicate with an access point (AP) to receive Wi-Fi communications. The method may include determining, by the device in response to the detection, a schedule for the AP to transmit Wi-Fi communications to the device. The schedule may include a burst limit for a first time period based on a periodicity of a second time period. The method may include the device communicating the schedule to the access point.

[0007] The first time period may be allocated for receiving Wi-Fi transmissions, and the second time period corresponds to a duration between a start of the first time period and a start of a next first time period based on the periodicity of the second time period. The next first time period may be allocated for receiving Wi-Fi transmissions. The method may include the device receiving an aggregated media access control protocol data unit (AMPDU) of the Wi-Fi communication during the next first time period. The AMPDU may include a size adjusted according to the next first time period.

[0008] The method may include receiving, by the device, an AMPDU for Wi-Fi communications during a next first time period. The AMPDU may include a size maximized to fit within the next first time period and to allow transmission of a block acknowledgement (BA) for the AMPDU to be completed within the next first time period.

[0009] The method may include detecting, by the device, that a second communication burst received by the second wireless transceiver overlaps with a portion of a first time period allocated according to a schedule to receive Wi-Fi communications from the AP. The method may include adjusting the schedule, by the device, in response to the overlap. The schedule may be adjusted to change at least one of a duration of the first time period or a duration of the second time period according to a duration of the second communication burst. The second wireless communication may correspond to at least one of: Bluetooth communication, ultra-wideband (UWB) communication, long term evolution (LTE) communication, licensed assisted access (LAA) communication, new radio (NR) communication, or new radio unlicensed (NR-U) communication.

[0010] The method may include receiving, by a device, an aggregate media access control protocol data unit (AMPDU) of Wi-Fi communications from an access point. The method may include generating, by the device, a block acknowledgment (BA) for the AMPDU. The method may include communicating, by the device, a schedule to the access point via the BA. The schedule may be used to receive Wi-Fi communications via a first communication channel of a plurality of communication channels.

[0011] The method may include detecting, by the device, that a second communication burst received by the second transceiver exceeds a second time period allocated for a second wireless communication. The method may include determining, by the device in response to the detection of the second communication burst, a second schedule for the access point to transmit Wi-Fi communications to the device via a second channel of the plurality of channels, the second schedule comprising a second burst limit of a third time period based on a second period of a fourth time period. The method may include communicating, by the device, the second schedule to the access point.

[0012] Aspects of the technical solution may relate to an access point (AP), such as a Wi-Fi AP device. The access point may include one or more processors coupled to a memory. The one or more processors may be configured to receive a block acknowledgement (BA) from a device including information identifying the presence of an intra-device coexistence problem on the device. The one or more processors may be configured to determine, in response to identifying an intra-device coexistence problem, to allow one or more BAs from the device to be delayed for more than a short interframe space (SIFS) in response to one or more aggregate media access control protocol data units (AMPDUs) from the AP without being identified as a failure. The one or more processors may be configured to receive a second BA from the device after the SIFS and in response to the determination. The second BA may include multiple acknowledgements corresponding to multiple AMPDUs received from the AP.

[0013] The one or more processors may be configured to determine, in response to determining, that the multiple transmissions of the multiple AMPDUs were successful regardless of a second BA received after the SIFS. The one or more processors may be configured to receive a block acknowledgment (BA) from the second device including information that no intra-device coexistence issues were identified on the second device. The one or more processors may be configured to transmit the AMPDU to the second device and determine that a BA for the AMPDU was not received within the SIFS. The one or more processors may be configured to identify that the transmission of the AMPDU has failed in response to not receiving a BA within the SIFS.

[0014] The one or more processors may be configured to recognize that the device is configured for Wi-Fi communication, wherein transmission of one or more BAs for one or more AMPDUs is delayed until after one or more SIFS after the one or more AMPDUs. The one or more processors may be configured to transmit, in response to the configuration, a provision that communicates the plurality of AMPDUs according to the configuration. The provision may be indicated in at least one of a header of a physical layer or a header of a medium access control header of an AMPDU in the plurality of AMPDUs.

[0015] One or more processors (e.g., processors of the receiver) may be configured to identify channel quality information indicating a signal-to-interference-plus-noise ratio (SINR) margin from the information. One or more processors (e.g., processors of the receiver) may be configured to adjust a modulation and coding scheme (MCS) for transmission to the device in response to the SINR margin. One or more processors (e.g., processors of the receiver) may be configured to identify from the information an indication corresponding to at least one of: a modulation and coding scheme (MCS) for transmission to the device, a signal strength of one or more AMPDUs, or a presence of one or more hidden nodes.

[0016] One or more processors (e.g., a processor of the transmitter) may be configured to adjust, in response to the indication, at least one of the following for a next AMPDU to be transmitted to the device: MCS, signal strength, or transmit power corresponding to one or more hidden nodes. One or more processors (e.g., a processor of the transmitter) may be configured to determine from the information that all MPDUs within the one or more AMPDUs have failed to be received by the device.

[0017] Aspects of the technical solution relate to a device for wirelessly communicating with an access point (AP). The device may include one or more processors coupled to a memory. The one or more processors may be configured to identify a physical protocol data unit (PPDU) created during a current TXOP and waiting to be transmitted to an access point (AP). The one or more processors may be configured to identify a low-latency packet received by the device during the current TXOP, and the low-latency packet is to be communicated to the AP in the next PPDU after the PPDU. The one or more processors may be configured to insert the low-latency packet into the PPDU. The one or more processors may be configured to transmit a PPDU including a low-latency packet to the AP in the current TXOP. The one or more processors may be configured to identify a low-latency packet in the next PPDU scheduled for transmission via the next TXOP after the current TXOP. The one or more processors may be configured to determine that the low-latency packet is inserted into the PPDU. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] These and other aspects and features of embodiments of the present invention will become apparent to those of ordinary skill in the art after reading the following description of specific embodiments in conjunction with the accompanying drawings.

[0019] Figure 1 is an example block diagram of a system for providing feedback enhancement for enhancing the performance of link adaptation, delay-sensitive traffic, and in-device coexistence.

[0020] Figure 2 is a block diagram illustrating the architecture of a computer system that may be used to implement elements of the systems and methods described and illustrated herein.

[0021] Figure 3An example diagram for managing delay-sensitive traffic with a structure of enhanced transmit opportunity (TXOP), protocol data unit (PDU), and aggregated MAC protocol data unit (AMPDU).

[0022] Figure 4 is another example of a diagram for managing delay-sensitive traffic with an enhanced structure of TXOP, PDU, and AMPDU.

[0023] Figure 5 is an example diagram of 802.11 activity bursts and burst limits followed by a period of inactivity.

[0024] Figure 6 Another example of a diagram illustrating an 802.11 activity burst followed by an inactivity period with dynamically adjusted burst duration.

[0025] Figure 7 is an example method for generating a schedule for Wi-Fi communications in response to a communication burst exceeding its allotted time.

[0026] Figure 8 is an example method for a Wi-Fi AP to delay receiving a Block Acknowledgement (BA) for a transmitted AMPDU in response to an IDC problem reported by a UE.

[0027] Fig. 9 An example method for facilitating transmission of low latency packets of a MAC protocol data unit (MPDU) scheduled for transmission at a later time by inserting the low latency packets into an MPDU scheduled for transmission in a current or upcoming TXOP. DETAILED DESCRIPTION

[0028] The following IEEE standards, including any draft versions of such standards, are hereby incorporated by reference in their entirety and made a part of this disclosure for all purposes: Wi-Fi Alliance standards and IEEE 802.11 standards, including but not limited to IEEE 802.11a TM 、IEEE 802.11b TM 、IEEE 802.11g TM 、IEEE P802.11n TM ;IEEEP802.11ac TM ; and IEEE P802.11be TM Draft versions D3.0 to D6.0 of the standards. Although the present disclosure may refer to aspects of these standards, the present disclosure is in no way limited to these standards.

[0029] The embodiments of the present invention should now be described in detail with reference to the figures, which are provided as illustrative examples of the embodiments so that those skilled in the art can practice the embodiments and alternatives obvious to those skilled in the art. The following figures and examples are not meant to limit the scope of the embodiments of the present invention to a single embodiment, but other embodiments are possible by exchanging some or all of the described or illustrated elements or elements obvious to those skilled in the art. Certain elements of the embodiments of the present invention may be implemented partially or completely using known components, and only those parts of such known components that are necessary for understanding the embodiments of the present invention should be described, and detailed descriptions of other parts of such known components will be omitted to avoid confusing the embodiments of the present invention. The embodiments described in their description context should not be limited thereto. For example, unless otherwise specified herein, as will be understood by those skilled in the art, the embodiments described as being implemented in software should not be limited to this implementation, but rather they may include embodiments implemented in hardware or a combination of software and hardware, and vice versa. In this specification, embodiments showing singular components should not be considered restrictive. Instead, unless otherwise explicitly stated herein, the present disclosure is intended to cover other embodiments including multiple identical components, and vice versa. Furthermore, applicant does not intend for any term in the specification or claims to be assigned an uncommon or special meaning unless expressly so stated.In addition, embodiments of the present invention encompass current and future known equivalents of known components referenced herein by way of description.

[0030] A wireless communication device, also referred to as user equipment (UE), may be configured to provide multiple types of wireless communications to a user, including Wi-Fi, Bluetooth, Ultra Wideband (UWB), Long Term Evolution (LTE), License Assisted Access (LAA), New Radio (NR), or New Radio Unlicensed (NR-U). Sometimes, some of these non-W-Fi technologies may be configured to share some UE resources with Wi-Fi functionality on the UE. These shared resources may include, for example, the UE's antenna system, baseband processor or other processing capabilities, power management circuitry, or radio frequency (RF) front-end components (such as filters, amplifiers, and switches), or any other hardware resources that may cause interference between different types of wireless communications. When these shared resources are used for communications conducted by non-Wi-Fi technologies, Wi-Fi communications may have to wait until the shared resources become available to continue their communications. The UE may include a system that supervises and coordinates communication events between these technologies to facilitate in-device coexistence (IDC) between these technologies on the same UE and avoid conflicts or transmission failures.

[0031] Sometimes, wireless communication devices may experience intra-device coexistence issues, where multiple wireless technologies such as Wi-Fi and Bluetooth interfere with each other's operations, resulting in degraded performance and communication inefficiencies. For example, wireless transmissions from non-Wi-Fi technologies may experience incoming communication bursts from their transmitting devices that exceed the time allocated for their wireless communications during a periodic or dynamically occurring duration with which Wi-Fi communications may overlap. A communication burst may include any group (e.g., two or more) of data packets transmitted in a sequence. In such examples, the extended communication burst may encroach on the time interval allocated for Wi-Fi communication. Unless avoided by Wi-Fi communication, such encroachment may lead to IDC problems (e.g., conflicts or overlaps) involving two technologies seeking to use the same shared resources at the same time. In such examples, a Wi-Fi access point that is unaware of the ongoing IDC problem at the device may rely on its predetermined allocated time and continue to transmit data frames for Wi-Fi communication. However, due to the IDC problem caused by the extended communication burst of other technologies, such transmissions may fail, which may cause the Wi-Fi access point to misdiagnose the problem and determine that the device cannot maintain a high data rate, reducing the data rate of the upcoming transmission. Thus, it is beneficial for the device to improve management of IDC issues between different technologies while informing the Wi-Fi access point to allow the Wi-Fi access point to make a more informed assessment of communication issues with the device. The communication bursts in which the second wireless transceiver participates can be periodic with a predetermined schedule (e.g., the first and second schedules) or aperiodic with dynamic burst instances occurring aperiodically.

[0032] Furthermore, in some examples, a wireless communication device or system may be limited because a block acknowledgement (BA) transmitted in response to an aggregate media access point (MAC) protocol data unit (AMPDU) may provide insufficient information regarding the cause of failure of the MAC protocol data unit (MPDU) or the margin for its failure.

[0033] An AMPDU may be an arrangement of multiple MAC protocol data units (MPDUs) organized into a single frame for transmission. An AMPDU may contain an arrangement of any group of data packets to be transmitted as a single burst communication to achieve more efficient communication and improved throughput. The receiver of an AMPDU may send an acknowledgment of a successful transmission back to the sender in the form of a block acknowledgment (BA).

[0034] A block acknowledgement (BA) may include any acknowledgement response (e.g., acknowledgement 126) used to acknowledge or provide a response regarding a received AMPDU transmission. Acknowledgement 126, such as a BA, may include a message or transmission data indicating a single acknowledgement receipt or response for one or more received data frames. A BA may be a feature that allows multiple data frames (e.g., an AMPDU or MPDUs of multiple AMPDUs) to be acknowledged in a single response. The receiver can only provide feedback if at least one of all constituent MPDUs of the AMPDU is correctly received.

[0035] Link adaptation convergence may also be problematic because it may be difficult to efficiently and flexibly try multiple modulation and coding schemes (MCS) or number of spatial streams (NSS) together because each physical protocol data unit (PPDU) with MCS / NSS may be tried one at a time after two lengths of short interframe space (SIFS) (e.g., 2*SIFS) and a gap of BA or SIFS. SIFS or short interframe space may include any fixed time interval used in Wi-Fi communications to separate the transmission of data frames, ensuring efficient and orderly access to the wireless medium. For example, SIFS may be used to allow timely reception of an acknowledgement 126 (e.g., BA) after an AMPDU transmission. For example, a BA for an AMPDU transmission may be expected by a Wi-Fi device to be received at or during a SIFS gap. According to the proposed scheme, non-receipt of a BA may be identified as an IDC problem. After this detection, the technical solution may configure the receiver to allow the BA to be delayed and received during a time period after the SIFS but within the time frame of the delayed time period. When composite feedback for multiple MCS / NSS is available and only when the initiator wishes, the convergence of the link adaptation algorithm may be made faster. The inventive solution may also have high channel state information (CSI) overhead and may lack a finer granularity of MCS.

[0036] For example, a receiver of an AMPDU (e.g., UE 102) may face processing constraints that prevent it from responding with a BA within SIFS after receiving the PPDU of the AMPDU. A physical protocol data unit (PPDU) may include any data frame used for wireless communication, which includes a data packet (e.g., a MAC protocol data unit or MPDU) and any related physical layer information for transmission and reception on a wireless medium. When an AMPDU receiver responds with a BA at SIFS after the PPDU that leads to the AMPDU, the receiver may not be able to do so due to internal processing limitations (e.g., processing delays exceeding SIFS based on MCS / byte count / MPDU count, etc.) that may be triggered by the extended communication burst of the second communication 112. These constraints may prevent the receiver from receiving later MPDUs within a long AMPDU. To address such limitations, a minimum MPDU start interval parameter may be used. The minimum MPDU start interval may be a parameter that takes into account processing constraints. This parameter may specify the minimum interval between any 2 MPDUs (e.g., in microseconds) and is independent of any MCS, bandwidth, or MIMO order, among other factors. Even though spacing may be guaranteed by padding, this may introduce inefficiencies in terms of transmit resources.A technical solution may allow this solution to be performed only when a specified maximum MPDU count or MPDU byte count is exceeded at the receiver, thereby avoiding waste of resources.

[0037] With respect to IDC functionality at a receiver (e.g., UE 102), when an AMPDU receiver is configured to respond with a BA at SIFS after a PPDU that leads to the AMPDU, the receiver may be unable to respond due to an upcoming burst of activity on another in-device technology (e.g., a second communication 112 such as Bluetooth, UWB, LTE, or NR) that may prevent UE 102 from receiving later MPDUs or transmitting BAs due to in-device interference.

[0038] Regarding the handling of non-scheduled triggered receiver (NSTR) clients at the AP, to avoid UL transmissions that may cause destructive interference to the receiver's ongoing reception on another link, the transmitter device may perform continuous DL transmissions to multiple receivers and then trigger BAs in a multi-user (MU) manner instead of sending BAs immediately. Regarding link adaptation convergence, multiple MCS / NSSs may not be tried together, and each combination may be tried one at a time followed by corresponding feedback. Convergence of the link adaptation algorithm may be made faster if composite feedback for multiple MCS / NSSs is available and only when the initiator wishes. Having mandatory intermediate BAs reduces efficiency.

[0039] Limitations of the TXOP / PPDU / AMPDU structure may include a lack of time margin in the medium lock (MLO) of the AMPDU construction. A medium lock duration (MLD) may be prepared to transmit AMPDUs simultaneously on both links, and transmissions with different sets of sequence numbers may have been prepared accordingly. However, if one of the links wins access first, or if the other link becomes busy, an earlier sequence number may be transmitted on the winning link, especially in the case of NSTR / EMLSR MLDs. If the bandwidth to win access to any link is different from the bandwidth assumed when preparing disjoint sets of transmissions for the two links, the AMPDU contents may be assembled again. In some cases, transmitting without reconstruction may result in unnecessary retransmissions of MPDUs or transmitting MPDUs with unnecessary gaps in sequence numbers. A STR MLD that wants to align PPDUs on 2 links may be waiting to decode the length information of a transmission from a NSTR ML device on one of the links (say link 1) while it wins access to the other link (say link 2). If the STR MLD does not align the end of its link 2 transmission with the end of its link 1 reception, then the NSTR ML device that has missed the link 2 preamble may collide with the link 2 transmission.

[0040] The limitations of the TXOP / PPDU / AMPDU structure may make it possible that in MLO, events on link 1 may affect decisions about transmissions on link 2. For example, the MLD may correctly receive a BA on link 1 but not on link 2, and receive the BA in an asynchronous manner. In this case, the transmitter MLD may want the flexibility to prioritize retransmissions of erroneous packets from link 2 even if link 1 transmission starts earlier than the end of link 2 transmission. Furthermore, in MLO and in the case of an NSTR ML receiver, it may be desirable to align the PPDUs on both links so that UL transmission of a BA on one link does not disrupt reception on the other link. Once transmission of a PPDU begins, the LENGTH and content of the AMPDU may not be adjustable because the LENGTH is contained in the L-SIG.

[0041] The handling of delay sensitive transmissions may be such that if delay sensitive traffic newly arrives, it may wait for the ongoing transmission burst / TXOP to end before it may be transmitted. The AMPDU may be constructed as long as possible, since longer AMPDUs improve MAC efficiency by omitting the intermediate PHY header / SFS / BA. For long AMPDUs, if the initial PHY header is missed, decoding may fail for the receiving device, and preamble detection may fail for any device performing CCA. The problem may be particularly evident in the presence of hidden nodes, fading channels, and blind areas in NSTR / EMLSRML devices. Link adaptation convergence may involve multiple MCS / NSSs that cannot be tried together, and each combination is limited to being tried one at a time, followed by corresponding feedback.

[0042] In addition, the receiver may lack control over the burst duration. In-device coexistence (IDC) is affected by the lack of control over long transmit bursts from the AP or triggered by the AP to the receiver. In IDC scenarios with 802.11 and Bluetooth / UWB, there are certain situations where continuous 802.11 medium availability may be limited to a few milliseconds. For example, depending on the Bluetooth profile, the medium availability of 802.11 may be: 2.5ms every 3.75ms or 6.25ms every 7.5ms or 8.5ms every 11ms, etc. It is very likely that long receive packets or RX packet bursts cross 802.11 medium boundaries and are limited by Bluetooth. This may require reducing the Rx packet duration in order to comply with the medium availability of 802.11 (outside the Bluetooth slot or any other coexisting device). Coexistence between 802.11 and Bluetooth / UWB / LTE can be handled in a customized manner.

[0043] Some non-standard implementations may overload existing functionality to indirectly control the duration of Rx / Tx packets. For the downlink, AMPDU aggregation can be reduced, even completely turned off AMPDU / AMSDU aggregation, or the maximum length in bytes can be reduced. This may result in suboptimal performance without solving the actual problem. Even after turning off aggregation, there may be no means to control the duration of a single MSDU, which may be long enough to overflow into the required inactive period. For the uplink, the triggered operating mode can be disabled, which also disables uplink OFDMA, which may be undesirable. If there is a standardized mechanism to support coexistence, the coexistence between 802.11 and BT / UWB can be improved. The same mechanism can be used to solve other problems of coexistence within the device, such as coexistence between 802.11 and LTE / NR. It can also be used to optimize performance in the case where any activity causes a temporary inability to receive / transmit 802.11 frames.

[0044] One aspect of the solution may involve including channel quality indicator (CQI) information into the BA to allow faster convergence of link adaptation by adjusting the modulation scheme and transmit power based on the signal to interference plus noise ratio (SINR) margin. Feedback reporting depends on the frame type and specific considerations, where the corresponding identifier is inserted by the feedback reporter. The timing of the feedback may occur during the SIFS gap after the PPDU, and the error scenarios for reporting feedback are limited. In addition, the solution allows for delayed BA and flexible selection of BA behavior, as well as small PPDUs and compound BAs for back-to-back PPDU sequences, improving link adaptation convergence and efficiency. In this way, the solution of the present invention can improve the performance of wireless communication systems in terms of link adaptation, latency, and coexistence with other technologies.

[0045] The inventive solution may also improve performance in various aspects such as delay-sensitive traffic, multi-link operation, link adaptation, and in-device coexistence by enhancing the existing AMPDU BA mechanism and transmit opportunity (TXOP) structure. For example, the solution may introduce a minimum MPDU start interval parameter to address processing constraints and ensure the interval between MPDUs without wasting transmit resources. For example, the solution may allow the receiver to control the length of the burst using the schedule to be sent to the sender of Wi-Fi communication to adjust the timing of the sender based on the communication burst encroached or prolonged by non-Wi-Fi communication over shared resources. Another enhancement may include the use of delayed BA, where the receiver indicates its limitations to the initiator and the BA transmission is delayed within the negotiated time frame. The solution may include an enhanced TXOP / PPDU / AMPDU structure to allow better handling of delay-sensitive traffic and decoding or clear channel assessment (CCA) failures, as well as faster convergence of the link adaptation algorithm. The inventive solution also proposes semi-static and dynamic adjustment of traffic parameters to optimize coexistence with other in-device technologies.

[0046] The feedback mechanism in 802.11 can provide objective information about the error status of data units (MPDUs), but it is possible to improve it to enhance the overall performance of 802.11 devices. This improvement may involve aspects of 802.11, including link adaptation, latency of delay-sensitive services, and coexistence with other technologies (such as Bluetooth, UWB, LTE, and NR) in the same device. By enhancing the feedback mechanism, 802.11 devices can better adjust their transmission parameters based on wireless channel conditions, optimize data rates, modulation schemes, and channel coding to maximize throughput and maintain stable connections. In addition, improving the latency of delay-sensitive services can allow timely delivery of time-critical data, while optimizing coexistence with other technologies can achieve seamless operation and interference mitigation, allowing 802.11 devices to effectively share the wireless spectrum with Bluetooth, UWB, LTE, NR and other wireless technologies.

[0047] The present solution presents enhancements with respect to feedback to achieve improvements in link adaptation, latency, and in-device coexistence. One aspect of the solution may include performance improvements in latency sensitive services, multi-link operation, link adaptation, and in-device coexistence. Different mechanisms may include enhancements to the existing Aggregate MAC Protocol Data Unit Block Acknowledgement (AMPDU-BA) mechanism and Transmit Opportunity (TXOP) structure to achieve more efficient multi-link operation, latency reduction, link adaptation, and in-device coexistence. Additionally, adjustments to service parameters and TXOPs may be considered to optimize in-device coexistence. By implementing these mechanisms, the present invention may maximize the efficiency and effectiveness of the feedback system to achieve the desired enhancements in 802.11 networks.

[0048] For example, the solution of the present invention can enhance the feedback mechanism to improve link adaptation, latency and in-device coexistence in 802.11 networks. It can include improvements to the existing AMPDU-BA mechanism and TXOP structure to achieve more efficient multi-link operation, latency reduction and better handling of hidden nodes. Integrating the channel quality indicator (CQI) information into the block confirmation (BA) allows faster convergence of link adaptation and enables adjustment of MCS and transmit power based on SINR margin. Feedback reporting may depend on the frame type and specific considerations, where the corresponding identifier is inserted by the feedback reporter. The technical solution can also allow feedback to be inserted even if all MPDUs have errors. For example, even if all MPDUs have errors, the technical solution can also include self-identification of the receiver because the MPDU can include the receiver address or other information that can allow the sender to improve communication and avoid IDC problems. The timing of the feedback occurs during the SIFS gap after the PPDU, and the error scenarios for reporting feedback are limited due to timing, dependence on previous exchanges, and additional PHY header information. The solution also allows delayed BA and flexible selection of BA behavior, such as dynamic per-burst selection. In addition, the inclusion of small PPDUs and compound BAs for back-to-back PPDU sequences enhances link adaptation convergence and efficiency. The initiator can indicate the absence of immediate BA and back-to-back structures in the PHY or MAC header for increased flexibility.

[0049] Depending on the configuration, the transmitter and receiver of the communication may be Wi-Fi 104 or UE 102. For example, both the transmission (e.g., MPDU or AMPDU) and the feedback (e.g., via BA) may be provided by a Wi-Fi AP or a client device (e.g., STA). For example, if Wi-Fi AP 104 is the transmitter of AMPDU, the Wi-Fi AP may perform adjustments based on feedback received from the client. For example, if the client (e.g., UE 102) is the transmitter of AMPDU, the client may perform adjustments based on feedback received from the Wi-Fi AP.

[0050] In some aspects, the inventive solution relates to enhancements to improve performance in the context of delay-sensitive services, multi-link operation, link adaptation, and in-device coexistence. The inventive solution may introduce improvements to the existing AMPDU-BA mechanism and TXOP structure to achieve more efficient multi-link operation, delay reduction, link adaptation, and in-device coexistence, as well as adjustments to service parameters and TXOPs to achieve better in-device coexistence.

[0051] Figure 1 An example of a system 100 for providing feedback enhancement for enhancing performance of link adaptation, delay sensitive traffic, and in-device coexistence is illustrated. The system 100 may include one or more user equipment (UE) 102 communicating with one or more access points (APs) 104 and one or more second communication systems 106 via one or more wireless links 160. The UE 102 may include one or more shared resources 108 coupled to one or more antennas 142. The UE 102 may include one or more Wi-Fi transceivers 120, communication functionality 130, and a second transceiver 110. The second transceiver 110 may include or implement one or more second communications 112. The Wi-Fi transceiver 120 may include or implement one or more Wi-Fi communications 122, which may include one or more transmit units 124 and acknowledgements 126. The communication functions 130 may include one or more Wi-Fi communications 122 and second communications 112 and a schedule 136, which may include one or more first time periods 128 and second time periods 140 for timing Wi-Fi communications. The AP 104 may include one or more communication resources 150 coupled to one or more antennas 142. The AP 104 may also include one or more communication functions 130 that may utilize the one or more schedules 136 and UE information 154 to manage communications with the UE 102 based on the received information. The second communication system 106 may include one or more communication resources 150 coupled to one or more antennas 142 for wireless communications with the UE 102 via a wireless link 160.

[0052] A user equipment (UE) 102 may include a combination of hardware and software designed or configured for wireless communication, such as a device. The UE 102 may include any integrated circuit system, processor, memory, controller, firmware, or software, including computer code with instructions and data, for facilitating wireless communication across a wireless link 160. The UE 102 may be a device including one or more hardware or software shared resources 108, an antenna 142, a transceiver for various types of wireless communications, including Wi-Fi communications 122 that may be implemented using a Wi-Fi transceiver 120 or other wireless communications such as a second communication 112 that may be implemented via a second transceiver 110. The UE 102 may include and utilize a communication function 130 to generate, process, and manage the Wi-Fi communication 122 and the second communication 112 to reduce the occurrence or management of IDC problems (e.g., overlap or conflict between different wireless technologies) and overcome the IDC problems using the communication function 130 and scheduling 136.

[0053] The access point 104 may include any combination of hardware and software for providing or exchanging Wi-Fi communications 122 with the UE 102. The AP 104 may facilitate communications between the UE 102 and a network infrastructure, which may include one or more other networks (e.g., a wired or wireless network, a cellular network, the Internet, or the like). The AP 104 may include or operate as a transceiver capable of sending and receiving data packets via communication resources 150. The communication resources 150 of the AP 104 may include any features or functionality for transmitting or receiving wireless communications, such as antennas 142, transceivers, RF front-end components (e.g., filters, amplifiers, and switches), baseband processors, or power management circuits. The AP 104 may send and receive Wi-Fi communications 122 via the communication resources 150 and its one or more antennas 142. The AP 104 may coordinate the traffic of the Wi-Fi communications 122 between itself and the UE 102 by managing access to the network, assigning IP addresses, and handling security protocols. The AP 104 may include a communication function 130 that may implement functionality to establish and utilize a schedule 136 to communicate with the UE 102 to manage or time wireless communications with the UE 102 .

[0054] The second communication system 106 may include any combination of hardware and software for communicating the second communication 122 with the UE 102. The second communication system 106 may include infrastructure and technology for non-Wi-Fi wireless communications, including components (e.g., communication resources 150) for transmitting and receiving the second communication 112. As in the AP 104, the communication resources 150 may include various wireless communication circuit systems, RF front-end modules, transceivers, and antennas 142, all of which may facilitate data transmission and reception. The second communication system 106 may facilitate the transmission and reception of any second communication 112 (e.g., including communication bursts that may infringe on the time allocated for Wi-Fi communication 122), and may include any of a variety of non-Wi-Fi technologies, such as Bluetooth, UWB, LTE, NR, NR-U, and LAA. The second communication system 106 may establish a wireless link 160 with the UE 102 and utilize the wireless link 160.

[0055] Wireless link 160 may include any wireless interface or communication path established between UE 102 device, AP 104 device, and second communication system 106. Wireless link 160 may facilitate data exchange and connectivity across or including various technologies, such as Wi-Fi communication 122 or second communication 112. The wireless link may facilitate connection to Internet access and local area networks, including via Wi-Fi, UWB, LTE, NR, NR-U, LAA, or other technologies.

[0056] When performing Wi-Fi communications 122, the UE 102 or AP 104 may act as a transmitter or receiver. For example, the UE 102 and AP 104 may each transmit any transmission unit 124 (e.g., AMPDU, PPDU, or low-latency packet) to each other and may receive an acknowledgement 126 (e.g., a BA for the transmitted AMPDU) from each other. For example, if at least one MPDU of the AMPDU has been correctly received, a BA in response to the PPDU or AMPDU reception may be provided. However, the receiver of the PPDU / AMPDU may generally have more information about the details of various individual MPDU receptions or errors, such as information about the difference in signal-to-interference-and-noise ratio (SINR) between what is implemented in the MPDU and the minimum required to support the MCS used in the system or device. The receiver may also be aware of any intermittent interference and its relative strength compared to the signal of interest.

[0057] For example, for each string of errors, if the quantized difference between the required SINR and the achieved SINR exceeds a threshold, the receiver can report it. The transmitter can use this to determine whether there is sudden interference in the middle due to a hidden node or whether the channel is weak, in which case the MCS can be reduced (or if the transmit power is increased). In addition, if the achieved SINR is higher than the required SINR, the receiver can report the minimum difference between the achieved SINR and the actual SINR, so that the transmitter can increase the MCS (or reduce the transmit power without changing the MCS) assuming the minimum achieved SINR. In addition, in the same AMPDU, different SINRs may exist at different times. For example, multiple SINRs may be provided, such as 2 (e.g., one for baseline and one for +OBSS), optionally presenting 0 1 or 2 values. The number of values ​​may be greater than 2, such as 4, 5 or more.

[0058] The shared resources 108 may include any combination of hardware and software of the UE 102 that may be shared or used by a variety of different wireless technologies, such as Wi-Fi, Bluetooth, UWB Ultra Wideband (UWB), Long Term Evolution (LTE), License Assisted Access (LAA), New Radio (NR), or New Radio Unlicensed (NR-U). The shared resources 108 may include any portion of the RF transmit or receive signal chain for any of these wireless communication protocols or technologies that may be utilized by the other two such protocols or technologies. The shared resources 108 may include an antenna system (e.g., antenna 142) and any circuitry for operating the antenna. The shared resources 108 may include radio frequency (RF) front-end components, including any filters, amplifiers, and switches that may be used to manage the different frequency bands or channels used by the Wi-Fi communication 122 or the second communication 112. The shared resources 108 may include a baseband processor for processing RF signals and a power management system for regulating power usage across the transceiver (e.g., 110 or 120).

[0059] The Wi-Fi transceiver 120 may include any combination of hardware and software for providing or implementing Wi-Fi communications 122. The Wi-Fi transceiver in the UE 102 device may include a combined transmitter and receiver unit designed for Wi-Fi wireless communications 122. The Wi-Fi transceiver 120 may facilitate the sending and receiving of Wi-Fi communications 122 over a Wi-Fi network by converting digital data into radio signals for transmission and vice versa for reception. The Wi-Fi transceiver 120 may include components for managing communication protocols, signal processing, and interaction with wireless access points to provide Internet connectivity and data exchange. The Wi-Fi transceiver 120 may utilize shared resources 108 to perform wireless communications.

[0060] The second transceiver 110 may include any combination of hardware and software for providing or implementing the second communication 112. The second communication 112 may include any wireless communication or wireless data exchange utilizing any non-Wi-Fi technology or standard, including, for example, Bluetooth, UWB, LTE, LAA, NE, or NR-U. The second transceiver 110 may manage one or more wireless protocols or standards, including any wireless standards or protocols of Bluetooth, UWB, LTE, LAA, NE, or NR-U, to allow the UE 102 to facilitate connectivity across different networks. The UE 102 may include multiple second transceivers 110, which may be configured for any combination of Bluetooth, UWB, LTE, LAA, NE, or NR-U communications. The second transceiver 110 may utilize the shared resources 108 to perform wireless communications.

[0061] Wi-Fi communications 122 may include any wireless data transmission and reception using radio waves over a local area network (LAN) or any other wireless network. Wi-Fi communications 122 may include wireless communications based on one or more IEEE 802.11 standards. Wi-Fi communications 122 may be implemented via a wireless link 160 (e.g., a wireless local area network connection) using a Wi-Fi access point 104 (e.g., a Wi-Fi wireless router). Wi-Fi communications 122 may include a transmitting unit 124 and an acknowledgement 126 that may be organized or configured according to a Wi-Fi standard (e.g., 802.11).

[0062] The transmission units 124 or frames may be assembled and utilized according to the Wi-Fi communication protocol or standard. For these transmission units, a PPDU (physical protocol data unit) may be included which may encapsulate one or more MPDUs (MAC protocol data units). Acknowledgement messages such as block acknowledgements (BAs) are used to facilitate reliable data delivery.

[0063] Wi-Fi communication 122 may include various communication frames. For example, AMPDU (aggregate MAC protocol data unit), MPDU (MAC protocol data unit), PPDU (physical protocol data unit), PDU (protocol data unit), and BA (block acknowledgement) may be components of wireless communication systems, where MPDUs are aggregated into AMPDUs, which are then transmitted as PPDUs, and the reception of these units is acknowledged by BAs.

[0064] The transmission unit 124 may include any packet format used in Wi-Fi communication 122. The transmission unit 124 may include an AMPDU (aggregate MAC protocol data unit), which may combine multiple MPDUs (MAC protocol data units) into a single transmission to reduce overhead and improve throughput. The transmission unit 124 may include or utilize a PPDU (physical protocol data unit), which may be a physical layer packet carrying an aggregated AMPDU, including any related headers and trailers. The transmission unit 124 may include a low-latency packet designed for time-sensitive data that is desired to be communicated with minimal delay. A low-latency packet may be any data packet configured to reduce or minimize delays during transmission and reception, such as a data packet including a time-sensitive payload configured for higher priority handling during transmission. A low-latency packet may include any packet that is to be delivered with a lower latency than average network traffic or is to be transmitted in priority over other types of network traffic. For example, in real-time voice communications over VoIP, low-latency packets ensure that voice data is transmitted quickly to maintain the quality of the conversation. For example, an AMPDU may include multiple MPDUs for a video stream, while a separate low-latency packet may be used for real-time gaming commands. The communication function 130 may combine various transmit units 124 to improve efficiency and reduce or manage IDC issues or overlap.

[0065] The acknowledgement 126 of the Wi-Fi transmit unit 124 may include any mechanism for confirming data reception or providing feedback information to facilitate reliable communication. The acknowledgement 126 may include a block acknowledgement (BA), which may confirm the reception of multiple MPDUs within an AMPDU and provide a bitmap of successfully received packets. The acknowledgement 126 may include an immediate acknowledgement message (e.g., ACK) for a single packet or a delayed ACK to accommodate scheduling and reduce IDC issues or conflicts. For example, after transmitting an AMPDU, the AP 104 may receive a BA from the UE 102 indicating which MPDUs were correctly received, or it may receive a delayed BA from the UE 102 that is delayed due to an ongoing IDC problem.

[0066] The communication function 130 may include any combination of hardware and software for monitoring the Wi-Fi communication 122 and the second communication 112 and detecting and managing in-device coexistence (IDC) issues. The communication function 130 may include functionality for improving IDC performance, reducing time overlap with respect to the shared resources 108, and reducing any communication conflicts or instances of network traffic reduction or loss. The communication function 130 may take actions to protect the Wi-Fi communication 122 and the second communication 122 from interfering with each other by adjusting (e.g., periodically, dynamically, or based on events) their operating times (e.g., schedule 136) and configurations with respect to frequency bands, channels, or shared resources 108. For example, if the communication function 130 detects a prolonged Bluetooth transmission (e.g., 112) that would interrupt a scheduled or ongoing Wi-Fi communication 122, the communication function 130 may utilize the scheduler 134 to update the first and second time periods of the schedule 136 in order to reschedule (e.g., postpone) the Wi-Fi transmission to avoid interference, thereby maintaining seamless connectivity and performance across the two technologies.

[0067] The communication function 130 may include any combination of hardware and software for controlling, managing, and implementing wireless communications, resource sharing, and improving IDC in the UE 102. The communication function 130 may manage the timing and transmission of the transmit units 124 (e.g., PPDU / AMPDU) and the acknowledgements 126 (e.g., BA). The communication function 130 may modify the transmit units 124 (e.g., repack, rearrange, and repack the AMPDU to include low-latency packets) and modify the acknowledgements 126 (e.g., to include data in the BA). The communication function 130 may detect extended transmission bursts that may exceed the time allocated for the shared resources and take actions to manage IDC issues. The communication function 130 may utilize the scheduler 134 to generate a schedule 136 having a first time period 138 during which the W-Fi communication 122 may be implemented and a second time period 140 (e.g., a time interval of the second communication 112) during which the W-Fi communication 122 will not be implemented.

[0068] The first period 138 may include a burst limit that identifies or corresponds to a point at which Wi-Fi communications are to end within the periodic duration defined by the second period. The burst limit may include any point in time during the first period 138 or at the end of the first period 138. For example, the burst limit may be the point at the end of the first period 138 at which Wi-Fi communications (e.g., both AMPDU transmissions and BA transmissions in response to the AMPDU) are to be completed within the second period 140. The remainder of the second period 140 after the burst limit marking the end of the first period 138 may be used for other purposes (e.g., second or non-Wi-Fi communications). The communication functions 130 may include functions for managing communications, including coordinating delays in acknowledgments 126 (e.g., BAs) regarding AMPDUs and updating BAs to include data regarding various failures or errors.

[0069] The communication function 130 may transmit or receive AMPDU frames during the first time period 138 of the second time period 140 (e.g., periodically), wherein the MPDUs are collected and arranged to form a size according to the burst limit (e.g., at the end of the first time period 138). For example, the communication function 1300 may transmit or receive an AMPDU of the Wi-Fi communication 122 during a next first time period 138 (e.g., a time period 138 in the future or after the second time period 140), the AMPDU including a certain size or being sized or configured to fit in this next first time period 138, while also leaving a portion of the first time period 138 for completing the transmission of a block acknowledgement (BA) for this AMPDU within the same next first time period 138.

[0070] For example, the communication function 130 may insert channel quality indicator (CQI) information from the receiver of the Wi-Fi communication 122 (e.g., AMPDU) into the acknowledgement 126 (e.g., BA), which may provide several benefits. For example, if there is sufficient SINR margin, inserting the information into the acknowledgement 126 (e.g., BA) may help the transmitter increase the MCS to the minimum supported level, resulting in higher data rates and potentially reduced transmit power. If the SINR is below a threshold of the current MCS, the transmitter may reduce the MCS to the maximum supported level to avoid errors and prevent the contention window (CW) from increasing. In Wi-Fi, the CW parameter may correspond to a random wait time that a device must wait before it attempts to transmit. Whenever an error is encountered, the CW may be increased. Therefore, the greater the number of errors, the longer the wait time and the worse the throughput.

[0071] This integration of CQI information facilitates faster convergence of link adaptation. In addition, the BA can inform the transmitter whether the hidden node has started transmitting during the burst or whether the TXOP does not start with an RTS / CTS exchange. In the latter case, if the receiver has virtual carrier sensing network allocation vector (CS NAV) information, it can be embedded in the BA, allowing the transmitter to make an informed decision about continuing to reduce the MCS within the same TXOP or reducing the TXOP to prevent other errors. In addition, if interference from a hidden node occurs in the middle of a burst but ends, producing an error-free MPDU in the latter part, the transmitter can make a decision about reducing the MCS based on the packet error rate (PER) derived from the BA. The solution of the present invention may include additional information about possible causes of failure, such as a sharp change in SINR in the middle of an AMPDU, rather than a small change. Based on such information, the transmitter can conclude whether the failure is due to a hidden node or general channel Doppler.

[0072] For example, the communication function 130 may include information about the SINR margin in the confirmation 126 (e.g., BA). If the SINR achieved is higher than the SINR threshold for a given MCS for a group of MPDUs, a quantized value representing the minimum difference between the SINR achieved and the required SINR may be reported. This information may allow the transmitter to increase the MCS or potentially reduce the transmit power. In the case of an erroneous sequence where the SINR achieved is lower than the SINR for a given MCS, a quantized value indicating the difference between the required SINR and the achieved SINR may be provided. The transmitter may use this information to infer the presence of a hidden node or to make adjustments such as reducing the MCS or increasing the transmit power. In a generalized form, for each string of MPDUs whose achieved SINR values ​​fall within a particular threshold, the quantized difference between the achieved SINR and the required SINR may be reported in the order in which they appear. This reporting mechanism allows one or more such values ​​to be potentially included in a BA.

[0073] The communication function 130 may insert information about the failure or error of MPDU transmission even when all MPDUs of an AMPDU have failed. For example, sometimes, the BA mechanism may include any ACK transmitted by the receiver that at least one MPDU of the AMPDU was correctly received. However, there are occasions when the receiver is able to correctly decode the long training sequence (L-SIG) or other parts of the physical layer (PHY) header even if all MPDUs have errors. Providing an acknowledgment 126 even when all MPDUs at a particular MCS have errors may also help exchange information to achieve better link adaptation, power control, or handling of hidden nodes, and preserve ownership of the medium through appropriate MCS adjustments. This acknowledgment may be enabled by allowing an ACK in the PHY header itself (given the L-SIG and therefore the end time of the PPDU is known, a SIFS after which an ACK may be transmitted). If additional fidelity regarding the end time of the PPDU can be indicated in a new field of the ultra-high rate (UHR) header using a lower MCS (in addition to the indication in the L-SIG / RL-SIG), then it can be achieved. Even if all MPDUS are erroneous, sending confirmation can be implemented for UHR transmitters and receivers. This information can be included in the UHR PHY header to reliably identify the transmitter / receiver.

[0074] The communication function 130 may implement a notification delayed BA mechanism. For example, the communication function 130 of the AMPDU receiver may indicate its limitations to the AMPDU initiator, including the maximum MPDU count, the maximum byte count, the maximum duration that the AMPDU can transmit a BA at SIFS, the minimum delay for BA transmission, the maximum delay, and the intra-device coexistence issues (if any). The communication function 130 of the AMPDU initiator may allow a delayed BA response, for example, if the AMPDU initiator complies with the limitations of the receiver, for example, transmits an AMPDU that falls below the RX-TX delay limit, and the receiver has not signaled the existence of a coexistence issue. The AMPDU initiator may interpret the lack of a BA at SIFS as a failure. Otherwise, the AMPDU initiator may interpret the lack of a BA as a delayed BA.

[0075] The communication function 130 may manage or implement any timing or content-related adjustments for any transmit unit 124 or acknowledgement 126. The reporting of feedback when all MPDUs are in error may depend on the type of frame and specific considerations. For example, for a downlink single-user (DL SU) frame, feedback may be reported based on a previously exchanged recipient within a transmit opportunity (TXOP) or any explicit indication of the addressee in an ultra-high rate (UHR) header. For a downlink multi-user (DL MU) frame, feedback reporting may rely on an indication of the addressee in the UHR header. In the case of an uplink single-user (UL SU) frame without a previous trigger, the feedback reporter may be determined based on a previously exchanged recipient within a TXOP or an explicit indication of the addressee in the UHR header. For a UL SU frame with a previous trigger, the access point (AP) transmitting the trigger or an indication of the addressee in the UHR header may determine the feedback reporter. Finally, for a UL MU frame that may have been a previous trigger, the AP transmitting the trigger or an indication of the addressee in the UHR header may be responsible for reporting the feedback. The feedback reporter inserts the corresponding identifier in the feedback accordingly.

[0076] The communication function 130 may manage the timing of any acknowledgement 126 or feedback. The recipient of the feedback may be omitted from the reported feedback because the entity that transmitted the previous PPDU may know and may recognize that the feedback is intended for itself based on the identification inserted in the feedback. The timing of the feedback report may occur during a SIFS gap derived from the long training sequence (L-SIG) or reverse long training sequence (RL-SIG) and other parts of the physical layer (PHY) header after the end of the PPDU. Due to the timing of the response, the reliance on the previous exchange, and the additional PHY header information, the error scenarios for reporting feedback may be limited.

[0077] The communication function 130 may facilitate the transmission of multiple AMPDUs with only a single BA as a response. For example, an initiator device or system may not want a BA after a SIFS because the initiator may intend to send a sequence of AMPDUs (without gaps or SIFS gaps) in order to perform MCS exploration for link adaptation, improving decoding / CCA. In such instances, the initiator may indicate a pre-set / expectation for delayed BAs to the receiver indicating this capability (e.g., an indication in the PHY header or MAC header). This may provide greater flexibility than setting ACK policy = Block ACK (within the HT immediate context) because the latter pre-set may mean that no AMPDUs can be acknowledged with an immediate BA, but instead must be acknowledged with a BAR-SIFS-BA combination.

[0078] For example, the communication function 130 of the initiator may transmit the transmit unit 124 again after a SIFS gap or even without any gap. The initiator may later elicit an acknowledgement 126 (e.g., a BA), e.g., by using implicit BAR / explicit BAR, and optionally allow the recipient to initiate a BA transmission, e.g., within the recipient's own TXOP. In some examples, the difference between existing delayed BA procedures and the inventive solution is that the solution allows for dynamic per-burst behavior regarding the selection of the BA (i.e., whether immediate or delayed), whereas the existing procedures force the BA of each burst to be either immediate or delayed BA, depending on the BA protocol establishment.

[0079] The communication function 130 may provide or facilitate sizing of the PPDU to improve efficiency. For example, a short PPDU may precede a longer PPDU with or without a SIFS gap in between. Inserting SIFS+BA+SFS between two AMPDUs may be avoided. This may also cause problems for synchronized MLD receivers. Having the flexibility to insert a small PPDU at the beginning, after which a PPDU with the desired final length and content may appear, is helpful. Such implementations may facilitate improved link adaptation convergence. For example, if composite feedback is available for a sequence of back-to-back PPDUs (AMPDUs) with multiple MCS / NSSs, the convergence of the link adaptation algorithm may be made faster. The transmitter may encapsulate back-to-back PPDUs, each with a different MCS / NSS combination, without any gaps or with a SIFS gap. At the end of a burst, a composite BA may be drawn, which may help the transmitter know which MCS / NSS combination was the most successful. Not having an intermediate BA (and SIFS) may help improve efficiency. In some link adaptation algorithms, multiple iterations may be used to obtain the correct MCS after one AMPDU, since the BA can only give information about the success / failure rate of the MCS, but not about the margin. In the absence of this enhanced BA, many iterations of the AMPDU-BA may be needed to reach the optimal MCS / NSS. The initiator may dynamically indicate in the PHY or MAC header that there is no immediate BA and back-to-back structure. This may provide higher flexibility than setting Acknowledgement Policy = Block Acknowledgement (within the HT Immediate Context), since the latter presetting means that no AMPDU can be acknowledged with an Immediate BA, but instead must be acknowledged with a BAR-SIFS-BA combination.

[0080] If the communication function 130 of the AMPDU initiator interprets the absence of a BA as a delayed BA, it may be assumed that the missing BA will be transmitted by the recipient using contention or triggered by a BAR after the negotiated minimum delay X and before the maximum delay Y. Expiration of the maximum delay may cause the assumed AMPDU at the initiator to be erroneous. It may continue its TXOP (i.e., after SIFS) to transmit the next PPDU to the same recipient or other recipients.

[0081] The communication function 130 of the AMPDU receiver may sometimes apply a delayed BA. For example, if the receiver transmits the BA within a SIFS, the BA may indicate the last processed sequence number of the AMPDU (<= the last sequence number in the AMPDU). Otherwise, when transmitted, the BA may be cumulative in terms of ACK information, for example, if additional AMPDUs arrive before the BA is transmitted.

[0082] The communication function 130 of the initiator may not want a BA after SIFS because it may intend to send a sequence of AMPDUs (without gaps or SIFS gaps), for example, to handle delay-sensitive traffic, MCS exploration for link adaptation, improved decoding / CCA. In addition, there may be known receiver limitations and AMPDU content, such as the AMPDU exceeds the receiver maximum byte count. In this case, the initiator may indicate (to the receiver indicating the capability) the pre-set / expectation for delayed BA. For example, there may be an indication in the PHY header or MAC header. After signaling, the initiator is free to transmit again after SIFS or even without any gap. The initiator may elicit the BA later, for example, when using implicit BAR / explicit BAR. Optionally, it may allow the receiver to initiate the BA transmission, for example, within the receiver's own TXOP.

[0083] The communication function 130 may facilitate an enhanced TXOP / PPDU / AMPDU structure. For example, a short PPDU (AMPDU) may precede a longer PPDU (AMPDU) with or without a SIFS gap in between. Inserting SIFS+BA+SFS between two AMPDUs may result in losses. It may also cause problems for synchronized MLD receivers. It may help if a small PPDU can be inserted flexibly at the beginning, after which a PPDU with the desired final length and content may follow. Advantages of the solution of the present invention may include a time margin for the AMPDU initiator to establish / rebuild the AMPDU based on the link that won channel access and the bandwidth it won channel access with or while waiting for decoded length information for alignment purposes. One option is for the AMPDU initiator to react to asynchronous events on multiple links of the MLD. Thus, the MLD may temporarily use a small PPDU at the beginning of link 1 transmission, and follow up with a larger PPDU depending on the ACK status on link 2.

[0084] The communication function 130 (e.g., of the UE 102 device) may detect a communication burst (e.g., 112) received by the second wireless transceiver 110 that exceeds a time period allocated for the second wireless communication 112. The UE 102 device may communicate with the AP 104 to receive the Wi-Fi communication 122. For example, the UE 102 may be configured and scheduled to receive the Wi-Fi transmission 122 during a time interval that has been exceeded or encroached by a communication burst from the second communication system 106. For example, the communication function 130 may detect that the second communication burst received by the second wireless transceiver 110 overlaps with a portion of the first time period allocated to receive the Wi-Fi communication 122 from the AP 104 according to a predetermined schedule 136. The communication function 130 may utilize the scheduler 134 to adjust the schedule 136 in response to the overlap. This updated schedule 136 may be transmitted to the AP 104 for use by the AP 104 to avoid conflict or overlap with the second communication burst (e.g., 112) at the UE 102.

[0085] For example, the communication function 130 may receive an AMPDU for the Wi-Fi communication 122. The AMPDU may be received during the next first time period of the periodic schedule 136, which includes a first time period 138 for receiving the Wi-Fi communication 122 within the second time period 140 that creates the periodicity. The AMPDU may include a size adjusted according to the next first time period. For example, the communication function 130 may determine the amount of the remaining portion of the first time period 138 and generate the AMPDU to fit within the remaining portion of the first time period 138 without exceeding it. In this way, by maximizing the use of the amount of the first time period 138 dedicated to the Wi-Fi communication 122, the communication function 130 may improve the throughput and data rate. The sender (e.g., the AP 104 or the UE 102) may insert an AMPDU of this size in an upcoming first time period 138 (e.g., in the next first time period 138). For example, the communication function 130 may receive an AMPDU for the Wi-Fi communication 122 during the next first time period, the AMPDU including a size that is established or configured (e.g., maximized so that it is formed using a maximum number of packets) to conform to the next first time period and that allows transmission of a block acknowledgement (BA) for the AMPDU to be completed within the next first time period.

[0086] The communication function 130 may detect that a second communication burst (e.g., 112) received by the second wireless transceiver 110 overlaps with a portion of a first time period 138 allocated according to a schedule 136 to receive Wi-Fi communications 122 from the AP 104. The communication function 130 may utilize the scheduler 134 to adjust the schedule 136 in response to the overlap. For example, the communication function 130 may adjust the timing of the start of the first time period 138 to avoid interference or overlap with the second burst. The updated schedule 136 may be transmitted to the AP 104 so that the communication function 130 of the AP 104 can manage the Wi-Fi communications 122 to the UE 102 so that transmissions from the AP 104 do not conflict with the second communication burst received via the shared resources 108 of the UE 102. The communication function 130 may receive the AMPDU of the Wi-Fi communication 122 from the sender, generate a block acknowledgement (BA) for the AMPDU, and then communicate the schedule to the sender (eg, the AP 104 or the UE 102) via the BA (eg, 126).

[0087] The communication function 130 may detect a second communication burst 112 received by the second transceiver 110 that exceeds a second time period allocated to the second wireless communication 112. The communication function 130 may determine a second schedule 136 in response to the detection of the second communication burst. The AP 104 may transmit Wi-Fi communications 122 to the UE 102 device via a second channel of the plurality of channels of the wireless link 160 according to the second schedule. The second schedule may include a second burst limit for a third time period based on a second second periodicity of a fourth time period. The communication function 130 may communicate the second schedule to the access point.

[0088] The communication function 130 of the AP 104 may modify the processing of the AMDPU transmission in response to information (e.g., via the acknowledgement 126) from the UE 102 indicating the existence of an IDC problem (e.g., overlap or collision). For example, the AP 104 may have a communication function 130, which may be implemented using one or more processors coupled to a memory. The communication function 130 may receive a block acknowledgement (BA) (e.g., 126) from the UE 102 device. The BA may include information identifying the existence of an intra-device coexistence problem on the device. The IDC may include, for example, a detected encroachment event of a second communication 112 (e.g., a communication burst received from the second communication system 106) via the shared resource 108 (including the antenna 142). The communication function 130 may determine, in response to identifying the intra-device coexistence problem, to allow one or more BAs (e.g., 126) from the UE 102 device to be delayed for more than SIFS in response to one or more AMPDUs from the AP 104. The communication function 130 may determine to allow one or more BAs (eg, 126) to arrive late without being identified as a failure (eg, without identifying the AMPDU transmission as a failed, incomplete, or dropped transmission).

[0089] The communication function 130 may receive a second BA from the UE 102 device after the SIFS and in response to the determination. The second BA (e.g., 126) may include multiple acknowledgments (e.g., BAs) corresponding to the multiple AMPDUs received from the AP. For example, after determining by the communication function 130 not to mark or identify the transmitted AMPDUs as failed transmissions despite the late or missing BAs (e.g., acknowledgments 126) at this time, the communication function 130 may receive a BA for those missing or late AMPDUs after a time threshold (e.g., an expected BA time threshold). The communication function 130 may determine, in response to the determination, that the multiple transmissions of the multiple AMPDUs were successful regardless of the second BA received after the SIFS.

[0090] When the communication function 130 receives information (e.g., via a BA) that the UE 102 will delay transmitting a BA to a previously transmitted AMPDU, the communication function 130 may determine to serve the other UE 102 instead. For example, the communication function 130 may receive a block acknowledgement (BA) from a second UE 102 device including information that no intra-device coexistence issues on the second device were identified. The communication function 130 may transmit an AMPDU (e.g., 122) to the second UE 102 device. The communication function 130 may determine to implement such transmission to the second UE 102 in response to determining that the (first) UE 102 is delaying its BA transmission. The communication function 130 may determine that a BA for the AMPDU is not received within a SIFS. The communication function 130 may identify that the transmission of the AMPDU has failed in response to not receiving a BA within a SIFS.

[0091] The communication function 130 may recognize that the device is configured for Wi-Fi communication, wherein transmission of one or more BAs for one or more AMPDUs is delayed until after one or more SIFS after the one or more AMPDUs. The communication function 130 may transmit, in response to the configuration, a preset that communicates the plurality of AMPDUs according to the configuration. The preset may be indicated in at least one of a header of a physical layer or a header of a medium access control header of an AMPDU in the plurality of AMPDUs.

[0092] The communication function 130 of the receiver of the BA may identify channel quality information indicating a signal-to-interference-and-noise ratio (SINR) margin from information (e.g., inserted into the BA by the communication function 130 of the sender). The communication function 130 of the receiver may adjust a modulation and coding scheme (MCS) for transmission to the device in response to the SINR margin. The communication function 130 of the receiver of the BA may identify an indication corresponding to at least one of the following from the information in the BA: a modulation and coding scheme (MCS) for transmission to the device, a signal strength of one or more AMPDUs, or the presence of one or more hidden nodes. The communication function 130 of the receiver of the BA may adjust at least one of the following for the next AMPDU to be transmitted to the device in response to the indication: an MCS, a signal strength, or a transmit power corresponding to a hidden node. The communication function 130 of the receiver of the BA may determine from information edited or adjusted by the communication function 130 of the sender received via the BA that all MPDUs within the one or more AMPDUs have failed to be received by the device.

[0093] The communication function 130 may identify a low-latency packet received by the UE 102 device during the current TXOP. The low-latency packet may be determined to be communicated to the AP 104. The communication function 130 may identify a physical protocol data unit (PPDU) created during the current TXOP and waiting to be transmitted to the AP 104. The communication function 130 may insert the low-latency packet into the PPDU. The communication function 130 may transmit the PPDU including the low-latency packet to the AP within the current TXOP. The communication function 130 may identify a low-latency packet within a second PPDU scheduled for transmission via a next TXOP after the current TXOP and determine to insert the low-latency packet into the PPDU.

[0094] The scheduler 134 may include any combination of hardware and software for generating a schedule 136 that allocates specific time periods to different types of wireless communications. The scheduler 134 may include functionality for generating a first time period 138 and a second time period 140 in order to improve IDC and minimize IDC issues, overlaps, or network conflicts that may result in network packet loss or discards. The scheduler 134 may generate a schedule 136 that may define, identify, or set the first time period 138 and the second time period 140, any periodicity or repetition of the time intervals, and any changes to the schedule 136. The schedule 136 may include a first time period 138 during which the scheduler notifies a Wi-Fi access point (AP) 104 of available time for Wi-Fi communication 122 and a second time period 140 designated for other communications, such as Bluetooth or LTE. For example, the scheduler 134 may generate a schedule 136 having a second period 140 that repeats every 20 milliseconds, within which a first period 138 of 5 milliseconds may be allocated for Wi-Fi communication 122, while the remaining 15 milliseconds of the second period 140 may be allocated for other wireless communications, such as Bluetooth or LTE.

[0095] The schedule 136 generated by the scheduler 134 may include any organized time interval or structured plan that allocates specific time intervals to specific wireless communications to facilitate IDC with respect to the shared resources 108 within the UE 102. The schedule 136 may include a first time period 138, which may identify time intervals dedicated to Wi-Fi communications 122 (e.g., transmissions of transmit units 124 from the Wi-Fi AP 104 and acknowledgements 126 from the UE 102). The Wi-Fi AP 104 may utilize the schedule 136 to synchronize or time when transmit units 124 (e.g., AMPDUs, low-latency packets) are transmitted to the UE 102 and when acknowledgements 126 (e.g., BAs) are expected to be received. The schedule may include periodic time intervals. The periodic time intervals may be defined by a second time period 140 that includes the first time period 138. The periodic time intervals may be defined by the duration of the concatenated first time period 138 and the second time period 140, where the first time period 138 corresponds to a Wi-Fi communication time interval and the second time period 40 corresponds to a second communication time interval.

[0096] The scheduler 134 may update the schedule 136 or generate a new schedule 136 based on the IDC event or problem. For example, the communication function 130 may generate a burst limit in response to a detected communication burst (e.g., 112). For example, the communication function 130 may determine a schedule 136 for the AP 104 to transmit Wi-Fi communications 122 to the UE 102 device in response to detecting that a communication burst received by the second wireless transceiver 110 exceeds a time period allocated for the second wireless communication 112. The schedule 136 may include a burst limit for a first time period 138 based on the periodicity of the second time period 140. The communication function 130 may receive the schedule 136 from the scheduler 134 and communicate the schedule to the access point using the Wi-Fi transceiver 120.

[0097] The first time period 138 may be allocated by the scheduler 134 for receiving Wi-Fi transmissions 122. The second time period 140 may correspond to the duration between the start of the first time period 138 and the start of a next first time period 138 based on the periodicity of the second time period 140. The next first time period 138 may be the first time period 138 of the next time period in the plurality of time periods consisting of the plurality of concatenated second time periods 140 time lengths. The next first time period 138 may be allocated for receiving any future Wi-Fi communications 122.

[0098] The first time period 138 may include, mark or indicate a burst limit 502, e.g. Figure 5 1. The burst limit 502 may include a time limit up to which Wi-Fi communications 122 may be communicated within the second time period. The burst limit 502 may mark the end of the first time period 138 and the beginning of the remainder of the second time period 140 during which no Wi-Fi communications are exchanged. The burst limit 502 may be established with reference to the beginning of at least one of the first time period 138 or the second time period 140. The burst limit 502 may mark a duration or interval allocated to Wi-Fi communications within a periodicity.

[0099] The scheduler 134 may adjust the schedule in response to the detected overlap between the second communication 112 and the Wi-Fi communication 122 with respect to the shared resource 108. For example, the scheduler may detect (e.g., via the communication function 130) that a second communication burst received by the second wireless transceiver overlaps with a portion of a first time period allocated according to the schedule to receive Wi-Fi communications from the AP. The scheduler 134 may update the schedule 136 or generate a new schedule 136 for receiving the Wi-Fi communication 122 via a first communication channel of a plurality of communication channels. The scheduler 134 may generate a schedule 136 for receiving the Wi-Fi communication 122 via a particular communication band of a plurality of communication bands (e.g., of Wi-Fi). The schedule 136 may be adjusted to change at least one of the duration of the first time period 138 or the duration of the second time period 140 according to the duration of the second communication burst.

[0100] The second period 140 may include the first period 138 and define an overall timing including a periodic or repeating interval to facilitate synchronous communication between the Wi-Fi AP 104 and the UE 102. The second period 140 may include a time interval including a portion of the time interval during which Wi-Fi communication 124 is allowed (e.g., the first period 138). The second period 140 may include a portion of the time interval during which Wi-Fi communication 124 is not allowed, such as the remainder of the second period 140 other than the first period 138 time interval. For example, the second period 140 may include or correspond to a time interval during which Wi-Fi communication 122 is not allowed (e.g., the time allocated for the second communication 112 at the UE 102). For example, the scheduler 134 may provide a schedule defining a second period 140 that repeats every 10 milliseconds, within which 4 milliseconds of the first period 138 are allocated for Wi-Fi communication 122, and the remainder of the second period 140 (e.g., 6 milliseconds) is not used for Wi-Fi communication 122. This approach ensures that the Wi-Fi transceiver 120 and other wireless transceivers do not interfere with each other, maintaining efficient and effective use of the device's shared resources.

[0101] Figure 2A block diagram of an example computer system 200, which may also be referred to as a computing system 200, is illustrated. The computer system 200 may include or be used to implement any computation or processing (e.g., commands, protocols, or data processing) of the system 100 described herein. The computer system 200 may be included in or run any device or system discussed herein (e.g., a UE 102, an AP 104, or a second communication system 106). The computer system 200 may be used to operate, implement, or communicate the functionality of the communications 112 or 122 and the communications functions 130 on any device or platform (e.g., a user's mobile device, a server, a virtual server, a cloud infrastructure, or any other system or service).

[0102] The computing system 200 may include at least one bus data bus 205 or other communication components for communicating information and at least one processor 210 or processing circuit coupled to the data bus 205 for processing information. The computing system 200 may include one or more processors 210 or processing circuits coupled to the data bus 205 for exchanging or processing data or information. The computing system 200 may include one or more main memories 215, such as random access memory (RAM), dynamic RAM (DRAM), or other dynamic storage devices, which may be coupled to the data bus 205 for storing information and instructions to be executed by the processor 210. The main memory 215 may be used to store information (e.g., data, computer code, commands, or instructions) during execution of instructions by the processor 210.

[0103] Computing system 200 may include one or more read only memories (ROMs) 220 or other static storage devices coupled to bus 205 for storing static information and instructions for processor 210. Storage device 225 may include any storage device, such as a solid-state device, magnetic disk, or optical disk, that can be coupled to data bus 205 to persistently store information and instructions.

[0104] The computing system 200 may be coupled to one or more output devices 235 via the data bus 205, such as a speaker or a display (e.g., a liquid crystal display or an active matrix display) for displaying or providing information to a user. An input device 230 (e.g., a keyboard, a touch screen, or a voice interface) may be coupled to the data bus 205 for communicating information and commands to the processor 210. The input device 230 may include, for example, a touch screen display (e.g., output device 235). The input device 230 may include a cursor control such as a mouse, a trackball, or cursor direction keys for communicating direction information and command selections to the processor 210 to control cursor movement on the display.

[0105] The computer system 200 may include input / output ports 240, also referred to as I / O ports 240, which may include physical interfaces that facilitate or provide communication between external or peripheral devices and the processor 210 and / or memory 215. The I / O ports 240 may be connected to the data bus 205, allowing data to be transferred between the processor 210, the memory 215, and any external devices, such as a keyboard, a mouse, a printer, and external storage devices. The computer system 200 may also include one or more network interfaces 245 coupled via the data bus 205. The network interface 245 may include any physical or virtual components that enable communication between the computer system 200 and any external network, such as the Internet. The network interface 245 may provide data transfer between the processor 210, the memory 215, and any external network.

[0106] The processes, systems, and methods described herein may be implemented by the computing system 200 in response to the processor 210 executing an instruction arrangement contained in the main memory 215. Such instructions may be read into the main memory 215 from another computer-readable medium, such as the storage device 225. The execution of the instruction arrangement contained in the main memory 215 causes the computing system 200 to perform the illustrative processes described herein. One or more processors 210 in a multi-processing arrangement may also be used to execute the instructions contained in the main memory 215. Hard-wired circuitry may be used in place of or in combination with software instructions and the systems and methods described herein. The systems and methods described herein are not limited to any specific combination of hardware circuitry and software.

[0107] although Figure 2 An example computing system has been described in the specification, but the subject matter including the operations described in this specification may be implemented in other types of digital electronic circuit systems or computer software, firmware, or hardware (including the structures disclosed in this specification and their structural equivalents), or a combination of one or more of them.

[0108] Figure 3 and 4 The illustration shows example diagrams 300 and 400 of a low-latency packet 302 originally prepared or intended for transmission in a next PPDU 308 or next TXOP 310 being inserted into a previous or current PPDU 304 scheduled for transmission in a current TXOP 306. Figure 3In example 300 of , a PDU / PPDU 304 may be created or desired for transmission in a current TXOP 306 and may contain its own network packet. Each PPDU may include a PPDU header 312, which may include information about its contents and may be organized as an AMPDU with multiple MPDUs. For example, a low-latency packet may be part of an MPDU of a next PPDU 308, which may correspond to a next AMPDU and may be inserted into the AMPDU of the current PPDU 304 (e.g., along with any related data, such as a part of a PPDU header 312 of the next PPDU 308 that is related to the low-latency packet). Following the PPDU 304 or PPDU 308 may be a BA 314 corresponding to the given PPDU, which may be transmitted by the receiver in response.

[0109] Figure 3 Also shown is a next PPDU 308 that may be scheduled for transmission after the current PPDU 304. The next PPDU 308 may be scheduled for transmission in the current TXOP 306 or in the next TXOP 310. The next PPDU 308 may include a low-latency packet 302 that is scheduled or intended to be transmitted with the next PPDU 308, such as in the next TXOP 310. However, the technical solution provides an enhanced TXOP / PPDU / AMPDU structure in which the low-latency packet 302 may be taken out of the next PPDU 308 and inserted into the current TXOP 306. This may be done by the communication function 130 in response to determining that the packet in the next PPDU 308 is a low-latency packet and there is space, time, or opportunity to include the low-latency packet in the current PPDU 304, such as Figure 4 When inserting a low-latency packet, the PPDU header 312 of the next PPDU 308 may be included in the low-latency packet to provide at least a portion of the PPDU header 312 information about the low-latency packet within the current PPDU 304.

[0110] Figure 3 and 4 Techniques are presented for handling latency sensitive traffic, allowing transmission of multiple PPDUs with SIFS gaps or no gaps between them. This technique may help better prioritize latency sensitive traffic and reduce latency (e.g., by improving transmission rate and throughput). For example, this technique may allow insertion of latency sensitive traffic in an ongoing transmission or in a previous PDU, rather than waiting for the ongoing transmission burst / TXOP to end. When low latency packets are expected, a long PPDU in a TXOP may be broken into a sequence of shorter PPDUs to allow insertion of low latency traffic.

[0111] The inventive solution may include decoding of clear channel assessment (CCA) failures for long AMPDUs / PPDUs. For example, if instead of a long PPDU, a sequence of shorter back-to-back PPDUs with no gaps or with SIFS gaps followed by a single composite BA can be transmitted, such issues may be mitigated. Even if any of the middle PPDUs are in error, the remaining ones may be decoded. This may result in better throughput at the receiver in case of fading / dynamic channels. This may also help avoid collisions through preamble detection, such as in case of blind spots in NSTR / EMLSR ML devices, because such devices may decode multiple preambles instead of just one for the same amount of data transmitted, and without the overhead of repeating SIFS+BA.

[0112] If composite feedback is available for a sequence of back-to-back PPDUs (AMPDUs) with multiple MCS / NSS, the convergence of the link adaptation algorithm can be made faster. The transmitter can pack back-to-back PPDUs, each with a different MCS / NSS combination, without any gaps or with a SIFS gap. At the end of the burst, a composite BA is drawn, which helps the transmitter know which MCS / NSS combination is the most successful. No intermediate BA (and SIFS) can help improve efficiency. The flexibility of the NSTR ML receiver can avoid UL transmissions from a receiver that may cause destructive interference to the receiver's ongoing reception on another link. The initiator can perform continuous DL transmissions to multiple receivers and then trigger BAs in MU mode.

[0113] The inventive solution may involve semi-static adjustment of traffic parameters without the need for reassociation. It may be desirable to have a semi-static limit on the duration of a burst to / from an associated non-AP, regardless of the number of bytes or the degree of MSDU / MPDU aggregation. A new action frame may be defined for semi-statically changing the downlink burst duration that can be supported by a non-AP in a coexistence environment. A similar procedure may also be used to semi-statically adjust the duration limit of a triggered uplink. This may reduce or eliminate the need to completely deactivate the triggered uplink. In addition to the downlink / uplink burst duration, it is also beneficial to indicate the required periodicity of downlink / uplink activity. For example, a non-AP may have a burst duration of up to x ms in every y ms, so that for non-802.11 operation, at least (yx) ms are available every y ms. The supported burst parameters may be on a per-link / per-channel / per-band basis, since each link / channel / band may have different in-device coexistence issues (regarding different technologies such as BT / UWB / LTE / LAA / NR / NR-U).

[0114] Figure 5An example of a transmission diagram 500 is illustrated according to a negotiated burst limit 502 for bursty communication (e.g., in a large AMPDU transmission). The burst limit 502 for bursty communication may be defined by setting a duration, e.g., x ms (e.g., first time period 138) and each periodic time length, e.g., y ms (e.g., second time period 140), as shown in the example 500. The diagram 500 may show a burst of activity up to an amount of "x" milliseconds (e.g., the duration of the first time period 138), followed by (yx) milliseconds of inactivity (e.g., a portion of the second time period 140 after the end of the first time period 138). The burst limit 502 of the diagram 500 and the first and second time periods 138, 140 may be represented as, included in, or correspond to the schedule 136.

[0115] The solution of the present invention may involve dynamic adjustment of burst duration. A device with an IDC constraint or problem may dynamically request a reduction in the remaining burst duration. The remaining burst duration may be indicated by a CTS or BA in response to a downlink transmission. In the CTS instance, the initial TXOP duration is contained in the RTS, and the responder with the IDC constraint suggests how much remaining TXOP duration it prefers, resulting in a dynamic reduction of the TXOP. In the BA instance, the transmission may start with a shorter DL burst, and in the BA, the responder suggests the remaining TXOP duration. The remaining burst duration may be indicated in the uplink packet transmitted in response to the trigger frame. The remaining burst duration may be used for downlink transmissions to or uplink transmissions from this device facing the IDC constraint. It may also be beneficial to indicate the required inactivity time after the current burst is completed. This may also be used as an absence notification.

[0116] Figure 6 An example diagram 600 illustrates dynamic adjustment of burst duration and inactivity periods. Figure 6 In the 802.11 PPDU, the remaining burst duration and the time until the preferred next start of 802.11 activity may be indicated using a BA in response to the AMPDU. In the same manner, these parameters may be indicated in a CTS in response to an RTS and in a TB PPDU in response to a trigger frame. In such examples, additional considerations may be included. For example, if the remaining burst duration is reduced after the medium is reserved for a longer duration using an RTS, then unused air time reserved for a particular non-AP may be left after the end of the burst. However, in that case, the CF end may be used by the AP in order to make this remaining duration available to other devices on the channel. The AP may also use this remaining reserved time for other exchanges (i.e., exchanges with other non-APs).

[0117] In 802.11bn, the AMPDU-BA exchange mechanism may allow the receiver to indicate constraints on immediate BA transmission, maximum MPDU count, maximum byte count of AMPDUs that meet SIFS, response time for BA transmission, minimum delay for BA transmission, maximum delay, and intra-device coexistence issues. The initiator indicates in the PPDU that BA transmission at SIFS after the PPDU may not be permitted.

[0118] 802.11bn AMPDU-BA exchange mechanism may allow PPDUs to be transmitted by AMPDU initiators without any intervening gaps or with SIFS gaps, where each PPDU is allowed to have different MCS / NSS / duration. New action frame for semi-statically changing downlink / uplink burst duration that may be supported by non-APs in a coexistence environment. In addition to burst duration, the preferred periodicity of the burst may also be indicated. Supported burst parameters may be per link / per channel / per band.

[0119] The support mechanism or field dynamically indicates the remaining required downlink / uplink burst duration immediately following the current transmission of the non-AP that can be supported by the non-AP in a coexisting device environment. The field may be included in a CTS, BA, or TB PPDU. In addition to the remaining burst duration, the preferred next occurrence of the burst may also be indicated.

[0120] The technical solution may use delayed block acknowledgment messages, for example, using a system combination that may include 802.11 devices and components (e.g., processing units, transceivers, antennas, receive and transmit process chains, data transmission and management components, etc.) to improve the efficiency of delay-sensitive traffic transmission. The technical solution may receive information indicating a block acknowledgment (BA) delay and include the transmission of an AMPDU. The technical solution may identify that the BA of the AMPDU is within a delay range, determine that the BA is delayed and include a postpone error message.

[0121] Aspects of the technical solution relate to in-device coexistence (IDC) optimization for concurrent client and mobile access point situations. In particular, the technical solution provides systems and methods for optimizing or improving the IDC of a device operating simultaneously as a mobile AP and a client connected to an infrastructure AP on the same link. The solution provides improved and efficient coordination between two WLAN (e.g., Wi-Fi) connections based at least on factors such as channel overlap and the impact of additional wireless technologies (e.g., Bluetooth or ultra-wideband). To simplify communications, the technical solution may utilize Wi-Fi 8 features to provide dynamic and periodic unavailability scheduling between a device and both an infrastructure AP and a peer-to-peer (P2P) client. By sending a control frame (CF) or control response (CR) with availability scheduling, a device may minimize latency and overhead associated with an independent communication channel. The technical solution may allow coordination of IDC constraints across connections to facilitate consistent operation and maximize resource utilization.

[0122] The technical solution is directed to systems and methods for optimizing intra-device coexistence (IDC) in a device that simultaneously acts as a mobile AP and a client connected to an infrastructure AP on the same link (e.g., a UE 102 that acts as a tethered connection for another UE 102). The Wi-Fi ecosystem may have many examples where a device plays the role of both a client connected to an infrastructure AP and a mobile AP that provides Wi-Fi connectivity to more distant or private peer clients. This may be referred to as "tethering" because the intermediate device tethering may be two communication links of Wi-Fi, wired, or cellular. The technical solution may be directed to a case where both links being tethered may be Wi-Fi links. In an example, the configuration may be as follows: AP 104←Wi-Fi link (e.g., 160)→[client / mobile AP (e.g., UE 102 tethered as AP]←Wi-Fi link (e.g., 160)→[P2P client (e.g., another UE 102)]. An intermediate client / mobile AP (e.g., UE 102 tethered device) may multitask between two Wi-Fi links that may be on the same channel or on different channels. The same channel overlap may include coordination between the two links. Even when different links are used for the two links, there may be hardware constraints at the intermediate client / mobile AP (e.g., tethered UE 102), which may trigger coordination of activities on the two links. Technical solutions may utilize or deploy communication functions 130 at the intermediate tethered UE 102 to reduce or resolve IDC issues and improve throughput performance using the technical solutions discussed herein.

[0123] An intermediate client / mobile AP (e.g., tethered UE 102) may have a Bluetooth / UWB device, which may additionally affect the coordination of its activities on both connections. Typically, and as also contemplated for Wi-Fi 8, for efficient operation, an intermediate client / mobile AP may independently and individually communicate with the infrastructure AP 104 on one side and with the P2P client on the other side, including any periodic or dynamic availability / unavailability instances and durations. Such instances indicated to the infrastructure AP 104 or the P2P client may be related. However, having to communicate them independently may increase latency and involve additional overhead, and technical solutions may address them using the techniques discussed herein.

[0124] A technical solution that can be implemented in Wi-Fi 8 can enable any non-AP to send an unavailability / availability schedule 136 generated by a scheduler 134 to its AP 104. These schedules 136 may include information about when a non-AP (e.g., a second communication system 106) may become unavailable, for how long, and how long it will be available afterwards. Indications may be sent in a control frame (CF) as a TXOP holder or in a control response (CR) as a TXOP responder. In one example, an intermediate client / mobile AP (e.g., a tethered UE 102) may send a CF / CR to an infrastructure AP with an availability schedule 136. This CF / CR may also be intended for P2P clients from which a complementary unavailability schedule may be inferred. An intermediate client / mobile AP may send a CF / CR to a P2P client along with an availability schedule. This CF / CR may also be intercepted by an infrastructure AP 104 to infer a complementary unavailability schedule from it. In addition, due to Bluetooth / UWB, a client / mobile AP may have other IDC constraints, which may cause it to be dynamically unavailable to both infrastructure APs and P2P clients. CF / CR may be enhanced to indicate this dynamic unavailability common to both connections. In the case of a CF in a multi-STA BA format, for example, confirmation may be sought from both recipients. Thus, using the techniques of the technical solution, both the terminal receiver (e.g., P2P device UE 102) and the AP 104 may receive two schedules 136 indicating a first time period 138 and a second time period 140 for transmissions from the P2P device and from the AP 104, and thus be fully aware of the two transmissions being received by the intermediate UE 102. Using these schedules 136, the AP 104 and the P2P device may adjust their transmission timing and determine or size their AMPDUs and other transmission bursts within their respective first time periods 138 (e.g., availability windows) to maximize their throughput.

[0125] In implementations such as Wi-Fi 8, any non-AP (e.g., 106) may send a periodic unavailability schedule 136 to its AP 104, and vice versa. These schedules 136 may include information about when a non-AP (e.g., 106) may become periodically unavailable and for how long. Such indications may also be coordinated across two connections to adjust the timing of transmissions to the UE 102 via the shared resource 108, whereby adjustments are made when the openings in the schedule 136 indicate additional available transmission time. For example, a client / mobile AP may decode the target beacon transmission time (TBTT) of an infrastructure AP, etc., and decide the time interval at which it wants to decode beacons. It may configure those as periodic unavailability with P2P clients. A client AP may decide the beacon interval for transmitting beacons intended for P2P clients, and configure it as periodic unavailability with an infrastructure AP. In addition, due to Bluetooth / UWB, a client / mobile AP may have other IDC constraints that may cause it to be periodically unavailable to infrastructure APs and P2P clients. Acknowledgements may be sought from both recipients, for example in a multi-station BA format.

[0126] Figure 7 An example method 700 for generating a schedule of Wi-Fi communications in response to a communication burst exceeding its allotted time is illustrated. The method 700 may be implemented, for example, using system features or techniques discussed in conjunction with FIGS. 100-600 , including, for example, system 100 implemented in computer system 200 . The method 700 may be implemented with methods 800 and 900 or using any of the acts or operations of methods 800 and 900 , and vice versa. The method 700 may include acts or operations 705-715 . At 705 , the method may detect a communication burst of a transceiver that shares resources with a Wi-Fi transceiver on a UE device. At 710 , the method may determine a schedule of Wi-Fi transmissions from an AP. At 715 , the method may communicate the schedule to a Wi-Fi AP.

[0127] At 705, the method may detect a communication burst of a transceiver that shares resources with a Wi-Fi transceiver on a UE. The method may include detecting, by a device including a Wi-Fi transceiver and a second wireless transceiver that share at least one antenna, a communication burst received by the second wireless transceiver. The communication burst may exceed a time period allocated for a second wireless communication to be received via the at least one antenna. The device may communicate with an access point (AP) to receive Wi-Fi communications from the access point.

[0128] The device may be a UE device that includes communication functionality for monitoring incoming network traffic via one or more transceivers at the device. The UE device may receive transmissions of a Wi-Fi transceiver from a Wi-Fi access point (AP) device over a wireless link (e.g., a WLAN connection). The UE device may receive transmissions of a second wireless communication via a second (e.g., non-Wi-Fi) transceiver that sends and receives wireless communications via a different technology or protocol set. The second wireless communication may include at least one of: Bluetooth communication, ultra-wideband (UWB) communication, long-term evolution (LTE) communication, licensed assisted access (LAA) communication, new radio (NR) communication, or new radio unlicensed (NR-U) communication. The second communication may be received from a second communication system, such as a system that uses any one or more of the following for wireless communication: Bluetooth, UWB, LTE, LAA, NR, or NR-U. The Wi-Fi and second transceivers may share one or more resources of the UE device for receiving or transmitting wireless communications, such as an antenna, RF front-end circuitry, a processor, or power management circuitry.

[0129] The communication burst may include a plurality of data packets from the second communication system that exceeds a predetermined time period allocated for the second communication (e.g., non-Wi-Fi communication). The communication function may monitor wireless communications received by the UE device and detect or determine that the communication burst from the second communication system has reached or exceeded a threshold indicating that it will encroach or extend into, or has encroached or extended into, the time allocated for Wi-Fi transmissions.

[0130] The method may include detecting, by the device, that a second communication burst received by the second wireless transceiver overlaps with a portion of a first time period allocated to receive Wi-Fi communications from the AP according to a schedule. The method may include detecting, by the device, that a second communication burst received by the second wireless transceiver exceeds a second time period allocated for a second wireless communication. For example, a communication function of the UE device may identify or detect a second communication burst from the same or a different second communication system. The second communication burst may include wireless communications in a third set of protocols or a third technology (e.g., different from Wi-Fi and the second wireless communication of the initial communication burst).

[0131] At 710, the method may determine a schedule for Wi-Fi transmissions from the AP. The method may include determining, by the device in response to the detection, a schedule for the AP to transmit Wi-Fi communications to the device. The schedule may include a burst limit for a first time period based on a periodicity of a second time period. The burst time limit may identify a duration of Wi-Fi transmissions within a first time period within a second time period that forms a periodic basis (e.g., periodicity) for scheduling Wi-Fi transmissions. The schedule may include identification of a start and end of a first time period (e.g., indicating an availability time for Wi-Fi transmissions) and a second time period (e.g., indicating an entire time period). From a difference between the first time period and a remainder of the second time period that exceeds the burst limit, the schedule may identify or indicate for the W-Fi AP a time interval during which Wi-Fi transmissions are unavailable.

[0132] For example, a first time period may be allocated for receiving Wi-Fi transmissions. A second time period may correspond to a duration between a start of the first time period and a start of a next first time period that may be defined based on the periodicity of the second time period (e.g., a period of the second time period). The first time period and the next first time period (e.g., a first time period in each of the periodic second time periods) may be allocated for receiving or sending Wi-Fi transmissions. In each of the periods of the second time periods, a portion of the second time period outside of the first time period within the second time period may correspond to or indicate a time that is not allocated for Wi-Fi transmissions and may be used to schedule or transmit a second wireless transmission (e.g., Bluetooth, UWB, LTE, LAA, NR, or NR-U).

[0133] The method may include the UE device adjusting the schedule in response to detecting or identifying an overlap from a second communication burst regarding a duration allocated or desired for Wi-Fi transmission. The schedule may be adjusted to change at least one of a duration of a first time period or a duration of a second time period according to the duration of the second communication burst. For example, when adjusting the schedule or generating a new schedule for a Wi-Fi AP, the schedule may change or reflect a change corresponding to a periodicity (e.g., a frequency of a period or a length of time of the second time period). For example, the schedule may include a change that extends or shortens the second time period or the first time period. For example, the schedule may include a change that shifts the time period within one or more second time periods (e.g., from the beginning of the second time period to the end of the second time period or to the middle of the second time period or to the beginning of the second time period).

[0134] The method may include a UE device receiving an aggregate medium access control protocol data unit (AMPDU) of Wi-Fi communications from an access point. The AMPDU may include multiple MPDUs that may be concatenated and transmitted in a series of single burst transmissions. The AMPDU may be transmitted from the Wi-Fi AP to the UE device. The method may include the UE device generating a block acknowledgement (BA) for the AMPDU. The BA may include information about the success or failure of the transmission or about the success or failure of each of the MPDUs within the AMPDU. The UE device may communicate a schedule to the Wi-Fi AP via the BA. For example, a communication function may insert the schedule into a portion of the BA and transmit the BA to the Wi-Fi AP to trigger or cause the Wi-Fi AP to update the schedule and modify the timing of the Wi-Fi transmission to avoid overlapping with a communication burst at the UE device.

[0135] The schedule may be a schedule for receiving Wi-Fi communications at a UE device via a first communication channel among a plurality of communication channels. The schedule may be a schedule for receiving Wi-Fi communications at a UE device via a specific communication band among a plurality of Wi-Fi communication bands. The schedule may be a schedule that sets a time period, such as one or more milliseconds, seconds, hours, days, weeks, months, or years. The schedule may be a long-term schedule that is used indefinitely by a Wi-Fi AP.

[0136] The method may include determining, by the device in response to detecting a second communication burst received by the second transceiver, a second schedule. The second communication burst may be determined by the UE device to exceed a second time period allocated to a second wireless communication of the Wi-Fi AP to transmit Wi-Fi communications to the UE device via a second channel of the plurality of channels.

[0137] For example, the schedule may be a schedule for Wi-Fi communication via a first communication channel or a frequency band among a plurality of channels or frequency bands, and the second schedule may be a schedule for Wi-Fi communication via a second channel or a frequency band among a plurality of channels or frequency bands. The second schedule may include a second burst limit for a third time period based on a second second periodicity of a fourth time period. The third time period may be a time period within the fourth time period. The third time period of the second schedule may correspond to the first time period of the schedule, and the fourth time period of the second schedule may correspond to the third time period of the schedule. The periodicity (e.g., the length of the second and fourth time periods) may be the same or different. Depending on the determination of the communication function, the lengths of the first and third time periods (e.g., the duration dedicated to Wi-Fi communication) may be the same or different.

[0138] At 715, the method may communicate the schedule to the Wi-Fi AP. The method may include the UE device communicating the schedule to the Wi-Fi AP. The UE device may communicate the schedule or the second schedule to the Wi-Fi AP in one or more ways. For example, the UE device may transmit the schedule to the Wi-Fi AP via a transmission or message, such as using one or more MPDUs or AMPDUs. The UE device may transmit the schedule or the second schedule via one or more BAs transmitted in response to one or more received AMPDUs. The UE device may transmit the schedule to the Wi-Fi AP periodically or in response to a change in the schedule.

[0139] The method may include a UE device receiving an AMPDU for a Wi-Fi communication during a next first time period. The AMPDU may include a size adjusted according to the next first time period. For example, the AMPDU may be transmitted from the Wi-Fi AP to the UE after the UE transmits a schedule to the AP. The AMPDU may be sized according to the first time period of the schedule so as to maximize the AMPDU size to fit within but not exceed the first time period. For example, the UE device may receive an AMPDU during the next first time period that includes a size maximized to fit within the next first time period. The AMPDU may be sized to maximize the use of the first time period but also include a time window or portion that allows for the transmission of a block acknowledgement (BA) of the AMPDU to be completed within the next first time period.

[0140] The method may include the UE device communicating a second schedule to the determined access point in response to detection of the second communication burst. The second schedule may be used by the Wi-Fi AP to coordinate or synchronize communications to the UE device via a second channel of the plurality of channels according to a second burst limit for a third time period based on a second second periodicity of a fourth time period.

[0141] Figure 8 An example method 800 is illustrated in which a Wi-Fi AP delays receiving a block acknowledgment (BA) for a transmitted AMPDU in response to an IDC problem reported by a UE. The method 800 may be implemented, for example, using system features or techniques discussed in conjunction with FIGS. 100 to 600 , including, for example, system 100 implemented in computer system 200 . The method 800 may be implemented with or using any of the actions or operations of methods 700 and 900 , and vice versa. The method 800 may include actions or operations 805 to 815 . At 805 , the method may receive a BA identifying an in-device coexistence (IDC) problem. At 810 , the method may determine to allow a delayed BA for the AMPDU without indicating a failure. At 815 , the method may receive a delayed BA.

[0142] At 805, the method may receive a BA identifying an in-device coexistence (IDC) issue. The method may include a Wi-Fi access point (AP) receiving a block acknowledgment (BA) from a device. The BA may include information identifying the presence of an in-device coexistence (IDC) issue on the UE device. The IDC issue may include, for example, a wireless communication burst from a second communication system in the form of one or more of: Bluetooth, UWB, LTE, LAA, NR, or NR-U. The AP may mark the UE device as a device with an IDC issue.

[0143] A wireless communication burst may be detected or determined by the communication function of the UE device as extending beyond or encroaching on scheduled Wi-Fi communications between the UE device and the AP. The BA may identify the channel or frequency band in which the communication is occurring. The BA may identify the duration of time that the communication burst will encroach on the Wi-Fi communication.

[0144] The method may include an AP receiving a block acknowledgment (BA) from a second device. The BA may include information that no intra-device coexistence problem was identified on the second device. The AP may mark the UE device as a UE device that does not have an IDC problem. The AP may be configured to manage communications with a UE device that provides notification of the existence of an IDC problem by allowing a delayed BA without identifying an AMPDU transmission as a failure. The AP may be configured to manage communications with a UE that is not notified of an IDC problem by not allowing a delayed BA but identifying an AMPDU transmission as a failure if the BA of the AMPDU transmission does not arrive within a predetermined time interval.

[0145] At 810, the method may determine to allow a delayed BA for an AMPDU without indicating a failure. The method may include the AP determining, in response to identifying an IDC problem, to allow one or more BAs from a device to be delayed for more than a short interframe space (SIFS) in response to one or more aggregate medium access control protocol data units (AMPDUs) from the AP without being identified as a failure. For example, the AP may be configured to mark all AMPDUs whose BAs do not arrive within a predetermined time interval (e.g., SIFS) as failed transmissions. In response to receiving an IDC presence notification from a UE device via a BA, the AP may reconfigure its communication management with respect to the UE to provide an additional time interval for the BA to arrive, and not identify such AMPDUs that are late for the BA as failed transmissions despite the late arrival of the BA.

[0146] The method may include receiving, by the AP, a block acknowledgement (BA) from a second device including information that no intra-device coexistence issue was identified on the second device. A communication function of the AP may identify that the device is configured for Wi-Fi communication, wherein transmission of one or more BAs for one or more AMPDUs is delayed until after one or more SIFS after the one or more AMPDUs. The AP may transmit, in response to this configuration, a preset that communicates the plurality of AMPDUs according to the configuration. The preset may be indicated in at least one of a header of a physical layer or a medium access control header of an AMPDU in the plurality of AMPDUs.

[0147] The method may include the AP identifying channel quality information indicating a signal-to-interference-plus-noise ratio (SINR) margin from the information. The method may include a communication function of the AP adjusting a modulation and coding scheme (MCS) for transmission to the device in response to the SINR margin. The AP may identify the indication from the received information. The indication may include information about or corresponding to at least one of: a modulation and coding scheme (MCS) for transmission to the device, a signal strength of one or more AMPDUs, or the presence of one or more hidden nodes. The communication function at the AP may adjust at least one of the following in response to the indication: the MCS, the signal strength, or a transmit power corresponding to one or more hidden nodes for the next AMPDU to be transmitted to the device. The AP may determine from the information that all MPDUs within the one or more AMPDUs have failed to be received by the device. The AP may receive a BA despite the failure of each of the MPDUs of the AMPDU.

[0148] In response to not receiving an indication of an IDC problem for the second UE device, the AP may transmit an AMPDU to the second device. After waiting for a predetermined length of time (e.g., SIFS) for a BA for the AMPDU to arrive from the second device, the AP may determine that a BA for the AMPDU was not received within the SIFS. In response to this determination, the AP may identify that transmission of the AMPDU has failed in response to not receiving a BA within the SIFS and not reporting the IDC problem to the second UE device.

[0149] At 815, the method may receive a delayed BA. The method may include the AP receiving, after a predetermined time period (e.g., SIFS) and in response to the determination, a second BA from the device. The second BA may include a plurality of acknowledgments corresponding to a plurality of AMPDUs received from the AP. For example, the AP may transmit a plurality of AMPDUs to the UE device. The AP may determine, in response to the determination at act 810, that the plurality of transmissions of the plurality of AMPDUs were successful, regardless of the second BA received after the SIFS.

[0150] Fig. 9An example method 900 is described for facilitating the transmission of low-latency packets of MPDUs scheduled for transmission later by inserting low-latency packets into MPDUs scheduled for transmission in a current or upcoming transmission opportunity (TXOP). Method 900 may be implemented, for example, using system features or techniques discussed in conjunction with Figures 100 to 600, including, for example, system 100 implemented in computer system 200. Method 900 may be implemented with methods 700 and 800 or implemented using any actions or operations of methods 700 and 800, and vice versa. Method 900 may include actions or operations 905 to 920. At 905, the method may identify a PPDU for transmission during a current TXOP. At 910, the method may identify a low-latency packet in a subsequent PPDU. At 915, the method may insert the low-latency packet into the PPDU. At 920, the method may transmit a PPDU with a low-latency packet in the current TXOP.

[0151] At 905, the method may identify a PPDU for transmission during a current transmit opportunity (TXOP). The method may include identifying, by a UE device in wireless communication with an access point (AP), a physical protocol data unit (PPDU) created during the current TXOP and waiting to be transmitted to the AP. The communication function may identify one or more MPDUs within the PPDU / AMPDU that are scheduled for transmission during the current TXOP. The one or more PPDUs may include a header including information about the PPDU to be transmitted.

[0152] At 910, the method may identify a low-latency packet in a subsequent PPDU. The method may include the UE device identifying a low-latency packet received by the device during the current TXOP. The low-latency packet may be a low-latency packet that is desired to be communicated to the AP in a next PPDU following the PPDU. The method may include identifying the low-latency packet in a next PPDU scheduled for transmission via the current TXOP (e.g., but still in an MPDU following the MPDU of action 905) or in a next TXOP following the current TXOP. The low-latency packet may include or be associated with a header. The header may include information or data for the low-latency packet. The header of the low-latency packet may include data for the next MPDU.

[0153] At 915, the method may insert the low latency packet into the PPDU. The method may include the UE device inserting the low latency packet into the PPDU. The method may include the UE device determining to insert the low latency packet into the PPDU. For example, the communication function may insert the low latency packet into at least a portion of the MPDU or adjacent to one or more MPDUs. The low latency packet may be inserted with a header of the long latency packet.

[0154] The communication function may identify the availability or opening of a second low-latency packet to be inserted into a third MPDU after the next or second MPDU. The communication function may insert the second low-latency packet into the next MPDU, replacing the low-latency packet now inserted into the (first) MPDU. The communication function may insert the second low-latency packet into the (first) MPDU in response to determining that there is sufficient time availability to insert the second low-latency packet.

[0155] At 920, the method may transmit a PPDU with a low latency packet to the AP in the current TXOP. The method may include the UE device transmitting the PPDU including the low latency packet to the AP within the current TXOP. The UE device may transmit the PPDU with the current TXOP and transmit the next MPDU within its own predetermined TXOP (e.g., the current TXOP or the next TXOP). The UE device may transmit the PPDU via shared resources and antennas and according to the schedule.

[0156] When an element is referred to herein as being "connected" or "coupled" to another element, it is understood that the element may be directly connected or coupled to the other element or have an intervening element between the connected or coupled elements. Conversely, when an element is referred to as being "directly connected" to another element or "directly coupled" to another element, it is understood that there are no intervening elements in the "direct" connection between the elements. However, the presence of a direct connection does not exclude other connections in which there may be intervening elements.

[0157] References to "or" may be interpreted as inclusive, such that any term described using "or" may indicate any of a single, more than one, and all of the described terms. References to at least one of a combined list of terms may be interpreted as inclusive or to indicate any of a single, more than one, and all of the described terms. For example, reference to "at least one of 'A' and 'B'" may include only 'A', only 'B', and both 'A' and 'B'. Such references used in conjunction with "includes" or other open terms may include additional items.

[0158] It should be noted that certain paragraphs of the present disclosure may reference terms such as "first" and "second" in connection with transmit spatial streams, sounding frames, responses, and devices for identification or distinction from one another or for other purposes. These terms are not intended to relate entities (e.g., a first substrate and a second substrate) only in time or according to a sequence, but in some cases, these entities may include such a relationship. These terms also do not limit the number of possible entities (e.g., delay circuits, filters, peak detectors) that may operate within a system or environment. It should be understood that the systems described above may provide multiple of any one or each of those components, and these components may be provided on independent structures or devices, or in some embodiments, on multiple structures or devices in a distributed system.

[0159] Although the foregoing written description of the methods and systems enables a person of ordinary skill to make and use embodiments thereof, the person of ordinary skill will understand and appreciate that variations, combinations, and equivalents of the specific embodiments, methods, and examples herein exist. The methods and systems should therefore not be limited by the embodiments, methods, and examples described above, but rather by all embodiments and methods within the scope and spirit of the present disclosure.

Claims

1. A device comprising a Wi-Fi transceiver and a second wireless transceiver that share at least one antenna, the device comprising one or more processors coupled to a memory to: detecting that a burst of communications received by the second wireless transceiver exceeds a time period allocated for a second wireless communication, the apparatus communicating with an access point AP to receive Wi-Fi communications; determining, in response to the detecting, a schedule for the AP to transmit Wi-Fi communications to the device, the schedule comprising a burst limit for a first time period based on a periodicity of a second time period; and The schedule is communicated to the access point.

2. The device of claim 1 , wherein the first time period is allocated for receiving the Wi-Fi transmission, and the second time period corresponds to a duration between a start of the first time period and a start of a next first time period based on the periodicity of the second time period, the next first time period being allocated for receiving the Wi-Fi transmission.

3. The device of claim 2, comprising the one or more processors to: An aggregate medium access control protocol data unit AMPDU of the Wi-Fi communication is received during the next first time period, the AMPDU including a size adjusted according to the next time period.

4. The device of claim 2, comprising the one or more processors to: An aggregate medium access control protocol data unit AMPDU of the Wi-Fi communication is received during the next first time period, the AMPDU being sized with respect to a time length of the next first time period and having a size that allows transmission of a block acknowledgement BA of the AMPDU to be completed within the next first time period.

5. The device of claim 1, comprising the one or more processors to: detecting that a second communication burst received by the second wireless transceiver overlaps with a portion of the first time period allocated to receive Wi-Fi communications from the AP according to the schedule; and The schedule is adjusted in response to the overlap.

6. The device of claim 5, wherein the schedule is adjusted to change at least one of a duration of the first time period or a duration of the second time period according to a duration of the second communication burst.

7. The device according to claim 1, wherein the second wireless communication corresponds to at least one of the following: Bluetooth communication, ultra-wideband UWB communication, long-term evolution LTE communication, licensed assisted access LAA communication, new radio NR communication or new radio unlicensed NR-U communication.

8. The device of claim 1, comprising the one or more processors to: receiving an aggregated media access control protocol data unit AMPDU of the Wi-Fi communication from the access point; generating a block acknowledgment BA for the AMPDU; and The schedule is communicated to the access point via the BA.

9. The apparatus of claim 1, wherein the schedule is for receiving the Wi-Fi communication via a first communication channel of a plurality of communication channels.

10. The device of claim 9, comprising the one or more processors to: detecting that a second communication burst received by the second transceiver exceeds a second time period allocated for a second wireless communication; determining, in response to the detection of the second communication burst, a second schedule for the access point to transmit Wi-Fi communications to the device via a second channel of the plurality of channels, the second schedule comprising a second burst limit for a third time period based on a second periodicity of a fourth time period; and The second schedule is communicated to the access point.

11. An access point, comprising: One or more processors coupled to the memory to: receiving, from a device, a block acknowledgment BA including information identifying the presence of an intra-device coexistence issue on the device; In response to identifying the intra-device coexistence issue, determining to allow one or more BAs from the device In response to one or more aggregate medium access control protocol data units AMPDU from the AP being delayed for more than a short interframe space SIFS without being identified as a failure; and After the SIFS and in response to the determining, a second BA is received from the device, the second BA including a plurality of acknowledgments corresponding to a plurality of AMPDUs received from the AP.

12. The access point of claim 11, comprising the one or more processors to: The plurality of transmissions of the plurality of AMPDUs are determined to be successful regardless of the second BA received after the SIFS in response to the determining.

13. The access point of claim 11, comprising the one or more processors to: receiving, from a second device, a block acknowledgment BA including information that no intra-device coexistence problem was identified on the second device; transmitting the AMPDU to the second device; determining that no BA for the AMPDU is received within the SIFS; and The transmission of the AMPDU is identified as having failed in response to not receiving the BA within the SIFS.

14. The access point of claim 11, comprising the one or more processors to: identifying that the device is configured for Wi-Fi communication, wherein transmission of one or more BAs for the one or more AMPDUs is delayed until after one or more SIFSs ​​after the one or more AMPDUs; and A preset is transmitted in response to the configuration to communicate the plurality of AMPDUs according to the configuration.

15. The access point of claim 14, wherein the preset indication is in at least one of a header of a physical layer or a header of a medium access control header of an AMPDU in the plurality of AMPDUs.

16. The access point of claim 11, comprising the one or more processors to: identifying channel quality information indicating a signal to interference plus noise ratio (SINR) margin from the information; and A modulation and coding scheme (MCS) used for transmission to the device is adjusted in response to the SINR margin.

17. The access point of claim 11, comprising the one or more processors to: identifying from the information an indication corresponding to at least one of: a modulation and coding scheme (MCS) used for transmission to the device, a signal strength of the one or more AMPDUs, or a presence of one or more hidden nodes; and At least one of the MCS, the signal strength, or a transmit power corresponding to the one or more hidden nodes is adjusted for a next AMPDU to be transmitted to the device in response to the indication.

18. The access point of claim 17, comprising the one or more processors to determine from the information that all MPDUs within the one or more AMPDUs failed to be received by the device.

19. A device for wirelessly communicating with an access point AP, the device comprising: One or more processors coupled to the memory to: Identify a physical protocol data unit PPDU created during a current transaction opportunity TXOP and waiting to be transmitted to an access point AP; identifying a low-latency packet received by the device during the current TXOP, the low-latency packet to be communicated to the AP in a next PPDU following the PPDU; inserting the low latency packet into the PPDU; and The PPDU including the low-latency packet is transmitted to the AP within the current TXOP.

20. The device of claim 19, comprising the one or more processors to: identifying the low-latency packet within the next PPDU scheduled for transmission via a next TXOP following the current TXOP; and Determining to insert the low-latency packet into the PPDU.

Images