RU2831355C1 - Method and device for transmitting data, microchips system and machine-readable data medium - Google Patents

Abstract

FIELD: wireless communication.

SUBSTANCE: method comprises: receiving a physical layer data unit (PPDU), where the PPDU contains a signaling field and the signaling field contains preamble puncturing indicator information, wherein preamble puncturing indicator information comprises one or more indicators, wherein one indicator corresponds to one piece of preamble puncturing information and the preamble puncturing information contains the size and location of the preamble puncturing or there is no preamble puncturing; in which the signaling field further comprises a bandwidth field, and the bandwidth field contains bandwidth indicator information for indicating the bandwidth of the data packet; where in case the data packet bandwidth is equal to 160 MHz bandwidth, the preamble puncturing indicator information contains the first indicator and the second indicator, where the first indicator indicates the preamble puncturing information in the sub-channel with the lowest frequency of 80 MHz in 160 MHz band; and the second indicator indicates the preamble puncturing information in the sub-channel with the highest frequency of 80 MHz in 160 MHz band; sending or receiving a data packet based on preamble puncturing indicator information.

EFFECT: reduction of service signaling.

35 cl, 29 dwg, 11 tbl

Description

Cross reference to related application

This application claims priority to Chinese Patent Application No. 202010172790.7, filed with the National Intellectual Property Administration of China on March 12, 2020, entitled “DATA TRANSMISSION METHOD AND DEVICE, CHIP SYSTEM, AND COMPUTER-READABLE STORAGE MEDIUM,” which is incorporated herein by reference in its entirety.

Field of technology to which the invention relates

The present application relates generally to the field of communication technologies and, in particular, to a method and device for transmitting data, a microcircuit system and a machine-readable storage medium.

State of the art

With the development of wireless local area network (WLAN), orthogonal frequency division multiple access (OFDMA) technology was first introduced, and the entire bandwidth was divided into multiple resource units (RUs). In other words, the user bandwidth resource is allocated by resource unit rather than channel. For example, a 20 MHz channel may include multiple RUs, which may be 26-tone RU, 52-tone RU, and 106-tone RU. The tone indicates the number of subcarriers. In addition, RUs may also be 242-tone RU, 484-tone RU, 996-tone RU, etc.

Preamble puncture can also be referred to as preamble puncturing. For example, if a portion of 20 MHz channels in the entire bandwidth is zero, it can be understood as a puncture when puncturing 20 MHz in the entire bandwidth. For OFDMA transmission, the discrete resources caused by puncturing can be allocated to different stations. For non-OFDMA transmission such as orthogonal frequency division multiplexing (OFDM) transmission, if preamble puncturing is used, the remaining resources that are not punctured also form a set of RUs, which are aggregated as a whole and allocated to one station (STA) or one group of stations.

However, how to specify the set of RUs for data transmission becomes a pressing issue that needs to be addressed.

The essence of the invention

Embodiments of the present application provide a data transmission method, a data transmission device, a chip system, and a machine-readable storage medium for transmitting a data packet based on preamble puncturing information.

According to a first aspect, the present application discloses a method for transmitting data. In the method, a station can receive preamble puncturing indicator information and send or receive a data packet based on the preamble puncturing indicator information. The preamble puncturing indicator information includes one or more indicators, one indicator corresponds to one piece of preamble puncturing information, and the preamble puncturing information includes a size and a location of the preamble puncturing or no preamble puncturing. The indicator can be an index corresponding to the preamble puncturing indicator information to know the preamble puncturing status of the data packet.

It can be learned that in this application, the station obtains the preamble puncturing status of the data packet based on the preamble puncturing indicator information to learn about the allocated multiple resource block. Compared with the existing method of directly indicating the multiple resource block, the method of indicating the preamble puncturing status in this application can reduce the signaling overhead.

In a further implementation, sending or receiving a data packet based on the preamble puncturing indicator information includes: if the preamble puncturing indicator information indicates no preamble puncturing, sending or receiving a data packet in the bandwidth of the data packet; or if the preamble puncturing indicator information indicates a size and location of the preamble puncturing, sending or receiving a data packet in a resource block in the bandwidth of the data packet different from the size and location of the preamble puncturing. It can be learned that when a preamble puncturing is present in a data packet, the method of indicating the size and location of the preamble puncturing can reduce the amount of indication signaling compared to the method of directly indicating discrete resource blocks obtained by puncturing the preamble.

For the preamble puncturing indicator information, the present application further provides several additional indication methods for indicating the preamble puncturing information. These methods are separately described below.

In a further implementation, the preamble puncturing indicator information includes one or more pointers, and one pointer corresponds to one piece of preamble puncturing information, or one pointer corresponds to a preamble puncturing status index.

In an additional implementation, the pointer specifies one or more pieces of the following preamble puncturing information in a 160 MHz channel:

20 MHz subchannel in 160 MHz channel;

a 40 MHz subchannel formed by any two 20 MHz subchannels in a 160 MHz channel;

a 60 MHz subchannel formed by any three 20 MHz subchannels in a 160 MHz channel;

an 80 MHz subchannel formed by any four 20 MHz subchannels in a 160 MHz channel; or

in the 160 MHz channel there is no preamble puncturing.

In another additional implementation, the pointer specifies one or more pieces of the following preamble puncturing information in a 160 MHz channel:

20 MHz subchannel in 160 MHz channel;

a 40 MHz subchannel formed by any two adjacent 20 MHz subchannels in a 160 MHz channel;

a 60 MHz subchannel formed by any three adjacent 20 MHz subchannels in a 160 MHz channel;

an 80 MHz subchannel formed by any four adjacent 20 MHz subchannels in a 160 MHz channel; or

in the 160 MHz channel there is no preamble puncturing.

In yet another additional implementation, the 160 MHz channel includes an 80 MHz subchannel with the highest frequency and an 80 MHz subchannel with the lowest frequency, and the indicator specifies one or more pieces of the following preamble puncturing information in the 160 MHz channel:

20 MHz subchannel in 160 MHz channel;

a 40 MHz subchannel formed by two subchannels with the lowest frequency of 20 MHz in a subchannel with the lowest frequency of 80 MHz;

a 40 MHz subchannel formed by two subchannels with the highest frequency of 20 MHz in a subchannel with the lowest frequency of 80 MHz;

a 40 MHz subchannel formed by two subchannels with the lowest frequency of 20 MHz in a subchannel with the highest frequency of 80 MHz;

a 40 MHz subchannel formed by two subchannels with the highest frequency of 20 MHz in a subchannel with the highest frequency of 80 MHz;

subchannel with the lowest frequency of 80 MHz;

the subchannel with the highest frequency of 80 MHz; or

in the 160 MHz channel, there is no preamble puncturing. In this implementation, the size and location of the preamble puncturing may correspond to the resource block obtained by dividing the channels, so that the allocated resource block is determined based on the preamble puncturing indicator information.

The 160 MHz channel includes an 80 MHz subchannel with the highest frequency and an 80 MHz subchannel with the lowest frequency. If necessary, the indicator can additionally indicate that the following preamble puncturing information or another index is reserved: a subchannel with a center frequency of 40 MHz in the subchannel with the highest frequency of 80 MHz or a subchannel with a center frequency of 40 MHz in the subchannel with the lowest frequency of 80 MHz. It can be noted that this implementation supports the case in which the same index corresponds to different values, so that different index tables can be used based on different cases, such as different locations of bandwidths or pointers in the preamble puncturing indicator information. This reduces the number of required indices, that is, reduces the number of bits to indicate.

If necessary, the pointer indicates indices corresponding to one or more pieces of preamble puncturing information in the 160 MHz channel, respectively. This allows the station to determine the preamble puncturing status of the data packet based on the preamble puncturing pointer information.

The bandwidth of the data packet is 320 MHz. The preamble puncturing indicator information includes a first indicator and a second indicator. The first indicator indicates the preamble puncturing information in the subchannel with the lowest frequency of 160 MHz in the bandwidth of 320 MHz; and the second indicator indicates the preamble puncturing information in the subchannel with the highest frequency of 160 MHz in the bandwidth of 320 MHz.

The bandwidth of the data packet is 160 MHz. The preamble puncturing indicator information includes the first indicator. The first indicator indicates the preamble puncturing information in the bandwidth of 160 MHz.

If necessary, the pointer in the preamble puncturing pointer information specifies one or more pieces of the following preamble puncturing information in the 80 MHz channel:

20 MHz subchannel in 80 MHz channel;

a 40 MHz subchannel formed by any two 20 MHz subchannels in an 80 MHz channel;

a 60 MHz subchannel formed by any three 20 MHz subchannels in an 80 MHz channel; or

in the 80 MHz channel there is no preamble puncturing.

If necessary, the pointer in the preamble puncturing pointer information specifies one or more pieces of the following preamble puncturing information in the 80 MHz channel:

20 MHz subchannel in 80 MHz channel;

a 40 MHz subchannel formed by any two adjacent 20 MHz subchannels in an 80 MHz channel;

a 60 MHz subchannel formed by any three adjacent 20 MHz subchannels in an 80 MHz channel; or

in the 80 MHz channel there is no preamble puncturing.

If necessary, the pointer in the preamble puncturing pointer information specifies one or more pieces of the following preamble puncturing information in the 80 MHz channel:

20 MHz subchannel in 80 MHz channel;

40 MHz subchannel with the lowest frequency in the 80 MHz channel;

subchannel with an average frequency of 40 MHz in a channel of 80 MHz;

40 MHz subchannel with the highest frequency in the 80 MHz channel;

80 MHz channel; or

in the 80 MHz channel there is no preamble puncturing.

In other words, the pointer in the preamble puncturing pointer information indicates indices corresponding to one or more pieces of preamble puncturing information in the 80 MHz channel, respectively.

If necessary, the data packet bandwidth is 240 MHz. The preamble puncturing indicator information includes a first indicator and a second indicator. The first indicator indicates preamble puncturing information in the subchannel with the lowest frequency of 160 MHz in the bandwidth of 240 MHz; and the second indicator indicates preamble puncturing information in the subchannel with the highest frequency of 80 MHz in the bandwidth of 240 MHz.

If necessary, the bandwidth of the data packet is 240 MHz. The preamble puncturing indicator information includes a first indicator and a second indicator. The first indicator indicates the preamble puncturing information in the subchannel with the lowest frequency of 80 MHz in the bandwidth of 240 MHz; and the second indicator indicates the preamble puncturing information in the subchannel with the highest frequency of 160 MHz in the bandwidth of 240 MHz.

If necessary, the bandwidth of the data packet is 240 MHz. Based on the preamble puncturing information in the 80 MHz channel, the preamble puncturing indicator information includes a first indicator, a second indicator and a third indicator. The first indicator indicates the preamble puncturing information in the subchannel with the lowest frequency of 80 MHz in the 240 MHz bandwidth. The second indicator indicates the preamble puncturing information in the subchannel with the middle frequency of 80 MHz in the 240 MHz bandwidth. The third indicator indicates the preamble puncturing information in the subchannel with the highest frequency of 80 MHz in the 240 MHz bandwidth. It can be learned that the indicator included in the preamble puncturing indicator information is associated with the bandwidth of the data packet and the frequency range of the preamble puncturing information, which can be indicated by the indicator.

If necessary, the bandwidth of the data packet is 320 MHz. Based on the preamble puncturing information in the 80 MHz channel, the preamble puncturing indicator information includes the first indicator, the second indicator, the third indicator, and the fourth indicator. One indicator may correspond to one piece of preamble puncturing information in the 80 MHz subchannel. For example, the 320 MHz bandwidth includes the subchannel with the lowest frequency of 160 MHz and the subchannel with the highest frequency of 160 MHz. The first indicator indicates the preamble puncturing information in the subchannel with the lowest frequency of 80 MHz in the subchannel with the lowest frequency of 160 MHz. The second indicator indicates the preamble puncturing information in the subchannel with the highest frequency of 80 MHz in the subchannel with the lowest frequency of 160 MHz. The third indicator indicates the preamble puncturing information in the subchannel with the lowest frequency of 80 MHz in the subchannel with the highest frequency of 160 MHz. The fourth indicator indicates the preamble puncturing information in the subchannel with the highest frequency of 80 MHz in the subchannel with the highest frequency of 160 MHz. It can be learned that the number of indicators included in the preamble puncturing indicator information may be related to the bandwidth of the data packet and the frequency range of the preamble puncturing information that can be indicated by the indicator. For example, if one of the indicators indicates the preamble puncturing indicator information in the subchannel of 160 MHz, and the bandwidth of the data packet is 320 MHz, the preamble puncturing indicator information may include a maximum of two such indicators.

If necessary, the bandwidth of the data packet is 160 MHz. The preamble puncturing indicator information includes a first indicator and a second indicator. The first indicator indicates the preamble puncturing information in the subchannel with the lowest frequency of 80 MHz in the bandwidth of 160 MHz; and the second indicator indicates the preamble puncturing information in the subchannel with the highest frequency of 80 MHz in the bandwidth of 160 MHz.

If necessary, the bandwidth of the data packet is 160 MHz. The preamble puncturing indicator information includes a first indicator and a second indicator. The first indicator indicates the preamble puncturing information of the first puncture in the bandwidth of 160 MHz; and the second indicator indicates the preamble puncturing information of the second puncture in the bandwidth of 160 MHz. It can be learned that the present application supports the case where the data packet has one or two punctures.

In another additional implementation, the pointer may indicate each index for each additional preamble puncturing status in the passband. In other words, each additional preamble puncturing status in the passband is in the index table of the preamble puncturing pointer information. This reduces the complexity of parsing the preamble puncturing information by the station based on the index table.

In yet another additional implementation, the preamble puncturing indicator information includes a first indicator and a second indicator. The first indicator indicates the size of the preamble puncturing, and the second indicator indicates the location of the preamble puncturing.

If necessary, the preamble puncture size specified by the first designator includes one or more of the following: 20 MHz, 40 MHz, 60 MHz, or 80 MHz.

If necessary, the preamble puncturing size indicated by the first designator is 20 MHz, and the preamble puncturing location includes one or more of the following: a 20 MHz subchannel in the data packet bandwidth.

The preamble puncturing size indicated by the first designator is 40 MHz, and the preamble puncturing location includes one or more of the following: a 40 MHz subchannel formed by any two 20 MHz subchannels in the data packet bandwidth.

The preamble puncturing size indicated by the first designator is 60 MHz, and the preamble puncturing location includes one or more of the following: a 60 MHz subchannel formed by any three 20 MHz subchannels in the data packet bandwidth.

The preamble puncturing size indicated by the first designator is 80 MHz, and the preamble puncturing location includes one or more of the following: an 80 MHz subchannel formed by any four 20 MHz subchannels in the data packet bandwidth.

If necessary, the preamble puncturing size indicated by the first designator is 20 MHz, and the preamble puncturing location includes one or more of the following: a 20 MHz subchannel in the data packet bandwidth.

The preamble puncturing size indicated by the first designator is 40 MHz, and the preamble puncturing location includes one or more of the following: a 40 MHz subchannel formed by any two adjacent 20 MHz subchannels in the data packet bandwidth.

The preamble puncturing size indicated by the first designator is 60 MHz, and the preamble puncturing location includes one or more of the following: a 60 MHz subchannel formed by any three adjacent 20 MHz subchannels in the data packet bandwidth;

The preamble puncturing size indicated by the first designator is 80 MHz, and the preamble puncturing location includes one or more of the following: an 80 MHz subchannel formed by any four adjacent 20 MHz subchannels in the data packet bandwidth.

It can be learned that different sizes of preamble puncturing correspond to different options of preamble puncturing locations. Thus, after determining the size of preamble puncturing based on the first pointer, the station can determine the location of preamble puncturing based on the index table of the location corresponding to the puncturing.

If necessary, the first indicator or the second indicator additionally indicates that there is no preamble piercing.

The data transmission execution mode based on preamble puncturing indicator information described in this application may be applicable to non-OFDMA transmission, and the data transmission execution mode based on the resource block allocation subfield may be applicable to OFDMA transmission.

In other words, the station performs the step of sending or receiving the data packet based on the preamble puncturing indicator information when the data packet is transmitted in the non-OFDMA mode. The station sends or receives the data packet based on the resource allocation subfield when the data packet is transmitted in the orthogonal frequency division multiple access (OFDMA) mode.

If necessary, the index table of the preamble puncturing indicator information and the index table of the resource block allocation subfield can be combined into one index table, and the preamble puncturing indicator information can reuse the resource block allocation subfield. This allows the station to determine the transmission mode of the data packet and the preamble puncturing status based on the index indicated by the preamble puncturing indicator information.

If necessary, the station can receive the transmission mode indicator information. The transmission mode indicator information indicates the transmission mode of the data packet. The transmission mode indicator information can be in the general signaling field or in the general field in the trigger frame.

In the case where the data transfer is performed based on the resource block allocation subfield, in an additional implementation, the resource block allocation subfield includes a resource block pointer and a resource block aggregation pointer.

If necessary, when the first resource block indicated by the resource block indicator is a 2x996-tone resource block, the resource block aggregation indicator indicates one or more of the following resource block aggregations: no resource block is aggregated with the first resource block; the second resource block is aggregated with the first resource block, where the second resource block is a 484-tone resource block adjacent to the first resource block or not adjacent to it; the third resource block is aggregated with the first resource block, where the third resource block is a 484-tone resource block adjacent to the first resource block with a low frequency, or a 484-tone resource block, with the first resource block with a high frequency; or the second resource block and the third resource block are aggregated with the first resource block.

If necessary, when the first resource block indicated by the resource block indicator is a 996-tone resource block, the resource block aggregation indicator indicates one or more of the following resource block aggregations: no resource block is aggregated with the first resource block; or a second resource block is aggregated with the first resource block, where the second resource block is a 484-tone resource block, adjacent to or non-adjacent to the first resource block;

According to a second aspect, the present application further provides a data transmission device. The data transmission device has part or all of the functions of the implementation of the station in the example method in the first aspect. For example, the data transmission device may have the function of part or all of the embodiments of the present application or may have the function of independently implementing any embodiment of the present application. The function may be implemented by hardware or may be implemented by hardware executing corresponding software. The hardware or software includes one or more blocks or modules corresponding to the function.

In a possible embodiment, the structure of the data transmission device may include a processing unit and a communication unit. The processing unit is configured to support the data transmission device when performing the corresponding function in the previous method. The communication unit is configured to support communication between the data transmission device and another device. The data transmission device may additionally include a storage unit. The storage unit is configured to be connected to the processing unit and the communication unit, and the storage unit stores program instructions and data that are necessary for the device to transmit data.

