Data transmission method and related apparatus

Abstract

The application discloses a data transmission method and related device. The method comprises: generating a signaling field of a PPDU, and transmitting the signaling field in a first frequency domain slice; wherein the channel bandwidth for transmitting the PPDU comprises at least two frequency domain slices; the at least two frequency domain slices comprise the first frequency domain slice; and a resource unit allocation subfield in the signaling field indicates resource units (RUs) included in the channel bandwidth for transmitting the PPDU, and the number of user fields corresponding to the RUs allocated to stations docked on the first frequency domain slice. In this way, the signaling field overhead can be saved by omitting the user fields not allocated to the current frequency domain slice. The application can be applied to WiFi systems such as 802.11be or extremely high throughput (EHT).

Description

[0001] This application is a divisional application. The original application has the application number 202010324346.2 and the original application date is April 22, 2020. The entire contents of the original application are incorporated herein by reference. Technical Field

[0002] This application relates to the field of communication technology, and in particular to a data transmission method and related apparatus. Background Technology

[0003] With the development of wireless local area networks (WLANs), the Orthogonal Frequency Division Multiple Access (OFDMA) technology has been introduced. The entire bandwidth is divided into multiple resource units (RUs). This means that user bandwidth allocation is not based on channels, but on resource units. For example, a 20MHz channel can contain multiple RUs, such as 26-tone RUs, 52-tone RUs, or 106-tone RUs. Here, "tone" represents the number of subcarriers. Furthermore, RUs can also be in the form of 242-tone RUs, 484-tone RUs, 996-tone RUs, etc.

[0004] In 802.11ax, the High Efficient Signal Field (HE-SIG-B) in the PHY protocol data unit (PPDU) sent by the access point to multiple sites includes a common field. This common field includes multiple Resource Element Allocation (RU) subfields, which indicate multiple resource elements. The user-specific fields in HE-SIG-B include all user fields corresponding to each RU configurable subfield. Thus, the HE-SIG-B sent to each site contains all user fields corresponding to each RU configurable subfield.

[0005] With the development of WLAN technology, in order to enable the PPDU transmitted by the access point to support more site users, the signaling fields in the PPDU need to transmit more and more user fields, which will lead to increasingly larger signaling overhead. Summary of the Invention

[0006] This application provides a data transmission method and related apparatus that can reduce the overhead of signaling fields in PPDU.

[0007] In a first aspect, embodiments of this application provide a data transmission method, comprising: generating a signaling field of a Physical Layer Protocol Data Unit (PPDU); wherein the channel bandwidth for transmitting the PPDU includes at least two frequency domain segments; the at least two frequency domain segments include a first frequency domain segment; the signaling field is transmitted in the first frequency domain segment and includes a common field and a user-specific field; the common field includes a resource unit allocation subfield, and the user-specific field includes a user field; the resource unit allocation subfield indicates the resource units (RUs) included in the channel bandwidth for transmitting the PPDU, and the number of user fields corresponding to RUs allocated to the stations docked in the first frequency domain segment; wherein the number of user fields corresponding to RUs allocated to the stations docked in the first frequency domain segment represents the number of user fields contributed by the RU to a content channel in the user-specific field, and the user field is the user field corresponding to the station docked in the first frequency domain segment; and transmitting the signaling field in the first frequency domain segment.

[0008] Thus, in the signaling field of the first frequency domain segment transmission, the resource unit allocation subfield indicates the resource units (RUs) included in the channel bandwidth for transmitting the PPDU, and the number of user fields corresponding to the RUs allocated to the stations docked on the first frequency domain segment. It does not indicate the number of users not allocated to the stations docked on the first frequency domain segment according to the actual resource unit allocation, thereby simplifying the user fields. In the user-specific field section, the user fields of RUs not docked on the first frequency domain segment can be omitted or simplified, thereby reducing the overhead of the signaling fields in the PPDU by reducing the number of user fields.

[0009] In some implementations, the resource unit allocation subfield indicates that the number of user fields corresponding to RUs not allocated to stations docked in the first frequency domain segment among the resource units (RUs) included in the channel bandwidth for transmitting the PPDU is 0, and the RUs not allocated to stations docked in the first frequency domain segment are RUs with 242 or more subcarriers. This eliminates the need for user fields for RUs with 242 or more subcarriers, thereby effectively reducing signaling field overhead.

[0010] In some implementations, the number of user fields corresponding to the RUs not assigned to stations docked in the first frequency domain segment, as indicated by the resource unit allocation subfield, is less than the actual number of user fields corresponding to the RUs not assigned to stations docked in the first frequency domain segment. This reduces the number of user fields in the signaling fields transmitted in the first frequency domain segment, thereby reducing signaling field overhead.

[0011] In some implementations, the RUs not assigned to stations docked in the first frequency domain segment indicated by the resource unit allocation subfield are actually at least two RUs not assigned to stations docked in the first frequency domain segment. This simplifies the indication method of the resource unit allocation subfield by indicating at least two RUs as a single RU, resulting in fewer user fields corresponding to these at least two RUs and thus reducing signaling field overhead.

[0012] In some implementations, the at least two RUs are both RUs with fewer than 242 subcarriers. Thus, compared to the prior art where the resource unit allocator indicates the allocation based on the actual resource unit allocation, requiring each small RU to correspond to a separate user field, the scheme of this application indicates at least two small RUs allocated to stations docked in the first frequency domain segment as a single RU. This way, each RU only needs to correspond to one user field, thereby eliminating the need to indicate a user field and reducing signaling field overhead.

[0013] Secondly, embodiments of this application also provide a data transmission method, comprising: a station docked in a first frequency domain segment receiving a signaling field of a Physical Layer Protocol Data Unit (PPDU) in the first frequency domain segment, wherein the channel bandwidth for transmitting the PPDU includes at least two frequency domain segments; the at least two frequency domain segments include the first frequency domain segment; the signaling field includes a common field and a user-specific field; the common field includes a resource unit allocation subfield, and the user-specific field includes a user field; the resource unit allocation subfield indicates a resource unit (RU) in the channel bandwidth for transmitting the PPDU, and the number of user fields corresponding to the RUs allocated to the station docked in the first frequency domain segment; wherein the number of user fields corresponding to the RUs allocated to the station docked in the first frequency domain segment represents the number of user fields contributed by the RU to a content channel in the user-specific field, and the user fields are user fields corresponding to the station docked in the first frequency domain segment; the station receives the user fields included in the user-specific field of the signaling field, obtains a user field carrying the identifier of the station, and obtains the data transmitted on the RU corresponding to the user field.

[0014] In this way, the resource element allocation subfield in the signaling field received by the station from the first frequency domain segment indicates the resource elements (RUs) included in the channel bandwidth for transmitting the PPDU, and the number of user fields corresponding to the RUs allocated to the station docked on the first frequency domain segment. It does not indicate the number of users not allocated to the station docked on the first frequency domain segment according to the actual resource element allocation, thus simplifying the user fields. In the user-specific field section, the user fields of RUs not docked on the first frequency domain segment can be omitted or simplified, thereby reducing the overhead of the signaling fields in the PPDU by reducing the number of user fields.

[0015] In some implementations, the resource unit allocation subfield indicates that the number of user fields corresponding to the resource units (RUs) included in the channel bandwidth for transmitting the PPDU that are not allocated to stations docked in the first frequency domain segment is 0, and the RUs not allocated to stations docked in the first frequency domain segment are RUs with 242 or more subcarriers. This eliminates the need for user fields for RUs with 242 or more subcarriers, thereby effectively reducing signaling field overhead.

[0016] In some implementations, the number of user fields corresponding to the RUs not assigned to stations docked in the first frequency domain segment, as indicated by the resource unit allocation subfield, is less than the actual number of user fields corresponding to the RUs not assigned to stations docked in the first frequency domain segment. This reduces the number of user fields in the signaling fields transmitted in the first frequency domain segment, thereby reducing signaling field overhead.

[0017] In some implementations, the RUs not assigned to stations docked in the first frequency domain segment indicated by the resource unit allocation subfield are actually at least two RUs not assigned to stations docked in the first frequency domain segment. This way, indicating at least two RUs not assigned to stations docked in the first frequency domain segment as a single RU reduces the number of user fields corresponding to these at least two RUs, thereby reducing signaling field overhead.

[0018] In some implementations, the at least two RUs are both RUs with fewer than 242 subcarriers. Thus, compared to the prior art where the resource unit allocator indicates the allocation based on the actual resource unit allocation, requiring each small RU to correspond to a separate user field, the scheme of this application indicates at least two small RUs allocated to stations docked in the first frequency domain segment as a single RU. This way, each RU only needs to correspond to one user field, thereby eliminating the need to indicate a user field and reducing signaling field overhead.

[0019] Thirdly, embodiments of this application also provide a data transmission method, comprising: generating a signaling field of a Physical Layer Protocol Data Unit (PPDU); wherein the channel bandwidth for transmitting the PPDU includes at least two frequency domain segments; the at least two frequency domain segments include a first frequency domain segment; transmitting the signaling field in the first frequency domain segment; wherein the signaling field includes a common field and a user-specific field, the common field includes a resource element allocation subfield; the user-specific field includes a user field; the resource element allocation subfield indicates a resource element (RU) in the channel bandwidth for transmitting the PPDU; the common field includes at least one RU indicated by the resource element allocation subfield being an RU of a plurality of subcarriers less than 242; each RU of the plurality of subcarriers less than 242 corresponds to at least one user field; the user field corresponding to at least one first RU carries an identifier of a station docked in the first frequency domain segment, and the user field corresponding to at least one second RU does not carry an identifier of a station docked in the first frequency domain segment, wherein at least a portion of the subcarriers corresponding to the second RU indicated by the resource element allocation subfield belongs to at least two RUs.

[0020] In this way, compared to indicating the two RUs according to the actual situation and indicating that each of the two RUs corresponds to at least one user field, the scheme of this application, in the first signaling field of the first frequency domain segmented transmission, the resource unit allocation subfield indicates one RU that is combined with the at least two RUs, and this one RU corresponds to only one user field. This can effectively reduce the number of user fields corresponding to multiple consecutive small RUs that are not allocated to STAs that remain in the frequency domain, thereby saving the overhead of signaling fields.

[0021] Fourthly, embodiments of this application also provide a data transmission method, comprising: a station docked in a first frequency domain segment receiving a signaling field of a Physical Layer Protocol Data Unit (PPDU) in the first frequency domain segment; wherein the channel bandwidth for transmitting the PPDU includes at least two frequency domain segments; the at least two frequency domain segments include a first frequency domain segment; the signaling field includes a common field and a user-specific field, the common field including a resource element allocation subfield; the user-specific field including a user field; the resource element allocation subfield indicating a resource element (RU) in the channel bandwidth for transmitting the PPDU; wherein the common field includes at least one of the resource element allocation subfields. The segment indicates that the RU is a plurality of RUs with fewer than 242 subcarriers; each of the plurality of RUs with fewer than 242 subcarriers corresponds to at least one user field; wherein, the user field corresponding to at least one first RU carries the identifier of the station docked in the first frequency domain segment, the user field corresponding to at least one second RU does not carry the identifier of the station docked in the first frequency domain segment, and at least a portion of the subcarriers corresponding to the second RU indicated by the resource unit allocation subfield belongs to at least two RUs; the station obtains the user field carrying its own identifier from the user fields included in the user-specific field, and obtains the data transmitted on the RU corresponding to the user field.

[0022] In this way, compared to indicating the two RUs according to the actual situation and indicating that each of the at least two RUs corresponds to at least one user field, the solution of this application, in the first signaling field received by the station from the first frequency domain segment, allocates a subfield to the resource unit to indicate one RU that is combined with the at least two RUs, and this one RU corresponds to only one user field. This can effectively reduce the number of user fields corresponding to multiple consecutive small RUs that are not assigned to the STAs that are staying in the frequency domain, thereby saving the overhead of signaling fields.

[0023] Fifthly, embodiments of this application also provide a data transmission apparatus, including a processing unit and a transceiver unit; the processing unit is used to generate a signaling field of a Physical Layer Protocol Data Unit (PPDU); wherein the channel bandwidth for transmitting the PPDU includes at least two frequency domain segments; the at least two frequency domain segments include a first frequency domain segment; the signaling field is transmitted in the first frequency domain segment and includes a common field and a user-specific field; the common field includes a resource unit allocation subfield, and the user-specific field includes a user field; the resource unit allocation subfield indicates the resource units (RUs) included in the channel bandwidth for transmitting the PPDU, and the number of user fields corresponding to the RUs allocated to the stations docked in the first frequency domain segment; wherein the number of user fields corresponding to the RUs allocated to the stations docked in the first frequency domain segment represents the number of user fields contributed by the RU to a content channel in the user-specific field, and the user field is the user field corresponding to the station docked in the first frequency domain segment; the transceiver unit is used to transmit the signaling field in the first frequency domain segment. The data transmission device can be a communication device or an access point, or the data transmission device can be deployed on a communication device or an access point.

[0024] Thus, in the signaling field of the first frequency domain segment transmission, the resource unit allocation subfield indicates the resource units (RUs) included in the channel bandwidth for transmitting the PPDU, and the number of user fields corresponding to the RUs allocated to the stations docked on the first frequency domain segment. It does not indicate the number of users not allocated to the stations docked on the first frequency domain segment according to the actual resource unit allocation, thereby simplifying the user fields. In the user-specific field section, the user fields of RUs not docked on the first frequency domain segment can be omitted or simplified, thereby reducing the overhead of the signaling fields in the PPDU by reducing the number of user fields.

[0025] In some implementations, the resource unit allocation subfield indicates that the number of user fields corresponding to RUs not allocated to stations docked in the first frequency domain segment among the resource units (RUs) included in the channel bandwidth for transmitting the PPDU is 0, and the RUs not allocated to stations docked in the first frequency domain segment are RUs with 242 or more subcarriers. This eliminates the need for user fields for RUs with 242 or more subcarriers, thereby effectively reducing signaling field overhead.

[0026] In some implementations, the number of user fields corresponding to the RUs not assigned to stations docked in the first frequency domain segment, as indicated by the resource unit allocation subfield, is less than the actual number of user fields corresponding to the RUs not assigned to stations docked in the first frequency domain segment. This reduces the number of user fields in the signaling fields transmitted in the first frequency domain segment, thereby reducing signaling field overhead.

[0027] In some implementations, the RUs not assigned to stations docked in the first frequency domain segment indicated by the resource unit allocation subfield are actually at least two RUs not assigned to stations docked in the first frequency domain segment. This simplifies the indication method of the resource unit allocation subfield by indicating at least two RUs as a single RU, resulting in fewer user fields corresponding to these at least two RUs and thus reducing signaling field overhead.

[0028] In some implementations, the at least two RUs are both RUs with fewer than 242 subcarriers. Thus, compared to the prior art where the resource unit allocator indicates the allocation based on the actual resource unit allocation, requiring each small RU to correspond to a separate user field, the scheme of this application indicates at least two small RUs allocated to stations docked in the first frequency domain segment as a single RU. This way, each RU only needs to correspond to one user field, thereby eliminating the need to indicate a user field and reducing signaling field overhead.

[0029] In a sixth aspect, embodiments of this application also provide a data transmission apparatus, including a processing unit and a transceiver unit; the transceiver unit is configured to receive signaling fields of Physical Layer Protocol Data Units (PPDUs) docked in the first frequency domain segment, wherein the channel bandwidth for transmitting the PPDU includes at least two frequency domain segments; the at least two frequency domain segments include the first frequency domain segment; the signaling field includes a common field and a user-specific field; the common field includes a resource unit allocation subfield, and the user-specific field includes a user field; the resource unit allocation subfield indicates the resource unit (RU) in the channel bandwidth for transmitting the PPDU, and the number of user fields corresponding to the RUs allocated to the station docked in the first frequency domain segment; wherein the number of user fields corresponding to the RUs allocated to the station docked in the first frequency domain segment represents the number of user fields contributed by the RU to a content channel in the user-specific field, and the user fields are user fields corresponding to the station docked in the first frequency domain segment; the processing unit is configured to receive the user fields included in the user-specific field of the signaling field, obtain the user field carrying the identifier of the station, and obtain the data transmitted on the RU corresponding to the user field. The data transmission device can be a communication device or a site, or the data transmission device can be deployed on a communication device or a site.

[0030] In this way, the resource element allocation subfield in the signaling field received by the station from the first frequency domain segment indicates the resource elements (RUs) included in the channel bandwidth for transmitting the PPDU, and the number of user fields corresponding to the RUs allocated to the station docked on the first frequency domain segment. It does not indicate the number of users not allocated to the station docked on the first frequency domain segment according to the actual resource element allocation, thus simplifying the user fields. In the user-specific field section, the user fields of RUs not docked on the first frequency domain segment can be omitted or simplified, thereby reducing the overhead of the signaling fields in the PPDU by reducing the number of user fields.

[0031] In some implementations, the resource unit allocation subfield indicates that the number of user fields corresponding to RUs not allocated to stations docked in the first frequency domain segment among the resource units (RUs) included in the channel bandwidth for transmitting the PPDU is 0, and the RUs not allocated to stations docked in the first frequency domain segment are RUs with 242 or more subcarriers. This eliminates the need for user fields for RUs with 242 or more subcarriers, thereby effectively reducing signaling field overhead.

[0032] In some implementations, the number of user fields corresponding to the RUs not assigned to stations docked in the first frequency domain segment, as indicated by the resource unit allocation subfield, is less than the actual number of user fields corresponding to the RUs not assigned to stations docked in the first frequency domain segment. This reduces the number of user fields in the signaling fields transmitted in the first frequency domain segment, thereby reducing signaling field overhead.

[0033] In some implementations, the RUs not assigned to stations docked in the first frequency domain segment indicated by the resource unit allocation subfield are actually at least two RUs not assigned to stations docked in the first frequency domain segment. This simplifies the indication method of the resource unit allocation subfield by indicating at least two RUs as a single RU, resulting in fewer user fields corresponding to these at least two RUs and thus reducing signaling field overhead.

[0034] In some implementations, the at least two RUs are both RUs with fewer than 242 subcarriers. Thus, compared to the prior art where the resource unit allocator indicates the allocation based on the actual resource unit allocation, requiring each small RU to correspond to a separate user field, the scheme of this application indicates at least two small RUs allocated to stations docked in the first frequency domain segment as a single RU. This way, each RU only needs to correspond to one user field, thereby eliminating the need to indicate a user field and reducing signaling field overhead.

[0035] In a seventh aspect, embodiments of this application also provide a data transmission apparatus, including a processing unit and a transceiver unit; the processing unit is configured to generate a signaling field for a Physical Layer Protocol Data Unit (PPDU); wherein the channel bandwidth for transmitting the PPDU includes at least two frequency domain segments; the at least two frequency domain segments include a first frequency domain segment; the transceiver unit is configured to transmit the signaling field in the first frequency domain segment; the signaling field includes a common field and a user-specific field, the common field includes a resource element allocation subfield; the user-specific field includes a user field; the resource element allocation subfield indicates a resource element (RU) in the channel bandwidth for transmitting the PPDU; the common field includes at least one RU indicated by the resource element allocation subfield being an RU of a plurality of subcarriers less than 242; each RU of the plurality of subcarriers less than 242 corresponds to at least one user field; wherein the user field corresponding to at least one first RU carries an identifier of a station docked in the first frequency domain segment, the user field corresponding to at least one second RU does not carry an identifier of a station docked in the first frequency domain segment, and at least a portion of the subcarriers corresponding to the second RU indicated by the resource element allocation subfield belongs to at least two RUs. The data transmission device can be a communication device or an access point, or the data transmission device can be deployed on a communication device or an access point.

[0036] In this way, compared to indicating the two RUs according to the actual situation and indicating that each of the two RUs corresponds to at least one user field, the scheme of this application, in the first signaling field of the first frequency domain segmented transmission, the resource unit allocation subfield indicates one RU that is combined with the at least two RUs, and this one RU corresponds to only one user field. This can effectively reduce the number of user fields corresponding to multiple consecutive small RUs that are not allocated to STAs that remain in the frequency domain, thereby saving the overhead of signaling fields.

