Data transmission method and electronic apparatus

Abstract

Embodiments of the present disclosure provide a data transmission method and an electronic apparatus. The method comprises: configuring a resource unit for each of a plurality of non-access point devices, wherein the resource unit comprises a first-type resource unit and a second-type resource unit; and sending a trigger frame to the plurality of non-access point devices, wherein the trigger frame is used for indicating the configured resource unit to each of the plurality of non-access point devices, and instructing a target non-access point device among the plurality of non-access point devices to puncture overlapping subcarriers, so that the target non-access point device performs data transmission on unpunctured subcarriers, the target non-access point device is a non-access point device that needs to puncture the overlapping subcarriers, and the overlapping subcarriers are identical subcarriers configured in a frequency domain for some or all of the plurality of non-access point devices.

Description

Data transmission methods and electronic devices

[0001] Cross-references to related applications

[0002] This application is based on and claims priority to Chinese patent application CN2024119828277 entitled “Data Transmission Method and Electronic Device”, filed on December 27, 2024, and incorporates the entire disclosure of that patent application by reference. Technical Field

[0003] This disclosure relates to the field of communications, and more specifically, to a data transmission method and an electronic device. Background Technology

[0004] With the widespread adoption of mobile internet and the continuous optimization of wireless network services, wireless communication technology has developed rapidly, and a wide variety of smart devices such as tablets, sensors, and smartphones have become integrated into our lives. Wireless Local Area Networks (WLANs) have gained increasing attention due to their advantages such as flexible networking methods and low deployment costs.

[0005] Figure 1 illustrates a WLAN network consisting of one or more wireless communication devices, including an access point (AP) 102 and a station (STA) 104. These devices are capable of exchanging data according to the IEEE 802.11 series of standards. IEEE 802.11 wireless communication technology can also be referred to as Wi-Fi technology. The technologies defined by the IEEE 802.11 series of standards include Medium Access Control (MAC) and Physical Layer (PHY) protocols. Wireless communication technology based on IEEE 802.11 can also be referred to as Wi-Fi technology.

[0006] Wi-Fi devices are subject to PSD (Power Segment Limitation) regulations, which are particularly stringent in the 6GHz band. For STA devices in the LPI band, the PSD limit is as low as -1dBm / MHz. If the subcarriers in the RU (Resource Unit) used for transmission are continuous, for the sake of discussion, they are simply referred to as RRU (regular RU). Due to the PSD limitation, the uplink communication rate and communication distance of the STA are severely restricted. Summary of the Invention

[0007] This disclosure provides a data transmission method and electronic device to at least solve the problem of severely limited uplink communication rate and communication distance of STA in the related art.

[0008] According to one embodiment of this disclosure, a data transmission method is provided, which should be configured as an access point device, comprising: configuring resource units for a plurality of non-access point devices, wherein the resource units include a first type of resource unit and a second type of resource unit; sending a trigger frame to the plurality of non-access point devices, wherein the trigger frame is configured to indicate the configured resource units to the plurality of non-access point devices and to instruct a target non-access point device among the plurality of non-access point devices to puncture overlapping subcarriers, so that the target non-access point device performs data transmission on unpunctured subcarriers; wherein the target non-access point device is a non-access point device that needs to puncture the overlapping subcarriers; the overlapping subcarriers are the same subcarriers configured in the frequency domain by some or all of the plurality of non-access point devices.

[0009] According to one embodiment of this disclosure, a data transmission method is provided, which should be configured as a non-access point device, comprising: configuring resource units according to a received trigger frame, wherein the trigger frame is configured to instruct an access point device to configure resource units to a plurality of non-access point devices, the resource units including a first type of resource unit and a second type of resource unit; when the non-access point device is a target access point device, puncturing overlapping subcarriers according to the trigger frame, and transmitting data on unpunctured subcarriers; wherein the overlapping subcarriers are the same subcarriers configured in the frequency domain by some or all of the plurality of non-access point devices.

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

[0011] According to yet another embodiment of this disclosure, 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.

[0012] According to yet another embodiment of this disclosure, 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. Attached Figure Description

[0013] Figure 1 is a schematic diagram of a WLAN network consisting of multiple wireless communication devices according to related technologies;

[0014] Figure 2 is a schematic diagram of the OFDMA access mechanism based on relevant technologies;

[0015] Figure 3 is a flowchart of a data transmission method according to an embodiment of the present disclosure;

[0016] Figure 4 is a flowchart of a data transmission method according to another embodiment of the present disclosure;

[0017] Figure 5 is a schematic diagram of the AP indicating the allocation of RU resources in the basic trigger frame according to Embodiment 1 of this disclosure;

[0018] Figure 6 is a schematic diagram of the signaling design according to Embodiment 1 of this disclosure;

[0019] Figure 7 is a schematic diagram of the DRU distribution in a 20MHz PPDU according to Embodiment 2 of this disclosure;

[0020] Figure 8 is a schematic diagram of a predefined subcarrier punching pattern according to Embodiment 2 of this disclosure;

[0021] Figure 9 is a schematic diagram of subcarrier puncturing according to Embodiment 2 of this disclosure;

[0022] Figure 10 is a schematic diagram of the subcarrier puncturing pattern indication in the User info field according to Embodiment 2 of this disclosure;

[0023] Figure 11 is a schematic diagram of the subcarrier puncturing pattern for a user-specific field indication according to Embodiment 2 of this disclosure;

[0024] Figure 12 is a schematic diagram of the offset subcarrier punching according to Embodiment 3 of this disclosure;

[0025] Figure 13 is a schematic diagram of the punching pattern designed according to Embodiment 3 of this disclosure;

[0026] Figure 14 is a schematic diagram of the AP indicating the allocation of DRU resources in the basic trigger frame according to Embodiment 3 of the present disclosure;

[0027] Figure 15 is a schematic diagram of the baseline pattern shifted to the right by two subcarriers according to Embodiment 3 of this disclosure;

[0028] Figure 16 is a schematic diagram of the baseline pattern shifted to the right by 7 subcarriers according to Embodiment 3 of this disclosure;

[0029] Figure 17 is a schematic diagram of the subcarrier puncturing pattern indication in the User info field according to Embodiment 3 of this disclosure;