In the implementation, the data transmission device includes:

a communication unit configured to receive preamble puncturing indicator information, where the preamble puncturing indicator information includes one or more indicators, one indicator corresponds to one piece of preamble puncturing information, and the preamble puncturing information includes a size and a location of the preamble puncturing, or there is no preamble puncturing.

The communication unit is further configured to send or receive a data packet based on the preamble puncturing indicator information.

If necessary, the data transmission device additionally includes a processing unit. The processing unit is configured to determine a plurality of allocated resource blocks based on the information of the preamble puncturing indicator.

For example, the processing unit may be a processor, the communication unit may be a transceiver or communication interface, and the storage unit may be a memory.

In the implementation, the data transmission device includes:

a transceiver configured to receive preamble puncturing indicator information, where the preamble puncturing indicator information includes one or more indicators, one indicator corresponds to one piece of preamble puncturing information, and the preamble puncturing information includes a size and a location of the preamble puncturing, or there is no preamble puncturing.

The transceiver is further configured to send or receive a data packet based on the preamble puncturing indicator information.

If necessary, the data transmission device additionally includes a processor. The processor is configured to determine a plurality of allocated resource blocks based on the information of the preamble puncturing indicator.

In a specific implementation process, the processor may be configured to perform, for example, but not limited to, baseband processing, and the transceiver may be configured to perform, for example, but not limited to, radio frequency sending and receiving. The above-mentioned components may be located separately on chips that are independent of each other, or at least some or all of the components may be located on the same chip. For example, the processor may be further divided into an analog baseband processor and a digital baseband processor. The analog baseband processor and the transceiver may be integrated into a single chip, and the digital baseband processor may be on an independent chip. Due to the constant development of integrated circuit technologies, more components may be integrated on the same chip. For example, a digital baseband processor may be integrated on a single chip with a plurality of application processors (for example, without limitation, with a graphics processor and a multimedia processor). The chip may be called a system on chip. Whether all components are located separately on different chips or combined and located on one or more chips usually depends on the specific requirements for the design of the product. The specific form of implementation of the above-mentioned components is not limited in this embodiment of the present invention.

According to a third aspect, the present application further provides a processor configured to perform the methods in the first aspect. In the process of performing these methods, the process of sending information and the process of receiving information in the methods can be understood as a process of outputting information by the processor and a process of receiving input information by the processor. In particular, when outputting information, the processor outputs information to the transceiver so that the transceiver transmits the information. Moreover, after the information is output by the processor, other processing may need to be performed before the information is received by the transceiver. Similarly, when the processor receives input information, the transceiver receives the information and inputs the information to the processor. In addition, after the transceiver receives the information, other processing may need to be performed on the information before the information is input to the processor.

Based on the above principle, for example, receiving the preamble puncturing indicator information mentioned in the above method can be regarded as inputting the preamble puncturing indicator information by the processor. In another example, sending a data packet can be regarded as outputting a data packet by the processor.

In this case, for operations such as transmitting, sending, and receiving that are related to the processor, unless there is a specific statement or unless the operations are inconsistent with the actual function or internal logic of the operations in the relevant descriptions, the operations can be more generally considered to be operations such as outputting, receiving, and inputting with respect to the processor, rather than operations such as transmitting, sending, and receiving directly performed by the RF circuit and antenna.

In a particular implementation process, the processor may be a processor specially configured to perform these methods, or a processor, such as a general-purpose processor, that executes computer instructions in a memory to perform these methods. The memory may be non-volatile memory, such as read-only memory (ROM). The memory and the processor may be integrated into the same chip or may be located separately on different chips. The type of memory and the arrangement of the memory and the processor are not limited in embodiments of the present invention.

According to a fourth aspect, an embodiment of the present invention provides a computer-readable storage medium configured to store computer software instructions used by the above-mentioned device for transmitting data. The computer-readable storage medium includes a program used to perform the first aspect of the above-mentioned method.

According to a fifth aspect, the present application further provides a computer program product including instructions. When the computer program product is run on a computer, the computer is capable of executing the method in the first aspect.

According to a sixth aspect, the present application provides a microcircuit system. The microcircuit system includes a processor and an interface and is configured to support a device for transmitting data when implementing the functions in the first aspect, for example at least one of the functions of determining or processing data and information related to the method. In a possible embodiment, the microcircuit system additionally includes a memory, and the memory is configured to store program instructions and data that are necessary for the station. The microcircuit system may include a microcircuit or may include a microcircuit and another discrete component.

Brief description of the drawings

Fig. 1 is a schematic diagram illustrating the structure of a network according to an embodiment of the present application;

Fig. 2 is a schematic algorithm for sending a data packet based on a trigger frame according to an embodiment of the present application;

Fig. 3 is another schematic algorithm for sending a data packet based on a trigger frame according to an embodiment of the present application;

Fig. 4 is a schematic representation of the structure of a trigger frame according to an embodiment of the present application;

Fig. 5 is a schematic diagram illustrating the structure of a highly efficient signal field according to an embodiment of the present application;

Fig. 6 is a schematic diagram illustrating the structure of a non-trigger based data packet according to an embodiment of the present application;

Fig. 7 is a schematic representation of channel distribution according to an embodiment of the present application;

Fig. 8 is a schematic representation of the allocation of resource blocks according to an embodiment of the present application;

Fig. 9 is a flow chart of the sequence of operations of the data transmission method according to an embodiment of the present application;

Fig. 10 is a schematic diagram illustrating the structure of a trigger frame according to an embodiment of the present application;

Fig. 11 is a schematic diagram illustrating the structure of another non-trigger based data packet according to an embodiment of the present application;

Fig. 12 is a flow chart of another method for transmitting data according to an embodiment of the present application;

Fig. 13 is a schematic diagram illustrating the structure of a multi-content channel according to an embodiment of the present application;

Fig. 14 is a schematic representation of preamble puncturing information corresponding to the indices in Table 3, according to an embodiment of the present application;

Fig. 15 is another schematic representation of preamble puncturing information corresponding to the indices in Table 3, according to an embodiment of the present application;

Fig. 16 is a schematic representation of the location and size of the preamble puncture according to an embodiment of the present application;

Fig. 17 is a schematic representation of another location and size of a preamble perforation according to an embodiment of the present application;

Fig. 18 is a schematic representation of another location and size of a preamble puncturing according to an embodiment of the present application;

Fig. 19 is a schematic representation of another location and size of a preamble puncturing according to an embodiment of the present application;

Fig. 20 is a schematic representation of another location and size of a preamble puncturing according to an embodiment of the present application;

Fig. 21 is a schematic representation of an additional location and size of a preamble puncturing according to an embodiment of the present application;

Fig. 22 is a schematic representation of preamble puncturing information corresponding to the indices in Table 4, according to an embodiment of the present application;

Fig. 23 is another schematic representation of preamble puncturing information corresponding to the indices in Table 4, according to an embodiment of the present application;

Fig. 24 is a schematic representation of another location and size of a preamble puncturing according to an embodiment of the present application;

Fig. 25 is a schematic representation of another location and size of a preamble puncturing according to an embodiment of the present application;

Fig. 26 is a schematic representation of another location and size of a preamble puncturing according to an embodiment of the present application;

Fig. 27 is a schematic diagram illustrating the structure of a data transmission device according to an embodiment of the present application;

Fig. 28 is a schematic diagram illustrating the structure of a data transmission device according to an embodiment of the present application; and

Fig. 29 is a schematic diagram illustrating the structure of a microcircuit according to an embodiment of the present application.

Detailed description of the invention

The following is a detailed description of specific embodiments of the present application with reference to the accompanying drawings.

Fig. 1 is used as an example to describe a network structure to which the data transmission method in the present application is applicable. Fig. 1 is a schematic diagram illustrating a network structure according to an embodiment of the present application. The network structure may include one or more stations with access points (AP) and one or more stations without access points (non-AP STA). For ease of description, in this specification, a station with an access point is called an access point (AP), and a station without an access point is called a station (STA). Fig. 1 is described using an example in which the network structure includes one AP and two stations (STA 1 and STA 2).

An access point can be an access point used by a terminal device (such as a mobile phone) to access a wired (or wireless) network, and is mainly deployed at home, in a building, and in a park. The typical coverage radius is tens to hundreds of meters. Of course, an access point can also be installed outdoors. An access point is equivalent to a bridge connecting a wired network and a wireless network. The main function of an access point is to connect wireless network clients, and then connect the wireless network to Ethernet. Specifically, an access point can be a terminal device (such as a mobile phone) or a network device (such as a router) with a wireless fidelity (Wi-Fi) chip. An access point can be a device that supports the 802.11be standard. Alternatively, the access point may be a device that supports multiple wireless local area network (WLAN) standards of the 802.11 family, such as 802.11be, 802.11ax, 802.11ac, 802.11n, 802.11g, 802.11b, and 802.11a. In the present application, the access point may be a high efficient (HE) access point or an extremely high throughput (EHT) access point, or may be an access point applicable to the future Wi-Fi standard.

The station may be a wireless communication chip, a wireless sensor, a wireless communication terminal, etc., and may also be referred to as a user. For example, the station may be a mobile phone supporting the Wi-Fi communication function, a tablet computer supporting the Wi-Fi communication function, a set-top box supporting the Wi-Fi communication function, a smart TV supporting the Wi-Fi communication function, an intelligent wearable device supporting the Wi-Fi communication function, a communication device installed on a vehicle supporting the Wi-Fi communication function, or a computer supporting the Wi-Fi communication function. If necessary, the station may support the 802.11be standard. The station can also support multiple 802.11 family wireless local area network (WLAN) standards, such as 802.11be, 802.11ax, 802.11ac, 802.11n, 802.11g, 802.11b, and 802.11a.

The access point in this application may be a high efficiency (HE) STA or an extremely high throughput (EHT) STA, or may be an STA applicable to a future Wi-Fi standard.

For example, the access point and station can be devices used in the Internet of Vehicles, Internet of Things nodes or sensors in the Internet of Things (IoT), smart cameras, smart remote controls and smart water meters in a smart home, and sensors in a smart city.

Although embodiments of the present application are primarily described using a network deployed based on IEEE 802.11 as an example, one skilled in the art may readily appreciate that various aspects of the present application may be extended to other networks using various standards or protocols, such as BLUETOOTH (Bluetooth), high performance radio LAN (HIPERLAN) (a wireless communication standard similar to IEEE 802.11 and primarily used in Europe), a wide area network (WAN), a wireless local area network (WLAN), a personal area network (PAN), or other networks currently known or previously developed. Thus, various aspects presented in the present application are applicable to any suitable wireless network regardless of coverage and wireless access protocol.

The embodiments of the present application are described below, and the embodiments of the present application do not limit the scope of protection and applicability of the claims. A person skilled in the art can adaptively change the functions and deployment of elements in the present application or omit, replace or add various processes or components as needed without departing from the embodiments of the present application.

To facilitate understanding of the related content in the embodiments of the present application, some concepts related to the embodiments of the present application are described below.

1. Data packet

The data transmission method in the present application may be applicable to uplink transmission or may be applicable to downlink transmission. In addition, the data transmission method is also applicable to point-to-point single-user transmission, downlink multi-user transmission, or uplink multi-user transmission. For uplink multi-user transmission, the data transmission method uses a trigger frame-based uplink transmission method. The trigger-based data packet and the trigger-based data packet are separately described below.

1.1 Trigger-based data packet

The data packet may be a high efficient trigger based physical layer protocol data unit (HE TB PPDU). The procedure for sending the TB HE PPDU based on the trigger frame is shown in Fig. 2. After receiving the trigger frame, the station may send the TB HE PPDU based on the trigger frame. As shown in Fig. 2, after receiving the trigger frame, the station may parse, from the trigger frame, a plurality of user fields that correspond to the association identifier of the station to send the TB HE PPDU on a plurality of resource blocks indicated by the resource block allocation subfields in the plurality of user fields. As shown in Fig. 2, from the HE-STF to the Data, the entire bandwidth is divided into one or more resource blocks.

The function of each field in the HE TB PPDU structure shown in Fig. 2 is given in Table 1.

Table 1 Element Description Legacy Short Training Field (L-STF) Performs PPDU detection, coarse synchronization and automatic gain control Legacy Long Training Field (L-LTF) Performs precise synchronization and channel estimation Legacy Signal Field A (L-SIG) Carries signaling information related to PPDU length to ensure coexistence High Efficient Signal Field A (HE-SIGA) Carries signaling used to demodulate subsequent data High Efficient Short Training Field (HE-STF) Performs automatic gain control of the subsequent field High Efficient Long Training Field (HE-LTF) Rates the channel Data Transfer information about data

The data packet may be an Extremely High Throughput trigger based physical layer protocol data unit (EHT TB PPDU), a next generation Wi-Fi trigger based physical layer protocol data unit, etc.

The procedure for sending the TB EHT PPDU based on the trigger frame is shown in Fig. 3. After receiving the trigger frame, the station can send the TB EHT PPDU based on the trigger frame. As shown in Fig. 3, after receiving the trigger frame, the station can parse, from the trigger frame, a plurality of user fields that correspond to the association identifier of the station, to send the TB EHT PPDU on a plurality of resource blocks indicated by the resource block allocation subfields in the plurality of user fields. As shown in Fig. 3, from the EHT-STF to the data, the entire bandwidth is divided into one or more resource blocks. The function of each field in the TB EHT PPDU shown in Fig. 3 is given in Table 2.

Table 2 Element Description Legacy Short Training Field (L-STF) Performs PPDU detection, coarse synchronization and automatic gain control Legacy Long Training Field (L-LTF) Performs precise synchronization and channel estimation Legacy Signal Field A (L-SIG) Carries signaling information related to PPDU length to ensure coexistence Universal Signal Field (U-SIG) Carries signaling used to demodulate subsequent data Extremely High Throughput Short Training Field (EHT-STF) Performs automatic gain control of the subsequent field Extremely High Throughput Long Training Field (EHT-LTF) Rates the channel Data Transfer information about data

The frame format of the trigger frame is shown in Fig. 4. The trigger frame may include only a portion of the fields shown in Fig. 4, or the trigger frame may include more fields than the fields shown in Fig. 4. This case is not limited to this embodiment of the present application.

For example, a trigger frame includes a common info field and a user info list field. A trigger frame may further include a frame control field, a duration field, a receive address (RA) field, a transmit address (TA) field, a padding field, a frame check sequence (FCS) field, etc. The common info field may also be called a common domain, a common information domain, or a common field. The common field includes common information that must be read by all stations, such as the trigger type subfield, the length subfield, the cascade indication subfield, the CS Required subfield, the bandwidth subfield, the GI+LTF subfield, and the trigger dependent common info subfield. The user information list field may also be called the user information list domain, the per-station domain, the per-station field, etc. The user information list field includes one or more user info fields (which may also be called user fields). Each user field includes information that must be read by every station, such as the Association Identifier (AID) subfield, the RU allocation subfield, the coding type subfield, the Modulation and Coding Scheme (MCS) subfield, the reserved subfield, and the trigger dependent user info subfield.

The association identifier field specifies the association identifier of the station corresponding to the user information field. The resource block allocation subfield specifies the resource block (or location of the resource block) that is specified in the user field and allocated to the station. The "field" described in this specification may also be referred to as "domain", "information", etc., and the "subfield" may be referred to as "subdomain", "information", etc.

1.2. PPDU MU HE

The method of allocating resource blocks in the TB HE PPDU is different from the method of indicating the allocation of resource blocks in the MU HE PPDU. In the TB HE PPDU, as shown in Fig. 4, the allocation of resource blocks is indicated in the resource block allocation subfield in each user field in the trigger frame. For example, an 8-bit resource block allocation subfield is required for each user field to indicate the resource block allocated to the user field. However, in the method of indicating the allocation of resource blocks in the MU HE PPDU, the allocation of resource blocks is indicated in the common field of the high efficiency signaling field. For example, the structure of the High Efficient Signal Field B (HE-SIG-B) in the High Efficient multiple user physical layer protocol data unit (HE MU PPDU) is shown in Fig. 5 and is divided into two parts. The first part common field includes 1 to N resource unit allocation subfields, a center-26-tone RU indication field which exists when the bandwidth is 80 MHz or greater, a cyclic redundancy code (CRC) subfield for checking, and a tail subfield for cyclic decoding. The second part user specific field includes 1 to M user fields based on the resource unit allocation sequence. Typically, two of the M user fields form a group. Every two user fields are followed by a CRC field and a tail field. However, the latter group should be excluded. The latter group may have one or two user fields.

In addition to the TB EHT PPDU, the extremely high throughput physical layer protocol data unit (EHT PPDU) further includes a non-trigger-based extremely high throughput physical layer protocol data unit. The trigger-based physical layer protocol data unit may be similar to the HE MU PPDU, and may also be classified into an extremely high throughput single user physical layer protocol data unit (EHT SU PPDU) and an extremely high throughput multiple user physical layer protocol data unit (EHT MU PPDU).

It can be seen from Fig. 4 and Fig. 6 that the method of allocating resource blocks in the TB EHT PPDU is different from the method of indicating the allocation of resource blocks in the non-trigger-based and extremely high-bandwidth physical layer protocol data units. In the method of allocating resource blocks in the TB EHT PPDU as shown in Fig. 4, the allocation of resource blocks is indicated in the resource block allocation subfield in each user field. For example, an 8-bit resource block allocation subfield is required for each user field to indicate the resource block allocated to the user field. In the non-trigger-based and extremely high-bandwidth physical layer protocol data unit as shown in Fig. 6, the allocation of resource block is indicated in the common field in the extremely high-bandwidth signaling field.

Referring to Fig. 6, Fig. 6 is a schematic diagram illustrating the structure of a data block of a non-trigger-based extremely high-throughput physical layer protocol according to an embodiment of the present application. As shown in Fig. 6, a data packet includes a legacy short training field (L-STF), a legacy long training field (L-LTF), a legacy signal field (L-SIG), a repeated legacy signal field (RL-SIG), a universal signal field (U-SIG), an extremely high throughput-signal field (EHT-SIG), and the like. The EHT-SIG is divided into two parts. The common field of the first part includes from 1 to N resource unit allocation subfields. The second part of the User Specific field includes from 1 to M User Fields based on the resource unit allocation sequence.

2. OFDMA transmission and non-OFDMA transmission

