Wireless communication methods and communication devices

Abstract

Provided are wireless communication methods and communication devices. A method comprises: a first device sending a first frame to a second device, wherein a first link and a second link have been established between the first device and the second device, the first frame is used for preempting a TXOP of the first link, and the first frame satisfies one or more of the following: the first frame is transmitted by means of the second link; and, when a first moment is earlier than a second moment, the first frame is transmitted by means of the first link, the first moment being a moment when the first device acquires in the first link a transmission resource for transmitting the first frame, and the second moment being a moment when the first device acquires in the second link a transmission resource for transmitting the first frame. The present application may use multiple links to initiate on a certain link a preemption of TXOPs of other links. Thus, even if a link is occupied, the link can still be preempted by means of a first frame, so that traffic to be transmitted can be transmitted as soon as possible, thus achieving low-delay transmission.

Description

Wireless communication method and communication device Technical Field

[0001] The present application relates to the field of communication technology, and more particularly, to a wireless communication method and a communication device. Background Art

[0002] Reducing communication latency is an important goal of some communication systems. In relevant communication protocols, if the channel is occupied, the data stream to be transmitted must wait for the next access competition before it can begin transmission, which will result in very high latency.

[0003] Summary of the Invention

[0004] The present application provides a wireless communication method and a communication device. The following introduces various aspects of the present application.

[0005] In a first aspect, a method for wireless communication is provided, the method comprising: a first device sending a first frame to a second device; wherein a first link and a second link are established between the first device and the second device, the first frame is used to indicate the seizure of part or all of the transmission resources in a transmission opportunity (TXOP) of the first link, and the first frame satisfies one or more of the following: the first frame is transmitted through the second link; when the first moment is earlier than the second moment, the first frame is transmitted through the first link, the first moment is the moment when the first device obtains the transmission resources for transmitting the first frame on the first link, and the second moment is the moment when the first device obtains the transmission resources for transmitting the first frame on the second link.

[0006] In a second aspect, a method for wireless communication is provided, the method comprising: a second device receiving a first frame sent by a first device; wherein a first link and a second link are established between the first device and the second device, the first frame is used to indicate the seizure of part or all of the transmission resources in the TXOP of the first link, and the first frame satisfies one or more of the following: the first frame is transmitted through the second link; when the first moment is earlier than the second moment, the first frame is transmitted through the first link, the first moment is the moment when the first device obtains the transmission resources for transmitting the first frame on the first link, and the second moment is the moment when the first device obtains the transmission resources for transmitting the first frame on the second link.

[0007] In a third aspect, a communication device is provided, which is a first device and includes: a first device sending unit, used to send a first frame to a second device; wherein a first link and a second link are established between the first device and the second device, and the first frame is used to indicate the seizure of part or all of the transmission resources in the TXOP of the first link, and the first frame satisfies one or more of the following: the first frame is transmitted through the second link; when the first moment is earlier than the second moment, the first frame is transmitted through the first link, the first moment is the moment when the first device obtains the transmission resources for transmitting the first frame on the first link, and the second moment is the moment when the first device obtains the transmission resources for transmitting the first frame on the second link.

[0008] In a fourth aspect, a communication device is provided, which is a second device, and includes: a receiving unit, used to receive a first frame sent by a first device; wherein a first link and a second link are established between the first device and the second device, and the first frame is used to indicate the seizure of part or all of the transmission resources in the TXOP of the first link, and the first frame satisfies one or more of the following: the first frame is transmitted through the second link; when the first moment is earlier than the second moment, the first frame is transmitted through the first link, the first moment is the moment when the first device obtains the transmission resources for transmitting the first frame on the first link, and the second moment is the moment when the first device obtains the transmission resources for transmitting the first frame on the second link.

[0009] In a fifth aspect, a communication device is provided, comprising a processor and a memory, wherein the memory is used to store one or more computer programs, and the processor is used to call the computer program in the memory to enable the communication device to perform some or all of the steps in the above-mentioned various aspects of the method.

[0010] In a sixth aspect, an embodiment of the present application provides a communication system, which includes the above-mentioned communication device. In another possible design, the system may also include other devices that interact with the communication device in the solution provided in the embodiment of the present application.

[0011] In a seventh aspect, an embodiment of the present application provides a computer-readable storage medium, which stores a computer program, and the computer program enables a communication device to execute part or all of the steps in the methods of the above aspects.

[0012] In an eighth aspect, embodiments of the present application provide a computer program product, wherein the computer program product includes a non-transitory computer-readable storage medium storing a computer program, wherein the computer program is operable to cause a communication device to perform some or all of the steps of the methods described in each of the above aspects. In some implementations, the computer program product may be a software installation package.

[0013] In a ninth aspect, an embodiment of the present application provides a chip comprising a memory and a processor, wherein the processor can call and run a computer program from the memory to implement some or all of the steps described in the methods of the above aspects.

[0014] This application can leverage multi-link technology to initiate a preemption of the TXOPs of other links on a particular link. Therefore, even if a link is occupied, it can be preempted by transmitting the first frame on another link, allowing the data stream to be transmitted to be sent as quickly as possible, thus achieving low-latency transmission. Furthermore, because this application is based on multi-link implementation, it can also combine the advantages of multi-link, such as achieving high throughput. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] FIG1 is a schematic diagram of a wireless communication system used in an embodiment of the present application.

[0016] FIG2 is a schematic diagram of the transmission process of Solution 1 for low-latency transmission.

[0017] FIG3 is a schematic diagram showing the delay benefit between a single link and multiple links.

[0018] FIG4 is a schematic diagram of the transmission process of the restricted-target wake time (R-TWT) technology.

[0019] FIG5 is a schematic flowchart of a wireless communication method provided in an embodiment of the present application.

[0020] FIG6A is a schematic diagram of a first frame format provided in an embodiment of the present application.

[0021] FIG6B is a schematic diagram of the control field format included in the first frame provided in an embodiment of the present application.

[0022] FIG7 is a schematic diagram of the format of a first response frame provided in an embodiment of the present application.

[0023] FIG8 is a schematic diagram of a preemptive data stream information element provided in an embodiment of the present application.

[0024] FIG9 is a schematic diagram of the format of an A-control field carrying second information provided in an embodiment of the present application.

[0025] FIG. 10A is an example diagram of scenario 1. FIG.

[0026] FIG. 10B is a diagram illustrating an example of a communication process for the scenario shown in FIG. 10A .

[0027] FIG. 10C is another exemplary diagram of a communication process for the scenario shown in FIG. 10A .

[0028] FIG11 is a schematic diagram of a primitive interaction method provided in an embodiment of the present application.

[0029] FIG. 12A is an example diagram of scenario 2. FIG.

[0030] FIG. 12B is a diagram illustrating an example of a communication process for the scenario shown in FIG. 12A .

[0031] FIG. 12C is another example diagram of a communication process for the scenario shown in FIG. 12A .

[0032] FIG12D is another example diagram of a communication process for the scenario shown in FIG12A .

[0033] FIG. 13A is an example diagram of scenario 3. FIG.

[0034] FIG. 13B is a diagram illustrating an example of a process of sharing a TXOP.

[0035] FIG13C is an example diagram of a communication process for the scenario shown in FIG13A .

[0036] FIG. 14A is an example diagram of scenario 4. FIG.

[0037] FIG. 14B is a diagram illustrating an example of a communication process for the scenario shown in FIG. 14A .

[0038] FIG15 is a diagram illustrating an example of a communication process in which the first device ends its preemptive TXOP and the preempted device continues to transmit.

[0039] FIG16 is a schematic structural diagram of a communication device provided in an embodiment of the present application.

[0040] Figure 17 is a schematic structural diagram of another communication device provided in an embodiment of the present application.

[0041] FIG18 is a schematic structural diagram of a device for communication provided in an embodiment of the present application. DETAILED DESCRIPTION

[0042] The technical solution in this application will be described below with reference to the accompanying drawings.

[0043] Communication System

[0044] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as wireless local area networks (WLAN), wireless fidelity (WiFi), high performance radio local area networks (HIPELAN), wide area networks (WAN), cellular networks, or other communication systems. For another example, the technical solutions provided in the embodiments of the present application can be applied to communication systems that adopt the 802.11 standard. For example, the 802.11 standard includes but is not limited to the 802.11ax standard, the 802.11be standard, and the next generation 802.11 standard.

[0045] FIG1 is a schematic diagram of a communication system applicable to embodiments of the present application. Referring to FIG1 , the communication devices in the communication system 100 may include access points (APs) 111 and 112, and stations (STAs) 121 and 122. STA 121 may access the network through AP 111, and STA 122 may access the network through AP 112.

[0046] In some implementations, a STA may establish an association with one or more APs, after which the associated STAs and APs may communicate. For example, as shown in FIG1 , AP 111 and STA 121 may communicate after establishing an association, and AP 112 and STA 122 may communicate after establishing an association.

[0047] In some implementations, the communication in the communication system 100 may be communication between an AP and a non-AP STA, communication between a non-AP STA and a non-AP STA, or communication between a STA and a peer STA, where a peer STA may refer to a device that communicates with the STA peer, for example, the peer STA may be an AP or a non-AP STA.

[0048] It should be understood that FIG1 exemplarily shows two AP STAs and two non-AP STAs, and the communication system 100 may also include a larger number of AP STAs, or the communication system 100 may include other numbers of non-AP STAs, which is not limited in the embodiments of the present application.

[0049] In addition, the above communication system can be applied to scenarios of multi-device collaboration, such as multi-AP (multiple access points, Multi-AP) collaboration, or multi-site collaboration.

[0050] In the embodiments of this application, the names of AP and / or STA are not limited. In some scenarios, AP can also be called AP STA, that is, in a sense, AP is also a type of STA. In other scenarios, STA can also be called non-AP STA.

[0051] In some scenarios, the aforementioned communication device may also be a "multi-link device (MLD)," i.e., a device that can communicate via multiple communication links, where the multiple communication links may include communication links in different frequency bands, such as millimeter wave bands and / or low-frequency bands. Generally, if the multi-link device is an AP, the AP may also be referred to as a "multi-link AP." If the multi-link device is a STA, the STA may also be referred to as a "multi-link STA."

[0052] In the embodiments of the present application, an AP may be a device in a wireless network. An AP may be a communication entity such as a communication server, a router, a switch, or a bridge, or the AP device may include various forms of macro base stations, micro base stations, relay stations, etc. Of course, the AP may also be a chip, circuit, or processing system in these various forms of devices, thereby realizing the methods and functions of the embodiments of the present application. The AP device can be applied to a variety of scenarios, such as sensor nodes in smart cities (e.g., smart water meters, smart electricity meters, smart air detection nodes), smart devices in smart homes (e.g., smart cameras, projectors, displays, televisions, speakers, refrigerators, washing machines, etc.), nodes in the Internet of Things, entertainment terminals (e.g., wearable devices such as AR and VR), smart devices in smart offices (e.g., printers, projectors, etc.), Internet of Vehicles devices in the Internet of Vehicles, and some infrastructure in daily life scenarios (e.g., vending machines, self-service navigation counters in supermarkets, self-service checkout devices, self-service ordering machines), etc.

[0053] In some implementations, the role of a STA in a communication system is not absolute; in some scenarios, a STA can function as an AP. For example, when a mobile phone is connected to a router, it can be a non-AP STA, while when it is acting as a hotspot for other phones, it functions as an AP.

[0054] In the embodiments of the present application, a STA device in the embodiments of the present application may be a device with wireless transceiver functions, such as a device that supports the 802.11 series of protocols and can communicate with an AP or other STAs. For example, a STA is any user communication device that allows a user to communicate with an AP and, in turn, with a WLAN. STA devices include, for example, user equipment (UE), mobile station (MS), mobile terminal (MT), access terminal, subscriber unit, subscriber station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or user device.

[0055] The STA in the embodiment of the present application may also be a device that provides voice / data connectivity to users, such as a handheld device or vehicle-mounted device with wireless connection function. Examples include: mobile phones, tablet computers, laptop computers, PDAs, mobile internet devices (MIDs), wearable devices, virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical surgery, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, cellular phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs), handheld devices with wireless communication capabilities, computing devices or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, terminal devices in 5G networks or future-evolved public land mobile communication networks. The terminal equipment in the network (PLMN), etc., is not limited to this in the embodiments of the present application.

[0056] By way of example and not limitation, in the embodiments of this application, the STA device may also be a wearable device. Wearable devices, also known as wearable smart devices, are a general term for wearable devices that utilize wearable technology to intelligently design and develop wearable devices, such as glasses, gloves, watches, clothing, and shoes. Examples include smart watches or smart glasses, as well as devices that focus on a specific application function and require integration with other devices, such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring.

[0057] In addition, in embodiments of the present application, the STA device can also be a terminal device in the Internet of Things (IoT) system. The IoT is an important component of the future development of information technology. Its main technical feature is to connect objects to the network through communication technology, thereby realizing an intelligent network that interconnects people and machines and things. In embodiments of the present application, IoT technology can achieve massive connections, deep coverage, and terminal power saving through, for example, narrowband (NB) technology.

[0058] Furthermore, in the embodiments of the present application, the STA device may be a device in a connected vehicle system. The communication methods in a connected vehicle system are collectively referred to as V2X (where X represents everything). For example, V2X communication includes vehicle-to-vehicle (V2V) communication, vehicle-to-infrastructure (V2I) communication, vehicle-to-pedestrian (V2P) communication, and vehicle-to-network (V2N) communication.

