Preemption techniques for transmitting high priority packets

Abstract

The disclosure relates to preemption techniques for transmitting high priority packets. A method for transmitting a high priority (HP) packet from a first wireless device to a second wireless device is described. The method comprises: determining the presence of an HP packet for uplink transmission; determining that a communication link for transmitting the HP packet using the wireless medium is busy; generating a preemption request message in the frame; and transmitting the frame with the preemption request message to the second wireless device. A first wireless device may receive, from a second wireless device, an indication that a preemption request is accepted or an indication that a contention-free period ends, such as by receiving a trigger frame with a resource allocation for transmitting an HP packet, to allow the first wireless device to compete for channel access to transmit the HP packet.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of U.S. Provisional Patent Application No. 63 / 536,042, filed on August 31, 2023, which is incorporated herein by reference in its entirety. Background Art

[0003] Many wireless devices communicate with each other using wireless local area networks (WLANs), such as those based on communication protocols compatible with Institute of Electrical and Electronics Engineers (IEEE) standards, such as the IEEE 802.11 standard (also known as "Wi-Fi"). A WLAN typically includes an access point (AP) that provides one or more stations (STAs) with access to another network, such as the Internet. There are many generations of the IEEE 802.11 standard, including 802.11ax (Wi-Fi 6) and 802.11be (Wi-Fi 7).

[0004] IEEE 802.11 is a packet-based protocol. According to the protocol, a transmitter (e.g., AP) packages control information or user data into a protocol data unit (PDU) in a physical layer convergence protocol (PLCP). A PLCP PDU (PPDU) includes a preamble and a data field, among other fields. After generating the PPDU, the AP can transmit the PPDU to a STA connected to the AP. Communication from the AP to the STA is called a downlink (DL), and communication from the STA to the AP is called an uplink (UL).

[0005] The PPDU includes a medium access control (MAC) PDU (MPDU) and a PLCP preamble and a PLCP header. The MPDU includes at least one MAC service data unit (MSDU) for transmission and other control information. Summary of the invention

[0006] Some specific implementations relate to a method for sending a high priority (HP) packet performed by a first wireless device, the method comprising: identifying an HP packet for uplink transmission; determining that a communication link used to send the HP packet is busy; generating a preemption request message; associating the preemption request message with a frame; and sending the frame to a second wireless device.

[0007] In some implementations, associating the preemption request message with the frame includes encoding the preemption request message in an A control subfield of a QoS null frame, a QoS data frame, or a management frame.

[0008] In some implementations, a QoS null frame, a QoS data frame, or a management frame is encoded in a MAC protocol data unit (MPDU).

[0009] In some specific implementations, generating the preemption request message includes encoding the preemption request message in a preamble of a PPDU that includes a control response frame.

[0010] In some specific implementations, the communication link is busy because the second wireless device is performing a frame burst; and the method also includes: receiving a trigger frame from the second wireless device, the trigger frame including a resource allocation for transmitting a HP packet; and transmitting the HP packet to the second wireless device according to the resource allocation indicated by the trigger frame.

[0011] In some implementations, the communication link is busy because the second wireless device is participating in an ongoing transmit opportunity (TXOP).

[0012] Some implementations include: receiving a contention-free (CF) end message from a second wireless device; contending for channel access; and sending a HP packet using resources allocated after contending for channel access.

[0013] Some implementations include: receiving a MU PPDU; identifying elements of HP data to be transmitted; encoding a preemption request message in a multi-STA BA; and transmitting the multi-STA BA to a second wireless device.

[0014] Some implementations include: receiving a trigger frame for transmitting HP data; and transmitting the HP data using resources associated with the trigger frame.

[0015] Some specific implementations include: receiving an RDG message; and transmitting HP data according to RDG parameters associated with the RDG message.

[0016] Some implementations include: receiving an indication of an end of a contention-free period; contending for channel access to a channel; and sending HP data on the channel.

[0017] In some implementations, the communication link is busy due to the second wireless device sending one or more physical protocol data units (PPDUs).

[0018] Some implementations include: receiving a MU PPDU including a preemption request message; and encoding a new PPDU end indication in an MPDU associated with the MU PPDU or the SUPPDU.

[0019] Some implementations include receiving a second element of the HP data from a second wireless device.

[0020] Some implementations include receiving multiple STABAs during a SIFS period prior to receiving a second element of HP data.

[0021] In some implementations, determining that a communication link used to send the HP packet is busy includes determining that a first link of a multi-link connection is busy.

[0022] In some implementations, sending the frame to the second wireless device includes sending the frame on a second link of the multi-link connection, wherein the preemption request identifies a first link used to send the HP packet.

[0023] In some specific implementations, sending the frame includes: sending the frame on a first link of a multi-link connection, and the preemption request identifies the first link for sending the HP packet.

[0024] Various aspects of a specific implementation relate to a method performed by a first wireless device, which communicates with a second wireless device via a wireless link, the method comprising: transmitting one or more lower priority PPDUs to the second wireless device; receiving a preemption request for a current communication from the second wireless device, wherein the preemption request is received in a QoS null frame, a QoS data frame, or a management frame associated with a control response frame; determining to preempt the current communication; transmitting at least one of a preemption indication or a PPDU end indication to the second wireless device; and receiving a high priority packet from the second wireless device on the wireless link.

[0025] In some implementations, the preemption indication includes an early block acknowledgement (BA), a trigger frame, a contention-free end frame, or a RDG indication for the low priority MPDU, thereby allowing the second wireless device to use the wireless medium to transmit the high priority packet.

[0026] In some implementations, the preemption request is encoded in an A control subfield of a control response frame, a QoS data frame, or a management frame.

[0027] In some implementations, the preemption request includes information corresponding to the high priority packet, the information including an indication of an amount of data associated with the high priority packet.

[0028] Some implementations include: encoding a new PPDU end indication in a last MPDU of the low priority PPDU; sending a last MPDU of the last low priority PPDU to the second wireless device; and receiving an early BA.

[0029] Some implementations include encoding a TXOP Take Over (TOT) indicator with the new end-of-PPDU indication to alert the second wireless device that the first wireless device will take over the TXOP.

[0030] In some implementations, a new end-of-PPDU indication is encoded in the A-control subfield of the last MPDU associated with the TXOP.

[0031] Some specific implementations include: transmitting a multi-user (MU) PPDU addressed to multiple second wireless devices; receiving a multi-STA BA including a preemption request message from at least one second wireless device among the multiple second wireless devices; transmitting a contention-free end indication or trigger frame to at least one second wireless device among the multiple second wireless devices or using a reverse grant (RDG) mechanism, wherein the RDG mechanism can grant the remaining TXOP to the second wireless device; and receiving an HP transmission from at least one device among the second multiple devices.

[0032] Some specific implementations include: encoding a preemption request message in one or more MPDUs included in a multi-user (MU) PPDU (MU PPDU); transmitting a MU PPDU addressed to multiple second wireless devices; receiving a new PPDU end indication from at least one second wireless device among the multiple second wireless devices; sending a MU block confirmation to at least one second wireless device among the multiple second wireless devices; and sending a HPPDU to at least one second wireless device among the multiple second wireless devices.

[0033] In some implementations, a first wireless device transmits a preemption request indication to a plurality of second wireless devices operating in a multi-user network environment using a first link.

[0034] In some implementations, at least one of the plurality of second wireless devices comprises a wireless station in a multi-link device (MLD).

[0035] Some specific implementations include receiving a PPDU early termination indication from at least one second wireless device among the plurality of second wireless devices, the PPDU early termination indication indicating that the at least one second wireless device has accepted the preemption indication request.

[0036] The details of one or more embodiments of these systems and methods are set forth in the following drawings and description. Other features, objects, and advantages of these systems and methods will be apparent from the description and drawings, and from the claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0037] Figure 1 A block diagram illustrating an example of a wireless device that performs wireless communications according to some implementations is illustrated.

[0038] Figure 2 is an example diagram of an overview of using the A control subfield of a QoS Null (QN) frame to preempt a TXOP according to some implementations of the present disclosure.

[0039] Figure 3 is an example diagram of an overview of using a preamble of a PPDU carrying an A control response frame to preempt a TXOP according to some specific implementations of the present disclosure.

[0040] Figure 4 is a schematic diagram of an example single-link system 400 illustrating preemption of frame bursts according to some implementations of the present disclosure.

[0041] Figure 5 is a schematic diagram of an example single-link system 500 illustrating preemption of a TXOP according to some implementations of the present disclosure.