OFDMA transmission is a multi-user communication mechanism and is applicable to the exchange of data frames between AP and STA in 802.11ax and later standards. The entire bandwidth can be divided into multiple resource blocks, and the resource blocks are allocated separately to different users. In non-OFDMA transmission, the entire bandwidth is used entirely for single user (SU) MIMO (SU-MIMO) or multi-user (MU) transmission (MU-MIMO). For non-OFDMA transmission, after preamble puncturing is performed, the remaining portion that is not punctured forms multiple RUs. A combination of multiple RUs supported by non-OFDMA transmission is equivalent to a combination of preamble puncturing supported by non-OFDMA transmission.

3. Resource block

The base bandwidth is 20 MHz, and the bandwidth is an exponential integer multiple of 20 MHz (e.g., 20, 40, 80, or 160 MHz). In a further implementation, 20 MHz is used as a channel. Channel allocation in 802.11 is shown in Fig. 7. Fig. 7 is a schematic representation of channel allocation according to an embodiment of the present application. When the bandwidth is 160 MHz, the channel can be divided into a primary 20 MHz channel (P20), a secondary 20 MHz channel (S20), a secondary 40 MHz channel (S40), and a secondary 80 MHz channel (840). In a further implementation, channel 1 may correspond to a primary 20 MHz channel, channel 2 may correspond to a secondary 20 MHz channel, channel 3 and channel 4 are aggregated into a secondary 40 MHz channel, and channel 5 - channel 8 are aggregated into a secondary 80 MHz channel. The primary 40 MHz channel (P40) is a 40 MHz channel on which the primary 20 MHz channel is located, and the primary 80 MHz channel (P80) is an 80 MHz channel on which the primary 20 MHz channel is located.

In another additional implementation, the data packet bandwidth may be divided into multiple resource units (RUs). RUs of different sizes may be aggregated with different numbers of subcarriers. For example, RUs of different sizes may include the following seven types: 996-tone RU, 484-tone RU, 484-tone RU, 106-tone RU, 26-tone RU, 52-tone RU, and 2×996-tone resource unit.

Referring to Fig. 8, Fig. 8 is a schematic diagram of resource block allocation in an 80 MHz channel according to an embodiment of the present application. As shown in Fig. 8, the first row indicates that the 80 MHz channel may include thirty-seven 26-tone RUs, the second row indicates that the 80 MHz channel may include sixteen 52-tone RUs, the third row indicates that the 80 MHz channel may include eight 106-tone RUs, the fourth row indicates that the 80 MHz channel may include four 242-tone RUs, the fifth row indicates that the 80 MHz channel may include two 484-tone RUs, and the sixth row indicates that the 80 MHz channel may include one 996-tone RU. In addition, as shown in Fig. 8, a central 26-tone RU formed by 13-tone sub-blocks additionally exists in each row of the 80 MHz channel. In addition, each row may include some guard subcarriers, zero subcarriers (shaded parts in Fig. 5), or direct current (DC) subcarriers.

As shown in Fig. 8, a 20 MHz subchannel may include nine 26-tone RUs, four 52-tone RUs, two 106-tone RUs, or one 242-tone RU. In addition, each row may include some guard subcarriers, zero subcarriers (shaded portions in Fig. 5), or DC subcarriers.

As shown in Fig. 8, a 40 MHz subchannel may include eighteen 26-tone RUs, eight 52-tone RUs, four 106-tone RUs, two 242-tone RUs, or one 484-tone RU. In addition, each row may include some guard subcarriers, zero subcarriers (shaded portions in Fig. 5), or DC subcarriers.

A 160 MHz bandwidth or a 160 MHz bandwidth formed by discrete 80 MHz + 80 MHz channels may be considered as an aggregation of the resource block allocation of two 80 MHz channels shown in Fig. 7. For example, a 160 MHz bandwidth may include one 2×996-tone RU or may include various combinations of 26-tone RUs, 52-tone RUs, 106-tone RUs, 242-tone RUs, 484-tone RUs, and 996-tone RUs.

In the resource blocks shown in Fig. 8, the frequencies increase sequentially from left to right. The leftmost resource block can be regarded as the resource block with the lowest frequency, and the rightmost resource block can be regarded as the resource block with the highest frequency. As shown in Fig. 7, four 242-tone RUs included in the 80 MHz channel can be separately numbered from left to right: the first 242-tone RU, the second 242-tone RU, the third 242-tone RU, and the fourth 242-tone RU. The first 242-tone RU and the second 242-tone RU correspond one-to-one to the two 20 MHz subchannels with the lowest frequencies in the 80 MHz channel in ascending frequency order. The third 242-tone RU and the fourth 242-tone RU correspond one-to-one to the two highest-frequency 20 MHz subchannels in the 80 MHz channel in ascending frequency order. Each 80 MHz channel has a central 26-tone RU. Thus, a 242-tone RU does not completely cover the corresponding 20 MHz subchannel in frequency.

Accordingly, two 484-tone RUs included in an 80 MHz channel can be separately numbered from left to right: the first 484-tone RU and the second 484-tone RU. The lowest frequency 40 MHz subchannel and the highest frequency 40 MHz subchannel in the 80 MHz channel correspond one-to-one to the first 484-tone RU and the second 484-tone RU in ascending frequency order.

It can be learned from the above that, for the trigger-based data packet, the resource block allocation subfield in each user field in the trigger frame can indicate the allocated resource block. The station can identify the user field whose association identifier is the same as the association identifier of the station, and learn the allocated resource block from the user field to transmit the trigger-based data packet. For the non-trigger-based data packet, the allocated resource block can be learned by using the resource block allocation subfield in the common field in the signaling field to obtain the data packet. For example, it is assumed that the resource blocks allocated to the station can be the first 484-tone RU and the fourth 242-tone RU in the 80 MHz channel, which are shown in Fig. 7.

However, if a preamble puncturing exists in the data packet bandwidth, all discrete resources caused by the puncturing are indicated using the resource block allocation subfield. The signaling overhead is high because a large number of resource blocks must be indicated.

In order to reduce the amount of overhead, preamble puncturing indicator information is used to indicate preamble puncturing information of a data packet in the embodiments of the present application for sending or receiving a data packet. The preamble puncturing indicator information includes one or more indicators, one indicator corresponds to one piece of preamble puncturing information, and the preamble puncturing information includes a size and a location of a preamble puncturing, or there is no preamble puncturing. In other words, a part of the channels in the bandwidth of the data packet is empty, or there is a puncture in the bandwidth of the data packet. The size and location of the puncture are indicated so that the station can receive or send a data packet on a resource block or on a channel other than the puncture in the bandwidth, in order to reduce signaling overhead.

For example, it is assumed that the size and location of the preamble puncturing correspond to the second 242-tone RU shown in Fig. 8, namely, the second 20 MHz subchannel, which is in the 80 MHz channel and corresponds to the second 242-tone RU. The discrete resources caused by the puncturing are the first 242-tone RU, the third 242-tone RU, and the fourth 242-tone RU. It is assumed that for non-OFDMA transmission, the first 242-tone RU, the third 242-tone RU, and the fourth 242-tone RU are allocated to one station or one group of stations. In this case, in the resource block allocation subfield corresponding to the station, it is necessary to specify the first 242-tone RU, the third 242-tone RU and the fourth 242-tone RU, or to separately specify the first 484-tone RU and the fourth 242-tone RU. In this application, the size and location of the preamble puncturing may be specified as the second 20 MHz subchannel of the 80 MHz channel. The station determines the allocated resource block based on the preamble puncturing indicator information. Compared with the method in which at least two resource blocks must be specified, this method of specifying can reduce the overhead for resource block allocation.

With reference to the accompanying drawings and the above related concepts, the following is a further description of the related content of the present application or the preamble piercing indicator information newly added to the present application.

Referring to Fig. 9, Fig. 9 is a flow chart of a data transmission method according to an embodiment of the present application. The data transmission method shown in Fig. 9 is described using an example in which an access point sends preamble puncturing indicator information. If necessary, in the data transmission method in the present application, a station can send preamble puncturing indicator information, and the access point can receive or send a data packet based on the preamble puncturing indicator information. Specifically, as shown in Fig. 9, the data transmission method includes the following steps.

101: The access point sends preamble puncturing indicator information.

The preamble puncturing indicator information includes one or more indicators, and one indicator corresponds to one piece of preamble puncturing information. In the present application, the preamble puncturing indicator information is used by the receiving side to determine the allocated resource block based on the preamble puncturing information corresponding to the receiving side. In other words, the function of the preamble puncturing indicator information is similar to the function of the resource block allocation subfield described above. Thus, for a trigger-based data packet, the preamble puncturing indicator information may be included in each user field in the trigger frame. For a non-trigger-based data packet, the preamble puncturing indicator information may be included in a common field in the signaling field of the data packet.

If necessary, the preamble puncturing indicator information may be a newly added field in the user field in the trigger frame or a reused spare field, or may be a newly added field in the common field in the signaling field in the data packet or a reused spare field.

If necessary, as shown in Fig. 10, compared with Fig. 4, the preamble puncturing pointer information may reuse the resource block allocation subfield in the user field in the trigger frame. For example, as shown in Fig. 10, it is assumed that the preamble puncturing pointer information includes a first pointer and a second pointer, and the two pointers indicate two pieces of the preamble puncturing information. If necessary, as shown in Fig. 11, compared with Fig. 6, the preamble puncturing pointer information may reuse the resource block allocation subfield in the EHT-SIG. For example, as shown in Fig. 11, it may be assumed that the preamble puncturing pointer information includes a first pointer and a second pointer, and the two pointers indicate two pieces of the preamble puncturing information.

102: The station receives preamble puncturing indicator information.

103: The station sends or receives a data packet based on the preamble puncturing indicator information.

If the preamble puncturing indicator information is in a signaling field, such as in the EHT-SIG shown in Fig. 11, the station can receive or send the preamble puncturing indicator information and the data packet as a whole.

Step 103 may include: when the preamble puncturing indicator information indicates no preamble puncturing, sending or receiving a data packet in the bandwidth of the data packet; or, when the preamble puncturing indicator information indicates a size and location of the preamble puncturing, sending or receiving a data packet in a resource block in the bandwidth of the data packet different from the size and location of the preamble puncturing.

In addition, embodiments of the present application further provide several additional methods for indicating preamble puncturing information. For details, see the following descriptions.

It can be learned that in the present application, the allocated resource block can be indirectly indicated based on the preamble puncturing indicator information for sending or receiving a data packet. Compared with the method in which the allocated resource block is directly indicated based on only the resource block allocation subfield, the present application can reduce the signaling overhead for allocating resource blocks.

Referring to Fig. 12. Fig. 12 is a flow chart of another method for transmitting data according to an embodiment of the present application. Compared with the method for transmitting data shown in Fig. 9, in the method for transmitting data shown in Fig. 12, the access point additionally sends transmission mode indicator information. The transmission mode indicator information indicates a transmission mode of a data packet. For example, the station can determine, based on the transmission mode indicator information, whether the data packet is transmitted in the OFDMA mode or in the non-OFDMA mode. For non-OFDMA transmission, a plurality of discrete resource blocks caused by preamble puncturing are uniformly allocated to one user or one group of users. To be precise, each user is usually allocated the same number of resource blocks. Thus, compared with the method in which the resource block allocation subfield indicates a plurality of discrete resource blocks, the present application uses the preamble puncturing indicator information. This can reduce the signaling overhead for indicating the resource blocks. For OFDMA transmission, a plurality of discrete resource blocks caused by preamble puncturing are allocated to different users. In other words, the resource block allocated to a user is part of these discrete resource blocks. In this case, the resource block allocation subfield is used for the indicator, and low signaling overhead is required. Thus, in the data transmission method shown in Fig. 12, different methods for indicating resource blocks can be used based on different transmission modes.

In particular, as shown in Fig. 12, the data transmission method includes the following steps.

201: The access point sends a signaling field or trigger frame. The signaling field or trigger frame includes transmission mode indicator information and preamble puncturing indicator information, or includes transmission mode indicator information and a resource block allocation subfield.

The signaling field may include the U-SIG and the EHT-SIG shown in Fig. 10, but is not limited to the signaling fields shown in Fig. 10. The trigger frame may have the structure shown in Fig. 11, but is not limited to the structure of the trigger frame shown in Fig. 11. As shown in Fig. 10, the signaling field is in the PPDU. Thus, for a physical layer protocol data unit that is not based on a trigger, the access point can send the signaling field and the data packet as a whole to the receiving side, for example, to the station.

As shown in Fig. 10, the transmission mode indicator information may be in a common field in the trigger frame, and the bandwidth of the data packet may also be in the common field. The transmission mode indicator information indicates non-OFDMA transmission, and the location of the resource block allocation subfield is the same as that of the preamble puncturing indicator information. In addition, for non-OFDMA transmission, the content of the preamble puncturing indicator information in the M user fields of the field for each station may be the same. The preamble puncturing indicator information may also be referred to as a preamble puncturing indicator subfield.

As shown in Fig. 11, the transmission mode indicator information may be located in the U-SIG of the data packet. The transmission mode indicator information indicates non-OFDMA transmission, and the resource block allocation subfield in the common field in the EHT-SIG is preamble puncturing indicator information. The preamble puncturing indicator information may also be referred to as a preamble puncturing indicator subfield. The bandwidth of the data packet may also be indicated in the U-SIG. For non-OFDMA transmission, the contents of the preamble puncturing indicator subfields corresponding to the M user fields may be the same. The order in which the user fields appear in the user-specific field is consistent with the preamble puncturing indicator information indicated by the corresponding preamble puncturing indicator subfields. A station can determine whether the user field belongs to a station by reading the station identifier (STA ID) in a user field. By referring to the location where the user field and the corresponding preamble puncturing indicator subfield appear, a station can learn the station's preamble puncturing information.

In order to effectively reuse resources, in the case of a bandwidth greater than or equal to 40 MHz, a content channel (CC) 1 or CC2 method may be used to represent content in an EHT-SIG or a field according to the future generation Wi-Fi standard. For example, when the bandwidth of a data packet is 40 MHz, there are two EHT-SIG content channels: CC1 and CC2. As shown in Fig. 13, the first CC1 of the EHT-SIG may include a first pointer in the preamble puncturing pointer information and the corresponding user field, and the second CC2 of the EHT-SIG includes a second pointer in the preamble puncturing pointer information and the corresponding user field. The first pointer and the second pointer correspond to the same user field.

If necessary, CC1 and CC2 may include the same preamble puncturing indicator information and the corresponding user field. By reading the information of CC1 and CC2, the user can fully know the preamble puncturing information in the passband. This can improve the reliability of transmitting the preamble puncturing information. If necessary, the preamble puncturing indicator information may alternatively appear on one of the CCs.

202: The station receives a signaling field or trigger frame.

Accordingly, as shown in Fig. 10, the signaling field is in the PPDU structure. Thus, for a non-trigger-based physical layer protocol data unit, the receiving side such as a station can receive the signaling field and the data packet as a whole.

203: When the transmission mode indicator information indicates OFDMA transmission, the station parses the resource block allocation subfield from the signaling field or trigger frame and receives or sends a data packet based on the resource block allocation subfield.

204: When the transmission mode indicator information indicates non-OFDMA transmission, the station parses the preamble puncturing indicator information from the signaling field or trigger frame and receives or sends a data packet based on the preamble puncturing indicator information.

It should be noted that step 203 and step 204 are not subject to a specific sequence. In addition, embodiments of the present application further provide several additional methods for indicating preamble puncturing information. Details are provided in the following descriptions.

It can be learned that in this embodiment of the present application, for non-OFDMA transmission, a data packet can be received or sent based on preamble puncturing indicator information; and for OFDMA transmission, a data packet can be received or sent based on a resource block allocation subfield. This makes it possible to reduce the amount of overhead data for indicating the allocated resource block.

In the data transmission methods shown in Fig. 9 and Fig. 12, if the access point sends a data packet based on a trigger, for example, an EHT PPDU, as shown in Fig. 10, the data packet can carry preamble puncturing indicator information, and the station can receive the preamble puncturing indicator information and the data packet as a whole. If the access point sends a data packet based on a trigger, for example, an EHT PPDU TB, a trigger frame is sent before sending the data packet based on the trigger. As shown in Fig. 11, the trigger frame can carry preamble puncturing indicator information, and the station can receive the data packet based on the preamble puncturing indicator information.

This embodiment of the present application further provides several additional methods for indicating preamble puncturing information.

Method 1: The preamble puncturing indicator information includes one or more indicator(s), and one indicator indicates one piece of preamble puncturing information.

Method 2: The preamble puncturing indicator information includes at least two indicators. One indicator indicates the size of the preamble puncturing and the other one or more indicators indicate the location of the preamble puncturing.

Method 3: The preamble puncturing indicator information indicates the preamble puncturing status in the bandwidth based on the bandwidth indicator information. The bandwidth indicator information may be the bandwidth field shown in Fig. 10 or Fig. 11, and indicates the bandwidth of the data packet.

The preamble puncturing information described in this specification may represent a specific preamble puncturing status, such as size and location, or no puncturing, or may be an index corresponding to the preamble puncturing status, etc. Three additional indication methods are described below.

Method 1. One pointer in the preamble puncturing pointer information corresponds to one piece of preamble puncturing information.

In an additional implementation, by configuration or pre-determining using signaling, the pointer indicates one or more pieces of the following preamble puncturing information in the 160 MHz channel:

20 MHz subchannel in 160 MHz channel;

a 40 MHz subchannel formed by any two 20 MHz subchannels in a 160 MHz channel;

a 60 MHz subchannel formed by any three 20 MHz subchannels in a 160 MHz channel;

an 80 MHz subchannel formed by any four 20 MHz subchannels in a 160 MHz channel; or

in the 160 MHz channel there is no preamble puncturing.

In this implementation, the pointer can indicate all possible preamble puncturing information in a 160 MHz channel, that is, it can indicate the puncturing statuses of a 40 MHz, 60 MHz, or 80 MHz subchannel formed by adjacent or non-adjacent (neighboring or non-adjacent) 20 MHz subchannels. This allows for increased flexibility of preamble puncturing.

In another additional implementation, by configuration or pre-determining using signaling, the pointer indicates one or more pieces of the following preamble puncturing information in the 160 MHz channel:

20 MHz subchannel in 160 MHz channel;

a 40 MHz subchannel formed by any two adjacent 20 MHz subchannels in a 160 MHz channel;

a 60 MHz subchannel formed by any three adjacent 20 MHz subchannels in a 160 MHz channel;

an 80 MHz subchannel formed by any four adjacent 20 MHz subchannels in a 160 MHz channel; or

in the 160 MHz channel there is no preamble puncturing.

In this implementation, the pointer can indicate the preamble puncturing information of the puncturing status with high or highest probability in the 160 MHz channel. This allows for increased flexibility of the preamble puncturing pointer and reduced bit overhead.