[0030] Figure 18 is a schematic diagram of the subcarrier puncturing pattern for a user-specific field indication according to Embodiment 3 of this disclosure;

[0031] Figure 19 is a schematic diagram of the baseline pattern designed for different PPDU BWs according to Embodiment 4 of this disclosure;

[0032] Figure 20 is a schematic diagram of the subcarrier puncturing pattern indication in the User info field according to Embodiment 4 of this disclosure;

[0033] Figure 21 is a schematic diagram of the subcarrier puncturing pattern for a user-specific field indication according to Embodiment 4 of this disclosure;

[0034] Figure 22 is a schematic diagram of AP instructing STA to allocate RU resources according to Embodiment 5 of this disclosure;

[0035] Figure 23 is a schematic diagram of the signaling design according to Embodiment 5 of this disclosure;

[0036] Figure 24 is a schematic diagram of an alternative signaling design according to Embodiment 5 of this disclosure;

[0037] Figure 25 is a schematic diagram of subcarrier puncturing according to Embodiment 6 of this disclosure;

[0038] Figure 26 is a schematic diagram of subcarrier puncturing according to Embodiment 7 of this disclosure.

[0039] Figure 27 is a schematic diagram of the structure of an electronic device according to an embodiment of the present disclosure. Detailed Implementation

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

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

[0042] To facilitate understanding of the technical solutions provided in the embodiments of this disclosure, a brief introduction to the relevant technical background is given below.

[0043] Channel bandwidth: Simply put, a channel is a frequency range that determines the frequency range within which a WLAN device communicates. Wi-Fi devices can operate on one or more frequency bands, such as 2.4GHz, 5GHz, 6GHz, and 60GHz. The 802.11 standard specifies multiple channels within each frequency band. Because overlapping channels can cause interference and degrade the overall performance of the wireless network, in practical use, adjacent access points (APs) should typically choose non-overlapping channels.

[0044] 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.

[0045] The concept of Resource Units (RUs) was introduced in IEEE 802.11ax (Wi-Fi 6). For example, an 80MHz channel is divided into multiple RUs within the same time domain. Each RU contains a certain number of subcarriers, and each STA transmits and receives information through the RU. Depending on the number of subcarriers, RUs can be categorized as 26-ton, 52-ton, 106-ton, 242-ton, 484-ton, 996-ton, 2x996-ton, etc. In Wi-Fi 7, different RU combination types are also defined, such as 26+52-ton, 242+484-ton, etc. The subcarriers within each RU are continuously distributed; they include various subcarrier types, such as data tones, pilot tones, DC tones, and guard tones. The size and number of these RUs depend on the channel bandwidth. Table 1 shows the types and numbers of RUs (excluding RU combinations) under different channel bandwidths.

[0046] Table 1

[0047] A tone plan is an important technical concept in WLAN, involving the planning of subcarrier usage in wireless communication. It aims to improve communication performance and efficiency through carefully designed subcarrier positions and parameter settings. The tone plan specifies the positions (subcarrier indices) of the guard subcarriers, data subcarriers, DC subcarriers, pilot subcarriers, and null subcarriers that make up the RU within the PPDU bandwidth.

[0048] One technique for STA uplink communication is based on AP trigger frames. Specifically, the STA receives trigger frames from the AP for UL MU communication. The STA configures a trigger-based PPDU based on the uplink resource information included in the trigger frame, thereby executing uplink communication. As shown in Figure 2, the general process is as follows:

[0049] (1) AP sends a trigger frame (type BSRP): requests the STA's cache information to the AP (or the STA implicitly feeds back the cache information), and the AP calculates the RU to be allocated to the STA based on the wake-up information.

[0050] (2) AP sends trigger frame (type MU-RTS): sends RTS information to multiple STAs to notify them in advance that the air interface will be occupied, thus avoiding collisions between users during transmission.

[0051] (3) AP sends trigger frame (type Basic): indicates the number of spatial streams, PPDU bandwidth, OFDMA corresponding resource allocation indication (used to determine frequency location, RU size and RU index of each user, etc.) and other transmission-related information.

[0052] The trigger frame contains one Common Info and multiple User Info sections. Depending on the specific trigger frame type, the Common Info and User Info fields are not entirely consistent.

[0053] After the uplink UL-OFDMA transmission is completed, the AP will send a Multi-STABlock ACK confirmation to multiple STAs. Alternatively, the AP can send a Block ACK to each STA individually, which is optional in the protocol.

[0054] In future WLAN networks, it is possible that both RRU and DRU-supporting STAs will coexist. Wi-Fi devices that support DRU will also support RRU, while traditional STAs will only support RRU.

[0055] The DRU mechanism allows STAs to overcome PSD limitations, thereby significantly increasing transmit power and expanding their coverage. However, within a certain bandwidth, if DRUs are allocated, the AP will be unable to allocate complete RRUs to STAs; conversely, if a small number of RRUs are allocated within a certain bandwidth, DRU resources cannot be scheduled for other STAs. This is detrimental to the coexistence of STAs using both types of resources within a certain bandwidth, resulting in reduced bandwidth utilization.

[0056] Therefore, this disclosure proposes a method for using RRU and DRU in combination, and the main inventive concept is as follows:

[0057] (1) The premise is that frequency domain resources can be allocated to different STAs simultaneously in the same bandwidth according to RRU and DRU types.

[0058] (2) For subcarriers that overlap / interfere with each other in DRU and RRU, punch ±n subcarriers in the corresponding subcarrier of one type of RU (protect subcarrier) to preserve the integrity of the other type of RU.

[0059] (3) When encoding uplink data, the STA must skip the punched subcarriers and guard subcarriers.

[0060] (4) When the AP receives uplink data, it must also skip the punched subcarriers and guard subcarriers.

[0061] Based on the above-described inventive concept, this disclosure provides a data transmission method applied to an access point device. Figure 3 is a flowchart of the data transmission method according to an embodiment of this disclosure. As shown in Figure 3, the process includes the following steps:

[0062] Step S302: Configure resource units for multiple non-access point devices, wherein the resource units include a first type of resource unit and a second type of resource unit.