[0059] In addition, in an embodiment of the present application, the STA device may also include sensors such as smart printers, train detectors, and gas stations. Its main functions include collecting data (partial terminal devices), receiving control information and downlink data from AP devices, and sending electromagnetic waves to transmit data to AP devices.

[0060] In addition, the AP device in the embodiment of the present application may be a device for communicating with a STA device. The AP device may be a network device in a wireless local area network. The AP device may be used to communicate with the STA device through the wireless local area network.

[0061] From the perspective of the communication standards supported by the AP, in some implementations, the AP can be a device that supports the 802.11be standard. The AP can also be a device that supports various current and future 802.11 family WLAN standards, such as 802.11ax, 802.11ac, 802.11n, 802.11g, 802.11b, and 802.11a.

[0062] From the perspective of STA-supported communication standards, in some implementations, non-AP STAs can support the 802.11be standard. Non-AP STAs can also support various current and future 802.11 family wireless local area network (WLAN) standards, including 802.11ax, 802.11ac, 802.11n, 802.11g, 802.11b, and 802.11a.

[0063] In the embodiments of the present application, there is no limitation on the frequency bands supported by WLAN technology. In some implementations, the frequency bands supported by WLAN technology may include, but are not limited to, low frequency bands (e.g., 2.4 GHz, 5 GHz, 6 GHz) and high frequency bands (e.g., 45 GHz, 60 GHz).

[0064] It should be understood that the specific forms of STA devices and AP devices in the embodiments of the present application are not particularly limited and are merely illustrative.

[0065] Low-latency transmission

[0066] Reducing latency is a key goal of some communication systems, such as Wi-Fi 8. In Wi-Fi protocols, if a single-link channel is occupied, bursty low-latency traffic must wait for the next access contention before transmission can begin, resulting in very high latency.

[0067] A low-latency data stream may refer to a data stream identified by a restricted target wake time traffic identifier (R-TWT TID) or a data stream identified by a stream classification service identifier (SCS ID). A low-latency data stream may be event-driven. For example, a low-latency data stream may include one or more of the following: a data stream generated by user instant messaging interactions, or a data stream generated by sensors.

[0068] Non-low-latency data flow may refer to a data flow that is neither identified by the R-TWT TID nor by the SCS ID.

[0069] It should be noted that "low-latency data flow" is only an exemplary representation. In some embodiments, low-latency data flow may also be referred to as low-latency data, delay-sensitive data, delay-sensitive data flow, low-latency traffic, etc.

[0070] For example, the related art proposes the following three possible solutions to achieve low-latency transmission.

[0071] Solution 1: Communication devices can divide the physical layer protocol data unit (PPDU) into several small PPDUs and insert interframe spaces (represented by xIFS) between the small PPDUs to provide preemptive opportunities for devices that need to transmit low-latency data streams.

[0072] Figure 2 is a schematic diagram of the transmission process of Scheme 1. As shown in Figure 2, within the TXOP obtained by the AP, the AP divides the downlink (DL) PPDU sent to STA1 into several small DL PPDUs. At the moment shown in Figure 2, the low latency packet sent to STA2 arrives at the AP (low latency packet arrives at AP for STA2). During the xIFS period, other communication devices can use an interframe interval shorter than the xIFS (Tp as shown in Figure 2) to transmit a preemption request (PR), thereby interrupting the AP's downlink transmission. For the situation shown in Figure 2, in response to the arrival of the low latency packet, the AP can interrupt the original downlink transmission and transmit a DL low latency (LL) PPDU to STA2. After the DL LL PPDU is transmitted, the AP can continue the original downlink transmission to STA1.

[0073] In some embodiments, whether preemption is allowed within the TXOP can be indicated in the first control frame of the TXOP, and whether preemption is allowed after the end of the PPDU can be indicated in the universal signal (U-SIG) or ultra-high reliability signal field (UHR-SIG) of the current PPDU. The relevant embodiments also design uplink and downlink preemption for the downlink TXOP. When a low-latency service arrives, preemption is initiated within the xIFS interval after the end of the current PPDU transmission, and the LL PPDU is sent. The LL PPDU can carry an indication bit, which can indicate that preemption is not allowed for the current PPDU. Continuing to refer to Figure 2, the DL LL PPDU carries an indication bit, indicating that preemption is not allowed within the time range shown in Figure 2.

[0074] Solution 2: Use multi-link operation (MLO) to achieve low-latency transmission. For example, MLO can initiate channel access in different links.

[0075] FIG3 exemplarily shows a comparison of the delay benefits of an extremely high throughput (EHT) STA between a single link and multiple links.

[0076] In Figure 3, the solid arrows represent packets queued at the EHT STA. The dotted double arrows represent the latency of a packet (packet, P) x, where x is the ID of the packet.

[0077] In a single-link scenario, after P1 arrives, it must wait for an EHT STA transmission opportunity on link 1 before it can be sent. In a multi-link scenario, after P1 arrives, if an EHT STA transmission opportunity exists on link 1 or link 2, P1 can be sent on either link 1 or link 2. Figure 3 clearly shows that compared to a single-link scenario, the latency of packets P1, P3, and P4 is significantly reduced in the multi-link scenario.

[0078] As shown in Figure 3, multi-link technology provides devices with more transmission opportunities. Utilizing multiple links can improve throughput and reduce channel access latency.

[0079] Solution three, R-TWT technology. R-TWT technology enables STAs in the basic service set (BSS) to use enhanced medium access protection and resource reservation mechanisms to transmit low-latency services. R-TWT technology can improve the reliability of transmission, and the low-latency data flow is periodic. As shown in Figure 4, for R-TWT SP members, if there is high priority data (high priority data), the STA can transmit the high priority data within the negotiated R-TWT service period (service period, SP). Among them, high priority data may include low-latency data streams.

[0080] The above low-latency transmission solutions all have some problems.

[0081] Regarding Solution 1, on the one hand, modifications to the PPDU may result in significant protocol changes. On the other hand, the inserted interframe space (xIFS) increases data transmission latency and reduces radio resource utilization. Furthermore, since Solution 1 is designed only for a single link, even if expanded to multiple links, it cannot leverage the characteristics of multiple links to achieve lower latency and higher throughput.

[0082] For Option 2, while multiple link resources can, to a certain extent, provide more transmission opportunities and bandwidth, thereby reducing access and transmission latency, latency due to contention for access is unavoidable. Furthermore, if multiple links are occupied, communications equipment will still be unable to obtain resources in a timely manner to prioritize the transmission of low-latency data streams. Furthermore, if links have issues such as poor link quality or limited bandwidth, further latency will be introduced, a problem that is particularly pronounced in high-capacity, low-latency services.

[0083] For solution three, although R-TWT technology solves the reliability problem of periodic low-latency data stream transmission, it cannot guarantee bursty low-latency data stream transmission.

[0084] Figure 5 is a schematic flowchart of a wireless communication method provided by an embodiment of the present application. The method shown in Figure 5 can be performed by a first device and a second device. The first device and the second device can belong to the same BSS. Both the first device and the second device can be MLDs. The first device can include an AP MLD or a non-AP MLD. The second device can include an AP MLD or a non-AP MLD.

[0085] Multiple links may be established or maintained between the first device and the second device. The multiple links may include a first link and a second link. The first link and the second link may be any two of the multiple links.

[0086] The method shown in FIG. 5 may include step S510 .

[0087] Step 510: The first device sends a first frame to the second device.

[0088] The first frame can be used to indicate the seizure of some or all transmission resources in the TXOP of the first link. It is understandable that the purpose of the first device sending the first frame is to actively send a signal through the TXOP of the first link. It should be noted that if the first device successfully completes the TXOP of the first link, the holder of the TXOP may change, for example, the holder of the TXOP may become the first device, or the holder of the TXOP may not change, for example, the first device may use some or all transmission resources in the TXOP for uplink transmission.

[0089] For the convenience of description, “seizing part or all of the transmission resources in the TXOP of a certain link” will be referred to as “seizing the TXOP of a certain link” hereinafter.

[0090] In some embodiments, the first frame may be transmitted via the second link. That is, via the first frame transmitted via one link in the multi-link, the first device may request to preempt the TXOP of another link of the second device. Based on this, the first frame may be a preemption request frame. The preemption request frame may be used to request to preempt the TXOP of the first link.

[0091] In some embodiments, if the first time is earlier than or equal to the second time, the first frame can be sent via the first link. The first time is the time when the first device obtains transmission resources for transmitting the first frame on the first link, and the second time is the time when the first device obtains transmission resources for transmitting the first frame on the second link.

[0092] Since the first device is the sender of the preemption request frame and the second device is the receiver of the preemption request frame, the first device can be called the preemption initiator or the device with the preemption request. Correspondingly, the second device can be called the preemptee or the preempted device.

[0093] Since, in some scenarios, the second link is used to transmit the preemption request frame, the second link may also be referred to as the preemption initiating link. Since the TXOP of the first link is preempted, the first link may also be referred to as the preempted link.

[0094] It should be noted that, for the convenience of description, TXOPs not explicitly specified below are all TXOPs of the second device on the first link.

[0095] In some embodiments, after the data stream arrives at the first device, the first device may transmit a first frame on the second link to preempt the TXOP of the first link. If the TXOP preemption of the first link is successful, the first device may transmit the data stream on the preempted TXOP.

[0096] As can be seen from this, the present application can leverage the multi-link feature to initiate a preemption of the TXOP of other links on a particular link. Therefore, even if a link is occupied, it can be preempted in the first frame, allowing the data stream to be transmitted to be sent as quickly as possible, thus achieving low-latency transmission. Furthermore, since the present application is based on a multi-link implementation, it can also combine the advantages of multi-link, such as achieving high throughput.

[0097] It should be noted that this application does not limit the frequency bands of the first link and the second link. The first link or the second link can be any one of the frequency bands of 2.4 / 5 / 6 GHz. This application also does not limit the frequency band combination of the first link and the second link. For example, the frequency band combination can be 2.4GHz+2.4GHz, 2.4GHz+5GHz, or 2.4GHz+6GHz, etc. For different frequency band combinations, since different links have different link qualities and different sizes of bandwidth, different low latency and throughput benefits may be generated. In general, this application can always achieve a certain degree of improvement in low latency performance and throughput.

[0098] If the first frame successfully seizes the TXOP of the first link, the first device can send the signal to be sent on the first link and the second link. In other words, signals can be sent simultaneously through multiple links, thereby improving throughput.

[0099] In the case that the first frame fails to seize the TXOP of the first link, the first device can still send the signal to be sent on the second link, thereby ensuring that the first device can send the data stream as soon as possible.

[0100] It should be noted that the first device or the second device may be an MLD device in synchronous transmit receive (STR) mode to transmit and / or receive on multiple links simultaneously without aligning the transmission direction and the transmission end time.

[0101] The first device can access the second link and send a first frame on the second link. For example, the first device can use high-priority channel access parameters to quickly access the second link. Rapid access to the second link allows for early transmission of data streams on the second link and early application for preemption of the TXOP of the first link using the first frame transmitted on the second link, thereby reducing the latency of the first device sending data streams.

[0102] In some embodiments, the high-priority channel access parameter may be a channel access parameter less than a first threshold. The first threshold may be a positive number. For example, the first device may access the second link using a first enhanced distributed channel access (EDCA) access parameter less than the first threshold. The first EDCA access parameter may include an arbitration inter-frame space (AIFSN) value and / or a contention window (CW) value.

[0103] In some embodiments, after accessing the second link, the first device may send a CTS-to-self frame to reserve a TXOP, thereby sending a data stream on the second link.

[0104] The first device can detect the busy / idle status and / or the network allocation vector (NAV) value on the first link. The detection can be achieved through physical carrier sensing and / or virtual carrier sensing. Based on the detected NAV value, the first device can estimate the remaining duration of the TXOP of the first link. Based on the remaining duration of the TXOP, the first device can determine whether to initiate preemption of the TXOP of the first link. For example, if the remaining duration of the TXOP of the first link is sufficient to meet the duration allowed for initiating TXOP preemption and / or meet all or part of the requirements for transmitting low-latency data streams, the first device will initiate TXOP preemption on the first link.

[0105] Regardless of whether the first frame successfully preempts the TXOP on the first link, the first device can send the signal to be sent on the second link. For example, the first device can send a CTS-to-self frame on the second link to reserve a TXOP on the second link and start sending the PPDU after a SIFS interval.

[0106] In some embodiments, the first frame may be used to preempt the TXOP of one or more links. The one or more links may include the first link. That is, the first frame transmitted via a link may request to preempt the TXOP of the one or more links.

[0107] In some embodiments, the first frame may be used to indicate one or more of the following information: information requesting to seize part or all of the transmission resources of a TXOP; information requesting to seize the data stream to be transmitted; and information requesting to seize the link to which the TXOP belongs. Each of these information is described below.

[0108] The information requesting to preempt part or all of the transmission resources of the TXOP may include one or more of the following: part or all of the duration of the TXOP, and part or all of the bandwidth of the TXOP.