In yet another additional implementation, the 160 MHz channel includes an 80 MHz subchannel with the highest frequency and an 80 MHz subchannel with the lowest frequency, and the indicator specifies one or more pieces of the following preamble puncturing information in the 160 MHz channel:

20 MHz subchannel in 160 MHz channel;

a 40 MHz subchannel formed by two subchannels with the lowest frequency of 20 MHz in a subchannel with the lowest frequency of 80 MHz;

a 40 MHz subchannel formed by two subchannels with the highest frequency of 20 MHz in a subchannel with the lowest frequency of 80 MHz;

a 40 MHz subchannel formed by two subchannels with the lowest frequency of 20 MHz in a subchannel with the highest frequency of 80 MHz;

a 40 MHz subchannel formed by two subchannels with the highest frequency of 20 MHz in a subchannel with the highest frequency of 80 MHz;

subchannel with the lowest frequency of 80 MHz;

the subchannel with the highest frequency of 80 MHz; or

in the 160 MHz channel there is no preamble puncturing.

In this implementation, the pointer may indicate a fragment of possible preamble puncturing information in a 160 MHz channel. For example, the size and location of the preamble puncturing may correspond to the resource block obtained by dividing the channel. This makes it possible to determine the allocated resource block based on the preamble puncturing pointer information and reduce the number of pointer bits.

Referring to Fig. 14, Fig. 14 shows a schematic representation of another channel assignment according to the present application. As shown in Fig. 14, the channel assignment for the 160 MHz channel shown in Fig. 7 is divided into indices corresponding to additional preamble puncturing sizes and locations. In other words, in Fig. 14, one or more channels corresponding to one index represent a preamble puncturing size and location in the 160 MHz channel.

Thus, the preamble puncturing information in one 20 MHz subchannel in a 160 MHz channel is the preamble puncturing information corresponding to one of the indices 0-7 shown in Fig. 14. The preamble puncturing information in a 40 MHz subchannel formed by two subchannels with the lowest frequency of 20 MHz in a subchannel with the lowest frequency of 80 MHz is the preamble puncturing information corresponding to the index 8 shown in Fig. 14. The preamble puncturing information in a 40 MHz subchannel formed by two subchannels with the highest frequency of 20 MHz in a subchannel with the lowest frequency of 80 MHz is the preamble puncturing information corresponding to the index 9 shown in Fig. 14. The preamble puncturing information in the 40 MHz subchannel formed by the two subchannels with the lowest frequency of 20 MHz in the subchannel with the highest frequency of 80 MHz is the preamble puncturing information corresponding to index 10 shown in Fig. 14. The preamble puncturing information in the 40 MHz subchannel formed by the two subchannels with the highest frequency of 20 MHz in the subchannel with the highest frequency of 80 MHz is the preamble puncturing information corresponding to index 11 shown in Fig. 14. The preamble puncturing information in the subchannel with the lowest frequency of 80 MHz is the preamble puncturing information corresponding to index 12 shown in Fig. 14. The preamble puncturing information in the 80 MHz subchannel with the highest frequency is the preamble puncturing information corresponding to index 13 shown in Fig. 14.

Accordingly, as shown in Table 3, each index in the first column corresponds to each piece of preamble puncturing information. The pointer must indicate any of the 15 types of preamble puncturing information in the 160 MHz channel. Thus, the pointer can occupy four bits.

In Table 3, as shown in Fig. 14, indices 0 to 7 correspond to the preamble puncturing information whose preamble puncturing size is 20 MHz. For example, if the index is 0000, it may indicate that the location and the preamble puncturing size are the preamble puncturing information corresponding to index 0. If the index is 0001, it may indicate that the location and the preamble puncturing size are the preamble puncturing information corresponding to index 1. Indices 8 to 11 in Table 3 may respectively indicate the preamble puncturing information whose preamble puncturing size is 40 MHz. Indices 12 to 13 in Table 3 may respectively indicate the preamble puncturing information whose preamble puncturing size is 80 MHz. Index 14 in Table 3 may indicate that there is no preamble puncturing and index 15 is reserved. The number of indices is the total number of preamble puncturing statuses described. For example, the number of indices in the first row is 8. This indicates that indices 0-7 correspond to a total of eight pieces of preamble puncturing information whose preamble puncturing size is 20 MHz. Accordingly, indices in the quantities from the first row to the third row in Table 3 may be expanded, and each row corresponds to one index.

It can be learned that the index can indicate the location and size of the preamble puncturing by this indication method. Compared with the method of directly indicating the discrete multiple resource blocks obtained after the preamble puncturing, the preamble puncturing indicator information can reduce the signaling overhead.

In an additional implementation, the 160 MHz channel includes an 80 MHz subchannel with the highest frequency and an 80 MHz subchannel with the lowest frequency. The indicator further indicates one or more of the following preamble puncturing data in the 160 MHz channel: a subchannel with a center frequency of 40 MHz in the subchannel with the highest frequency of 80 MHz or a subchannel with a center frequency of 40 MHz in the subchannel of 80 MHz.

In one case, the following can be added to Fig. 14 or Table 3: index 15 corresponds to the size and location of the preamble puncturing on the subchannel with a center frequency of 40 MHz in the subchannel with the lowest frequency of 80 MHz. The subchannel with a center frequency of 40 MHz in the subchannel with the lowest frequency of 80 MHz is the 40 MHz subchannel formed by channel 2 and channel 3, which are shown in Fig. 7.

In another case, the following can be added to Fig. 14 or Table 3: index 15 corresponds to the size and location of the preamble puncturing on the subchannel with a center frequency of 40 MHz in the subchannel with the highest frequency of 80 MHz. The subchannel with a center frequency of 40 MHz in the subchannel with the highest frequency of 80 MHz is the 40 MHz subchannel formed by channel 5 and channel 6, which are shown in Fig. 7.

In another case, the number of bits indicated in the preamble puncturing indicator information may be increased, for example, to five bits. In this case, the following may be added to Fig. 14 or Table 3: index 15 corresponds to the size and location of the preamble puncturing on the subchannel with a center frequency of 40 MHz in the subchannel with the lowest frequency of 80 MHz, and index 16 corresponds to the size and location of the preamble puncturing of the subchannel with a center frequency of 40 MHz in the subchannel with the highest frequency of 80 MHz.

Table 3. Table of preamble puncturing indicator information indices in 160 MHz channel (using 4 bits as an example) Record index Description Number of records 0-7 Preamble Puncture Size 20 MHz 8 8-11 Preamble puncture size is 40 MHz. 4 12-13 Preamble Puncture Size 80 MHz 2 14 No piercing 1 15 Reserved 1

Accordingly, based on the schematic representation of resource block allocation in Fig. 8, a correspondence between a resource block and a channel in a 160 MHz channel can be obtained. For example, as shown in Fig. 15, a 20 MHz subchannel corresponds to a 242-tone RU in a 160 MHz channel from left to right and in ascending frequency order. The sizes and locations of the preamble puncturing corresponding to the indices in Table 3 are shown in Fig. 15. With reference to Fig. 14 or Fig. 15 and the indices shown in Table 3, a description of the preamble puncturing information corresponding to the preamble puncturing indicator information is given below.

The bandwidth of the data packet is 160 MHz. The preamble puncturing indicator information may include a first indicator. The first indicator indicates one piece of preamble puncturing information in the bandwidth of 160 MHz.

For example, as shown in Fig. 16, a 160 MHz bandwidth includes eight 20 MHz subchannels or eight 242-tone RUs. It is assumed that the first indicator is 0001. The station can determine from Table 3 that the size and location of the preamble puncturing in the data packet corresponds to a 20 MHz subchannel filled with the grids shown in Fig. 16. Accordingly, the station can receive or send a data packet on seven 20 MHz subchannels other than the 20 MHz subchannel filled with grids, or on seven 242-tone RUs corresponding to the seven 20 MHz subchannels.

As another example, as shown in Fig. 17, a 160 MHz bandwidth includes four 40 MHz subchannels. It is assumed that the first indicator is 0101. The station can determine from Table 3 that the size and location of the preamble puncturing in the data packet corresponds to a 40 MHz subchannel filled with the grids shown in Fig. 17. Accordingly, the station can receive or send a data packet on three 40 MHz subchannels other than the 40 MHz subchannel filled with grids, or on three 484-tone RUs corresponding to the three 40 MHz subchannels.

The bandwidth of the data packet is 320 MHz. The preamble puncturing indicator information includes a first indicator and a second indicator. The first indicator indicates the preamble puncturing information in the subchannel with the lowest frequency of 160 MHz in the bandwidth of 320 MHz, and the second indicator indicates the preamble puncturing information in the subchannel with the highest frequency of 160 MHz in the bandwidth of 320 MHz. It can be learned that for a plurality of resource blocks in the bandwidth of 320 MHz, 8-bit preamble puncturing indicator information is used for indication based on Table 3.

For example, as shown in Fig. 18, a 320 MHz bandwidth includes sixteen 20 MHz subchannels or sixteen 242-tone RUs. It is assumed that the first pointer in the preamble puncturing pointer information is 0111 and the second pointer is 0000. The station can determine that the size and location of the preamble puncturing are a 20 MHz subchannel filled with grids in the lowest frequency 160 MHz subchannel and a 20 MHz subchannel filled with grids in the highest frequency 160 MHz subchannel shown in Fig. 18. Thus, a station can send or receive a data packet on the remaining channels or resource blocks in the 320 MHz bandwidth, for example, on fourteen 20 MHz subchannels other than the 20 MHz subchannel filled with grids, or on fourteen 242-tone RUs corresponding to the fourteen 20 MHz subchannels shown in Fig. 9. In this case, the equivalent bandwidth is 280 MHz.

As another example, as shown in Fig. 19, a 320 MHz bandwidth includes sixteen 20 MHz subchannels, or sixteen 242-tone RUs, or eight 242-tone RUs and four 484-tone RUs. It is assumed that the first pointer in the preamble puncturing pointer information is 0111 and the second pointer is 1000. The station can determine that the size and location of the preamble puncturing are a 20 MHz subchannel filled with grids in the lowest frequency 160 MHz subchannel and a 40 MHz subchannel filled with grids in the highest frequency 160 MHz subchannel shown in Fig. 19. Thus, a station can send or receive a data packet on each 20 MHz subchannel or on the corresponding 242-tone RU or 484-tone RU other than 20 MHz and 40 MHz, which are filled with grids in a bandwidth of 320 MHz. In other words, the equivalent bandwidth is 260 MHz.

As another example, as shown in Fig. 20, the 320 MHz bandwidth includes sixteen 20 MHz subchannels, sixteen 242-tone RUs, or eight 484-tone RUs. It is assumed that the first pointer in the preamble puncturing pointer information is 1000 and the second pointer is 0000. The station can determine that the size and location of the preamble puncturing are a 40 MHz subchannel filled with grids in the lowest frequency 160 MHz subchannel and a 20 MHz subchannel filled with grids in the highest frequency 160 MHz subchannel shown in Fig. 20. Thus, a station can send or receive a data packet on each 20 MHz subchannel or on the corresponding 242-tone RU or 484-tone RU, except for 20 MHz and 40 MHz, which are filled with grids in the 320 MHz bandwidth.

As another example, as shown in Fig. 21, a 320 MHz bandwidth includes sixteen 20 MHz subchannels, sixteen 242-tone RUs, or eight 484-tone RUs. It is assumed that the first pointer in the preamble puncturing pointer information is 1011 and the second pointer is 1000. The station can determine that the size and location of the preamble puncturing are a 40 MHz subchannel filled with grids in the lowest frequency 160 MHz subchannel and a 40 MHz subchannel filled with grids in the highest frequency 160 MHz subchannel shown in Fig. 21. Thus, the station can send or receive a data packet on the remaining channels or on the remaining resource blocks in the 320 MHz bandwidth without preamble puncturing, that is, in an equivalent bandwidth of 240 MHz.

In an additional implementation, the same pointer corresponds to different preamble puncturing information in different bandwidths. This makes it possible to reduce the number of pieces of preamble puncturing information that must be indicated by the preamble puncturing pointer information and to reduce the number of bits required for the preamble puncturing pointer information.

In an additional implementation, a pointer in the preamble puncturing pointer information specifies one or more pieces of the following preamble puncturing information in an 80 MHz channel:

20 MHz subchannel in 80 MHz channel;

a 40 MHz subchannel formed by any two 20 MHz subchannels in an 80 MHz channel;

a 60 MHz subchannel formed by any three 20 MHz subchannels in an 80 MHz channel; or

in the 80 MHz channel there is no preamble puncturing.

In this implementation, the pointer can indicate all possible preamble puncturing information in an 80 MHz channel, that is, it can indicate the puncturing statuses of a 40 MHz or 60 MHz subchannel formed by adjacent or non-adjacent (neighboring or non-adjacent) 20 MHz subchannels. This allows for increased flexibility of preamble puncturing.

In another additional implementation, by configuration or pre-determining using signaling, the preamble puncturing information in the 80 MHz channel includes one or more of the following:

20 MHz subchannel in 80 MHz channel;

a 40 MHz subchannel formed by any two adjacent 20 MHz subchannels in an 80 MHz channel;

a 60 MHz subchannel formed by any three adjacent 20 MHz subchannels in an 80 MHz channel;

in the 80 MHz channel there is no preamble puncturing.

In this implementation, the pointer can indicate the preamble puncturing information of the puncturing status with high or highest probability in the 80 MHz channel. This allows for increased flexibility of the preamble puncturing pointer and reduced bit overhead.

In yet another additional implementation, by configuration or pre-determining using signaling, the preamble puncturing information in the 80 MHz channel includes one or more of the following:

20 MHz subchannel in 80 MHz channel;

40 MHz subchannel with the lowest frequency in the 80 MHz channel;

subchannel with an average frequency of 40 MHz in a channel of 80 MHz;

40 MHz subchannel with the highest frequency in the 80 MHz channel;

80 MHz channel; or

in the 80 MHz channel there is no preamble puncturing.

In this implementation, the pointer can indicate the preamble of the puncturing information with the highest or highest probability in the 80 MHz channel. This allows for further reduction of the number of bits to indicate.

As shown in Table 4, each pointer in the preamble puncturing pointer information may separately indicate the preamble puncturing status corresponding to each index in Table 4. For example, based on the schematic diagram of the channels shown in Fig. 7, the size and location of the preamble puncturing corresponding to each index in Table 4 are shown in Fig. 22. The size and location of the preamble puncturing corresponding to index 6 belong to channel 2 and channel 3, and may also be a subchannel with a center frequency of 40 MHz in the 80 MHz channel. Accordingly, based on the schematic diagram of the resource blocks shown in Fig. 8, the sizes and locations of the preamble puncturing corresponding to the indices in Table 4 are shown in Fig. 23. If necessary, if the preamble puncturing indicator information does not indicate no puncturing, the preamble puncturing information shown in Table 4 may be indicated using the 3-bit preamble puncturing indicator information.

Table 4. Table of preamble puncturing indicator information indices in 80 MHz channel Index Description Number of entries 0-3 Preamble Puncture Size 20 MHz 4 4-6 Preamble puncture size is 40 MHz. 3 7 Preamble Puncture Size 80 MHz 1 8 No piercing 1 9-15 Reserved 7

With reference to Fig. 22 or Fig. 23 and the indices shown in Table 3 and Table 4, preamble puncturing information corresponding to the preamble puncturing indicator information is described below.

The bandwidth of the data packet is 240 MHz. The preamble puncturing indicator information includes a first indicator and a second indicator. The first indicator indicates the preamble puncturing information in the subchannel with the lowest frequency of 160 MHz in the bandwidth of 240 MHz; and the second indicator indicates the preamble puncturing information in the subchannel with the highest frequency of 80 MHz in the bandwidth of 240 MHz. It can be learned that, based on Table 3 and Table 4, for a plurality of resource blocks in the bandwidth of 240 MHz, only the preamble puncturing indicator information occupying 8 bits needs to be used for indication.

For example, based on Table 3 and Table 4, the bandwidth of a data packet is 240 MHz. As shown in Fig. 24, the first indicator in the preamble puncturing information is 0111, and the second indicator is 0000. The station can determine, based on the first indicator and Table 3, that the size and location of the preamble puncturing in the subchannel with the lowest frequency of 160 MHz are the fourth subchannel with a frequency of 20 MHz in the subchannel with the lowest frequency of 160 MHz shown in Fig. 24. The station can determine, based on the second indicator and Table 4, that the size and location of the preamble puncturing in the subchannel with the highest frequency of 80 MHz are the first subchannel of 20 MHz in the subchannel with the highest frequency of 80 MHz shown in Fig. 22. Thus, the station can send or receive a data packet on the remaining channels or resource blocks in the bandwidth of 240 MHz.

As another example, as shown in Fig. 25, it is assumed that the first pointer in the preamble puncturing pointer information is 1000 and the second pointer is 0000. The station can determine, based on the first pointer and Table 3, that the size and location of the preamble puncturing is a 40 MHz subchannel filled with grids in the lowest frequency 160 MHz subchannel shown in Fig. 14. The station can further determine, based on the second pointer and Table 4, that the size and location of the preamble puncturing is a 20 MHz subchannel filled with grids in the highest frequency 80 MHz subchannel shown in Fig. 25. In this way, the station can send or receive a data packet on the remaining channels or resource blocks in the 240 MHz bandwidth, for example on the channels or on the resource blocks shown in Fig. 14 that are not filled with grids.

As another example, as shown in Fig. 26, it is assumed that the first pointer in the preamble puncturing pointer information is 0111 and the second pointer is 0100. The station can determine, based on the first pointer and Table 3, that the size and location of the preamble puncturing is a 20 MHz subchannel filled with grids in the lowest frequency 160 MHz subchannel shown in Fig. 24. The station can further determine, based on the second pointer and Table 2, that the size and location of the preamble puncturing is a 40 MHz subchannel filled with grids in the highest frequency 80 MHz subchannel shown in Fig. 26. In this way, the station can send or receive a data packet on the remaining channels or resource blocks in the 240 MHz bandwidth, for example, on the channels or resource blocks shown in Fig. 24 that are not filled with grids.

If necessary, the data packet bandwidth is 240 MHz. The first pointer in the preamble puncturing pointer information indicates the preamble puncturing information in the subchannel with the lowest frequency of 160 MHz in the bandwidth of 240 MHz; and the second pointer indicates the preamble puncturing information in the subchannel with the highest frequency of 80 MHz in the bandwidth of 240 MHz.