[0037] Eighthly, embodiments of this application also provide a data transmission apparatus, including a processing unit and a transceiver unit. The processing unit is configured to receive signaling fields of Physical Layer Protocol Data Units (PPDUs) in a first frequency domain segment; wherein the channel bandwidth for transmitting the PPDU includes at least two frequency domain segments; the at least two frequency domain segments include a first frequency domain segment; the signaling fields include a common field and a user-specific field, the common field including a resource unit allocation subfield; the user-specific field including a user field; the resource unit allocation subfield indicating a resource unit (RU) in the channel bandwidth for transmitting the PPDU; wherein the common field includes at least one of the resource unit allocation subfields. The segment indicates that the RU is a plurality of RUs with fewer than 242 subcarriers; each of the plurality of RUs with fewer than 242 subcarriers corresponds to at least one user field; wherein, the user field corresponding to at least one first RU carries an identifier of a station docked in the first frequency domain segment, the user field corresponding to at least one second RU does not carry an identifier of a station docked in the first frequency domain segment, and at least a portion of the subcarriers corresponding to the second RU indicated by the resource unit allocation subfield belongs to at least two RUs; the transceiver unit is used to obtain the user field carrying the identifier of the current station from the user fields included in the user-specific field, and to obtain the data transmitted on the RU corresponding to the user field. This data transmission device can be a communication device or a station, or the data transmission device can be deployed in a communication device or deployed in a station.

[0038] In this way, the resource element allocation subfield in the signaling field received by the station from the first frequency domain segment indicates the resource elements (RUs) included in the channel bandwidth for transmitting the PPDU, and the number of user fields corresponding to the RUs allocated to the station docked on the first frequency domain segment. It does not indicate the number of users not allocated to the station docked on the first frequency domain segment according to the actual resource element allocation, thus simplifying the user fields. In the user-specific field section, the user fields of RUs not docked on the first frequency domain segment can be omitted or simplified, thereby reducing the overhead of the signaling fields in the PPDU by reducing the number of user fields.

[0039] In some implementations, the resource unit allocation subfield indicates that the number of user fields corresponding to RUs not allocated to stations docked in the first frequency domain segment among the resource units (RUs) included in the channel bandwidth for transmitting the PPDU is 0, and the RUs not allocated to stations docked in the first frequency domain segment are RUs with 242 or more subcarriers. This eliminates the need for user fields for RUs with 242 or more subcarriers, thereby effectively reducing signaling field overhead.

[0040] In some implementations, the number of user fields corresponding to the RUs not assigned to stations docked in the first frequency domain segment, as indicated by the resource unit allocation subfield, is less than the actual number of user fields corresponding to the RUs not assigned to stations docked in the first frequency domain segment. This reduces the number of user fields in the signaling fields transmitted in the first frequency domain segment, thereby reducing signaling field overhead.

[0041] In some implementations, the RUs not assigned to stations docked in the first frequency domain segment indicated by the resource unit allocation subfield are actually at least two RUs not assigned to stations docked in the first frequency domain segment. This simplifies the indication method of the resource unit allocation subfield by indicating at least two RUs as a single RU, resulting in fewer user fields corresponding to these at least two RUs and thus reducing signaling field overhead.

[0042] In some implementations, the at least two RUs are both RUs with fewer than 242 subcarriers. Thus, compared to the prior art where the resource unit allocator indicates the allocation based on the actual resource unit allocation, requiring each small RU to correspond to a separate user field, the scheme of this application indicates at least two small RUs allocated to stations docked in the first frequency domain segment as a single RU. This way, each RU only needs to correspond to one user field, thereby eliminating the need to indicate a user field and reducing signaling field overhead.

[0043] Ninthly, embodiments of this application also provide a communication device, which may include: a processor, a transceiver, and optionally a memory, wherein when the processor executes a computer program or instructions in the memory, the method of any embodiment of the first aspect is executed, or the method of any embodiment of the second aspect is executed, or the method of the embodiment of the third aspect is executed, or the method of the embodiment of the fourth aspect is executed.

[0044] In a tenth aspect, embodiments of this application also provide a computer-readable storage medium storing computer instructions that instruct a communication device to perform the method of any embodiment of the first aspect, or the computer instructions that instruct a communication device to perform the method of any embodiment of the second aspect, or the computer instructions that instruct a communication device to perform the method of the third aspect, or the computer instructions that instruct a communication device to perform the method of the fourth aspect.

[0045] Eleventhly, embodiments of this application also provide a computer program product, the computer program product including a computer program, which, when the computer program is run on a computer, causes the computer to perform the method of any embodiment of the first aspect, or causes the computer to perform the method of any embodiment of the second aspect, or causes the computer to perform the method of the third aspect, or causes the computer to perform the method of the fourth aspect.

[0046] In a twelfth aspect, this application also provides a processor for executing any one of the methods described in the first to fourth aspects. During the execution of these methods, the processes of sending and receiving the aforementioned information can be understood as the processor outputting the aforementioned information and the processor receiving the input information. Specifically, when outputting the aforementioned information, the processor outputs the information to a transceiver for transmission. Furthermore, after being output by the processor, the information may require further processing before reaching the transceiver. Similarly, when the processor receives the input information, the transceiver receives the information and inputs it to the processor. Furthermore, after the transceiver receives the information, the information may require further processing before being input to the processor.

[0047] In this way, the transmission, receiving, and other operations involved in the processor can be more generally understood as processor output and receiving, input, and other operations, rather than transmission, receiving, and receiving operations directly performed by the radio frequency circuit and antenna, unless otherwise specified or contradicted by their actual function or internal logic in the relevant description.

[0048] In specific implementation, the processor can be a dedicated processor for executing these methods, or it can be a processor that executes computer instructions stored in memory to execute these methods, such as a general-purpose processor. The memory can be a non-transitory memory, such as read-only memory (ROM), which can be integrated with the processor on the same chip or disposed on different chips. The embodiments of the present invention do not limit the type of memory or the arrangement of the memory and the processor.

[0049] In a thirteenth aspect, this application provides a chip system including a processor and an interface for supporting a communication transmission device in implementing the functions involved in the methods of any one of the first to fourth aspects, such as determining or processing at least one of the data and information involved in the aforementioned methods. In one possible design, the chip system further includes a memory for storing necessary information and data of the aforementioned communication device. This chip system may be composed of chips or may include chips and other discrete devices.

[0050] In a fourteenth aspect, this application provides a functional entity for implementing the method described in any one of the first to fourth aspects. Attached Figure Description

[0051] Figure 1A This is a schematic diagram of a network structure provided in an embodiment of this application;

[0052] Figure 1B This is a schematic diagram of the structure of a communication device provided in an embodiment of this application;

[0053] Figure 1C This is a schematic diagram of the structure of a chip provided in an embodiment of this application;

[0054] Figure 2A This is a schematic diagram of one method of allocating resource units;

[0055] Figure 2B This is a schematic diagram illustrating another method of allocating resource units;

[0056] Figure 3A This is a possible structural diagram of a signaling field;

[0057] Figure 3B This is a schematic diagram of another possible structure for the signaling field;

[0058] Figure 4A This is a schematic diagram of the PPDU involved in this application;

[0059] Figure 4B This is another structural schematic diagram of the PPDU involved in this application;

[0060] Figure 5 This is a flowchart illustrating the method for transmitting the preamble portion of the PPDU provided in this application embodiment;

[0061] Figure 6A This is a schematic diagram of the PPDU structure provided in the embodiments of this application;

[0062] Figure 6B This is another structural schematic diagram of the PPDU provided in the embodiments of this application;

[0063] Figure 6C This is another structural schematic diagram of the PPDU provided in the embodiments of this application;

[0064] Figure 7A This is a flowchart illustrating the data transmission method according to an embodiment of this application;

[0065] Figure 7B This is another structural schematic diagram of the PPDU provided in the embodiments of this application;

[0066] Figure 8A This is a schematic diagram illustrating a scenario of resource unit allocation according to an embodiment of this application;

[0067] Figure 8B This is a schematic diagram of the content channel structure according to an embodiment of this application;

[0068] Figure 8C This is a schematic diagram of the structure of the signaling field in an embodiment of this application;

[0069] Figure 8D This is a schematic diagram of the content channel structure according to another embodiment of this application;

[0070] Figure 8E This is a schematic diagram of the structure of a signaling field according to another embodiment of this application;

[0071] Figure 9 This is a schematic diagram illustrating a scenario of resource unit allocation according to another embodiment of this application;

[0072] Figure 10 This is a schematic diagram illustrating a scenario of resource unit allocation according to another embodiment of this application;

[0073] Figure 11 This is a schematic diagram illustrating a scenario of resource unit allocation according to another embodiment of this application;

[0074] Figure 12 A schematic diagram illustrating a scenario for resource unit allocation in yet another embodiment of this application;

[0075] Figure 13 This is a schematic diagram of the data transmission device according to an embodiment of this application;

[0076] Figure 14 This is a schematic diagram of a data transmission apparatus according to another embodiment of this application;

[0077] Figure 15 This is a schematic diagram of a data transmission device according to another embodiment of this application;

[0078] Figure 16 This is a schematic diagram of a data transmission device according to another embodiment of this application. Detailed Implementation

[0079] The specific embodiments of this application will be described in further detail below with reference to the accompanying drawings.

[0080] by Figure 1A The following example illustrates the network structure to which the data transmission method described in this application is applicable. Figure 1A This is a schematic diagram of a network structure provided in an embodiment of this application. The network structure may include one or more access point (AP) type stations and one or more non-access point station (non-AP STA) stations. For ease of description, this document refers to access point type stations as access points (APs) and non-access point type stations as stations (STAs). An AP may be, for example... Figure 1A AP1 and AP2, STA for example Figure 1A STA1, STA2, and STA3.

[0081] Access points are points through which terminal devices (such as mobile phones) access wired (or wireless) networks. They are primarily deployed in homes, buildings, and campuses, with a typical coverage radius of tens to hundreds of meters. They can also be deployed outdoors. An access point acts as a bridge between wired and wireless networks, connecting various wireless network clients and then connecting the wireless network to the Ethernet. Specifically, access points can be terminal devices (such as mobile phones) or network devices (such as routers) equipped with wireless fidelity (WiFi) chips. Access points can be devices supporting the 802.11be standard. Access points can also be devices supporting various wireless local area networks (WLANs) within the 802.11 family, such as 802.11be, 802.11ax, 802.11ac, 802.11n, 802.11g, 802.11b, and 802.11a. The access point in this application can be a high-efficiency (HE) AP or an extrameally high-throughput (EHT) AP, or it can be an access point that is compatible with a future generation of WiFi standards.

[0082] An access point may include a processor and a transceiver. The processor is used to control and manage the actions of the access point, and the transceiver is used to receive or send information.

[0083] A site can be a wireless communication chip, wireless sensor, or wireless communication terminal, and can also be referred to as a user. For example, a site can be a mobile phone supporting WiFi communication, a tablet computer supporting WiFi communication, a set-top box supporting WiFi communication, a smart TV supporting WiFi communication, a smart wearable device supporting WiFi communication, an in-vehicle communication device supporting WiFi communication, and a computer supporting WiFi communication, etc. Optionally, the site can support the 802.11be standard. The site can also support various 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.

[0084] A site may include a processor and a transceiver. The processor is used to control and manage the actions of the access point, and the transceiver is used to receive or send information.

[0085] The access point in this application can be a high efficient (HE) STA or an extrameally high throughput (EHT) STA, or a STA that is compatible with a future generation of WiFi standards.

[0086] For example, access points and sites can be devices used in the Internet of Vehicles (IoV), IoT nodes and sensors in the Internet of Things (IoT), smart cameras, smart remote controls, smart water and electricity meters in smart homes, and sensors in smart cities.

[0087] The access points and sites involved in the embodiments of this application can also be collectively referred to as communication devices, which may include hardware structures and software modules, and implement the above functions in the form of hardware structures, software modules, or hardware structures plus software modules. One of the above functions can be implemented in the form of hardware structures, software modules, or hardware structures plus software modules.

[0088] Figure 1B This is a schematic diagram of a communication device provided in an embodiment of this application. Figure 1B As shown, the communication device 200 may include: a processor 201, a transceiver 205, and optionally a memory 202.

[0089] The transceiver 205, also known as a transceiver unit, transceiver, or transceiver circuit, is used to implement transceiver functions. The transceiver 205 may include a receiver and a transmitter. The receiver, also known as a receiver or receiving circuit, is used to implement the receiving function; the transmitter, also known as a transmitter or transmitting circuit, is used to implement the transmitting function.

[0090] The memory 202 may store computer programs, software code, or instructions 204, which may also be referred to as firmware. The processor 201 can control the MAC layer and PHY layer by running the computer programs, software code, or instructions 203 therein, or by calling the computer programs, software code, or instructions 204 stored in the memory 202, to implement the data transmission methods provided in the following embodiments of this application. The processor 201 may be a central processing unit (CPU), and the memory 202 may be, for example, a read-only memory (ROM) or a random access memory (RAM).

[0091] The processor 201 and transceiver 205 described in this application can be implemented on integrated circuits (ICs), analog ICs, radio frequency integrated circuits (RFICs), mixed-signal ICs, application-specific integrated circuits (ASICs), printed circuit boards (PCBs), electronic devices, etc.

[0092] The communication device 200 may also include an antenna 206. The modules included in the communication device 200 are merely illustrative examples and are not intended to limit the scope of this application.

[0093] As mentioned above, the communication device 200 described in the above embodiments may be an access point or a station, but the scope of the communication device described in this application is not limited to this, and the structure of the communication device may vary. Figure 1B The communication device can be a standalone device or part of a larger device. For example, the communication device can be implemented as follows:

[0094] (1) A standalone integrated circuit IC, or chip, or chip system or subsystem; (2) A collection of one or more ICs, optionally including storage components for storing data or instructions; (3) A module that can be embedded in other devices; (4) Receivers, smart terminals, wireless devices, handheld devices, mobile units, vehicle-mounted devices, cloud devices, artificial intelligence devices, etc.; (5) Others, etc.

[0095] For communication devices implemented as chips or chip systems, please refer to [link / reference]. Figure 1C The diagram shows the structure of the chip. Figure 1C The chip shown includes a processor 301 and an interface 302. The number of processors 301 can be one or more, and the number of interfaces 302 can be multiple. Optionally, the chip or chip system may include a memory 303.

[0096] This application provides embodiments that do not limit the scope and applicability of the claims. Those skilled in the art can make adaptive changes to the function and deployment of the elements involved in this application without departing from the scope of the embodiments, or omit, substitute, or add various processes or components as appropriate.

[0097] In terms of bandwidth configuration, 802.11ax currently supports the following bandwidth configurations: 20MHz, 40MHz, 80MHz, 160MHz, and 80+80MHz. The difference between 160MHz and 80+80MHz is that the former is a continuous frequency band, while the latter's two 80MHz bands can be separated. 802.11be will support a 320MHz bandwidth configuration.

[0098] In frequency band resource allocation, a user's frequency band resources are allocated not on a channel basis, but on a Resource Unit (RU) basis. The size of an RU can be 26-tone RU, 52-tone RU, or 106-tone RU; these RUs are generally referred to as small RUs. Here, "tone" represents a subcarrier. For example, a 26-tone RU means an RU consisting of 26 subcarriers, which can be allocated to a single user. Furthermore, the size of an RU can also be 242-tone, 484-tone, 996-tone, etc., and these are generally referred to as large RUs. Typically, an RU of 106-tone or greater can be allocated to one or more users. In 802.11be, it will support allocating multiple RUs to a single user; in this application, a user can be understood as a STA (Standard Operating System).

[0099] When the channel bandwidth for transmitting PPDU is 20MHz, such as Figure 2A As shown, Figure 2AThe diagram illustrates the possible allocation of resource units when the channel bandwidth for transmitting PPDUs is 20MHz. The entire 20MHz channel bandwidth can be composed of a single resource unit (242-tone RU) consisting of 242 subcarriers, or various combinations of resource units consisting of 26 subcarriers (26-tone RU), 52 subcarriers (52-tone RU), and 106 subcarriers (106-tone RU). In addition to the RUs used for data transmission, there are also guard subcarriers, empty subcarriers, or direct current (DC) subcarriers.

[0100] When the channel bandwidth for transmitting PPDU is 40MHz, such as Figure 2B As shown, Figure 2B The diagram illustrates various resource unit allocation methods when the channel bandwidth for transmitting PPDUs is 40MHz. The entire channel bandwidth is roughly equivalent to a replication of a 20MHz subcarrier distribution. The entire 40MHz channel bandwidth can be composed of a single resource unit (484-tone RU) consisting of 484 subcarriers, or it can be composed of various combinations of 26-tone RUs, 52-tone RUs, 106-tone RUs, and 242-tone RUs.

[0101] When the channel bandwidth for transmitting PPDUs is 80MHz, the entire channel bandwidth is roughly equivalent to a 20MHz subcarrier distribution. The entire 80MHz channel bandwidth can be composed of a single resource unit (996-tone RU) consisting of 996 subcarriers, or various combinations of 484-tone RUs, 242-tone RUs, 106-tone RUs, 52-tone RUs, and 26-tone RUs. Furthermore, in the middle of the entire 80MHz channel bandwidth, there exists an intermediate 26-tone RU (Center 26-Tone RU) composed of two 13-tone subunits.

[0102] Similarly, when the channel bandwidth for transmitting PPDUs is 160MHz, the entire channel bandwidth can be considered as a replica of two 80MHz subcarrier distributions. The entire channel bandwidth can consist of a single 2×996-tone RU (a resource unit composed of 1992 subcarriers), or various combinations of 26-tone RUs, 52-tone RUs, 106-tone RUs, 242-tone RUs, 484-tone RUs, and 996-tone RUs. Furthermore, in the middle of the entire 80MHz channel bandwidth, there exists an intermediate 26-tone RU composed of two 13-tone subunits.

[0103] In 802.11ax, the AP uses the signal field (SIG) to notify the user of RU allocation. See also... Figure 3A , Figure 3A This is a structural diagram of the signaling field. For example... Figure 3A As shown, HE-SIG includes common fields and user-specific fields.

[0104] The common fields include 1 to N resource unit allocation subfields (RU allocation subfields), a cyclic redundancy code (CRC) for verification, and a tail subfield for cyclic decoding. One resource unit allocation subfield corresponds to the allocation of one 20MHz resource unit, and one resource unit allocation subfield indicates the size and location of one or more resource units corresponding to 20MHz.

[0105] One of the resource unit allocation subfields is an index, which indicates the size and location of one or more resource units corresponding to 20MHz.

[0106] As shown in Table 1, according to 802.11ax, the resource unit allocation subfield can be an index in the first column of Table 1, for example, 00000000, 00000001, 00000010. The row where each index is located represents the size and location of the resource unit corresponding to 20MHz.

[0107] Table 1

[0108]

[0109]

[0110] The signaling field (HE-SIG) contains user-specific fields, ranging from 1 to M, arranged in the order of resource unit allocation. The M user fields are typically grouped in pairs, with each pair of user fields followed by a CRC and a tail field. If the number of user fields is odd, the last user field is grouped separately, and this last user field is followed by a CRC and a tail field. One of these user fields carries station identification information, indicating that its corresponding RU has been assigned to a specific STA.

[0111] When a resource unit allocation subfield indicates a combination of resource units comprising 10⁶ or more subcarriers, the index also indicates the number of MU MIMO users supported by the resource unit comprising 10⁶ or more subcarriers. In the 802.11ax standard, the number of MU MIMO users is less than or equal to 8. For example, index 01000y2y1y0, where y2y1y0 is 010, indicates that 10⁶-tones are allocated to 3 users.