[0109] The information about the part or all transmission resources of the TXOP requested to be preempted may be carried in the transmission resource field in the first frame. The "transmission resource" field is only an exemplary name for carrying the information about the part or all transmission resources of the TXOP requested to be preempted, and the field may also be called by other names.

[0110] The data flow information requesting to preempt TXOP may be used to indicate one or more of the following information of the data flow: a traffic ID (TID), a data flow queue size, and a scaling factor of the data flow queue size.

[0111] The TID may indicate the traffic category (TC) and / or priority of the low-latency data flow. The TID value may be an integer greater than or equal to 0. For example, the TID value may be any one of 0 to 7.

[0112] The TID may be carried in a TID field in the first frame. "TID field" is only an exemplary name for a field carrying the TID, and the field may also be called other names.

[0113] The data flow queue size may indicate the size of the data flow to be sent by the first device. The data flow queue size may be carried in the Low Latency Data Flow Queue Size (LL Traffic Queue Size) field in the first frame. The "Low Latency Data Flow Queue Size field" is merely an exemplary name for a field carrying the queue size, and the field may also be referred to by other names.

[0114] This application does not limit the representation of the data flow queue size. For example, the data flow queue size can be represented by the expected transmission duration of the data flow. For another example, the data flow queue size can be represented by the bytes occupied by the data flow.

[0115] The queue size scaling factor can represent the unit of the value indicated by the queue size field. The queue size is multiplied by this scaling factor to obtain the actual value of the queue size. For example, the queue size scaling factor can be 16 bytes, 256 bytes, 2048 bytes, or 32768 bytes. The queue size scaling factor can be carried in the scaling factor field of the first frame. The scaling factor field can be 2 bits. Values ​​of 0 to 3 can correspond to 16 bytes, 256 bytes, 2048 bytes, and 32768 bytes, respectively. "Scaling factor field" is merely an exemplary name for a field that carries the units of the queue size; this field may also be referred to by other names.

[0116] The information about the link to which the TXOP preemption request belongs may include the link ID of the link to which the TXOP preemption request belongs. The link ID of the link to which the TXOP preemption request belongs may be represented by a bitmap. The link ID bitmap field of the first frame may carry the link ID of the link to which the TXOP preemption request belongs. The "link ID bitmap field" is merely an exemplary name for a field that carries the link ID of the link to which the TXOP preemption request belongs; the field may also be referred to by other names.

[0117] In some embodiments, the first frame may be an action management frame. For example, the first frame may be a newly defined action management frame. Alternatively, the first frame may be an existing action management frame. For example, the first frame may be an action management frame of the Quality of Service (QoS) category. In other words, the first frame may be implemented using the QoS Management Frame (QMF) mechanism.

[0118] FIG6A is a schematic diagram showing the format of an action management frame in which the first frame provided in an embodiment of the present application is a frame.

[0119] The action management frame shown in FIG6A may include one or more of the following fields: category, action, dialog token, and preemption request element.

[0120] The category field can be used to indicate that the category of the action management frame is the category to which the first frame belongs. The value of the category field can be any value. For example, the value of the category field can be a reserved value (for example, any value between 30 and 125) to indicate that the action management frame is a newly defined category related to TXOP preemption. Alternatively, the value of the category field can be a value corresponding to a defined category to indicate that the action management frame is of a defined category. Exemplarily, the value of the category can be 1 to indicate that the action management frame is of a QoS category.

[0121] The Action field can be combined with the Category field to indicate that the Action frame is the first frame. If the Category field indicates a newly defined category, the Action field can take any value (e.g., 0). If the Category field indicates an already defined category, the Action field can take a reserved value within that category. For example, if the Category field indicates that the frame is of the QoS category, the Action field can take a value between 7 and 255 (e.g., 7).

[0122] The Conversation Token field can be used to match operation responses to operation requests when there are multiple concurrent operation requests. The Conversation Token can be an integer value that helps STAs group management frames sent or received at different times as part of the same conversation. The integer value selected can be implemented by a specific algorithm.

[0123] The preemption request element may be used to request preemption of the TXOP of the first link. The preemption request element may include one or more of the following fields: element ID, length, element ID extension, and preemption request information.

[0124] The preemption request information field may include one or more of the following fields: transmission resource, TID, link identification bitmap, low-latency data flow queue size, scaling factor, and reservation. These fields are described above and will not be repeated here.

[0125] It should be noted that the format of the first frame shown in FIG6A is only an example, and the fields included in the first frame and the positions of the fields may vary.

[0126] In some embodiments, the first frame may be a QoS data frame, a QoS null frame, or a management frame. In this case, the first frame may indicate the preemption of the TXOP through a control field. The control field may be, for example, an A-control field.

[0127] FIG6B is a schematic diagram of the control field format included in the first frame provided in an embodiment of the present application.

[0128] As shown in Figure 6B, the control field can be an HT Control field, of type HE variant. The control field can be 4 bytes long, with the first two bits both set to 1, indicating that the HT Control field is an HE variant. The A-control field can be 30 bits long. The control flag field can use reserved bits in related technologies. For example, the control flag field can have a value of 10 to 14.

[0129] The A-control field may include a preemption information indication field. The preemption information indication field may be 26 bits long. The preemption information indication field may include one or more of the following fields: link identification bitmap, low-latency data flow queue size, and scaling factor. These fields are described above and are not repeated here.

[0130] It should be noted that the format of the control field of the first frame shown in FIG6B is only an example, and the fields included in the control field and the positions of the fields may vary.

[0131] The access priority of the first frame can be set higher, so that TXOP can be initiated more quickly to a certain extent. For example, the AC of the first frame can be set to AC_V0 to obtain the highest access priority.

[0132] In some embodiments, in response to receiving the first frame, the second device may send a first response frame. The first response frame may be used to indicate: a status code, whether the second device permits the first device to perform reverse transmission on the first link, transmission resources of the TXOP that the first device can preempt, and the link to which the TXOP successfully preempted by the first device belongs.

[0133] The transmission resources that the first device can preempt for the TXOP can be used to indicate the duration and / or bandwidth of the TXOP that the second identification allows the first device to preempt. The duration for which the first device is allowed to preempt the TXOP can be carried in the preemption duration field. The preemption duration can range from 1 to 255. The final preemption duration can be multiplied by the unit. Taking the unit as 32us and the preemption duration as an example, which can range from 1 to 255, the time range allowed for preemption is 32us to 8160us. The bandwidth that the first device is allowed to preempt for the TXOP can be carried in the preemption BW field. The preemption continuous bandwidth can range from 1 to 15. Different values ​​can correspond to different bandwidths.

[0134] The status code can be used to indicate whether the first device successfully preempted the TXOP and / or whether the second device allows the first device to preempt the TXOP. Therefore, the first response frame can be a preemption response frame. The preemption response frame can be used to indicate whether the preemption of the TXOP is successful and / or whether the first device is allowed to preempt the TXOP. Both the preemption request frame and the preemption response frame can be referred to as preemption frames.

[0135] In some scenarios (such as Scenario 1 described below), the second device may be the TXOP holder and the first device may be the TXOP responder. Therefore, the direction in which the second device can send a PPDU on the first link can be from the second device to the first device. The first device preempts the TXOP in order to send a data stream to the second device. In this case, as the TXOP holder, the second device can permit the first device to perform reverse transmission on the second link, that is, the TXOP responder sends a PPDU to the TXOP holder. In this scenario, the present application proposes that the second device indicate whether it permits the first device to perform reverse transmission on the first link through a first response frame. If the second device permits the first device to perform reverse transmission on the first link, the transmission direction of the first link can be changed so that the TXOP responder (first device) sends a PPDU or a non-response type frame to the TXOP holder (second device). If the second device does not permit the first device to perform reverse transmission on the first link, the current scenario may not involve reverse transmission, and TXOP preemption needs to be achieved through other means.

[0136] The information on whether the second device permits the first device to perform reverse transmission on the first link can be carried in the reverse direction grant (RDG) field in the first response frame. For example, if the value of the RDG field is 1, the second device permits the first device to perform reverse transmission on the first link; if the value of the RDG field is 0, the second device does not permit the first device to perform reverse transmission on the first link. For another example, if the value of the RDG field is 0, the second device permits the first device to perform reverse transmission on the first link; if the value of the RDG field is 1, the second device does not permit the first device to perform reverse transmission on the first link.

[0137] The link to which the TXOP successfully preempted by the first device belongs can be carried in the link ID field. The link ID can take a value from 0 to 16, indicating the IDs of 16 links respectively.

[0138] The link identification field and the duration field may belong to the preemption link information field. The first response frame may include one or more preemption link information fields to respectively indicate information about the links that the first device successfully preempted. In other words, the number of preemption link information fields may be related to the number of links allowed to be preempted. For example, if there are several links allowed to be preempted, the first response frame may include a corresponding number of link information fields.

[0139] In some embodiments, the first response frame may be an action management frame.

[0140] FIG7 is a schematic diagram of the format of a first response frame provided in an embodiment of the present application.

[0141] The action management frame shown in FIG7 may include one or more of the following fields: category, action, dialog token, and preemption response element.

[0142] The category field can be used to indicate that the category of the action management frame is the category to which the first response frame belongs. The value of the category field can be any value. For example, the value of the category field can be a reserved value (for example, any value between 30 and 125) to indicate that the action management frame is a newly defined category related to TXOP preemption. Alternatively, the value of the category field can be a value corresponding to an existing category to indicate that the action management frame is a defined category. Exemplarily, the value of the category can be 1 to indicate that the action management frame is a QoS category.

[0143] The Action field can be combined with the Category field to indicate that the Action frame is a first response frame. If the Category field indicates a newly defined category, the Action field can take any value (e.g., 0). If the Category field indicates an already defined category, the Action field can take a reserved value within that category. For example, if the Category field indicates that the frame is a QoS category, the Action field can take a value between 7 and 255 (e.g., 8).

[0144] The Conversation Token field can be used to match operation responses to operation requests when there are multiple concurrent operation requests. The Conversation Token can be an integer value that helps STAs group management frames sent or received at different times as part of the same conversation. The integer value selected can be implemented by a specific algorithm.

[0145] The preemption response element may be used to respond to a request to preempt the TXOP of the first link. The preemption response element may include one or more of the following fields: element identifier, length, element identifier extension, RDG field, one or more preemption link information fields, and padding field.

[0146] The preemption link information field may include an identification field of the preempted link, a duration field for allowing preemption under the link, and a bandwidth field for allowing preemption under the link.

[0147] The padding field may be used to supplement the frame length so that the first response frame meets an integer number of bytes.

[0148] It should be noted that the format of the first response frame shown in Figure 7 is only an example. The fields included in the first response frame and the positions of the fields may vary.

[0149] In some embodiments, the second device may send the first information. The first information may be used to indicate information of a data flow that is allowed to preempt the TXOP of the first link.

[0150] It should be noted that, when the second device is an AP, the second device can send the first information.

[0151] It should be noted that the first information may be sent by the second device to one or more devices. The one or more devices may include the first device. For example, if the second device includes an AP, the AP may send the first information to all STAs associated with the AP.

[0152] In some embodiments, the data flow allowed to preempt the TXOP may be a low-latency data flow. In other words, the first information may be used to indicate information about the low-latency data flow. Therefore, based on the first information, the low-latency data flow may be identified.

[0153] In some embodiments, the information about data flows permitted to preempt a TXOP may include TIDs for which TXOP preemption is permitted. That is, the second device may indicate to other devices, through the first information, which TID(s) may preempt the second device's TXOP, or which data flows corresponding to the TID(s) may be low-latency data flows. Data flows permitted to preempt a TXOP may be identified by the second device as low-latency data flows. Data flows not permitted to preempt a TXOP may be identified by the second device as non-low-latency data flows.

[0154] The first device may determine whether to preempt the TXOP of the second device based on the first information. For example, if the data stream to be transmitted by the first device does not belong to a TID that allows preemption of the TXOP, the first device may not send the first frame to the second device, thereby avoiding unnecessary communication resource usage and improving the success rate of TXOP preemption.

[0155] This application does not limit the method for indicating "TIDs allowed to preempt TXOPs". For example, it can be indicated through a bitmap. The value of 1 at position k in the bitmap indicates that TID k is allowed to preempt TXOPs.

[0156] In some embodiments, the information of the data stream that is allowed to preempt the TXOP may include uplink data stream information and / or downlink data stream information. For example, the first information may uniformly indicate the data stream that is allowed to preempt the TXOP of the first link in the uplink and downlink. For another example, the first information may separately indicate the data stream that is allowed to preempt the TXOP of the uplink of the first link and the data stream that is allowed to preempt the TXOP of the downlink of the first link. Exemplarily, the uplink data stream information that is allowed to preempt the TXOP may be carried in the "preemption traffic DL TID bitmap" field; the downlink data stream information that is allowed to preempt the TXOP may be carried in the "preemption traffic UL TID bitmap" field.

[0157] In some embodiments, the first information may be carried in one or more of the following frames: a beacon frame, an association response frame, or a reassociation response frame. The first information may be carried in a preempted data stream information element.

[0158] FIG8 is a schematic diagram of a preemptive data stream information element provided in an embodiment of the present application.

[0159] As shown in Figure 8, the Preemption Data Stream Information Element may include one or more of the following fields: Element Identifier, Length, Element Identifier Extension, Preemption Downstream Data Stream TID Bit Map, Preemption Upstream Data Stream TID Bit Map. For example, the Element Identifier may be 255, and the Element Identifier Extension field may be 98 or other reserved values.