[0042] Figure 6 is a schematic diagram of an example multi-link system according to some implementations of the present disclosure, illustrating preemption of frame bursts on one link of a multi-link operation (MLO) using simultaneous transmit and receive (STR).

[0043] Figure 7 is a schematic diagram of another example multi-link system 700 illustrating preemption of frame bursts on one link of a multi-link operation (MLO) using simultaneous transmit and receive (STR) according to some implementations of the present disclosure.

[0044] Figure 8 is a diagram of an example enhanced multi-link single radio (EMLSR) system in which a STA may request TXOP / frame burst preemption using a preemption request message encoded in the A control subfield according to some implementations of the present disclosure.

[0045] Fig. 9 is a diagram of another example enhanced multi-link single radio (EMLSR) system according to some implementations of the present disclosure, in which a STA may request TXOP / frame burst preemption using a preemption request message encoded in the A control subfield.

[0046] Fig.10 is a diagram of an example MLO system including PPDU preemption according to some implementations of the present disclosure.

[0047] Fig.11 is a diagram of a second example MLO system including PPDU preemption according to some implementations of the present disclosure.

[0048] Fig.12 is a diagram illustrating an example single-link system 1200 in which a STA preempts its own PPDU according to some implementations of the present disclosure.

[0049] Fig.13 is a diagram illustrating an example enhanced multi-link single radio (EMLSR) system 1300 in which a STA preempts its own PPDU according to some implementations of the present disclosure.

[0050] Fig.14 A block diagram of an example wireless device is illustrated according to some implementations.

[0051] Like reference numerals indicate like component features. DETAILED DESCRIPTION

[0052] A station (STA), including an access point (AP) station (AP STA) or a non-AP STA, may have one or more high priority (HP) packets available for transmission. However, the link used to transmit the HP packets may be busy due to uplink (UL) or downlink (DL) activity.

[0053] For example, a single-link STA (including an AP STA or a non-AP STA) or a multi-link device (MLD) (including an AP MLD or a non-AP MLD) may have an HP packet to send. The single link or multiple links may be busy due to a UL or DL ​​transmit opportunity (TXOP) or a frame burst. Before transmitting the HP packet, the STA may have to wait until the end of the TXOP or the completion of the frame burst, and even at this time, the STA may have to compete with other STAs for resources for transmitting the HP packet, so access to the channel is not guaranteed. Competition for resources may cause additional delays in transmitting the HP packet.

[0054] The present disclosure describes techniques for TXOP / frame burst preemption that enable transmission of HP packets with minimal delay. Depending on the length of the number of frame sequences in a frame burst / TXOP and the duration of each PPDU within the burst, preempting a frame burst or TXOP carrying low priority (LP) traffic can help improve HP traffic latency.

[0055] The MLD may request preemption of a TXOP / frame burst on the same link or another link for the following reasons: If the ongoing transmission on a link contains an HP packet, the MLD may request preemption of a TXOP carrying low priority data on another link; The MLD may prefer to use another link with higher BW and link quality, for example, a simultaneous transmit and receive (STR) situation with two links on the 2.4 GHz and 5 GHz bands. The MLD may prefer to use a link with a higher BW that may be busy due to an ongoing low priority TXOP or frame burst; Due to the traffic identifier (TID)-link mapping negotiation, the HP packet may have to be delivered over the link that is undergoing a TXOP / frame burst.

[0056] The present disclosure describes a mechanism for enabling a STA or MLD to preempt an ongoing transmission using a preemption request signal. In some implementations, if a STA or MLD has a HP packet, the STA or MLD may indicate a TXOP / frame burst preemption request to another STA or MLD in the UL or DL ​​over the same link or a cross-link. That is, a first STA may transmit a request for TXOP / frame burst preemption to a second STA or MLD on a link. In a multi-link operation (MLO) scenario, a request for TXOP / frame burst may be a request for channel access to the same first link or a different second link (a so-called cross-link). The term "same link" means sending a preemption indication on the same link that the MLD is requesting to preempt; and "cross-link" means sending a preemption indication on a different link from the one that the MLD is requesting to preempt. The second STA or MLD may use the information in the preemption request to decide whether to preempt the ongoing TXOP / frame burst.

[0057] In an MLO scenario, when a first MLD (AP MLD or non-AP MLD) has a high priority (HP) packet but all links are busy due to UL and / or DL ​​PPDUs (e.g., carrying low priority (LP) traffic), the first MLD with the HP packet must wait until the PPDU ends before sending the HP packet. In an MLO scenario, the first MLD can send a preemption request in the A Control subfield to a second MLD using the same link or a cross link. The MLD with the HP packet can use the A Control subfield to signal a preemption indication to another MLD using the Control ID and Subtype in the A Control subfield. The Link ID subfield can be used to indicate which link is being requested to preempt (i.e., the same link or a cross link).

[0058] In some implementations, the A control subfield may be used to send a preemption request from a first STA or MLD to a second STA or MLD. The A control subfield in QoS data frames, QoS empty frames, and management frames may be used. The receiver of the preemption indication uses this information to decide whether to perform preemption. The A control subfield is part of the high throughput (HT) control field. The HT control field is always present in a control wrapper frame and is present in QoS data frames, (11ax) QoS empty frames, and management frames, as determined by the +HTC subfield of the frame control field defined in §9.2.4.1.10 (+HTC subfield). A control may be encoded in the MPDU. QoS empty and block acknowledgment (BA) may be aggregated and transmitted as a control response frame (in the PPDU).

[0059] For example, the preemption request may cause the second STA or MLD to stop using the desired link to allow the first STA or MLD to access the channel for sending the HP packet. In some implementations, the second STA or MLD may transmit a new PPDU end indication in response to the preemption indication. The A control subfield may be implemented as or similar to the format shown in Table 1.

[0060] Table 1: A Control Subfield Format .

[0061] Control ID Subtype Link ID reserve 4-digit 4-digit 16-bit 6-digit

[0062] The A control subfield includes a control ID and a subtype. The subtype may indicate the purpose of the link ID bitmap. The control ID may be defined to indicate that the A control is for preemption. The link ID shows the link index to which the indication applies.

[0063] In some implementations, the preemption request may be sent in a preamble of a PPDU carrying a control response (CR) frame. In some implementations, the second STA or MLD may grant the first STA or MLD channel access, as described in more detail below.

[0064] Figure 1 A block diagram of an example system 100 is illustrated that includes a group of wireless devices that communicate with each other using a wireless medium, according to some implementations. The system 100 may include a first wireless device 110-1 that is wirelessly associated with a second wireless device 112. The wireless device 110-1 may communicate with the second wireless device 112 using a wireless signal 116. The system 100 may also include a third wireless device 110-2 that is also wirelessly associated with the second wireless device 112. In some implementations, the first wireless device 110-1, the second wireless device 112, and the third wireless device 110-2 include wireless stations (STAs).

[0065] The first wireless device 110-1 includes one or more communication radio components 114-1. The first wireless device 110-1 can be a single-link device or a multi-link device (MLD). In some embodiments, the first wireless device 110-1 is referred to as a STA, an MLD, or a non-AP STA or a non-AP MLD. An MLD can be characterized as having multiple STAs or radio components, each STA or radio component capable of communicating on the communication link of the STA or the radio component itself. The third wireless device 110-2 includes one or more communication radio components 114-3. The first wireless device 110-2 can be a single-link device or a multi-link device (MLD). In some embodiments, the first wireless device 110-2 is referred to as a STA, an MLD, or a non-AP STA or a non-AP MLD. In some examples described herein, the first wireless device 110-1 and the third wireless device 110-2 can be wireless devices (e.g., a smart phone, a laptop, a notebook computer, a tablet computer, a set-top box, a game console, a smart watch, or another such wireless device). Typically, in combination Figure 1 , the wireless devices 110 - 1 and 110 - 2 are referred to as wireless devices or STAs 110 .

[0066] The second wireless device 112 may also include one or more radio components 114-2. The second wireless device 112 may be a single link device or an MLD. In some embodiments, the second wireless device 112 is referred to as an AP, an AP STA, or an AP MLD. For example, an MLD may have multiple AP STAs or radio components, each of which is capable of communicating with other STAs or MLDs across a communication link. Figure 1 , the second wireless device 112 can be referred to as AP 112.