[0112] The order of the user fields in the user-specific fields matches the order of the resource units indicated by the corresponding resource unit allocation subfield. The STA can identify whether the resource unit corresponding to that user field belongs to itself by reading the user field. Then, the STA can determine the resource unit allocated to itself by combining the position of the user field with the corresponding resource unit allocation subfield.

[0113] For example, such as Figure 3B As shown, Figure 3B This is another possible structural diagram of the signaling field. Resource Unit Allocation Subfield 1 is 00001111. Based on the row containing 00001110 in Table 1, it can be determined that the resource units indicated by Transmission Resource Unit Allocation Subfield 1 are 52-tone RU, 52-tone RU, 26-tone RU, 52-tone RU, and 52-tone RU. The user-specific field section includes n user fields, where User Field 1, User Field 2, User Field 3, User Field 4, and User Field 5 correspond to 52-tone RU, 52-tone RU, 26-tone RU, 52-tone RU, and 52-tone RU, respectively. Thus, the 52-tone RU, 52-tone RU, 26-tone RU, 52-tone RU and 52-tone RU indicated by resource unit allocation subfield 1 are respectively allocated to STA1 corresponding to user field 1, STA2 corresponding to user field 2, STA3 corresponding to user field 3, STA4 corresponding to user field 4, and STA5 corresponding to user field 5.

[0114] As can be seen, in 802.11ax, the resource unit corresponding to each user field is determined based on the correspondence between the order of resource units indicated by the resource unit allocation subfield and the order of user fields in the user-specific fields. Therefore, the HE-SIG-B sent to each station contains all user fields corresponding to each resource unit allocation subfield. This ensures that the STA can determine the resource unit allocated to itself by combining the position of the user field with the corresponding resource unit allocation subfield.

[0115] However, with the development of WLAN technology, in order to enable PPDU to support more STAs, the signaling fields in PPDU need to transmit more and more user fields, which will increase the signaling overhead.

[0116] Please see Figure 4A , Figure 4A This is a schematic diagram of the PPDU involved in this application. To reduce overhead, in one specific embodiment, as shown below... Figure 4A The frequency domain segmentation structure shown divides the channel bandwidth of the transmitted PPDU into multiple frequency domain segments. Each frequency domain segment hosts several stations, and the AP sends PPDUs to the STAs hosted in multiple frequency domain segments. Specifically, the aforementioned hosting refers to a correspondence determined or known by the system; it is semi-static, meaning the correspondence between the frequency domain segment and one or more hosted stations is configured and remains unchanged for a certain period of time. In a more specific example, each frequency domain segment is 80MHz; of course, other bandwidth granularities are also possible, such as 40MHz, 160MHz, etc. The specific process of configuring the hosting relationship is not described in the various embodiments and will therefore not be elaborated further.

[0117] It should be understood that the station parking described in this application is located in a certain frequency domain segment, or the station resides in a certain frequency domain segment, or the station is located in or belongs to a certain frequency domain segment.

[0118] In this embodiment, frequency domain segmentation can also be referred to as frequency domain partitioning, etc. (See reference...) Figure 4B , Figure 4B This is a schematic diagram of the PPDU structure. A PPDU 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), an EHT Short Training Field (EHT-STF), an EHT Long Training Field (EHT-LTF), and data. Among these, L-STF, L-LTF, L-SIG, RL-SIG, U-SIG, EHT-SIG, EHT-STF, and EHT-LTF are partial structures within the physical layer header (or pre-processor) of the PPDU.

[0119] L-STF, L-LTF, and L-SIG can be understood as traditional preamble fields, used to ensure the coexistence of new and traditional equipment. RL-SIG is used to enhance the reliability of traditional signaling fields.

[0120] U-SIG and EHT-SIG are signaling fields. U-SIG carries common information such as PPDU version information, uplink / downlink information, PPDU frequency bandwidth information, and puncturing indication information. EHT-SIG includes information indicating resource allocation and data demodulation.

[0121] It should be noted that, in this embodiment, the fields in the PPDU under the 802.11be scenario are used as examples. The fields in the PPDU mentioned in this embodiment are not limited to those related to 802.11be; the fields in the PPDU mentioned in this embodiment can also be fields related to standard versions after 802.11be.

[0122] Based on the frequency domain segmentation structure, the fields of the preamble of the PPDU are carried on each frequency domain segment. That is, the preamble of the PPDU includes one or more frequency domain segment contents. For example, the first frequency domain segment contents include a first conventional preamble field, a first U-SIG, and a first EHT-SIG; the second frequency domain segment contents include a second conventional preamble field, a second U-SIG, and a second EHT-SIG.

[0123] In this way, the U-SIG transmitted in each frequency domain segment can only contain puncturing indication information for its own frequency domain segment. For example, the puncturing indication field can be set to 1 bit. This can save the overhead of transmitting U-SIG in each frequency domain segment. However, since most of the fields in the U-SIG part are common fields that each STA needs to receive, the overhead can only be saved by a few fields related to each STA (such as puncturing indication), so the effect of saving overhead is not significant.

[0124] Based on the above structure, some embodiments are provided for saving the overhead of signaling fields.

[0125] Please see Figure 5 , Figure 5 This is a flowchart illustrating a method for transmitting the preamble portion of a PPDU according to an embodiment of this application. In one embodiment of this application, a method for transmitting the preamble portion of a PPDU is provided. Figure 5 As shown, the method for transmitting the preamble of the PPDU includes:

[0126] 101. The AP generates a preamble to a PPDU. This preamble includes one or more frequency domain slice contents. The frequency domain slice contents include at least complete scheduling information for the stations docked on the corresponding frequency domain slice. "Complete" here means that for a frequency domain slice, if the stations docked there are in the current scheduling process, their scheduling information is carried on the corresponding frequency domain slice, including resource allocation information and relevant station information (e.g., resource allocation fields for the docked stations and all user fields for the scheduled docked stations; the specific structure will be described in detail in other embodiments).

[0127] It should be noted that for a frequency domain segment, the resource elements allocated to the stations it serves do not necessarily all reside on that specific segment. Instead, they may be allocated at any location across the entire channel bandwidth based on resource and service requirements. That is, the resource element allocation subfield indicating resource allocation for each station is transmitted on that frequency domain segment, but the data fields for these stations may not be transmitted on that segment. Of course, in a simplified embodiment, only the stations may be allocated to the specific frequency domain segment they serve. Alternatively, the stations may be allocated across a portion of the channel bandwidth.

[0128] It is understood that when an AP transmits a PPDU to a station docked in a certain frequency domain segment, the signaling field of the PPDU is transmitted on the frequency domain segment where the station is docked. The resource unit indicated by the resource unit allocation subfield in the signaling field of the PPDU may or may not belong to the frequency domain segment where the station is docked. In other words, the frequency domain segment where the station is docked, as referred to in this application, may be different from the frequency band range in which the station transmits data.

[0129] The aforementioned PPDU includes a traditional preamble field, a signaling field, and data. The signaling field may include, for example, U-SIG and EHT-SIG. The traditional preamble field can be combined with the aforementioned... Figure 4A or Figure 4B The U-SIG is consistent with the traditional preamble field. It carries common information that stations docked in this frequency domain segment need to receive. U-SIG may include, for example, information indicating the PPDU version, information indicating uplink / downlink, information indicating the frequency domain bandwidth of the PPDU, puncturing indication information, etc. EHT-SIG carries at least complete scheduling information for stations docked in this frequency domain segment.

[0130] 102. The AP transmits the corresponding frequency domain segment content on the corresponding frequency domain segment. That is, it transmits the first frequency domain segment content on the first frequency domain segment and the second frequency domain segment content on the second frequency domain segment.

[0131] Accordingly, a method for the pre-processing part of a site receiving a PPDU is provided:

[0132] 201. The station receives the frequency domain fragment content corresponding to the frequency domain fragment from the preamble of the PPDU where the frequency domain fragment is docked. The frequency domain fragment content includes complete scheduling information of the scheduled stations among the stations where the frequency domain fragment is docked (e.g., resource allocation fields for the docked stations and all user fields for the scheduled docked stations).

[0133] 202. The station obtains its own scheduling information based on the above information.

[0134] Using the above method, a station docked at a certain frequency domain segment only needs to obtain the signaling field portion of the preceding part corresponding to that frequency domain segment, and does not need to obtain the signaling field portion of the entire channel bandwidth.

[0135] In another embodiment, a station docked in a frequency domain segment can transmit only within a specific frequency band of the channel bandwidth. The signaling fields transmitted in each frequency domain segment only include those related to the frequency band corresponding to that segment, rather than transmitting signaling fields for the entire channel bandwidth in each segment. Specifically, each frequency domain segment can correspond to a preset frequency band, which can be understood as the frequency band of the RU allocated to the STA docked in that segment, or as the frequency band in which the STA transmits data. In this way, a frequency domain segment can transmit only a portion of the signaling fields related to the frequency band, thereby reducing the signaling field overhead of a single frequency domain segment.

[0136] Specifically, the signaling fields in the frequency domain slice include the resource unit allocation subfield corresponding to the aforementioned frequency band range, and at least the user field of the station docked in the frequency domain slice allocated on the RU indicated by the resource unit allocation subfield.

[0137] Please see Figures 6A-6C The following examples illustrate a scheme for transmitting the signaling field of the complete channel bandwidth in a frequency domain segment, and a scheme for transmitting a portion of the signaling field of the corresponding frequency band range in a frequency domain segment, as described above.

[0138] For example, the signaling field may include a field indicating the channel bandwidth for transmitting PPDUs. The AP uses the bandwidth indication field in the signaling field to indicate to the STA that the total channel bandwidth is 320MHz, which is divided into four frequency domain segments. The first frequency domain segment is the first 80MHz, the second is the second 80MHz, the third is the third 80MHz, and the fourth is the fourth 80MHz. For ease of description, the STA docked in the first frequency domain segment is referred to as the first STA, the STA docked in the second frequency domain segment as the second STA, the STA docked in the third frequency domain segment as the third STA, and the STA docked in the fourth frequency domain segment as the fourth STA.

[0139] In the first possible scenario, for each frequency domain segment, the docking station can be assigned to an RU at any location across the entire channel bandwidth. That is, the frequency band corresponding to each frequency domain segment is the complete channel bandwidth of 320MHz used to transmit the PPDU. Each frequency domain segment transmits the signaling field for the complete channel bandwidth. Figure 6A This is a schematic diagram of the PPDU structure provided in an embodiment of this application. Figure 6A As shown, the signaling field for each frequency domain segment transmission, such as in EHT-SIG, contains a resource unit allocation subfield indicating the full channel bandwidth of 320MHz.

[0140] For ease of explanation, in the embodiments of this application, each resource unit allocation subfield is in 20MHz granularity, indicating a corresponding RU allocation for 20MHz. However, this application is not limited to each resource unit allocation subfield being in 20MHz granularity.

[0141] For example, if each resource unit allocation subfield is granular at 20MHz, indicating a RU allocation corresponding to 20MHz, then Figure 6A In the example, the signaling field of each frequency domain segment transmission contains 16 resource unit allocation subfields, as well as the user field corresponding to the RU indicated by these 16 resource unit allocation subfields.

[0142] In the second possible scenario, at least one frequency domain segment allocates the docking station to a portion of the channel bandwidth. That is, the bandwidth corresponding to at least one frequency domain segment is less than the full channel bandwidth of 320MHz for transmitting the PPDU.

[0143] For example, Figure 6B This is another structural schematic diagram of the PPDU provided in the embodiments of this application, as shown below. Figure 6BAs shown, the signaling field of each frequency domain segment transmission includes a signaling field for indicating the frequency band range corresponding to each frequency domain segment. In the corresponding example, the signaling field may only include a resource unit allocation sub-field indicating the RU allocation for the frequency band range corresponding to the frequency domain segment, and a user field corresponding to the resource unit allocation sub-field. It may not include resource allocation information for other frequency band ranges, thereby reducing overhead.

[0144] It should be noted that the frequency band range corresponding to each frequency domain segment does not refer to the "80MHz" of the signaling field transmitted in each frequency domain segment mentioned in the example above. This can be understood in conjunction with the specific examples below.

[0145] For a specific example, the frequency band corresponding to the first frequency domain segment is 320MHz. The frequency band for the first STA to receive data is also 320MHz. Therefore, the signaling field transmitted by the AP in the first frequency domain segment (the first 80MHz) contains 16 resource unit allocation subfields, each indicating the RU allocation for every 20MHz within the 320MHz.

[0146] Following the frequency order from low to high, the second frequency domain segment corresponds to the second 80MHz band within the 320MHz range. The frequency band for receiving data by the second STA is this 80MHz. Therefore, the signaling fields transmitted in the second frequency domain segment are the signaling fields corresponding to this 80MHz. The signaling fields transmitted in the second frequency domain segment only need four resource unit allocation subfields, indicating the RU allocation for every 20MHz within this 80MHz band.

[0147] The frequency band corresponding to the third frequency domain segment is 160MHz, the highest frequency in the 320MHz range. The frequency band for receiving data by the third STA is this 160MHz. Therefore, the signaling fields transmitted in the third frequency domain segment are the signaling fields corresponding to this 160MHz range. The signaling fields transmitted in the third frequency domain segment only need 8 resource unit allocation subfields, which respectively indicate the RU allocation for every 20MHz in the 160MHz range.

[0148] The fourth frequency domain segment corresponds to the highest frequency of 80MHz within the 320MHz range. The fourth STA receives data within this 80MHz range. The signaling fields transmitted in the fourth frequency domain segment are the signaling fields corresponding to this 80MHz range. The signaling fields transmitted in the fourth frequency domain segment only need four resource unit allocation subfields, indicating the RU allocation for every 20MHz within this 80MHz range.

[0149] For example, each frequency domain segment's docking station is only assigned to the frequency domain segment it docks in. That is, the frequency band range corresponding to each frequency domain segment is the same as the frequency domain segment it docks in. Figure 6C As shown, Figure 6C This is another structural diagram of the PPDU provided in this application embodiment. The frequency band corresponding to the first frequency domain segment is the first 80MHz, the frequency band corresponding to the second frequency domain segment is the second 80MHz, the frequency band corresponding to the third frequency domain segment is the third 80MHz, and the frequency band corresponding to the fourth frequency domain segment is the fourth 80MHz. Therefore, each frequency domain segment only needs 4 resource unit allocation subfields.

[0150] Therefore, compared to the first possible scenario where each frequency domain segment transmission signaling field needs to include 16 resource element allocation subfields indicating the complete channel bandwidth, the second possible scenario does not require the frequency domain segment transmission signaling field to include these 16 resource element allocation subfields. It can be understood that the user field corresponds to the resource element allocation subfields; if the number of resource element allocation subfields in the signaling field decreases, the number of user fields will also decrease accordingly.

[0151] In this way, each frequency domain segment only transmits the signaling field of the frequency band corresponding to its own frequency domain segment. That is to say, the signaling field transmitted by each frequency domain segment only contains the scheduling information of the STAs docked in this frequency domain segment, which can save the overhead of signaling fields.

[0152] Optionally, the signaling field may include a field indicating the frequency band division corresponding to each frequency domain segment. This allows for flexible configuration of the corresponding frequency band range for each segment, thus making RU allocation more flexible.

[0153] In some optional embodiments, each frequency domain segment corresponds to a preset frequency band range. The user field in the signaling field transmitted by each frequency domain segment corresponds to at least one RU (Real Estate Unit) within the preset frequency band range corresponding to that frequency domain segment. For example, the preset frequency band range corresponding to the first frequency domain segment is 160MHz. Therefore, any user field in the signaling field transmitted by the first frequency domain segment corresponds to at least one RU within that 160MHz carrier frequency range. In this way, the frequency band range corresponding to each frequency domain segment is preset, and it is not necessary to indicate the frequency band range corresponding to each frequency domain segment in the signaling field of the PPDU, thereby further saving signaling field overhead.

[0154] Each frequency domain segment corresponds to a preset frequency band range, which refers to the frequency band range where the RU (Resource Utility) allocated to the STA (Station) docked in that frequency domain segment is located. The STA in each frequency domain segment receives data from the RU within the preset frequency band range corresponding to that frequency domain segment. For an explanation of the definition of the preset frequency band range corresponding to each frequency domain segment, please refer to the explanation of the frequency band range corresponding to each frequency domain segment in the above embodiments; it will not be repeated here.

[0155] Below are some examples of preset frequency band ranges corresponding to each frequency domain segment.

[0156] The 320MHz channel bandwidth is divided into four frequency domain segments, each with a bandwidth of 80MHz. The first frequency domain segment is the first 80MHz, the second frequency domain segment is the second 80MHz, the third frequency domain segment is the third 80MHz, and the fourth frequency domain segment is the fourth 80MHz.

[0157] In one example, the preset frequency band range corresponding to the first frequency domain segment is 320MHz. The preset frequency band ranges corresponding to the frequency domain segments other than the first frequency domain segment are all consistent with the frequency band range of the first frequency domain segment. That is, the preset frequency band range corresponding to the second frequency domain segment is the second 80MHz, the preset frequency band range corresponding to the third frequency domain segment is the third 80MHz, and the preset frequency band range corresponding to the fourth frequency domain segment is the fourth 80MHz.

[0158] In another example, the preset frequency band corresponding to the first frequency domain segment is 320MHz. The preset frequency band corresponding to the second frequency domain segment is the same as the frequency band of the first segment, that is, the preset frequency band corresponding to the second frequency domain segment is the second 80MHz. The preset frequency band corresponding to the third frequency domain segment is 160MHz, which is the highest frequency of 160MHz in the 320MHz channel bandwidth for transmitting PPDUs. The preset frequency band corresponding to the fourth frequency domain segment is the same as the frequency band of the first segment, that is, the preset frequency band corresponding to the fourth frequency domain segment is the highest frequency of 80MHz in the 320MHz.

[0159] In another example, the preset frequency band corresponding to the first frequency domain segment is 320MHz. The preset frequency band corresponding to the second frequency domain segment is 240MHz, that is, the lowest frequency of 240MHz in the 320MHz range. The preset frequency band corresponding to the third frequency domain segment is 160MHz, that is, the highest frequency of 160MHz in the 320MHz range. The preset frequency band corresponding to the fourth frequency domain segment is the same as the frequency band of the first frequency domain segment, that is, the preset frequency band corresponding to the fourth frequency domain segment is 80MHz, the highest frequency of 320MHz.

[0160] In another embodiment, to further reduce signaling overhead in frequency domain fragmentation scenarios, a method for setting the resource unit allocation subfield and user field in the signaling field of the PPDU is provided. Compared with the methods corresponding to steps 101-102 and 201-202 above, this method simplifies each field of each frequency domain fragment content, using only the complete scheduling information of the station docked on the corresponding frequency domain fragment, thereby further reducing signaling overhead. It should be understood that the solution in this embodiment can be implemented alone or in combination with the solutions in the above embodiments.

[0161] For example, the common fields and user-specific fields in the signaling fields of a frequency domain fragment can be simplified separately:

[0162] 1. Simplify the resource unit allocation subfield of the public field.

[0163] Each resource unit allocation subfield in the common field focuses only on the allocation of resource blocks for scheduled stations among those docked on the current frequency domain slice. This focus means that, since a station may be allocated to any resource block of the channel bandwidth, each resource unit allocation subfield needs to cover or indicate the result of resource block partitioning across the entire channel bandwidth. However, it can provide accurate information only for the resource units allocated to docked stations, while providing simplified (or obfuscated) information for other unrelated resource units.

[0164] 2. Simplify the user fields in the user-specific fields section.

[0165] The user-specific fields can include the user fields of the scheduled stations among the stations docked on the current frequency domain slice, while the user fields of stations docked outside the current frequency domain slice can be completely omitted or partially omitted.

[0166] Accordingly, in this embodiment, the station only receives the signaling fields in the preceding part on the frequency domain segment where it is docked.

[0167] For sites docked in different frequency domain segments, the resource unit allocation subfield and user-specific field of the signaling field in the PPDU will be configured according to the docking site situation in a certain frequency domain segment in order to solve the problem of reducing the indication overhead of the signaling field.