[0063] In one embodiment, the first type of resource unit is a continuous resource unit (RRU), and the second type of resource unit is a distributed resource unit (DRU).

[0064] In step S302 of this embodiment, configuring resource units for a plurality of non-access point devices includes one of the following: configuring a continuous resource unit for any non-access point device among the plurality of non-access point devices; configuring a distributed resource unit for any non-access point device among the plurality of non-access point devices; configuring both a continuous resource unit and a distributed resource unit for any non-access point device among the plurality of non-access point devices.

[0065] Step S304: Send a trigger frame to the plurality of non-access point devices, wherein the trigger frame is used to indicate the configured resource elements to the plurality of non-access point devices and to instruct a target non-access point device among the plurality of non-access point devices to puncture overlapping subcarriers, so that the target non-access point device can transmit data on unpunctured subcarriers; wherein the target non-access point device is a non-access point device that needs to puncture the overlapping subcarriers; the overlapping subcarriers are the same subcarriers configured in the frequency domain by some or all of the plurality of non-access point devices.

[0066] In step S304 of this embodiment, sending a trigger frame to the plurality of non-access point devices includes: sending the trigger frame to the plurality of non-access point devices to trigger uplink orthogonal frequency division multiple access transmission of the plurality of non-access point devices, so as to instruct the plurality of non-access point devices to configure the resource unit through the trigger frame; wherein, the trigger frame includes a user information list field, and the user list field includes a resource unit allocation field.

[0067] In an exemplary embodiment, the trigger frame further carries a resource unit type identifier and a physical layer data unit bandwidth identifier, wherein the resource unit type identifier is used to indicate that the resource unit configured on the non-access point device is a first resource unit and / or a second resource unit, and the physical layer data unit bandwidth is used to indicate the physical layer data unit bandwidth configured on the non-access point device.

[0068] In another exemplary embodiment, the trigger frame also carries a punch mark and a punch pattern mark, wherein the punch pattern mark is used to indicate that the target non-access point device needs to punch overlapping subcarriers, and the punch pattern mark is used to indicate that the target non-access point device determines the overlapping subcarriers.

[0069] In yet another exemplary embodiment, before sending the trigger frame to the plurality of non-access point devices, the method further includes: pre-defining a plurality of puncturing patterns for all subcarrier puncturing scenarios; wherein the puncturing pattern corresponds to the puncturing pattern identifier.

[0070] In yet another exemplary embodiment, the trigger frame also carries a puncture identifier, a target resource unit identifier, and an index of the target resource unit; wherein the target resource unit is a resource unit allocated to the target non-access point device, the puncture identifier is used to indicate that the target non-access point device needs to puncture overlapping subcarriers, and the index of the target resource unit is used to indicate that the target non-access point device punctures overlapping subcarriers in conjunction with a predefined first baseline puncture pattern.

[0071] In yet another exemplary embodiment, the first baseline punch pattern includes a plurality of first baseline punch patterns, one first baseline punch pattern corresponds to one physical layer data unit bandwidth, and one physical layer data unit bandwidth corresponds to one non-access point device.

[0072] In yet another exemplary embodiment, the trigger frame further carries a puncture identifier, an identifier of a second baseline puncture pattern, and an index of a target resource element; wherein the puncture identifier is used to indicate that the target non-access point device needs to puncture the overlapping subcarriers, and the index of the target resource element is used to indicate that the target non-access point device punctures the overlapping subcarriers in combination with the second baseline puncture pattern corresponding to the identifier of the second baseline puncture pattern.

[0073] In yet another exemplary embodiment, each first type of resource or second type of resource of different sizes under a physical layer data unit bandwidth corresponds to a second baseline punch pattern, and a second baseline punch pattern corresponds to a second baseline punch pattern identifier. The different physical layer data unit bandwidths correspond to different non-access point devices.

[0074] In yet another exemplary embodiment, the trigger frame also carries information about resource units allocated by other non-access point devices, wherein the other non-access point devices are non-access point devices other than the target non-access point device among the plurality of non-access point devices, and the information about the resource units includes identification information and index information of the resource units.

[0075] In yet another exemplary embodiment, the trigger frame includes a user information field and a public information field. The user information field carries a punch mark, and the public information field carries at least one of the following: a resource unit type identifier, a physical layer data unit bandwidth identifier, and a punch mark pattern identifier.

[0076] In yet another exemplary embodiment, after sending a trigger frame to the plurality of non-access point devices, the method further includes: encoding data corresponding to an un-punctured subcarrier according to the trigger frame, and transmitting the encoded data to the non-access point devices.

[0077] Through the steps described above in the embodiments of this disclosure, STAs can increase their transmission power by utilizing specific resource unit allocation methods, while not affecting the allocation of resources to other STAs using traditional methods within this bandwidth, thus solving the problem of coexistence of two allocation methods within a certain bandwidth.

[0078] This disclosure provides a data transmission method applied to a non-access point device. Figure 4 is a flowchart of the data transmission method according to an embodiment of this disclosure. As shown in Figure 4, the process includes the following steps:

[0079] Step S402: Configure resource units according to the received trigger frame, wherein the trigger frame is used to instruct the access point device to configure resource units for multiple non-access point devices, and the resource units include a first type of resource unit and a second type of resource unit.

[0080] Step S404: When the non-access point device is the target access point device, the overlapping subcarriers are punctured according to the trigger frame, and data is transmitted on the unpunctured subcarriers; wherein, the overlapping subcarriers are the same subcarriers configured in the frequency domain for some or all of the multiple non-access point devices.

[0081] In this embodiment, the first type of resource unit is a continuous resource unit, and the second type of resource unit is a distributed resource unit.

[0082] In one exemplary embodiment, the trigger frame includes a user-specific field and a public information field. The user-specific field carries at least a resource unit type identifier and a punch identifier. The public information field carries at least one of the following: a resource unit type identifier, a physical layer data unit bandwidth identifier, and a punch pattern identifier.

[0083] In step S402 of this embodiment, configuring resource units according to the received trigger frame includes: configuring resource units according to resource unit type identifier and physical layer data unit bandwidth identifier carried in the trigger frame, wherein the resource unit type identifier is used to indicate that the resource unit configured on the non-access point device is a first resource unit and / or a second resource unit, and the physical layer data unit bandwidth is used to indicate the physical layer data unit bandwidth configured on the non-access point device.