The first indicator may indicate preamble puncturing information in the subchannel with the lowest frequency of 80 MHz in the bandwidth of 240 MHz, and the second indicator may indicate preamble puncturing information in the subchannel with the highest frequency of 160 MHz in the bandwidth of 240 MHz.

When the data packet bandwidth is 160 MHz, the preamble puncturing indicator information may be specified in the following several additional implementations.

In an additional implementation, the preamble puncturing pointer information may include one pointer, such as the first pointer. The first pointer may indicate the preamble puncturing information based on table 3. This can reduce the amount of pointer overhead.

In another additional implementation, the preamble puncturing pointer information may include two pointers. The preamble puncturing information is also specified based on Table 3. Thus, one of the pointers may be a reserved value or any value, or the station may ignore the pointer value. It can be learned that this implementation allows using a unified structure of the preamble puncturing pointer information for different bandwidths.

In yet another additional implementation, the preamble puncturing indicator information includes two pointers. These two pointers may, respectively, indicate the size and location of the puncturing in the 80 MHz subchannel. For example, the preamble puncturing indicator information includes a first pointer and a second pointer. The first pointer indicates the preamble puncturing information in the subchannel with the lowest frequency of 80 MHz in the bandwidth of 160 MHz; and the second pointer indicates the preamble puncturing information in the subchannel with the highest frequency of 80 MHz in the bandwidth of 160 MHz.

In this embodiment of the present application, the bandwidth can support one or more punctures in the preamble, that is, there are one or more punctures in the bandwidth. Each puncture can be indicated using the indicating method in this embodiment of the present application. If necessary, a plurality of punctures can be limited by adjacent punctures. For example, the bandwidth of a data packet is 160 MHz, and the preamble puncturing indicator information includes a first indicator and a second indicator. The first indicator indicates the preamble puncturing information of the first puncture in the bandwidth of 160 MHz; and the second indicator indicates the preamble puncturing information of the second puncture in the bandwidth of 160 MHz. The preamble puncturing information of the first puncture and the second puncture can be determined using Table 3 or Table 4.

In the above implementations, one pointer in the preamble puncturing pointer information corresponds to one piece of preamble puncturing information, and how the preamble puncturing pointer information indicates a bandwidth of 320 MHz, 240 MHz, 160 MHz, or 80 MHz is described.

In addition, the present application further provides a method for indicating preamble puncturing information, namely the above-mentioned second method. The details are described below.

If necessary, for the records shown in Table 3 or Table 4, the number of record indices that can be indicated by the preamble puncturing indicator information is related to the number of bits of the preamble puncturing indicator information. For example, the preamble puncturing indicator information may occupy a smaller number of bits to indicate a part of the record indices in Table 3 or Table 4. Accordingly, the record indices shown in Table 3 or Table 4 may be further expanded. For example, the preamble puncturing information that can be indicated by the preamble puncturing indicator information may include a puncture formed by any 20 MHz subchannel in the bandwidth, a 40 MHz subchannel formed by any two 20 MHz subchannels in the bandwidth, a 60 MHz subchannel formed by any three 20 MHz subchannels, an 80 MHz subchannel formed by any four 20 MHz subchannels, and the like.

Method 2. The size and location of the preamble piercing are specified separately.

It is assumed that there is only one puncture in the passband. The preamble puncture indicator information includes a first indicator and a second indicator. The first indicator indicates the size of the preamble puncture, and the second indicator indicates the location of the preamble puncture.

If necessary, the preamble puncturing size indicated by the first indicator includes one or more of the following: 20 MHz, 40 MHz, 60 MHz or 80 MHz. For example, the preamble puncturing size indicated by the first indicator may be a puncturing size corresponding to each index in Table 3. In addition, as shown in Table 5, the first indicator may further indicate no preamble puncturing in the passband. Alternatively, no preamble puncturing may be indicated by the second indicator. This case is not limited to this embodiment of the present application.

Table 5. Puncture sizes Record index Description Number of entries 0 Preamble Puncture Size 20 MHz 1 1 Preamble puncture size is 40 MHz. 1 2 Preamble Puncture Size 60 MHz 1 3 Preamble Puncture Size 80 MHz 1 4 Without piercing the preamble 1

Based on the puncture sizes shown in Table 5, the puncture locations also vary for different bandwidth sizes. The details are described below.

In a further implementation, the preamble puncturing size indicated by the first indicator is 20 MHz, and the preamble puncturing location includes one or more of the following: a 20 MHz subchannel in the data packet bandwidth. For example, for a bandwidth of 320 MHz, as shown in Fig. 18, there are 16 cases of 20 MHz puncturing locations. As shown in Table 6, each index corresponds to a 20 MHz puncturing location, so that the second indicator can indicate an index to notify the station of a 20 MHz puncturing location in a bandwidth of 320 MHz.

Table 6. Puncture locations Record index Description Number of entries 0-15 Puncture locations when puncturing the preamble 16

For example, for a 240 MHz bandwidth, there are 12 instances of 20 MHz puncture locations. Each index corresponds to a location, so the second designator can indicate the index to notify the station of the location of the 20 MHz puncture in the 240 MHz bandwidth. The location of the 20 MHz puncture in the 160 MHz bandwidth or the 80 MHz bandwidth can alternatively be indicated by the second designator.

In a further implementation, the preamble puncturing size indicated by the first indicator is 40 MHz, and the preamble puncturing location includes one or more of the following: a 40 MHz subchannel formed by any two 20 MHz subchannels in the data packet bandwidth.

In another additional implementation, the preamble puncturing size indicated by the first indicator is 40 MHz, and the preamble puncturing location includes one or more of the following: a 40 MHz subchannel formed by any two adjacent 20 MHz subchannels in the data packet bandwidth. It can be learned that for a bandwidth of 320 MHz, there are 15 cases of 40 MHz puncturing locations formed by any two adjacent 20 MHz subchannels. Each index corresponds to a location, so that the second indicator can indicate an index to notify the station of a 40 MHz puncturing location in a bandwidth of 320 MHz.

Accordingly, for the 240 MHz bandwidth, there are 11 cases of locations of a 40 MHz puncture formed by any two adjacent 20 MHz subchannels. Each index corresponds to a location, so the second indicator can indicate the index to notify the station of the location of a 40 MHz puncture in the 240 MHz bandwidth. The location of a 40 MHz puncture in the 160 MHz bandwidth or the 80 MHz bandwidth can alternatively be indicated by the second indicator.

In a further implementation, the preamble puncturing size indicated by the first indicator is 60 MHz, and the preamble puncturing location includes one or more of the following: a 60 MHz subchannel formed by any two 20 MHz subchannels in the data packet bandwidth.

In another further implementation, the preamble puncturing size indicated by the first indicator is 60 MHz, and the preamble puncturing location includes one or more of the following: a 60 MHz subchannel formed by any three adjacent 20 MHz subchannels in the data packet bandwidth.

For example, for a 320 MHz bandwidth, there are 14 instances of 60 MHz puncture locations. Each index corresponds to a location, so that a second designator can indicate an index to notify a station of a 60 MHz puncture location in a 320 MHz bandwidth. A 60 MHz puncture location in a 240 MHz bandwidth, a 160 MHz bandwidth, or an 80 MHz bandwidth can alternatively be indicated by a second designator.

In a further implementation, the preamble puncturing size indicated by the first indicator is 80 MHz, and the preamble puncturing location includes one or more of the following: an 80 MHz subchannel formed by any four 20 MHz subchannels in the data packet bandwidth.

In another additional implementation, the preamble puncturing size indicated by the first indicator is 80 MHz, and the preamble puncturing location includes one or more of the following: an 80 MHz subchannel formed by any four adjacent 20 MHz subchannels in the data packet bandwidth. For example, for a bandwidth of 320 MHz, there are 13 cases of 80 MHz puncturing locations formed by any four adjacent 20 MHz subchannels. Each index corresponds to a location, and the second indicator can indicate the index to notify the station of the 80 MHz puncturing location in the 320 MHz bandwidth.

For the records described in Table 5, the number of record indices that can be indicated by the first pointer, that is, the size and number of punctures that can be indicated, is related to the number of bits of the first pointer. For example, the first pointer may occupy a smaller number of bits and indicate a part of the record indices in Table 5. Accordingly, for punctures of different sizes, the number of record indices of preamble puncture locations that can be indicated by the second pointer is also related to the number of bits of the second pointer. The second pointer may indicate a part or all of the record indices in Table 6.

In another additional implementation, the index table of the preamble puncturing indicator information includes various possible preamble puncturing information. In other words, the number of bits required for the pointer in the preamble puncturing indicator information must be able to separately indicate various possible preamble puncturing information.

For example, Table 7 includes preamble puncturing information about any 20 MHz subchannel in a 320 MHz bandwidth, a 40 MHz subchannel formed by any two adjacent 20 MHz subchannels, a 60 MHz subchannel formed by any three adjacent 20 MHz subchannels, and an 80 MHz subchannel formed by any four adjacent 20 MHz subchannels.

Table 7. Preamble Puncture Indicator Information Index Table Index Description Number of entries 0-15 Preamble Puncture Size 20 MHz 15 or 16 (with 15 entries, it is assumed that the primary 20 MHz channel is not punctured, and any of the other fifteen 20 MHz channels can be punctured). If flexible puncturing on a 20 MHz subchannel in a 160 MHz subchannel is supported, only 7 or 8 entries are required. 16-30 Preamble puncture size is 40 MHz. 15 31-44 Preamble Puncture Size 60 MHz 14 45-57 Preamble Puncture Size 80 MHz 13 58 Without piercing the preamble 1 ... ... ...

If necessary, the status of the preamble puncturing information that can be included in Table 7 is related to the number of bits of the preamble puncturing indicator information. If two puncturings are supported in a passband, the preamble puncturing information included in Table 7 can be expanded accordingly. If necessary, the preamble puncturing indicator information can occupy a smaller number of bits to indicate a part of the entries in Table 7.

If necessary, the second pointer may indicate the preamble puncture absence status based on Table 7. If necessary, the preamble puncture absence status may be indicated by the first pointer. In other words, an index corresponding to the preamble puncture absence case may be added to Table 6.

Method 3. The preamble puncturing indicator information indicates the preamble puncturing information with reference to the bandwidth indicator information

Unlike the previous implementations in which the preamble puncturing indicator information indicates the preamble puncturing information in the passband, the present application further provides another method for indicating the preamble puncturing information. In the indicating method, the passband indicator information and the preamble puncturing indicator information jointly indicate the preamble puncturing information in the passband.

In an additional implementation, the bandwidth indicator information indicates whether preamble puncturing exists in the data packet. If preamble puncturing exists, the bandwidth indicator information may indicate the preamble puncturing status on the primary 80 MHz channel. The preamble puncturing indicator information indicates another preamble puncturing status in the data packet to support more puncturing. For example, the bandwidth field indicates a specific puncturing, and the preamble puncturing indicator information additionally indicates one or two puncturing. In the case of no preamble puncturing or non-puncture mode, the preamble puncturing information does not need to be indicated in the trigger frame or in the data packet.

With reference to the embodiment described in Fig. 12, whether a trigger frame or a data packet includes preamble puncturing indicator information, or whether the preamble puncturing information is indicated using a resource block allocation subfield, relates to a transmission mode of a data packet or relates to a transmission mode of a data packet, and bandwidth indicator information or relates to bandwidth indicator information.

The bandwidth indicator information can be a bandwidth field in the trigger frame or in the data packet.

For example, the preamble puncturing status of a data packet indicated by the bandwidth indicator information is shown in Table 8. Each index corresponds not only to the bandwidth of a data packet but also to the preamble puncturing status of the primary 80 MHz channel. "80 MHz no puncturing mode" indicates no preamble puncturing in the bandwidth. "80+80 MHz" indicates a non-adjacent bandwidth of 160 MHz formed by two 80 MHz subchannels. "160+80 MHz" indicates a non-adjacent bandwidth of 240 MHz formed by a 160 MHz subchannel and an 80 MHz subchannel. The bandwidth of a data packet corresponding to indices 6, 8, 10, and 12 and the preamble puncturing statuses on the primary 80 MHz channel are the general preamble puncturing statuses of a data packet. When the bandwidth indicator information is 6, the data packet cannot be sent or received with reference to the preamble puncturing indicator information. When the bandwidth indicator information is 0, 1, 2, 3, 4 or 5, it clearly indicates that the data packet does not have preamble puncturing. Thus, the data packet does not need to be sent or received with reference to the preamble puncturing indicator information. When the bandwidth indicator information is 7, 8, 9, 10, 11, 12 or 13, the preamble puncturing information of the data packet needs to be further determined with reference to the preamble puncturing indicator information. When the bandwidth indicator information is 8, 10 or 12, the preamble puncturing status on P80 can be determined based on Table 8, and the preamble puncturing status on another channel can be determined with reference to the preamble indicator information.

It can be learned that the method of specifying the preamble puncturing information in this implementation can reduce the overhead of the preamble puncturing indicator information, or can specify when to receive or send a data packet based on the preamble puncturing indicator information, and when not to receive or send a data packet based on the preamble puncturing indicator information. This can reduce the signaling overhead.

Table 8. Bandwidth Indicator Information Index Table Record index Meaning 0 20 MHz 1 40 MHz 2 80 MHz no puncturing mode 3 160 MHz or 80+80 MHz without piercing 4 240 MHz or 160+80 MHz without piercing 5 320 MHz or 160+160 MHz without piercing 6 80 MHz piercing mode, in which only the secondary 20 MHz channel (secondary 20 MHz, S20) is pierced. 7 80 MHz piercing mode, in which only the 20 MHz subchannel of the 40 MHz secondary channel (secondary 40 MHz, S40) is pierced. 8 160 MHz piercing mode, which pierces only the secondary 20 MHz (S20) channel in P80 (the subchannel of 80 MHz that P20 is in). 9 A 160 MHz puncturing mode in which P40 exists in P80 (the 80 MHz subchannel in which P20 resides) and at least one 20 MHz subchannel of the non-P40 MHz portion is puncturing. 10 240 MHz piercing mode, which pierces only the secondary 20 MHz (S20) channel in P80 (the subchannel of 80 MHz that P20 is in). 11 A 240 MHz puncturing mode in which P40 exists in P80 (the 80 MHz subchannel in which P20 resides) and at least one 20 MHz subchannel of the non-P40 MHz portion is punctured. 12 320 MHz piercing mode, which pierces only the secondary 20 MHz (S20) channel in P80 (the subchannel of 80 MHz that P20 is in). 13 A 320 MHz puncturing mode in which P40 exists in P80 (the 80 MHz subchannel in which P20 resides) and at least one 20 MHz subchannel of the non-P40 MHz portion is puncturing. 14 Reserved 15 Reserved

[00240] For the entries described in table 8, the bandwidth indicator information may determine, based on the number of bits of the bandwidth indicator information, the number of entry indices that may be indicated. For example, the bandwidth indicator information may occupy a smaller number of bits to indicate a portion of the entries in table 8.

In this embodiment of the present application, a data packet is transmitted in an orthogonal frequency division multiple access (OFDMA) mode, and a station determines a plurality of allocated resource blocks based on a resource block allocation subfield. In OFDMA transmission, discrete resource blocks obtained after puncturing a preamble need to be allocated to a plurality of different stations. Therefore, it is necessary to use a resource block allocation subfield in a trigger frame or in a signaling field to indicate possible aggregation of resource blocks. As shown in Table 9, the resource blocks corresponding to sequence numbers 0-67 are individual resource blocks, and the resource blocks corresponding to sequence numbers 68-130 are a combination or integration of a plurality of resource blocks. It can be learned that for OFDMA transmission, the resource block allocation subfield can indicate these indices to notify each station of the resource block allocated to the station.

In Table 9, corresponding to indices 72-79, on a 20 MHz subchannel in a bandwidth of 80 MHz, in a solution with a combination of a 52-tone RU and a 26-tone RU adjacent on the same side on a 20 MHz subchannel, "adjacent on the same side" refers to the location of the 20 MHz subchannel in the bandwidth of 80 MHz. The frequencies of the 80 MHz bandwidth increase from left to right. If the 20 MHz subchannel is to the left of the central location in the bandwidth of 80 MHz, "adjacent on the same side" is "adjacent on the left side". If the 20 MHz subchannel is to the right of the central location in the bandwidth of 80 MHz, "adjacent on the same side" is "adjacent on the right side". For example, with reference to the schematic representation of the resource block allocation shown in Fig. 8 it is assumed that the 20 MHz subchannel is the 20 MHz subchannel with the lowest frequency in the 80 MHz bandwidth. Thus, "same-side adjacent" means "left-side adjacent", and the 52-tone RU is the second 52-tone RU on the 20 MHz subchannel. In this case, the 26-tone RU that is on the 20 MHz subchannel and that is on the same side as the 52-tone RU is the second 26-tone RU on the 20 MHz subchannel. Thus, on the 20 MHz subchannel with the lowest frequency in the 80 MHz bandwidth, the solution with the combination of the 52-tone RU and the same-side adjacent 26-tone RU on the 20 MHz subchannel is: the combination of the second 26-tone RU and the second 52-tone RU on the 20 MHz subchannel.

Accordingly, solutions with RU combinations indicated by other indices can be determined with reference to Fig. 8, and the details are not described here again.

Table 9. Table of resource block allocation subfield indexes Record index Description Number of entries 0-36 Possible 26-tone RUs on 80 MHz subchannel 37 37-52 Possible 52-tone RUs on 80 MHz subchannel 16 53-60 Possible 106-tone RUs on 80 MHz subchannel 8 61-64 Possible 242-tone RUs on 80 MHz subchannel 4 65-66 Possible 484-tone RUs on 80 MHz subchannel 2 67 996-tone RU on 80 MHz subchannel 1 68-70 Two 996-tone RU 3 71 Four 996-tone RU 1 72-79 Combination of 106-tone RU on 20 MHz subchannel in 80 MHz subchannel and central 26-tone RU on 20 MHz subchannel 8 80-87 Combination of 52-tone RU and adjacent 26-tone RU on the same side on 20 MHz subchannel in 80 MHz subchannel 8 88-89 Combination of 484-tone RU and adjacent 242-tone RU on 80 MHz subchannel 2 90-91 Combination of 484-tone RU and non-adjacent 242-tone RU on 80 MHz subchannel 2 92 Combination of two 242-tone RUs on both sides of an 80 MHz subchannel 1 93-94 Combination of the currently specified 996-tone RU and the 484-tone RU on the adjacent 80 MHz subchannel
996+484 (lowest frequency or leftmost 484-tone RU)
996+484 (highest frequency or rightmost 484-tone RU) 2 95-98 Combination of the currently specified 996-tone RU and 484-tone RU + 242-tone RU on the adjacent 80 MHz subchannel 4 99-101 Combination of the current 996-tone RU and two of the other three 996-tone RUs 3 102-117 Combination of 484-tone RU + 242-tone RU on the currently specified 80 MHz subchannel and 484-tone RU + 242-tone RU on the adjacent 80 MHz subchannel 16 118 Combination of the currently specified 996-tone RU and two 242-tone RUs on the far side on an adjacent 80 MHz subchannel 1 119-122 Combination of 996-tone RU on current 80 MHz subchannel and 996-tone RU + 484-tone RU on two other 80 MHz subchannels with 240 MHz bandwidth 4 123-128 Combination of 996-tone RU on current 80 MHz subchannel and 2×996+484-tone RUs on three other 80 MHz subchannels with 320 MHz bandwidth 6 129-130 Combination of 106-tone RU + central 26-tone RU on 80 MHz subchannel 2