[0168] In a specific example, when an AP sends a PPDU to a station docked in a certain frequency domain slice, at least one of the number of RUs and the number of user fields indicated by the resource unit allocation subfield in the signaling field of the PPDU is simplified by using a "deceptive," "fake," or "non-real" method. That is to say, for a station docked in a certain frequency domain slice, the number of resource units not allocated to the station docked in that frequency domain slice in the resource unit allocation subfield of the signaling field of the PPDU sent by the AP may not be the real number of resource units, and the number of user fields corresponding to the resource units may not be real. However, the number of resource units allocated to the station docked in that frequency domain slice and the number of user fields corresponding to the resource units are real. This does not affect the station docked in this frequency domain slice from obtaining its real allocated resource units.

[0169] The first method to simplify the indication is to transmit a PPDU to a station docked in a certain frequency domain segment. The signaling field of the PPDU is transmitted on that frequency domain segment. For resource elements not allocated to stations docked in this frequency domain segment, the resource element allocation subfield indicates that the number of user fields corresponding to that resource element is 0. Correspondingly, no corresponding user fields are set in the user-specific field of that signaling field; that is, the number of user fields corresponding to that resource element is 0. This eliminates the need for user fields in the user-specific field, thus saving indication overhead. By simplifying the user fields, in the signaling field transmitted in a frequency domain segment, the user-specific field portion only contains the user fields of STAs docked in this frequency domain segment.

[0170] For example, if the RUs corresponding to the channel bandwidth for transmitting PPDUs include one RU that is not assigned to a STA docked in this frequency domain segment, then the resource unit allocation subfield of the signaling field transmitted in this frequency domain segment indicates that the number of user fields corresponding to that resource unit is 0. Correspondingly, in the user-specific field, if no user field corresponding to that large RU is set, the resource unit allocation subfield indicates that the number of user fields corresponding to that large RU is 0. This simplified method of not setting user fields according to the actual situation in the signaling field can eliminate the need for user fields corresponding to large RUs that are not assigned to STAs docked in this frequency domain segment.

[0171] The second method for simplifying indication is as follows: When transmitting a PPDU to a station docked in a certain frequency domain segment, the signaling field of the PPDU is transmitted on that frequency domain segment. For multiple resource elements not allocated to a station docked in this frequency domain segment, on the one hand, they are treated as larger resource elements as possible and indicated through the resource element allocation subfield. In this way, the number of RUs indicated by the resource element allocation subfield is smaller than the actual number of RUs not allocated to a station docked in this frequency domain segment; on the other hand, the user field corresponding to the RUs not allocated to a station docked in this frequency domain segment indicated by the resource element allocation subfield is kept as small as possible.

[0172] On the other hand, when setting user fields corresponding to RUs in user-specific fields, the number of user fields can be as small as possible compared to the number of user fields corresponding to the actual resource unit, thereby saving the number of user fields in user-specific fields and thus saving indication overhead. This simplified indication method simplifies the allocation of subfields for resource units and eliminates at least some user fields for stations that are not located in this frequency domain.

[0173] For example, a 20MHz RU includes at least one RU assigned to a STA docked in this frequency domain segment, and at least two second RUs not assigned to a STA docked in this frequency domain segment. In the signaling field transmitted in this frequency domain segment, the at least two second RUs can be treated as a larger RU, indicated through the corresponding resource unit allocation subfield. Therefore, in the user-specific field section, only the user field corresponding to this larger RU needs to be set, and the number of user fields should be set to the smallest possible value. According to existing technology, these at least two second RUs correspond to at least two user fields. This simplified indication method can minimize the number of user fields. Simultaneously, when the resource unit allocation subfield indicates this larger RU, the number of its corresponding user fields is minimized, for example, to one.

[0174] Based on the simplified indication method described above, this application provides a data transmission method. This data transmission method is used to transmit PPDUs, and by employing the simplified indication method described above, it saves the overhead of signaling fields in the PPDU.

[0175] Please see Figure 7A , Figure 7A This is a schematic flowchart illustrating the data transmission method of this application embodiment. This application embodiment describes an example of an AP sending a PPDU to a STA. The data transmission method of this application is also applicable to scenarios where an AP sends a PPDU to another AP, or a STA sends a PPDU to another STA. In different scenarios, the names of the transmitted PPDU and its signaling fields may differ, but their functions and roles are similar. This application embodiment will not elaborate on each scenario.

[0176] In this embodiment, the channel bandwidth for the AP to transmit PPDUs to STAs includes at least two frequency domain segments; these at least two frequency domain segments include a first frequency domain segment; each frequency domain segment hosts a number of STAs. For example, the number of stations hosted in a frequency domain segment can be any number greater than or equal to 0. The signaling fields of the PPDU include, but are not limited to, common fields and user-specific fields. Common fields include the resource unit allocation subfield. User-specific fields include user fields.

[0177] The data transmission method in this application embodiment may include the following steps:

[0178] S701, signaling fields generated by AP for PPDU;

[0179] Step S701 can be implemented by the AP's processor. That is, the AP's processor generates the signaling fields of the PPDU.

[0180] In the data transmission method of this application, when the AP transmits the PPDU to the STA, the indication method of the signaling field transmitted in the first frequency domain segment adopts at least one of the above-mentioned simplified indication methods.

[0181] In 802.11be, this signaling field can refer to EHT-SIG, or it can refer to both U-SIG and EHT-SIG. The signaling field in this application embodiment is not limited to the SIG field in 802.11be; the signaling field in this application embodiment can also be the SIG field related to standard versions after 802.11be.

[0182] In this embodiment of the application, the resource unit allocation subfield can be indicated using entries in the resource unit allocation subfield (RUallocation subfield, RA subfield) table. For example, the resource unit allocation subfield can be indicated using entries in Table 1, or using entries in Table 2 or Table 3, or using entries in Table 2 or Table 3 in combination with Table 4 or Table 5.

[0183] S702, Signaling field for AP to send PPDU.

[0184] Step S702 can be implemented by the AP's transceiver. That is, the AP's transceiver sends a PPDU.

[0185] Correspondingly, the STA docked in the first frequency domain segment receives the PPDU sent by the AP, retrieves the user field carrying the STA's identifier from the user fields included in the user-specific fields, and then retrieves the data transmitted on the RU corresponding to that user field. Specifically, the STA's transceiver receives the PPDU sent by the AP. The STA's processor retrieves the user field carrying the STA's identifier from the user fields included in the user-specific fields, then retrieves the RU corresponding to that user field, and receives data from that RU.

[0186] Based on the above data transmission method, the resource unit indicator subfield and user field in this signaling field are described below when two simplified indication methods are used.

[0187] In some possible implementations, the resource unit allocation subfield in the signaling field is indicated using the first simplified indication method described above.

[0188] In this embodiment, the number of user fields indicated by the resource unit allocation subfield corresponding to the large RU in the signaling field represents the number of user fields contributed by the RU to a content channel in a user-specific field. These user fields are the user fields corresponding to the STAs docked on the first frequency domain segment. The user fields include the identifier of the corresponding STA.

[0189] The signaling fields transmitted in each frequency domain segment can be transmitted by two or more Content Channels (CCs). Each CC transmits a portion of the signaling fields.

[0190] For example, the channel bandwidth for transmitting the PPDU is 320MHz. The signaling fields of the PPDU transmitted in the first frequency domain segment are transmitted by CC1 and CC2. The signaling fields of the first frequency domain segment transmission contain 16 resource element allocation subfields. These 16 resource element allocation subfields can be numbered sequentially, with odd-numbered resource element allocation subfields transmitted on CC1 and even-numbered resource element allocation subfields transmitted on CC2. On each CC, the user field corresponding to the resource element allocation subfield of that CC is also transmitted. For example, the user field corresponding to the odd-numbered resource element allocation subfield is transmitted on CC1, and the user field corresponding to the even-numbered resource element allocation subfield is transmitted on CC2. The resource element allocation subfield indicates the RUs included in the channel bandwidth for transmitting the PPDU, and the number of user fields contributed by the RUs to the user-specific field in the corresponding content channel.

[0191] In one implementation, the resource unit allocation subfield indicates that the number of user fields corresponding to the RUs allocated to non-docked STAs in the first frequency domain segment is 0, which is included in the resource unit RUs of the channel bandwidth for transmitting the PPDU.

[0192] The resource unit allocation subfield indicates that among the resource units RU included in the channel bandwidth for transmitting the PPDU, the number of user fields corresponding to RU is 0, indicating that RU has not been allocated to STAs docked on the first frequency domain segment.

[0193] In this embodiment, the signaling field of the first frequency domain segmentation transmission indicates one or more RUs, and the number of user fields corresponding to the large RUs assigned to STAs not docked in the first frequency domain segment is 0. Thus, in the user-specific field portion of the signaling field, a corresponding user field is set for large RUs docked in the first frequency domain segment, where the user field carries the station's identifier; while for large RUs not docked in the first frequency domain segment, no corresponding user field is set. This reduces the number of user fields in the signaling field, thereby saving signaling field overhead.

[0194] Please see Figure 7B , Figure 7B This is a schematic diagram of the structure of a PPDU transmitted in different frequency domains. In this embodiment, the signaling field of each frequency domain segmented PPDU is different, and the resource unit allocation subfield in the signaling field of each frequency domain segmented PPDU is divided into two parts, which are transmitted in two CCs respectively. The user field in the signaling field of each frequency domain segmented PPDU is also divided into two parts, which are transmitted in two CCs respectively.

[0195] Specifically, the resource unit allocation subfield in the signaling field of a frequency domain segment transmission indicates different resource unit allocation situations. For RUs and corresponding user fields allocated to STAs docked in this frequency domain segment, the resource unit allocation subfield in the signaling field indicates the actual situation, while for RUs and corresponding user fields allocated to STAs not docked in this frequency domain segment, it may not indicate the actual situation.

[0196] The user fields in the signaling fields of a frequency domain segment transmission are also different. Among the multiple resource units (RUs) indicated by the resource unit allocation subfield in the signaling subsegment of a frequency domain segment, the RUs allocated to the STAs docked in this frequency domain segment have corresponding user fields set, which contain the identifier of the STAs docked in this frequency domain segment; the RUs not allocated to the STAs docked in this frequency domain segment do not have user fields set or the number of user fields is 0.

[0197] For example, the resource unit allocation subfield in the signaling field of the first frequency domain segmentation transmission indicates a first RU and a second RU among multiple RUs. The first RU is the RU allocated to the STA docked in the first frequency domain segment; the second RU is a large RU not allocated to the STA in the first frequency domain segment.

[0198] The user-specific field portion of the signaling field transmitted in the first frequency domain segment includes the user field corresponding to the first RU, which carries the identifier of the STA docked in the first frequency domain segment; the user-specific field portion does not include the user field corresponding to the second RU.

[0199] Furthermore, the second RU can actually be one or more RUs not assigned to STAs docked in the first frequency domain segment. RUs not assigned to STAs docked in the first frequency domain segment can be one or more RUs assigned to STAs docked in frequency domain segments other than the first frequency domain segment, or RUs not assigned to any STA.

[0200] The following example illustrates a scenario where the channel bandwidth for transmitting PPDUs is 320MHz, and the channel bandwidth for transmitting PPDUs is divided into four frequency domain segments.

[0201] In ascending order of frequency, the first frequency domain segment is the first 80MHz, the second frequency domain segment is the second 80MHz, the third frequency domain segment is the third 80MHz, and the fourth frequency domain segment is the fourth 80MHz. This embodiment specifically illustrates the first signaling field transmitted in the first frequency domain segment corresponding to one 80MHz segment and the second signaling field transmitted in the second frequency domain segment corresponding to the second 80MHz segment. The signaling fields transmitted in the third frequency domain segment corresponding to the third 80MHz segment and the fourth frequency domain segment corresponding to the fourth 80MHz segment are not listed individually in this embodiment.

[0202] Please see Figure 8A , Figure 8AThis is a schematic diagram illustrating the resource unit allocation scenario according to an embodiment of this application. In one example, the actual allocation of resource units corresponding to the 320MHz channel bandwidth is as follows: the lowest frequency of 40MHz in the first 80MHz corresponds to one 484-tone RU, which is allocated to two STAs docked in the first frequency domain segment. The highest frequency of 40MHz in the first 80MHz corresponds to one 484-tone RU, which is allocated to two STAs docked in the first frequency domain segment. The lowest frequency of 20MHz in the second 80MHz corresponds to one 242-tone RU, which is allocated to four STAs docked in the second frequency domain segment; the next second lowest frequency of 20MHz corresponds to nine 26-tone RUs, which are allocated to nine STAs docked in the second frequency domain segment. The highest frequency of 40MHz in the second 80MHz corresponds to a 484-tone RU, which is assigned to a STA docked in the first frequency domain segment; the allocation of RUs for the third and fourth 80MHz is not shown.

[0203] like Figure 8B , Figure 8B This is a schematic diagram of the content channel structure according to an embodiment of this application. The first signaling field of the first frequency domain segmented transmission is sent through two CCs, namely CC1 and CC2. The signaling field of the first frequency domain segmented transmission includes resource unit allocation subfield 1 to resource unit allocation subfield 16. In order of frequency from low to high, resource unit allocation subfield 1 to resource unit allocation subfield 16 respectively correspond to one 20MHz in 320MHz.

[0204] Specifically, resource unit allocation subfields with odd-numbered sequence numbers are transmitted in CC1, while resource unit allocation subfields with even-numbered sequence numbers are transmitted in CC2. This effectively shortens the length of the common fields transmitted in each CC.

[0205] Figure 8C This is a schematic diagram of the signaling field structure according to an embodiment of this application. Please refer to... Figure 8B and Figure 8CResource unit allocation subfield 1 indicates a 484-tone RU, and indicates that the number of user fields corresponding to the 484-tone RU contained in CC1 is 1. Resource unit allocation subfield 2 indicates a 484-tone RU, and indicates that the number of user fields corresponding to the 484-tone RU contained in CC2 is 1. Resource unit allocation subfield 3 indicates a 484-tone RU, and indicates that the number of user fields corresponding to the 484-tone RU contained in CC1 is 1. Resource unit allocation subfield 4 indicates a 484-tone RU, and indicates that the number of user fields corresponding to the 484-tone RU contained in CC2 is 1. Resource unit allocation subfield 5 indicates a 484-tone RU, and indicates that the number of user fields corresponding to the 484-tone RU contained in CC1 is 1. Resource unit allocation subfield 6 indicates a 484-tone RU, and indicates that the number of user fields corresponding to the 484-tone RU contained in CC2 is 1. Resource unit allocation subfield 7 indicates a 484-tone RU and indicates that the number of user fields corresponding to the 484-tone RU contained in CC1 is 1. Resource unit allocation subfield 8 indicates a 484-tone RU and indicates that the number of user fields corresponding to the 484-tone RU contained in CC1 is 0.

[0206] A STA docked in a frequency domain segment can determine the RU corresponding to each user field based on the order of the RUs corresponding to the resource unit allocation subfields in each CC of the frequency domain segment and the order of the user fields in the CC.

[0207] For example, STA1, docked in the first frequency segment, can determine the user field corresponding to the 484-tone RU at the lowest frequency of the first 80MHz as 1a based on the order of the RUs indicated by the resource unit allocation subfields in CC1 and CC2 and the order of the user fields. User field 1a carries STA1's identification information, thus STA1 determines that this 484-tone RU is the RU assigned to it. Similarly, STA2, docked in the first frequency segment, determines that the 484-tone RU is the RU assigned to it based on user field 2a and the STA2 identification information carried therein. STA3, docked in the first frequency segment, can determine that the 484-tone RU at the highest frequency of the first 80MHz is the RU assigned to it based on the STA3 identification information carried in user field 3a. STA4, docked in the first frequency segment, can determine that the 484-tone RU at the highest frequency of the first 80MHz is the RU assigned to it based on the STA4 identification information carried in user field 4a. STA5 docked in the first frequency domain segment can determine the 484-tone RU corresponding to the highest frequency of 40MHz in the second 80MHz segment as the RU assigned to it, based on the STA5 identification information carried in user field 5a.

[0208] Therefore, in the first signaling field of the first frequency domain segment transmission, the resource unit allocation subfield indicates that the lowest frequency of 40MHz in the second 80MHz segment corresponds to a 484-tone RU, and the number of user fields corresponding to this 484-tone RU is 0. However, the RU corresponding to this 40MHz is actually one 242-tone RU and nine 26-tone RUs, all of which are not assigned to STAs docked in this frequency domain segment. Therefore, STAs docked in the first frequency domain segment do not need to care which STA is assigned to this one 242-tone RU and nine 26-tone RUs. In the first signaling field, the resource unit allocation subfield may not indicate the 242-tone RU and nine 26-tone RUs according to the actual situation, and the user-specific field part does not need to be set with user fields according to the actual situation.

[0209] In this way, compared with the existing technology, the user-specific field section requires setting one user field corresponding to the 242-tone RU (assuming that the 242-tone is only assigned to one STA) and nine user fields corresponding to the nine 26-tone RUs. In this embodiment, the user-specific field section of the first signaling field does not set user fields corresponding to the one 242-tone RU and the nine 26-tone RUs, thereby saving at least 10 user fields and reducing the overhead of signaling fields.

[0210] Furthermore, in the resource unit allocation subfield of the first signaling field, this one 242-tone RU and nine 26-tone RUs are treated as a single 484-tone RU. In the second signaling field for second frequency domain fragmented transmission, the two 484-tone RUs corresponding to the lowest frequency of 80MHz of the channel bandwidth for transmitting PPDUs are combined into a single 996-tone RU. This makes the indication in the resource unit allocation subfield simpler and clearer.

[0211] Furthermore, such as Figure 8C Following the order of frequency from low to high, the 40MHz corresponding to the lowest frequency of the first 80MHz band is allocated to two users docked in the first frequency domain segment. Resource unit allocation subfield 1 and resource unit allocation subfield 2 indicate this 484-tone RU. Resource unit allocation subfield 1 indicates that there is one user field in CC1 corresponding to this 484-tone RU. Therefore, the user-specific field portion of CC1 includes user field 1a corresponding to this 484-tone RU. Resource unit allocation subfield 3 indicates that there is one user field in CC2 corresponding to this 484-tone RU. Therefore, the user-specific field portion of CC1 includes user field 3a corresponding to this 484-tone RU. In this way, the multiple user fields corresponding to this 484-tone RU are distributed as evenly as possible across CC1 and CC2 for transmission, resulting in a more balanced number of user fields transmitted in each CC.

[0212] Please see Figure 8D For STAs docked in the second frequency domain segment, the second signaling field of the PPDU transmitted by the AP is transmitted through the second frequency domain segment. Specifically, the second signaling field is transmitted on two CCs, CC3 and CC4. The second signaling field transmitted in the second frequency domain segment includes resource unit allocation subfields 17 to 32. In ascending order of frequency, resource unit allocation subfields 17 to 32 correspond to a 20MHz segment within the 320MHz band.

[0213] Specifically, resource unit allocation subfields with odd-numbered sequence numbers are transmitted in CC3, while resource unit allocation subfields with even-numbered sequence numbers are transmitted in CC4. This effectively shortens the length of the common fields transmitted in each CC.

[0214] Please see Figure 8D and Figure 8E , Figure 8D This is a schematic diagram of the content channel structure according to another embodiment of this application. Figure 8EThis is a schematic diagram of the signaling fields according to another embodiment of this application. Resource unit allocation subfield 17 indicates a 996-tone RU and indicates that the number of user fields corresponding to the 996-tone RU in CC3 is 0. Resource unit allocation subfield 18 indicates a 996-tone RU and indicates that the number of user fields corresponding to the 996-tone RU in CC4 is 0. Resource unit allocation subfield 19 indicates a 996-tone RU and indicates that the number of user fields corresponding to the 996-tone RU in CC3 is 0. Resource unit allocation subfield 20 indicates a 996-tone RU and indicates that the number of user fields corresponding to the 996-tone RU in CC4 is 0. Resource unit allocation subfield 21 indicates a 242-tone RU and indicates that the number of user fields corresponding to the 242-tone RU in CC3 is 4. Resource unit allocation subfield 22 indicates nine 26-tone RUs, and indicates that the number of user fields corresponding to these nine 26-tone RUs in CC4 is nine. Resource unit allocation subfield 23 indicates a 484-tone RU, and indicates that the number of user fields corresponding to these 484-tone RUs in CC3 is zero. Resource unit allocation subfield 8 indicates a 484-tone RU, and indicates that the number of user fields corresponding to these 484-tone RUs in CC4 is zero.