[0084] In an exemplary embodiment, when the non-access point device is the target access point device, puncturing the overlapping subcarriers according to the trigger frame includes: puncturing the overlapping subcarriers according to a puncturing identifier and a puncturing pattern identifier carried in the trigger frame, wherein the puncturing pattern identifier is used to indicate that the target non-access point device needs to puncture the overlapping subcarriers, and the puncturing pattern identifier is used to indicate that the target non-access point device determines the overlapping subcarriers.

[0085] In an exemplary embodiment, when the non-access point device is the target access point device, puncturing overlapping subcarriers according to the trigger frame includes: puncturing the overlapping subcarriers according to a puncturing identifier, a target resource unit identifier, and an index of the target resource unit carried in the trigger frame; wherein the target resource unit is a resource unit allocated to the target non-access point device, the puncturing identifier is used to indicate that the target non-access point device needs to puncture the overlapping subcarriers, and the index of the target resource unit is used to indicate that the target non-access point device punctures the overlapping subcarriers in conjunction with a predefined first baseline puncturing pattern.

[0086] In one exemplary embodiment, the first baseline punch pattern includes multiple patterns, one first baseline punch pattern corresponds to one physical layer data unit bandwidth, and one physical layer data unit bandwidth corresponds to one non-access point device.

[0087] In an exemplary embodiment, when the non-access point device is the target access point device, puncturing the overlapping subcarriers according to the trigger frame includes: puncturing the overlapping subcarriers according to a puncturing identifier, a second baseline puncturing pattern identifier, and a target resource element index carried in the trigger frame; wherein the puncturing identifier is used to indicate that the target non-access point device needs to puncture the overlapping subcarriers, and the target resource element index is used to indicate that the target non-access point device punctures the overlapping subcarriers in combination with the second baseline puncturing pattern corresponding to the second baseline puncturing pattern identifier.

[0088] In an exemplary embodiment, each first type of resource or second type of resource of different sizes under a physical layer data unit bandwidth corresponds to a second baseline punch pattern, and a second baseline punch pattern corresponds to a second baseline punch pattern identifier. The different physical layer data unit bandwidths correspond to different non-access point devices.

[0089] In an exemplary embodiment, when the non-access point device is the target access point device, puncturing the overlapping subcarriers according to the trigger frame includes: puncturing the overlapping subcarriers according to information of resource units allocated by other non-access point devices carried in the trigger frame, wherein the other non-access point devices are non-access point devices other than the target non-access point device among the plurality of non-access point devices, and the information of the resource unit includes identification information and index information of the resource unit.

[0090] In one exemplary embodiment, data transmission on an un-punctured subcarrier includes: receiving encoded data from the access point device and decoding data in the encoded data corresponding to the un-punctured subcarrier according to the un-punctured subcarrier.

[0091] To facilitate understanding of the technical solutions provided in this disclosure, specific scenario embodiments are described below.

[0092] Example 1

[0093] As shown in Figure 5, this embodiment involves DRU / RRU hybrid resource allocation, and may include the following steps:

[0094] Step 1. The AP side, according to the above method, indicates the PPDU (Physical Layer Protocol Data) bandwidth, the allocated RU resources for STA1 and STA2, and the corresponding RU type identifier in the basic trigger frame. For example:

[0095] STA1: RU Allocation: 26-tone RU-8; RU Type Identifier: DRU; Drill Indicator: No Drill.

[0096] STA2: RU Allocation: 26-tone RU-2; RU type identifier: RRU; Punch indication: subcarrier punch information.

[0097] Step 2. After receiving the PPDU, STA1 determines the assigned RU information (i.e., 26-tone DRU-8). STA1 configures the RU for the data field in the UL PPDU according to the indicated RU information (26-tone DRU-8) and sends the uplink PPDU.

[0098] Step 3. After receiving the PPDU, STA2 determines the allocated RU information (i.e., 26-tone RRU-2) and the subcarrier puncturing information; STA2 configures the RU for the data field in the UL PPDU according to the indicated RU information (26-tone RRU-2), and punctures the relevant sub-channels according to the received sub-channel puncturing information, and sends the uplink PPDU.

[0099] Step 4. After receiving the PPDU from STA1 / 2, the AP sends an ACK / BA to acknowledge receipt. When decoding the UL Data from STA2, the AP must also skip the punctured subcarriers.

[0100] As shown in Figure 6, the signaling design example in step 1 is as follows:

[0101] For the UHR-SIG field of the MAC layer basic trigger frame and the physical layer UHR Preamble:

[0102] a) Reuse the existing RU Allocation field;

[0103] b) The RU type identifier field in the User info section indicates the RU type;

[0104] c) The user information section indicates subcarrier puncturing information. This information can also be placed in the public information section, depending on how the puncturing information is indicated.

[0105] Example 2

[0106] This embodiment involves an RRU puncturing pattern. Figure 7 shows a section of the DRU deployment with a 20MHz PPDU (±n guard subcarriers are not shown in the figure).

[0107] Figure 7 shows an example of the DRU distribution in a 20MHz PPDU. As can be seen from Figure 7:

[0108] (1) The spacing between subcarriers in a 26-tone DRU is 9 subcarriers (when the bandwidth is 40 / 80MH, the subcarrier spacing is 18 / 36 subcarriers).

[0109] (2) For a hybrid deployment of DRU and RRU, it is necessary to consider protecting subcarriers to reduce inter-subcarrier interference.

[0110] (3) The larger the DRU size, the more subcarriers; the more DRUs are allocated, the more subcarriers there are.

[0111] It should be noted that in the example in Figure 7, the subcarriers of DRU26 1 to 9 are offset sequentially, and the large-size DRU is a combination of two adjacent small RUs. However, this may not be the case in practice, depending on the final protocol tone plan design.

[0112] For RRUs, available subcarriers = number of RRU subcarriers - number of punctured DRU subcarriers - guard subcarriers (0 or ±1); DRU size and the number of DRUs allocated need to be limited to ensure the proportion of available subcarriers, such as:

[0113] (1) DRU size: cannot be too large, and DRU size ≤ RRU size; for example, 20MHz PPDU: limited to 26-tone DRU.

[0114] (2) Number of DRUs: 1 / 2 / 4 and so on.

[0115] (3) The determination of the above two values ​​is related to various factors such as DRU / RRU size and PPDU bandwidth.

[0116] This embodiment may include the following steps:

[0117] Step 1. As shown in Figure 8, a one-to-one corresponding tone puncturing pattern is predefined for all subcarrier puncturing scenarios. There are many puncturing patterns, but the implementation is simple; the STA can directly determine the puncturing mode based on the pattern ID.

[0118] Step 2. As shown in Figure 9, the AP side determines the resources allocated to STA1 and STA2, and determines the punching pattern ID based on the predefined punching pattern. The basic trigger frame indicates the PPDU bandwidth, the RU resource allocation for STA1 and STA2, the RU type identifier, the punching identifier, the punching pattern ID, and other information.

[0119] STA1: RU Allocation: 26-tone RU-8; RU type identifier: DRU; Punch Pattern ID: 0, meaning no punch.

[0120] STA2: RU Allocation: 26-tone RU-2; RU type identifier: RRU; Punch Pattern ID: 17.

[0121] Step 3. STA1 / 2 receives and parses the frames sent by the AP.

[0122] 1) STA1: Analyze the allocated DRU resources and determine that the subcarrier puncturing pattern = 0, indicating that no puncturing is required.

[0123] 2) STA2: Analyze the allocated RRU resources, determine that the subcarrier punching pattern = 17, indicating that punching is required. The punching pattern is: [1111111x0x

[0124] 111111x0x1111111).

[0125] Step 4. STA2 uses the 26-tone RRU-2 resource allocated to it to punch a hole pattern and remove the corresponding subcarrier (black part in Figure 9).

[0126] Step 5. After receiving the PPDU from STA1 / 2, the AP sends an ACK / BA to acknowledge receipt. When decoding the UL Data from STA2, the AP must also skip the punctured subcarriers.

[0127] For DRUs assigned to multiple users, AP indicates multiple punch patterns, and STA2 combines multiple punch patterns to determine the final punch pattern.

[0128] Signaling design example in step 2:

[0129] a. In the basic trigger frame format of the MAC layer, the subcarrier puncturing pattern in the User info field indicates the puncturing pattern.

[0130] For STA1: Subcarrier puncturing flag = 0, see Figure 10.

[0131] For STA2: Corresponding to two User info records:

[0132] In the first User Info record, the subcarrier punching flag is set to 1;

[0133] In the second User Info record, the number of RUs is 1 and the punch pattern is 17.

[0134] b. The user-specific part field of the UHR-SIG of the physical layer UHR Preamble indicates the subcarrier puncturing pattern, as shown in Figure 11.

[0135] For STA1: RU number = 0;

[0136] For STA2: RU number = 1, punch pattern = 17.

[0137] Additionally, for MDRU, a unique punching pattern can be designed for each scenario; or it can be a combination of multiple DRUs, which can be combined by indicating multiple punching patterns (because MDRU allocates multiple DRUs to one user, which is essentially a combination of multiple DRUs).

[0138] Example 3

[0139] This embodiment relates to a single baseline puncturing pattern plus offset within the PPDU bandwidth. For PPDUs with the same bandwidth:

[0140] Among different RRUs of the same size, the subcarriers that conflict with the DRU are not exactly the same, but they are related (i.e., a certain offset relationship).

[0141] A large-size RU is a combination of small-size RUs according to certain relationships.

[0142] Therefore, for different PPDU BWs, a baseline subcarrier puncturing pattern is designed for each; within the same PPDU BW, the final puncturing pattern for different cases is determined by offset and combination.

[0143] Offset values ​​and combination relationships: related to the final tone plan design in the protocol.

[0144] As shown in Figure 12, when the space before the punch point after offset equals the subcarrier interval (9 subcarriers in this embodiment), the punched subcarrier ± n protection subcarrier is set.

[0145] This embodiment may include the following steps:

[0146] Step 1. Design the baseline pattern for different PPDU BWs. As shown in Figure 13, in this embodiment, the number of patterns is small. It is necessary to combine the DRU / RRU index for offset and the DRU / RRU size for combined calculation to determine the punch pattern in the group. Therefore, it is necessary to transmit the DRU index and DRU size information.

[0147] Step 2. On the AP side, resources are allocated to STA1 and STA2 in the basic trigger frame, and the corresponding RU type identifier, puncturing identifier, DRU index required for puncturing, DRU size, and other information are indicated, as shown in Figure 14:

[0148] STA1: Subcarrier punching flag = 0.

[0149] STA2: Subcarrier puncturing identifier = 1; DRU size: 26-tone; DRU index: 8.

[0150] Step 3. STA1 / 2 receives and parses the frames sent by the AP.

[0151] 1)STA1: Analyze the allocated DRU resources and determine that no punching is required.

[0152] 2)STA2: Parse the allocated RRU resources to obtain the subcarrier puncturing identifier, puncturing-related DRU size, DRU index and other information.

[0153] Step 4. Based on the information obtained in Step 3, STA2 allocates 26-tone RRU-2 resources to itself and, in conjunction with the determined final punching pattern, punches out the corresponding subcarrier (the black part in Figure 11).

[0154] 1) Determine the baseline punching pattern based on the PPDU bandwidth;

[0155] 2) Determine the offset relationship between DRU-1 based on the DRU RU index; determine the offset relationship between DRU-1 and RRU-1 based on your own RU index. Combine these two offsets to offset the baseline pattern and determine the final punch pattern.

[0156] As shown in Figure 15, for RRU-2: the baseline pattern is shifted to the right by 2 subcarriers;

[0157] As shown in Figure 16, for DRU-8: the baseline pattern is shifted to the right by 7 subcarriers.

[0158] If the DRU size is different from the baseline DRU size: the combination of punch patterns also needs to be considered. In this embodiment, the DRU size and the baseline DRU size are the same, so no combination is required.

[0159] Step 5. After receiving the PPDU from STA1 / 2, the AP sends an ACK / BA to acknowledge receipt. When decoding the UL Data from STA2, the AP must also skip the punctured subcarriers.