[0160] In some embodiments, the first device may send the first frame to the second device if the TXOP is allowed to be preempted. That is, the first device will request to preempt the TXOP through the second link only if the TXOP of the first link is allowed to be preempted.

[0161] In some embodiments, the second device may send second information. The second information may be used to indicate one or more of the following: whether the TXOP allows preemption, whether the TXOP allows preemption via the first frame, and whether the PPDU sent within the TXOP is fragmented. The TXOP may be the TXOP currently reserved by the second device on the first link.

[0162] Whether the TXOP is allowed to be preempted can indicate: whether the TXOP is allowed to be preempted or whether the TXOP is not allowed to be preempted. If the second information indicates that the TXOP of the first link is allowed to be preempted, the first device has a higher probability of successfully preempting the TXOP, thereby increasing the probability of successful TXOP preemption. If the second information indicates that the TXOP of the first link is not allowed to be preempted, the first device can preempt the TXOP of other links that can be preempted, thereby increasing the probability of successful TXOP preemption.

[0163] In some embodiments, when the data transmitted by the second device in the TXOP does not have a high requirement for latency, and the TID corresponding to the data is not included in the low-latency data stream indicated by the first information, the second device can set the TXOP as a preemptible TXOP for other devices to initiate preemption.

[0164] Whether a TXOP is preemptible can be indicated by a preemption indication field. The preemption indication field can be represented by a single bit. For example, a value of 1 in the preemption indication field indicates that the TXOP is preemptible; a value of 0 in the preemption indication field indicates that the TXOP cannot be preempted. For another example, a value of 0 in the preemption indication field indicates that the TXOP is preemptible; a value of 1 in the preemption indication field indicates that the TXOP cannot be preempted.

[0165] Whether the TXOP can be preempted by the first frame can indicate whether the TXOP can be preempted by the technical solution provided in this application. That is, the second information can be used to indicate whether the TXOP of the first link can be preempted by the multi-link preemption method.

[0166] Optionally, whether the TXOP can be preempted through the first frame can be carried in the preemption type field. The preemption type field can be represented by one bit. For example, a value of 1 in the preemption type field can indicate that the TXOP can be preempted through multi-link preemption. For another example, a value of 0 in the preemption type field can indicate that the TXOP can be preempted through multi-link preemption. For another example, a value of 1 in the preemption type field can indicate that the TXOP can be preempted through a single-link preemption. For another example, a value of 0 in the preemption type field can indicate that the TXOP can be preempted through a single-link preemption. The single-link preemption method can include the preemption method of solution 1 described above.

[0167] In some embodiments, when the TXOP of the first link can be preempted by the first frame, the PPDU sent by the second device within the TXOP may be fragmented. As described above, the second information may be used to indicate whether the PPDU sent by the second device within the TXOP is fragmented.

[0168] Exemplarily, fragmentation may refer to splitting the payload of the PPDU into multiple small payload fragments. For example, a PPDU includes a physical layer header (PHY header) and multiple payload fragments.

[0169] For example, a fragmented PPDU may include multiple end markers. Multiple end markers may be inserted into the payload. In other words, the fragment boundary may be an end marker. In other words, the end marker may separate the fragments. If the TXOP is preempted by the first frame, the fragmented PPDU may stop transmitting at the most recent end marker.

[0170] It is understood that even if the TXOP of the first link is preempted by the first device, through fragmentation, the second device can still transmit part of the payload before the TXOP is preempted, thereby reducing the impact of the TXOP preemption on the signal that the second device needs to transmit. For example, this can reduce the impact on the performance of a high-throughput data stream being transmitted by the second device.

[0171] In some embodiments, the first device may receive the second information before sending the first frame. The first device may send the first frame according to the instruction of the second information. For example, if the second information indicates that the TXOP allows preemption, the first device may send the first frame.

[0172] Exemplarily, the second information may be included in a request to send (RTS) frame. The RTS frame may be the first frame of a TXOP reserved by the second device. The RTS frame may be transmitted on the first link.

[0173] In some embodiments, the second information may be carried in a control field of a frame. The control field may be, for example, an A-control field. FIG9 is a schematic diagram of the format of an A-control field carrying the second information provided in an embodiment of the present application. The control information field in the A-control field may include one or more of the following fields: a preemption indication, a preemption type, and a reserved field. The descriptions of each field are detailed above and are not repeated here.

[0174] As shown in Figure 9, the HT Control field is included in the RTS frame. The HT Control field is of the HE variant type. The HT Control field is 4 bytes long, with the first two bits both set to 1, indicating that the HT Control is of the HE variant type. The A-Control field in the HE variant is 30 bits long and includes a 10-bit preemption control information field. As shown in Figure 9, the Control ID field can use the reserved bits in the related art, with a value of 10. The Control Information field includes the following subfields: The Preemption Indication subfield indicates whether preemption is allowed for the currently scheduled TXOP. A value of 1 indicates that preemption is allowed for the TXOP and that the PPDU is fragmented. The Preemption Type subfield indicates whether preemption is performed over a single link or multiple links. A value of 0 indicates single-link preemption, and a value of 1 indicates multi-link preemption. The Padding field is used to fill the remaining bits to ensure that the HT Control is 4 bytes.

[0175] In some embodiments, the second device may transmit third information. The third information may be used to indicate the duration for which a TXOP is allowed to be preempted. The second device may determine the duration for which a TXOP is allowed to be preempted and transmit the third information to the first device. The second device may determine the duration for which a TXOP is allowed to be preempted based on the data stream to be transmitted by the second device. For example, after subtracting the duration for which a TXOP is allowed to be preempted from the TXOP, the second device may still be able to complete transmission of the data stream to be transmitted. The second device may determine the duration for which a TXOP is allowed to be preempted based on the size of the data stream for which the TXOP is requested to be preempted. For example, within the duration for which a TXOP is allowed to be preempted, the first device may be able to complete transmission of the data stream for which the TXOP is requested to be preempted.

[0176] In some scenarios, the TXOP may belong to the second device, that is, the second device may be the owner of the TXOP. Before the TXOP is preempted, the second device may send data to the first device within the TXOP. In this application, this scenario may be referred to as Scenario 1. Figure 10A is an example diagram of Scenario 1.

[0177] As shown in Figure 10A, AP MLD acts as the preempted party (i.e., the second device), and non-AP MLD1 acts as the preemption initiator (i.e., the first device). The dotted arrow represents the preemption-initiating link (i.e., the second link), and the solid arrow represents the preempted link (i.e., the first link). In Scenario 1 shown in Figure 10A, AP MLD is transmitting data to non-AP MLD1, but non-AP MLD1 needs to initiate preemption, interrupting the transmission and transmitting a low-latency data stream to AP MLD, i.e., performing reverse transmission. In this scenario, AP MLD requires non-AP MLD1 to perform reverse transmission on the first link, enabling non-AP MLD1 to transmit the low-latency data stream to AP MLD.

[0178] It is understandable that the scenario shown in FIG. 10A is merely an example, and scenario 1 may also include a situation where non-AP MLD1 transmits data to AP MLD, and AP MLD preempts the TXOP.

[0179] For scenario 1, in response to the first device successfully preempting the TXOP of the first link, the second device allows the first device to perform reverse transmission. That is, before the first device preempts the TXOP of the first link, the second device can actively transmit signals to the first device; after the first device successfully preempts the TXOP of the first link, the first device can actively transmit signals to the second device, that is, the first device can transmit non-response type frames to the second device.

[0180] Fig. 10B is an example diagram of a communication process for the scenario shown in Fig. 10A. In Fig. 10B, the first link may be "link 1 (link 1)" and the second link may be "link 2 (link 2)".

[0181] FIG. 10B may include steps S1011 - S1017 .

[0182] In step S1011, the AP MLD accesses the link 1 through contention and reserves a TXOP through the RTS / CTS mechanism.

[0183] Step S1012 : AP MLD transmits data on link 1 .

[0184] In step S1012, the AP MLD transmits a fragmented PPDU, which includes a physical header and multiple payloads.

[0185] In step S1012 , the low-latency data flow sent by non-AP MLD1 to AP MLD arrives.

[0186] In step S1013, non-AP MLD1 sends a preemption request frame (indicated by Preq in FIG10B ) to AP MLD on link 2.

[0187] The preemption request frame is used to request to preempt the current TXOP of link 1 to send uplink low-latency data flow.

[0188] In step S1014, the AP MLD responds to the preemption request frame and feeds back a preemption response frame (indicated by Pres in FIG10B ).

[0189] The preemption response frame may indicate whether non-AP MLD1 is allowed to preempt the TXOP of link 1. The preemption response frame may carry an RDG field to indicate whether reverse transmission is permitted.

[0190] In step S1015 , non-AP MLD1 sends a CTS-to-self frame on link 2 to reserve a TXOP.

[0191] Step S1016: After a SIFS interval from the CTS-to-self frame, the non-AP MLD1 starts sending the LL PPDU-2.

[0192] If non-AP MLD1 successfully seizes the TXOP of link 1, the first link may change the transmission direction, and non-AP MLD1 may execute step S1017.

[0193] In step S1017 , non-AP MLD1 sends LL PPDU-1 on link 1 .

[0194] As shown in Figure 10B, non-AP MLD1 can send low-latency data streams on two links, meeting the low-latency requirement and achieving better latency and throughput benefits for high-capacity low-latency services.

[0195] Fig. 10C is another example diagram of a communication process for the scenario shown in Fig. 10A. In Fig. 10C, non-AP MLD1 requests to seize the TXOPs of multiple links.

[0196] In FIG. 10C , the first link may include “link 1 (link1)” and / or “link 2 (link2)”; the second link may include “link 3 (link3)”.

[0197] FIG. 10C may include steps S1021 - S1028 .

[0198] In step S1021, the AP MLD accesses the link 1 through contention and reserves a TXOP through the RTS / CTS mechanism.

[0199] Step S1022 : AP MLD transmits data on link 1 .

[0200] In step S1022, the AP MLD transmits a fragmented PPDU, which includes a physical header and multiple payloads.

[0201] AP MLD also reserves a TXOP on link 2 and transmits fragmented PPDUs on link 2.

[0202] In step S1022 , the low-latency data flow sent by non-AP MLD1 to AP MLD arrives.

[0203] In step S1023, non-AP MLD1 sends a preemption request frame (indicated by Preq in FIG10C ) to AP MLD on link 3.

[0204] The Preemption Request frame is used to request the preemption of the current TXOP of Link 1 and Link 2 to send uplink low-latency data flows. For example, non-AP MLD1 can indicate the link ID to be preempted in the bit position corresponding to the Link ID Bitmap in the Preemption Request frame.

[0205] In step S1024, the AP MLD responds to the preemption request frame and feeds back a preemption response frame (indicated by Pres in FIG10C ).

[0206] The preemption response frame can indicate whether non-AP MLD1 is allowed to preempt the TXOP of link 1 and link 2. The preemption response frame can carry an RDG field to indicate whether reverse transmission is permitted. For example, the preemption response frame can include the ID of the link allowed to be preempted and the duration of the corresponding preemption permission.

[0207] In step S1025 , non-AP MLD1 sends a CTS-to-self frame on link 3 to reserve a TXOP.

[0208] In step S1026 , after a SIFS interval from the CTS-to-self frame, the non-AP MLD1 starts sending the LL PPDU-3.

[0209] If non-AP MLD1 successfully preempts the TXOPs of link 1 and link 2, non-AP MLD1 may transmit in the reverse direction on link 1 and link 2, and non-AP MLD1 may proceed to step S1027. Whether non-AP MLD1 successfully preempts the link and the duration of the preemption allowed on the corresponding link may be determined by the information in the preemption response frame.

[0210] In step S1027 , non-AP MLD1 sends LL PPDU-1 on link 1 .

[0211] If the non-AP MLD1 successfully seizes the TXOP of the link 2, the non-AP MLD1 may transmit in the reverse direction on the link 2, and the non-AP MLD1 may execute step S1028.

[0212] In step S1028 , non-AP MLD1 sends LL PPDU- 2 on link 2 .

[0213] As shown in Figure 10C , non-AP MLD1 can send low-latency data streams on three links, meeting low-latency requirements and achieving better latency and throughput benefits for high-capacity low-latency services.

[0214] In some embodiments, if the first device needs to transmit in the reverse direction on the first link, the first device may instruct the first device to transmit in the reverse direction on the first link through an interaction primitive. For example, the first device may be attached to STA1 of the first link and STA2 of the second link. The station management entity (SME) of STA2 may instruct the MAC sublayer management entity (MLME) of STA2 to send a reverse direction (RD) primitive to the MLME of the attached STA1, instructing the attached STA1 to change the transmission direction of the first link.

[0215] Figure 11 is a schematic diagram of a primitive interaction method provided by an embodiment of the present application. The method shown in Figure 11 may include steps S1110 to S1160.

[0216] Step S1110 , the SME of STA2 sends a reverse request (MLME-REVERSEDIRECTION.request) to the MLME.

[0217] Step S1120 , the MLME of STA2 sends a reverse direction request element (RD request (elements)) to the MLME of STA1 .

[0218] Step S1130 , the MLME of STA1 sends a reverse direction indication (MLME-REVERSEDIRECTION.indication) to the SME of STA1 .