[0067] STA 110 and AP 112 may communicate wirelessly in a WLAN using IEEE 802.11 communication protocols. Thus, wireless device 110 may be associated with AP 112 or may have a connection with the AP. For example, wireless device 110 and AP 112 may communicate wirelessly in the following situations: detecting each other by scanning a wireless channel, sending and receiving beacons or beacon frames on a wireless channel, establishing a connection (e.g., by sending a connection request), and / or sending and receiving packets or frames (which may include requests and / or additional information (such as data) as payload). It should be noted that AP 112 may provide access to a network (such as the Internet) via an Ethernet protocol and may be a physical access point or a virtual or "software" access point implemented on a computer or wireless device. In this specification, wireless device 110 is sometimes referred to as a "receiving wireless device" or "receiver station."

[0068] Despite providing Figure 1 The environment shown is provided as an example, but in alternative implementations, there may be different numbers and / or types of wireless devices. For example, some implementations may include more or fewer wireless devices. As another example, in some implementations, different wireless devices may send and / or receive packets or frames. In some implementations, multiple links may be used during communications between wireless devices 110.

[0069] As referenced below Fig.14 As further described, the wireless device 110 and the AP 112 may include subsystems, such as a networking subsystem, a memory subsystem, and a processor subsystem. In addition, the wireless device 110 and the AP 112 may include a radio component 114 in the networking subsystem. More generally, the wireless device 110 and the AP 112 may include any wireless device having a networking subsystem (or may be included in the wireless device) that enables the wireless device 110 and the AP 112, respectively, to communicate wirelessly with another wireless device. This may include sending beacons on a wireless channel to enable wireless devices to make initial contact or detect each other, and then exchanging subsequent data / management frames (such as connection requests) to establish a connection, configure security options, send and receive packets or frames via the connection, etc.

[0070] like Figure 1 As shown, wireless signals 116 are communicated by one or more radio components 114-1 and 114-2 in wireless device 110-1 and AP 112, respectively. For example, as previously described, wireless device 110-1 and AP 112 may exchange packets or frames using the Wi-Fi communication protocol in a WLAN. In addition, one or more radio components 114-1 may receive wireless signals 116 sent by one or more radio components 114-2 via one or more links between wireless device 110-1 and AP 112. Alternatively, one or more radio components 114-1 may send wireless signals 116 that are received by one or more radio components 114-2.

[0071] In some implementations, the wireless signal 116 is communicated by one or more radio components 114 in the wireless device 110 and the AP 112, respectively. For example, the one or more radio components 114-1 and 114-3 can receive the wireless signal 116 sent by the one or more radio components 114-2 via one or more links between the wireless devices 110-1 and 110-2 and the AP 112.

[0072] In some implementations, the AP 112 may group the wireless devices 110 into a target station set. The target station set concept comes from downlink multi-user transmission, where the AP 112 may use orthogonal frequency division multiple access (OFDMA) or multi-user (MU) multiple input multiple output (MU-MIMO) to transmit to multiple stations simultaneously in one PPDU. Here, the target station set is a set of stations that can be served by the AP 112 at the same time. The stations in the set do not need to share the same PHY parameters, such as MCS, number of streams, etc.

[0073] In some implementations, the AP 112 may use multi-user (MU) technology, such as MU multiple-input multiple-output (MU-MIMO), to communicate with multiple wireless devices 110 simultaneously. In some examples, the AP 112 communicates with the wireless devices 110 using frequency reuse, such that the AP 112 allocates a portion of the total bandwidth to each of the wireless devices. For example, to communicate with four wireless devices simultaneously over an 80 megahertz (MHz) bandwidth, the AP 112 sends a MU-PPDU over the 80 MHz bandwidth. The MU-PPDU includes a sub-PPDU for each of the four wireless devices, where each sub-PPDU (or sub-channel) is allocated 20 MHz. The AP 112 may use the MU-PPDU to communicate with devices in the same target set, devices in different target sets, or a combination of both.

[0074] In some implementations, the AP 112 and one or more wireless devices may be compatible with an IEEE 802.11 standard (e.g., IEEE 802.11ax) that includes trigger-based channel access. In 802.11ax, orthogonal frequency division multiple access (OFDMA) is used to enable simultaneous communication between the AP 112 and multiple wireless devices. OFDMA divides the available physical spectrum into multiple orthogonal subchannels or resource units (RUs) that can be allocated to different wireless devices (users). According to the standard, the AP 112 coordinates multi-user OFDMA by broadcasting a trigger frame, which additionally allocates RUs to each participating wireless device. Each wireless device responds to the trigger frame by sending a PPDU to the AP 112 using the allocated RU. The trigger frame may also include power control information. The AP 112 may instruct all wireless devices 110 when to start and stop transmitting. Note that AP 112 and wireless device 110 may communicate with one or more legacy wireless devices that are not compliant with the IEEE 802.11 standard (ie, the one or more legacy wireless devices do not use trigger-based multi-user channel access).

[0075] In some implementations, processing a packet or frame in one of the wireless devices 110, the AP 112, or a combination of both includes: receiving a wireless signal 116 that encodes the packet or frame; decoding / extracting the packet or frame from the received wireless signal 116 to obtain the packet or frame; and processing the packet or frame to determine information contained in the packet or frame (such as data in a payload).

[0076] As previously described, one or more wireless devices in the wireless device 110 and the AP 112 may communicate with each other. It is noteworthy that the AP 112 may send a PPDU including a preamble and a data field. In some specific implementations, the AP 112 may be configured to use a cascaded PPDU (C-PPDU), for example, for low-latency communication with a receiver station. The C-PPDU includes a plurality of component PPDUs, each of which includes a preamble and a data payload. As described in more detail below, the C PPDU includes a plurality of component PPDUs. The first component PPDU is preceded by a first preamble called a "full preamble". Each of the remaining component PPDUs in the C-PPDU is preceded by a corresponding preamble having a length shorter than the first preamble. In some specific implementations, before sending a plurality of component PPDUs, the AP 112 may not perform contention or receive a block acknowledgement (BA). The PPDU may include a plurality of MPDUs as well as a PPDU preamble and header information.

[0077] When a STA (AP STA or non-AP STA) or MLD (AP MLD or non-AP MLD) has a high priority (HP) packet and the link is busy due to an uplink (UL) or downlink (DL) TXOP or frame burst, the STA with the HP packet must wait until the TXOP or ongoing frame burst ends. (There may be multiple TXOPs in a frame burst sequence.) After the ongoing TXOP or frame burst ends, the STAs compete to deliver HP traffic, where access to the channel is not guaranteed and may cause additional delays.

[0078] Depending on the length of the number of frame sequences in a frame burst / TXOP and the duration of each PPDU within the burst, preempting a frame burst or TXOP carrying low priority (LP) traffic can help improve HP traffic latency. In the case of MLO, an MLD device may request preemption of a frame burst / TXOP for the following reasons:

[0079] If the first STA or MLD (AP or non-AP) has an HP packet, the STA may indicate a TXOP / frame burst preemption request to the second STA or MLD (non-AP or AP) in UL or DL ​​via the same link or a cross link. The second STA or MLD uses the preemption information to decide whether to preempt the ongoing TXOP / frame burst of the second STA or MLD.

[0080] There are two options for frame burst / TXOP preemption indication. Option 1 (MAC indication) is determined by Figure 2 As an example, the figure is a schematic diagram of an overview of using the A control subfield of a QoS Null (QN) frame 204 to preempt a TXOP according to some specific implementations of the present disclosure. A STA or MLD may deliver a preemption indication in the A control subfield of an MPDU in a control response (CR) frame. For example, a block acknowledgment (BA) 202 may be sent by the first STA or MLD with a QoS Null frame 204 encoded using the A control subfield for a preemption request. Option 1 may perform frame bursts / TXOP preemption indications for up to 16 links.

[0081] Option 2 (PHY preamble indication) consists of Figure 3 As an example, the figure is a schematic diagram 300 of an overview of preempting a TXOP using a preamble of a control response frame according to some specific implementations of the present disclosure. A STA or MLD may deliver a preemption indication in the preamble of a PPDU carrying a control response (CR) frame using the EHT-SIG field. For example, in an EHT MU PPDU preamble, B13-B16 in the common field of an Extremely High Throughput (EHT)-SIG frame may be used to preempt a TXOP / frame burst (currently bits B13-B16 are ignored subfields in 802.11be); for UHR, a new subfield may be defined for preemption indication. Each bit may represent a preemption request, and the bitmap may indicate the desired link.

