Data transmission method, storage medium, electronic device and product

Abstract

Embodiments of the present application provide a data sending method, a storage medium, an electronic device and a product. The method comprises: a pre-empting station (STA) sending a transmission opportunity pre-emption request to a point-to-point (P2P) transmission opportunity initiator, wherein the transmission opportunity pre-emption request comprises pre-emption information; the pre-empting STA receiving a transmission opportunity pre-emption request response sent by the P2P transmission opportunity initiator, and sending a data frame in the pre-empted transmission opportunity. Through the embodiments of the present application, the problem that other data frames cannot be transmitted in time due to waiting for long frame transmission of non-time delay sensitive services, such as P2P transmission ending, is solved.

Description

Technical Field

[0001] This application relates to the field of communications, and more specifically, to a data transmission method, storage medium, electronic device, and product. Background Technology

[0002] Different types of real-time applications or latency-sensitive services may have different latency metrics. Latency metrics in upcoming communication protocols, such as IEEE 802.11 versions (e.g., WiFi 8), may range from 1ms to 10ms. In current protocols, the longest Physical Layer Protocol Data Unit (PPDU) is 5.484ms, and the transmission opportunity (TXOP) duration can reach 6ms. Therefore, if a Station Address (STA) has real-time application traffic and other latency-sensitive traffic, the needs of its real-time application traffic and other latency-sensitive traffic may not be met while other STAs are transmitting long frames of non-latency-sensitive services (e.g., peer-to-peer (P2P) transmissions). In such scenarios, the STA may not be able to tolerate waiting for the long frame of a P2P transmission to end, making data frame transmission impossible. Summary of the Invention

[0003] This application provides a data transmission method, storage medium, electronic device, and product to at least solve the problem in the related art where other data frames cannot be transmitted in a timely manner due to waiting for the transmission of long frames of non-latency-sensitive services, such as the end of P2P transmission.

[0004] According to one embodiment of this application, a data transmission method is provided, comprising: a preempting station STA sending a transmission opportunity preemption request to a peer-to-peer (P2P) transmission opportunity initiator, wherein the transmission opportunity preemption request includes preemption information; the preempting STA receiving a transmission opportunity preemption request response sent by the P2P transmission opportunity initiator, and transmitting a data frame in the preempted transmission opportunity.

[0005] According to another embodiment of this application, a data transmission method is provided, wherein a point-to-point (P2P) transmission opportunity initiator receives a transmission opportunity preemption request sent by a preempting station (STA), wherein the transmission opportunity preemption request includes preemption information; the P2P transmission opportunity initiator sends a transmission opportunity preemption request response to the preempting STA, so that the preempting STA can transmit data frames in the preempted transmission opportunity.

[0006] According to yet another embodiment of this application, a computer-readable storage medium is also provided, wherein a computer program is stored therein, and the computer program is configured to perform the steps in any of the above method embodiments when it is run.

[0007] According to yet another embodiment of this application, an electronic device is also provided, including a memory and a processor, wherein the memory stores a computer program and the processor is configured to run the computer program to perform the steps in any of the above method embodiments.

[0008] According to yet another embodiment of this application, a computer program product is also provided, including a computer program that, when executed by a processor, implements the steps in any of the above method embodiments.

[0009] Through the embodiments described above in this application, when a preemptive STA has data frames to send, the preemptive STA can send a transmission opportunity preemption request to seize the currently ongoing transmission opportunity and use the preempted transmission opportunity to send data frames. This reduces the waiting time for data frame transmission, and network resources can be allocated more efficiently to data frames that need to be sent. Therefore, the problem of delayed transmission of other data frames caused by waiting for the transmission of long frames of non-latency-sensitive services, such as the end of P2P transmission, can be solved. Attached Figure Description

[0010] Figure 1 This is a hardware structure block diagram of a computer terminal for a data transmission method according to an embodiment of this application;

[0011] Figure 2 This is a diagram of the network structure of wireless communication devices;

[0012] Figure 3 This is a flowchart of a data transmission method according to an embodiment of this application;

[0013] Figure 4 This is a schematic diagram of a TDLS transmission example, a P2P transmission technology.

[0014] Figure 5 A schematic diagram of a TXOP sharing opportunity;

[0015] Figure 6 This is a schematic diagram of a transmission timeline;

[0016] Figure 7 This is a flowchart of a data transmission method according to another embodiment of this application;

[0017] Figure 8 This is a structural block diagram of a data transmission apparatus according to an embodiment of this application;

[0018] Figure 9 This is a structural block diagram of a data transmission apparatus according to another embodiment of the present application;

[0019] Figure 10 This is a block diagram of a wireless communication device according to an embodiment of this application;

[0020] Figure 11 This is a schematic diagram of the long-term preemption protocol negotiation according to an embodiment of this application;

[0021] Figure 12 This is a schematic diagram of short-term preemption protocol negotiation according to an embodiment of this application;

[0022] Figure 13 This is a schematic diagram (a) illustrating the P2P transmission opportunity preemption according to an embodiment of this application;

[0023] Figure 14 This is a schematic diagram (II) illustrating P2P transmission opportunity preemption according to another embodiment of this application;

[0024] Figure 15 This is a schematic diagram (iii) illustrating P2P transmission opportunity preemption according to another embodiment of this application;

[0025] Figure 16 This is a schematic diagram (four) illustrating the P2P transmission opportunity preemption according to yet another embodiment of this application;

[0026] Figure 17 This is a schematic diagram (V) illustrating the P2P transmission opportunity preemption according to yet another embodiment of this application;

[0027] Figure 18 This is a schematic diagram (six) illustrating P2P transmission opportunity preemption according to yet another embodiment of this application;

[0028] Figure 19 This is a schematic diagram (VII) illustrating P2P transmission opportunity preemption according to yet another embodiment of this application;

[0029] Figure 20 This is a schematic diagram (eight) illustrating P2P transmission opportunity preemption according to yet another embodiment of this application. Detailed Implementation

[0030] The embodiments of this application will be described in detail below with reference to the accompanying drawings and examples.

[0031] It should be noted that the terms "first," "second," etc., in the specification, claims, and drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence.