[0160] In this embodiment, the signaling design example in step 2 is as follows:

[0161] 1) In the basic trigger frame format of the MAC layer:

[0162] 1.1) Indicate the subcarrier puncturing identifier in the User info field;

[0163] 1.2) The common info field indicates information such as DRU size and DRU index required to determine subcarrier puncturing. This information is universal for all STAs that require subcarrier puncturing.

[0164] Specifically, it is identified through the Special User Info field, whose AID12 value is a specific value (such as 2044), as shown in Figure 17.

[0165] 2) The user-specific part of the UHR-SIG of the physical layer UHR Preamble indicates the number of DRUs, DRU size, and DRU index, as shown in Figure 18.

[0166] Alternatively, MDRU can be achieved by offsetting and combining baseline punch patterns.

[0167] Example 4

[0168] This embodiment relates to a multiple baseline punching pattern + offset within the PPDU bandwidth.

[0169] Based on Example 3, this embodiment designs its own baseline punching pattern for different DRU sizes within the same PPDW bandwidth:

[0170] The punching patterns of 26-tone DRU-1 and 26-tone RRU-1 are used as baseline pattern 1;

[0171] The punch patterns of 52-tone DRU-1 and 26-tone RRU-1 are used as baseline pattern 2;

[0172] Similarly, the punch patterns of x-tone DRU-1 and x-tone RRU-1 serve as baseline pattern n.

[0173] Step 1. Design baseline patterns for different PPDU BWs and sizes. Refer to Figure 19. In this embodiment, the number of patterns is moderate, and the patterns are already associated with the DRU / RRU sizes. Only the DRU / RRU index needs to be used for offsetting to determine the final punch pattern. Therefore, only the Pattern ID and DRU index need to be passed.

[0174] Step 2. The AP side allocates resources to STA1 and STA2 in the basic trigger frame and indicates the corresponding RU type identifier, punch identifier, punch pattern ID, DRU index and other information;

[0175] Step 3. STA1 / 2 receives and parses the frames sent by the AP.

[0176] 1)STA1: Parse the allocated DRU resources and determine that no punching is required;

[0177] 2)STA2: Parse the allocated RRU resources to obtain the subcarrier puncturing identifier, puncturing-related pattern ID, DRU index, and other information;

[0178] Step 4. Based on the information obtained in step 3, STA2 allocates 26-tone RRU-2 resources to itself and, in conjunction with the determined final punching pattern, punches out the corresponding subcarriers (the bolded part in Figure 9).

[0179] 1) Determine the baseline punching pattern based on the PPDU bandwidth and pattern ID;

[0180] 2) Determine the offset relationship between DRU-1 based on the DRU index; determine the offset relationship between your own RU index and RRU-1. Combine these two offsets to offset the baseline pattern and determine the final punch pattern.

[0181] Step 5. After receiving the PPDU from STA1 / 2, the AP sends an ACK / BA to acknowledge receipt. When decoding the UL Data from STA2, the AP must also skip the punctured subcarriers.

[0182] In this embodiment, the signaling design example in step 2 is as follows:

[0183] 1) The basic trigger frame format of the MAC layer is shown in Figure 20:

[0184] 1.1) Indicate the subcarrier puncturing identifier in the User info field;

[0185] 1.2) Since the baseline pattern is associated with the RRU size, and the size corresponding to different STAs is different, the Pattern Id, DRU index and other information required for punching are placed in the User Info field.

[0186] For STA1: Subcarrier punching flag = 0.

[0187] For STA2: there are two corresponding User info records (with equal AID12 values).

[0188] In the first User Info record, the subcarrier punching flag is set to 1;

[0189] In the second User Info record, the number of RUs is 1, the punch pattern ID is 1, and the DRU index is 8.

[0190] 2) The user-specific part of the UHR-SIG of the physical layer UHR Preamble indicates the number of DRUs, the baseline Pattern ID, and the DRU index, as shown in Figure 21.

[0191] Additionally, for MDRU, a baseline punching pattern can be designed for MDRU; or it can be a combination of multiple DRUs by indicating multiple punching patterns (because MDRU allocates multiple DRUs to one user, it is essentially a combination of multiple DRUs).

[0192] Example 5

[0193] This embodiment involves a non-drilling pattern that directly notifies the DRU of RU Allocation information.

[0194] In Examples 2 to 4, the STA2 directly punches holes according to the predefined punching pattern (+offset).

[0195] As shown in Figure 22, in this embodiment, no puncturing pattern is predefined. The AP directly notifies the STA2 of the RU Allocation (including RU size and index information) of the relevant DRU. The STA2 compares its own RRU tone plan with the DRU tone plan to determine the conflicting subcarriers, and adds the protection subcarriers to determine the subcarriers that need to be punctured.

[0196] The signaling design can be shown in Figure 23. The DRU allocation information is the same for each RRU STA, so it can exist as a general information and be identified by AID12 = a special value.

[0197] Alternative signaling design: As shown in Figure 24, the Puncturing tone Flag field is in the User Info field. For RRU resources, Puncturing tone Flag = 1; for DRU, it is Tone Puncturing tone Flag = 0.

[0198] Example 6

[0199] This embodiment involves puncturing DRU subcarriers while maintaining RRU integrity.

[0200] In Examples 1-5, the DRU is intact, and the RRU is punctured with subcarriers. Alternatively, the RRU can remain intact, but the DRU is punctured (with DRU subcarriers overlapping with and adjacent to the RRU). In this case, the number of RRUs needs to be limited, for example, to one or two, to ensure that the DRU has a sufficient number of available subcarriers; for example, as shown in Figure 25.

[0201] The RRU resource information currently allocated to STA2 (such as 26-tone RRU-2) is notified to STA1 using DRU. STA1 will then perform puncturing within the RRU-2 range and adjacent subcarriers, i.e., skip these subcarriers for processing.

[0202] The specific signaling and procedures are similar to those in Examples 2-5, except that the instructions for DRU and RRU are reversed, and the predefined punching pattern is also from the perspective of DRU, which will not be elaborated here.

[0203] Example 7