[0219] Step S1140 , the SME of STA1 sends a reverse response (MLME-REVERSEDIRECTION.response) to the MLME of STA1 .

[0220] In step S1150 , the MLME of STA1 sends a reverse element (RD response (elements)) to the MLME of STA2.

[0221] Step S1160 , the MLME of STA2 sends a reverse confirmation (MLME-REVERSEDIRECTION.confirm) to the SME of STA2 .

[0222] In some scenarios, a TXOP may belong to a second device, meaning that the second device may be the owner of the TXOP. Before the TXOP is preempted, the second device can send data to devices other than the second device within the TXOP. After the first device preempts the TXOP, it can send data to devices other than the first device. The following examples illustrate these scenarios using the scenarios shown in Figures 12A and 13A. The scenario shown in Figure 12A can be referred to as Scenario 2, and the scenario shown in Figure 13A can be referred to as Scenario 3.

[0223] In Figure 12A, the first device is non-AP MLD2 and the second device is AP MLD. AP MLD is transmitting data to non-AP MLD1, but non-AP MLD2 needs to initiate TXOP preemption, interrupt the transmission, and transmit a low-latency data stream to AP-MLD.

[0224] In Figure 13A, the first device is AP MLD and the second device is non-AP MLD1. Non-AP MLD1 is transmitting data to AP MLD, but AP MLD wants to preempt the transmission and transmit a low-latency data stream to non-AP MLD2.

[0225] If the TXOP belongs to the second device, in response to the first device successfully preempting the TXOP or allowing the first device to preempt the TXOP, the first device may receive a first trigger frame or a second trigger frame sent by the second device. The first trigger frame may be used to trigger the first device to send data to the second device on the first link. The second trigger frame may be used to share the TXOP with the first device. Both the first trigger frame and the second trigger frame may be transmitted on the first link.

[0226] It should be noted that whether the first device successfully preempts the TXOP can be indicated or determined by whether it sends or receives the first trigger frame or the second trigger frame. For example, if the first device receives the first trigger frame or the second trigger frame, the first device can determine that the first device successfully preempts the TXOP. For another example, if the first device does not receive the first trigger frame or the second trigger frame, the first device can determine that the first device fails to preempt the TXOP.

[0227] Therefore, it can be seen that the first trigger frame or the second trigger frame can also have the function of the first response frame. In other words, the same frame can indicate whether the TXOP preemption is successful and can also trigger the first device to send data on the first link.

[0228] The first trigger frame may be sent by the AP to trigger the non-AP STA to send uplink data on the first link.

[0229] The following is an example of the first trigger frame based on scenario 2 with reference to FIG12B , FIG12C and FIG12D .

[0230] FIG12B is a diagram illustrating an example of a communication process for the scenario shown in FIG12A. In FIG12B, the first link is represented by "link 1" and the second link is represented by "link 2." A first response frame indicates whether the TXOP preemption is successful.

[0231] FIG. 12B may include steps S1211 - S1218 .

[0232] Step S1211 : AP MLD accesses link 1 through contention and reserves a TXOP through the RTS / CTS mechanism.

[0233] Step S1212 : AP MLD transmits data on link 1 .

[0234] In step S1212, the AP MLD transmits a fragmented PPDU, which includes a physical header (PHY header) and multiple payloads.

[0235] In step S1212 , the low-latency data flow sent by non-AP MLD2 to AP MLD arrives.

[0236] In step S1213, non-AP MLD2 sends a preemption request frame (indicated by Preq in FIG12B ) to AP MLD on link 2.

[0237] The preemption request frame is used to request to preempt the current TXOP of link 1 to send uplink low-latency data flow.

[0238] In step S1214, the AP MLD responds to the preemption request frame and feeds back a preemption response frame (indicated by Pres in FIG12B ).

[0239] The preemption response frame may indicate whether non-AP MLD2 is allowed to preempt the TXOP of link 1.

[0240] In step S1215 , non-AP MLD2 sends a CTS-to-self frame on link 2 to reserve a TXOP.

[0241] In step S1216, after a SIFS interval from the CTS-to-self frame, the non-AP MLD2 starts sending the LL PPDU-2.

[0242] If the AP MLD allows the non-AP MLD2 to preempt the TXOP of the link 2, the AP MLD may execute step S1217.

[0243] In step S1217 , the AP MLD sends a first trigger frame (TF) to trigger the non-AP MLD2 to send uplink data to the AP MLD.

[0244] In step S1218 , non-AP MLD2 sends LL PPDU- 1 on link 1 .

[0245] Figure 12C is another example diagram of the communication process for the scenario shown in Figure 12A. In Figure 12C, the first link is represented by "link 1" and the second link is represented by "link 2." The first trigger frame indicates whether the TXOP preemption is successful.

[0246] FIG. 12C may include steps S1221 - S1228 .

[0247] In step S1221, the AP MLD accesses the link 1 through contention and reserves a TXOP through the RTS / CTS mechanism.

[0248] Step S1222 : AP MLD transmits data on link 1 .

[0249] In step S1222, the AP MLD transmits a fragmented PPDU, which includes a physical header (PHY header) and multiple payloads.

[0250] During step S1222 , the low-latency data flow sent by non-AP MLD2 to AP MLD arrives.

[0251] In step S1223, non-AP MLD2 sends a preemption request frame to AP MLD on link 2 (indicated by "indication" in FIG12C).

[0252] The preemption request frame is used to request to preempt the current TXOP of link 1 to send uplink low-latency data flow.

[0253] In step S1224, non-AP MLD2 sends a CTS-to-self frame on link 2 to reserve a TXOP.

[0254] In step S1225 , after a SIFS interval from the CTS-to-self frame, the non-AP MLD2 starts sending the LL PPDU-2.

[0255] If the AP MLD allows the non-AP MLD2 to preempt the TXOP of the link 2, the AP MLD may execute step S1226.

[0256] In step S1226 , the AP MLD sends a first trigger frame (TF) to indicate that the TXOP preemption is successful and trigger the non-AP MLD2 to send uplink data to the AP MLD.

[0257] In step S1227 , non-AP MLD2 sends LL PPDU- 1 on link 1 .

[0258] Figure 12D is another example diagram of the communication process for the scenario shown in Figure 12A. In Figure 12D, the first link is represented by "link 1"; the second link is represented by "link 2." The first frame can be a QoS data frame, a QoS null frame, or a management frame. The first frame can indicate a preemption request using the HT Control field in the first frame.

[0259] FIG12D may include steps S1231 - S1235 .

[0260] In step S1231, the AP MLD accesses the link 1 through contention and reserves a TXOP through the RTS / CTS mechanism.

[0261] Step S1232 : AP MLD transmits data on link 1 .

[0262] In step S1232, the AP MLD transmits a fragmented PPDU, which includes a physical header (PHY header) and multiple payloads.

[0263] During step S1232 , the low-latency data flow sent by non-AP MLD2 to AP MLD arrives.

[0264] In step S1233, non-AP MLD2 sends a QoS data frame (ie, PPDU-1 in FIG12D ) to AP MLD on link 2.

[0265] The QoS data frame is used to request to seize the current TXOP of link 1 to send the uplink low-latency data flow. That is, the QoS data frame is the first frame.

[0266] In step S1234 , the AP MLD sends a first trigger frame (TF) to indicate that the TXOP preemption is successful and trigger the non-AP MLD2 to send uplink data to the AP MLD.

[0267] In step S1235 , non-AP MLD2 sends LL PPDU- 2 on link 1 .

[0268] As shown in Figures 12B, 12C, and 12D, non-AP MLD2 can send low-latency data streams on two links, meeting low-latency requirements and achieving better latency and throughput benefits for high-capacity low-latency services.

[0269] The second trigger frame may be a TXOP sharing (TXS) trigger frame. For example, the second trigger frame may be a MU-RTS TXS frame. Based on the second trigger frame, a mechanism for one device to share a TXOP with another device, i.e., a trigger-based TXOP sharing process, may be implemented.

[0270] If the Triggered TXOP Sharing Mode subfield in the Common Information field of a MU-RTS frame sent by an AP is set to a non-zero value, it indicates that the TXOP is allocated to the associated non-AP MLD for transmitting one or more non-TB PPDUs. Figure 13B uses AP shared TXOP as an example. As shown in Figure 13B, when the Triggered TXOP Sharing Mode subfield value is 2, the MU-RTS TXS Trigger frame sent by the AP indicates that a portion of its TXOP time is allocated to non-AP STA1. Non-AP STA1 responds with a CTS frame to the AP and begins transmitting non-TB PPDUs to the AP or non-AP STA2.

[0271] In the related art, only the AP can share its TXOP with the STA through the above-mentioned shared TXOP mechanism. Non-AP STA can only use its TXOP for its own uplink transmission and cannot share the downlink and uplink of other STAs, resulting in the inability to send low-latency sensitive data streams in a timely manner. To address this problem, the present application proposes to enable non-AP STAs to have the ability to trigger TXOP sharing, namely, a reverse TXOP sharing mechanism. The above-mentioned reverse TXOP sharing mechanism can effectively improve the efficient utilization of bandwidth and achieve low-latency performance. In addition, this solution makes very little change to the relevant standards and can expand the TXS mode in the relevant standards (such as the value of the TXOP sharing mode subfield).

[0272] Table 1 shows examples of the meanings of the Triggered TXOP Sharing Mode subfield values. A value of 1 in the Triggered TXOP Sharing Mode subfield indicates that the AP shares its TXOP with associated STAs, and STAs can only transmit MPDUs to the AP. A value of 2 in the Triggered TXOP Sharing Mode subfield indicates that the AP shares its TXOP with STAs, and STAs can transmit MPDUs to the associated AP or other peer STAs.

[0273] Table 1

[0274] The present application proposes to further expand the triggered TXOP sharing mode and add a reverse TXOP sharing mode, so that the STA can reversely share its TXOP with the associated AP. The reserved bit in the triggered TXOP sharing mode subfield can be used to indicate the reverse TXOP sharing mode. For example, 3 in the triggered TXOP sharing mode subfield can be defined as: the STA uses the MU-RTS TXS frame to start the triggered TXOP sharing process, shares the TXOP with the associated AP, so that the AP can transmit the MPDU to any associated STA. For another example, 3 in the triggered TXOP sharing mode subfield can be defined as: the STA uses the MU-RTS TXS frame to start the triggered TXOP sharing process, shares the TXOP with other STAs, so that the STA can transmit the MPDU to another STA. Through the extension of the mode, during the TXOP preemption process, the non-AP STA can share its TXOP with the AP or other STA that initiated the preemption.

[0275] The second trigger frame is described below with reference to FIG13C based on Scenario 3. FIG13C is a schematic diagram of a transmission process for Scenario 3 provided in an embodiment of the present application.

[0276] Figure 13C is an example diagram of a communication process for the scenario shown in Figure 13 A. In Figure 13C, the first link is represented by "link 1 (link 1)" and the second link is represented by "link 2 (link 2)".

[0277] FIG. 13C may include steps S1311 - S1319 .

[0278] In step S1311, non-AP MLD1 accesses link 1 through contention and reserves a TXOP through the RTS / CTS mechanism.

[0279] In step S1312 , non-AP MLD1 transmits data on link 1 .

[0280] In step S1312, non-AP MLD1 transmits a fragmented PPDU, which includes a physical header (PHY header) and multiple payloads.

[0281] In step S1312 , the low-latency data flow sent by AP MLD to non-AP MLD2 arrives.

[0282] In step S1313, the AP MLD sends a preemption request frame (indicated by Preq in FIG13C ) to the non-AP MLD1 on link 2.

[0283] The preemption request frame is used to request to preempt the current TXOP of link 1 to send downlink low-latency data flow.

[0284] In step S1314, non-AP MLD1 responds to the preemption request frame and feeds back a preemption response frame (indicated by Pres in FIG13C ).

[0285] The preemption response frame may indicate whether the AP MLD is allowed to preempt the TXOP of link 1.

[0286] In step S1315 , the AP MLD sends a CTS-to-self frame on link 2 to reserve a TXOP.

[0287] Step S1316: After a SIFS interval from the CTS-to-self frame, the AP MLD starts sending the LL PPDU-2.

[0288] If non-AP MLD1 allows AP MLD to preempt the TXOP of link 2, non-AP MLD1 may execute step S1317.

[0289] In step S1317, non-AP MLD1 sends a second trigger frame, which may be a MU-RTS TXS frame (denoted by TXS in FIG13C ), to share the TXOP of non-AP MLD1 with AP MLD.

[0290] Step S1318: AP MLD sends a CTS frame in response to TXOP sharing.

[0291] In step S1319 , the AP MLD sends LL PPDU- 1 on link 1 .

[0292] As shown in Figure 13C, AP MLD can send low-latency data streams on two links, meeting low-latency requirements and achieving better latency and throughput benefits for high-capacity low-latency services.

[0293] In some scenarios, a TXOP may belong to a third device. That is, the third device may be the owner of the TXOP. The third device may be a different device from the first or second device. Before the TXOP is preempted, the third device can send data within the TXOP to devices other than the third device. The first device can communicate with the second device but cannot communicate with the third device. For ease of description, this scenario is referred to as Scenario 4 below. Scenario 4 is illustrated below using Figure 14A.