[0032] The methods and embodiments provided in this application can be executed on a mobile terminal, computer terminal, or similar computing device. Taking running on a mobile terminal as an example, Figure 1 This is a hardware structure block diagram of the mobile terminal used in the embodiments of the method of this application. For example... Figure 1 As shown, a mobile terminal may include one or more ( Figure 1 Only one is shown in the diagram. A processor 102 (which may include, but is not limited to, a microprocessor MCU or a programmable logic device FPGA, etc.) and a memory 104 for storing data are also shown. The mobile terminal may further include a transmission device 106 for communication functions and an input / output device 108. Those skilled in the art will understand that... Figure 1 The structure shown is for illustrative purposes only and does not limit the structure of the mobile terminal described above. For example, the mobile terminal may also include components that are more... Figure 1 The more or fewer components shown, or having the same Figure 1 The different configurations shown.

[0033] The memory 104 can be used to store computer programs, such as application software programs and modules, like the computer program corresponding to the data transmission method in this embodiment. The processor 102 executes various functional applications and data processing by running the computer program stored in the memory 104, thus implementing the above-described method. The memory 104 may include high-speed random access memory and non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 104 may further include memory remotely located relative to the processor 102, and these remote memories can be connected to the mobile terminal via a network. Examples of such networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

[0034] The transmission device 106 is used to receive or send data via a network. Specific examples of the network described above may include a wireless network provided by the mobile terminal's communication provider. In one example, the transmission device 106 includes a Network Interface Controller (NIC), which can connect to other network devices via a base station to communicate with the Internet. In another example, the transmission device 106 may be a Radio Frequency (RF) module, used for wireless communication with the Internet.

[0035] Figure 2 It is a network composed of one or more wireless communication devices, and the embodiments of this application can be applied to Figure 2 The wireless devices mentioned above can also be used with other wireless devices. Figure 2This includes an access point (AP) 102 and a wireless terminal device (STA) 104. In some examples, these devices are capable of exchanging data according to the Institute of Electrical and Electronics Engineers (IEEE) 802 series standards. The IEEE 802 standards cover communication specifications for a variety of network devices, from Local Area Networks (LANs) to Metropolitan Area Networks (MANs). In particular, the IEEE 802.11 standard sets clear guidelines for communication in Wireless Local Area Networks (WLANs). In these networks, communication must adhere to at least one communication protocol to ensure communication between different devices. These communication protocols are dynamically evolving and are continuously updated with technological advancements to enhance communication stability and improve data transmission efficiency.

[0036] IEEE 802.11 wireless communication technology can also be referred to as WiFi technology. In this example, AP102 and STA104 transmit data via one or more protocols from the IEEE 802.11 protocol family. These protocols cover a range from early standards such as 802.11b, 802.11g, and 802.11a, to the Very High Throughput (VHT) of 802.11n and 802.11ac, to the High Efficiency (HE) of 802.11ax, and the Extremely High Throughput (EHT) of 802.11be. Furthermore, it includes next-generation IEEE 802.11 technologies such as the Ultra High Reliability (UHR) standard, as well as other developing IEEE 802.11 wireless communication specifications.

[0037] In other examples, AP102 and STA104 may communicate according to other standards, such as the Long-Term Evolution (LTE) standard developed by the Third Generation Partnership Project (3GPP). Furthermore, wireless communication standards may include LTE-A (an enhanced version of LTE), next-generation 5G NR technology, Bluetooth, global navigation satellite systems (such as GPS or GLONASS), and mobile television broadcasting standards (such as ATSC-M / H). These technologies can be used individually or in combination. In some embodiments, STA104 may be designed to support only a single wireless communication technology. The names of AP102 and STA104 may also differ depending on the technological context. For example, in an LTE network, AP102 may be referred to as an Evolved NodeB (eNB), while STA104 may be referred to as User Equipment (UE).

[0038] In some embodiments, the wireless terminal device, also known as a station (STA), may be more specifically defined as a non-access point STA (non-AP STA). These STAs 104 are capable of wirelessly connecting to nearby network devices, such as access points (APs 102). The wireless terminal device can be a mobile phone, handheld device, wearable device, computer or tablet, unmanned aerial vehicle (UAV), unmanned flight controller (UAC), vehicle, or virtually any type of wireless device. The STA may include a processor configured to execute program instructions stored in memory. The STA 104 can perform any of the methods described in this application by executing such stored instructions. Alternatively, the STA 104 may also include programmable hardware elements, such as field-programmable gate arrays (FPGAs), integrated circuits, or other hardware components configured to perform any part or all of the methods described herein.

[0039] In some implementations, AP102 can be defined as a station (STA), and more specifically, an access point STA (AP STA). AP102 can be, but is not limited to, a router, a mobile terminal enabling a hotspot, a base station, etc., all possessing the hardware to wirelessly communicate with STA104. Furthermore, AP102 can be configured to communicate with network 106, which can be a telecommunications network, such as the Public Switched Telephone Network (PSTN), the Internet, or other possible networks. Therefore, AP102 can enable communication not only between STA104 but also between STA104 and network 106. As will be further described later in this document, AP102 includes the hardware required to achieve wireless communication with STA104, and may also include hardware and software components for implementing or supporting the features described herein.

[0040] The communication range of AP102 is typically referred to as the Basic Service Set (BSS). AP102 and STA104 can communicate via various radio access technologies or wireless communication technologies, including but not limited to LTE, LTE Advanced (LTEA), 5G NR, WiFi, and Ultra Wideband (UWB). AP102 can also be configured to provide STA104 with a communication connection to network 106.

[0041] The STA104 can also be configured to communicate with other STA104 devices. For example, the STA104 can be configured to support direct device-to-device communication, commonly referred to as peer-to-peer (P2P) communication. This communication method allows two devices to communicate directly without the AP102.

[0042] Multiple BSSs can be combined to form an Extended Service Set (ESS). In this example, AP102 may not be a single access point, but rather one of multiple access points. A controller, not shown in the diagram, can be responsible for storing and managing shared information among the multiple AP102s and for controlling the BSSs, such as allocating parameters like the primary channel and BSS color.

[0043] The traditional STA108 can operate according to one or more standards in the IEEE 802.11 standard family, which may include 802.11a / b / g / n / ac / ad / ah / ay / ax, etc. The AP102 can communicate with the traditional STA108 using traditional IEEE 802.11 communication technology.

[0044] The MAC and PHY layers in AP102 and STA104 exchange PDUs (Protocol Data Units) and SDUs (Service Data Units) during the management of wireless communication traffic. The PHY layer is configured to receive SDUs from the MAC layer, encapsulating the MACSDUs into PPDUs (Physical Layer Protocol Data Units) by adding a preamble. In some embodiments, different types of PPDUs may exist, such as single-user (SU) PPDUs, downlink (DL) PPDUs, multi-user (MU) PPDUs, extended range (ER) SUPPDUs, and / or trigger-based (TB) PPDUs. The PPDU preamble may include various training fields that the receiving AP102 or STA104 uses to perform synchronization, gain control, channel characteristic estimation, and signal equalization. AP102 and STA104 then exchange wireless communication signals in PPDU format.

[0045] Wireless communication channel bandwidths offer a variety of options, including but not limited to 20MHz, 40MHz, 80MHz, 160MHz, and combinations such as 80+80MHz. Furthermore, in some embodiments, the channel bandwidth may reach 320MHz, or appear in a combination of 160+160MHz. For narrower channels, bandwidth options may include subdivisions from 1MHz to 10MHz, or combinations thereof, or other bandwidths less than or equal to the available bandwidth may also be used. In some embodiments, the channel bandwidth may also be determined based on the number of subcarriers carrying data, which may be 26, 52, 106, 242, 484, 996, and 2x996. In some embodiments, the allocation of bandwidth, tone, or number of subcarriers may be referred to as resource unit (RU) allocation.

[0046] In some embodiments of IEEE 802.11, such as the ax / be embodiment, AP102 gains control of the wireless channel through a contention mechanism to acquire a transmission window (TXOP). During the TXOP, AP102 can transmit frames containing EHT / HE trigger information, which may be related to the synchronous uplink and downlink data transmission of STA104. AP102 can provide the duration of the TXOP and RU allocation information. STA104 communicates with AP102 using multiple access technologies such as OFDMA or MUMIMO. During the TXOP, AP102 can send one or more PPDUs to exchange data with STA104.

[0047] In some implementations, STA104 and / or AP102 are configured to perform the methods and functions described in the embodiments of this application. The term "WiFi" may refer to one or more versions of the IEEE 802.11 communication standard. APs and STAs may include access points and terminal devices based on EHT / HE technology standards, as well as conventional wireless communication devices.

[0048] Figure 3 This is a flowchart of a data transmission method according to an embodiment of this application, such as... Figure 3 As shown, the process includes the following steps:

[0049] Step S302: The preempting station STA sends a transmission opportunity preemption request to the peer-to-peer P2P transmission opportunity initiator, wherein the transmission opportunity preemption request includes preemption information;

[0050] It's important to note that P2P transmission is a network data exchange model where each node (or peer) in the network can act as a provider and consumer of services and data, directly interacting with other nodes without the need for a central server. P2P architecture is widely used in both wireless LANs (WLANs) and wired networks, demonstrating unique advantages, particularly in file sharing, streaming media distribution, online gaming, and distributed computing. In the IEEE 802.11 standard, P2P transmission is applied in various scenarios, such as file sharing, allowing direct file sharing between devices without intermediary devices or networks; direct transmission of video and music playback between two devices; and XR devices connecting computing units via P2P.

[0051] In one embodiment, Figure 4 This diagram illustrates a Tunneled Direct Link Setup (TDLS) transmission example, showing P2P transmission between STA1 and STA2. TDLS is a technology that allows wireless devices (such as laptops and smartphones) to establish direct connections for communication without going through an access point (AP). TDLS is based on the IEEE 802.11z standard. TDLS technology allows devices to automatically create a link between each other after accessing the wireless network, eliminating the need for data transmission through an AP and avoiding delays caused by network congestion.

[0052] like Figure 5As shown, STA1 and STA2 negotiated the TDLS protocol. After STA1 successfully competes for the channel through the backoff procedure, it sends a Request To Send (RTS) frame to protect the TXOP initiated by STA1. STA2 sends a Clear To Send (CTS) frame. Subsequently, STA1 can perform one or more data burst transmissions within the TXOP time protected by RTS / CTS.

[0053] Figure 5 It is the TXOP sharing procedure defined by IEEE 802.11be, in which the TXOP sharing mode subfield value carried by MU-RTS TXS is equal to 2. After the target STA1 successfully receives the MU-RTS TXS frame, it responds with CTS, and then can carry out P2P transmission within the time period shared with STA1.

[0054] If, during P2P transmission, the AP, P2P responders, or other STAs with uplink transmission needs to send low-latency data (e.g., in XR scenarios where computing units need to exchange data with the network via the AP, or the AP may have urgent data to send to other devices), or in industrial deployments where some STAs have higher traffic priority, these STAs need to wait for the current transmission to finish. In the current protocol, the longest PPDU length is 5.484ms, and the TXOP duration can reach 6ms. Therefore, the needs of real-time application traffic and other latency-sensitive traffic flows of these STAs may not be met. Furthermore, the increased number of STAs, packet collisions due to exponential backoff, and the prolonged channel blocking caused by long TXOPs from some devices all contribute to increased latency. Figure 6 A possible transmission timeline is shown, in which the low-latency (LL) service of STA2 arrives during the TXOP of STA1, and the LL service needs to be delayed until STA1 completes the TXOP and STA2 finishes competing for the channel.

[0055] In an exemplary embodiment of this application, the preemption information includes at least one of the following: preemption object, preemption mode, preemption physical layer protocol data unit (PPDU) length, and preemption duration.

[0056] In an exemplary embodiment of this application, the preemptive STA includes a P2P transmission opportunity recipient or a third-party STA, wherein the third-party STA includes STAs other than the P2P transmission opportunity initiator and the P2P transmission opportunity recipient.

[0057] The P2P transmission technology involved in the embodiments of this application is not limited to a specific method. It can be applied to other P2P transmission technologies such as TDLS protocol and TXOP sharing. During the P2P TXOP, the P2P transmission opportunity recipient or a third-party STA can preempt the TXOP for transmitting low-latency data. In some embodiments, the third-party STA can be an AP or a STA with high priority.

[0058] Step S304: The preempting STA receives the transmission opportunity preemption request response sent by the P2P transmission opportunity initiator, and sends a data frame in the preempted transmission opportunity.

[0059] In an exemplary embodiment of this application, before the preempting STA sends a data frame in the preempted transmission opportunity, the method further includes: the preempting STA sending a frame carrying a preemption indication to the P2P transmission opportunity initiator, so that the P2P transmission sender stops data transmission in the transmission opportunity preempted by the preempting STA; wherein, the preempting STA is the P2P transmission opportunity receiver.

[0060] In an exemplary embodiment of this application, the preempting STA transmits data frames during the preempted transmission opportunity, including: the preempting STA transmitting one or more data frames to the P2P transmission opportunity initiator during the preempted transmission opportunity, wherein the preempting STA is the P2P transmission opportunity receiver; and when the data frame transmission is completed or the preempted transmission opportunity ends, the preempting STA transmits a frame carrying the return of the transmission opportunity to the P2P transmission opportunity initiator, so that the P2P transmission opportunity initiator can resume data transmission.

[0061] In an exemplary embodiment of this application, the preempting STA transmits data frames during the preempted transmission opportunity, including: the preempting STA transmitting one or more data frames to a third-party STA during the preempted transmission opportunity, wherein the preempting STA is a P2P transmission opportunity receiver; when the data frame transmission is completed or the preempted transmission opportunity ends, the P2P transmission opportunity receiver sends a frame carrying the return of the transmission opportunity to the P2P transmission opportunity initiator, so that the P2P transmission opportunity initiator can resume data transmission.

[0062] In an exemplary embodiment of this application, before the preempting STA sends a transmission opportunity preemption request to the peer-to-peer (P2P) transmission opportunity initiator, the method further includes: the preempting STA receiving a frame carrying a preemption permission indication sent by the P2P transmission opportunity initiator and a frame sent by the P2P transmission receiver, wherein the preempting STA is a third-party STA.

[0063] In an exemplary embodiment of this application, the preempting STA transmits data frames during the preempted transmission opportunity, including: the third-party STA transmits one or more data frames to the P2P transmission opportunity initiator during the preempted transmission opportunity; and when the data frame transmission is completed or the preempted transmission opportunity ends, the third-party STA sends a frame carrying the return of the transmission opportunity to the P2P transmission opportunity initiator so that the P2P transmission opportunity initiator can resume data transmission.

[0064] In an exemplary embodiment of this application, the preemptive STA transmitting data frames during the preempted transmission opportunity includes: a third-party STA transmitting one or more data frames to other third-party STAs during the preempted transmission opportunity.

[0065] In an exemplary embodiment of this application, if a third-party STA confirms that there is an inter-frame interval greater than the Short Frame Inter-Frame Spacing (SIFS) in a transmission opportunity, it uses SIFS to send a data frame to the P2P transmission opportunity initiator to preempt the transmission opportunity. The data frame carries transmission opportunity return indication information to indicate that the P2P transmission opportunity initiator can resume the transmission opportunity.

[0066] In an exemplary embodiment of this application, a third-party STA sends a data frame during a preempted transmission opportunity, including: the third-party STA sending a data frame to other third-party STAs during the preempted transmission opportunity; wherein the data frame carries a transmission opportunity return indication, which is used to instruct the third-party STA to return the transmission opportunity and stop the burst transmission of SIFS after sending the data frame, so that the P2P transmission opportunity initiator can resume transmission opportunity transmission after confirming the end of the data frame transmission.

[0067] In one embodiment, regarding the P2P transmission opportunity, the initiator resumes transmission opportunity transmission after confirming the end of data frame transmission. If STA4 is not hidden from STA1, STA1 resumes TXOP transmission after waiting for an acknowledgment frame sent by STA4. If STA4 is hidden from STA1, i.e., STA1 cannot hear the BA frame sent by STA4, then STA3 needs to send a notification frame carrying TXOP return indication information after receiving the BA frame sent by STA4. This frame can be a control frame addressed to STA1 or a QoS NULL frame addressed to STA1 without requiring an acknowledgment. Subsequently, STA1 can resume TXOP transmission.

[0068] In an exemplary embodiment of this application, when the transmission opportunity preemption request is used to indicate that the transmission opportunity requested by the preempting STA is greater than a preset threshold, the effective period of the transmission opportunity preemption request is N transmission opportunities, where N is a positive integer greater than 1; when the transmission opportunity preemption request is used to indicate that the transmission opportunity requested by the preempting STA is less than the preset threshold, the effective period of the transmission opportunity preemption request is one transmission opportunity.

[0069] In one embodiment, the preempting STA sends a Tunnel Direct Link Establishment (TDLS) request frame to the P2P transmission opportunity initiator. The preempting STA receives a TDLS establishment response frame returned by the P2P transmission opportunity initiator. The TDLS establishment request frame and the TDLS establishment response frame carry preemption information. The preempting STA and the P2P transmission opportunity initiator reach a TDLS protocol and complete long-term negotiation. The TDLS establishment response frame is effective for N transmission opportunities, where N is a positive integer greater than 1. That is, after one negotiation is completed, the STA can preempt multiple times within a certain period of time. During the effective period of the TDLS protocol, the preemption method in this embodiment can be executed.

[0070] In one embodiment, the preempting STA sends a multi-user request to share a transmission opportunity frame to the P2P transmission opportunity initiator. The preempting STA receives a multi-user request to share a transmission opportunity response frame from the P2P transmission opportunity initiator, completing a short-term negotiation. The multi-user request to share a transmission opportunity frame is valid for a single transmission opportunity. A multi-user request to extend service transmission frame indicates that the transmission opportunity the preempting STA is requesting to preempt is less than a preset threshold. During the transmission opportunity period for sending the user request to share a transmission opportunity frame, the preemption method described in this embodiment can be executed.

[0071] Figure 7 This is a flowchart of a data transmission method according to another embodiment of this application, such as... Figure 7 As shown, the process includes the following steps:

[0072] Step S702: The point-to-point (P2P) transmission opportunity initiator receives a transmission opportunity preemption request sent by the preemption site (STA), wherein the transmission opportunity preemption request includes preemption information.

[0073] In an exemplary embodiment of this application, the preemption information includes at least one of the following: preemption object, preemption mode, preemption PPDU length, and preemption duration.

[0074] In an exemplary embodiment of this application, the preemptive STA includes a P2P transmission opportunity recipient or a third-party STA, wherein the third-party STA includes STAs other than the P2P transmission opportunity initiator and the P2P transmission opportunity recipient.

[0075] In an exemplary embodiment of this application, a point-to-point (P2P) transmission opportunity initiator receives a transmission opportunity preemption request sent by a preempting station (STA), including: the P2P transmission opportunity initiator receiving a Tunnel Direct Link Establishment (TDLS) request frame sent by the preempting STA, wherein the TDLS establishment request frame is used to indicate that the transmission opportunity requested by the preempting STA is greater than a preset threshold.

[0076] In an exemplary embodiment of this application, the P2P transmission opportunity initiator receives a transmission opportunity preemption request sent by the preempting STA, including: the P2P transmission opportunity initiator receives a multi-user request to send extended service transmission frame sent by the preempting STA, wherein the multi-user request to send extended service transmission frame is used to indicate that the transmission opportunity requested to be preempted by the preempting STA is less than a preset threshold.

[0077] In step S704, the P2P transmission opportunity initiator sends a transmission opportunity preemption request response to the preempting STA, so that the preempting STA can send data frames in the preempted transmission opportunity.

[0078] In an exemplary embodiment of this application, after the P2P transmission opportunity initiator sends a transmission opportunity preemption request response to the preempting STA, the method further includes: the P2P transmission opportunity initiator stopping data transmission during the transmission opportunity preempted by the preempting STA.

[0079] In an exemplary embodiment of this application, before the point-to-point (P2P) transmission opportunity initiator receives the transmission opportunity preemption request sent by the preempting STA, the method further includes: the P2P transmission opportunity initiator sending a frame carrying a preemption permission indication to the preempting STA, wherein the preempting STA is a third-party STA.

[0080] In an exemplary embodiment of this application, after the data frame transmission is completed, the P2P transmission sender sends an acknowledgment request frame to the P2P transmission receiver during a preempted transmission opportunity or during a transmission opportunity following a preempted transmission opportunity.

[0081] In an exemplary embodiment of this application, the P2P transmission opportunity initiator receives a data frame sent by a third-party STA using a short frame inter-frame interval. The data frame is used to preempt the transmission opportunity, and carries transmission opportunity return indication information, which is used to indicate to the P2P transmission opportunity initiator that the transmission opportunity can be resumed.

[0082] In an exemplary embodiment of this application, the P2P transmission opportunity initiator detects the channel idle time; if the P2P transmission opportunity initiator detects that the channel idle time is greater than or equal to the Point Coordination Function Inter-Frame Spacing (PIFS), the transmission opportunity is resumed.

[0083] In an exemplary embodiment of this application, the P2P transmission opportunity initiator resumes transmission opportunity transmission after confirming the end of data frame transmission; wherein, the data frame is sent by a third-party STA to other STAs during the preempted transmission opportunity, and the data frame carries a transmission opportunity return indication, which is used to instruct the third-party STA to return the transmission opportunity and stop the burst transmission of SIFS after sending the data frame.

[0084] In an exemplary embodiment of this application, after the P2P transmission opportunity initiator sends a frame carrying a preemption indication to the preempting STA, the method further includes: the P2P transmission opportunity initiator modifying the network allocation vector (NAV) of the transmitted data frame. The modified NAV is used to protect the non-preempting STA from competing for the channel during the Point Coordination Function Inter-Frame Spacing (PIFS) time. The modified NAV includes at least the Short Frame Spacing (SIFS), PIFS, and an acknowledgment frame or block acknowledgment frame.

[0085] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods according to the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal device (which may be a mobile phone, computer, server, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0086] This embodiment also provides a data transmission device for implementing the above embodiments and preferred embodiments; details already described will not be repeated. As used below, the term "module" can refer to a combination of software and / or hardware that performs a predetermined function. Although the device described in the following embodiments is preferably implemented in software, hardware implementation, or a combination of software and hardware, is also possible and contemplated.

[0087] Figure 8 This is a structural block diagram of a data transmission apparatus according to an embodiment of this application, such as... Figure 8 As shown, the device includes: a first transmitting module 801 and a second transmitting module 802.

[0088] The first sending module 801 is used to send a transmission opportunity preemption request to the initiator of the peer-to-peer (P2P) transmission opportunity, wherein the transmission opportunity preemption request includes preemption information.

[0089] The second sending module 802 is used to receive the transmission opportunity preemption request response sent by the P2P transmission opportunity initiator, and send data frames in the preempted transmission opportunity.

[0090] Figure 9 This is a structural block diagram of a data transmission apparatus according to another embodiment of the present application, such as... Figure 9 As shown, the device includes a receiving module 901 and a third transmitting module 902.

[0091] The receiving module 901 is used to receive a transmission opportunity preemption request sent by the preempting station STA, wherein the transmission opportunity preemption request includes preemption information;

[0092] The third transmitting module 902 is used to send a transmission opportunity preemption request response to the preempting STA, so that the preempting STA can transmit data frames in the preempted transmission opportunity.

[0093] To facilitate understanding of the technical solutions provided in the application embodiments, the following description is based on specific scenario embodiments.

[0094] Figure 10 This is a block diagram of a wireless communication device according to an embodiment of this application, such as... Figure 10 As shown, device 200 can operate independently or connect with other devices to form a network system. When device 200 is deployed in a network, it can operate as a server or client in a server-client mode, or as a node in a P2P network mode. Device 200 may represent AP102, STA104, STA108, or any other device capable of executing relevant instructions, including methods for implementing or supporting the features described herein.

[0095] Device 200 includes processor 204 (e.g., central processing unit (CPU), graphics processing unit (GPU) or any combination thereof), memory 202, display device 212, input device 214, sensor device 216 and antenna 218.

[0096] Memory 202 stores the control program and various data used. AP102 and STA104, STA108 can be configured to implement or support the implementation of part or all of the methods described herein, for example, by executing program instructions stored in the memory. The memory can be implemented as RAM, flash memory, ROM, EPROM, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art. In this respect, the memory can be coupled to the processor, allowing the processor to read information from and write information to the memory. In some embodiments, the memory may each include a cache for storing temporary variables or other intermediate information during the execution of instructions executed by the processor. The memory may also include non-volatile memory for storing instructions to be executed by the processor. Upon device power-up, one or more programs stored on a hard disk or read-only memory are transferred to random access memory and registers for storing variables and parameters required by the present invention.

[0097] Device 200 may also include display device 212 and input device 214 (e.g., keyboard and mouse). In some embodiments, display device 212 and input device 214 may be touch screen displays. Sensor 216 may be, for example, a Global Positioning System (GPS) sensor or other sensors.

[0098] Processor 204 is responsible for executing various instruction sets or software programs and managing data transmission and reception tasks. Processor 204 may include a Media Access Control Unit 206 (MAC unit), a Physical Layer Unit 208 (PHY unit), and a storage unit 210. These units, including PHY unit 208, MAC unit 206, and storage unit 210, can be interconnected and may be partially or entirely integrated on a single chip. Processor 204 can implement or assist in implementing one or more of the functions, operations, or methods described herein by running program code stored in storage units 202 or 210. Furthermore, processor 204 can be configured to use one or more antennas to transmit and receive signals with other wireless devices (e.g., AP 102, STA 104, or legacy device 108). In a particular embodiment, PHY unit 208 is responsible for performing functions such as signal encoding and decoding, power amplification, and filtering, including generating baseband signals for transmission and decoding received signals. PHY unit 208 can also transmit signals according to one of the 802.11 standards discussed herein, such as 802.11ax / 802.11be. MAC unit 206 is responsible for managing access rights to the wireless communication medium. In some embodiments, MAC unit 206 can compete for access to the wireless medium based on Network Allocation Vector (NAV) and Channel Clearance Assessment (CCA). Certain functions of signal transmission and reception may be performed collaboratively by PHY unit 208, MAC unit 206, and other components. In some embodiments, processor 204 may integrate one or more general-purpose or purpose-specific processors. Processor 204 may also be configured as a Field Programmable Gate Array (FPGA) or implemented using dedicated hardware components such as Application-Specific Integrated Circuits (ASICs) to implement the required hardware and logic circuitry. In some cases, the implementation of processor 204 may rely on the combination of software-configured elements with other hardware elements.

[0099] Antenna 218 may include one or more directional or omnidirectional antennas, including, for example, linearly polarized antennas, circularly polarized antennas, narrowband antennas, wideband antennas, ultra-wideband antennas, or other types of antennas suitable for transmitting RF signals. In some embodiments, antenna 218 may be configured to perform wireless communication using at least one of single-input multiple-output (SIMO), multiple-input multiple-output (MIMO), or multiple-input single-output (MISO) technologies. In some embodiments, multi-user MIMO technology may be used for wireless communication.

[0100] In several embodiments, the methods described herein may be implemented entirely in software, or in part through a combination of software and firmware. These software components and / or firmware may be encoded on a persistent computer-readable storage medium for the processor to read. The processor parses and executes these encoded instructions to perform the series of operations described herein. These instructions may exist in various forms, including but not limited to raw source code, compiled code, scripts requiring interpretation, directly executable programs, statically compiled programs, or dynamically generated programs.

[0101] This application provides a method for preempting P2P transmission opportunities. First, the P2P TXOP initiator needs to negotiate a preemption strategy with the preempting STA. This negotiation can be a long-term negotiation or a short-term negotiation based on the TXOP. After the P2P STA and the preempting STA complete the negotiation, the preempting STA can preempt the TXOP to send low-latency data frames. In response to the TXOP preemption action, the P2P TXOP initiator suspends TXOP transmission until a later time before transmitting data. Finally, the P2P TXOP responder or the AP returns the TXOP and resumes P2P transmission. In some embodiments, the preempting STA can be a STA paired with the P2P STA for P2P transmission. In other embodiments, the preempting STA can be an AP or other non-AP STA.

[0102] Regarding the negotiation phase, negotiations can be divided into long-term preemptive agreement negotiations and short-term preemptive agreement negotiations. For example... Figure 11 As shown, the validity period of the long-term preemption protocol negotiation typically lasts for multiple Beacon frame cycles. In this embodiment, the preempting STA is the AP. STA1 can negotiate the preemption protocol with the AP through the exchange of associated frames. The associated frames contain preemption information, which may include information such as the preemption target, preemption mode, preemption PPDU length, and preemption duration.

[0103] Furthermore, if the P2P transmission is initiated by the TDLS protocol, during TDLS negotiation, the STA can send a TDLS establishment request frame and a TDLS suggestion response frame containing preemption information. The STA can also initiate preemption session negotiation independently after TDLS establishment; the STA can send a TDLS preemption request frame and a TDLS preemption response frame containing the aforementioned information. This information can be carried by newly defined element fields.

[0104] like Figure 12As shown, short-term preemption negotiation can be conducted between the P2PTXOP initiator and the preemptive STA at the start of each P2PTXOP. In this embodiment, the preemptive STA is the AP. The negotiation can be carried out through an action frame containing preemption information. The preemption information may include the preemption mode, such as the various preemption mode embodiments described in this application, the preemption duration, the preemption start time, and other information.

[0105] Furthermore, if the P2P transmission is initiated in TXOP sharing mode, the AP can carry preemption information in the MU-RTS TXS frame for short-term preemption protocol negotiation. This preemption information can be indicated using the reserved field in the MU-RTS TXS frame. Since the AP is the TXOP initiator and shares the TXOP with the STA for P2P transmission, the AP can force itself to preempt the TXOP within the shared time period using the methods described in this disclosure or other disclosures. After preempting the TXOP, the AP can choose not to return it, meaning the AP reclaims the TXOP sharing time period early. Alternatively, the AP can choose to return the TXOP before the shared time expires using the methods described in this disclosure or other disclosures, and then reuse the TXOP after the shared time expires.

[0106] After the preemptive STA completes the preemption protocol negotiation, it can preempt based on the preemption start time. The preemptive STA does not need to track the exchange process of each frame in the P2PTXOP process. In some embodiments, the preemptive STA is a low-power device. The preemptive STA can enter a sleep state before the preemption start time to save power, and wake up and begin preemption when the preemption start time expires. In other embodiments, the P2PTXOP initiator itself has low-latency traffic to send, so the P2PTXOP initiator can determine the preemption start time through a short preemption negotiation method to allow the P2PTXOP initiator sufficient time to transmit low-latency traffic.

[0107] Figure 13This is a schematic diagram (I) of P2P transmission opportunity preemption according to an embodiment of this application, where STA1 is the P2P TXOP initiator and STA2 is the TXOP responder. Low-latency traffic arrives at STA2 during STA1's TXOP period. STA2 can carry a preemption TXOP indication in the Block Acknowledgment (BA) frame sent to STA1. After receiving the BA frame carrying the preemption TXOP indication, STA1 will stop SIFS burst transmission. STA2 can subsequently send a low-latency data frame addressed to STA1 after sending the BA frame. STA2 can send one or more low-latency data frames within the TXOP until STA2's low-latency data transmission is completed, the TXOP time expires, or for other reasons. STA2 can carry a return TXOP indication in the low-latency data frame and stop SIFS burst transmission. STA1 resumes TXOP transmission after receiving the data frame carrying the return TXOP indication. In addition, STA2 can also choose not to send low-latency data frames carrying TXOP return indication information. STA2 only needs to suspend SIFS burst transmission, and STA1 can resume TXOP transmission after checking the channel for continuous idle PIFS time.

[0108] Although a preemption request may resemble a Reverse Authorization Group (RDG) protocol message, the direction of the preemption request is reversed (i.e., from the TXOP responder to the TXOP holder). In IEEE 802.11e, RDG can be used by the TXOP initiator to provide the TXOPs it has acquired to the TXOP responder. Since RDG is determined by the TXOP initiator, it is difficult to schedule low-latency traffic for the TXOP responder in a timely manner.

[0109] To define the control signaling for a preemption request indication, at least one of the following methods can be used. First, reuse the CAS control subfield, using a reserved bit to indicate the preemption request in the CAS control subfield. Second, define a new A-control subfield. The new subfield can include more information, but this method requires defining a new control signaling subfield. Third, use a reserved bit in the BA (Block Acknowledgment) frame.

[0110] In the P2P transmission process shared by TXOP, using Figure 13 The method described can also meet the requirements of P2P reverse transmission. Currently, many P2P transmissions require bidirectional transmission. In the TXOP shared P2P transmission baseline rules, the responder of a P2P transmission cannot transmit data to the initiator of the P2P transmission (TXOP shared object) within the shared time.

[0111] Figure 14This is a schematic diagram (II) of P2P transmission opportunity preemption according to another embodiment of this application, wherein after receiving a data frame sent by STA1, STA2 can directly send a low-latency data frame addressed to the TXOP initiator STA1 or a third party STA3. In some embodiments, STA3 can be an AP with uplink low-latency traffic that needs to be sent. At this time, STA1 needs to suspend TXOP transmission. STA2 can send one or more low-latency data frames. Finally, STA2 can send a BA frame to STA1 to indicate that STA1 can resume TXOP transmission. Another function of the BA frame is to respond to the data frame addressed to STA2 sent by STA1 before the preemption occurred.

[0112] Figure 15 This is a schematic diagram (III) of P2P transmission opportunity preemption according to another embodiment of this application. STA2 has low-latency data frames addressed to a third party STA3. STA2 carries preemption TXOP indication information in the BA frame sent to STA1. Subsequently, STA1 suspends TXOP transmission, allowing STA2 to send low-latency data frames addressed to STA3. STA2 can send one or more low-latency data frames within the TXOP until STA2's low-latency data transmission is completed, the TXOP time expires, or for other reasons. STA2 can carry a return TXOP indication in the low-latency data frame and stop SIFS burst transmission. STA1 resumes TXOP transmission after waiting for an acknowledgment frame sent by STA3. Optionally, if STA3 is hidden from STA1, i.e., STA1 cannot hear the BA frames sent by STA3, then STA2 needs to send a notification frame carrying return TXOP indication information after receiving the BA frame sent by STA3. This frame can be a control frame, such as a BA frame addressed to STA1, or a QoS NULL frame addressed to STA1 without requiring an acknowledgment. Subsequently, STA1 can resume TXOP transmission.

[0113] Whether STA3 is a hidden node of STA1 depends on the network topology. Furthermore, in other P2P transmission technologies, there may be P2P transmission groups where all STAs can hear each other. Therefore, if STA1, STA2, and STA3 are members of the same P2P transmission group, STA2 does not need to send a notification frame.

[0114] The above-mentioned preemption method is the preemption process in P2P transmission where the responder preempts the TXOP by sending an address to the TXOP initiator (a shared object in TXOP sharing mode) or a third-party STA.

[0115] Figure 16This is a schematic diagram (fourth) illustrating P2P transmission opportunity preemption according to another embodiment of this application, wherein STA1 is the initiator of the P2P transmission TXOP or a shared object under TXOP sharing, and STA3 buffers low-latency data frames addressed to STA1 during TXOP or shared TXOP. In some embodiments, STA3 may be an AP or a STA with high priority in certain scenarios. Figure 16 In the illustrated process, each DATA-BA step of the P2P transmission uses PIFS or other inter-frame intervals longer than SIFS. STA3 can use SIFS to send low-latency data frames addressed to STA1 to preempt the TXOP. STA3 can carry a TXOP return indication in the low-latency data frame to indicate to STA1 that it can resume TXOP transmission. Alternatively, STA3 can choose not to send a low-latency data frame carrying the TXOP return indication; STA3 only needs to suspend SIFS burst transmission, and STA1 can resume TXOP transmission after checking the channel for a sustained PIFS idle time.

[0116] Figure 17 This is a schematic diagram (five) of P2P transmission opportunity preemption according to another embodiment of this application, wherein SIFS inter-frame interval is used in each DATA-BA process of P2P transmission. STA1 can carry preemption permission indication information in the data frame to indicate that STA3 can preempt the TXOP to send low-latency data frames. If STA3 has buffered low-latency data frames, it can burst-send low-latency data frames to preempt the TXOP after the BA frame responding to the data frame carrying the preemption permission indication. STA3 returns the TXOP process and... Figure 16 The process is the same.

[0117] Figure 18 This is a schematic diagram (six) illustrating P2P transmission opportunity preemption according to another embodiment of this application. STA3 may not have buffered low-latency data frames. STA1 sends a data frame carrying preemption permission information and continuously listens for the channel idle PIFS time after receiving the BA frame. STA1 can then resume TXOP transmission. In some embodiments, the NAV of STA1's DATA transmission only protects the SIFS+BA / ACK time. Therefore, it is necessary to modify the NAV of STA1's DATA transmission to the SIFS+PIFS+ACK / BA time to protect the channel contention of non-preemptive STAs during the PIFS time.

[0118] Figure 19This is a schematic diagram (seven) illustrating P2P transmission opportunity preemption according to another embodiment of this application, wherein STA3 buffers low-latency data frames addressed to a third party STA4. STA3 carries a TXOP return indication in the low-latency data frame and stops SIFS burst transmission. STA1 resumes TXOP transmission after waiting for an acknowledgment frame sent by STA4. Optionally, if STA4 is hidden from STA1, i.e., STA1 cannot hear the BA frames sent by STA4, then STA3 needs to send a notification frame carrying TXOP return indication information after receiving the BA frame sent by STA4. This frame can be a control frame addressed to STA1 or a QoS NULL frame addressed to STA1 without requiring an acknowledgment. Subsequently, STA1 can resume TXOP transmission.

[0119] Figure 20 This is a schematic diagram (eight) of P2P transmission opportunity preemption according to another embodiment of this application, wherein STA2 stops sending BA frames after receiving a data frame carrying a preemption permission indication sent by STA1. STA3 can preempt the TXOP by burst transmitting a low-latency data frame after the data frame via SIFS. When STA3 returns the TXOP, if there is sufficient remaining time in the TXOP, STA1 can send a BA request frame before the TXOP ends to request STA2 to send a BA frame in response to the data frame addressed to STA2 before preemption. If the TXOP time is insufficient, STA1 can choose to end the TXOP and initiate a TXOP again in the next re-contention for the channel to send a BA request frame.

[0120] Figures 16 to 20 In the example of STA3 preemption shown, STA3 needs to satisfy basic NAV = 0 in order to preempt, which is to protect other ongoing OBSS TXOPs; STA3 can ignore intraNAV.

[0121] Embodiments of this application also provide a computer-readable storage medium storing a computer program, wherein the computer program is configured to execute the steps in any of the above method embodiments when run.

[0122] In one exemplary embodiment, the aforementioned computer-readable storage medium may include, but is not limited to, various media capable of storing computer programs, such as a USB flash drive, read-only memory (ROM), random access memory (RAM), portable hard disk, magnetic disk, or optical disk.

[0123] Embodiments of this application also provide an electronic device including a memory and a processor, wherein the memory stores a computer program and the processor is configured to run the computer program to perform the steps in any of the above method embodiments.

[0124] In one exemplary embodiment, the electronic device may further include a transmission device and an input / output device, wherein the transmission device is connected to the processor and the input / output device is connected to the processor.

[0125] Specific examples in this embodiment can be found in the examples described in the above embodiments and exemplary implementations, and will not be repeated here.

[0126] Obviously, those skilled in the art should understand that the modules or steps of this application described above can be implemented using general-purpose computing devices. They can be centralized on a single computing device or distributed across a network of multiple computing devices. They can be implemented using computer-executable program code, and thus can be stored in a storage device for execution by a computing device. In some cases, the steps shown or described can be performed in a different order than those presented here, or they can be fabricated as separate integrated circuit modules, or multiple modules or steps can be fabricated as a single integrated circuit module. Thus, this application is not limited to any particular combination of hardware and software.

[0127] The above description is merely a preferred embodiment of this application and is not intended to limit this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the principles of this application should be included within the protection scope of this application.

Claims

1. A data transmission method, characterized in that, include: The STA (Station) sends a transmission opportunity preemption request to the initiator of the peer-to-peer (P2P) transmission opportunity, wherein the transmission opportunity preemption request includes preemption information; The preempting STA receives the transmission opportunity preemption request response sent by the P2P transmission opportunity initiator, and sends data frames in the preempted transmission opportunity.

2. The method according to claim 1, characterized in that, The preemption information includes at least one of the following: preemption target, preemption mode, preemption physical layer protocol data unit (PPDU) length, and preemption duration.

3. The method according to claim 1, characterized in that, The preempting STA includes the P2P transmission opportunity recipient or a third-party STA, wherein the third-party STA includes STAs other than the P2P transmission opportunity initiator and the P2P transmission opportunity recipient.

4. The method according to claim 1, characterized in that, in, When the transmission opportunity preemption request is used to indicate that the transmission opportunity to be preempted by the preemption STA is greater than a preset threshold, the validity period of the transmission opportunity preemption request is N transmission opportunities, where N is a positive integer greater than 1. When the transmission opportunity preemption request is used to indicate that the transmission opportunity to be preempted by the preempting STA is less than a preset threshold, the validity period of the transmission opportunity preemption request is one transmission opportunity.

5. The method according to claim 3, characterized in that, Before the preempting STA sends a data frame during the preempted transmission opportunity, the process also includes: The preempting STA sends a frame carrying a preemption indication to the P2P transmission opportunity initiator, so that the P2P transmission sender stops data transmission in the transmission opportunity preempted by the preempting STA. The preempting STA is the P2P transmission opportunity receiver.

6. The method according to claim 3, characterized in that, The preempting STA transmits data frames during the preempted transmission opportunity, including: The preempting STA sends one or more data frames to the P2P transmission opportunity initiator during the preempted transmission opportunity, wherein the preempting STA is the P2P transmission opportunity receiver. Upon completion of the data frame transmission or the termination of the preempted transmission opportunity, the preempting STA sends a frame carrying the return of the transmission opportunity to the P2P transmission opportunity initiator, so that the P2P transmission opportunity initiator can resume data transmission.

7. The method according to claim 3, characterized in that, The preempting STA transmits data frames during the preempted transmission opportunity, including: The preempting STA sends one or more data frames to a third-party STA during the preempted transmission opportunity, wherein the preempting STA is a P2P transmission opportunity receiver. Upon completion of the data frame transmission or the termination of the preempted transmission opportunity, the P2P transmission opportunity receiver sends a frame carrying the return of the transmission opportunity to the P2P transmission opportunity initiator, so that the P2P transmission opportunity initiator can resume data transmission.

8. The method according to claim 3, characterized in that, Before the preempting station (STA) sends a transmission opportunity preemption request to the peer-to-peer (P2P) transmission opportunity initiator, the method further includes: The preempting STA receives a frame carrying a preemption instruction sent by the P2P transmission opportunity initiator and a frame sent by the P2P transmission receiver, wherein the preempting STA is the third-party STA.

9. The method according to claim 8, characterized in that, The preempting STA transmits data frames during the preempted transmission opportunity, including: The third-party STA sends one or more data frames to the P2P transmission opportunity initiator during the preempted transmission opportunity. Upon completion of the data frame transmission or the termination of the preempted transmission opportunity, the third-party STA sends a frame carrying the return of the transmission opportunity to the P2P transmission opportunity initiator, so that the P2P transmission opportunity initiator can resume data transmission.

10. The method according to claim 8, characterized in that, The preempting STA transmits data frames during the preempted transmission opportunity, including: The third-party STA sends one or more data frames to other third-party STAs during the preempted transmission opportunity.

11. The method according to claim 3, characterized in that, The method further includes: If the third-party STA confirms that there is an inter-frame interval greater than the Short Frame Inter-Frame Spacing (SIFS) in the transmission opportunity, it uses the SIFS to send a data frame to the P2P transmission opportunity initiator to preempt the transmission opportunity. The data frame carries transmission opportunity return indication information to indicate that the P2P transmission opportunity initiator can restore the transmission opportunity.

12. The method according to claim 3, characterized in that, The third-party STA sends data frames during the preempted transmission opportunity, including: The third-party STA sends data frames to other third-party STAs during the preempted transmission opportunity; The data frame carries a return transmission opportunity indication, which instructs the third-party STA to return the transmission opportunity and stop SIFS burst transmission after sending the data frame, so that the P2P transmission opportunity initiator can resume transmission opportunity transmission after confirming the end of the data frame transmission.

13. A data transmission method, characterized in that, include: The peer-to-peer (P2P) transmission opportunity initiator receives a transmission opportunity preemption request sent by the preemption site (STA), wherein the transmission opportunity preemption request includes preemption information; The P2P transmission opportunity initiator sends a transmission opportunity preemption request response to the preempting STA, so that the preempting STA can send data frames in the preempted transmission opportunity.

14. The method according to claim 13, characterized in that, The preemption information includes at least one of the following: preemption target, preemption mode, preemption PPDU length, and preemption duration.

15. The method according to claim 13, characterized in that, The preempting STA includes the P2P transmission opportunity recipient or a third-party STA, wherein the third-party STA includes STAs other than the P2P transmission opportunity initiator and the P2P transmission opportunity recipient.

16. The method according to claim 13, characterized in that, in, When the transmission opportunity preemption request received by the P2P transmission opportunity initiator is used to indicate that the transmission opportunity requested by the preemption STA is greater than a preset threshold, the validity period of the transmission opportunity preemption request is N transmission opportunities, where N is a positive integer greater than 1. When the transmission opportunity preemption request is used to indicate that the transmission opportunity to be preempted by the preempting STA is less than a preset threshold, the validity period of the transmission opportunity preemption request is one transmission opportunity.

17. The method according to claim 13, characterized in that, After the P2P transmission opportunity initiator sends a transmission opportunity preemption request response to the preempting STA, the process also includes: The P2P transmission opportunity initiator stops data transmission during the transmission opportunity seized by the preemptive STA.

18. The method according to claim 13, characterized in that, Before the point-to-point (P2P) transmission opportunity initiator receives the transmission opportunity preemption request sent by the preempting site (STA), the process also includes: The P2P transmission opportunity initiator sends a frame carrying a preemption permission indication to the preempting STA, wherein the preempting STA is a third-party STA.

19. The method according to claim 18, characterized in that, The method further includes: Upon completion of the data frame transmission, the P2P transmission sender sends an acknowledgment request frame to the P2P transmission receiver during the preempted transmission opportunity or during a subsequent transmission opportunity.

20. The method according to claim 15, characterized in that, The method further includes: The P2P transmission opportunity initiator receives a data frame sent by the third-party STA using a short frame inter-frame interval. The data frame is used to preempt the transmission opportunity. The data frame carries transmission opportunity return indication information, which is used to indicate to the P2P transmission opportunity initiator that the transmission opportunity can be resumed.

21. The method according to claim 20, characterized in that, The method further includes: The P2P transmission opportunity initiator detects the channel idle time; If the P2P transmission opportunity initiator detects that the channel idle time is greater than or equal to the Point Coordination Function Inter-Frame Interval (PIFS), the transmission opportunity is resumed.

22. The method according to claim 20, characterized in that, The method further includes: the P2P transmission opportunity initiator resumes transmission opportunity transmission after confirming the end of data frame transmission; The data frame is sent by the third-party STA to other STAs during the preempted transmission opportunity. The data frame carries a return transmission opportunity indication, which is used to instruct the third-party STA to return the transmission opportunity and stop the burst transmission of SIFS after sending the data frame.

23. The method according to claim 18, characterized in that, After the P2P transmission opportunity initiator sends a frame carrying a preemption permission indication to the preempting STA, the process further includes: The P2P transmission opportunity initiator modifies the network allocation vector (NAV) for sending data frames. The modified NAV is used to protect the non-preemptive STA contention channel during the PIFS time. The modified NAV includes at least the short frame inter-frame interval (SIFS), PIFS, and acknowledgment frames or block acknowledgment frames.

24. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program, wherein the computer program, when executed by a processor, implements the steps of the method described in any one of claims 1 to 12 or 13 to 23.

25. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the steps of the method described in any one of claims 1 to 12 or 13 to 23.

26. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method described in any one of claims 1 to 12 or 13 to 23.

Images