[0204] This embodiment involves both RRU subcarrier puncturing and DRU subcarrier puncturing, which coexist.

[0205] In Examples 1 to 6, either the DRU remains intact while the RRU undergoes subcarrier puncturing, or the RRU remains intact while the DRU undergoes subcarrier puncturing; there is no situation where both RU types undergo puncturing.

[0206] In this embodiment, as shown in Figure 26, we consider a scenario where drilling occurs simultaneously, with 3 STAs as shown below.

[0207] Step 1. First, the AP side indicates the PPDU bandwidth, the RU resource allocation for STA1 to STA3, and the corresponding RU type identifier in the basic trigger frame according to the above method.

[0208] STA1: RU Allocation: 26-tone RU-8; RU type identifier: DRU; Drill indication: Drill; Drill related information: related to 26-tone RRU-3 (STA2), for details please refer to Examples 1-6, which will not be repeated here.

[0209] STA2: RU Allocation: 26-tone RU-3; RU type identifier: RRU; Drill indication: No drilling.

[0210] STA3: RU Allocation: 26-tone RU-2; RU Type Identifier: RRU; Punch Indicator: Punch; Punch Related Information: Related to 26-tone

[0211] For details regarding DRU-8 (STA1), please refer to Examples 1-5, which will not be repeated here.

[0212] Step 1. After receiving the PPDU, STA1 determines the allocated RU information (i.e., 26-tone DRU-8). STA1 configures the RU for the data field in the UL PPDU according to the indicated RU information (26-tone DRU-8), and punches the relevant sub-channels according to the received sub-channel punching information, and sends the uplink PPDU.

[0213] Step 2. After receiving the PPDU, STA3 determines the assigned RU information (i.e., 26-tone RRU-3). STA2 configures the RU for the data field in the UL PPDU according to the indicated RU information (26-tone RRU-3) and sends the uplink PPDU.

[0214] Step 3. After receiving the PPDU, STA2 determines the allocated RU information (i.e., 26-tone RRU-2) and the subcarrier puncturing information; STA2 configures the RU for the data field in the UL PPDU according to the indicated RU information (26-tone RRU-2), and punctures the relevant sub-channels according to the received sub-channel puncturing information, and sends the uplink PPDU.

[0215] Step 4. After receiving the PPDU from STA1 / 2 / 3, the AP sends an ACK / BA to acknowledge receipt. When decoding the UL Data from STA1 / 3, the AP must also skip the punctured subcarriers.

[0216] 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 disclosure, 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 disclosure.

[0217] Embodiments of this disclosure also provide a computer-readable storage medium storing a computer program configured to perform the steps in any of the above method embodiments when executed.

[0218] 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.

[0219] Embodiments of this disclosure also provide an electronic device 400, as shown in FIG27. The electronic device 400 may include a memory 401 and a processor 402. The memory 401 stores a computer program, and the processor 402 is configured to run the computer program to perform the steps in any of the above method embodiments.

[0220] 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.

[0221] 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.

[0222] It is obvious to those skilled in the art that the modules or steps of this disclosure 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 herein, 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 disclosure is not limited to any particular combination of hardware and software.

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

Claims

1. A data transmission method, applied to an access point device, comprising: Configure resource units for multiple non-access point devices, wherein the resource units include a first type of resource unit and a second type of resource unit; A trigger frame is sent to the plurality of non-access point devices, wherein the trigger frame is used to indicate the configured resource elements to the plurality of non-access point devices and to instruct a target non-access point device among the plurality of non-access point devices to puncture overlapping subcarriers so that the target non-access point device can transmit data on unpunctured subcarriers; wherein the target non-access point device is the non-access point device that needs to puncture the overlapping subcarriers; the overlapping subcarriers are the same subcarriers configured in the frequency domain by some or all of the plurality of non-access point devices.

2. The method according to claim 1, wherein, The first type of resource unit is a continuous resource unit, and the second type of resource unit is a distributed resource unit.

3. The method according to claim 2, wherein, Configure resource units for multiple non-access point devices, including one of the following: For any one of the plurality of non-access point devices, configure a continuous resource unit for that non-access point device; For any one of the plurality of non-access point devices, configure a distributed resource unit for that non-access point device; For any one of the plurality of non-access point devices, configure a continuous resource unit and a distributed resource unit for that non-access point device.

4. The method according to claim 1, wherein, Sending trigger frames to the plurality of non-access point devices includes: A trigger frame is sent to the plurality of non-access point devices to trigger uplink orthogonal frequency division multiple access transmission of the plurality of non-access point devices, so as to instruct the plurality of non-access point devices to configure the resource unit through the trigger frame; wherein, the trigger frame includes a user information list field, and the user list field includes a resource unit allocation field.

5. The method according to claim 4, wherein, The trigger frame also carries a resource unit type identifier and a physical layer data unit bandwidth identifier. The resource unit type identifier is used to indicate that the resource unit configured on the non-access point device is a first resource unit and / or a second resource unit, and the physical layer data unit bandwidth is used to indicate the physical layer data unit bandwidth configured on the non-access point device.

6. The method according to claim 4, wherein, The trigger frame also carries a punch mark and a punch pattern mark, wherein the punch pattern mark is used to indicate that the target non-access point device needs to punch overlapping subcarriers, and the punch pattern mark is used to indicate that the target non-access point device determines the overlapping subcarriers.

7. The method according to claim 6, wherein, Before sending the trigger frame to the plurality of non-access point devices, the method further includes: For all subcarrier punching scenarios, multiple punching patterns are predefined; wherein, the punching pattern corresponds to the punching pattern identifier.

8. The method according to claim 6, wherein, The trigger frame also carries a punching identifier, a target resource unit identifier, and an index of the target resource unit; wherein, the target resource unit is a resource unit allocated to the target non-access point device, the punching identifier is used to indicate that the target non-access point device needs to punch overlapping subcarriers, and the index of the target resource unit is used to indicate that the target non-access point device punches overlapping subcarriers in combination with a predefined first baseline punching pattern.

9. The method according to claim 8, wherein, The first baseline punch pattern includes multiple patterns, and each first baseline punch pattern corresponds to one physical layer data unit bandwidth, and each physical layer data unit bandwidth corresponds to one non-access point device.