When the resource block allocation subfield occupies 7 bits, the resource block allocation subfield may indicate a portion of the records or an instance of the RU combination in Table 9. In other words, for the records described in Table 9, the resource block allocation subfield may determine, based on the number of bits of the resource block allocation subfield, the number of record indices that can be indicated. For example, the resource block allocation subfield may occupy fewer bits to indicate a portion of the records in Table 9.

For non-OFDMA transmission, various types of preamble puncturing information may be alternatively configured in a preamble puncturing indicator information index table, for example, as shown in Table 10. In addition, for the entries described in Table 10, the preamble puncturing indicator information may determine, based on the number of bits of the bandwidth indicator information, the number of indexes of entries that may be indicated. For example, the preamble puncturing indicator information may occupy a smaller number of bits to indicate a portion of the entries in Table 10.

Table 10. Preamble Puncture Indicator Information Index Table Record index Description Number of entries 0-15 Preamble Puncture Size 20 MHz 15 or 16 (with 15 entries it is assumed that the primary 20 MHz channel is not punctured and any of the other fifteen 20 MHz channels can be punctured). If flexible puncturing on a 20 MHz subchannel in a 160 MHz subchannel is supported, only 7 or 8 entries are required. 16-30 Preamble Puncture Size 40 MHz 15 31-44 Preamble Puncture Size 60 MHz 14 45-57 Preamble Puncture Size 80 MHz 13 58 Without piercing the preamble 1 ... ... ...

If necessary, the RU allocation decision for OFDMA transmission in Table 9 and the preamble puncturing information for non-OFDMA transmission in Table 10 may be located in a single index table, as shown in Table 11. Table 11 includes the preamble puncturing information from Table 10 when there is one puncturing in the preamble puncturing. If necessary, Table 11 may also include all the preamble puncturing information in Table 10. The preamble puncturing indicator information may reuse the resource block allocation subfield, so that the station can determine the transmission mode of the data packet and the preamble puncturing status based on the index indicated in the preamble puncturing indicator information.

Table 11 Record index Description Number of entries 0-36 Possible 26-tone RUs on 80 MHz subchannel 37 37-52 Possible 52-tone RUs on 80 MHz subchannel 16 53-60 Possible 106-tone RUs on 80 MHz subchannel 8 61-64 Possible 242-tone RUs on 80 MHz subchannel 4 65-66 Possible 484-tone RUs on 80 MHz subchannel 2 67 996-tone RU on 80 MHz subchannel 1 68-70 Two 996-tone RU 3 71 Four 996-tone RU 1 72-79 Combination of 106-tone RU on 20 MHz subchannel in 80 MHz subchannel and central 26-tone RU on 20 MHz subchannel 8 80-87 Combination of 52-tone RU and adjacent 26-tone RU on the same side on a 20 MHz subchannel in an 80 MHz subchannel 8 88-89 Combination of 484-tone RU and adjacent 242-tone RU on 80 MHz subchannel 2 (These two entries indicate the lowest frequency 484-tone RU of the highest frequency 484-tone RU) 90-91 Combination of 484-tone RU and non-adjacent 242-tone RU on 80 MHz subchannel 2 (These two entries indicate the lowest frequency 484-tone RU of the highest frequency 484-tone RU) 92 Combination of two 242-tone RUs on both sides of an 80 MHz subchannel 1 93-94 Combination of 996-tone RU and 484-tone RU on adjacent 80 MHz subchannel:
996-tone RU + 484-tone RU (484-tone RU is the leftmost or lowest frequency 484-tone RU)
996-tone RU + 484-tone RU (484-tone RU is the rightmost or highest frequency 484-tone RU) 2 95-98 Combination of the currently specified 996-tone RU and 484-tone RU + 242-tone RU on the adjacent 80 MHz subchannel 4 99-101 Combination of the current 996-tone RU and two of the other three 996-tone RUs 3 102 BW=320, 140+140
For example, a 60 MHz puncture formed by a 20 MHz subchannel filled with grids and a 40 MHz subchannel shown in Fig. 18 1 (one puncture, if one puncture) 103-104 BW=320, 140+120
For example, a 60 MHz puncture formed by a 20 MHz subchannel and a 40 MHz subchannel filled with the grids shown in Fig. 19; as another example, a puncture formed by a 40 MHz subchannel in the lowest frequency 160 MHz subchannel and a 20 MHz subchannel in the highest frequency 160 MHz subchannel. 2 (one puncture, if one puncture) 105-106 BW=320, 160+100
By referring to the above-mentioned preamble puncturing information in each passband, preamble puncturing information corresponding to two indices can be obtained accordingly. The details are not described again here. 2 (one puncture, if one puncture) 107 BW=320, 120+120
By referring to the above-mentioned preamble puncturing information in each passband, preamble puncturing information corresponding to two indices can be obtained accordingly. The details are not described again here. 1 (one puncture, if one puncture) 108-109 BW=240, 140+60
For example, a 40 MHz puncture formed by 20 MHz subchannels filled with the grids shown in Fig. 24; as another example, a puncture formed by a 20 MHz subchannel in the lowest frequency 80 MHz subchannel and a 40 MHz subchannel in the highest frequency 160 MHz subchannel. 2 (one puncture, if one puncture) 110-111 BW=240, 120+60
For example, a 60 MHz puncture formed by a 40 MHz subchannel and a 20 MHz subchannel filled with the grids shown in Fig. 25 and Fig. 26 2 (one puncture, if one puncture) 112-113 BW=240, 140+40
By referring to the above-mentioned preamble puncturing information in each passband, preamble puncturing information corresponding to two indices can be obtained accordingly. The details are not described again here. 2 (one puncture, if one puncture) 114-115 BW=240, 120+40
By referring to the above-mentioned preamble puncturing information in each passband, preamble puncturing information corresponding to two indices can be obtained accordingly. The details are not described again here. 2 (one puncture, if one puncture) 116-117 A combination of the currently specified 996-tone RU and two 242-tone RUs on the far side on an adjacent 80 MHz subchannel. 1 118-121 Combination of RU 996+484-tone RU on the current 80 MHz subchannel and RU 996+484-tone RU on two other 80 MHz subchannels with a bandwidth of 240 MHz 4 122-127 Combination of 996-tone RU on current 80 MHz subchannel and 2×996+484-tone RU on three other 80 MHz subchannels with 320 MHz bandwidth 6 128-131 Combination of 106-tone RU + central 26-tone RU on 80 MHz subchannel 2

For the entries described in Table 11, the resource block allocation subfield or preamble puncturing indicator information may determine, based on the number of bits of the resource block allocation subfield or preamble puncturing indicator information, the number of entry indices that can be specified. For example, a smaller number of bits may be occupied to specify a portion of the entries in Table 11.

In the case where data transmission is performed based on the resource block allocation subfield, in addition to directly indicating the resource block allocation method corresponding to each index as shown in Table 9, in this application, the resource block allocation subfield includes a resource block pointer and a resource block aggregation pointer.

If necessary, when the first resource block indicated by the resource block indicator is a 2x996-tone resource block, the resource block aggregation indicator indicates one or more of the following resource block aggregations: no resource block is aggregated with the first resource block; the second resource block is aggregated with the first resource block, where the second resource block is a 484-tone resource block adjacent to the first resource block or not adjacent to it; the third resource block is aggregated with the first resource block, where the third resource block is a 484-tone resource block adjacent to the first resource block with a low frequency, or a 484-tone resource block adjacent to the first resource block with a high frequency; or the second resource block and the third resource block are aggregated with the first resource block.

"A resource block adjacent to the first resource block with a low frequency" refers to a resource block that is adjacent to the first resource block and whose frequency is lower than the frequency of the first resource block. As shown in Fig. 8, the 52-tone RU adjacent to the second 106-tone RU with a low frequency is the second 52-tone RU shown in Fig. 8. "A resource block adjacent to the first resource block with a high frequency" refers to a resource block that is adjacent to the first resource block and whose frequency is higher than the frequency of the first resource block. As shown in Fig. 8, the 52-tone RU adjacent to the second 106-tone RU with a high frequency is the fifth 52-tone RU shown in Fig. 8.

If necessary, when the first resource block indicated by the resource block indicator is a 996-tone resource block, the resource block aggregation indicator indicates one or more of the following resource block aggregations: no resource block is aggregated with the first resource block; or a second resource block is aggregated with the first resource block, where the second resource block is a 484-tone resource block, adjacent to or non-adjacent to the first resource block.

The above implementations describe methods for indicating preamble puncture information. In the embodiment shown in Fig. 12, for non-OFDMA transmission, a data packet is sent or received based on preamble puncture indicator information. Thus, in a further implementation, in the case of non-OFDMA transmission, the user field in the trigger frame shown in Fig. 10 may not include the RU allocation subfield and may not include the preamble puncture indicator information (or preamble puncture info). Accordingly, the common field in the extremely high throughput signaling field shown in Fig. 11 may also not include the RU allocation subfield and may not include the preamble puncture indicator information (or preamble puncture info).

In another additional implementation, in the case of non-OFDMA transmission, the user field in the trigger frame shown in Fig. 10 may use the RU allocation subfield to indicate preamble puncture indicator information (or preamble puncture info). Accordingly, the common field in the extremely high throughput signaling field shown in Fig. 11 may also use the RU allocation subfield to indicate preamble puncture indicator information (or preamble puncture info).

The above embodiments of the present application describe the method provided in the embodiments of the present application from the perspective of an access point and a station. In order to implement the functions in the method provided in the embodiments of the present application, the access point and the station may include a hardware structure and a software module, and implement the functions as a hardware structure, a software module, or a combination of a hardware structure and a software module. The function of the above functions may be implemented as a hardware structure, a software module, or a combination of a hardware structure and a software module.

Referring to Fig. 27, Fig. 27 is a schematic diagram illustrating the structure of a data transmission device according to an embodiment of the present application. The data transmission device 2700 shown in Fig. 27 may include a communication unit 2701 and a processing unit 2702. The communication unit 2701 may include a sending unit and a receiving unit. The sending unit is configured to implement a sending function, the receiving unit is configured to implement a receiving function, and the communication unit 2701 may implement a sending function and/or a receiving function. The communication unit may also be described as a transceiver unit.

The data communication device 2700 may be a station, a device in a station, an access point, or a device in an access point.

In the implementation, the data transmission device 2700 includes a communication unit 2701 and a processing unit 2702.

The communication unit 2701 is configured to receive preamble puncturing indicator information. The preamble puncturing indicator information includes one or more indicators, one indicator corresponds to one piece of preamble puncturing information, and the preamble puncturing information includes the size and location of the preamble puncturing, or there is no preamble puncturing.

The communication unit 2701 is further configured to send or receive a data packet based on the preamble puncturing indicator information.

If necessary, the data transmission device additionally includes a processing unit 2702. The processing unit 2702 is configured to determine a plurality of allocated resource blocks based on the information of the preamble puncturing indicator.

It can be known that the data transmission device can indicate the preamble puncturing status in the data packet based on the preamble puncturing indicator information to know the allocated multiple resource blocks. Compared with the existing method of directly indicating multiple resource blocks, the preamble puncturing indicator information in the present application can reduce the signaling overhead.

In an additional implementation, the pointer specifies one or more pieces of the following preamble puncturing information in a 160 MHz channel:

20 MHz subchannel in 160 MHz channel;

a 40 MHz subchannel formed by any two 20 MHz subchannels in a 160 MHz channel;

a 60 MHz subchannel formed by any three 20 MHz subchannels in a 160 MHz channel;

an 80 MHz subchannel formed by any four 20 MHz subchannels in a 160 MHz channel; or

in the 160 MHz channel there is no preamble puncturing.

It can be learned that this implementation can specify the case in which a 40 MHz subchannel, a 60 MHz subchannel, or an 80 MHz subchannel formed by adjacent or non-adjacent 20 MHz subchannels is punctured. This allows for greater flexibility in preamble puncturing.

In an additional implementation, the 160 MHz channel includes an 80 MHz subchannel with the highest frequency and an 80 MHz subchannel with the lowest frequency. The pointer additionally indicates the following piece of preamble puncturing information in the 160 MHz channel:

a subchannel with a center frequency of 40 MHz in a subchannel with the highest frequency of 80 MHz, or a subchannel with a center frequency of 40 MHz in a subchannel with the lowest frequency of 80 MHz.

In an additional implementation, the data packet bandwidth is 320 MHz. The preamble puncturing indicator information includes a first indicator and a second indicator.

The first pointer indicates the preamble puncturing information in the lowest frequency channel of 160 MHz in a bandwidth of 320 MHz.

The second pointer indicates the preamble puncturing information in the subchannel with the highest frequency of 160 MHz in the 320 MHz bandwidth.

In an additional implementation, the pointer specifies one or more pieces of the following preamble puncturing information in the 80 MHz channel:

20 MHz subchannel in 80 MHz channel;

a 40 MHz subchannel formed by any two 20 MHz subchannels in an 80 MHz channel;

a 60 MHz subchannel formed by any three 20 MHz subchannels in an 80 MHz channel;

in the 80 MHz channel there is no preamble puncturing.

It can be learned that this implementation can specify the case in which a 40 MHz subchannel or a 60 MHz subchannel formed by adjacent or non-adjacent 20 MHz subchannels is punctured. This allows for greater flexibility in preamble puncturing.

In an additional implementation, the data packet bandwidth is 240 MHz. The preamble puncturing indicator information includes a first indicator and a second indicator. The first indicator indicates preamble puncturing information in the subchannel with the lowest frequency of 160 MHz in the bandwidth of 240 MHz; and the second indicator indicates preamble puncturing information in the subchannel with the highest frequency of 80 MHz in the bandwidth of 240 MHz.

In an additional implementation, the data packet bandwidth is 160 MHz. The preamble puncturing indicator information includes a first indicator. The first indicator indicates preamble puncturing information in a bandwidth of 160 MHz.

In another additional implementation, the bandwidth of the data packet is 160 MHz. The preamble puncturing indicator information includes a first indicator and a second indicator. The first indicator indicates preamble puncturing information in the subchannel with the lowest frequency of 80 MHz in the bandwidth of 160 MHz; and the second indicator indicates preamble puncturing information in the subchannel with the highest frequency of 80 MHz in the bandwidth of 160 MHz.

In yet another further implementation, the bandwidth of the data packet is 160 MHz. The preamble puncturing indicator information includes a first indicator and a second indicator. The first indicator indicates preamble puncturing information of the first puncture in the bandwidth of 160 MHz; and the second indicator indicates preamble puncturing information of the second puncture in the bandwidth of 160 MHz.

In an additional implementation, the preamble puncturing indicator information includes a first indicator and a second indicator. The first indicator indicates the size of the preamble puncturing, and the second indicator indicates the location of the preamble puncturing.

In an additional implementation, the preamble puncturing size indicated by the first indicator is 20 MHz, and the preamble puncturing location includes one or more of the following: a 20 MHz subchannel in the data packet bandwidth.

The preamble puncturing size indicated by the first designator is 40 MHz, and the preamble puncturing location includes one or more of the following: a 40 MHz subchannel formed by any two 20 MHz subchannels in the data packet bandwidth.

The preamble puncturing size indicated by the first designator is 60 MHz, and the preamble puncturing location includes one or more of the following: a 60 MHz subchannel formed by any three 20 MHz subchannels in the data packet bandwidth.

The preamble puncturing size indicated by the first designator is 80 MHz, and the preamble puncturing location includes one or more of the following: an 80 MHz subchannel formed by any four 20 MHz subchannels in the data packet bandwidth.

In an additional implementation, the first pointer or the second pointer further indicates that there is no preamble puncturing.

In an additional implementation, the station performs a step of sending or receiving a data packet based on preamble puncturing indicator information when the data packet is transmitted in a non-orthogonal frequency division multiple access (non-OFDMA) mode.

In an additional implementation, the station sends or receives a data packet based on a resource block allocation subfield when the data packet is transmitted in an orthogonal frequency division multiple access (OFDMA) mode. Accordingly, the communication unit 2701 is further configured to receive transmission mode indicator information. The transmission mode indicator information indicates a transmission mode of the data packet.

It is possible to know that the data transmission device can receive or send a data packet based on the preamble puncturing indicator information for non-OFDMA transmission; and receive or send a data packet based on the resource block allocation subfield for OFDMA transmission. This can reduce the amount of overhead for indicating the allocated resource block.

In an additional implementation, the resource block allocation subfield includes a resource block pointer and a resource block aggregation pointer. When the first resource block pointed to by the resource block pointer is a 2x996 tone resource block, the resource block aggregation pointer points to one or more of the following resource block aggregations:

no resource block is aggregated with the first resource block;

the second resource block is aggregated with the first resource block, where the second resource block is a 484-tone resource block adjacent to or non-adjacent to the first resource block;

a third resource block is aggregated with the first resource block, where the third resource block is a 484-tone resource block adjacent to the first resource block at a low frequency, or a 484-tone resource block adjacent to the first resource block at a high frequency; or

the second resource block and the third resource block are aggregated with the first resource block.

In an additional implementation, when the first resource block pointed to by the resource block pointer is a 996-tone resource block, the resource block aggregation pointer points to one or more of the following resource block aggregations:

no resource block is aggregated with the first resource block; or

the second resource block is aggregated with the first resource block, where the second resource block is a 484-tone resource block adjacent to or non-adjacent to the first resource block.

It can be found that the two previous implementations can specify the aggregation of resource blocks crossing 160 MHz subchannels. This allows for greater flexibility in resource allocation to the user.