[0082] Option 2 may have a lower modulation and coding set (MCS) rate index for EHT-SIG, such as a frame burst / TXOP duration indication in the PHY. Option 2 may be used alone or in combination with Option 1 (MAC indication).

[0083] Figure 4 is a schematic diagram of an example single link system 400 illustrating preemption of frame bursts according to some implementations of the present disclosure. Figure 4404, a single link between a STA 410 (or a non-AP STA, but referred to herein simply as a STA) and an AP 412 is busy due to an ongoing frame burst, and the STA 410 receives a HP packet while a frame burst (or TXOP) is occurring. (For a non-AP STA, a single link scenario may apply when the non-AP STA is operating one of the links of the non-AP STA.) Here, a frame burst is a downlink frame burst of a PPDU. The STA 410 indicates a frame burst / TXOP preemption to the AP 412 using the A control subfield in the QoS space 404. In response to receiving the PPDU, the STA 410 may transmit a BA 402 and a QN 404 to the AP 412. The preemption request may include an identification of the data that the STA 410 must deliver, such as the access category for the HP packet, the amount of data, and other information about the payload.

[0084] When AP 412 receives the preemption request, AP 412 may determine whether to preempt the frame burst / TXOP. If AP 412 decides to preempt the frame burst / TXOP, AP 412 may transmit a trigger frame (TF) 406 to STA 410. TF 406 provides STA 410 with resource allocation for HP packets in the UL for delivery of HP packets during the remaining TXOP. Note that the preemption indication may also be carried in the EHT-SIG (ie, option 2).

[0085] In this example, if the TXOP duration is reserved for multiple frame exchanges, another option is for STA 410 to take over the TXOP on link-1 using the Reverse Direction Grant (RDG) protocol. AP 412 transmits a PPDU with RDG=1 to grant the TXOP to STA 410 after receiving the preemption request indication. If STA 410 delivers all HP traffic and there is TXOP duration remaining, STA 410 may similarly return the TXOP to AP 412 after transmission. This allows quick access to the medium immediately following the current frame sequence.

[0086] Figure 5 is a schematic diagram of an example single-link system 500 illustrating preemption of a TXOP according to some implementations of the present disclosure. Figure 4(Case 1), STA 510 determines that the STA has HP service 504 to be transmitted on the UL, but the link is busy. As previously described, STA 510 transmits a preemption request by encoding the QoS empty A control field with the preemption request. In this case (Case 2), the TXOP is reserved for multiple frame exchanges. After AP 512 receives the preemption request and decides to preempt the TXOP, AP 512 preempts the TXOP by transmitting a contention-free end (CF-END) message 502 to the STA. The CF-End control frame 502 indicates the end of the contention-free period, which means that STA 510 can contend for channel access. After receiving the CF-End message 502, STA 510 contends for access to the channel.

[0087] Taking over the frame burst / TXOP allows the full TXOP to be used. For the frame burst option, the AP 512 is not aware of the STA's traffic, so the STA 510 can contend for the access category corresponding to the STA.

[0088] In both Case 1 and Case 2, STA 510 may indicate in the same A Control field the STA's intent to poll in the UL using RDG or to make a new access to the channel.

[0089] If the AP 512 does not receive the A control subfield or EHT-SIG preemption indication, the AP 512 continues the frame burst or TXOP, and the STA 510 must wait until the frame burst or TXOP ends to send the HP packet 504. Preemption allows the STA 510 to at least attempt to transmit the HP packet 504 earlier.

[0090] Figure 6 and Figure 7 TXOP / frame burst preemption for multi-link operation - simultaneous transmit and receive (MLO-STR) operation is shown. The example described below is a STR case where link 1 is on 2.4 GHz with BW=20 MHz and link 2 is on 5 GHz with BW=80 MHz. AP MLD 614 may include AP-1 and AP-2; non-AP MLD 616 may include STA-1 and STA-2. In the following example, AP-1 may communicate with STA-1 using link 1; and AP-2 may communicate with STA-2 using link 2.

[0091] If Link-2 is "busy", non-AP MLD 616 may transmit a preemption request in QN 604 aggregated with BA 602 (the first BA from STA-2). In general, the preemption indication may be transmitted over an access channel to transmit QN 604, aggregated with BA 602, or in a QoS data frame.

[0092] Figure 6 is a schematic diagram of an example multi-link system 600 illustrating preemption of frame bursts on one link of a multi-link operation (MLO) using simultaneous transmit and receive (STR) according to some implementations of the present disclosure. Figure 6 , a burst of frames occurs on Link 2. Non-AP MLD 616 may determine that the non-AP MLD has HP packets 606 to transmit on one link (Link 1 or Link 2) of the multilink connection. STA-1 indicates preemption to AP-1 over Link 1 to preempt the burst of frames on Link-2. The preemption indication is sent in the A Control subfield in QoS space 604.

[0093] If AP MLD 614 decides to preempt the frame burst on Link 2, AP-2 preempts the frame burst in DL and transmits TF 608 to trigger STA-2 of non-AP MLD 616 in UL to deliver HP packet 606. If the TXOP is reserved for multiple frame exchanges, the TXOP can be preempted. And similar to the single link case, two other options can be implemented: use the RDG protocol to take over the TXOP; or the AP transmits CF-End to end the TXOP and STA-2 competes for the complete TXOP. After STA-2 receives the TF, STA-2 can use the resources in TF 608 to send HP packet 606 over Link 2.

[0094] Figure 7 is a schematic diagram of another example multi-link system 700 according to some implementations of the present disclosure, which illustrates the preemption of frame bursts on one link of a multi-link operation (MLO) using simultaneous transmission and reception (STR). Figure 7 As depicted, STA-1 wants to deliver HP traffic using link 2. Therefore, STA-2 accesses the channel and sends a QoS Null (QN) 704 with an A control encoding for preemption to indicate frame burst preemption.

[0095] The QN 704 for the frame burst preemption indication may be transmitted over another link. For example, AP-2 may decide to preempt the frame burst in DL over Link-2 and transmit TF 708 to trigger STA-2 of the non-AP MLD 716 in UL to deliver the HP packet 706. After STA-2 receives TF 708, STA-2 may use the resources in TF 708 to send the HP packet 706 over Link-2.

[0096] Case 1( Figure 6 ) and case 2( Figure 7 ) is that for Figure 6 , Link-1 is busy, so QN 604 (and preemption indication) is transmitted as a response to LP PPDU 610. Figure 7 , non-AP MLD 716 may access the channel on link 1 to transmit QN frame 704 also on link 1; and non-AP MLD 716 may then receive ACK 710 for QN 704 from AP MLD 714.

[0097] Figure 8 and Fig. 9 TXOP / frame burst preemption for an enhanced multi-link single radio component is illustrated. The non-AP MLD 816 can implement enhanced multi-link single radio (EMLSR) operation when the device has a single radio component, and can operate on multiple links following the EMLSR procedure. After receiving the initial control frame (MU-RTS or BSRP) from the AP MLD 814 over one of the links, the non-AP MLD 816 in EMLSR operation switches to that link to receive the rest of the TXOP.

[0098] Figure 8 8 is a diagram of an example of an enhanced multi-link single radio (EMLSR) system 800 according to some implementations of the present disclosure, wherein a STA of a non-AP MLD 816 operating in EMLSR mode may request TXOP / frame burst preemption using a preemption request message encoded in the A control subfield. Figure 8 In (Case 1), AP MLD 814 may transmit traffic (LP PPDU 802) from AP-1 to STA-1 (of non-AP MLD 816) on Link 1 as part of an ongoing frame burst or TXOP. Non-AP MLD 816 may prefer to transmit HP traffic on Link 1. STA-1 of non-AP MLD 816 indicates preemption to AP-1 using the A Control subfield in QoS Space 804. AP-1 preempts the frame burst and transmits TF 806 to trigger STA-1 of non-AP MLD 816 to deliver HP packets in the UL over the same link.

[0099] In case 2 (in Fig. 9 ), STA-1 of non-AP MLD 916 indicates frame burst preemption for link-1, and then non-AP MLD 916 can use any of these links to transmit. Fig. 9 is a diagram of another example enhanced multi-link single radio (EMLSR) system 900 in which a non-AP MLD 916 can request TXOP / frame burst preemption on a link using a preemption request message encoded in the A control subfield, according to some implementations of the present disclosure. Fig. 9 Similar to Figure 8, where the HP packet arrives during the frame burst. After the frame burst preemption indication, AP MLD 914 terminates the frame burst on Link-1. After a period of time (e.g. Fig. 9 ), the non-AP MLD 916 switches back to the listening operation after determining the end of the frame exchange and contends to start a new TXOP on link-2. In this case, the non-AP MLD 916 prefers link-2 due to higher BW and / or TID-link mapping or other reasons. The EMLSR frame exchange end determination follows the rules in the 802.11be specification.