[0215] A STA docked in a frequency domain segment can determine the RU corresponding to each user field based on the order of the RUs corresponding to the resource unit allocation subfields in each CC of the frequency domain segment and the order of the user fields in the CC.

[0216] For example, STA6, docked in the second frequency segment, can determine its assigned RU based on the STA6 identification information in user field 1b, specifically the 242-tone RU corresponding to the lowest 20MHz frequency in the second 80MHz segment. Similarly, STA7, docked in the second frequency segment, can determine its assigned RU based on the STA7 identification information in user field 2b. STA8, docked in the second frequency segment, can determine its assigned RU based on the STA8 identification information in user field 3b. STA9, docked in the second frequency segment, can determine its assigned RU based on the STA9 identification information in user field 4b. Other STAs docked in the second frequency segment can also use the above method to determine the RU corresponding to the user field containing their own STA's identification information as their assigned RU.

[0217] Therefore, the Resource Unit Allocation subfield in the second signaling field indicates that the RU corresponding to the lowest frequency of 80MHz of the channel bandwidth for transmitting the PPDU is a 996-tone RU, and indicates that the number of user fields corresponding to this 996-tone RU in a specific part of the user field is 0. However, in reality, the RUs corresponding to the lowest frequency of 80MHz of the channel bandwidth for transmitting the PPDU are actually two 484-tone RUs, both of which are not assigned to STAs docked in this frequency domain segment. STAs docked in the second frequency domain segment do not need to care which STA these two 484-tone RUs are assigned to. In the second signaling field, the Resource Unit Allocation subfield may not actually indicate two 484-tone RUs, nor may it actually indicate the user fields corresponding to these two 484-tone RUs.

[0218] In this way, compared with the existing technology, which requires setting the user-specific field corresponding to the two 484-tone RUs according to the actual RU allocation, in the embodiment, the user-specific field part of the second signaling field does not set the user field corresponding to the two 484-tone RUs, thereby saving the user field corresponding to the two 484-tone RUs and reducing the overhead of the signaling field.

[0219] In another implementation, the resource element allocation subfield in the second signaling field indicates that the RU corresponding to the lowest frequency of 80MHz of the channel bandwidth for transmitting the PPDU is a 996-tone RU, and the number of user fields corresponding to it is 1. Therefore, the number of user fields corresponding to this 996-tone RU in a specific part of the user fields is 1. This also saves at least 1 user field from the 4 user fields corresponding to two 484-tone RUs.

[0220] In this way, on the one hand, two 484-tone RUs can be treated as one 996-tone RU for indication, reducing the number of resource unit allocation subfield indication RUs. Thus, the number of user fields corresponding to one 996-tone RU is less than the number of user fields corresponding to two 484-tone RUs. On the other hand, in user-specific fields, the number of user fields corresponding to that RU is also set to the minimum as much as possible, such as 1 or 0. In this way, the number of user fields can be greatly reduced, thereby saving indication overhead.

[0221] Figure 9 This is a schematic diagram illustrating a scenario of resource unit allocation according to an embodiment of this application. For example... Figure 9 As shown, in another example, the actual allocation of these 320MHz resource units is as follows, in ascending order of frequency: the first 80MHz corresponds to one 996-tone RU, which is allocated to the three STAs docked in the first frequency segment. The lowest 20MHz of the second 80MHz corresponds to one 242-tone RU, allocated to one STA docked in the first frequency segment. The second lowest 20MHz of the second 80MHz corresponds to nine 26-tone RUs, allocated to nine STAs docked in the second frequency segment. The highest 40MHz of the second 80MHz corresponds to a 484-tone RU, allocated to one STA docked in the first frequency segment; for simplicity, the third and fourth 80MHz are... Figure 9 It is not shown in the text.

[0222] The resource unit allocation indication subfield in the first signaling field of the PPDU transmitted in the first frequency domain indicates that, in ascending order of frequency, the first 80MHz corresponds to one 996-tone RU, and there are 3 user fields corresponding to this 996-tone RU in the user-specific field section; the lowest frequency of 20MHz in the second 80MHz corresponds to one 242-tone RU, and there is 1 user field corresponding to this 242-tone RU in the user-specific field section; the second lowest frequency of 20MHz in the second 80MHz corresponds to one 242-tone RU, and there are 0 user fields corresponding to this 242-tone RU in the user-specific field section; the highest frequency of 40MHz in the second 80MHz corresponds to one 484-tone RU, and there is 1 user field corresponding to this 484-tone RU in the user-specific field section.

[0223] As can be seen, following the frequency order from low to high, the RU corresponding to the second 20MHz within the second 80MHz band is actually nine 26-tone RUs, all of which are not assigned to STAs docked in this frequency domain segment. Therefore, STAs docked in the first frequency domain segment do not need to care which STA these nine 26-tone RUs are assigned to. The resource unit allocation subfield of the first frequency domain segment transmission may not actually indicate the 242-tone RU and the nine 26-tone RUs. For example, the resource unit allocation subfield of the first frequency domain segment transmission may indicate that this 20MHz band corresponds to one 242-tone RU, and the number of user fields corresponding to this 242-tone RU is 0. This one 242-tone RU can be understood as the second RU.

[0224] In this way, compared with the prior art, the user-specific field section requires setting the 9 user fields corresponding to the 9 26-tone RUs. In this embodiment, the user-specific field section of the first signaling field does not set the user fields corresponding to these 9 26-tone RUs, thereby saving at least 9 user fields and reducing the overhead of signaling fields.

[0225] The resource unit allocation indication subfield in the second signaling field of the PPDU included in the second frequency domain segmented transmission indicates that, in ascending order of frequency, the first 80MHz corresponds to one 996-tone RU, and there are 0 user fields corresponding to this 996-tone RU in the user-specific field section; the lowest frequency of 20MHz in the second 80MHz corresponds to one 242-tone RU, and there are 0 user fields corresponding to this 242-tone RU in the user-specific field section; the second lowest frequency of 20MHz in the second 80MHz corresponds to nine 26-tone RUs, and there are nine user fields corresponding to these nine 26-tone RUs in the user-specific field section; the highest frequency of 40MHz in the second 80MHz corresponds to a 484-tone RU, and there are 0 user fields corresponding to this 484-tone RU in the user-specific field section.

[0226] As can be seen, in order of frequency from low to high, the 996-tone RU corresponding to the first 80MHz, the 242-tone RU corresponding to the lowest frequency of 20MHz in the second 80MHz, and the 484-tone RU corresponding to the highest frequency of 40MHz in the second 80MHz are all RUs not assigned to STAs docked in this frequency domain segment.

[0227] In this way, compared with the prior art, the user-specific field section requires setting the user field corresponding to the 996-toneRU, the user field corresponding to the 242-toneRU, and the user field corresponding to the 484-toneRU. In this embodiment, the user-specific field section of the first signaling field does not set the user field corresponding to the 996-toneRU, the user field corresponding to the 242-toneRU, and the user field corresponding to the 484-toneRU, thereby effectively saving user fields and reducing signaling field overhead.

[0228] As can be seen from the above example, if the RUs corresponding to the channel bandwidth for transmitting PPDUs include multiple RUs that are not assigned to STAs docked in this frequency domain segment, the resource element allocation subfield in the signaling field can treat these multiple RUs as a single larger RU. In this way, the resource element allocation subfield can provide a simplified indication of multiple RUs that are not assigned to STAs docked in this frequency domain segment. It should be understood that such a simplified indication requires the existence of a corresponding index in the RA subfield table (e.g., Table 1, Table 2, or Table 3) that can support indicating these multiple RUs as a single RU.

[0229] For example, the above Figure 8AIn the example, one 242-tone RU and nine 26-tone RUs are both RUs assigned to STAs docked in the first frequency domain segment. In Table 1, there exists index 01110010, which indicates a 484-tone RU, and the user field corresponding to this 484-tone RU is 0. Therefore, in the resource unit allocation subfield of the first signaling field, this one 242-tone RU and the nine consecutive 26-tone RUs can be indicated together as a 484-tone RU through the corresponding index (e.g., 01110010), indicating that the number of user fields corresponding to this 484-tone RU is 0.

[0230] In another implementation, the resource unit allocation subfield of the first frequency domain segmentation transmission indicates that the 20MHz corresponds to one 242-tone RU, and the number of user fields corresponding to the 242-tone RU is one. The station identifier carried by this user field does not belong to any station docked in the first frequency domain segment. Thus, compared to the prior art, where the user-specific field section requires setting nine user fields corresponding to the nine 26-tone RUs, in this embodiment, the user-specific field portion of the first signaling field only sets the user field corresponding to this one 242-tone RU, thereby saving at least eight user fields and reducing signaling field overhead.

[0231] In another implementation, the resource unit allocation subfield of the first frequency domain segmentation transmission indicates a combination of multiple 52-tone RUs and 26-tone RUs corresponding to the 20MHz band. For example, in Table 1, 00001111 corresponds to five 52-tone RUs, 52-tone RUs, 26-tone RUs, 52-tone RUs, and 52-tone RUs. Each RU corresponds to one user field, and the station identifier carried by this user field does not belong to any station docked in the first frequency domain segment. Thus, compared to the prior art, where the user-specific field section requires setting nine user fields corresponding to the nine 26-tone RUs, in this embodiment, the user-specific field section of the first signaling field sets five user fields corresponding to these five RUs, thereby saving at least four user fields and reducing signaling field overhead.

[0232] Furthermore, the multiple RUs not allocated to STAs docked in this frequency domain segment can all be RUs with fewer than 242 subcarriers. Alternatively, the multiple RUs can all be small RUs. Or, at least a portion of the subcarriers corresponding to the large RUs not allocated to STAs docked in the first frequency domain segment belong to at least two small RUs. In this embodiment, if at least 20MHz of the channel bandwidth for transmitting the PPDU corresponds to multiple small RUs, and all of them are not allocated to STAs docked in this frequency domain segment, the resource element allocation subfield in the signaling field of the PPDU transmitted in this frequency domain segment can indicate these consecutive multiple small RUs as a single large RU, and indicate that the number of user fields corresponding to this single large RU is 0. It should be understood that such a simplified indication also requires the existence of a corresponding index in the RA subfield table (e.g., Table 1, Table 2, or Table 3) that can indicate multiple RUs as a single RU.

[0233] For example, such as Figure 10 As shown, Figure 10 This is a schematic diagram illustrating the resource unit allocation scenario in an embodiment of this application. The 20MHz channel bandwidth for transmitting PPDUs corresponds to nine 26-tone RUs. The two 26-tone RUs with the lowest frequency are allocated to STAs docked in the first frequency domain segment, while the other seven 26-tone RUs are not allocated to STAs docked in either the first or second frequency domain segment. It can be understood that all RUs corresponding to this 20MHz frequency segment are not allocated to STAs docked in the second frequency domain segment.

[0234] The signaling field of the PPDU containing the first frequency domain segmentation transmission includes the resource unit allocation indication subfield corresponding to the 20MHz, indicating that the RU frequencies corresponding to the 20MHz include, from low to high, two 26-tone RUs, one 52-tone RU, one 26-tone RU, and one 106-tone RU, with each RU corresponding to a user field.

[0235] In Table 1, there exists an index 01110001 that can indicate a 242-tone RU, and that the user field corresponding to this 242-tone RU is 0. Therefore, in the signaling field of the second frequency domain segmented transmission, the resource unit allocation subfield can be indicated by the corresponding index (e.g., 01110001) to indicate that the RU corresponding to this 20MHz is a 242-tone RU, and that the user field corresponding to this 242-tone RU is 0.

[0236] For example, Figure 8AThe nine 26-tone RUs in the first signaling field are all RUs not assigned to the STAs in the first frequency domain segment. Therefore, in the resource unit allocation subfield of the first signaling field, the nine 26-tone RUs can be identified as a single 242-tone RU by index 01110001, and the user field corresponding to this single 242-tone RU can be set to 0.

[0237] Therefore, according to existing technology, if the resource unit allocation subfield in the signaling field indicates multiple small RUs according to the actual situation, the user-specific field of the signaling field needs to include the user field corresponding to each of these multiple small RUs. However, according to the solution of this application, in the resource allocation unit subfield of the signaling field, these multiple small RUs that are not docked to the STA in this frequency domain segment are merged and indicated into one large RU, and the number of user fields corresponding to this large RU is 0. In this way, the user-specific field of the signaling field does not include the user fields corresponding to these multiple small RUs, thereby effectively saving user fields and reducing the overhead of the signaling field.

[0238] In some other possible implementations, the resource unit allocation subfield in the signaling field indicates the RU using the second simplified indication method described above.

[0239] In this embodiment, the signaling field includes at least one resource element allocation subfield indicating that the RU is a plurality of small RUs. Each of the plurality of small RUs corresponds to at least one user field. At least one of the plurality of small RUs includes a user field corresponding to a third RU carrying an identifier of a STA docked in the first frequency domain segment. At least one fourth RU corresponds to a user field that does not carry an identifier of a STA docked in the first frequency domain segment. The fourth RU is actually at least two small RUs not allocated to STAs docked in this frequency domain segment. In other words, at least a portion of the subcarrier corresponding to the fourth RU belongs to at least two RUs.

[0240] It is understandable that if the channel bandwidth for transmitting a PPDU includes a 20MHz RU corresponding to multiple smaller RUs, and among these smaller RUs, at least one RU is assigned to a STA docked in this frequency domain segment, and at least two RUs are not assigned to a STA docked in this frequency domain segment, then the signaling field of the PPDU transmitted in this frequency domain segment, indicating that the resource unit allocation subfield corresponding to this 20MHz, can treat these at least two RUs as one RU and indicate that this one RU corresponds to a user field. Alternatively, it can be said that the resource unit allocation subfield corresponding to this 20MHz can treat these multiple RUs as a larger RU and indicate that this one RU corresponds to the same user field. It should be understood that the larger RU can find its corresponding index in the RAsubfield table.

[0241] Therefore, in the user-specific field section, the number of user fields corresponding to each RU is 1. That is to say, these at least two RUs correspond to only one user field. Thus, by setting the signaling field content in the above way, compared to indicating according to the actual situation, at least one user field can be reduced in the signaling fields, thereby saving signaling field overhead.

[0242] For example, such as Figure 11 , Figure 11 This is a schematic diagram of resource unit allocation in an embodiment of this application. If a 20MHz RU corresponds to nine 26-tone RUs within the channel bandwidth for transmitting PPDUs, then, in ascending order of frequency, the first and second 26-tone RUs are allocated to STAs docked in the first frequency domain segment, and the third and fourth 26-tone RUs are allocated to STAs docked in the second frequency domain segment.

[0243] In the signaling field of the PPDU transmitted in the first frequency domain, the resource unit allocation subfield corresponding to the 20MHz can indicate a total of 5 RUs: 2 26-tone RUs, 1 52-tone RU, 1 26-tone RU, and 1 106-tone RU.

[0244] In the signaling field of the PPDU transmitted in the second frequency domain, the resource unit allocation subfield corresponding to the 20MHz can indicate one 52-tone RU, two 26-tone RUs, one 26-tone RU, and one 106-tone RU, for a total of 5 RUs.

[0245] When the resource unit allocation subfield in the signaling field indicates multiple small RUs, the user-specific field in the signaling field includes one user field corresponding to each small RU. Therefore, if the resource unit allocation subfield indicates according to the actual RU allocation, in both the first and second frequency domain segments, the resource unit allocation subfield corresponding to the 20MHz MHz segment will indicate nine 26-tone RUs. Thus, the user-specific field includes nine user fields corresponding one-to-one with the nine 26-tone RUs indicated by the resource unit allocation subfield. However, if the resource unit allocation subfield indicates five RUs in the same manner, then the user-specific field will also only contain five user fields corresponding to the RUs indicated by the resource unit allocation subfield.

[0246] As can be seen, the solution of this application, by giving a merging instruction for at least two small RUs not assigned to STAs docked in this frequency domain, can reduce the number of user fields corresponding to multiple consecutive small RUs not assigned to STAs docked in this frequency domain in the user-specific field part of the signaling field, thereby saving signaling field overhead.

[0247] It should be understood that the second simplified indication method is not limited to indicating small RUs; it can also be used to indicate large RUs, or both large and small RUs. Thus, if the RUs corresponding to the channel bandwidth for transmitting PPDUs include at least two RUs allocated to STAs docked in this frequency domain segment, then in the signaling field of the transmission in this frequency domain segment, the resource element allocation subfield can indicate that these at least two RUs constitute a larger RU, and indicate that the user field corresponding to this larger RU is 1. These at least two RUs can both be large RUs, both be small RUs, or may include at least one small RU and at least one large RU.

[0248] Examples of these three scenarios are provided below.

[0249] For an example illustrating that at least two RUs are large RUs, the above can be used as a basis. Figure 8A For example, in the 320MHz channel bandwidth for transmitting PPDUs, the two highest 80MHz frequencies are allocated to 484-tone RUs (large RUs) of STAs docked in the first frequency domain segment, and each 484-tone RU is allocated to two STAs docked in the first frequency domain segment. Therefore, in the signaling field of the second frequency domain segment transmission, the resource unit allocation subfield can indicate that the two 484-tone RUs are combined into a single 996-tone RU, and indicate that the user field corresponding to this 996-tone RU is 1. Thus, compared to the prior art which requires setting four user fields corresponding to the two 484-tone RUs in the user-specific field section according to the actual allocation, this embodiment only requires setting one user field corresponding to the 996-tone RU, thereby saving the number of user fields and reducing the overhead of the signaling fields.

[0250] Examples of at least two RUs including at least one small RU and at least one large RU can be based on the above. Figure 8AFor example, in a 320MHz channel bandwidth for transmitting PPDUs, in ascending order of frequency, the second 80MHz lowest frequency (40MHz) corresponds to one 242-tone RU (large RU) and nine 26-tone RUs (small RUs). This one 242-tone RU is allocated to four STAs docked in the second frequency domain segment, and the nine 26-tone RUs are allocated to nine STAs docked in the second frequency domain segment. Therefore, in the signaling field of the first frequency domain segment transmission, the resource unit allocation subfield can combine this one 242-tone RU and the nine 26-tone RUs into one 484-tone RU, and indicate that the user field corresponding to this 484-tone RU is 1. In this way, compared with the prior art which requires setting 13 user fields corresponding to one 242-tone RU and nine 26-tone RUs according to the actual allocation, the solution in this embodiment only requires setting one user field corresponding to the 484-tone RU, thereby saving the number of user fields and reducing the overhead of signaling fields.

[0251] For examples illustrating that at least two RUs are small RUs, please refer to the above. Figure 11 Corresponding examples will not be elaborated here.

[0252] In the second simplified indication method described above, the resource unit allocation subfield of the common field section in the signaling field indicates at least two RUs as a larger large RU, and indicates that the user field corresponding to this larger large RU is 1. In the user-specific field section, the user field corresponding to this larger RU can be a special user field, which is used to indicate that the corresponding RU is not fragmented to stations docked in this frequency domain. This special user field can be, for example, but not limited to, "2046".

[0253] In some optional embodiments, the user field includes a fragmentation indicator subfield, which indicates the frequency domain fragment to which the STA corresponding to the user field will dock upon the next PPDU reception. That is, the user field includes the STA identifier and the fragmentation indicator subfield. Optionally, the fragmentation indicator subfield may have 2 bits. It should be understood that this optional embodiment can be implemented in conjunction with any of the above embodiments, or it can be implemented alone.