[0294] In Figure 14A, the first device is non-AP MLD2. The second device is AP MLD. The third device is non-AP MLD1. As shown in Figure 14A, non-AP MLD1 is transmitting data to AP MLD, but non-AP MLD2 needs to initiate preemption, interrupting the transmission and transmitting a low-latency data stream to AP MLD. Because non-AP STAs cannot communicate directly in most cases, the AP assists in transmitting preemption information.

[0295] In this scenario, non-AP MLD1 needs to share its TXOP with non-AP MLD2 through AP MLD, so that non-AP MLD2 can transmit low-latency data flows to AP MLD.

[0296] In scenario 4, the first frame can be used to trigger the second device to send the second frame to the third device. The second frame can be used by the second device to preempt the TXOP. It is understood that the second frame in scenario 4 can be similar to the first frame in scenarios 1-3, which is a preemption request frame, both used to request the peer end to preempt TXOP sharing. Therefore, the description of the first frame above can also be applied to the second frame.

[0297] In some embodiments, in response to the second device successfully seizing the TXOP of the first link, the first device receives the first trigger frame or the second trigger frame sent by the second device. The meanings of the first trigger frame and the second trigger frame are consistent with those described above and are not repeated here.

[0298] Taking the scenario shown in Figure 14A as an example, non-AP MLD2 can apply to preempt the TXOP of non-AP MLD through AP MLD. After AP MLD successfully preempts the TXOP, it can share the TXOP with non-AP MLD2 or trigger non-AP MLD2 to perform uplink transmission.

[0299] The following is an example of the first trigger frame based on scenario 4 and in conjunction with Figure 14B. Figure 14B is a schematic diagram of a transmission process for scenario 4 provided by an embodiment of the present application.

[0300] Figure 14B is an example diagram of a communication process for the scenario shown in Figure 14A. In Figure 14B, the first link is represented by "link 1 (link 1)" and the second link is represented by "link 2 (link 2)".

[0301] FIG. 14B may include steps S1411 - S1423 .

[0302] In step S1411, non-AP MLD1 accesses link 1 through contention and reserves a TXOP through the RTS / CTS mechanism.

[0303] In step S1412 , non-AP MLD1 transmits data on link 1 .

[0304] In step S1412, non-AP MLD1 transmits a fragmented PPDU, which includes a physical header (PHY header) and multiple payloads.

[0305] The low-latency data flow sent by non-AP MLD2 to AP MLD arrives.

[0306] Since there is no P2P communication between non-AP MLD1 and non-AP MLD2, non-AP MLD2 cannot directly initiate a preemption request to non-AP MLD1.

[0307] In step S1413, non-AP MLD2 sends a preemption request frame (indicated by Preq in FIG14B ) to AP MLD on link 2.

[0308] The preemption request frame is used to request to preempt the current TXOP of link 1 to send uplink low-latency data flow.

[0309] In step S1414 , the AP MLD sends a preemption request frame to the non-AP MLD1 on link 2 .

[0310] In step S1415, non-AP MLD1 responds to the preemption request frame in step S1414 by feeding back a preemption response frame to AP MLD (indicated by Pres in FIG14B).

[0311] The preemption response frame may indicate whether the AP MLD is allowed to preempt the TXOP of link 1.

[0312] In step S1416 , the AP MLD responds to the preemption request frame in step S1413 by feeding back a preemption response frame to the non-AP MLD2 .

[0313] In step S1417, non-AP MLD2 sends a CTS-to-self frame on link 2 to reserve a TXOP.

[0314] In step S1418, after a SIFS interval from the CTS-to-self frame, the non-AP MLD starts sending LL PPDU-2.

[0315] If the non-AP MLD1 allows other devices to preempt the TXOP of the link 2 , the non-AP MLD1 may execute step S1419 .

[0316] In step S1419 , non-AP MLD1 sends a second trigger frame, which may be a MU-RTS TXS frame, to share the TXOP of non-AP MLD1 with AP MLD.

[0317] Step S1420 , the AP MLD sends a CTS frame in response to TXOP sharing.

[0318] In step S1421 , the AP MLD sends a second trigger frame, which may be a MU-RTS TXS frame, to share the TXOP seized by the AP MLD with the non-AP MLD2 .

[0319] Step S1422 , non-AP MLD2 sends a CTS frame in response to TXOP sharing.

[0320] In step S1423 , non-AP MLD2 sends LL PPDU-1 on link 1 .

[0321] As shown in Figure 14B, by triggering the TXOP sharing mechanism twice, non-AP MLD1's TXOP is first shared with AP MLD, and then shared with non-AP MLD2. Therefore, non-AP MLD2 can send low-latency data streams on both links, meeting low-latency requirements and achieving better latency and throughput benefits for high-capacity, low-latency services.

[0322] In scenario 4, where a second device is required to assist in forwarding the preemption request, the frame exchange overhead is higher than that of direct requests in scenarios 1 to 3. For example, in the preemption scenario between STAs, STAs cannot communicate directly and require the AP to assist in forwarding preemption-related information. In this case, the frame exchange overhead is higher than that of the preemption scenario between APs and STAs.

[0323] A quantitative analysis of the time consumption of the frame interaction process in scenario 4 is conducted. The following analysis is conducted using the scenario shown in FIG14A as an example. It should be noted that the following frame interaction time consumption analysis is also applicable to scenarios other than the scenario shown in FIG14A.

[0324] Assume that all control management frames use 40Mhz bandwidth and the minimum MCS rate is 17.2Mbps (NSS=2, protection interval 0.8ns). Assume that the access category (AC) of the data frame being transmitted by non-AP MLD1 is AC_BE, and the TXOP limit is 3.264ms. The PPDU limit is 5.484ms. Assume that the length of the currently transmitted PPDU is 2.5ms, and the AC of the LL PPDU is AC_VO, and the transmission time is 1ms. The frame spacing of each control frame is SIFS and the length is 16us. Based on the above assumed transmission rate, the CTS frame length is 14 bytes, and the transmission time is: The preemption frame designed in this application includes a preemption request frame and a preemption response frame, wherein the preemption request frame is 42 bytes long, and the preemption response frame length is 42 bytes, taking the preemption of two links as an example. The transmission times are The frame length of the MU RTS TXS trigger frame is about 29 bytes, and the transmission time is Finally, the total transmission time of the preemption process in the scenario of Figure 14A is: (T Pres +T Prsp +T CTS +T TXS )*2+T SIFS *7=229.8μs.

[0325] As can be seen, in scenario 4, the preemption frame exchange overhead between STAs is at the microsecond level, which is not on the same order of magnitude as the millisecond-level transmission time of PPDU and LL PPDU. The actual transmission latency is very small compared to the data transmission time and is basically negligible, indicating that preemption in this scenario has low-latency performance benefits.

[0326] In some embodiments, after the first device completes its preemption of the TXOP, the TXOP owner can continue to transmit signals within the TXOP. It is understood that the technical solutions proposed in this application for reverse transmission, the first trigger frame, and the second trigger frame implementation do not require changing the TXOP owner. Therefore, the TXOP owner can continue to transmit.

[0327] The following describes the scenario 2 as shown in FIG. 15 and FIG. 12A as an example.

[0328] In Figure 15, when a low-latency service preempts and is forced to interrupt data transmission, the preempted device can choose to control the TXOP duration allowed for preemption so that after the preemption ends, there is enough TXOP time left to continue transmitting the original data.

[0329] As shown in FIG. 15 , the steps shown in FIG. 12B may further include S1219 .

[0330] In step S1219 , if the AP MLD needs to continue transmitting the original data and the remaining TXOP time is sufficient to transmit part or all of the data, the AP MLD can resume transmitting the original data on link 1 after the preemption ends.

[0331] After the TXOP preemption ends, the TXOP owner can continue to transmit without having to compete for access again, thus avoiding the impact of contention on data transmission latency. This allows for low-latency data flows while minimizing the performance impact on high-throughput data flows.

[0332] In some embodiments, after the first device finishes preempting the TXOP, the owner of the TXOP may end the current TXOP, ie, not continue transmission.

[0333] It should be noted that the names of the fields in this application are only examples. These fields may have other names, and this application does not limit this. The method embodiments of the present application are described in detail above, and the device embodiments of the present application are described in detail below. It should be understood that the description of the method embodiments corresponds to the description of the device embodiments. Therefore, for portions not described in detail, reference can be made to the above method embodiments.

[0334] FIG16 is a schematic structural diagram of a communication device 1600 provided in an embodiment of the present application. The communication device 1600 may be a first device and may include a sending unit 1610.

[0335] The sending unit 1610 is used to send a first frame to the second device; wherein a first link and a second link are established between the first device and the second device, the first frame is used to seize part or all of the transmission resources in the TXOP of the first link, and the first frame satisfies one or more of the following: the first frame is transmitted through the second link; when the first moment is earlier than the second moment, the first frame is transmitted through the first link, the first moment is the moment when the first device obtains the transmission resources for transmitting the first frame on the first link, and the second moment is the moment when the first device obtains the transmission resources for transmitting the first frame on the second link.

[0336] In an optional embodiment, the sending unit 1610 may be a transceiver 1830. The communication device 1600 may further include a processor 1810 and a memory 1820, as specifically shown in FIG18 .

[0337] FIG17 is a schematic structural diagram of a communication device 1700 provided in an embodiment of the present application. The communication device 1700 may be a second device and may include a receiving unit 1710.

[0338] The receiving unit 1710 is used to receive a first frame sent by a first device; wherein a first link and a second link are established between the first device and the second device, the first frame is used to seize part or all of the transmission resources in the TXOP of the first link, and the first frame satisfies one or more of the following: the first frame is transmitted through the second link; when the first moment is earlier than the second moment, the first frame is transmitted through the first link, the first moment is the moment when the first device obtains the transmission resources for transmitting the first frame on the first link, and the second moment is the moment when the first device obtains the transmission resources for transmitting the first frame on the second link.

[0339] In an optional embodiment, the receiving unit 1710 may be a transceiver 1830. The communication device 1700 may further include a processor 1810 and a memory 1820, as specifically shown in FIG18 .

[0340] Figure 18 is a schematic block diagram of a communication device according to an embodiment of the present application. The dashed lines in Figure 18 indicate that the unit or module is optional. Device 1800 can be used to implement the method described in the above method embodiment. Device 1800 can be a chip or a communication device.

[0341] The device 1800 may include one or more processors 1810. The processor 1810 may support the device 1800 to implement the method described in the method embodiment above. The processor 1810 may be a general-purpose processor or a special-purpose processor. For example, the processor may be a central processing unit (CPU). Alternatively, the processor may be another general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, etc. The general-purpose processor may be a microprocessor or the processor may be any conventional processor, etc.

[0342] The apparatus 1800 may further include one or more memories 1820. The memories 1820 store programs that can be executed by the processor 1810, causing the processor 1810 to perform the methods described in the above method embodiments. The memories 1820 may be independent of the processor 1810 or integrated into the processor 1810.

[0343] The apparatus 1800 may further include a transceiver 1830. The processor 1810 may communicate with other devices or chips via the transceiver 1830. For example, the processor 1810 may transmit and receive data with other devices or chips via the transceiver 1830.

[0344] The present invention also provides a computer-readable storage medium for storing a program. The computer-readable storage medium can be applied to the communication device provided in the present invention, and the program enables a computer to execute the method performed by the communication device in each embodiment of the present invention.

[0345] The present application also provides a computer program product. The computer program product includes a program. The computer program product can be applied to the communication device provided in the present application, and the program causes a computer to execute the method performed by the communication device in each embodiment of the present application.

[0346] The embodiments of the present application also provide a computer program. The computer program can be applied to the communication device provided in the embodiments of the present application, and the computer program enables a computer to execute the method executed by the communication device in each embodiment of the present application.

[0347] It should be understood that the terms "system" and "network" in this application can be used interchangeably. In addition, the terms used in this application are only used to explain the specific embodiments of this application and are not intended to limit this application. The terms "first", "second", "third", and "fourth" in the specification and claims of this application and the accompanying drawings are used to distinguish different objects rather than to describe a specific order. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions.

[0348] In the embodiments of the present application, a "field" may also be referred to as a "field," a "subfield," or a "subfield." A field may occupy one or more bytes (byte / octet), or a field may occupy one or more bits (bit).

[0349] In the embodiments of this application, the term "indication" may refer to a direct indication, an indirect indication, or an indication of an association. For example, "A indicates B" may refer to a direct indication of B, e.g., B can obtain information through A; it may refer to an indirect indication of B, e.g., A indicates C, e.g., B can obtain information through C; or it may refer to an association between A and B.

[0350] In the embodiment of the present application, "B corresponding to A" means that B is associated with A and B can be determined based on A. However, it should be understood that determining B based on A does not mean determining B based solely on A, but B can also be determined based on A and / or other information.

[0351] In the embodiments of the present application, the term "corresponding" may indicate a direct or indirect correspondence between the two, or an association relationship between the two, or a relationship between indication and indication, configuration and configuration, etc.

[0352] In the embodiments of the present application, "pre-defined" or "pre-configured" may be implemented by pre-storing corresponding codes, tables, or other methods that can be used to indicate relevant information in devices (e.g., including APs and STAs). The present application does not limit the specific implementation method. For example, pre-defined may refer to information defined in a protocol.