For a corresponding description of the above implementations, see the associated description of the above embodiments of the method. The details are not described again here.

Referring to Fig. 28, Fig. 28 is a schematic diagram illustrating the structure of another device for transmitting data according to an embodiment of the present application. The data transmission device 2800 may be an access point, a station, or a chip, a chip system, a processor, etc. that support an access point when implementing the above-mentioned method, or a chip, a chip system, a processor, etc. that support a station when implementing the above-mentioned method. The data transmission device may be configured to implement the methods described in the previous embodiments of the method. For details, see the descriptions of the above embodiments of the method.

The data transmission device 2800 may include one or more processors 2801. The processor 2801 may be a general-purpose processor, a specialized processor, etc. The processor 2801 may be configured to control the communication device (e.g., an access point, an access point chip, a station, or a station chip), execute a software program, and process data in the software program.

If necessary, the data communication device 2800 can include one or more memory devices 2802. The memory 2802 can store instructions 2804. The instructions can be executed on the processor 2801, so that the data communication device 2800 performs the methods described in the previous embodiments of the method. If necessary, the memory 2802 can additionally store data. The processor 2801 and the memory 2802 can be located separately or can be combined together.

If necessary, the data transmission device 2800 may further include a transceiver 2805 and an antenna 2806. The transceiver 2805 may be called a transceiver unit, a transceiver machine, a transceiver circuit, etc., and is configured to implement a transceiver function. The transceiver 2805 may include a receiver and a transmitter. The receiver may be called a receiving machine, a receiver circuit, etc., and is configured to implement a receiving function. The transmitter may be called a transmitting machine, a transmitter circuit, etc., and is configured to implement a sending function.

In the data transmission device 2800, the transceiver 2805 is configured to perform the operations in steps 101-103 shown in Fig. 9 and to perform the operations of receiving or sending the corresponding information in steps 201-204 shown in Fig. 12. The processor 2801 is configured to perform the associated parsing operations in steps 203 and 204 shown in Fig. 12.

It can be known that the data transmission device can indicate the preamble puncturing status in the data packet based on the preamble puncturing indicator information to know the allocated multiple resource blocks. Compared with the existing method of directly indicating multiple resource blocks, the preamble puncturing indicator information in the present application can reduce the signaling overhead.

In an additional implementation, the pointer specifies one or more pieces of the following preamble puncturing information in a 160 MHz channel:

20 MHz subchannel in 160 MHz channel;

a 40 MHz subchannel formed by any two 20 MHz subchannels in a 160 MHz channel;

a 60 MHz subchannel formed by any three 20 MHz subchannels in a 160 MHz channel;

an 80 MHz subchannel formed by any four 20 MHz subchannels in a 160 MHz channel; or

in the 160 MHz channel there is no preamble puncturing.

It can be learned that this implementation can specify the case in which a 40 MHz subchannel, a 60 MHz subchannel, or an 80 MHz subchannel formed by adjacent or non-adjacent 20 MHz subchannels is punctured. This allows for greater flexibility in preamble puncturing.

In an additional implementation, the 160 MHz channel includes an 80 MHz subchannel with the highest frequency and an 80 MHz subchannel with the lowest frequency. The pointer additionally indicates the following piece of preamble puncturing information in the 160 MHz channel:

a subchannel with a center frequency of 40 MHz in a subchannel with the highest frequency of 80 MHz, or a subchannel with a center frequency of 40 MHz in a subchannel with the lowest frequency of 80 MHz.

In an additional implementation, the data packet bandwidth is 320 MHz. The preamble puncturing indicator information includes a first indicator and a second indicator.

The first pointer indicates the preamble puncturing information in the lowest frequency channel of 160 MHz in a bandwidth of 320 MHz.

The second pointer indicates the preamble puncturing information in the subchannel with the highest frequency of 160 MHz in the 320 MHz bandwidth.

In an additional implementation, the pointer specifies one or more pieces of the following preamble puncturing information in the 80 MHz channel:

20 MHz subchannel in 80 MHz channel;

a 40 MHz subchannel formed by any two 20 MHz subchannels in an 80 MHz channel;

a 60 MHz subchannel formed by any three 20 MHz subchannels in an 80 MHz channel;

in the 80 MHz channel there is no preamble puncturing.

It can be learned that this implementation can specify the case in which a 40 MHz subchannel or a 60 MHz subchannel formed by adjacent or non-adjacent 20 MHz subchannels is punctured. This allows for greater flexibility in preamble puncturing.

In an additional implementation, the data packet bandwidth is 240 MHz. The preamble puncturing indicator information includes a first indicator and a second indicator. The first indicator indicates preamble puncturing information in the subchannel with the lowest frequency of 160 MHz in the bandwidth of 240 MHz; and the second indicator indicates preamble puncturing information in the subchannel with the highest frequency of 80 MHz in the bandwidth of 240 MHz.

In an additional implementation, the data packet bandwidth is 160 MHz. The preamble puncturing indicator information includes a first indicator. The first indicator indicates preamble puncturing information in a bandwidth of 160 MHz.

In another additional implementation, the bandwidth of the data packet is 160 MHz. The preamble puncturing indicator information includes a first indicator and a second indicator. The first indicator indicates preamble puncturing information in the subchannel with the lowest frequency of 80 MHz in the bandwidth of 160 MHz; and the second indicator indicates preamble puncturing information in the subchannel with the highest frequency of 80 MHz in the bandwidth of 160 MHz.

In yet another further implementation, the bandwidth of the data packet is 160 MHz. The preamble puncturing indicator information includes a first indicator and a second indicator. The first indicator indicates preamble puncturing information of the first puncture in the bandwidth of 160 MHz; and the second indicator indicates preamble puncturing information of the second puncture in the bandwidth of 160 MHz.

In an additional implementation, the preamble puncturing indicator information includes a first indicator and a second indicator. The first indicator indicates the size of the preamble puncturing, and the second indicator indicates the location of the preamble puncturing.

In an additional implementation, the preamble puncturing size indicated by the first indicator is 20 MHz, and the preamble puncturing location includes one or more of the following: a 20 MHz subchannel in the data packet bandwidth.

The preamble puncturing size indicated by the first designator is 40 MHz, and the preamble puncturing location includes one or more of the following: a 40 MHz subchannel formed by any two 20 MHz subchannels in the data packet bandwidth.

The preamble puncturing size indicated by the first designator is 60 MHz, and the preamble puncturing location includes one or more of the following: a 60 MHz subchannel formed by any three 20 MHz subchannels in the data packet bandwidth.

The preamble puncturing size indicated by the first designator is 80 MHz, and the preamble puncturing location includes one or more of the following: an 80 MHz subchannel formed by any four 20 MHz subchannels in the data packet bandwidth.

In an additional implementation, the first pointer or the second pointer further indicates that there is no preamble puncturing.

In an additional implementation, the station performs a step of sending or receiving a data packet based on preamble puncturing indicator information when the data packet is transmitted in a non-orthogonal frequency division multiple access (non-OFDMA) mode.

In an additional implementation, a station sends or receives a data packet based on a resource block allocation subfield when the data packet is transmitted in an orthogonal frequency division multiple access (OFDMA) mode.

It is possible to know that the data transmission device can receive or send a data packet based on the preamble puncturing indicator information for non-OFDMA transmission; and receive or send a data packet based on the resource block allocation subfield for OFDMA transmission. This can reduce the amount of overhead for indicating the allocated resource block.

In an additional implementation, the resource block allocation subfield includes a resource block pointer and a resource block aggregation pointer. When the first resource block pointed to by the resource block pointer is a 2x996 tone resource block, the resource block aggregation pointer points to one or more of the following resource block aggregations:

no resource block is aggregated with the first resource block; or

the second resource block is aggregated with the first resource block, where the second resource block is a 484-tone resource block adjacent to or non-adjacent to the first resource block;

a third resource block is aggregated with the first resource block, where the third resource block is a 484-tone resource block adjacent to the first resource block at a low frequency, or a 484-tone resource block adjacent to the first resource block at a high frequency; or

the second resource block and the third resource block are aggregated with the first resource block.

In an additional implementation, when the first resource block pointed to by the resource block pointer is a 996-tone resource block, the resource block aggregation pointer points to one or more of the following resource block aggregations:

no resource block is aggregated with the first resource block; or

the second resource block is aggregated with the first resource block, where the second resource block is a 484-tone resource block adjacent to or non-adjacent to the first resource block.

It can be found that the two previous implementations can specify the aggregation of resource blocks crossing 160 MHz subchannels. This allows for greater flexibility in resource allocation to the user.

The corresponding content of the above implementations is presented in the related content of the above embodiments of the method. The details are not described again here.

In another possible embodiment, the transceiver may be a transceiver circuit, an interface, or an interface circuit. The transceiver circuit, the interface, or the interface circuit, configured to implement the functions of receiving and sending, may be separated or may be combined together. The transceiver circuit, the interface, or the interface circuit may be configured to read and write code/data. Alternatively, the transceiver circuit, the interface, or the interface circuit may be configured to transmit or carry a signal.

In another possible implementation, the processor 2801 may additionally store instructions 2803. When the instructions 2803 are executed in the processor 2801, the communication device 2800 receives the ability to perform the methods described in the previous embodiments of the method. The instructions 2803 may be built into the processor 2801. In this case, the processor 2801 may be implemented in hardware.

In another possible implementation, the communication device 2800 may include a circuit. The circuit may implement the sending, receiving or communication function in the above-mentioned embodiments of the method.

The processor and transceiver described in this application may be implemented on an integrated circuit (IC), an analog IC, a radio frequency integrated circuit (RFIC), a hybrid signal IC, an application-specific integrated circuit (ASIC), a printed circuit board (PCB), an electronic device, etc.

The communication device described in the previous embodiments may be an access point or a station. However, the scope of the communication device described in this application is not limited to this, and the structure of the communication device may not be limited to Fig. 28. The communication device may be an independent device or may be part of a larger device. For example, the communication device may be:

(1) an independent integrated circuit (IC), microcircuit, or microcircuit system or subsystem;

(2) a set including one or more ICs, where, additionally, the set of ICs may further include a storage component configured to store data and instructions;

(3) ASIC, such as a modem;

(4) a module that can be embedded into another device;

(5) receiver, intelligent terminal, wireless device, portable device, mobile device, vehicle-mounted device, cloud device, artificial intelligence device, etc.;

(6) other devices.

For the case where the communication device can be a microcircuit or a system of microcircuits, reference should be made to the schematic diagram of the structure of the microcircuit shown in Fig. 29. The microcircuit 2900 shown in Fig. 29 includes a processor 2901 and an interface 2902. One or more processors 2901 can be used and a plurality of interfaces 2902 can be used.

In the case where the microcircuit is designed to implement the functions of the station in the embodiments of the present application, the following descriptions should be referred to.

In the implementation, the interface 2902 is configured to receive preamble puncturing indicator information. The preamble puncturing indicator information includes one or more pointers, one pointer corresponds to one piece of preamble puncturing information, and the preamble puncturing information includes the size and location of the preamble puncturing, or there is no preamble puncturing.

The interface 2902 is further configured to send or receive a data packet based on the preamble puncturing indicator information.

If necessary, the data transmission device additionally includes a processor 2901. The processor 2901 is configured to determine a plurality of allocated resource blocks based on the information of the preamble puncturing indicator.

If necessary, the microcircuit additionally includes memory 2903 connected to processor 2901. Memory 2903 is designed with the ability to store program instructions and data that are necessary for the terminal device.

It can be learned that the chip can indicate the preamble puncturing status in the data packet based on the preamble puncturing indicator information to learn about the allocated multiple resource blocks. Compared with the existing method of directly indicating multiple resource blocks, the preamble puncturing indicator information in the present application can reduce the signaling overhead.

In an additional implementation, the pointer specifies one or more pieces of the following preamble puncturing information in a 160 MHz channel:

20 MHz subchannel in 160 MHz channel;

a 40 MHz subchannel formed by any two 20 MHz subchannels in a 160 MHz channel;

a 60 MHz subchannel formed by any three 20 MHz subchannels in a 160 MHz channel;

an 80 MHz subchannel formed by any four 20 MHz subchannels in a 160 MHz channel; or

in the 160 MHz channel there is no preamble puncturing.

It can be learned that this implementation can specify the case in which a 40 MHz subchannel, a 60 MHz subchannel, or an 80 MHz subchannel formed by adjacent or non-adjacent 20 MHz subchannels is punctured. This allows for greater flexibility in preamble puncturing.

In an additional implementation, the 160 MHz channel includes an 80 MHz subchannel with the highest frequency and an 80 MHz subchannel with the lowest frequency. The pointer additionally indicates the following piece of preamble puncturing information in the 160 MHz channel:

a subchannel with a center frequency of 40 MHz in a subchannel with the highest frequency of 80 MHz, or a subchannel with a center frequency of 40 MHz in a subchannel with the lowest frequency of 80 MHz.

In an additional implementation, the data packet bandwidth is 320 MHz. The preamble puncturing indicator information includes a first indicator and a second indicator.

The first pointer indicates the preamble puncturing information in the lowest frequency channel of 160 MHz in a bandwidth of 320 MHz.

The second pointer indicates the preamble puncturing information in the subchannel with the highest frequency of 160 MHz in the 320 MHz bandwidth.

In an additional implementation, the pointer specifies one or more pieces of the following preamble puncturing information in the 80 MHz channel:

20 MHz subchannel in 80 MHz channel;

a 40 MHz subchannel formed by any two 20 MHz subchannels in an 80 MHz channel;

a 60 MHz subchannel formed by any three 20 MHz subchannels in an 80 MHz channel;

in the 80 MHz channel there is no preamble puncturing.

It can be learned that this implementation can specify the case in which a 40 MHz subchannel or a 60 MHz subchannel formed by adjacent or non-adjacent 20 MHz subchannels is punctured. This allows for greater flexibility in preamble puncturing.

In an additional implementation, the data packet bandwidth is 240 MHz. The preamble puncturing indicator information includes a first indicator and a second indicator. The first indicator indicates preamble puncturing information in the subchannel with the lowest frequency of 160 MHz in the bandwidth of 240 MHz; and the second indicator indicates preamble puncturing information in the subchannel with the highest frequency of 80 MHz in the bandwidth of 240 MHz.

In an additional implementation, the data packet bandwidth is 160 MHz. The preamble puncturing indicator information includes a first indicator. The first indicator indicates preamble puncturing information in a bandwidth of 160 MHz.

In another additional implementation, the bandwidth of the data packet is 160 MHz. The preamble puncturing indicator information includes a first indicator and a second indicator. The first indicator indicates preamble puncturing information in the subchannel with the lowest frequency of 80 MHz in the bandwidth of 160 MHz; and the second indicator indicates preamble puncturing information in the subchannel with the highest frequency of 80 MHz in the bandwidth of 160 MHz.

In yet another further implementation, the bandwidth of the data packet is 160 MHz. The preamble puncturing indicator information includes a first indicator and a second indicator. The first indicator indicates preamble puncturing information of the first puncture in the bandwidth of 160 MHz; and the second indicator indicates preamble puncturing information of the second puncture in the bandwidth of 160 MHz.

In an additional implementation, the preamble puncturing indicator information includes a first indicator and a second indicator. The first indicator indicates the size of the preamble puncturing, and the second indicator indicates the location of the preamble puncturing.

In an additional implementation, the preamble puncturing size indicated by the first indicator is 20 MHz, and the preamble puncturing location includes one or more of the following: a 20 MHz subchannel in the data packet bandwidth.

The preamble puncturing size indicated by the first designator is 40 MHz, and the preamble puncturing location includes one or more of the following: a 40 MHz subchannel formed by any two 20 MHz subchannels in the data packet bandwidth.

The preamble puncturing size indicated by the first designator is 60 MHz, and the preamble puncturing location includes one or more of the following: a 60 MHz subchannel formed by any three 20 MHz subchannels in the data packet bandwidth.

The preamble puncturing size indicated by the first designator is 80 MHz, and the preamble puncturing location includes one or more of the following: an 80 MHz subchannel formed by any four 20 MHz subchannels in the data packet bandwidth.

In an additional implementation, the first pointer or the second pointer further indicates that there is no preamble puncturing.

In an additional implementation, the station performs a step of sending or receiving a data packet based on preamble puncturing indicator information when the data packet is transmitted in a non-orthogonal frequency division multiple access (non-OFDMA) mode.

In an additional implementation, the station sends or receives a data packet based on a resource block allocation subfield when the data packet is transmitted in an orthogonal frequency division multiple access (OFDMA) mode. Accordingly, the interface 2902 is further configured to receive transmission mode indicator information. The transmission mode indicator information indicates a transmission mode of the data packet.

It is possible to know that the data transmission device can receive or send a data packet based on the preamble puncturing indicator information for non-OFDMA transmission; and receive or send a data packet based on the resource block allocation subfield for OFDMA transmission. This can reduce the amount of overhead for indicating the allocated resource block.

In an additional implementation, the resource block allocation subfield includes a resource block pointer and a resource block aggregation pointer. When the first resource block pointed to by the resource block pointer is a 2x996 tone resource block, the resource block aggregation pointer points to one or more of the following resource block aggregations:

no resource block is aggregated with the first resource block; or

the second resource block is aggregated with the first resource block, where the second resource block is a 484-tone resource block adjacent to or non-adjacent to the first resource block;

a third resource block is aggregated with the first resource block, where the third resource block is a 484-tone resource block adjacent to the first resource block at a low frequency, or a 484-tone resource block adjacent to the first resource block at a high frequency; or

the second resource block and the third resource block are aggregated with the first resource block.

In an additional implementation, when the first resource block pointed to by the resource block pointer is a 996-tone resource block, the resource block aggregation pointer points to one or more of the following resource block aggregations:

no resource block is aggregated with the first resource block; or

the second resource block is aggregated with the first resource block, where the second resource block is a 484-tone resource block adjacent to or non-adjacent to the first resource block.

It can be found that the two previous implementations can specify the aggregation of resource blocks crossing 160 MHz subchannels. This allows for greater flexibility in resource allocation to the user.

The corresponding content of the above implementations is presented in the related content of the above embodiments of the method. The details are not described again here.

It may be further understood by a person skilled in the art that the various illustrative logical blocks and steps listed in the embodiments of the present application may be implemented using electronic hardware, computer software, or a combination thereof. Whether the functions are implemented using hardware or software depends on the specific applications and the design requirements of the overall system. A person skilled in the art may use different ways of implementing the described functions for each specific application, but it should not be considered that the implementation goes beyond the scope of protection of the embodiments of the present application.