[0254] The frequency segment where the STA will dock for the next PPDU reception can be the same as or different from the frequency segment where it docked for the current PPDU reception. For example, if the STA currently receives PPDUs docked in the first frequency segment, then the segmentation indicator subfield in the user field corresponding to that STA can indicate that the STA will receive PPDUs in the first frequency segment next time, or it can indicate that the STA will receive PPDUs in a frequency segment other than the first frequency segment next time.

[0255] This allows the signaling field to indicate the frequency domain segment to which the STA is switching docks, thus ensuring the reliability of the frequency domain segment to which the STA is switching docks.

[0256] The method for indicating the Resource Unit Allocation Subfield (RU) according to an embodiment of this application is described in detail below.

[0257] It should be noted that in the method for indicating RU by allocating subfields of resource units, which will be described below with reference to Tables 2 to 5 in the embodiments of this application, the method for indicating the merging of multiple RUs or the method for indicating the allocation of multiple RUs to a STA can be implemented independently.

[0258] Please refer to Table 2, which can be understood as the RA subfield table. The resource unit allocation subfield includes two parts of fields used to indicate resource unit allocation and merging, referred to here as the resource unit indication part and the merging indication part. The merging indication part is also referred to as the additional field of the resource unit allocation subfield. The resource unit indication is used to indicate the resource unit corresponding to the resource unit allocation subfield, and the merging indication is used to indicate the merging relationship between the resource unit and other resource units. Table 2 includes entries indicating that RUs with 106 or more subcarriers are allocated to 0-16 STAs.

[0259] Please refer to Table 2 for details. The resource unit indication part in the resource unit allocation subfield can be an 8-bit binary string (B7 B6 B5 B4 B3 B2 B1 B0) corresponding to an entry number in the first column of Table 2. For example, the resource unit indication for entry 0 is 00000000, the resource unit indication for entry 1 is 00000001, and the resource unit indication for entry 2 is 00000010. The resource unit indications for the remaining entries can be deduced accordingly, and will not be listed here. The resource unit indication and corresponding merge indication for each entry can be understood as an index.

[0260] Table 2

[0261]

[0262]

[0263]

[0264]

[0265]

[0266] The merge indication section in the resource unit allocation subfield is an entry in the second column corresponding to the resource unit indication section. The rows containing the entries corresponding to the resource unit indication section and the merge indication section indicate the size and location of one or more resource units corresponding to the 20MHz transmission of this resource unit allocation subfield.

[0267] Resource elements with fewer than 10⁶ subcarriers can only be allocated to one STA, while resource elements with 10⁶ or more subcarriers can be allocated to one or more STAs. In 802.11be, resource elements with 10⁶ or more subcarriers can be allocated to up to 16 STAs.

[0268] Each resource unit indicated by the resource unit allocation subfield corresponding to each of the 0-15 entries in the resource unit indication section is used to allocate only one STA. That is to say, each resource unit indicated by the resource unit allocation subfield corresponding to each of the 0-15 entries in the resource unit indication section is less than 106 subcarriers.

[0269] Each of the 16-255 entries in the Resource Element Indication section indicates one or more resource elements in its corresponding Resource Element Allocation Subfield, including at least one resource element with 106 subcarriers or more. Each of the 16-255 entries in the Resource Element Indication section also indicates one or more resource elements in its corresponding Resource Element Allocation Subfield, signifying that a resource element can be allocated to multiple STAs.

[0270] As shown in Table 2, the resource unit indication portion of the resource unit allocation subfield is 8 bits (B7 B6 B5 B4 B3B2 B1B0), and the merge indication portion is 2 bits (B1B0). The resource unit indication portion includes a total of 256 entries, and each entry in the resource unit indication portion corresponds to 4 entries in the merge indication portion.

[0271] If the merge instruction is 00, it indicates that the RU has not been merged with other RUs. Therefore, in Table 2, if the merge instruction is 00, the contents indicated by entries 0-115 are the same as those in Table 1 provided by 802.11ax.

[0272] For small RUs, the merge instruction is 01, indicating that the RU is merged with the adjacent low-frequency RU to form a multi-RU in ascending order of frequency. For example, in entry 2 of Table 2, the merge instruction is 01, indicating that the 26-tone RU of #8 is merged with the 52-tone RU of the lower frequency to the left to form a multi-RU.

[0273] The merge instruction of 10 indicates that RUs are merged into multi-RUs in ascending order of frequency with adjacent high-frequency RUs.

[0274] The merge instruction of 11 indicates that among the RUs corresponding to the resource unit allocation subfield, one RU is merged into a multi-RU by combining it with the adjacent high-frequency RU in ascending order of frequency, and the other RU is merged into a multi-RU by combining it with the adjacent low-frequency RU. For example, in entries 40-47 of Table 2, merge instruction 11 indicates that the 26-tone RU of #2 is merged into a multi-RU by combining it with the adjacent high-frequency 52-tone RU on the right, and indicates that the 106-tone RU of #6 is merged into a multi-RU by combining it with the adjacent low-frequency 26-tone RU on the left.

[0275] Of course, in other embodiments, the meanings of 01, 10, and 11 in the merge instruction can be interchanged.

[0276] For example, a merge instruction of 01 indicates that among the RUs corresponding to the resource unit allocation subfield, one RU is merged into a multi-RU by combining it with adjacent high-frequency RUs in ascending order of frequency, and another RU is merged into a multi-RU by combining it with adjacent low-frequency RUs. A merge instruction of 10 indicates that RUs are merged into a multi-RU by combining it with adjacent low-frequency RUs in ascending order of frequency. A merge instruction of 11 indicates that RUs are merged into a multi-RU by combining it with adjacent high-frequency RUs in ascending order of frequency.

[0277] For example, a merge instruction of 01 indicates that an RU is merged with an adjacent high-frequency RU to form a multi-RU, in ascending order of frequency. A merge instruction of 10 indicates that among the RUs corresponding to the resource unit allocation subfield, one RU is merged with an adjacent high-frequency RU to form a multi-RU, and the other RU is merged with an adjacent low-frequency RU to form a multi-RU. A merge instruction of 11 indicates that an RU is merged with an adjacent low-frequency RU to form a multi-RU, in ascending order of frequency.

[0278] In this embodiment, the constraints for merging multiple RUs include several. One constraint includes: 1. Small RUs and large RUs are not merged; 2. The merging of small RUs shall not cross the 20MHz channel boundary; 3. The merging of small RUs should be continuous (or adjacent). Based on the above constraints, the merging of small RUs can be: a continuous 52-tone RU and a 26-tone RU within 20MHz, or a continuous 106-tone RU and a 26-tone RU within 20MHz. Specifically, the position of a continuous 52-tone RU and a 26-tone RU within 20MHz can be: the 52-tone RU is to the left of the 26-tone RU, or the 52-tone RU is to the right of the 26-tone RU; the position of a continuous 106-tone RU and a 26-tone RU within 20MHz can be: the 106-tone RU is to the left of the 26-tone RU, or the 106-tone RU is to the right of the 26-tone RU. A constrained RU merging method is called a restricted RU merging method. This method balances the flexibility of merging with the gains it brings, making merging multiple RUs more reasonable and less complex. Of course, RU merging can also be done without any constraints, meaning any RU can be merged with each other; this method is called an unconstrained RU merging method.

[0279] Table 2 adds entries indicating the merging of large RUs. For example, when the merge instruction for entries 113-255 is 10, it can indicate the merging of large RUs.

[0280] To facilitate understanding, the contents indicated by some of the items in Table 2 are explained in detail below.

[0281] Entry 113 of the resource unit indication in Table 2 indicates a 242-tone RU, and this 242-tone RU is not assigned to a STA docked in the frequency domain segment containing this 20MHz. The merge indication 00 corresponding to entry 113 of the resource unit indication indicates that this 242-tone RU is not merged with other RUs to form a multi-RU. The merge indication 01 corresponding to entry 113 of the resource unit indication indicates a 242+484 multi-RU, which is continuous within 80MHz and is formed by merging a 242-tone RU and a 484-tone RU.

[0282] In Table 2, entry 114 of the resource unit indication indicates a 484-tone RU, which is not assigned to any STA docked in the 20MHz frequency domain segment. The merge indication 00 corresponding to entry 114 of the resource unit indication indicates that the 484-tone RU is not merged with other RUs into a multi-RU. The merge indication 01 corresponding to entry 114 of the resource unit indication indicates a 484+242 multi-RU, which is contiguous within 80MHz and is formed by merging a 484-tone RU and a 242-tone RU. The merge indication 10 corresponding to entry 114 of the resource unit indication indicates a 484+242 multi-RU, which is discontinuous within 80MHz and is formed by merging a 484-tone RU and a 242-tone RU. The resource unit indicates entry 114, which corresponds to merge indication 11, indicating 484+996 multi-RU, and is continuous within 160MHz. The 484+996 multi-RU is formed by merging 484-tone RU and 996-tone RU.

[0283] In Table 2, resource unit indication entry 115 indicates a 996-tone RU, and this 996-tone RU is not assigned to any STA docked in the frequency domain segment containing this 20MHz. The corresponding merge indication 01 for resource unit indication entry 115 indicates a 996+484multi-RU, which is contiguous within 160MHz and is formed by merging a 996-tone RU and a 484-tone RU. The corresponding merge indication 10 for resource unit indication entry 115 indicates a 996+484multi-RU, which is discontinuous within 160MHz and is formed by merging a 996-tone RU and a 484-tone RU. The resource unit indicates entry 115, which corresponds to merge indication 11, indicating 996+2*996 multi-RU, and is continuous within 320MHz. The 996+2*996 multi-RU is formed by merging 996-tone RU and 2*996-tone RU.

[0284] Entry 116 of the resource unit indication in Table 2 indicates a 2*996-tone RU, and this 2*996-tone RU is not assigned to a STA docked in the frequency domain segment containing this 20MHz. The merge indication 00 corresponding to entry 116 of the resource unit indication indicates that this 2*996-tone RU is not merged with other RUs to form a multi-RU. The merge indication 01 corresponding to entry 116 of the resource unit indication indicates a 2*996+996-tone multi-RU, which is continuous within 320MHz, and is formed by merging 2*996-tone RUs and 996-tone RUs. The merge indication 10 corresponding to entry 116 of the resource unit indication indicates a 2*996+996-tone multi-RU, which is discontinuous within 320MHz, and is formed by merging 2*996-tone RUs and 996-tone RUs.

[0285] In Table 2, resource unit indicators 192-207 indicate 242-tone RUs, and each of these indicators specifies that the 242-tone RU is assigned to one of 16 STAs. The merge indicator 00 corresponding to any one of these resource unit indicators indicates that the 242-tone RU has not been merged with other RUs to form a multi-RU. The merge indicator 01 corresponding to any one of these resource unit indicators indicates a 242+484 multi-RU, which is continuous within an 80MHz range and is formed by merging a 242-tone RU and a 484-tone RU.

[0286] In Table 2, resource unit indication entries 208-223 indicate 484-tone RUs, and each entry indicates that the 484-tone RU is allocated to 1-16 STAs. The merge indication 00 corresponding to any entry in resource unit indication 208-223 indicates that the 484-tone RU is not merged with other RUs to form a multi-RU. The merge indication 01 corresponding to any entry in resource unit indication 208-223 indicates a 484+242 multi-RU, which is contiguous within 80MHz and is formed by merging a 484-tone RU and a 242-tone RU. The merge indication 10 corresponding to any entry in resource unit indication 208-223 indicates a 484+242 multi-RU, which is discontinuous within 80MHz and is formed by merging a 484-tone RU and a 242-tone RU. The resource unit indicates that any one of the entries 208-223 corresponds to the merge instruction 11 indicating 484+996multi-RU, which is continuous within 160MHz. The 484+996multi-RU is formed by merging 484-tone RU and 996-tone RU.

[0287] In Table 2, resource unit indicators 224-239 indicate 996-tone RUs, and each of these indicators specifies that the 996-tone RU is allocated to 1-16 STAs. The merge indicator 00 corresponding to any of these resource unit indicators 224-239 indicates that the 996-tone RU is not merged with other RUs to form a multi-RU. The merge indicator 01 corresponding to any of these resource unit indicators 224-239 indicates a 996+484 multi-RU, which is contiguous within 160MHz and is formed by merging a 996-tone RU and a 484-tone RU. The merge indicator 10 corresponding to any of these resource unit indicators 224-239 indicates a 996+484 multi-RU, which is discontinuous within 160MHz and is formed by merging a 996-tone RU and a 484-tone RU. The resource unit indicates that any one of the entries 224-239 corresponds to a merge instruction 11 indicating a 996+2*996 multi-RU, which is continuous within 320MHz. The 996+2*996 multi-RU is formed by merging a 996-tone RU and a 2*996-tone RU.

[0288] In Table 2, resource unit indicators 240-255 indicate 2*996-tone RUs, and each of these 2*996-tone RUs is assigned to 1-16 STAs. The merge indicator 00 corresponding to any of these resource unit indicators 240-255 indicates that the 2*996-tone RU has not been merged with other RUs to form a multi-RU. The merge indicator 01 corresponding to any of these resource unit indicators 240-255 indicates 2*996+996-tone multi-RUs, consecutive within 320MHz, which are formed by merging 2*996-tone RUs with 996-tone RUs. The resource unit indicates that any one of the entries 240-255 corresponds to a merge instruction 10 indicating a 2*996+996-tone multi-RU, which is discontinuous within 320MHz. The 2*996+996-tone multi-RU is formed by merging 2*996-tone RU and 996-tone RU.

[0289] Thus, the Resource Unit Allocation subfield, by employing the entries in Table 2 provided in this embodiment to indicate RU allocation, can support indicating 16 STAs. Moreover, this indication method makes the structure of the Resource Unit Allocation subfield clearer and simpler. The Resource Unit indication is used to indicate the resource unit allocation and the corresponding number of STAs. The Merge indication is only used to indicate merging, and does not indicate merging in some cases and the number of users in others.

[0290] The above Figure 7A The corresponding implementation can also be applied to scenarios where multiple RUs are allocated to a single STA. In this scenario, the above... Figure 7A The resource unit allocation subfield in the corresponding embodiment can be indicated using the entries in Table 2. For example, Figure 12 A schematic diagram of the scenario allocated to this resource unit, such as... Figure 12 As shown, the channel bandwidth for transmitting PPDUs is 320MHz, and this bandwidth is divided into four frequency domain segments. In ascending order of frequency, the first frequency domain segment is the first 80MHz, the second is the second 80MHz, the third is the third 80MHz, and the fourth is the fourth 80MHz. This embodiment specifically uses the first signaling field transmitted in the first frequency domain segment and the second signaling field transmitted in the second frequency domain segment as examples. The signaling fields transmitted in the third and fourth frequency domain segments are not listed in detail in this embodiment.

[0291] The actual allocation of these 320MHz resource units is as follows, in ascending order of frequency: the first 80MHz corresponds to one 484+242 multi-RU and one 242-tone RU. The 484+242 multi-RU is allocated to the three STAs docked in the first frequency domain segment, and the 242-tone RU is allocated to one STA docked in the first frequency domain segment. The lowest 20MHz frequency in the second 80MHz corresponds to one 242-tone RU, allocated to one STA docked in the first frequency domain segment. The second lowest 20MHz frequency in the second 80MHz corresponds to nine 26-tone RUs, allocated to nine STAs docked in the second frequency domain segment. The highest 40MHz frequency in the second 80MHz corresponds to a 484-tone RU, allocated to one STA docked in the second frequency domain segment. For simplicity, the third and fourth 80MHz are not shown.

[0292] The resource unit allocation indication subfield in the first signaling field of the first frequency domain segmented transmission indicates that: the first 80MHz corresponds to one 484+242 multi-RU and one 242-tone RU, and the number of user fields corresponding to the 484+242 multi-RU in the user-specific field section is 3, and the number of user fields corresponding to the 242-tone RU is 1; the lowest frequency 20MHz in the second 80MHz corresponds to one 242-tone RU, and the number of user fields corresponding to the 242-tone RU in the user-specific field section is 1; the second 20MHz of the second 80MHz corresponds to one 242-tone RU and the highest frequency 40MHz of the second 80MHz corresponds to one 484-tone RU, which are combined into a multi-RU, and the number of user fields corresponding to the multi-RU in the user-specific field section is 0.

[0293] Therefore, the resource unit allocation indication subfield corresponding to the first 20MHz in the first 80MHz can be indicated by entries 208-223 (1100y3y2y1y) in Table 2, which indicates the 484-tone RU and the entry with 2 users (i.e., 1100y3y2y1y = 11010001), and the merging indication 01 indicates that the 484-tone RU is merged with the 242-tone RUs that are consecutive within 80MHz (i.e., the 242-tone RU corresponding to the lowest frequency 20MHz in the second 40MHz in the first 80MHz) into a 484+242multi-RU, and the number of user fields corresponding to the 484+242multi-RU is 2. The resource unit allocation indication subfield corresponding to the second 20MHz in the first 80MHz can be indicated by entries 208-223 (1100y3y2y1y) in Table 2, which indicates the 484-tone RU and the entry with 1 user (i.e., 1100y3y2y1y = 11010000), and the merge indication 01 indicates that the 484-tone RU is merged with the 242-tone RUs that are consecutive within 80MHz (i.e., the 242-tone RU corresponding to the lowest frequency 20MHz in the second 40MHz in the first 80MHz) into a 484+242multi-RU, and the number of user fields corresponding to the 484+242multi-RU is 1. Similarly, the resource unit allocation indicator subfield corresponding to the third 20MHz in the first 80MHz can be identified through entries 192-207 (1100y3y2y1y0) in Table 2, which indicate 242-tone RUs and entries with 0 users, and merge indicator 01 indicating 242-tone RUs. These 242-tone RUs are merged with consecutive 484-tone RUs within the 80MHz (i.e., the 484-tone RUs corresponding to the first and second 20MHz in the first 80MHz) to form a 242+484multi-RU, and the number of user fields corresponding to this 242+484multi-RU is 0. It can be seen that the resource unit allocation indicator subfields corresponding to the first 20MHz, the second 20MHz, and the third 20MHz indicate a total of 3 484+242multi-RUs.

[0294] The resource unit allocation indication subfield corresponding to the second 20MHz of the second 80MHz in the signaling field of the PPDU of the first frequency domain segmented transmission can be indicated by the resource unit indication of entry 113 in Table 2, and the merging indication 10 corresponding to entry 113, indicating that the RU corresponding to the 20MHz is a 242-tone RU. The 242-tone RU and the consecutive 484-tone RUs within 80MHz (that is, the 40MHz of the highest frequency in the second 80MHz corresponds to the 484-tone RU) are merged into a multi-RU, and the number of user fields corresponding to the multi-RU is 0. The resource unit allocation indication subfield corresponding to the third and fourth 20MHz in the second 80MHz can be indicated by the resource unit indication corresponding to entry 114 in Table 2, and the merging indication 01 corresponding to entry 114, indicating that the RU corresponding to the 20MHz is a 484-tone RU. The 484-tone RU is merged with the 242-tone RUs that are consecutive within the 80MHz (that is, the 242-tone RU corresponding to the second 20MHz in the second 80MHz) into a multi-RU, and the number of user fields corresponding to the multi-RU is 0.

[0295] The above Figure 7A The resource unit allocation subfield in the corresponding embodiments is not limited to being indicated only by the examples in Table 2. In other embodiments, other entries in Table 2 may be used for indication based on the actual RU allocation situation. This application does not limit which specific entry is used for the resource unit allocation subfield.

[0296] In addition, the above Figure 7A The resource unit allocation subfield in the corresponding embodiments is not limited to the multi-RU indication method shown in Table 2. There can be other implementations of the multi-RU indication method.