[0100] In a multi-user (MU) scenario, only non-AP STAs can request preemption in DL or triggered UL from the AP. Non-triggered UL preemption (where the AP requires STAs to preempt their UL frame exchanges) is equivalent to the already combined Figure 4 and Figure 5 The single-user preemption case is discussed. Both Option 1 and Option 2 can be applied to the multi-user (MU) case.

[0101] Option 1: In DL-MU frame exchange, the STA may indicate the preemption indication to the AP by indicating the STA's request in the Multi-STA Control Response (i.e., in response to the QoS NULL aggregated with the multi-STA BA). In (trigger-based) UL multi-user (MU) frame exchange, the STA may indicate the preemption indication to the AP by indicating the STA's request in the A Control of the MPDU in the UL traffic delivery.

[0102] Option 2: In DL-MU frame exchange, the STA may indicate the preemption indication to the AP by indicating the STA's request in the preamble of the multi-STA BA (i.e., UHR-SIG). In (trigger-based) UL-MU frame exchange, the STA may indicate the preemption indication to the AP by indicating the STA's request in the preamble of the UL TB PPDU (i.e., Ultra High Reliability (UHR)-SIG). If the AP can preempt after receiving the request, the AP polls (trigger) the STA in the UL or terminates the DL / UL TXOP of the AP in advance to allow the STA to access the channel for HP packet UL service delivery.

[0103] PPDU Preemption and Early PPDU Termination: The first MLD with the HP packet uses the A Control subfield to preempt the second MLD. An example of the A Control subfield is shown in Table 2.

[0104] Table 2: A Control Subfield for Requesting PPDU Preemption

[0105] Control ID Subtype Link ID reserve 4-digit 4-digit 16-bit 6-digit

[0106] The A control subfield may include the control ID and subtype in the A control subfield. The link ID subfield will be used for same link or cross link preemption indication (i.e., the link ID is used to identify which link the HP packet is to be sent on). The receiver of the preemption indication uses this information and decides whether to preempt.

[0107] The present disclosure describes a new PPDU end indication: If the second MLD decides to preempt, the second MLD needs to indicate the new preempted PPDU end so that the first MLD can prepare a BA SIFS after the preempted PPDU end. A control signaling can be used by the second MLD to indicate the new PPDU end. The A control subfield can also be used as an indicator for the first MLD to take over the TXOP after preemption.

[0108] The A Control subfield may be used as a new PPDU end indication. Table 3 shows an example A Control subfield for the new PPDU end indication.

[0109] Table 3: A Control Subfield for New PPDU End Indication

[0110] Control ID Subtype PPDU END ToT reserve 4-digit 4-digit 1st 1st 20 people

[0111] A control subfield control ID and new subtype may be encoded in the last MPDU of the PPDU. If the second MLD does not indicate the end of a new PPDU (i.e., the end of the preempted PPDU), the first MLD will not know the actual end of the preempted PPDU. Therefore, the first MLD cannot transmit a HP packet or a block acknowledgement (BA) response and will continue decoding until the end of the L-SIG length (the L-SIG length indicates the original end of the PPDU transmission by the second MLD).

[0112] The control IDs between Table 2 and Table 3 are the same. However, there are different subtypes for different functions. For example, subtype = 0 may be set for a TXOP preemption request, subtype = 1 may be set for a PPDU preemption request, and subtype = 2 may be set for a new PPDU end indication.

[0113] Fig.10 is a diagram of an example MLO system including PPDU preemption according to some implementations of the present disclosure. Fig.10 A PPDU preemption indication transmitted in the first link and a new PPDU end indication transmitted in the cross link are shown.

[0114] Fig.10 An example scenario is shown in which the AP MLD 1014 and the non-AP MLD 1016 operate in simultaneous transmission and reception (STR). Fig.10In the STR example, AP-1 of AP MLD 1014 and STA-1 of non-AP MLD 1016 use link 1 to communicate at 2.4 GHz with BW=20 MHz; and AP-2 of AP MLD 1014 and STA-2 of non-AP MLD 1016 use link 2 to communicate at 5 GHz with BW=80 MHz.

[0115] exist Fig.10 , AP-1 is sending a PPDU 1002 to STA-1 on link 1. AP-2 is sending a LP PPDU 1004 to STA-2 on link 2. During the PPDU transmission, AP-1 determines that AP MLD 1014 has a HP PPDU for transmission to non-AP MLD 1016 on link 2. Therefore, AP MLD 1014 transmits a PPDU preemption request to non-AP MLD 1016.

[0116] The preemption request may indicate a request to preempt the LP PPDU 1004 received from STA-2 on Link-2. For PPDU preemption, when the AP MLD 1014 receives an HP packet and there is an ongoing LP PPDU reception on Link-2, AP-1 transmits the A Control subfield to the non-AP MLD 1016 over Link-1 as an indicator to preempt the LP PPDU 1004 over Link-2. The AP MLD 1014 may encode the preemption request in the A Control subfield within the MPDU of the PPDU 1002 being sent on Link-1. AP-1 may transmit the preemption request to the non-AP MLD 1016 (towards STA-1) on Link-1 within the PPDU transmission. AP-1 may then continue to transmit the PPDU on Link-1.

[0117] STA-2, after receiving the preemption indication, encodes a "new PPDU end" indicator in the A control subfield of the last MPDU of the last PPDU, which indicates the new end of the PPDU, and then STA-2 preempts the LP PPDU 1004. Within a short interframe space (SIFS), STA-2 can obtain a HP PPDU from AP-2 on link 2. For example, after the end of the preempted LP PPDU 1004, the AP MLD 1014 can aggregate the BA with the HP MPDU 1006 and send the PPDU. STA-2 can also set the ToT (Take Over TXOP) field in A control (along with the new PPDU end) to let AP-2 know that STA-2 can take over the TXOP after receiving the current MPDU.

[0118] In this case, AP-2 takes over the TXOP initiated by STA-2, so the AP-2 should respect the initial TXOP duration initiated by STA-2. This allows the STA to quickly take over the TXOP along with the HP packets to be transmitted, which means that the HP packets can be transmitted quickly.

[0119] Fig.11 is a schematic diagram of a second example MLO system 1100 including PPDU preemption according to some specific implementations of the present disclosure. Case 2 is similar to Case 1 ( Fig.10 ), but in Fig.11 In the example, AP-2 requires a larger TXOP duration.

[0120] AP-2 sends a BA 1102 after receiving the new PPDU end and initiates channel access to start HP PPDU transmission 1104. The channel access procedure may include the fact that AP-2 has HP traffic and may also be configured to provide sufficient resources to send HP packets (assuming that the remaining TXOP from STA-2 is insufficient to send HP packets). In case 2, AP-2 has a full TXOP to deliver traffic.