[0353] In the embodiments of this application, the term "and / or" is simply a description of the association relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this document generally indicates that the related objects are in an "or" relationship.

[0354] In the embodiments of this application, the term "include" can refer to direct inclusion or indirect inclusion. Alternatively, the term "include" in the embodiments of this application can be replaced with "indicates" or "is used to determine." For example, "A includes B" can be replaced with "A indicates B" or "A is used to determine B."

[0355] In various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0356] In the embodiments of the present application, the “protocol” may refer to a standard protocol in the communication field, for example, it may include a WiFi protocol and related protocols used in future WiFi communication systems, and the present application does not limit this.

[0357] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0358] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0359] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0360] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from one website, computer, server or data center to another website, computer, server or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium can be any available medium that can be read by a computer or a data storage device such as a server or data center that includes one or more available media integrated therein. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a digital versatile disc (DVD)), or a semiconductor medium (eg, a solid state disk (SSD)).

[0361] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

Claims

1. A method for wireless communication, characterized in that, comprising: A first device sends a first frame to a second device; Wherein, a first link and a second link are established between the first device and the second device, and the first frame is used to indicate preempting some or all of the transmission resources in a transmission opportunity TXOP of the first link, and the first frame satisfies one or more of the following: the first frame is transmitted through the second link; In the case where a first moment is earlier than a second moment, the first frame is transmitted through the first link, the first moment is the moment when the first device obtains transmission resources for transmitting the first frame on the first link, and the second moment is the moment when the first device obtains transmission resources for transmitting the first frame on the second link.

2. The method according to claim 1, characterized in that, The first frame is used to indicate one or more of the following information: Information requesting to preempt some or all of the transmission resources of the TXOP; Information requesting to preempt the link to which the TXOP belongs; Information of the data stream to be transmitted.

3. The method according to claim 2, characterized in that, The information of preempting some or all of the transmission resources of the TXOP includes one or more of the following: some or all of the duration of the TXOP; some or all of the bandwidth of the TXOP.

4. The method according to claim 2 or 3, characterized in that, The information of the data stream to be transmitted includes one or more of the following information of the data stream: flow identifier TID, data stream queue size, scale factor of the data stream queue size.

5. The method according to any one of claims 1-4, characterized in that, The first frame is an action management frame, a quality of service QoS data frame carrying a control field, a QoS null frame carrying a control field, or a management frame carrying a control field.

6. The method according to any one of claims 1-5, characterized in that, further comprising: The first device receives first information sent by the second device; Wherein, the first information is used to indicate information of the data stream allowed to preempt the TXOP.

7. The method according to claim 6, characterized in that, The information of the data stream allowed to preempt the TXOP includes the type of the data stream allowed to preempt the TXOP.

8. The method according to claim 6 or 7, characterized in that, The first information is carried in one or more of the following frames: beacon frame, association response frame, re-association response frame.

9. The method according to any one of claims 6-8, characterized in that, The information of the data stream allowed to preempt the TXOP includes: information of the uplink data stream allowed to preempt the TXOP and / or information of the downlink data stream allowed to preempt the TXOP.

10. The method according to any one of claims 1-9, characterized in that, The first device sending the first frame to the second device includes: In the case where the TXOP is allowed to be preempted, the first device sends the first frame to the second device.

11. The method according to any one of claims 1 - 10, characterized in that, further comprising: the first device receives second information sent by the second device; wherein the second information is used to indicate one or more of the following: whether the TXOP is allowed to be preempted; whether the TXOP is allowed to be preempted by the first frame; whether the physical layer protocol data unit (PPDU) sent within the TXOP is fragmented.

12. The method according to claim 11, characterized in that, the second information is transmitted through the first link.

13. The method according to claim 11 or 12, characterized in that, the second information is carried in the control field of a frame.

14. The method according to any one of claims 11 - 13, characterized in that, the second information is included in the RTS frame.

15. The method according to any one of claims 1 - 14, characterized in that, in the case where the TXOP is allowed to be preempted by the first frame, the PPDU sent by the first device within the TXOP is fragmented.

16. The method according to claim 15, characterized in that, the fragmented PPDU includes a plurality of end markers, and in the case where the TXOP is preempted by the first frame, the fragmented PPDU stops transmitting at the nearest end marker.

17. The method according to any one of claims 1 - 16, characterized in that, further comprising: the first device receives third information sent by the second device; wherein the third information is used to indicate the duration for which the TXOP is allowed to be preempted.

18. The method according to any one of claims 1 - 17, characterized in that, further comprising: the first device receives a first response frame sent by the second device; wherein the first response frame is used to indicate whether the first device has successfully preempted the TXOP.

19. The method according to claim 18, characterized in that, the first response frame is used to indicate one or more of the following information: a status code, used to indicate whether the first device has successfully preempted the TXOP, and / or whether the second device allows the first device to preempt the TXOP; whether the second device permits the first device to perform reverse transmission on the first link; the transmission resources of the TXOP that the first device can preempt; the link to which the TXOP successfully preempted by the first device belongs.

20. The method according to claim 19, characterized in that, the first response frame is an action management frame.

21. The method according to any one of claims 1 - 20, characterized in that, the first link belongs to a plurality of links, and the first frame is used to preempt the transmission resources of the TXOP of the plurality of links.

22. The method according to any one of claims 1 - 21, characterized in that, the TXOP belongs to the second device, and the TXOP is used for the second device to send data to the first device. The method further comprises: In response to the first device successfully pre - empting the TXOP of the first link or being allowed to pre - empt the TXOP, the first device performs a reverse transmission on the first link according to the permission of the second device.

23. The method according to claim 22, wherein, the first device indicates, through an interaction primitive, that the first device performs a reverse transmission on the first link.

24. The method according to any one of claims 1 - 23, wherein, the TXOP belongs to the second device, and the method further includes: in response to the first device successfully pre - empting the TXOP or being allowed to pre - empt the TXOP, the first device receives a first trigger frame or a second trigger frame sent by the second device; wherein, both the first trigger frame and the second trigger frame are transmitted on the first link, the first trigger frame is used to trigger the first device to send data to the second device on the first link, and the second trigger frame is used to share the TXOP with the first device.

25. The method according to any one of claims 1 - 21, wherein, the TXOP belongs to a third device, the first frame is used to trigger the second device to send a second frame to the third device, and the second frame is used for the second device to pre - empt the TXOP.

26. The method according to claim 25, wherein, the method further includes: in response to the second device successfully pre - empting the TXOP of the first link, the first device receives a first trigger frame or a second trigger frame sent by the second device; wherein, both the first trigger frame and the second trigger frame are transmitted on the first link, the first trigger frame is used to trigger the first device to send data to the second device on the first link, and the second trigger frame is used to share the TXOP with the first device.

27. The method according to any one of claims 1 - 26, wherein, both the first device and the second device are multi - link devices.

28. The method according to any one of claims 1 - 27, wherein, the data stream requesting to pre - empt the TXOP includes a delay - sensitive data stream.

29. The method according to any one of claims 1 - 28, wherein, further includes: the first device performs channel access on the second link; wherein, the channel access process is implemented through first enhanced distributed channel access (EDCA) parameters, and the first EDCA parameters are less than or equal to a first threshold.

30. The method according to any one of claims 1 - 29, wherein, further includes: the first device determines whether to send the first frame to the second device according to the remaining duration of the TXOP; wherein, the remaining duration of the TXOP is determined by the network allocation vector (NAV) of the second device on the first link.

31. A method for wireless communication, wherein, includes: a second device receives a first frame sent by a first device; Among them, a first link and a second link are established between the first device and the second device. The first frame is used to indicate seizing some or all of the transmission resources in the transmission opportunity TXOP of the first link, and the first frame satisfies one or more of the following: the first frame is transmitted through the second link; In the case where a first moment is earlier than a second moment, the first frame is transmitted through the first link, the first moment is the moment when the first device obtains the transmission resources for transmitting the first frame on the first link, and the second moment is the moment when the first device obtains the transmission resources for transmitting the first frame on the second link.

32. The method according to claim 31, characterized in that, the first frame is used to indicate one or more of the following information: information requesting to seize some or all of the transmission resources of the TXOP; information requesting to seize the link to which the TXOP belongs; information of the data stream to be transmitted.

33. The method according to claim 32, characterized in that, the information of seizing some or all of the transmission resources of the TXOP includes one or more of the following: some or all of the duration of the TXOP; some or all of the bandwidth of the TXOP.

34. The method according to claim 32 or 33, characterized in that, the information of the data stream to be transmitted includes one or more of the following information of the data stream: flow identifier TID, data stream queue size, scale factor of the data stream queue size.

35. The method according to any one of claims 31-34, characterized in that, the first frame is an action management frame, a quality of service QoS data frame carrying a control field, a QoS null frame carrying a control field or a management frame carrying a control field.

36. The method according to any one of claims 31-35, characterized in that, further comprising: the second device sends first information to the first device; wherein, the first information is used to indicate the information of the data stream allowed to seize the TXOP.

37. The method according to claim 36, characterized in that, the information of the data stream allowed to seize the TXOP includes the type of the data stream allowed to seize the TXOP.

38. The method according to claim 36 or 37, characterized in that, the first information is carried in one or more of the following frames: beacon frame, association response frame, re-association response frame.

39. The method according to any one of claims 36-38, characterized in that, the information of the data stream allowed to seize the TXOP includes: information of the uplink data stream allowed to seize the TXOP and / or information of the downlink data stream allowed to seize the TXOP.

40. The method according to any one of claims 31-39, characterized in that, the second device receiving the first frame sent by the first device includes: in the case where the TXOP is allowed to be seized, the second device receives the first frame sent by the first device.

41. The method according to any one of claims 31-40, characterized in that, Further included are: The second device sends second information to the first device; Wherein, the second information is used to indicate one or more of the following: Whether the TXOP is allowed to be preempted; Whether the TXOP is allowed to be preempted by the first frame; Whether the physical layer protocol data unit (PPDU) sent within the TXOP is fragmented.

42. The method according to claim 41, characterized in that The second information is transmitted through the first link.

43. The method according to claim 41 or 42, characterized in that The second information is carried in the control field of the frame.

44. The method according to any one of claims 41-43, characterized in that The second information is included in the RTS frame.

45. The method according to any one of claims 31-44, characterized in that In the case where the TXOP is allowed to be preempted by the first frame, the PPDU sent by the first device within the TXOP is fragmented.

46. The method according to claim 45, characterized in that The fragmented PPDU includes a plurality of end markers. In the case where the TXOP is preempted by the first frame, the fragmented PPDU stops transmitting at the nearest end marker.

47. The method according to any one of claims 31-46, characterized in that Further included are: The second device sends third information to the first device; Wherein, the third information is used to indicate the duration for which the TXOP is allowed to be preempted.

48. The method according to any one of claims 31-47, characterized in that Further included are: The second device sends a first response frame to the first device; Wherein, the first response frame is used to indicate whether the first device successfully preempts the TXOP.

49. The method according to claim 48, characterized in that The first response frame is used to indicate one or more of the following information: A status code, used to indicate whether the first device successfully preempts the TXOP, and / or whether the second device allows the first device to preempt the TXOP; Whether the second device permits the first device to perform reverse transmission on the first link; The transmission resources of the TXOP that the first device can preempt; The link to which the TXOP successfully preempted by the first device belongs.

50. The method according to claim 49, characterized in that The first response frame is an action management frame.

51. The method according to any one of claims 31-50, characterized in that The first link belongs to a plurality of links, and the first frame is used to preempt the transmission resources of the TXOP of the plurality of links.

52. The method according to any one of claims 31-51, characterized in that The TXOP belongs to the second device, and the TXOP is used for the second device to send data to the first device. The method further includes: In response to the first device successfully preempting the TXOP of the first link, the second device permits the first device to perform reverse transmission on the first link.

53. The method according to claim 52, It is characterized in that the first device indicates, through an interaction primitive, that the first device performs reverse transmission on the first link.

54. The method according to any one of claims 31-53, It is characterized in that the TXOP belongs to the second device, and the method further includes: in response to the first device successfully preempting the TXOP or being allowed to preempt the TXOP by the first device, the second device sends a first trigger frame or a second trigger frame to the first device; wherein, both the first trigger frame and the second trigger frame are transmitted on the first link, the first trigger frame is used to trigger the first device to send data to the second device on the first link, and the second trigger frame is used to share the TXOP with the first device.

55. The method according to any one of claims 31-51, It is characterized in that the TXOP belongs to a third device, the first frame is used to trigger the second device to send a second frame to the third device, and the second frame is used for the second device to preempt the TXOP.

56. The method according to claim 55, It is characterized in that the method further includes: in response to the second device successfully preempting the TXOP of the first link, the second device sends a first trigger frame or a second trigger frame to the first device; wherein, both the first trigger frame and the second trigger frame are transmitted on the first link, the first trigger frame is used to trigger the first device to send data to the second device on the first link, and the second trigger frame is used to share the TXOP with the first device.

57. The method according to any one of claims 31-56, It is characterized in that both the first device and the second device are multi-link devices.

58. The method according to any one of claims 31-57, It is characterized in that the data stream requesting to preempt the TXOP includes a delay-sensitive data stream.

59. The method according to any one of claims 31-58, It is characterized in that further includes: after the first device finishes preempting the TXOP, the second device continues to transmit signals within the TXOP.