[0297] For example, in another possible implementation, entries 192-225 of the resource element indication in Table 2 can also be replaced with entries 192-225 of the resource element indication in Table 3. Table 3 includes entries indicating that RUs with 106 or more subcarriers will be allocated to 0-16 STAs.

[0298] Table 3

[0299]

[0300]

[0301]

[0302] In Table 3, entries 192-199 of the resource unit indication indicate 242-tone RUs, and each entry indicates that the 242-tone RU is assigned to 1-8 STAs respectively. The merge indication 00 corresponding to any entry in the resource unit indication 192-199 indicates that the 242-tone RU has not been merged into a multi-RU with other RUs. The merge indication 01 corresponding to any entry in the resource unit indication 192-199 indicates that the 242-tone RU has been merged into a multi-RU with a 484-tone RU and is contiguous within 80MHz.

[0303] In Table 3, entries 200-207 of the resource unit indication indicate 484-tone RUs, and each entry indicates that the 484-tone RU is assigned to 1-8 STAs respectively. The merge indication 00 corresponding to any entry in the resource unit indication 200-207 indicates that the 484-tone RU is not merged with other RUs into a multi-RU. The merge indication 01 corresponding to any entry in the resource unit indication 200-207 indicates that the 484-tone RU is merged with a 242-tone RU into a multi-RU and is contiguous within 80MHz. The merge indication 10 corresponding to any entry in the resource unit indication 200-207 indicates that the 484-tone RU is merged with a 242-tone RU into a multi-RU and is not contiguous within 80MHz. Merge instruction 11 corresponding to any one of the entries 200-207 indicated by the resource unit indicates that the 484-tone RU and the 996-tone RU are merged into a multi-RU and are continuous within 160MHz.

[0304] In Table 3, entries 208-215 of the resource unit indication indicate a 996-tone RU, and each entry indicates that the 996-tone RU is assigned to 1-8 STAs respectively. The merge indication 00 corresponding to any entry in resource unit indication 208-215 indicates that the 996-tone RU is not merged into a multi-RU with other RUs. The merge indication 01 corresponding to any entry in resource unit indication 208-215 indicates that the 996-tone RU is merged into a multi-RU with a 484-tone RU and is contiguous within 160MHz. The merge indication 10 corresponding to any entry in resource unit indication 208-215 indicates that the 996-tone RU is merged into a multi-RU with a 484-tone RU and is not contiguous within 160MHz. Merging instruction 11 corresponding to any one of the entries 208-215 indicated by the resource unit indicates that the 996-tone RU and 2*996-tone RUs are merged into a multi-RU and are continuous within 320MHz.

[0305] In Table 3, entries 216-223 of the resource unit indication indicate 2*996-tone RUs, and entries 216-223 respectively indicate that the 2*996-tone RUs are allocated to 1-8 STAs. The merge indication 00 corresponding to any entry in resource unit indication 216-223 indicates that the 2*996-tone RUs are not merged into a multi-RU with other RUs. The merge indication 01 corresponding to any entry in resource unit indication 216-223 indicates that the 2*996-tone RUs are merged into a multi-RU with 996-tone RUs and are contiguous within 160MHz. The merge indication 10 corresponding to any entry in resource unit indication 216-223 indicates that the 2*996-tone RUs are merged into a multi-RU with 996-tone RUs and are not contiguous within 160MHz. The merge instruction 11 corresponding to any one of the entries 216-223 indicated by the resource unit indicates that the 996-tone RU and 2*996-tone RU are merged into a multi-RU and are continuous within 320MHz.

[0306] In Table 3, resource unit indicators 224-231 indicate 242-tone RUs, and each of these indicators specifies that the 242-tone RU is allocated to 9-16 STAs. A merge indicator 00 corresponding to any of the entries in resource unit indicators 224-231 indicates that the 242-tone RU has not been merged into a multi-RU with other RUs. A merge indicator 01 corresponding to any of the entries in resource unit indicators 224-231 indicates that the 242-tone RU has been merged into a multi-RU with a 484-tone RU and is contiguous within an 80MHz band.

[0307] In Table 3, entries 232-239 of the resource unit indication indicate a 484-tone RU, and each entry indicates that the 484-tone RU is allocated to 9-16 STAs. The merge indication 00 corresponding to any entry in the resource unit indication 232-239 indicates that the 484-tone RU is not merged with other RUs into a multi-RU. The merge indication 01 corresponding to any entry in the resource unit indication 232-239 indicates that the 484-tone RU and the 242-tone RU are merged into a multi-RU and are contiguous within 80MHz. The merge indication 10 corresponding to any entry in the resource unit indication 232-239 indicates that the 484-tone RU and the 242-tone RU are merged into a multi-RU and are not contiguous within 80MHz. Merge instruction 11 corresponding to any of the entries 232-239 indicated by the resource unit indicates that the 484-tone RU and the 996-tone RU are merged into a multi-RU and are continuous within 160MHz.

[0308] In Table 3, entries 240-237 of the resource unit indication indicate a 996-tone RU, and each entry indicates that the 996-tone RU is allocated to 9-16 STAs. The merge indication 00 corresponding to any entry in these resource unit indications indicates that the 996-tone RU is not merged into a multi-RU with other RUs. The merge indication 01 corresponding to any entry in these resource unit indications indicates that the 996-tone RU is merged into a multi-RU with a 484-tone RU and is contiguous within 160MHz. The merge indication 10 corresponding to any entry in these resource unit indications indicates that the 996-tone RU is merged into a multi-RU with a 484-tone RU and is not contiguous within 160MHz. The merge instruction 11 corresponding to any of the entries 240-237 indicated by the resource unit indicates that the 996-tone RU and 2*996-tone RU are merged into a multi-RU and are continuous within 320MHz.

[0309] In Table 3, entries 248-255 of the resource unit indication indicate 2*996-tone RUs, and entries 248-255 respectively indicate that the 2*996-tone RUs are allocated to 9-16 STAs. The merge indication 00 corresponding to any entry in resource unit indication 248-255 indicates that the 2*996-tone RUs are not merged into a multi-RU with other RUs. The merge indication 01 corresponding to any entry in resource unit indication 248-255 indicates that the 2*996-tone RUs are merged into a multi-RU with 996-tone RUs and are contiguous within 320MHz. The merge indication 10 corresponding to any entry in resource unit indication 248-255 indicates that the 2*996-tone RUs are merged into a multi-RU with 996-tone RUs and are not contiguous within 320MHz. The merge instruction 11 corresponding to any one of the entries 248-255 indicated by the resource unit indicates that the 996-tone RU and 2*996-tone RU are merged into a multi-RU and are continuous within 320MHz.

[0310] The above Figure 5 or Figure 7A The resource unit allocation subfield in the corresponding embodiment can also be indicated using the entries in Table 3. The specific entry selected can be determined based on the RU allocation situation.

[0311] This application also provides a scheme for RU merging indication. The resource unit allocation subfield includes a resource unit indication and a 2-bit merging indication part. The merging indications in all resource unit allocation subfields corresponding to a large RU indicate the merging status of that large RU. The STA determines the merging status of the large RU based on the merging indications in all resource unit allocation subfields corresponding to a large RU, and thus knows the specific location of the multi-RU merging. The resource unit indication part can use entries from the resource unit indication part of any one of Tables 1, 2, or 3 above.

[0312] The scheme for merging the RU can be used in a data transmission method according to an embodiment of this application. The data transmission method includes:

[0313] The signaling field of the AP generates the PPDU, the signaling field includes at least two resource unit allocation subfields corresponding to a multi-RU, the multi-RU is the merging of at least two RUs included in the channel bandwidth for transmitting the PPDU, each resource unit allocation subfield in the at least two resource unit allocation subfields includes an indication part and a merging indication part, the merging indication part in the at least two resource unit allocation subfields indicates that the at least two RUs are merged into the multi-RU;

[0314] The AP sends the signaling field;

[0315] The corresponding STA receives the signaling field and obtains the at least two resource unit allocation subfields in the signaling field.

[0316] The following section, in conjunction with Table 4, elaborates on the scheme for the aforementioned merger instructions.

[0317] Please refer to Table 4. A 242-tone RU corresponds to one resource unit allocation subfield, meaning a 2-bit merge indication corresponds to one 2-bit merge indication. As shown in Table 4, a merge indication of 00 indicates no merge. A merge indication of 01 indicates that the 242-tone RU and the 484-tone RU are merged into a single multi-RU within 80MHz. The remaining merge indications (e.g., 11) can be reserved entries to indicate other RU merge situations or other information.

[0318] The 484-tone RU corresponds to two resource unit allocation subfields, meaning it corresponds to two 2-bit merging indicators. As shown in Table 4, two merging indicators of 00 and 00 indicate no merging. Two merging indicators of 00 and 01 indicate that the 484-tone RU and 242-tone RU are merged into a single multi-RU within 80MHz and are contiguous within that 80MHz. Two merging indicators of 00 and 10 indicate that the 484-tone RU and 242-tone RU are merged into a single multi-RU within 80MHz and are not contiguous within that 80MHz. Other merging indicator combinations (e.g., 10 and 10, 10 and 11, etc.) can be reserved entries to indicate other RU merging situations or other information.

[0319] The 996-tone RU corresponds to four resource unit allocation subfields, meaning it corresponds to four 2-bit merging indicators. As shown in Table 4, the four merging indicators are 00, 00, 00, and 00, indicating no merging. The four merging indicators are 00, 00, 00, and 01, indicating that the 996-tone RU and 484-tone RU are merged into a multi-RU within 160MHz and are contiguous within 80MHz. The four merging indicators are 00, 00, 00, and 10, indicating that the 996-tone RU and 484-tone RU are merged into a multi-RU within 160MHz and are not contiguous within 80MHz. Other merging indicator combinations (e.g., four 10s, four 11s, etc.) can be reserved entries to indicate other RU merging situations or other information.

[0320] Table 4

[0321]

[0322] The above Figure 7A The resource unit allocation subfield in the corresponding embodiment can be indicated using the entries in Table 4. For example, based on Figure 12For example, the actual allocation of resource units in the 320MHz range is as follows: In ascending order of frequency, the first 80MHz corresponds to one 484+242 multi-RU and one 242-tone RU. The 484+242 multi-RU is allocated to the three STAs docked in the first frequency segment, and the 242-tone RU is allocated to one STA docked in the first frequency segment. In the second 80MHz range, the lowest frequency 20MHz corresponds to one 242-tone RU, allocated to one STA docked in the first frequency segment. The second lowest frequency 20MHz of the second 80MHz range corresponds to nine 26-tone RUs, allocated to nine STAs docked in the second frequency segment. The highest frequency 40MHz of the second 80MHz range corresponds to a 484-tone RU, allocated to one STA docked in the second frequency segment.

[0323] Therefore, in the resource unit allocation indication subfield of the first and second 20MHz segments within the first 80MHz band, the resource unit indications both indicate 484-tone RUs. The merging indications in the first and second 20MHz resource unit allocation indication subfields can be 00 and 01 respectively, thus the two merging indications together indicate 484+242 multi-RUs. In the resource unit allocation indication subfield of the third 20MHz segment within the first 80MHz band, the resource unit indication is 242-tone RUs, and the merging indication is 01. This resource unit allocation indication subfield indicates that the three 20MHz bands correspond to 242+484 multi-RUs.

[0324] This application also provides a scheme for merging instructions of RUs.

[0325] This application provides a method and communication apparatus for resource unit merging indication. The method includes: determining a Physical Layer Protocol Data Unit (PPDU), the PPDU including a signaling field, the signaling field including a resource unit allocation subfield and a merging indication corresponding to the resource unit allocation subfield, the resource unit allocation subfield indicating multiple resource units, and the merging indication used to indicate merging information of the multiple resource units; and transmitting the PPDU. The method provided by this application can support one or more users to use multiple consecutive or discontinuous RUs for data transmission, and indicate the merging status of multiple RUs to the user, improving the flexibility of RU allocation in the system and improving the system spectrum utilization.

[0326] The resource unit allocation subfield includes a resource unit indicator and a 2-bit merging indicator. The merging indicators in all resource unit allocation subfields corresponding to a large RU transmitted on a content channel indicate the merging status of that large RU. The merging indicators in multiple resource unit allocation subfields used to indicate a large RU transmitted on two channels are identical. Thus, the STA can determine the merging status of a large RU based on the merging indicators in all resource unit allocation subfields corresponding to that large RU transmitted on a content channel.

[0327] For example, a 996-tone RU corresponds to four resource unit allocation subfields, namely resource unit allocation subfield 1 through resource unit allocation subfield 4. The merging indication of resource unit allocation subfield 1 transmitted by CC1 is the same as the merging indication of the first unit allocation subfield 2 transmitted by CC2. The merging indication of resource unit allocation subfield 3 transmitted by CC1 is the same as the merging indication of the first unit allocation subfield 4 transmitted by CC2.

[0328] Specifically, please refer to Table 5. A 242-tone RU corresponds to one resource unit allocation subfield, meaning a 2-bit merge indication corresponds to one 2-bit merge indication. As shown in Table 4, a merge indication of 00 indicates no merge. A merge indication of 01 indicates that the 242-tone RU and the 484-tone RU are merged into a single multi-RU within 80MHz. The remaining merge indications (e.g., 11) can be reserved as entries to indicate other RU merge situations or to indicate other information.

[0329] The 484-tone RU corresponds to two resource unit allocation subfields, that is, the 484-tone RU corresponds to two 2-bit merge indications. These two merge indications are transmitted in CC1 and CC2 respectively. These two merge indications are identical. As shown in Table 4, when both resource unit indicators in the two resource unit allocation subfields corresponding to the RU indicate a 484-tone RU, the two merge indicators in the two resource unit allocation subfields are 00 and 00, respectively transmitted on CC1 and CC2. A merge indicator of 00 on either CC indicates no merge. When the two merge indicators in the two resource unit allocation subfields are 01 and 01, respectively transmitted on CC1 and CC2, a merge indicator of 01 on either CC indicates that the 484-tone RU and 242-tone RU are merged into a multi-RU within 80MHz and are continuous within 80MHz. Similarly, when the two merge indicators in the two resource unit allocation subfields are 10 and 10, respectively transmitted on CC1 and CC2, a merge indicator of 10 on either CC indicates that the 484-tone RU and 242-tone RU are merged into a multi-RU within 80MHz and are not continuous within 80MHz. The two merge instructions are 11 and 11 indicates that the 484-tone RU and the 996-tone RU are merged into a multi-RU.

[0330] The 996-tone RU corresponds to four resource unit allocation subfields, which are four 2-bit merging instructions. These four merging instructions are transmitted in CC1 and CC2 respectively. Specifically, the first merging instruction is transmitted in CC1, the second in CC2, the third in CC1, and the fourth in CC2. The first and second merging instructions are identical. The third and fourth merging instructions are identical.

[0331] When the RU indicated by the resource unit indicator in the four resource unit indicator subfields corresponding to a RU is a 996-tone RU, the merge indicator can be, but is not limited to, the following cases.

[0332] The four merge indications in the four resource unit allocation subfields are 00, 00, 00, and 00. Specifically, the first and third 00s transmitted on CC1 indicate no merge, and the second and fourth 00s transmitted on CC2 also indicate no merge. Therefore, if the STA receives two merge indications of 00 and 00 on a single CC, it can determine that no merge is needed.

[0333] The four merge indications in the four resource unit allocation subfields are 00, 00, 01, and 01. The first 00 and the first 01 are transmitted on CC1, indicating that the 996-tone RU and 484-tone RU are merged into a multi-RU within 160MHz and are contiguous within 80MHz. The second 00 and the second 01 are transmitted on CC2, also indicating that the 996-tone RU and 484-tone RU are merged into a multi-RU within 160MHz and are contiguous within 80MHz. Thus, the STA can determine that the 996-tone RU and 484-tone RU are merged into a multi-RU within 160MHz and are contiguous within 80MHz based on the merge indications 00 and 01 on one of the CCs.

[0334] The four merge indications in the four resource unit allocation subfields are 00, 00, 10, and 10. The first 00 and the first 10 are transmitted on CC1, indicating that the 996-tone RU and the 484-tone RU are merged into a multi-RU within 160MHz and are not contiguous within 80MHz. The second 00 and the second 10 are transmitted on CC2, indicating that the 996-tone RU and the 484-tone RU are merged into a multi-RU within 160MHz and are not contiguous within 80MHz.

[0335] The remaining merge indication combinations (e.g., four 10s, four 11s, etc.) can be reserved as entries to indicate other RU merge situations or to indicate other information.

[0336] Table 5

[0337]

[0338] The above Figure 7A The resource unit allocation subfield in the corresponding embodiment can be indicated using the entries in Table 5. For example, based on Figure 12For example, following the order of frequency from lowest to highest, the actual allocation of resource units in the 320MHz range is as follows: The first 80MHz range corresponds to one 484+242 multi-RU and one 242-tone RU. The 484+242 multi-RU is allocated to the three STAs docked in the first frequency domain segment, and the 242-tone RU is allocated to one STA docked in the first frequency domain segment. The lowest 20MHz frequency in the second 80MHz range corresponds to one 242-tone RU, allocated to one STA docked in the first frequency domain segment. The next lowest 20MHz frequency in the second 80MHz range corresponds to nine 26-tone RUs, allocated to nine STAs docked in the second frequency domain segment. The highest 40MHz frequency in the second 80MHz range corresponds to a 484-tone RU, allocated to one STA docked in the second frequency domain segment.

[0339] Therefore, in the resource unit allocation indication subfields of the first and second 20MHz segments within the first 80MHz band, the resource unit indications both indicate 484-tone RUs. The merging indications in both the first and second 20MHz resource unit allocation indication subfields are 01. Either of these two merging indications (01) can independently indicate a 242+484 multi-RU, which is continuous within the 80MHz band. Thus, since the merging indications are identical in both the first and second 20MHz resource unit allocation indication subfields during transmission at the two CCs, the STA only needs to read the resource unit indication indicating a 484-tone RU and the merging indication (01) from the resource unit allocation indication subfield on one of the CCs to determine that the RU indicated by the resource unit allocation subfield is a 242+484 multi-RU, which is continuous within the 80MHz band.

[0340] In the embodiments provided above, the methods provided by the embodiments of this application have been described from the perspectives of access points and sites. To implement the functions of the methods provided in the embodiments of this application, access points and sites may include hardware structures and software modules, and may implement the above functions in the form of hardware structures, software modules, or a combination of hardware structures and software modules. One of the above functions may be executed in the form of hardware structures, software modules, or a combination of hardware structures and software modules.

[0341] Please see Figure 13 , Figure 13 This is a schematic diagram of a data transmission device provided in an embodiment of this application. The data transmission device 13 includes a processing unit 1301 and a transceiver unit 1302;

[0342] Processing unit 1301 is used to generate signaling fields for Physical Layer Protocol Data Units (PPDUs); wherein the channel bandwidth for transmitting the PPDU includes at least two frequency domain segments; the at least two frequency domain segments include a first frequency domain segment; the signaling fields are transmitted in the first frequency domain segment and include common fields and user-specific fields; the common fields include resource unit allocation subfields, and the user-specific fields include user fields; the resource unit allocation subfields indicate the resource units (RUs) included in the channel bandwidth for transmitting the PPDU, and the number of user fields corresponding to the RUs allocated to the stations docked in the first frequency domain segment; wherein the number of user fields corresponding to the RUs allocated to the stations docked in the first frequency domain segment represents the number of user fields contributed by the RU to a content channel in the user-specific fields, and the user fields are the user fields corresponding to the stations docked in the first frequency domain segment;

[0343] The transceiver unit 1302 is used to transmit the signaling field in the first frequency domain segment.

[0344] Thus, in the signaling field of the first frequency domain segment transmission, the resource unit allocation subfield indicates the resource units (RUs) included in the channel bandwidth for transmitting the PPDU, and the number of user fields corresponding to the RUs allocated to the stations docked on the first frequency domain segment. It does not indicate the number of users not allocated to the stations docked on the first frequency domain segment according to the actual resource unit allocation, thereby simplifying the user fields. In the user-specific field section, the user fields of RUs not docked on the first frequency domain segment can be omitted or simplified, thereby reducing the overhead of the signaling fields in the PPDU by reducing the number of user fields.