10. The method according to claim 6, wherein, The trigger frame also carries a punching identifier, a second baseline punching pattern identifier, and a target resource element index; wherein, the punching identifier is used to indicate that the target non-access point device needs to punch overlapping subcarriers, and the target resource element index is used to indicate that the target non-access point device punches overlapping subcarriers in combination with the second baseline punching pattern corresponding to the second baseline punching pattern identifier.

11. The method according to claim 10, wherein, Each type of first-type resource or type of second-type resource of different sizes under a physical layer data unit bandwidth corresponds to a second baseline punch pattern, and a second baseline punch pattern corresponds to a second baseline punch pattern identifier. The different physical layer data unit bandwidths correspond to different non-access point devices.

12. The method according to claim 6, wherein, The trigger frame also carries information about resource units allocated by other non-access point devices, wherein the other non-access point devices are non-access point devices other than the target non-access point device among the plurality of non-access point devices, and the information of the resource units includes the identification information and the index information of the resource units.

13. The method according to claim 1, wherein, The trigger frame includes a user information field and a public information field. The user information field carries a punch mark, and the public information field carries at least one of the following: a resource unit type identifier, a physical layer data unit bandwidth identifier, and a punch mark pattern identifier.

14. The method according to claim 1, wherein, After sending trigger frames to the plurality of non-access point devices, the method further includes: The data corresponding to the un-punched subcarrier is encoded according to the trigger frame, and the encoded data is transmitted to the non-access point device.

15. A data transmission method applied to a non-access point device, comprising: Configure resource units according to the received trigger frame, wherein the trigger frame is used to instruct the access point device to configure resource units for multiple non-access point devices, and the resource units include a first type of resource unit and a second type of resource unit; When the non-access point device is the target access point device, the overlapping subcarriers are punctured according to the trigger frame, and data is transmitted on the unpunctured subcarriers; wherein, the overlapping subcarriers are the same subcarriers configured in the frequency domain for some or all of the plurality of non-access point devices.

16. The method according to claim 15, wherein, The first type of resource unit is a continuous resource unit, and the second type of resource unit is a distributed resource unit.

17. The method according to claim 15, wherein, The trigger frame includes a user-specific field and a public information field. The user-specific field carries at least a resource unit type identifier and a punch identifier. The public information field carries at least one of the following: a resource unit type identifier, a physical layer data unit bandwidth identifier, and a punch pattern identifier.

18. The method according to claim 15, wherein, Configure resource units according to the received trigger frame, including: Configure resource units according to the resource unit type identifier and physical layer data unit bandwidth identifier carried in the trigger frame, wherein the resource unit type identifier is used to indicate that the resource unit configured on the non-access point device is a first resource unit and / or a second resource unit, and the physical layer data unit bandwidth is used to indicate the physical layer data unit bandwidth configured on the non-access point device.

19. The method according to claim 15 or 18, wherein, When the non-access point device is the target access point device, puncturing the overlapping subcarriers according to the trigger frame includes: The overlapping subcarriers are punched according to the punching identifier and punching pattern identifier carried in the trigger frame, wherein the punching pattern identifier is used to indicate that the target non-access point device needs to punch the overlapping subcarriers, and the punching pattern identifier is used to indicate that the target non-access point device determines the overlapping subcarriers.

20. The method according to claim 15 or 18, wherein, When the non-access point device is the target access point device, puncturing the overlapping subcarriers according to the trigger frame includes: The overlapping subcarriers are perforated according to the perforation identifier, target resource unit identifier, and target resource unit index carried in the trigger frame; wherein, the target resource unit is a resource unit allocated to the target non-access point device, the perforation identifier is used to indicate that the target non-access point device needs to perforate the overlapping subcarriers, and the target resource unit index is used to indicate that the target non-access point device perforates the overlapping subcarriers in conjunction with a predefined first baseline perforation pattern.

21. The method according to claim 20, wherein, The first baseline punch pattern includes multiple patterns, and each first baseline punch pattern corresponds to one physical layer data unit bandwidth, and each physical layer data unit bandwidth corresponds to one non-access point device.

22. The method according to claim 15 or 18, wherein, When the non-access point device is the target access point device, puncturing the overlapping subcarriers according to the trigger frame includes: The overlapping subcarriers are perforated according to the perforation identifier, the identifier of the second baseline perforation pattern, and the index of the target resource unit carried in the trigger frame; wherein, the perforation identifier is used to indicate that the target non-access point device needs to perforate the overlapping subcarriers, and the index of the target resource unit is used to indicate that the target non-access point device perforates the overlapping subcarriers in combination with the second baseline perforation pattern corresponding to the identifier of the second baseline perforation pattern.

23. The method according to claim 22, wherein, Each type of first-type resource or type of second-type resource of different sizes under a physical layer data unit bandwidth corresponds to a second baseline punch pattern, and a second baseline punch pattern corresponds to a second baseline punch pattern identifier. The different physical layer data unit bandwidths correspond to different non-access point devices.

24. The method according to claim 15 or 18, wherein, When the non-access point device is the target access point device, puncturing the overlapping subcarriers according to the trigger frame includes: The overlapping subcarriers are perforated according to the information of resource units allocated by other non-access point devices carried in the trigger frame, wherein the other non-access point devices are non-access point devices other than the target non-access point device among the plurality of non-access point devices, and the information of the resource unit includes the identification information and the index information of the resource unit.

25. The method according to claim 15, wherein, Data transmission on un-punctured subcarriers includes: The system receives encoded data from the access point device and decodes the data in the encoded data corresponding to the un-punctured subcarriers based on the un-punctured subcarriers.

26. A computer-readable storage medium storing a computer program, wherein, When the computer program is executed by a processor, it implements the steps of the method described in any one of claims 1 to 14, or the steps of the method described in any one of claims 15 to 24.

27. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor, when executing the computer program, implements the steps of the method according to any one of claims 1 to 14, or implements the steps of the method according to any one of claims 15 to 24.

28. A computer program product comprising a computer program that, when executed by a processor, implements the steps of the method according to any one of claims 1 to 14, or implements the steps of the method according to any one of claims 15 to 24.

Images