The present application additionally provides a machine-readable information carrier. The machine-readable information carrier stores a computer program, and when the machine-readable information carrier is executed by a computer, the function of any of the above embodiments of the method is implemented.

The present application additionally provides a computer program product. When the computer program product is executed by a computer, the function of any of the above embodiments of the method is implemented.

All or part of the above embodiments may be implemented using software, hardware, firmware, or any combination thereof. When software is used to implement the embodiments, all or part of the embodiments may be implemented as a computer program product. The computer program product includes one or more computer instructions. When the computer instructions are loaded and executed in a computer, all or part of the procedure or functions according to the embodiments of the present application are produced. The computer may be a general-purpose computer, a specialized computer, a computer network, or another programmable device. The computer instructions may be stored on a computer-readable storage medium or may be transmitted from a computer-readable storage medium to another computer-readable storage medium. For example, computer instructions may be transmitted from a website, computer, server, or data center to another website, computer, server, or data center by wire (e.g., coaxial cable, fiber optic cable, or digital subscriber line (DSL)) or wireless (e.g., infrared waves, radio waves, or microwaves). The computer-readable storage medium may be any usable storage medium accessible to a computer or a data storage device, such as a server or data center, incorporating one or more usable storage media. The storage medium used may be a magnetic storage medium (e.g., a floppy disk, hard disk, or magnetic tape), an optical storage medium (e.g., a high-density digital video disc (DVD)), a semiconductor storage medium (e.g., a solid state disk (SSD)) or the like.

It may be understood by one skilled in the art that various numerals such as "first" and "second" are used in this application merely for distinction in order to simplify the description and are not used to limit the scope of the embodiments of the present application or to represent a sequence.

The correspondences shown in the tables of the present application may be configured or may be predetermined. Some values of the information in the tables are simply examples, and other values may be configured. This is not limited in the present application. When the correspondence between the information and each parameter is configured, not all correspondences shown in the tables need to be configured. For example, in the tables of the present application, the correspondences shown in some rows may not be configured. As another example, appropriate changes and adjustments such as splitting and combining can be made based on the above tables. The names of the parameters shown in the headers of the previous tables may alternatively have other names that may be understandable to the communication device, and the values or representation methods of the parameters may alternatively be other values or representation methods that may be understandable to the communication device. When implementing the above tables, another data structure may be used, such as an array, a queue, a container, a stack, a linear table, a pointer, a linked list, a tree, a graph, a structure, a class, a package, or a hash table.

As used in this application, the term "predetermine" may be understood as "define", "predetermine", "store", "pre-store", "pre-align", "pre-configure", "embed", or "pre-record".

A person skilled in the art may know that in combination with the blocks and steps of the algorithm in the examples described in the embodiments disclosed in this description, the present application can be implemented using electronic hardware or a combination of computer software and electronic hardware. Whether the functions are performed using hardware or software depends on the specific applications and design limitations of the technical solutions. A person skilled in the art may use different methods to implement the described functions for each specific application, but it should not be considered that the implementation goes beyond the scope of the present application.

It should be clear to a person skilled in the art that, for the purpose of conveniently and briefly describing the detailed working process of the above-mentioned system, device and unit, reference can be made to the corresponding process in the above embodiment of the method. The details are not described again in this document.

The above descriptions are merely specific implementations of the present application, but are not intended to limit the protection scope of the present application. Any variation or replacement easily found by a person skilled in the art within the technical scope disclosed in the present application shall fall within the protection scope of the present application. Thus, the protection scope of the present application shall correspond to the protection scope of the claims.

Claims (131)

1. A data transfer method comprising: receiving a physical protocol data unit (PPDU), wherein the PPDU comprises a signaling field, and the signaling field comprises preamble puncturing pointer information, wherein the preamble puncturing pointer information comprises one or more pointers, wherein one pointer corresponds to one piece of preamble puncturing information and the preamble puncturing information comprises a size and a location of the preamble puncturing or no preamble puncturing; wherein the signaling field further comprises a bandwidth field, and the bandwidth field comprises bandwidth pointer information for indicating the bandwidth of the data packet; wherein, in case the bandwidth of the data packet is equal to the bandwidth of 160 MHz, the preamble puncturing indicator information contains the first indicator and the second indicator, where the first pointer indicates the preamble puncturing information in the subchannel with the lowest frequency of 80 MHz in the 160 MHz bandwidth; and the second pointer indicates the preamble puncturing information in the subchannel with the highest frequency of 80 MHz in the bandwidth of 160 MHz; sending or receiving a data packet based on the preamble puncturing indicator information. 2. The method according to claim 1, wherein one of the pointers indicates one or more fragments of the following preamble puncturing information in a 160 MHz channel: 20 MHz subchannel in 160 MHz channel; a 40 MHz subchannel formed by any two 20 MHz subchannels in a 160 MHz channel; a 60 MHz subchannel formed by any three 20 MHz subchannels in a 160 MHz channel; an 80 MHz subchannel formed by any four 20 MHz subchannels in a 160 MHz channel; or in the 160 MHz channel there is no preamble puncturing. 3. The method according to claim 2, wherein the 160 MHz channel comprises an 80 MHz subchannel with the highest frequency and an 80 MHz subchannel with the lowest frequency and one of the pointers indicates the following piece of preamble puncturing information in the 160 MHz channel: a subchannel with a center frequency of 40 MHz in a subchannel with the highest frequency of 80 MHz, or a subchannel with a center frequency of 40 MHz in a subchannel with the lowest frequency of 80 MHz. 4. The method according to any one of paragraphs 1-3, in which, in case the bandwidth of the data packet is equal to the bandwidth of 320 MHz, the preamble puncturing indicator information contains the first indicator and the second indicator, where the first pointer indicates the preamble puncturing information in the subchannel with the lowest frequency of 160 MHz in the 320 MHz bandwidth; and The second pointer indicates the preamble puncturing information in the subchannel with the highest frequency of 160 MHz in the 320 MHz bandwidth. 5. The method according to any one of paragraphs 1-4, wherein the first indicator and/or the second indicator indicates one or more pieces of the following preamble puncturing information in the 80 MHz subchannel: frequency range 20 MHz in 80 MHz subchannel; a 40 MHz frequency range formed by any two 20 MHz frequency ranges in an 80 MHz subchannel; a 60 MHz frequency range formed by any three 20 MHz frequency ranges in an 80 MHz subchannel; or in the 80 MHz subchannel there is no preamble puncturing. 6. The method according to any one of paragraphs 1-5, in which, in case the bandwidth of the data packet is equal to the bandwidth of 240 MHz, the preamble puncturing indicator information contains the first indicator and the second indicator, where the first pointer indicates the preamble puncturing information in the subchannel with the lowest frequency of 160 MHz in the 240 MHz bandwidth; and The second pointer indicates the preamble puncturing information in the subchannel with the highest frequency of 80 MHz in the 240 MHz bandwidth. 7. The method according to any one of paragraphs 1-3, in which the preamble piercing pointer information additionally contains a third pointer, where The third pointer indicates the preamble puncturing information in the 160 MHz bandwidth. 8. The method according to any one of paragraphs 1-3, in which the preamble piercing pointer information additionally contains a fourth pointer and a fifth pointer, where the fourth pointer indicates the preamble puncturing information of the first puncture in the 160 MHz bandwidth; and The fifth pointer indicates the preamble puncturing information of the second puncture in the 160 MHz bandwidth. 9. The method according to any one of paragraphs 1-8, in which the preamble piercing pointer information additionally contains a sixth pointer and a seventh pointer; the sixth pointer indicates the size of the preamble puncture; and The seventh pointer indicates the location of the preamble puncture. 10. The method according to item 9, in which the preamble puncturing size indicated by the sixth designator is 20 MHz and the preamble puncturing location contains one or more of the following: a 20 MHz subchannel in the data packet bandwidth; the preamble puncturing size indicated by the sixth designator is 40 MHz and the preamble puncturing location contains one or more of the following: a 40 MHz subchannel formed by any two 20 MHz subchannels in the packet data bandwidth; the preamble puncturing size indicated by the sixth designator is 60 MHz and the preamble puncturing location contains one or more of the following: a 60 MHz subchannel formed by any three 20 MHz subchannels in the packet data bandwidth; and/or the preamble puncturing size specified by the sixth designator is 80 MHz and the preamble puncturing location contains one or more of the following: an 80 MHz subchannel formed by any four 20 MHz subchannels in the data packet bandwidth. 11. The method according to claim 10, wherein the sixth indicator or the seventh indicator further indicates that there is no preamble puncturing. 12. The method according to any one of paragraphs 2, 5 and 7-11, wherein the step of sending or receiving a data packet based on the preamble puncturing indicator information is performed when the data packet is transmitted in a non-orthogonal frequency division multiple access (non-OFDMA) mode. 13. The method according to any one of claims 1, 3, 4 and 6, wherein the method further comprises sending or receiving a data packet based on the resource block allocation subfield when the data packet is transmitted in the orthogonal frequency division multiple access (OFDMA) mode. 14. The method according to claim 12 or 13, wherein the method further comprises receiving transmission mode indicator information, wherein the transmission mode indicator information indicates a transmission mode of a data packet. 15. The method according to claim 13 or 14, wherein the resource block allocation subfield contains a resource block indicator and a resource block aggregation indicator, where, When the first resource block pointed to by the resource block pointer is a 2×996-tone resource block, the resource block aggregation pointer points to one or more of the following resource block aggregations: no resource block is aggregated with the first resource block; the second resource block is aggregated with the first resource block, wherein the second resource block is a 484-tone resource block, adjacent or non-adjacent to the first resource block; a third resource block is aggregated with the first resource block, wherein the third resource block is a 996-tone resource block adjacent to the first resource block with a low frequency, or a 996-tone resource block adjacent to the first resource block with a high frequency; or the second resource block and the third resource block are aggregated with the first resource block. 16. The method according to claim 13 or 14, wherein, When the first resource block specified by the resource block pointer is a 996-tone resource block, the resource block aggregation pointer specifies one or more of the following resource block aggregations: no resource block is aggregated with the first resource block; or the second resource block is aggregated with the first resource block, wherein the second resource block is a 484-tone resource block, adjacent or non-adjacent to the first resource block. 17. A data transmission device comprising a processor, a memory and a transceiver, in which: the transceiver is configured to receive preamble puncturing indicator information and send or receive a data packet based on the preamble puncturing indicator information, wherein the preamble puncturing indicator information indicates preamble puncturing information of the data packet; the memory is designed to store program code; and the processor is configured to call up program code from memory to perform the method according to any of paragraphs 1-16. 18. A data transmission microcircuit system comprising a processor and an interface in which the interface is configured to receive a physical protocol data unit (PPDU), where the PPDU comprises a signaling field, and the signaling field comprises preamble puncturing indicator information, wherein the preamble puncturing indicator information comprises one or more pointers, one pointer corresponds to preamble puncturing information of a data packet, and the preamble puncturing information comprises a size and a location of a preamble puncturing or there is no preamble puncturing; wherein the signaling field further comprises a bandwidth field, and the bandwidth field comprises bandwidth indicator information for indicating the bandwidth of the data packet; where, in case the bandwidth of the data packet is equal to the bandwidth of 160 MHz, the preamble puncturing indicator information contains the first indicator and the second indicator, where the first pointer indicates the preamble puncturing information in the subchannel with the lowest frequency of 80 MHz in the 160 MHz bandwidth; and the second pointer indicates the preamble puncturing information in the subchannel with the highest frequency of 80 MHz in the bandwidth of 160 MHz; the processor is configured to determine a plurality of allocated resource blocks based on the preamble puncturing indicator information; and the interface is further configured to send or receive a data packet on a plurality of resource blocks. 19. A machine-readable information carrier, in which the machine-readable information carrier is configured to store instructions and, when the instructions are executed, the method according to any one of paragraphs 1-16 is implemented. 20. A data transmission device comprising: a communication unit configured to receive a physical protocol data unit (PPDU), wherein the PPDU comprises a signaling field, and the signaling field comprises preamble puncturing indicator information, wherein the preamble puncturing indicator information comprises one or more pointers, one pointer corresponds to one piece of preamble puncturing information, and the preamble puncturing information comprises a size and a location of the preamble puncturing or there is no preamble puncturing; wherein the signaling field further comprises a bandwidth field, and the bandwidth field comprises bandwidth indicator information for indicating a bandwidth of the data packet; wherein, in case the bandwidth of the data packet is equal to the bandwidth of 160 MHz, the preamble puncturing indicator information contains the first indicator and the second indicator, where the first pointer indicates the preamble puncturing information in the subchannel with the lowest frequency of 80 MHz in the 160 MHz bandwidth; and the second pointer indicates the preamble puncturing information in the subchannel with the highest frequency of 80 MHz in the 160 MHz bandwidth; and a processing unit configured to determine a plurality of allocated resource blocks based on the preamble puncturing indicator information; and the communication unit is additionally configured to send or receive a data packet on a plurality of allocated resource blocks. 21. The device of claim 20, wherein one of the pointers indicates one or more fragments of the following preamble puncturing information in a 160 MHz channel: 20 MHz subchannel in 160 MHz channel; a 40 MHz subchannel formed by any two 20 MHz subchannels in a 160 MHz channel; a 60 MHz subchannel formed by any three 20 MHz subchannels in a 160 MHz channel; an 80 MHz subchannel formed by any four 20 MHz subchannels in a 160 MHz channel; or in the 160 MHz channel there is no preamble puncturing. 22. The device of claim 21, wherein the 160 MHz channel comprises an 80 MHz subchannel with the highest frequency and an 80 MHz subchannel with the lowest frequency and one of the pointers indicates the following piece of preamble puncturing information in the 160 MHz channel: a subchannel with a center frequency of 40 MHz in a subchannel with the highest frequency of 80 MHz, or a subchannel with a center frequency of 40 MHz in a subchannel with the lowest frequency of 80 MHz. 23. A device according to any one of paragraphs 20-22, in which, in case the bandwidth of the data packet is equal to the bandwidth of 320 MHz, the preamble puncturing indicator information contains the first indicator and the second indicator, where the first pointer indicates the preamble puncturing information in the subchannel with the lowest frequency of 160 MHz in the 320 MHz bandwidth; and The second pointer indicates the preamble puncturing information in the subchannel with the highest frequency of 160 MHz in the 320 MHz bandwidth. 24. The device according to any one of paragraphs 20-23, in which the first indicator and/or the second indicator indicates one or more pieces of the following preamble puncturing information in the 80 MHz subchannel: frequency range 20 MHz in 80 MHz subchannel; a 40 MHz frequency range formed by any two 20 MHz frequency ranges in an 80 MHz subchannel; a 60 MHz frequency range formed by any three 20 MHz frequency ranges in an 80 MHz subchannel; or in the 80 MHz subchannel there is no preamble puncturing. 25. A device according to any one of paragraphs 20-24, in which, in case the bandwidth of the data packet is equal to the bandwidth of 240 MHz, the preamble puncturing indicator information contains the first indicator and the second indicator, where the first pointer indicates the preamble puncturing information in the subchannel with the lowest frequency of 160 MHz in the 240 MHz bandwidth; and The second pointer indicates the preamble puncturing information in the subchannel with the highest frequency of 80 MHz in the 240 MHz bandwidth. 26. A device according to any one of paragraphs 20-22, in which the preamble piercing pointer information additionally contains a third pointer, where The third pointer indicates the preamble puncturing information in the 160 MHz bandwidth. 27. A device according to any one of paragraphs 20-22, in which the preamble piercing pointer information additionally contains a fourth pointer and a fifth pointer, where the fourth pointer indicates the preamble puncturing information of the first puncture in the 160 MHz bandwidth; and The fifth pointer indicates the preamble puncturing information of the second puncture in the 160 MHz bandwidth. 28. A device according to any one of paragraphs 20-27, in which the preamble piercing pointer information additionally contains a sixth pointer and a seventh pointer; the sixth pointer indicates the size of the preamble puncture; and The seventh pointer indicates the location of the preamble puncture. 29. The device according to item 28, in which the preamble puncturing size indicated by the sixth designator is 20 MHz and the preamble puncturing location contains one or more of the following: a 20 MHz subchannel in the data packet bandwidth; the preamble puncturing size indicated by the sixth designator is 40 MHz and the preamble puncturing location contains one or more of the following: a 40 MHz subchannel formed by any two 20 MHz subchannels in the packet data bandwidth; the preamble puncturing size indicated by the sixth designator is 60 MHz and the preamble puncturing location contains one or more of the following: a 60 MHz subchannel formed by any three 20 MHz subchannels in the packet data bandwidth; and/or the preamble puncturing size specified by the sixth designator is 80 MHz and the preamble puncturing location contains one or more of the following: an 80 MHz subchannel formed by any four 20 MHz subchannels in the data packet bandwidth. 30. The device of claim 29, wherein the sixth indicator or the seventh indicator further indicates that there is no preamble piercing. 31. The device according to any one of claims 21, 24 and 26-30, in which the processing unit is configured to perform an operation of determining a plurality of allocated resource blocks based on the preamble puncturing indicator information when the data packet is transmitted in a non-orthogonal frequency division multiple access (non-OFDMA) mode. 32. The device according to any one of claims 20, 22, 23 and 25, in which the processing unit is further configured to determine a plurality of allocated resource blocks based on the resource block allocation subfield when the data packet is transmitted in an orthogonal frequency division multiple access (OFDMA) mode. 33. The device according to item 31 or 32, in which the communication unit is further configured to receive information of a transmission mode indicator, wherein the information of the transmission mode indicator indicates the transmission mode of the data packet. 34. The device of claim 32 or 33, wherein the resource block allocation subfield comprises a resource block pointer and a resource block aggregation pointer, where, When the first resource block pointed to by the resource block pointer is a 2×996-tone resource block, the resource block aggregation pointer points to one or more of the following resource block aggregations: no resource block is aggregated with the first resource block; or the second resource block is aggregated with the first resource block, where the second resource block is a 484-tone resource block adjacent to or non-adjacent to the first resource block; a third resource block is aggregated with the first resource block, where the third resource block is a 484-tone resource block adjacent to the first resource block at a low frequency, or a 484-tone resource block adjacent to the first resource block at a high frequency; or the second resource block and the third resource block are combined with the first resource block. 35. The device according to item 32 or 33, in which, When the first resource block specified by the resource block pointer is a 996-tone resource block, the resource block aggregation pointer specifies one or more of the following resource block aggregations: no resource block is aggregated with the first resource block; or the second resource block is aggregated with the first resource block, wherein the second resource block is a 484-tone resource block adjacent to or non-adjacent to the first resource block.