[0121] Between STAs (in Fig.10 and Fig.11 The information exchanged between the AP MLD and the non-AP MLD in the case of a STA-2 MLD may take some time. The exchange of preemption requests may delay a possible preemption event at STA-2. It is worth noting that STA-2 may decide whether to perform preemption.

[0122] STA-2 transmits the next MPDU with A control containing a new PPDU end indicator after determining the preemption, which indicates to AP-2 that the preemption occurs after the MPDU with the new PPDU end indicator. If STA-1 of non-AP MLD 1116 does not receive the preemption indication (A control in the MPDU transmitted from AP-1 to STA-1 on link 1), STA-2 continues LP PPDU transmission 1106 on link 2.

[0123] After STA-2 decides to preempt, if AP-2 does not receive a new PPDU end indication (controlled by A in the MPDU transmitted by STA-2 on link 2), AP-2 continues to receive LP PPDU 1106 on link 2 until the L-SIG duration. Therefore, AP MLD 1114 will not transmit BA 1102 with HP PPDU 1104 within SIFS after the preempted PPDU 1108, but waits until the LP PPDU reception ends before starting to send HP PPDU 1104. Again, after receiving the complete LPPPDU 1106, the transmission of HP PPDU 1104 will follow the channel contention procedure, which may delay the transmission of HP packets.

[0124] In some implementations, a STA may use the "new PPDU end" indication to preempt the STA's own PPDU and receive a BA for the delivered MPDU. Below are some examples for single link and EMLSR scenarios:

[0125] Fig.12 1 is a diagram illustrating a single-link system 1200 according to some specific implementations of the present disclosure, in which a STA 1210 preempts the STA's own PPDU 1202. An AP 1212 sending an LP PPDU 1202 determines that the AP has HP traffic for DL ​​transmission to the STA 1210. The AP 1212 replaces the LP MPDU with the HP MPDU 1204 in the LP PPDU 1202. Since the AP 1212 wants to receive a BA 1206 just after the HP MPDU 1204 is transmitted, the AP transmits a new PPDU end indication in the last HP MPDU and preempts the LP PPDU 1202 (preemption means that the AP 1212 stops the transmission of the LL PPDU 1202 after the transmission of the HP MPDU 1204). The STA 1210 sends a BA 1206 for all received MPDUs (including the HP MPDU 1204) after receiving the new PPDU end indication.

[0126] Fig.13 is a diagram illustrating an enhanced multi-link single radio (EMLSR) system 1300 in which a STA preempts its own PPDU according to some implementations of the present disclosure. Fig.131302 on the uplink to AP-2 on link 2. Non-AP MLD 1316 determines that it has HP traffic for transmission on the UL on link 2. Because non-AP MLD 1316 is in EMLSR mode, non-AP MLD 1316 cannot transmit on link 1 simultaneously with LPPPDU transmission 1302 on link 2. Therefore, STA-2 replaces the LP MPDU with the HP MPDU 1304 in the LP PPDU 1302 being transmitted on link 2. STA-2 encodes the "new PPDU end" indication in the A control frame of the last HP MPDU 1304 transmitted to AP-2 on link 2. AP-2 may transmit BA 1306 just after receiving all HP MPDU 1304 transmissions (i.e., after AP-2 decodes the "new PPDU end" indication). STA-2 thus preempts the LP PPDU 1302.

[0127] In both cases, if no A-control is received, the receiver continues to receive the LP PPDU 1302 until the LPPPDU duration ends, and will transmit a BA 1306 thereafter.

[0128] The AP MLD 1314 may have established a link between multiple non-AP MLDs, and the AP MLD 1314 may send the LP PPDU 1302 on the link. The APMLD 1314 having HP traffic to be transmitted to one or more non-AP MLDs 1316 on the DL MU may transmit a PPDU preemption indication in the DL (e.g., on the second link) to the one or more non-AP MLDs 1316. If the non-AP MLD STA 1316 accepts the request, each non-AP MLD STA that receives the PPDU preemption indication may indicate early termination of the PPDU for the SU or MU in the UL, for example, through the first link.

[0129] The AP MLD 1314 may encode the preemption request into different MPDUs, each directed to a different non-AP MLD 1316 in the DL MU.

[0130] The non-AP MLD 1316 may have HP traffic to transmit to the AP MLD 1314. The non-AP MLD 1316 may transmit a PPDU preemption indication in the UL MU (UL OFDMA). If the AP MLD 1314 accepts the preemption request, the AP of the AP MLD 1314 on the cross link may indicate early termination of the PPDU for the MU in DL or UL ODFMA. The non-AP MLD 1316 may then use the preempted link to transmit the HP traffic. Each non-AP MLD 1316 may encode a preemption request in the UL MU that its own MPDU is directed to the APMLD 1314.

[0131] Fig.14 A block diagram of an electronic device 1400 according to some implementations is illustrated. The electronic device 1400 may be a cellular phone, a smart watch, an access point, a wireless speaker, an Internet of Things (IoT) device, etc. The electronic device 1400 includes hardware resources 1402, which include one or more processors (or processor cores) 1410, one or more memory / storage devices 1420, and one or more communication resources 1430, each of which may be communicatively coupled via a bus 1440.

[0132] The one or more processors 1410 include one or more devices configured to perform computing operations. For example, the one or more processors 1410 may include one or more microprocessors, application specific integrated circuits (ASICs), microcontrollers, graphics processing units (GPUs), programmable logic devices, and / or one or more digital signal processors (DSPs). The processors 1410 may include, for example, processors 1412 and processors 1414. The processors 1410 may be, for example, a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a DSP such as a baseband processor, an ASIC, an FPGA, a radio frequency integrated circuit (RFIC), another processor (including those discussed herein), or any suitable combination thereof.

[0133] The memory / storage device 1420 may include a main memory, a disk storage device, or any suitable combination thereof. The memory / storage device 1420 may include, but is not limited to, any type of volatile or non-volatile memory, such as a dynamic random access memory (DRAM), a static random access memory (SRAM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a flash memory, a solid-state storage device, and the like. In some implementations, the memory / storage device 1420 is coupled to one or more high-capacity mass storage devices (not shown). In some examples, the memory / storage device 1420 may be coupled to a disk drive or an optical drive, a solid-state drive, or another type of mass storage device. In these examples, the memory / storage device 1420 may be used by the electronic device 1400 as a fast access storage device for frequently used data, while the mass storage device is used to store less frequently used data.

[0134] The communication resources 1430 may include an interconnect or network interface component or other suitable device to communicate with one or more peripheral devices 1404 or one or more databases 1406 via the network 1408. For example, the communication resources 1430 may include a wired communication component (e.g., for coupling via USB), a cellular communication component, an NFC component, (or Low power consumption) components, components and other communication components.

[0135] The communication resources 1430 include one or more devices configured to couple to and communicate on a wired and / or wireless network (i.e., perform network operations), such as: a control logic component, one or more interface circuits, and a group of antennas (or antenna elements) in an adaptive array that can be selectively turned on and / or off by the control logic component to produce a variety of optional antenna patterns or "beam patterns." Alternatively, instead of the group of antennas, in some examples, the electronic device 1400 includes one or more nodes (e.g., pads or connectors) that can be coupled to the group of antennas. Thus, the electronic device 1400 may or may not include the group of antennas. For example, the communication resources 1430 may include a Bluetooth TM networking systems, cellular networking systems (e.g., 3G / 4G / 5G / 6G networks such as UMTS, LTE, etc.), universal serial bus (USB) networking systems, networking systems based on standards described in IEEE 802.11 (such as networking system), an Ethernet networking system, and / or another networking system.

[0136] In some implementations, the communication resources 1430 include one or more radio components, such as a wake-up radio component for receiving wake-up frames and wake-up beacons, and a main radio component for transmitting and / or receiving frames or packets during normal operating mode. The wake-up radio component and the main radio component can be implemented separately (such as using discrete components or separate integrated circuits) or can be implemented in a common integrated circuit.

[0137] The communication resources 1430 include processors, controllers, radio components / antennas, sockets / plugs, and / or other devices for coupling to each supported networked system, communicating on each supported networked system, and processing data and events for each supported networked system. It should be noted that the mechanisms for coupling to the network of a network system, communicating on the network of a network system, and processing data and events on the network of a network system are sometimes collectively referred to as the "network interface" of the network system.

[0138] The instructions 1450 may include software, programs, applications, applet, applications, or other executable code for causing at least any one of the processors 1410 to perform any one or more of the methods discussed herein. The instructions 1450 may reside completely or partially within at least one of the processors 1410 (e.g., within a cache memory of a processor), within the memory / storage device 1420, or within any suitable combination thereof. In some implementations, any portion of the instructions 1450 may be passed to the hardware resources 1402 from any combination of the peripheral device 1404 or the database 1406. Thus, the memory of the processor 1410, the memory / storage device 1420, the peripheral device 1404, and the database 1406 are examples of computer-readable and machine-readable media.

[0139] Although the foregoing discussion uses the Wi-Fi communication protocol as an illustrative example, in other specific implementations, a variety of communication protocols may be used, and more generally, wireless communication technologies may be used. Therefore, the communication technology may be used in a variety of network interfaces. In addition, although some of the operations in the foregoing specific implementations are implemented in hardware or software, in general, the operations in the foregoing specific implementations may be implemented in a variety of configurations and architectures. Thus, some or all of the operations in the foregoing specific implementations may be performed in hardware, in software, or in a combination of both hardware and software. For example, at least some of the operations in the communication technology may be implemented using instructions 1450, an operating system (such as a driver for an interface circuit in the communication resource 1430), or in firmware in an interface circuit in the communication resource 1430. Additionally or alternatively, at least some of the operations in the communication technology may be implemented in a physical layer (such as hardware in an interface circuit in the communication resource 1430). In some specific implementations, the communication technology is implemented at least in part in a MAC layer and / or a physical layer in an interface circuit in the communication resource 1430.

[0140] Although the foregoing embodiments illustrate the use of wireless signals in one or more frequency bands, in some implementations, electromagnetic signals in one or more different frequency bands are used to determine distance. For example, these signals may be communicated in one or more frequency bands, including: microwave bands, radar bands, 900 MHz, 2.4 GHz, 5 GHz, 6 GHz, 60 GHz, and / or frequency bands used by Citizens Broadband Radio Service, LTE, 5G, or any other communication system.

[0141] Although electronic device 1400 is described using specific components, in some implementations, different components and / or subsystems may be present in electronic device 1400. For example, electronic device 1400 may include one or more additional processing subsystems, memory subsystems, networking subsystems, and / or display subsystems. Additionally, one or more of the subsystems may not be present in electronic device 1400. In some implementations, electronic device 1400 may include Fig.14 In some implementations, the electronic device may include an analysis subsystem that performs at least some of the operations in the communication technology. Fig.14 , but in some implementations, some or all of a given subsystem or component may be integrated into one or more of the other subsystems or components in the electronic device 1400.

[0142] For one or more embodiments, at least one of the components shown in one or more of the foregoing figures may be configured to perform one or more operations, techniques, processes, or methods described in the following example section. For example, the baseband circuit described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples described below. For another example, the circuits associated with the UE, base station, network element, etc. described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples shown in the example section below.

[0143] In the following sections, additional exemplary embodiments are provided.

[0144] Embodiment 1 is a method for sending a high priority (HP) packet performed by a first wireless device, the method comprising: identifying an HP packet for uplink transmission; determining that a communication link for sending the HP packet is busy; generating a preemption request message; associating the preemption request message with a frame; and sending the frame to a second wireless device.

[0145] Embodiment 2 may include the subject matter of embodiment 1, wherein associating the preemption request message with the frame comprises encoding the preemption request message in an A control subfield of a QoS null frame, a QoS data frame, or a management frame.

[0146] Embodiment 3 may include the subject matter of embodiment 2, wherein the QoS null frame, the QoS data frame, or the management frame is encoded in a MAC protocol data unit (MPDU).

[0147] Embodiment 4 may include the subject matter of embodiment 1, wherein generating the preemption request message comprises encoding the preemption request message in a preamble of a PPDU comprising a control response frame.

[0148] Embodiment 5 may include the subject matter of any one of Embodiments 1 to 4, wherein the communication link is busy because the second wireless device is performing a frame burst; and the method further includes: receiving a trigger frame from the second wireless device, the trigger frame including a resource allocation for transmitting the HP packet; and transmitting the HP packet to the second wireless device according to the resource allocation indicated by the trigger frame.

[0149] Embodiment 6 may include the subject matter of any one of Embodiments 1-4, wherein the communication link is busy due to the second wireless device participating in an ongoing transmit opportunity (TXOP).

[0150] Embodiment 7 may include the subject matter of embodiment 5, further comprising: receiving a contention-free (CF) end message from the second wireless device; contending for channel access; and sending the HP packet using resources allocated after contending for channel access.

[0151] Embodiment 8 may include the subject matter of any one of Embodiments 6 to 7, further comprising: receiving a MUPPDU; identifying elements of HP data to be transmitted; encoding a preemption request message in a multi-STA BA; and transmitting the multi-STA BA to the second wireless device.

[0152] Embodiment 9 may include the subject matter of embodiment 8, further comprising: receiving a trigger frame for transmitting the HP data; and transmitting the HP data using resources associated with the trigger frame.

[0153] Embodiment 10 may include the subject matter of embodiment 8, further comprising: receiving an RDG message; and transmitting the HP data according to RDG parameters associated with the RDG message.

[0154] Embodiment 11 may include the subject matter of embodiment 8, further comprising: receiving an indication of an end of a contention-free period; contending for channel access to a channel; and transmitting the HP data on the channel.

[0155] Embodiment 12 may include the subject matter of any one of Embodiments 1-4, wherein the communication link is busy due to the second wireless device transmitting one or more physical protocol data units (PPDUs).

[0156] Embodiment 13 may include the subject matter of embodiment 12, further comprising: receiving a MU PPDU including a preemption request message; and encoding a new PPDU end indication in an MPDU associated with the MU PPDU or the SU PPDU.

[0157] Embodiment 14 may include the subject matter of Embodiment 12, further comprising: receiving a second element of HP data from the second wireless device.

[0158] Embodiment 15 may include the subject matter of any one of Embodiments 13 or 14, further comprising: receiving a multi-STA BA during a SIFS period prior to receiving the second element of HP data.

[0159] Embodiment 16 may include the subject matter of any one of Embodiments 1-5, wherein determining that the communication link used to send the HP packet is busy includes determining that a first link of a multi-link connection is busy.

[0160] Embodiment 17 may include the subject matter of Embodiment 16, wherein sending the frame to the second wireless device comprises sending the frame on a second link of the multi-link connection, wherein the preemption request identifies the first link for sending the HP packet.

[0161] Embodiment 18 may include the subject matter of Embodiment 16, wherein sending the frame comprises sending the frame on the first link of the multi-link connection, the preemption request identifying the first link for sending the HP packet.

[0162] Embodiment 19 is a method performed by a first wireless device, wherein the first wireless device communicates with a second wireless device via a wireless link, the method comprising: transmitting one or more lower priority PPDUs to the second wireless device; receiving a preemption request for a current communication from the second wireless device, wherein the preemption request is received in a QoS empty frame, a QoS data frame, or a management frame associated with a control response frame; determining to preempt the current communication; transmitting at least one of a preemption indication or a PPDU end indication to the second wireless device; and receiving a high priority packet from the second wireless device on the wireless link.

[0163] Embodiment 20 may include the subject matter of embodiment 19, wherein the preemption indication comprises an early block acknowledgement (BA), a trigger frame, a contention-free end frame, or an RDG indication for a low priority MPDU, thereby allowing the second wireless device to use the wireless medium to transmit the high priority packet.

[0164] Embodiment 21 may include the subject matter of any one of Embodiments 19-20, wherein the preemption request is encoded in an A control subfield of a control response frame, a QoS data frame, or a management frame.

[0165] Embodiment 22 may include the subject matter of any one of Embodiments 19 to 21, wherein the preemption request includes information corresponding to the high priority packet including an indication of an amount of data associated with the high priority packet.

[0166] Embodiment 23 may include the subject matter of embodiment 19, further comprising: encoding a new PPDU end indication in the last MPDU of the low priority PPDU; sending the last MPDU in the last low priority PPDU to the second wireless device; and receiving an early BA.

[0167] Embodiment 24 may include the subject matter of embodiment 23, further comprising encoding a TXOP takeover (TOT) indicator with the new end-of-PPDU indication to alert the second wireless device that the first wireless device will take over the TXOP.

[0168] Embodiment 25 may include the subject matter of Embodiment 23, wherein the new end-of-PPDU indication is encoded in the A-control subfield of the last MPDU associated with the TXOP.

[0169] Embodiment 26 may include a subject matter according to any one of embodiments 27 to 25, the subject matter further comprising: transmitting a multi-user (MU) PPDU addressed to a plurality of second wireless devices; receiving a multi-STA BA including the preemption request message from at least one second wireless device among the plurality of second wireless devices; transmitting a contention-free end indication or trigger frame to at least one second wireless device among the plurality of second wireless devices or using a reverse grant (RDG) mechanism, wherein the RDG mechanism may grant the remaining TXOP to the second wireless device; and receiving the HP transmission from at least one device among the second plurality of devices.

[0170] Embodiment 27 may include a subject matter according to any one of embodiments 19 to 23, wherein the subject matter further includes: encoding a preemption request message in one or more MPDUs included in a multi-user (MU) PPDU (MU PPDU); transmitting the MU PPDU addressed to a plurality of second wireless devices; receiving a new PPDU end indication from at least one second wireless device among the plurality of second wireless devices; sending a MU block acknowledgment to at least one second wireless device among the plurality of second wireless devices; and sending the HP PPDU to at least one second wireless device among the plurality of second wireless devices.

[0171] Embodiment 28 may include the subject matter of any one of Embodiments 19 to 27, wherein the first wireless device transmits a preemption request indication to a plurality of second wireless devices operating in a multi-user network environment using a first link.

[0172] Embodiment 29 may include the subject matter of Embodiment 28, wherein at least one second wireless device of the plurality of second wireless devices comprises a wireless station in a multi-link device (MLD).

[0173] Embodiment 30 may include a subject matter according to any one of embodiments 29 to 30, the subject matter further comprising: receiving a PPDU early termination indication from at least one second wireless device among the multiple second wireless devices, the PPDU early termination indication indicating that at least one second wireless device has accepted the preemption indication request.

[0174] Embodiment 31 is an apparatus configured to perform any of the operations described in embodiments 19 to 30.

[0175] Embodiment 32 is an apparatus configured to perform any of the operations described in embodiments 1 to 18.

[0176] Embodiment 33 is a device configured to perform the operations described in this specification.

[0177] Embodiment 34 is an access point configured to perform any of the operations of claims 13 to 20.

[0178] Embodiment 35 is a non-AP STA configured to perform the operations described in this specification.

[0179] Embodiment 36 may include one or more non-transitory computer-readable media, wherein the one or more non-transitory computer-readable media include instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform one or more elements of a method described or related to any one of Embodiments 1 to 35 or any other method or process described herein.

[0180] Embodiment 37 may include a device comprising logic components, modules or circuits for performing one or more elements of the method described in accordance with or related to any of Embodiments 1 to 36 or any other method or process described herein.

[0181] Embodiment 38 may include methods, techniques or processes described or related to any one of Embodiments 1 to 37, or portions or components thereof.

[0182] Embodiment 39 may include a device comprising: one or more processors and one or more computer-readable media, wherein the one or more computer-readable media include instructions that, when executed by the one or more processors, cause the one or more processors to perform a method, technique, process, or portion thereof as described in or related to any one of Embodiments 1 to 38.

[0183] Embodiment 40 may include a signal as described or related to any one of Embodiments 1 to 39, or a portion or component thereof.

[0184] Embodiment 41 may include a datagram, information element, packet, frame, segment, PDU or message, or a portion or component thereof, as described or associated with any one of Embodiments 1 to 40, or otherwise described in the present disclosure.

[0185] Embodiment 42 may include a signal encoded with data as described or associated with any one of Embodiments 1 to 41, or a portion or component thereof, or otherwise described in this disclosure.

[0186] Embodiment 43 may include a signal encoded with a datagram, IE, packet, frame, segment, PDU or message as described or associated with any one of Embodiments 1 to 42, or a portion or component thereof, or otherwise described in the present disclosure.

[0187] Embodiment 44 may include an electromagnetic signal carrying computer-readable instructions, wherein the computer-readable instructions are executed by one or more processors to cause the one or more processors to perform a method, technique, or process, or a portion thereof, as described or related to any one of Embodiments 1 to 43.

[0188] Embodiment 45 may include a computer program, the computer program including instructions, wherein the program is executed by a processing element for causing the processing element to perform a method, technique, or process, or a portion thereof, according to or related to any one of embodiments 1 to 44. The operation or action performed by the instructions executed by the processing element may include a method according to any one of embodiments 1 to 30.

[0189] Embodiment 47 may include a method of communicating in a wireless network as shown and described herein.

[0190] Embodiment 48 may include a system for providing wireless communication as shown and described herein. The operations or actions performed by the system may include a method according to any one of Embodiments 1 to 47.

[0191] Embodiment 49 may include an apparatus for providing wireless communications as shown and described herein. The operations or actions performed by the apparatus may include a method according to any one of Embodiments 1 to 48.

[0192] Previously described embodiments 1 to 49 can be implemented using: a computer-implemented method; a non-transitory computer-readable medium storing computer-readable instructions to perform the computer-implemented method; and a computer system comprising a computer memory interoperably coupled to a hardware processor configured to execute the computer-implemented method or instructions stored on the non-transitory computer-readable medium.

[0193] A system (e.g., a base station, a device including one or more baseband processors, etc.) may be configured to perform a specific operation or the action by having software, firmware, hardware, or a combination thereof installed on the system that causes the system to perform the action in operation. The operation or the action performed by the system may include a method according to any one of embodiments 1 to 20.

[0194] Unless explicitly stated otherwise, any of the above examples may be combined with any other example (or combination of examples). The foregoing description of one or more specific implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise form disclosed. In view of the above teachings, modifications and variations are possible or can be obtained from the practice of various embodiments.

[0195] Although the above embodiments have been described in considerable detail, numerous variations and modifications will become apparent to those skilled in the art once the above disclosure is fully appreciated. It is intended that the following claims be interpreted to include all such variations and modifications.

[0196] It is understood that the use of personally identifiable information should be subject to privacy policies and practices that are generally recognized to meet or exceed industry or government requirements for maintaining user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of the authorized use should be clearly stated to users.

Claims

1. A method for sending a high priority (HP) packet performed by a first wireless device, the method comprising: identifying the HP packet for uplink transmission; Determining that a communication link for sending the HP packet is busy; Generate a preemption request message; associating the preemption request message with a frame; as well as The frame is sent to a second wireless device.

2. The method of claim 1 , wherein associating the preemption request message with the frame comprises: The preemption request message is encoded in the A control subfield of a QoS null frame, a QoS data frame or a management frame.

3. The method of claim 2, wherein the QoS null frame, the QoS data frame, or the management frame is encoded in a MAC protocol data unit MPDU.

4. The method according to claim 1, wherein generating the preemption request message comprises: The preemption request message is encoded in a preamble of a PPDU including a control response frame.

5. The method of claim 1, wherein the communication link is busy because the second wireless device is participating in an ongoing transmit opportunity (TXOP).

6. The method of claim 1, wherein the communication link is busy due to the second wireless device performing a frame burst, the method further comprising: receiving a trigger frame from the second wireless device, the trigger frame comprising a resource allocation for transmitting the HP packet; as well as The HP packet is transmitted to the second wireless device according to the resource allocation indicated by the trigger frame.

7. The method according to claim 6, further comprising: receiving a contention-free CF end message from the second wireless device; Compete for channel access; as well as The HP packet is sent using resources allocated after contention for channel access.

8. The method according to claim 6, further comprising: Receive MU PPDU; identifying elements of the HP data to be transmitted; Encoding the preemption request message in a multi-STA BA; as well as The multi-STA BA is transmitted to the second wireless device.

9. The method according to claim 8, further comprising: receiving the trigger frame for transmitting the HP data; as well as The HP data is transmitted using resources associated with the trigger frame.

10. The method according to claim 8, further comprising: Receive RDG message; as well as The HP data is transmitted according to RDG parameters associated with the RDG message.

11. The method according to claim 8, further comprising: receiving an indication of the end of a contention-free period; contending for channel access to a channel; as well as The HP data is transmitted on the channel.

12. The method of claim 1, wherein the communication link is busy due to the second wireless device transmitting one or more physical protocol data units (PPDUs).

13. The method according to claim 12, further comprising: receiving a MU PPDU including the preemption request message; as well as A new PPDU end indication is encoded in the MPDU associated with the MU PPDU or SU PPDU.

14. The method of claim 12, further comprising receiving a second element of HP data from the second wireless device.

15. The method of claim 14, further comprising receiving a multi-STA BA during a SIFS period prior to receiving the second element of HP data.

16. The method of claim 1, wherein determining that the communication link used to send the HP packet is busy comprises: It is determined that a first link of the multi-link connection is busy.

17. The method of claim 16, wherein sending the frame to the second wireless device comprises: The frame is sent on a second link of the multi-link connection, wherein the preemption request message identifies the first link used to send the HP packet.

18. The method of claim 16, wherein sending the frame comprises: The frame is sent on the first link of the multi-link connection, and the preemption request message identifies the first link used to send the HP packet.

19. A method performed by a first wireless device, the first wireless device communicating with a second wireless device via a wireless link, the method comprising: transmitting one or more lower priority PPDUs to the second wireless device; receiving a preemption request for a current communication from the second wireless device; Determining to preempt the current communication; transmitting at least one of a preemption indication or a PPDU end indication to the second wireless device; as well as A high priority packet is received from the second wireless device over the wireless link.

20. An apparatus comprising: one or more processors; and A memory storing instructions that, when executed, are configured to cause the one or more processors to perform operations including: Identify high priority HP packets for uplink transmission; Determining that a communication link for sending the HP packet is busy; Generate a preemption request message; associating the preemption request message with a frame; as well as The frame is sent to a second wireless device.

Images