[0345] The data transmission device 1300 can be a communication device or an access point, or it can be deployed on a communication device or an access point. The processing unit 1301 of the data transmission device 1300 can be a processor, and the transceiver unit 1302 of the data transmission device 1300 can be a transceiver.

[0346] The functional implementation details and technical effects of each functional unit of the data transmission device 1300 provided in this embodiment can be found in the relevant detailed description of the method provided in the above method embodiment, and will not be repeated here.

[0347] In some embodiments, the resource unit allocation subfield indicates that the number of user fields corresponding to RUs not allocated to stations docked in the first frequency domain segment among the resource units RUs included in the channel bandwidth for transmitting the PPDU is 0, and the RUs not allocated to stations docked in the first frequency domain segment are RUs with 242 or more subcarriers. This eliminates the need for user fields for RUs with 242 or more subcarriers, thereby effectively reducing signaling field overhead.

[0348] In some embodiments, the number of user fields corresponding to the RUs not assigned to stations docked in the first frequency domain segment, as indicated by the resource unit allocation subfield, is less than the actual number of user fields corresponding to the RUs not assigned to stations docked in the first frequency domain segment. This reduces the number of user fields in the signaling fields transmitted in the first frequency domain segment, thereby reducing signaling field overhead.

[0349] In some embodiments, the RUs not assigned to stations docked in the first frequency domain segment indicated by the resource unit allocation subfield are actually at least two RUs not assigned to stations docked in the first frequency domain segment. This simplifies the indication method of the resource unit allocation subfield by indicating at least two RUs as a single RU, resulting in fewer user fields corresponding to these at least two RUs and thus reducing signaling field overhead.

[0350] In some embodiments, the at least two RUs are both RUs with fewer than 242 subcarriers. Thus, compared to the prior art where the resource unit allocator indicates the allocation according to the actual resource unit allocation, requiring each small RU to correspond to a separate user field, the scheme of this application indicates at least two small RUs allocated to stations docked in the first frequency domain segment as a single RU. This way, each RU only needs to correspond to one user field, thereby eliminating the need to indicate a user field and reducing signaling field overhead.

[0351] Please see Figure 14 , Figure 14 This is a schematic diagram of a data transmission device provided in an embodiment of this application. This application also provides a data transmission device 1400, including a processing unit 1401 and a transceiver unit 1402.

[0352] The transceiver unit 1402 is used to receive signaling fields of Physical Layer Protocol Data Units (PPDUs) docked in the first frequency domain segment, wherein the channel bandwidth for transmitting the PPDU includes at least two frequency domain segments; the at least two frequency domain segments include the first frequency domain segment; the signaling fields include common fields and user-specific fields; the common fields include resource unit allocation subfields, and the user-specific fields include user fields; the resource unit allocation subfield indicates the resource unit (RU) in the channel bandwidth for transmitting the PPDU, and the number of user fields corresponding to the RUs allocated to the stations docked in the first frequency domain segment; wherein the number of user fields corresponding to the RUs allocated to the stations docked in the first frequency domain segment represents the number of user fields contributed by the RU to a content channel in the user-specific fields, and the user fields are the user fields corresponding to the stations docked in the first frequency domain segment;

[0353] The processing unit 1401 is used to receive the user fields included in the user-specific fields of the signaling field, obtain the user field carrying the identifier of the local station, and obtain the data transmitted on the RU corresponding to the user field.

[0354] The data transmission device can be a communication device or a station, or it can be deployed on a communication device or a station. The processing unit 1401 of the data transmission device 1400 can be a processor, and the transceiver unit 1402 of the data transmission device 1400 can be a transceiver.

[0355] In this way, the resource element allocation subfield in the signaling field received by the station from the first frequency domain segment indicates the resource elements (RUs) included in the channel bandwidth for transmitting the PPDU, and the number of user fields corresponding to the RUs allocated to the station docked on the first frequency domain segment. It does not indicate the number of users not allocated to the station docked on the first frequency domain segment according to the actual resource element allocation, thus simplifying the user fields. In the user-specific field section, the user fields of RUs not docked on the first frequency domain segment can be omitted or simplified, thereby reducing the overhead of the signaling fields in the PPDU by reducing the number of user fields.

[0356] The functional implementation details and technical effects of each functional unit of the data transmission device 1400 provided in this embodiment can be found in the relevant detailed description of the method provided in the above method embodiment, and will not be repeated here.

[0357] In some embodiments, the resource unit allocation subfield indicates that the number of user fields corresponding to RUs not allocated to stations docked in the first frequency domain segment among the resource units RUs included in the channel bandwidth for transmitting the PPDU is 0, and the RUs not allocated to stations docked in the first frequency domain segment are RUs with 242 or more subcarriers. This eliminates the need for user fields for RUs with 242 or more subcarriers, thereby effectively reducing signaling field overhead.

[0358] In some embodiments, the number of user fields corresponding to the RUs not assigned to stations docked in the first frequency domain segment, as indicated by the resource unit allocation subfield, is less than the actual number of user fields corresponding to the RUs not assigned to stations docked in the first frequency domain segment. This reduces the number of user fields in the signaling fields transmitted in the first frequency domain segment, thereby reducing signaling field overhead.

[0359] In some embodiments, the RUs not assigned to stations docked in the first frequency domain segment indicated by the resource unit allocation subfield are actually at least two RUs not assigned to stations docked in the first frequency domain segment. This simplifies the indication method of the resource unit allocation subfield by indicating at least two RUs as a single RU, resulting in fewer user fields corresponding to these at least two RUs and thus reducing signaling field overhead.

[0360] In some embodiments, the at least two RUs are both RUs with fewer than 242 subcarriers. Thus, compared to the prior art where the resource unit allocator indicates the allocation according to the actual resource unit allocation, requiring each small RU to correspond to a separate user field, the scheme of this application indicates at least two small RUs allocated to stations docked in the first frequency domain segment as a single RU. This way, each RU only needs to correspond to one user field, thereby eliminating the need to indicate a user field and reducing signaling field overhead.

[0361] Please see Figure 15 , Figure 15 This is a schematic diagram of a data transmission device provided in an embodiment of this application. An embodiment of this application also provides a data transmission device 1500, including a processing unit 1501 and a transceiver unit 1502;

[0362] Processing unit 1501 is used to generate the signaling field of Physical Layer Protocol Data Unit (PPDU); wherein the channel bandwidth for transmitting the PPDU includes at least two frequency domain segments; the at least two frequency domain segments include a first frequency domain segment;

[0363] The transceiver unit 1502 is used to transmit the signaling field in the first frequency domain segment.

[0364] The signaling fields include common fields and user-specific fields. The common fields include a resource element allocation subfield. The user-specific fields include user fields. The resource element allocation subfield indicates a resource element (RU) in the channel bandwidth through which the PPDU is transmitted. The common fields include at least one RU indicated by the resource element allocation subfield as a plurality of RUs with fewer than 242 subcarriers. Each of the plurality of RUs with fewer than 242 subcarriers corresponds to at least one user field. Wherein, the user field corresponding to at least one first RU carries an identifier of a station docked in the first frequency domain segment, and the user field corresponding to at least one second RU does not carry an identifier of a station docked in the first frequency domain segment. At least a portion of the subcarriers corresponding to the second RU indicated by the resource element allocation subfield belongs to at least two RUs.

[0365] The data transmission device can be a communication device or a station, or it can be deployed on a communication device or a station. The processing unit 1501 of the data transmission device 1500 can be a processor, and the transceiver unit 1502 of the data transmission device 1500 can be a transceiver.

[0366] In this way, compared to indicating the two RUs according to the actual situation and indicating that each of the two RUs corresponds to at least one user field, the scheme of this application, in the first signaling field of the first frequency domain segmented transmission, the resource unit allocation subfield indicates one RU that is combined with the at least two RUs, and this one RU corresponds to only one user field. This can effectively reduce the number of user fields corresponding to multiple consecutive small RUs that are not allocated to STAs that remain in the frequency domain, thereby saving the overhead of signaling fields.

[0367] In some embodiments, the resource unit allocation subfield indicates that the number of user fields corresponding to RUs not allocated to stations docked in the first frequency domain segment among the resource units RUs included in the channel bandwidth for transmitting the PPDU is 0, and the RUs not allocated to stations docked in the first frequency domain segment are RUs with 242 or more subcarriers. This eliminates the need for user fields for RUs with 242 or more subcarriers, thereby effectively reducing signaling field overhead.

[0368] In some embodiments, the number of user fields corresponding to the RUs not assigned to stations docked in the first frequency domain segment, as indicated by the resource unit allocation subfield, is less than the actual number of user fields corresponding to the RUs not assigned to stations docked in the first frequency domain segment. This reduces the number of user fields in the signaling fields transmitted in the first frequency domain segment, thereby reducing signaling field overhead.

[0369] In some embodiments, the RUs not assigned to stations docked in the first frequency domain segment indicated by the resource unit allocation subfield are actually at least two RUs not assigned to stations docked in the first frequency domain segment. This simplifies the indication method of the resource unit allocation subfield by indicating at least two RUs as a single RU, resulting in fewer user fields corresponding to these at least two RUs and thus reducing signaling field overhead.

[0370] In some embodiments, the at least two RUs are both RUs with fewer than 242 subcarriers. Thus, compared to the prior art where the resource unit allocator indicates the allocation according to the actual resource unit allocation, requiring each small RU to correspond to a separate user field, the scheme of this application indicates at least two small RUs allocated to stations docked in the first frequency domain segment as a single RU. This way, each RU only needs to correspond to one user field, thereby eliminating the need to indicate a user field and reducing signaling field overhead.

[0371] The functional implementation details and technical effects of each functional unit of the data transmission device 1500 provided in this embodiment can be found in the relevant detailed description of the method provided in the above method embodiment, and will not be repeated here.

[0372] Please see Figure 16 , Figure 16 This is a schematic diagram of a data transmission device provided in an embodiment of this application. An embodiment of this application also provides a data transmission device 1600, including a processing unit 1601 and a transceiver unit 1602.

[0373] Processing unit 1601 is configured to receive signaling fields of Physical Layer Protocol Data Units (PPDUs) in the first frequency domain segment; wherein the channel bandwidth for transmitting the PPDU includes at least two frequency domain segments; the at least two frequency domain segments include a first frequency domain segment; the signaling fields include a common field and a user-specific field, the common field includes a resource element allocation subfield; the user-specific field includes a user field; the resource element allocation subfield indicates a resource element (RU) in the channel bandwidth for transmitting the PPDU; the common field includes at least one RU indicated by the resource element allocation subfield being an RU of multiple subcarriers less than 242; each of the multiple RUs of less than 242 subcarriers corresponds to at least one user field; wherein the user field corresponding to at least one first RU carries an identifier of a station docked in the first frequency domain segment, the user field corresponding to at least one second RU does not carry an identifier of a station docked in the first frequency domain segment, and at least a portion of the subcarriers corresponding to the second RU indicated by the resource element allocation subfield belongs to at least two RUs;

[0374] The transceiver unit 1602 is used to obtain a user field carrying the identifier of the site from the user fields included in the user-specific field, and to obtain the data transmitted on the RU corresponding to the user field. This data transmission device can be a communication device or a site, or the data transmission device can be deployed on a communication device or a site.

[0375] The data transmission device can be a communication device or a station, or it can be deployed on a communication device or a station. The processing unit 1601 of the data transmission device 1600 can be a processor, and the transceiver unit 1602 of the data transmission device 1600 can be a transceiver.

[0376] In this way, the resource element allocation subfield in the signaling field received by the station from the first frequency domain segment indicates the resource elements (RUs) included in the channel bandwidth for transmitting the PPDU, and the number of user fields corresponding to the RUs allocated to the station docked on the first frequency domain segment. It does not indicate the number of users not allocated to the station docked on the first frequency domain segment according to the actual resource element allocation, thus simplifying the user fields. In the user-specific field section, the user fields of RUs not docked on the first frequency domain segment can be omitted or simplified, thereby reducing the overhead of the signaling fields in the PPDU by reducing the number of user fields.

[0377] In some embodiments, the resource unit allocation subfield indicates that the number of user fields corresponding to RUs not allocated to stations docked in the first frequency domain segment among the resource units RUs included in the channel bandwidth for transmitting the PPDU is 0, and the RUs not allocated to stations docked in the first frequency domain segment are RUs with 242 or more subcarriers. This eliminates the need for user fields for RUs with 242 or more subcarriers, thereby effectively reducing signaling field overhead.

[0378] In some embodiments, the number of user fields corresponding to the RUs not assigned to stations docked in the first frequency domain segment, as indicated by the resource unit allocation subfield, is less than the actual number of user fields corresponding to the RUs not assigned to stations docked in the first frequency domain segment. This reduces the number of user fields in the signaling fields transmitted in the first frequency domain segment, thereby reducing signaling field overhead.

[0379] In some embodiments, the RUs not assigned to stations docked in the first frequency domain segment indicated by the resource unit allocation subfield are actually at least two RUs not assigned to stations docked in the first frequency domain segment. This simplifies the indication method of the resource unit allocation subfield by indicating at least two RUs as a single RU, resulting in fewer user fields corresponding to these at least two RUs and thus reducing signaling field overhead.

[0380] In some embodiments, the at least two RUs are both RUs with fewer than 242 subcarriers. Thus, compared to the prior art where the resource unit allocator indicates the allocation according to the actual resource unit allocation, requiring each small RU to correspond to a separate user field, the scheme of this application indicates at least two small RUs allocated to stations docked in the first frequency domain segment as a single RU. This way, each RU only needs to correspond to one user field, thereby eliminating the need to indicate a user field and reducing signaling field overhead.

[0381] The functional implementation details and technical effects of each functional unit of the data transmission device 1600 provided in this embodiment can be found in the relevant detailed description of the method provided in the above method embodiment, and will not be repeated here.

[0382] Those skilled in the art will also understand that the various illustrative logical blocks and steps listed in the embodiments of this application can be implemented by electronic hardware, computer software, or a combination of both. Whether such functionality is implemented through hardware or software depends on the specific application and the overall system design requirements. Those skilled in the art can implement the described functionality using various methods for each specific application, but such implementation should not be construed as exceeding the scope of protection of the embodiments of this application.

[0383] This application also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a computer, implements the functions of any of the above method embodiments.

[0384] This application also provides a computer program product that, when executed by a computer, implements the functions of any of the above method embodiments.

[0385] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product. The computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device such as a server or data center that integrates one or more available media. The available media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., high-density digital video discs (DVDs)), or semiconductor media (e.g., solid-state disks (SSDs)).

[0386] Those skilled in the art will understand that the various numerical designations such as "first," "second," etc., involved in this application are merely for the convenience of description and are not intended to limit the scope of the embodiments of this application, nor do they indicate the order of sequence.

[0387] The correspondences shown in the tables of this application can be configured or predefined. The values ​​of the information in each table are merely examples and can be configured to other values; this application is not limited to these values. When configuring the correspondences between information and parameters, it is not necessarily required to configure all the correspondences shown in each table. For example, the correspondences shown in some rows of the tables in this application may not be configured. Furthermore, appropriate modifications and adjustments can be made based on the above tables, such as splitting, merging, etc. The names of the parameters shown in the headings of the above tables can also use other names that the communication device can understand, and the values ​​or representations of the parameters can also be other values ​​or representations that the communication device can understand. In the implementation of the above tables, other data structures can also be used, such as arrays, queues, containers, stacks, linear lists, pointers, linked lists, trees, graphs, structures, classes, heaps, hash tables, or hash tables, etc.

[0388] The term "predefined" in this application can be understood as definition, pre-defined, stored, pre-stored, pre-negotiated, pre-configured, solidified, or pre-burned.

[0389] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0390] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0391] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A data transmission method, characterized by, Comprising: a station parked at a first frequency domain slice receives a signaling field of a physical layer protocol data unit (PPDU) at the first frequency domain slice, wherein a channel bandwidth in which the PPDU is transmitted comprises at least two frequency domain slices; the at least two frequency domain slices comprise the first frequency domain slice; the signaling field comprises a common field and a user-specific field; the common field comprises a resource unit allocation subfield, and the user-specific field comprises user fields; the resource unit allocation subfield indicates resource units (RUs) / multiple RUs (MRUs) in the channel bandwidth in which the PPDU is transmitted, and a number of user fields corresponding to RUs / MRUs allocated to the station parked at the first frequency domain slice and a number of user fields corresponding to RUs not allocated to the station parked at the first frequency domain slice in the RUs / MRUs; for the RUs / MRUs allocated to the station parked at the first frequency domain slice and the corresponding user fields, actual conditions are indicated, and for the RUs / MRUs not allocated to the station parked at the first frequency domain slice and the corresponding user fields, actual conditions are not indicated; wherein the number of user fields corresponding to the RUs / MRUs allocated to the station parked at the first frequency domain slice indicated by one resource unit allocation subfield represents the number of user fields contributing to one content channel in the user-specific field; the station receives user fields included in the user-specific field of the signaling field, obtains a user field carrying an identifier of the station, and obtains data transmitted on corresponding RUs / MRUs according to the user field.

2. The method of claim 1, wherein, The number of user fields corresponding to the RUs / MRUs not allocated to the station parked at the first frequency domain slice indicated by the resource unit allocation subfield is 0, and the RUs / MRUs not allocated to the station parked at the first frequency domain slice are RUs greater than or equal to 242 subcarriers.

3. The method of claim 1, wherein, The number of user fields corresponding to the RUs / MRUs not allocated to the station parked at the first frequency domain slice indicated by the resource unit allocation subfield is less than the number of user fields actually corresponding to the RUs / MRUs not allocated to the station parked at the first frequency domain slice.

4. The method of claim 3, wherein, The RUs / MRUs not allocated to the station parked at the first frequency domain slice indicated by the resource unit allocation subfield are actually at least two RUs / MRUs not allocated to the station parked at the first frequency domain slice.

5. The method of claim 4, wherein, The at least two RUs / MRUs are RUs less than 242 subcarriers.

6. The method of claim 1, wherein, The at least two frequency domain segments include a second frequency domain segment, when the 80MHz corresponding RU of the lowest frequency of the channel bandwidth in which the PPDU is transmitted is actually two 484-tone RUs, and both are RUs not allocated to STAs docking at the second frequency domain segment, a resource unit allocation subfield in a second signaling field transmitted in the second frequency domain segment does not actually indicate the two 484-tone RUs according to actual conditions, nor does it actually indicate the number of user fields corresponding to the two 484-tone RUs in the user field.

7. The method according to claim 1 or 6, characterized in that The at least two frequency domain segments include a second frequency domain segment, when the 80MHz corresponding RU of the lowest frequency of the channel bandwidth in which the PPDU is transmitted is actually two 484-tone RUs, and both are RUs not allocated to STAs docking at the second frequency domain segment, a resource unit allocation subfield in a second signaling field transmitted in the second frequency domain segment indicates that the 80MHz corresponding RU of the lowest frequency of the channel bandwidth in which the PPDU is transmitted is a 996-tone RU, and indicates that the number of user fields corresponding to the 996-tone RU in the user field specific part is 0.

8. The method of claim 1, wherein, The resource unit indication subfield included in the signaling field corresponds to the size of the channel bandwidth in which the PPDU is transmitted, and each of the resource unit indication subfields corresponds to a 20MHz bandwidth.

9. A communications device, characterized by The processor is coupled with a memory, and is configured to read instructions in the memory and implement the method in any one of claims 1-8.

10. A computer-readable storage medium, characterized in that, The computer readable storage medium stores computer instructions, and the computer instructions instruct a communication device to execute the method in any one of claims 1-8.

11. A computer program product, characterised in that, The computer program product includes a computer program, and when the computer program runs on a computer, the computer program causes the computer to execute the method in any one of claims 1-8.

Images