60. A communication device, It is characterized in that the communication device is a first device, and the communication device includes: a sending unit, configured to send a first frame to a second device; wherein, a first link and a second link are established between the first device and the second device, the first frame is used to indicate preemption of some or all of the transmission resources in the transmission opportunity TXOP of the first link, and the first frame satisfies one or more of the following: the first frame is transmitted through the second link; in the case where a first moment is earlier than a second moment, the first frame is transmitted through the first link, the first moment is the moment when the first device obtains the transmission resources for transmitting the first frame on the first link, and the second moment is the moment when the first device obtains the transmission resources for transmitting the first frame on the second link.

61. The communication device according to claim 60, It is characterized in that The first frame is used to indicate one or more of the following information: Information requesting to preempt some or all of the transmission resources of the TXOP; Information requesting to preempt the link to which the TXOP belongs; Information on the data stream to be transmitted.

62. The communication device according to claim 61, wherein, The information on preempting some or all of the transmission resources of the TXOP includes one or more of the following: some or all of the duration of the TXOP; some or all of the bandwidth of the TXOP.

63. The communication device according to claim 61 or 62, wherein, The information on the data stream to be transmitted includes one or more of the following information of the data stream: traffic identifier TID, data stream queue size, scaling factor of the data stream queue size.

64. The communication device according to any one of claims 60-63, wherein, The first frame is an action management frame, a quality of service QoS data frame carrying a control field, a QoS null frame carrying a control field, or a management frame carrying a control field.

65. The communication device according to any one of claims 60-64, wherein, The communication device is further configured to: Receive the first information sent by the second device; wherein, the first information is used to indicate the information on the data stream allowed to preempt the TXOP.

66. The communication device according to claim 65, wherein, The information on the data stream allowed to preempt the TXOP includes the type of the data stream allowed to preempt the TXOP.

67. The communication device according to claim 65 or 66, wherein, The first information is carried in one or more of the following frames: beacon frame, association response frame, re-association response frame.

68. The communication device according to any one of claims 65-67, wherein, The information on the data stream allowed to preempt the TXOP includes: information on the uplink data stream allowed to preempt the TXOP and / or information on the downlink data stream allowed to preempt the TXOP.

69. The communication device according to any one of claims 65-68, wherein, The sending unit is specifically configured to: Send a first frame to the second device when the TXOP is allowed to be preempted.

70. The communication device according to any one of claims 60-69, wherein, The communication device is further configured to: Receive the second information sent by the second device; wherein, the second information is used to indicate one or more of the following: Whether the TXOP is allowed to be preempted; Whether the TXOP is allowed to be preempted by the first frame; Whether the physical layer protocol data unit PPDU sent within the TXOP is fragmented.

71. The communication device according to claim 70, wherein, The second information is transmitted through the first link.

72. The communication device according to claim 70 or 71, wherein, The second information is carried in the control field of the frame.

73. The communication device according to any one of claims 70-72, wherein, The second information is included in the RTS frame.

74. The communication device according to any one of claims 60-73, wherein, when the TXOP is allowed to be preempted by the first frame, the PPDU sent by the first device within the TXOP is fragmented.

75. The communication device according to claim 74, wherein, the fragmented PPDU includes a plurality of end markers, and when the TXOP is preempted by the first frame, the fragmented PPDU stops transmitting at the nearest end marker.

76. The communication device according to any one of claims 60-75, wherein, the communication device is further configured to: receive third information sent by the second device; wherein the third information is used to indicate the duration for which the TXOP is allowed to be preempted.

77. The communication device according to any one of claims 60-76, wherein, the communication device is further configured to: receive a first response frame sent by the second device; wherein the first response frame is used to indicate whether the first device successfully preempts the TXOP.

78. The communication device according to claim 77, wherein, the first response frame is used to indicate one or more of the following information: a status code, used to indicate whether the first device successfully preempts the TXOP, and / or whether the second device allows the first device to preempt the TXOP; whether the second device permits the first device to perform reverse transmission on the first link; the transmission resources of the TXOP that the first device can preempt; the link to which the TXOP successfully preempted by the first device belongs.

79. The communication device according to claim 78, wherein, the first response frame is an action management frame.

80. The communication device according to any one of claims 60-79, wherein, the first link belongs to a plurality of links, and the first frame is used to preempt the transmission resources of the TXOP of the plurality of links.

81. The communication device according to any one of claims 60-80, wherein, the TXOP belongs to the second device, and the TXOP is used for the second device to send data to the first device. The communication device is further configured to: in response to the first device successfully preempting the TXOP of the first link, perform reverse transmission on the first link according to the permission of the second device.

82. The communication device according to claim 81, wherein, the first device indicates the first device to perform reverse transmission on the first link through an interaction primitive.

83. The communication device according to any one of claims 60-82, wherein, the TXOP belongs to the second device, and the communication device is further configured to: in response to the first device successfully preempting the TXOP or allowing the first device to preempt the TXOP, receive a first trigger frame or a second trigger frame sent by the second device; Among them, the first trigger frame and the second trigger frame are both transmitted on the first link. The first trigger frame is used to trigger the first device to send data to the second device on the first link, and the second trigger frame is used to share the TXOP with the first device.

84. The communication device according to any one of claims 60-80, wherein, the TXOP belongs to a third device, the first frame is used to trigger the second device to send a second frame to the third device, and the second frame is used for the second device to preempt the TXOP.

85. The communication device according to claim 84, wherein, the communication device is further configured to: in response to the second device successfully preempting the TXOP of the first link, receive the first trigger frame or the second trigger frame sent by the second device; Among them, the first trigger frame and the second trigger frame are both transmitted on the first link. The first trigger frame is used to trigger the first device to send data to the second device on the first link, and the second trigger frame is used to share the TXOP with the first device.

86. The communication device according to any one of claims 60-85, wherein, both the first device and the second device are multi-link devices.

87. The communication device according to any one of claims 60-86, wherein, the data stream requesting to preempt the TXOP includes a delay-sensitive data stream.

88. The communication device according to any one of claims 60-87, wherein, the communication device is further configured to: perform channel access on the second link; Among them, the channel access process is implemented by first enhanced distributed channel access (EDCA) parameters, and the first EDCA parameter is less than or equal to a first threshold.

89. The communication device according to any one of claims 60-88, wherein, the communication device is further configured to: determine whether to send the first frame to the second device according to the remaining duration of the TXOP; Among them, the remaining duration of the TXOP is determined by the network allocation vector (NAV) of the second device on the first link.

90. A communication device, wherein, the communication device is a second device, and the communication device includes: a receiving unit, configured to receive a first frame sent by a first device; Among them, a first link and a second link are established between the first device and the second device. The first frame is used to indicate preemption of some or all of the transmission resources in the transmission opportunity (TXOP) of the first link. The first frame satisfies one or more of the following: the first frame is transmitted through the second link; in the case where a first moment is earlier than a second moment, the first frame is transmitted through the first link, the first moment is the moment when the first device obtains the transmission resources for transmitting the first frame on the first link, and the second moment is the moment when the first device obtains the transmission resources for transmitting the first frame on the second link.

91. The communication device according to claim 90, wherein, The first frame is used to indicate one or more of the following information: Information requesting to preempt some or all of the transmission resources of the TXOP; Information requesting to preempt the link to which the TXOP belongs; Information on the data stream to be transmitted.

92. The communication device according to claim 91, wherein, the information on preempting some or all of the transmission resources of the TXOP includes one or more of the following: some or all of the duration of the TXOP; some or all of the bandwidth of the TXOP.

93. The communication device according to claim 91 or 92, wherein, the information on the data stream to be transmitted includes one or more of the following information on the data stream: traffic identifier TID, data stream queue size, scale factor of the data stream queue size.

94. The communication device according to any one of claims 90-93, wherein, the first frame is an action management frame, a quality of service QoS data frame carrying a control field, a QoS null frame carrying a control field, or a management frame carrying a control field.

95. The communication device according to any one of claims 90-94, wherein, the communication device is further configured to: send first information to the first device; wherein, the first information is used to indicate information on the data stream allowed to preempt the TXOP.

96. The communication device according to claim 95, wherein, the information on the data stream allowed to preempt the TXOP includes the type of the data stream allowed to preempt the TXOP.

97. The communication device according to claim 95 or 96, wherein, the first information is carried in one or more of the following frames: beacon frame, association response frame, re-association response frame.

98. The communication device according to any one of claims 95-97, wherein, the information on the data stream allowed to preempt the TXOP includes: information on the uplink data stream allowed to preempt the TXOP and / or information on the downlink data stream allowed to preempt the TXOP.

99. The communication device according to any one of claims 90-98, wherein, the receiving unit is specifically configured to: receive the first frame sent by the first device when the TXOP is allowed to be preempted.

100. The communication device according to any one of claims 90-99, wherein, the communication device is further configured to: send second information to the first device; wherein, the second information is used to indicate one or more of the following: whether the TXOP is allowed to be preempted; whether the TXOP is allowed to be preempted by the first frame; whether the physical layer protocol data unit PPDU sent within the TXOP is fragmented.

101. The communication device according to claim 100, wherein, the second information is transmitted through the first link.

102. The communication device according to claim 100 or 101, wherein, the second information is carried in the control field of the frame.

103. The communication device according to any one of claims 100-102, It is characterized in that the second information is included in the RTS frame.

104. The communication device according to any one of claims 90-103, It is characterized in that when the TXOP is allowed to be preempted by the first frame, the PPDU sent by the first device within the TXOP is fragmented.

105. The communication device according to claim 104, It is characterized in that the fragmented PPDU includes a plurality of end markers, and when the TXOP is preempted by the first frame, the fragmented PPDU stops transmitting at the nearest end marker.

106. The communication device according to any one of claims 90-105, It is characterized in that the communication device is further configured to: send third information to the first device; wherein the third information is used to indicate the duration for which the TXOP is allowed to be preempted.

107. The communication device according to any one of claims 90-106, It is characterized in that the communication device is further configured to: send a first response frame to the first device; wherein the first response frame is used to indicate whether the first device successfully preempts the TXOP.

108. The communication device according to claim 107, It is characterized in that the first response frame is used to indicate one or more of the following information: a status code, used to indicate whether the first device successfully preempts the TXOP, and / or whether the second device allows the first device to preempt the TXOP; whether the second device permits the first device to perform reverse transmission on the first link; the transmission resources of the TXOP that the first device can preempt; the link to which the TXOP successfully preempted by the first device belongs.

109. The communication device according to claim 108, It is characterized in that the first response frame is an action management frame.

110. The communication device according to any one of claims 90-109, It is characterized in that the first link belongs to a plurality of links, and the first frame is used to preempt the transmission resources of the TXOPs of the plurality of links.

111. The communication device according to any one of claims 90-110, It is characterized in that the TXOP belongs to the second device, the TXOP is used for the second device to send data to the first device, and the communication device is further configured to: permit the first device to perform reverse transmission on the first link in response to the first device successfully preempting the TXOP of the first link.

112. The communication device according to claim 111, It is characterized in that the first device indicates the first device to perform reverse transmission on the first link through an interaction primitive.

113. The communication device according to any one of claims 90-112, It is characterized in that the TXOP belongs to the second device, and the communication device is further configured to: send a first trigger frame or a second trigger frame to the first device in response to the first device successfully preempting the TXOP or allowing the first device to preempt the TXOP; Among them, the first trigger frame and the second trigger frame are both transmitted on the first link. The first trigger frame is used to trigger the first device to send data to the second device on the first link, and the second trigger frame is used to share the TXOP with the first device.

114. The communication device according to any one of claims 90-110, characterized in that the TXOP belongs to a third device, the first frame is used to trigger the second device to send a second frame to the third device, and the second frame is used for the second device to preempt the TXOP.

115. The communication device according to claim 114, characterized in that the communication device is further configured to: in response to the second device successfully preempting the TXOP of the first link, send a first trigger frame or a second trigger frame to the first device; Among them, the first trigger frame and the second trigger frame are both transmitted on the first link. The first trigger frame is used to trigger the first device to send data to the second device on the first link, and the second trigger frame is used to share the TXOP with the first device.

116. The communication device according to any one of claims 90-115, characterized in that both the first device and the second device are multi-link devices.

117. The communication device according to any one of claims 90-116, characterized in that the data flow requesting to preempt the TXOP includes a delay-sensitive data flow.

118. The communication device according to any one of claims 90-117, characterized in that the communication device is further configured to: after the first device finishes preempting the TXOP, continue to transmit signals within the TXOP.

119. A communication device, characterized in that it includes a memory and a processor. The memory is used to store programs, and the processor is used to call the programs in the memory so that the communication device executes the method according to any one of claims 1-59.

120. A device, characterized in that it includes a processor, which is used to call a program from a memory so that the device executes the method according to any one of claims 1-59.

121. A chip, characterized in that it includes a processor, which is used to call a program from a memory so that the device installed with the chip executes the method according to any one of claims 1-59.

122. A computer-readable storage medium, characterized in that a program is stored thereon, and the program enables a computer to execute the method according to any one of claims 1-57.

123. A computer program product, characterized in that it includes a program, and the program enables a computer to execute the method according to any one of claims 1-59.

124. A computer program, characterized in that the computer program enables a computer to execute the method according to any one of claims 1-59.

Images