Method and device for indicating multi-resource unit Multi-RU merging

Abstract

The present application relates to the field of wireless communications, and in particular to a method and device for indicating the merging of multiple resource units (Multi‑RU), which can improve the flexibility of RU allocation and improve spectrum utilization. The method includes: a sending device determines a physical layer protocol data unit (PPDU), the PPDU includes a signaling field, and the signaling field includes a merging indication for indicating whether a first RU is merged with an adjacent second RU into a Multi‑RU; the sending device sends the PPDU, and the receiving device determines whether the method is allocated a Multi‑RU according to the signaling field.

Description

Technical Field

[0001] The present application relates to the field of wireless communications, and in particular to a method and apparatus for indicating multi-resource unit (Multi-RU) merging in a wireless communication system. Background Art

[0002] Wireless LAN (WLAN) has gone through many generations, including 802.11a / b / g, 802.11n, 802.11ac, 802.11ax, and the 802.11be that is currently under discussion. Among them, the 802.11n standard is called HT (High Throughput), the 802.11ac standard is called VHT (Very High Throughput), the 802.11ax standard is called HE (High Efficient), and the 802.11be standard is called EHT (Extremely High Throughput).

[0003] 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 can separate the two 80MHz. In 802.11be, configurations such as 320MHz will be supported.

[0004] In 802.11ax, the allocation of user frequency band resources is not based on 20MHz channels, but on RUs (Resource Units). In a 20MHz channel of 802.11ax, multiple RUs can be included, which can be in the form of 26-tone RU, 52-tone RU, 106-tone RU, where tone represents the number of subcarriers. In addition, RU can also be in the form of 242-tone, 484-tone, 996-tone, etc. The specific RU allocation notification method in 11ax will be described in the prior art 1.

[0005] 11ax currently only supports allocating one RU to one or more users, which reduces the allocation flexibility of the system and also makes the spectrum utilization of the system low when there is preamble puncturing. Therefore, how to improve the flexibility of RU allocation and spectrum utilization of the next-generation WLAN system is a crucial issue. Summary of the invention

[0006] In order to solve the above problems, the present application provides a method and device for indicating the merging of multiple resource units (Multi-RU), which are applied to a wireless communication system to improve the flexibility of RU allocation and improve spectrum utilization.

[0007] In a first aspect, a method for indicating a merge of multiple resource units (Multi-RU) is provided, the method comprising: determining a physical layer protocol data unit (PPDU), the PPDU comprising a signaling field, the signaling field comprising a merge indication for indicating whether a first RU is merged with an adjacent second RU into a Multi-RU; and sending the PPDU.

[0008] In a second aspect, a method for indicating a multi-resource unit Multi-RU merge is provided, the method comprising:

[0009] Receive a physical layer protocol data unit PPDU, the PPDU includes a signaling field, the signaling field includes a merge indication, used to indicate whether the first RU is merged with an adjacent second RU into a Multi-RU, and the signaling field does not include a user field corresponding to the second RU; determine whether the method is allocated a Multi-RU based on the signaling field.

[0010] By adopting the method of the first aspect or the second aspect, multiple RUs can be allocated to one or more users for data transmission, thereby improving the flexibility of resource unit allocation and improving spectrum efficiency.

[0011] In a possible example, the signaling field also includes a resource unit allocation subfield, which indicates the size and location of multiple RUs allocated in 20 MHz, and the multiple RUs include the first RU.

[0012] In one possible example, the resource unit allocation subfield indicates that the corresponding 20MHz is divided into any one of the following: [106,-,52,52], [52,52,-,106], [106,-,106], [52,52,-,52,52]; the second RU is the middle 26-tone RU, and the first RU is a 106-tone RU or a 52-tone RU adjacent to the middle 26-tone RU.

[0013] In one possible example, the resource unit allocation subfield indicates that the corresponding 20MHz is divided into any one of the following: [26,26,26,26,-,106], [26,26,52,-,106], [52,26,26,-,106], [106,-,26,26,26,26], [106,-,52,26,26] or [106,-,26,26,52], the second RU is the middle 26-tone RU, and the first RU is a 106-tone RU adjacent to the middle 26-tone RU.

[0014] In a possible example, the signaling field also includes a user field corresponding to the first RU, and the signaling field does not include a user field corresponding to the second RU; at least one user field corresponding to the first RU includes the merge indication; if the merge indication indicates that the first RU and the second RU are merged into a Multi-RU, the Multi-RU is allocated to the user indicated by the user field corresponding to the first RU, and the PPDU also includes a data field, and the data field includes data carried on the Multi-RU.

[0015] In a possible example, the first RU is a 106-tone RU, and the 106-tone RU corresponds to at least two user fields.

[0016] This method uses a resource unit allocation subfield with a special value combined with a merge indication Multi-RU, which is compatible with sites that support 802.11ax. Furthermore, it can simply determine users who use Multi-RU for MU-MIMO with low complexity, and saves signaling overhead based on the combination of the value of the special resource unit subfield and the merge indication.

[0017] In one possible example, the merge indication includes 1 bit, the merge indication takes a first value to indicate that the first RU is not merged with the adjacent second RU; the merge indication takes a second value to indicate that the first RU is merged with the adjacent second RU. In one possible example, the merge indication includes 2 bits, the merge indication takes a first value to indicate that the first RU is not merged with the adjacent second RU; the merge indication takes a second value to indicate that the first RU is merged with the adjacent second RU on the left; the merge indication takes a third value to indicate that the first RU is merged with the adjacent second RU on the right.

[0018] In a third aspect, an embodiment of the present application provides a communication device, which can be an access point or a station, and can implement the method and function of the first aspect, and the function can be implemented by hardware or by software that executes a response in hardware. The hardware or software includes one or more modules corresponding to the above functions.

[0019] In one possible design, the device includes a processing unit and a transceiver unit, and the processor is configured to support the access point or station to perform the corresponding functions in the above method. The transceiver unit is used to support communication between the device and other devices. The device may also include a storage unit, which is used to couple with the processing unit and store program instructions and data necessary for the access point. Optionally, the device may also be a chip, for example, the transceiver unit is an input and output interface, and the processing unit may be a processing circuit in the chip, so that the device installed with the chip can implement the method and function of the first aspect mentioned above.

[0020] In a fourth aspect, an embodiment of the present application provides a communication device, which can be an access point or a station, and can implement the method and function of the second aspect, and the function can be implemented by hardware or by software that executes a response in hardware. The hardware or software includes one or more modules corresponding to the above functions.

[0021] In one possible design, the device includes a processing unit and a transceiver unit, and the processor is configured to support the access point or station to perform the corresponding functions in the above method. The transceiver unit is used to support communication between the device and other devices. The device may also include a storage unit, which is used to couple with the processing unit and store program instructions and data necessary for the access point. Optionally, the device may also be a chip, for example, the transceiver unit is an input and output interface, and the processing unit may be a processing circuit in the chip, so that the device installed with the chip can implement the method and function of the second aspect.

[0022] In a fifth aspect, an embodiment of the present application provides a chip or system system, including a processor, the processor is coupled to a memory, the memory stores instructions, and when the processor executes the instructions, the device is controlled to execute any of the above methods. Optionally, the memory can be located inside the chip or outside the chip, coupled to the chip, and the chip can call the instructions stored in the memory.

[0023] In a sixth aspect, the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores instructions, and the instructions can be executed by one or more processors on a processing circuit. When the instructions are executed on a computer, the computer executes the method described in any one of the above aspects.

[0024] In a seventh aspect, the present application provides a computer program product comprising instructions, which, when executed on a computer, enables the computer to execute the method described in any of the above aspects. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] In order to more clearly illustrate the embodiments of the present invention, the drawings required for use in the embodiments are briefly introduced below.

[0026] Figure 1 A schematic diagram of a possible application scenario of an embodiment of the present application is shown;

[0027] Figure 2 A schematic diagram of the structure of the HE-SIG-B field of 802.11ax is shown;

[0028] Figure 3 A schematic diagram showing a Multi-RU merging method provided in an embodiment of the present application is shown;

[0029] Figure 4 A schematic diagram of a flow chart of a method for indicating Multi-RU provided in an embodiment of the present application is shown;

[0030] Figure 5 An example of the structure of a common domain and a site-by-site domain in a trigger frame provided by an embodiment of the present application is shown;

[0031] Figure 6 A schematic diagram indicating allocation of multiple resource units within 20 MHz provided in an embodiment of the present application is shown;

[0032] Figure 7 A schematic flow chart of another method for indicating Multi-RU provided in an embodiment of the present application is shown;

[0033] Figure 8 A schematic diagram of a flow chart of another method for indicating Multi-RU provided in an embodiment of the present application is shown;

[0034] Fig. 9 A schematic diagram indicating the merging of multiple resource units within 20 MHz provided in an embodiment of the present application is shown;

[0035] Fig.10 A schematic diagram of a flow chart of another method for indicating Multi-RU provided in an embodiment of the present application is shown;

[0036] Fig.11 A schematic diagram showing another method of merging multiple resource units within 20 MHz provided in an embodiment of the present application is shown;

[0037] Fig.12 A schematic diagram of the structure of a device provided in an embodiment of the present application is shown;

[0038] Fig.13 A schematic diagram showing the structure of another device improved by an embodiment of the present application is shown;

[0039] Fig.14 A schematic diagram of the structure of another device improved in an embodiment of the present application is shown. DETAILED DESCRIPTION

[0040] The scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application and do not constitute a limitation on the technical solutions provided in the embodiments of the present application.

[0041] See also Figure 1 , shows a wireless local area network (WLAN) communication system 100. The communication system 100 includes an access point AP 105, and stations (e.g., STA101 to STA105). The access point and the stations can support the 802.11be standard, or the next generation wireless communication standard protocol of 802.11be or the next generation wireless communication standard protocol. Of course, they can also support standards before 802.11be, such as 802.11ax / ac / a / b / g / n, etc.

[0042] An access point (e.g., AP105) is a device with wireless communication capabilities. The access point AP 105 may be an AP that uses the 802.11 protocol for data transmission. In one example, multiple stations STA are connected to the AP via wireless links that follow Wi-Fi to obtain general connectivity to the Internet or other wide area networks. In some implementations, STA may also be used as an AP. It is understood that the number of APs and STAs in the above-mentioned WLAN communication system 100 is only exemplary and does not constitute a limitation on the embodiments of the present application.

[0043] Those skilled in the art can understand that in the above-mentioned WLAN communication system, the above-mentioned site involved in the present application can also be various user terminals, user devices, access devices, subscriber stations, subscriber units, mobile stations, user agents, user equipment or other names with wireless communication functions, wherein the user terminal can include various handheld devices, vehicle-mounted devices, wearable devices, computing devices or other processing devices connected to a wireless modem with wireless communication functions, as well as various forms of user equipment (User Equipment, referred to as UE), mobile stations (Mobile station, referred to as MS), terminals, terminal equipment (Terminal Equipment), portable communication devices, handheld machines, portable computing devices, entertainment devices, game devices or systems, global positioning system devices, IoT nodes in IoT communication systems or any other suitable devices configured to perform network communication via wireless media, etc. Here, for the convenience of description, the above-mentioned devices are collectively referred to as sites or STAs.

[0044] The access point AP involved in this application is a device deployed in a wireless communication network to provide wireless communication functions for a station, which can be used as the hub of a WLAN. The access point AP can also be a base station, a router, a gateway, a repeater, a communication server, a switch or a bridge, etc., wherein the base station can include various forms of macro base stations, micro base stations, relay stations, etc. For the convenience of description, the above-mentioned devices that provide wireless communication function services for the station STA are collectively referred to as access points or APs.

[0045] WLAN has gone through several generations, including 802.11a / b / g, 802.11n, 802.11ac, 802.11ax, and the 802.11be that is currently under discussion. Among them, the 802.11n standard is called HT (High Throughput), the 802.11ac standard is called VHT (Very High Throughput), the 802.11ax standard is called HE (High Efficient), and the 802.11be standard is called EHT (Extremely High Throughput).

[0046] 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 can separate the two 80MHz. In future WiFi protocols, such as 802.11be, configurations such as 320MHz will be supported.

[0047] In 802.11ax, the allocation of user frequency band resources is not based on 20MHz channels, but on RUs (Resource Units). In a 20MHz channel of 802.11ax, multiple RUs can be included, which can be in the form of 26-tone RU, 52-tone RU, 106-tone RU, where tone represents the number of subcarriers. In addition, RUs can also be in the form of 242-tone, 484-tone, 996-tone, etc.

[0048] The notification method for user RU allocation in 802.11ax specifically involves the RU Allocation subfield in the Commonfield of HE-SIG-B in the MU PPDU. For the sake of clarity, the structure of HE-SIG-B is first introduced here, such as Figure 2 As shown:

[0049] HE-SIG-B is divided into two parts, the first part is a common field, which includes 1 to N resource unit allocation subfields (RU Allocation subfield), and the center 26-subcarrier (Center 26-Tone) resource unit indication field when the bandwidth is greater than or equal to 80MHz, followed by a cyclic redundancy code (Cyclic Redundancy Code, CRC) for verification and a tail (Tail) subfield for cyclic decoding; in addition, in the user specific field (User Specific field), there are 1 to M user fields (User Field) in the order of resource unit allocation. The M user fields are usually grouped in two, and every two user fields are followed by a CRC and Tail field, but the last group should be excluded. In the last group, there may be 1 or 2 user fields.

[0050] Before describing the resource unit allocation indication method in detail, here is the description of the subcarrier distribution (Tone Plan) under different data packet bandwidths of 802.11ax: When the bandwidth is 20MHz, the entire bandwidth can be composed of a whole 242-tone RU, or a combination of 26-tone RU, 52-tone RU, and 106-tone RU. In addition to the RU used to transmit data, it also includes some guard subcarriers, empty subcarriers, or direct current (DC) subcarriers.

[0051] When the bandwidth is 40MHz, the entire bandwidth is roughly equivalent to a replication of the 20MHz subcarrier distribution. The entire bandwidth can be composed of a whole 484-tone RU, or various combinations of 26-tone RU, 52-tone RU, 106-tone RU, and 242-toneRU:

[0052] When the bandwidth is 80MHz, the entire bandwidth is composed of four 242-tone RU resource units. In particular, in the middle of the entire bandwidth, there is an intermediate 26-tone RU composed of two 13-tone sub-units. The entire bandwidth can be composed of a whole 996-tone RU, or various combinations of 26-tone RU, 52-tone RU, 106-tone RU, 242-toneRU, and 484-tone RU.

[0053] When the bandwidth is 160MHz or 80+80MHz, the entire bandwidth can be regarded as a replication of two 80Mhz subcarrier distributions. The entire bandwidth can be composed of a whole 2*996-tone RU, or various combinations of 26-tone RU, 52-tone RU, 106-tone RU, 242-tone RU, 484-tone RU, and 996-tone RU.

[0054] The above subcarrier distributions are based on 242-tone RUs. The subcarriers on the left side of the bandwidth can be considered as the lowest frequency, and the subcarriers on the right side of the bandwidth can be considered as the highest frequency. From left to right, the 242-tone RUs can be numbered: 1st, 2nd, ..., 8th. It should be noted that in the data field, the 8 242-tone RUs correspond to the 8 20MHz channels one by one from low to high in frequency, but due to the existence of the 26-tone RU in the middle, the frequencies do not completely overlap.

[0055] The following describes the indication method of 11ax resource unit allocation. 802.11ax introduces the concept of content channel (CC). When the data packet bandwidth is only 20MHz, HE-SIG-B contains only one content channel, which contains one resource unit allocation subfield, which is used to indicate the resource unit allocation indication within the 242-tone (subcarrier) RU of the data part. The resource unit allocation subfield is 8 bits, which indicates all possible resource unit permutations and combinations within the 242-toneRU by index. In addition, for RUs with a size greater than or equal to 106-tone, the number of users performing SU / MU-MIMO transmission in the RU is also indicated by index. The index table of the resource unit allocation subfield is as follows:

[0056] Table 1 Resource unit allocation subfields in 11ax

[0057]

[0058]

[0059] Each row in the table represents an RU configuration, where most of the RU configurations in the table are within the range of 242-tone, and a small number of them indicate that the RU belongs to 242-tone RU, 484-tone RU, and 996-tone RU. Each 8-bit resource unit allocation subfield will inform the RU allocation status within the corresponding 20MHz range, which can be understood as: 20MHz has 1 resource unit allocation subfield, 40MHz has 2 resource unit allocation subfields, 80MHz has 4 resource unit allocation subfields, and 160MHz has 8 resource unit allocation subfields.

[0060] It should be noted that the order in which the user fields appear in the user-specific field is consistent with the order of RUs divided in the corresponding resource unit allocation subfield. The user can identify whether the user field belongs to himself by reading the STA ID in the user field. Combining the position of the user field with the corresponding resource unit allocation subfield, the user can know his RU allocation status.

[0061] 11ax currently only supports allocating one RU to one or more users, which reduces the allocation flexibility of the system and also makes the spectrum utilization of the system low when there is preamble puncturing. In order to solve these problems, the embodiment of the present application proposes to allocate multiple RUs to one or more users, improve the flexibility of RU allocation and improve the spectrum utilization of the system.

[0062] The solution of this embodiment is described below in conjunction with more drawings.

[0063] The embodiment of the present application supports one user to use multiple RUs for data transmission. In the embodiment of the present application, "Multi-RU" is generally a combination of multiple RUs that are continuous or discontinuous in the frequency domain defined in 802.11ax. Optionally, the combination of multiple RUs that are continuous or discontinuous in the frequency domain defined in 802.11ax can also be called Multi-RU, and the "Multi-RU" can be the next generation definition of 802.11ax, for example, the newly defined RU in 802.11be. Of course, "Multi-RU" can also have other names, such as RU combination, etc. The number of RUs combined in Multi-RU is not limited, for example, it can be 2 RUs combined, or 3 RUs combined or more. Multi-RU can be assigned to one or more users for data transmission, and multiple users can perform MU-MIMO transmission in Multi-RU. It should be noted that the "user" mentioned in the embodiment of the present application is a general term for network elements that can use resource units for transmission, which can be sites or access points.

[0064] Optionally, multiple large-size RUs are combined into Multi-RUs, and multiple small-size RUs are combined into Mutil-RUs. In the embodiment of the present application, an RU whose size is less than 242-tone is a small RU, for example, 26-tone RU, 52-tone RU and 106-tone RU are small RUs. An RU whose size is greater than or equal to 242-tone is a large RU, for example, 242-tone RU, 484-tone RU and 996-tone RU are large RUs.

[0065] A combination of multiple small-size RUs can be a combination of 26-tone RU, 52-tone RU and 106-tone RU. For example, at least 2 small RUs are combined into a Multi-RU. Optionally, in an embodiment of the present application, if it is agreed that small RUs of the same size are not combined, that is, it is agreed that small RUs of the same size do not support being combined into a Multi-RU, for example, 26-tone RU is not combined with 26-tone RU, 52-tone RU is not combined with 52-tone RU, and 106-tone RU is not combined with 106-tone RU. Suppose Multi-RU is the combination of two small RUs. The first combination of small RUs includes a 106-tone RU and a 26-tone RU, which can be recorded as (106+26). The second combination of small RUs includes a 52-tone RU and a 26-tone RU, which can be recorded as (52+26). The third combination of small RUs includes a 106-tone RU and a 52-tone RU, which can be recorded as (106+52).

[0066] A combination of large-size RUs can be a combination of 242-tone RU, 484-tone RU and 996-tone RU. For example, at least 2 large RUs are combined into a Multi-RU, any of which can be any of 242-tone RU, 484-tone RU and 996-tone RU. If the Multi-RU includes 2 large RUs, the combination of large RUs can be: (242+242), (242+484), (242+996), or (448+996). For another example, the merging of large RUs can be: 1. (242+484) (contiguous and non-contiguous, within each 80MHz segment); 2. (242+242) (punched case, non-contiguous); 3. (484+996); 4. (242+484+242+484); 5. (242+484+996); 6. (242+242+996), etc.

[0067] It should be noted that, in the embodiment of the present application, the constraints for merging multiple RUs include multiple ones. One constraint includes: 1. Small RUs and large RUs are not merged; 2. A combination of small-sizeRUs shall not cross 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 52-tone RU and a 26-tone RU consecutively within 20MHz, or a 106-tone RU and a 26-tone RU consecutively within 20MHz. Among them, the positions of a 52-tone RU and a 26-tone RU consecutively within 20MHz can be: the 52-tone RU is located on the left side of the 26-tone RU, or the 52-tone RU is located on the right side of the 26-tone RU; the positions of a 106-tone RU and a 26-toneRU consecutively within 20MHz can be: the 106-tone RU is located on the left side of the 26-tone RU, or the 106-tone RU is located on the right side of the 26-tone RU. The RU merging method with constraints can be called a restricted RU merging method. The restricted RU merging method takes into account the balance between the merging flexibility and the gain brought by the merging, making the merging of multiple RUs more reasonable and less complex. Of course, the merging of RUs may not include any constraints, that is, any RUs can be merged with each other, then this merging method can be called an unrestricted RU merging method.

[0068] An example of a Multi-RU merging method is as follows Figure 3 Among them, it supports large RU merging within 80MHz (see Figure 2 The two 242-tone RUs marked as A are merged, and the one 242-tone RU and one 484-tone RU marked as B are merged. Large RUs within 160MHz are merged (see Figure 2 In the merging method of C, D, E, F, etc., two RUs marked with C are merged, four RUs marked with D are merged, two RUs marked with E are merged, and three RUs marked with F are merged. In addition, Figure 2 Only a part of the possible merging combinations are shown, and the specific merged RU positions, etc. may also vary, and the embodiments of the present application are not specifically limited.

[0069] The size, location, division and indication method of the small RU and large RU mentioned above may refer to the existing 802.11ax, for example, refer to the aforementioned Table 1.

[0070] The 802.11ax standard currently only supports allocating one RU to one user for uplink or downlink OFDMA transmission. In the next-generation WiFi protocol (for example, 802.11be), it will support allocating Multi-RU to one user for uplink or downlink OFDMA transmission. Therefore, in the next-generation WiFi protocol, how to effectively indicate Multi-RU and the sites that use Multi-RU is a crucial issue.

[0071] The embodiment of the present application mainly improves the signaling field in the preamble of the PPDU. The signaling field may be a signaling B (SIG-B) field, and the SIG-B field may be called an EHT-SIG-B field. It is understandable that the SIG-B field may also have other names. The signaling field includes a resource unit allocation subfield and a user field. A resource unit allocation subfield corresponds to the allocation of a 20MHz frequency domain resource unit, and a resource unit allocation subfield indicates the size and position of one or more resource units included in the 20MHz. The resource unit allocation subfield includes multiple bits. For the case where 20MHz includes greater than or equal to 106-tone RUs, since greater than or equal to 106-tone RUs can be used for MU-MIMO transmission, a portion of bits in this resource unit allocation subfield may also be used to indicate the number of users performing MU-MIMO transmission in greater than or equal to 106-tone RUs. Optionally, the resource unit allocation subfield may refer to the design of the resource unit allocation subfield in the HE-SIG-B in 802.11ax. The user field includes a station ID subfield (STAID subfield), which includes the station's associated identifier AID. One or more user fields correspond to a resource unit indicated by the resource unit allocation field. According to the correspondence between the STA ID subfield and the user field and the RU, the station can determine the size and location of the allocated RU.

[0072] It should be noted that the scheme of the embodiments of the present application can be applied to the communication between access points and sites, the communication between access points and access points, and the communication between sites. For example, in downlink transmission, the sending device is the access point and the receiving device is the site. For example, the access point sends a downlink PPDU, allocates the Multi-RU to one or more sites, and indicates the Multi-RU, and the site receives the data carried on the Multi-RU. For another example, in uplink transmission, the sending device is the site and the receiving device is the access point. For example, the site sends an uplink PPDU, uses Multi-RU to send uplink data, and indicates the Multi-RU. For example, the communication between access points and access points can be AP collaboration, in which case the sending device is the access point and the receiving device is also the access point. For example, in D2D transmission, the sending device is the site and the receiving device is also the site.

[0073] For ease of description, in the embodiments of the present application, communication between an access point and a site is adopted, and the sending device is an access point and the receiving device is a site for description and explanation. It can be understood that the sending device can also be a site or an access point, and the receiving device can also be a site or an access point.

[0074] The design in the signaling field is described in detail below in combination with each embodiment.

[0075] Embodiment 1 provides a flexible and effective Multi-RU indication method, so that multiple RUs can be merged and allocated to one or more users for data transmission, thereby improving spectrum efficiency and flexibility of resource unit allocation.

[0076] Method 1: The access point sends a PPDU, which includes a signaling field. The signaling field includes a resource unit allocation subfield and a user field. Among them, a resource unit allocation subfield corresponds to the allocation of a 20MHz frequency domain resource unit, and a resource unit allocation subfield indicates the size and position of one or more resource units included in 20MHz. The resource unit allocation subfield includes multiple bits. Optionally, the resource unit allocation subfield can refer to the design of the resource unit allocation subfield in HE-SIG-B in 802.11ax. For the case where 20MHz includes greater than or equal to 106-tone RUs, since 802.11ax defines that RUs greater than or equal to 106-tone can be used for MU-MIMO transmission, optionally, this resource unit allocation subfield can also have a part of bits used to indicate the number of users performing MU-MIMO transmission in RUs greater than or equal to 106-tone. In an embodiment of the present application, an RU allocated to multiple users may be referred to as a MU-MIMO RU. The user field includes a station ID subfield (STA ID subfield), which includes the station's associated identifier AID. One or more user fields correspond to a resource unit indicated by the resource unit allocation field. According to the correspondence between the station ID subfield and the user field and the RU, the station can determine the size and position of the allocated RU. In a possible implementation, in order to indicate that the Multi-RU is allocated to one or more stations for data transmission, the station ID subfield in each corresponding user field in the Multi-RU can be set to the AID of the station. The station reads the station ID subfield in each user field in the signaling field in turn, and determines that the RU corresponding to the user field carrying its own AID is merged into the Multi-RU, thereby realizing the indication of the Multi-RU. For example, the resource allocation subfield indicates that a 20MHz is divided into RU sizes and the order is: 26-tone RU, 26-tone RU, 26-tone RU, 26-tone RU, 26-tone RU, 52-tone RU and 52-tone RU, which are recorded as [26, 26, 26, 26, 52, 52] for the convenience of description. The signaling field includes 7 user fields, and the AID subfields in the 5th and 6th user fields are set to the AID of STA101. Then STA101 reads the 7 user fields in sequence and determines that the fifth 26-tone RU is combined with the first 52-tone RU and allocated to STA101, so that STA101 can communicate using Multi-RU.

[0077] Method 2: Although method 1 can realize the allocation of multiple resource units, since multiple user fields correspond to one site and each user field carries the same STA ID subfield, there will be a lot of duplicate information in the multiple user fields corresponding to a Multi-RU, and the transmission efficiency is low. In order to improve system performance, method 2 modifies the information in the multiple user fields corresponding to the Multi-RU except the last user field, and indicates the absolute or relative position information of the next merged RU in other user fields. Through this indication, the site allocated with the Multi-RU can directly know the size and position of the next merged RU after reading the user field corresponding to the first RU. Using method 2, the site does not need to read each user field in turn, which saves energy consumption to a certain extent and improves efficiency. For example, the resource allocation subfield indicates that a 20MHz is divided into: [26,26,26,26,26,52,52], where the access point allocates the Multi-RU to STA101, where the Multi-RU includes the first 26-tone RU and the first 52-tone RU, and the user-specific field includes 7 user fields, where the first user field corresponds to the first 26-tone RU, and carries location information indicating that the next RU merged with the first 26-tone RU is the sixth RU, that is, the first 52-tone RU. Then STA101 reads the first user field (the STA ID subfield of the first user field is the AID of STA101), determines that the next merged RU is the sixth RU according to the location information, and after reading the user field corresponding to the sixth RU, determines that there is no other merged RU after the 52-toneRU in the Multi-RU, then STA101 determines that the Multi-RU allocated by the access point to STA101 is the first 26-tone RU and the first 52-tone RU, so that STA101 can communicate on the Multi-RU. Optionally, the location information may include 9 bits, and a value of the 9 bits may uniquely correspond to the size and position of an RU, so that the size and position of the next merged RU may be uniquely determined.

[0078] The method of this embodiment can indicate a Multi-RU obtained based on a restricted merging method, and can also indicate a Multi-RU obtained based on an unrestricted merging method, which has high flexibility and simple implementation. However, since one Multi-RU corresponds to multiple user fields, there is repeated signaling information in the multiple user fields, which has large redundancy and low efficiency.

[0079] Embodiment 2

[0080] Embodiment 2 proposes another method for indicating Multi-RU, which implements Multi-RU indication by carrying a combined indication in a signaling field, which is highly flexible and easy to implement. Figure 4 As shown, the method includes:

[0081] S101: The access point determines a PPDU, where the PPDU includes a signaling field, where the signaling field includes at least one merging indication, and the at least one merging indication is used to indicate the size and position of at least two RUs in a Multi-RU.

[0082] Optionally, the PPDU includes data of a site carried on a Multi-RU. Optionally, the PPDU also includes data carried on other RUs.

[0083] S102: The access point sends the PPDU.

[0084] S103: The station receives the PPDU.

[0085] S104: The site determines the size and position of at least two RUs in a Multi-RU according to at least one merging indication in the PPDU. Optionally, the site obtains data on the Multi-RU. Optionally, the merging indication includes one or more bits. The Multi-RU includes at least two RUs, which can be merged into a large RU or a small RU.

[0086] The signaling field includes: a resource unit allocation subfield, and one or more user fields. A resource unit allocation subfield corresponds to the allocation of a 20MHz frequency domain RU, and a resource unit allocation subfield indicates the size and location of one or more RUs within 20MHz. The resource unit allocation subfield includes multiple bits. Optionally, the resource unit allocation subfield can refer to the design of the resource unit allocation subfield in HE-SIG-B in 802.11ax. The user field includes a STA ID subfield, which is used to indicate to which station the RU corresponding to the user field is allocated.

[0087] Therefore, in order to allow the site to accurately obtain the size and position of at least two RUs in the Multi-RU, the embodiments of the present application provide a variety of methods for indicating Multi-RU. Since the size and position of multiple RUs can be determined by the resource unit allocation subfield, the position of at least two RUs in the Multi-RU can be determined by the resource unit allocation subfield and the combined indication.

[0088] The first method: any user field corresponding to at least two RUs in the Multi-RU contains a merge indication. For example, the Multi-RU includes RU1 and RU2, where RU1 corresponds to user field 1 and RU2 corresponds to user field 2. The merge indication is carried in user field 1, where RU1 and RU2 can be large RUs or small RUs.

[0089] Implementation method 1: The merge indication takes the first value to indicate that RU1 is merged with the adjacent RU2, that is, the merge indication takes the first value to indicate that the Multi-RU includes RU1 and the adjacent RU2, and RU2 is adjacent to RU1, or it can be said that RU2 is continuous with RU1, and RU2 can be the RU adjacent to the left side of RU1, or the RU adjacent to the right side of RU1. The merge indication takes the second value to indicate no merging. For example, the merge indication includes 1 bit, which can be a reserved bit in the user field, or a newly added bit in the user field. For example, taking 1 indicates that the merge indication RU1 is merged with the adjacent (or continuous) RU2 into a Multi-RU. For example, the merge indication in the user field 1 corresponding to the 106-tone RU includes 1 bit, and the merge indication takes 1 to indicate that the 106-tone RU is merged with the adjacent 26-tone RU into one Multi-RU, and the merge indication takes 0 to indicate that the 106-tone RU is not merged with the adjacent 26-tone RU, or, indicates that the 106-tone RU is not merged with other RUs. Within a 20MHz, if the 106-tone RU is on the left side of the 20MHz, the adjacent 26-tone RU is on the right side; if the 106-tone RU is on the right side of the 20MHz, the adjacent 26-tone RU is on the left side.

[0090] Implementation method 2: The user field type in user field 1 can be used as a merge indication. The user field type indicates that the RU1 corresponding to the user field 1 is merged with the adjacent RU2. In other words, the user field type indicates that the RU1 is a merged RU and is merged with the adjacent RU2. Of course, the adjacent RU1 can be located on the left or on the right.

[0091] Implementation method three: The special STA ID in user field 1 can be used as a merge indication, that is, the STA ID subfield in user field 1 takes a special value, for example, 2046, etc., which can be used to indicate that the RU1 corresponding to the user field 1 is merged with the adjacent RU2.

[0092] Optionally, in implementations 1 to 3, by default, RU2 is merged with the RU adjacent to the right. For example, RU2 is the RU adjacent to the left of RU1, user field 1 is located to the left of user field 2, user field 1 carries a merge indication, and takes a first value to indicate that RU1 is merged with RU2 adjacent to the right.

[0093] Implementation method 4: User field 1 carries a bitmap to indicate which RUs in the 20MHz are included in the combination of Multi-RU, that is, it can indicate which RUs in the 20MHz are merged into Multi-RU. One bit in the bitmap corresponds to one RU. For example, if 9 bits are set, 1100 0000 0 indicates that the combination of Multi-RU is the first and second RUs; 11001000 0 indicates that the combination of Multi-RU is the first RU, the second RU and the fifth RU are merged.

[0094] Implementation method 5: User field 1 carries the index of the merged RU, for example, user field 1 carries the index of RU2, indicating that the RU merged with RU1 is RU2. For example, 3 bits are used to indicate that RU2 within 20 MHz is merged with RU1.

[0095] It should be noted that if RU1 is located on the left side of RU2, a merge indication can be carried in user field 1 to indicate that RU1 is merged with RU2. In this case, the merge indication can be implemented in method one, method four, and method five. Optionally, user field 2 can also carry a merge indication in methods one to five, and carry a merge indication on the basis of user field 1 carrying a merge indication, thereby improving robustness. If RU1 is located on the right side of RU2, user field 2 is located before user field 1, and a merge indication can be carried in user field 2. The method is similar and will not be repeated. The first method has low complexity and is simple to implement. It does not require STA to read each user field, which reduces STA processing complexity and saves energy. And implementation methods four and five can be applied to unrestricted RU merging methods.

[0096] The second method: Each user field corresponding to at least two RUs in the Multi-RU contains a merge indication. The size and position of at least two RUs in the Multi-RU are jointly determined based on the merge indication in each user field. For example, the Multi-RU includes RU1 and RU2, wherein RU1 corresponds to user field 1, RU2 corresponds to user field 2, user field 1 carries merge indication 1, user field 2 carries merge indication 2, merge indication 1 takes a first value to indicate that RU1 needs to be merged, that is, merge indication 1 takes a first value to indicate that the Multi-RU includes RU1, and merge indication 2 takes a first value to indicate that RU2 needs to be merged, that is, the Multi-RU includes RU2. Therefore, based on the resource unit allocation subfield, combined with merge indication 1 and merge indication 2, the size and position of RU1 and RU2 in the Multi-RU can be determined. The second method is applicable to unrestricted RU merging. Using the second method, the site needs to read the merge indication in each user field in turn to determine the Multi-RU. It should be noted that the merge indication can be reserved bits in the user field or newly added bits.

[0097] Of course, the combined indication in the embodiment of the present application can also be applied to the trigger frame (Triggerframe) for scheduling uplink transmission, for example Figure 5 As shown, the trigger frame includes: a public domain and a site-by-site domain, wherein the site-by-site domain includes a user information field, wherein the user information field includes: an association identifier AID12 subfield indicating a site, and a resource unit allocation subfield indicating an RU allocated to the site. Optionally, a merge indication may be carried in the user information field of the trigger frame. For example, user information field 1 indicates RU1, and user information field 2 indicates RU2. If the first method is adopted, merge indication 1 may be carried in user information field 1 to indicate that RU1 is merged with RU2. If the second method is adopted, merge indication 1 may be carried in user information field 1, and merge indication 2 may be carried in user information field 2, then merge indication 1 and merge indication 2 indicate that RU1 is merged with RU2.

[0098] In the embodiment of the present application, a merge indication is carried in a signaling field to implement a Multi-RU indication, which is highly flexible and simple to implement.

[0099] The above describes the implementation of the merge indication. For the case where a Multi-RU is assigned to multiple users (or sites) for MU-MIMO, since the MU-MIMO RU is assigned to multiple sites, corresponding to multiple user fields, if the STA ID in each user field corresponding to the Multi-RU is simply set to the AID of the same site, problems will arise. For example, Figure 6As shown, the resource unit allocation subfield indicates that a 20MHz is divided into: [106, 26, 26, 26, 26, 26], where there are 3 users who can apply MU-MIMO transmission in the 106-tone RU. These 3 users are called MU-MIMO users. Therefore, the 106-tone RU corresponds to 3 user fields, and the remaining 5 26-tone RUs correspond to 5 user fields respectively. If the 106-tone RU is combined with the adjacent 26-tone RU on its right into a Multi-RU, the following problems will occur according to the aforementioned method 1:

[0100] 1. Which user's AID should be in the STA ID subfield of the user field 4 corresponding to the 26-tone RU?

[0101] 2.How many MU-MIMO users are using this 26-tone RU? Are they all three users in the 106-tone RU on the left, or just one or two of them?

[0102] 3. If the STA ID subfield of the user field corresponding to the 26-tone RU is set to the STAID of one of the users, according to method 1, the other two STAs corresponding to the 106-tone RU will not think that the 26-tone RU is allocated to them, which will make it difficult to inform the Multi-RU allocation status of the other two users.

[0103] The following third embodiment further introduces the situation where the Multi-RU is allocated to multiple users, and how to further indicate which users can use the Multi-RU for MU-MIMO.

[0104] Take Multi-RU including two RUs as an example. Optionally, the Multi-RU includes a first RU (denoted as RU1) and a second RU (denoted as RU2), and the first RU is a MU-MIMO RU. The access point sends a PPDU, wherein the signaling field of the PPDU includes at least two first user fields (denoted as user field 1) corresponding to the first RU, and a second user field (denoted as user field 2) corresponding to the second RU. The Multi-RU is allocated to multiple users. The site determines the user to whom the Multi-RU is allocated based on the signaling field.

[0105] Methods for indicating which users can use Multi-RU for MU-MIMO may include, but are not limited to:

[0106] Implementation method 1: Since RU1 and RU2 are merged, and RU2 is the RU adjacent to the right side of RU1, the second user field includes MU-MIMO transmission information, indicating: users using Multi-RU for MU-MIMO transmission; or, indicating which users using Multi-RU for MU-MIMO are the users corresponding to RU1, or, indicating that the users using Multi-RU for MU-MIMO are the first few users corresponding to RU1.

[0107] For example, the MU-MIMO transmission information may be a bitmap, for example, including 8 bits or 16 bits, indicating which users corresponding to RU1 can use Multi-RU for MU-MIMO. For example, 1010 0000 corresponds to indicating that the first and third users in RU1 occupy Multi-RU. This method can be used to indicate that some users corresponding to RU1 use Multi-RU for MU-MIMO transmission, which is more flexible and makes full use of the redundant bits in multiple user fields. Optionally, the MU-MIMO transmission information may not be carried in the user field.

[0108] Implementation method 2: The STAs that use Multi-RU for MU-MIMO transmission are not displayed, but are determined by the protocol.

[0109] Optionally, by agreement, the user performing MU-MIMO in Multi-RU is the user corresponding to RU1. Figure 6 As shown in the figure, the first 106-tone RU corresponds to 3 users (corresponding to User field 1 to User field 3, assuming that User field 1 to User field 3 are STA101-STA103), the 106-tone RU is combined with the adjacent 26-tone RU on the right into a Multi-RU, and the Multi-RU is allocated to these 3 users (STA101-STA103) for MU-MIMO. This method does not require additional signaling, which can save signaling overhead.

[0110] Optionally, it may also be agreed by the protocol that the users performing MU-MIMO in the Multi-RU include the users corresponding to RU1 and the users corresponding to another combined RU (RU2). Figure 6As shown, the first 106-tone RU corresponds to 3 users (corresponding to STA101-STA103 respectively), the 106-tone RU and the adjacent 26-tone RU on the right are merged into a Multi-RU, and the 26-tone RU corresponds to 1 user (for example, SRA104). It is agreed that the Multi-RU is allocated to the 4 users (STA101-STA104) corresponding to RU1 and RU2 for MU-MIMO.

[0111] Optionally, in the third embodiment, user field 1 and / or user field 2 may also include the merge indication in the second embodiment, so that the size and position of at least two RUs in the Multi-RU are determined by the merge indication, and further combined with the MU-MIMO transmission information, the user performing MU-MIMO in the Multi-RU can be determined. Figure 6 As shown, if implementation method one is adopted, the first 106-tone RU corresponds to 3 users (corresponding to STA101-STA103 respectively), and at least one of user fields 1 to 3 carries a merging indication, indicating that the 106-tone RU and the adjacent 26-tone RU on the right are merged into a Multi-RU, then user field 4 carries MU-MIMO transmission information, and STA101 to STA103 read the merging indication in user field 1 and the MU-MIMO transmission information in user field 4, and can determine that the 106-tone RU and the adjacent 26-tone RU on the right are merged into a Multi-RU, and which STAs among STA101 to STA103 can use Multi-RU for MU-MIMO. If implementation method 2 is adopted, the first 106-tone RU corresponds to 3 users (corresponding to STA101-STA103 respectively), the 26-tone RU corresponds to 1 user (for example, SRA104), and at least one of user fields 1 to 3 carries a merging indication, indicating that the 106-tone RU and the adjacent 26-tone RU on the right are merged into a Multi-RU. STA101 to STA104 determine that the 106-tone RU and the adjacent 26-tone RU on the right are merged into a Multi-RU, and STA101 to STA104 can use Multi-RU for MU-MIMO.

[0112] Embodiment 4 designs a method for indicating Multi-RU. By using some special resource allocation subfield values ​​and combining the merge indication, the number of user fields can be reduced, signaling overhead can be saved, and the implementation is simple and the compatibility is good. Figure 7 As shown, the method includes:

[0113] S201: The access point determines a PPDU, where the PPDU includes a signaling field, and the signaling field includes a merging indication for indicating whether a first RU is merged with an adjacent second RU into a Multi-RU.

[0114] The signaling field also includes a resource unit allocation subfield, which indicates the size and location of multiple RUs allocated in one 20 MHz, and the multiple RUs include the first RU.

[0115] The resource unit allocation subfield indicates that the corresponding 20MHz is divided into any of the following: [106, -, 52, 52], [52, 52, -, 106], [106, -, 106] or [52, 52, -, 52, 52]; where "-" represents that a 26-toneRU in the middle is not allocated. The second RU is the middle 26-tone RU, and the first RU is a 106-tone RU or a 52-tone RU adjacent to the middle 26-tone RU.

[0116] The resource unit allocation subfield indicates that the corresponding 20MHz is divided into any one of the following: [26,26,26,26,-,106], [26,26,52,-,106], [52,26,26,-,106], [106,-,26,26,26,26], [106,-,52,26,26] or [106,-,26,26,52], the second RU is the middle 26-tone RU, and the first RU is a 106-tone RU adjacent to the middle 26-tone RU.

[0117] The signaling field also includes a user field corresponding to the first RU, and the signaling field does not include a user field corresponding to the second RU; at least one user field corresponding to the first RU includes the merging indication;

[0118] If the merging indication indicates that the first RU and the second RU are merged into a Multi-RU, the Multi-RU is allocated to the user indicated by the user field corresponding to the first RU.

[0119] Optionally, the first RU may be a 106-tone RU or a 52-tone RU, and the 106-tone RU may be allocated to one or more users. In the case where the 106-tone RU is allocated to multiple users, the first RU corresponds to multiple user fields, and the first RU may be called a MU-MIMO RU, then the Multi-RU is allocated to multiple users corresponding to the first RU.

[0120] Optionally, the merging indication includes 1 bit, and the merging indication takes a first value to indicate that the first RU is not merged with the adjacent second RU; the merging indication takes a second value to indicate that the first RU is merged with the adjacent second RU.

[0121] Optionally, the merge indication includes 2 bits, the merge indication takes a first value to indicate that the first RU is not merged with the adjacent second RU; the merge indication takes a second value to indicate that the first RU is merged with the second RU adjacent to the left; the merge indication takes a third value to indicate that the first RU is merged with the second RU adjacent to the right

[0122] S202: The access point sends the PPDU.

[0123] S203: The station receives the PPDU.

[0124] S204: The station determines whether a Multi-RU is allocated according to the signaling field. Optionally, if it is determined that a Multi-RU is allocated, the station obtains data carried on the Multi-RU.

[0125] Optionally, the merge indication may be carried in any user field corresponding to the first RU. The implementation method of the merge indication may refer to the implementation methods 1 to 5 proposed in the above-mentioned embodiment 2.

[0126] Optionally, the PPDU further includes a data field. If the merge indication indicates a merge, it means that the first RU and the second RU are merged into a Multi-RU, and the data field includes data carried on the Multi-RU.

[0127] One possible implementation method is to combine some special value resource allocation subfields specified in the existing 802.11ax standard with the merge indication to implement Multi-RU indication.

[0128] For example, as shown in Table 1, if the access point divides 20MHz into [106, 26, 52, 52], according to the design principles of the resource unit allocation subfield and user field of the existing 802.11ax, the access point needs to set the resource unit allocation subfield to 01000y2y1y0, and the signaling field includes a user field corresponding to the 26-tone RU. In an example of an embodiment of the present application, the access point can merge the 106-tone RU and the 26-tone RU in [106, 26, 52, 52] into a Multi-RU, and the access point can set the resource unit allocation subfield to 00011y2y1y0 according to 802.11ax to indicate that 20MHz is divided into: [106, -, 52, 52], where "-" represents that a 26-tone RU is not allocated, and the signaling field does not include the user field of the 26-tone RU, and the signaling field includes at least one user field corresponding to the 106-tone RU carrying a merge indication. Therefore, after reading 00011y2y1y0, the station supporting 802.11ax will consider that the 26-tone RU immediately adjacent to the right is not allocated, and the signaling field does not include the user field corresponding to the RU, so it does not affect the 802.11ax station from accurately obtaining its own RU allocation status; and if the station supporting the new standard (e.g., 802.11be) determines that the resource unit allocation subfield is 00011y2y1y0 and the merge indication indicates a merge, the station supporting the new standard determines that the 106-tone RU is merged with the 26-tone RU immediately adjacent to the right; if the resource unit allocation subfield is 00011y2y1y0 and the merge indication indicates no merge, it is determined that the 106-tone RU is not merged with the 26-tone RU immediately adjacent to the right, that is, the 26-tone RU is also not allocated.

[0129] Based on similar principles, it can be understood that the resource unit allocation subfields with several special values ​​shown in Table 2 can also implement Multi-RU indication.

[0130] Table 2

[0131]

[0132] For example, as shown in Table 2, the access point can set the resource unit allocation subfield in the signaling field to 01110000, indicating that 20MHz is divided into: [52,52,-,52,52], "-" means that the 26-tone RU is not allocated, and the signaling field does not include the user field of the 26-tone RU. If the merge indication in the user field corresponding to the second 52-tone RU in the signaling field indicates a merge, then the station supporting the new standard can determine that the second 52-tone RU is merged with a 26-tone RU adjacent to its right. Furthermore, the station obtains data on the Multi-RU, and the 802.11ax station still parses according to the 802.11ax protocol agreement, which is not repeated here.

[0133] For another example, the access point can set the resource unit allocation subfield in the signaling field to 00010010, indicating that 20MHz is divided into: [52,52,-,106], and the signaling field includes: user field 1 corresponding to the first 52-tone RU, user field 2 corresponding to the second 52-tone RU, and 3 user fields corresponding to the 106-tone RU (user fields 3-5), wherein at least one of the user fields 3-5 has a merge indication indicating a merge. A site supporting the new standard can determine that the 106-tone RU is merged with a 26-tone RU adjacent to its left side into a Multi-RU. Optionally, it can also be determined that the Multi-RU corresponds to 3 user fields (user fields 3-5) and is allocated to 3 users (or sites). Further, the site obtains data on the Multi-RU.

[0134] In this way, when a Multi-RU is allocated to multiple users, it can be agreed that the users who use the Multi-RU for MU-MIMO are the users corresponding to the MU-MIMO RU.

[0135] This implementation method is compatible with sites that support 802.11ax and can implement Multi-RU indication. Furthermore, it can simply determine users who use Multi-RU for MU-MIMO with low complexity, and saves signaling overhead based on the combination of the value of the special resource unit subfield and the combined indication.

[0136] Furthermore, some reserved values ​​of the resource unit allocation subfield in 802.11ax can be redesigned and defined, and combined with the merge indication to achieve the effect of indicating more types of RU merges.

[0137] Some reserved values ​​in Table 1 are shown in Table 3. The following 6 resource unit allocation subfields and the combined indication jointly indicate the Multi-RU combination, where the reserved value is 011101x1x 0， 01111y2y1y 0， 11011y2y1y 0， 111x4x3x2x1x0. The corresponding relationship between each reserved value and a combination of multiple RUs is not limited and can be flexibly designed.

[0138] Table 3

[0139]

[0140] In the embodiment of the present application, by using some special resource allocation subfield values ​​combined with the merge indication to indicate Multi-RU merging, a user field can be saved, signaling overhead can be saved, and the implementation is simple and compatible. In addition, by using this method, it can be determined that the user performing MU-MIMO transmission in Multi-RU is a user of MU-MIMO RU, and the aforementioned problem does not exist.

[0141] Embodiment 5 introduces another method for indicating the Multi-RU and which STAs can use the Multi-RU for MU-MIMO in a situation where the Multi-RU is allocated to multiple users. Figure 8 The methods shown include:

[0142] S301: Determine the PPDU; the PPDU includes a Multi-RU, the Multi-RU includes a first RU and a second RU, the signaling field of the PPDU includes at least two first user fields corresponding to the first RU, and the second RU corresponds to a second user field, and the STA ID in the second user field is any STA ID in the at least two first user fields.

[0143] When the access point sends a PPDU, if the first RU and the second RU are combined for data transmission, the access point may set the STA ID in the second user field to any STA ID in the at least two first user fields. Optionally, the first RU corresponds to at least two user fields and is a MU-MIMO RU.

[0144] S302: Send PPDU;

[0145] S303: The station receives the PPDU;

[0146] S304: Determine that the Multi-RU includes the first RU and the second RU according to that the STA ID in the second user field is any STA ID in the at least two first user fields.

[0147] Optionally, the site further determines that the users performing MU-MIMO in the Multi-RU are users corresponding to at least two first user fields.

[0148] Optionally, the second user field may also include other information, such as MU-MIMO transmission information, indicating which of the users performing MU-MIMO in the Multi-RU are the users corresponding to at least two first user fields. The implementation method thereof may refer to the aforementioned embodiment three. Furthermore, the site may determine whether to use Multi-RU for MU-MIMO transmission based on the MU-MIMO transmission information. For example, if the site determines that it cannot, the site can only use the first RU for MU-MIMO; if the site determines that it can, the site uses Multi-RU for MU-MIMO.

[0149] Optionally, the embodiment of the present application may not require a merge indication. It is specified that the site needs to read at least two first user fields corresponding to the first RU, and also needs to read the second user field corresponding to the second RU. If the STA ID in the second user field is the same as any STA ID in at least two first user fields, the site can determine that the first RU is merged with the second RU. Furthermore, the site can also determine that the users performing MU-MIMO in Multi-RU are users corresponding to at least two first user sites. Optionally, the STA ID in the second user field is the same as the STA ID in the first user field of at least two first user fields. The STA in the first user field can be regarded as a group leader. After reading the ID of the group leader, other sites can save the STA ID of the group leader. If the STA ID of other user fields is the same as the STA ID of the group leader, it is considered that the RU corresponding to the other user fields is merged with the RU corresponding to itself. Of course, the STA in the non-first first user field in at least two first user fields can also be used as the group leader. The implementation method is similar and will not be repeated.

[0150] Optionally, the positions of the first RU and the second RU may be preset. For example, 20MHz is divided into: [106, 26, 26, 26, 26, 26], and the positions of the first RU and the second RU are the first 106-tone RU and the adjacent 26-tone RU on the right; or, the preset positions of the first RU and the second RU are the 106-tone RU and the second 26-tone RU. The preset position may be agreed upon by the protocol or negotiated in advance between the access point and the site, and is not limited in this application.

[0151] For example, Fig. 9 As shown, 20MHz is divided into: [106, 26, 26, 26, 26, 26], where the 106-tone RU corresponds to user fields 1 to 3 (for example, carrying the IDs of STA101, STA102 and STA103 respectively), and the adjacent 26-tone RU on the right corresponds to user field 4 (carrying the ID of STA101). STA101, STA102 and STA103 can read user fields 1 to 4. For example, STA101 reads that both user field 1 and user field 4 carry the ID of STA101, then it is determined that the 106-tone RU and the adjacent 26-tone RU on the right are merged, and it can be determined that the Multi-RU is allocated to STA101-STA103 for MU-MIMO transmission. STA102 reads user field 1 to user field 4, saves the ID of STA101 in user field 1 corresponding to the 106-tone RU, reads that user field 2 carries its own STA ID, and user field 4 carries STA101 ID, then STA102 can also determine that the 106-tone RU and the adjacent 26-tone RU on the right are merged into a Multi-RU, and can determine that the Multi-RU is allocated to STA101-STA103 for MU-MIMO transmission. The processing of STA103 is similar to that of STA102, which is not repeated here.

[0152] The above example shows the situation where the 106-tone RU is on the left side of 20MHz. It can be understood that the situation where the 106-tone RU is on the right side of 20MHz is similar. The difference is that the site will first read the second user field and then read the first user field. The method for determining Multi-RU is similar to the above and will not be repeated here.

[0153] In addition, although Fig. 9 In the example shown, the Multi-RU is a 106-tone RU and its adjacent 26-tone RU. In fact, the method of the embodiment of the present application is also applicable to the case where non-adjacent RUs are merged. For example, it can be specified that the Multi-RU has other preset positions or no preset positions, and Fig. 9The example shown is that the 106-tone RU and the 26-tone RU are located in the same 20MHz. Of course, the method of this embodiment can also be applied to the case of merging RUs across 20MHz, that is, the 106-toneRU and the 26-tone RU are located in different 20MHz. For the merging of RUs at preset positions, the site only needs to read the user fields corresponding to the RUs according to the preset positions, and there is no need to read all the fields. For the merging of RUs without preset positions, the site needs to read each user field one by one in sequence to determine the Multi-RU. The method of the embodiment of the present application is not only applicable to the merging of two RUs, but also to the merging of more than two RUs, and the principles are similar.

[0154] Embodiment 5 of the present application describes a method that does not require merging indication bits and only requires modifying the STA ID in the user field. The implementation is simple and has good compatibility.

[0155] Embodiment 6 introduces another method for indicating Multi-RU. By carrying the location information of the merged RU, the indication of Multi-RU is realized, which is more flexible and does not need to limit the location of Multi-RU. This method is applicable to both restricted merging and unrestricted merging. Fig.10 As shown,

[0156] S401: Determine a PPDU; the data field of the PPDU includes data carried by a Multi-RU, and the signaling field of the PPDU includes combined RU location information, which is used for the site to determine the Multi-RU;

[0157] The Multi-RU includes a first RU and a second RU, and the signaling field of the PPDU includes at least two first user fields corresponding to the first RU and one second user field corresponding to the second RU.

[0158] Optionally, the second user field includes merged RU location information for indicating the location of the first RU; or, the first user field includes merged RU location information for indicating the location of the second RU; or, the signaling field includes merged RU location information.

[0159] Optionally, the first RU is allocated to multiple users and is a MU-MIMO RU. Optionally, the first RU may be a RU greater than or equal to 106-tone. For example, it may be a 106-tone RU, a 242-tone RU, or a 484-tone RU, or a 996-tone RU.

[0160] S402: Send PPDU.

[0161] S403: The station receives the PPDU.

[0162] S404: Determine Multi-RU according to the merged RU location information.

[0163] There are many ways to carry the combined RU location information, including but not limited to:

[0164] Mode 1: The second user field carries the merged RU location information, indicating the location of the first RU. The site determines to merge the first RU with the second RU according to the merged RU location information.

[0165] For method 1, there are the following situations:

[0166] In case 1, the second RU is located on the left side of the first RU, and the second user field is located on the left side of at least two first user fields. The second user field carries the merged RU location information. When the STA reads the second user field carrying its own STA ID and the merged RU location information indicating the first RU, it determines that the first RU and the second RU are merged into a Multi-RU, and further parses the data carried on the Multi-RU.

[0167] Scenario 2: If the second RU is located on the right side of the first RU, then the second user field is located on the right side of at least two first user fields (i.e., the second user field is located after at least two first user fields), and the second user field carries the merged RU location information and the merge indication. The STA first reads the STA ID carried in the first user field to determine that the STA is assigned the first RU. Furthermore, the site continues to read subsequent user fields. If the merge indication in the second user field indicates a merge, and the RU indicated by the merged RU location information is the first RU, the STA determines that the first RU and the second RU are merged into a Multi-RU, and further parses the data carried on the Multi-RU.

[0168] Mode 2: The first user field carries the merged RU location information, indicating the location of the second RU. The site determines that the Multi-RU includes the first RU and the second RU according to the merged RU location information.

[0169] For example, the second RU is located on the right side of the first RU, the second user field is located on the right side of at least two first user fields (that is, the second user field is located after at least two first user fields), and the first user field carries the merged RU location information. When the STA reads the first user field carrying its own STA ID and the merged RU location information indicating the second RU, it determines that the first RU and the second RU are merged into a Multi-RU, thereby parsing the data carried on the Multi-RU.

[0170] Mode 3: The signaling field includes the merged RU location information, which can be used to indicate the first RU and the second RU included in the Multi-RU. The site determines the size and location of the first RU and the second RU included in the Multi-RU based on the merged RU location information, thereby parsing the data carried in the Multi-RU.

[0171] Optionally, the merged RU location information is located in a new field of the signaling field, and the new field can be located before the first and second user fields. In one example, the new field is a special user field, indicating that the first RU is merged with the second RU. In order to prevent the subsequent user fields from having errors in the reading order and position, the number of the first user field needs to be 1 more than the actual number of users. For example, 20MHz is divided into: [106, 26, 26, 26, 26, 26]. There are 3 users on the 106-tone RU, and 1 user field can be added to the signaling field. Therefore, the 106-tone RU corresponds to 4 user fields. The extra user field can carry the location information of the first RU and the location information of the second RU. In another example, the new field is other fields located before the user-specific field, which can also be called a location information field, etc., without limitation.

[0172] Furthermore, the specific implementation methods of merging RU location information include the following:

[0173] The first type: The merged RU location information is a bitmap, where one bit corresponds to one RU. For example, a 20MHz is divided into a maximum of 9 RUs, and the merged RU location information can be 9 bits or 8 bis, indicating the merged RUs within the 20MHz, thereby indicating Multi-RU. For example, 20MHz is divided into: [106, 26, 26, 26, 26, 26], and the merged RU location information is 9 bits, and its value is 110000000, indicating that the 106-tone RU and the adjacent 26-tone RU are merged into one Multi-RU.

[0174] The second type: The merged RU position information includes multiple bits, and any value of these multiple bits corresponds to an RU within 20MHz. The merge indication can be carried in the user field. For example, the merge indication is carried in any first user field. The merge indication is 4 bits or 3 bits, indicating the position of the second RU in 20MHz. Since the first RU may be merged with other RUs except the first RU to form a Multi-RU, there are a maximum of 8 RUs that can participate in the merge within 20MHz, which can also be achieved using 3 bits.

[0175] The first and second methods are applicable to the situation where Multi-RUs are located in the same 20MHz.

[0176] The third type: the merged RU location information includes multiple bits, some of which are used to indicate the 20MHz where the merged RU is located, and the other bits are used to indicate which RU in the 20MHz the merged RU is. For example, the merged RU location information includes 8 bits, and the merged RU location information is located in the second user field, of which 4 bits indicate which 20MHz in the entire channel the first RU merged with the second RU is located. If the entire channel bandwidth is 320MHz, 4 bits can be implemented, and the other 4 bits indicate which RU in the 20MHz the first RU is, thereby implementing the indication of the first RU.

[0177] The fourth type: the merged RU location information includes multiple bits, and the values ​​of the multiple bits indicate which RU in the 320MHz the merged RU is. For example, the merged location information includes 9 bits, of which 2 bits are used to indicate which 80MHz in the 320MHz the merged RU is located, and the other 7 bits are used to indicate which RU in the 80MHz the merged RU is. Optionally, the indication of these 7 bits can refer to the design of B12-B19 in the user information field in the trigger frame in the existing 802.11ax. The 320MHz channel can be composed of 4 80MHz, 2 80MHz and one 160MHz, 2 160MHz, or 1 240MHz and 1 80MHz.

[0178] The third method and the fourth method can be applied to the situation where any multiple RUs within 320MHz are merged.

[0179] It should be noted that, since there is a corresponding relationship between the position of the RU in 20 MHz and the position of each user field in the user-specific field, it can also be said that the merged RU position information indicates the position of the user field of the merged RU.

[0180] Optionally, the user field may further include a merge indication. For a detailed description of the merge indication, reference may be made to the foregoing embodiment, for example: Fig.11As shown, User field 1 to 3 correspond to STA101 to STA103 respectively, and User field 4 includes a merge indication. For example, the merge indication in User field 4 is a special STA ID or other implementation method (refer to the aforementioned embodiment 2), indicating that the 26-tone RU is a merged RU, and User field 4 also includes location information pointing to the 106-tone RU, then STA101 to STA103 can determine that the Multi-RU is (106+26) according to the merge indication and the location information. Of course, the merge indication may not be included, but the merged RU location information is used to implement the functions of the merge indication and the location indication. For example, the merged RU location information 9 bits is set to a certain value, such as a special location value (such as 000000000), indicating that there is no RU merge, and when other values ​​are taken, the location of the merged RU is indicated.

[0181] The method of the embodiment of the present application is not only applicable to the situation where the Multi-RU is assigned to one user, but also to the situation where the Multi-RU is assigned to multiple users, which is not limited by the present application. Optionally, the second user field may also include MU-MIMO transmission information. Optionally, it may also be agreed by the protocol that the users performing MU-MIMO in the Multi-RU are the multiple users corresponding to the first RU. Please refer to the implementation method 1 and implementation method 2 of the aforementioned embodiment 3, which will not be repeated here.

[0182] Embodiment 7 provides another method for indicating a Multi-RU, and indicating which users the Multi-RU is allocated to. In this embodiment, the focus is on the merging of large RUs. It should be noted that there is a difference between small RUs and large RUs when MU-MIMO is merged. For small RUs, the notification of the number of users of MU-MIMO is mainly based on a single RU Allocation subfield, while for large RUs, the notification of the number of users of MU-MIMO will involve multiple RU Allocation subfields. For example, if a Multi-RU includes a 242-tone RU and another 242-tone RU, the two 242-tone RUs will involve two resource unit allocation subfields. The access point determines the PPDU, the PPDU includes a signaling field, and the access point sends the PPDU.

[0183] How to indicate the Multi-RU and the user using the Multi-RU may include but is not limited to the following methods:

[0184] Method 1: The signaling field includes at least one first user field (user field 1) corresponding to the first RU and at least one second user field (user field 2) corresponding to the second RU, and the first RU and the second RU are merged into a Multi-RU. Let the number of user fields 1 be the same as the number of user fields 2, and the STA ID in the user field 1 be the same as the STA ID in the user field 2. For example, the Multi-RU is (242+242), and the resource unit allocation sub-word 1 corresponding to the first 242-tone RU has a value of 11000001, corresponding to 2 user fields 1, and the resource unit allocation sub-field 2 corresponding to the second 242-tone RU also has a value of 11000001, corresponding to 2 user fields 2, and the STA IDs of the two user fields 1 are the same as the STA IDs in the two user fields 2. Optionally, at least one of the two user fields 1 or the two user fields 2 may also include a merge indication, which indicates that the RU is merged with other RUs. After the station corresponding to the user field 1 reads the STA ID and the merge indication in the user field 1, it can be determined that the Multi-RU is (242+242) and is allocated to 2 users.

[0185] Of course, Multi-RU can also be (242+484), then the resource unit subfield 1 takes the value of 11000001, which also corresponds to 2 user fields 1, and the resource unit subfield 2 takes the value of 11001001, which corresponds to 2 user fields 2. The STAIDs of the 2 user fields 1 are the same as the STA IDs in the 2 user fields 2. Other examples will not be repeated.

[0186] Method 2: The access point determines the PPDU, and the PPDU includes a signaling field. The signaling field includes N first user fields (user field 1) corresponding to the first RU, where N is greater than or equal to 1. The Multi-RU includes a first RU and a second RU, wherein the first resource unit allocation subfield indicates that the first RU corresponds to N user fields 1, and the second resource unit allocation subfield indicates that the second RU is empty (zero user, not allocated). And at least one user word carries a merging indication. The site determines based on the above information that the Multi-RU includes the first RU and the second RU, and is allocated to N users. Optionally, the value of the second resource unit allocation subfield can be 0111000 or 01110010, or 01110011. By adopting this method, the number of user fields is saved, thereby saving signaling overhead, and the implementation is simple.

[0187] Method three: The access point determines the PPDU, the PPDU includes a signaling field, the signaling field includes N first user fields (user field 1) corresponding to the first RU and 1 second user field (user field 2) corresponding to the second RU, and the Multi-RU includes the first RU and the second RU. Optionally, the user field may also carry a merge indication, indicating that the first RU is merged with the second RU. Optionally, the merge indication may adopt the first method and the second method introduced in the aforementioned embodiment two. Furthermore, the user to whom the Multi-RU is assigned may be determined in a similar manner to the aforementioned embodiment three.

[0188] For example, the Multi-RU is (242+484), the resource unit allocation subfield 1 indicates that the 242-tone RU is allocated to 6 users, the 6 user fields 1 indicate the 6 users, and the resource unit allocation subfield 2 indicates that the 484-tone RU corresponds to 1 user field 2. Optionally, the user field 2 carries the STA ID in the first user field 1 or carries a special STA ID, indicating that the 484-tone RU is merged with the 242-tone RU. Furthermore, the site can also determine that the Multi-RU is allocated to the 6 users corresponding to the 6 user fields 1. If the STA ID of the user field 2 is the ID of another site, the site can also determine that the Multi-RU is allocated to the users corresponding to the 7 user fields. Optionally, the user field 2 can also carry MU-MIMO transmission information (as described in Example 3), and the site can determine which users the Multi-RU is allocated to based on the MU-MIMO transmission information.

[0189] For another example, the merge information of the user field 2 can also be a 16-bit merged bitmap, where each bit corresponds to a 242-tone RU. In this way, 16 bits can represent the large RU merging situation on 320MHz. When the merge information is represented in this way, the Multi-RU can be determined based on the information. If the number of RUs included in the Multi-RU is greater than 2, if the value of the 16 bits can be 1001 1111 0000 0000, combined with the resource unit allocation subfield, it can be determined that the Multi-RU is (242+242+996), then the resource unit subfield corresponding to the third and subsequent RUs can indicate that the RU is empty (zero user), and the signaling field does not include the user fields corresponding to the third and subsequent RUs, thereby saving the number of user fields.

[0190] For another example, the merge indication may be carried in the user field 1, and the merge indication may adopt the implementation method 1, implementation method 4, implementation method 5 and the second method in the second embodiment.

[0191] For example, as shown in Table 4, the commonly used merging combinations within 80MHz are as follows:

[0192] Table 4

[0193]

[0194] One row represents a merger. The first row indicates that the Multi-RU includes the first 242-tone RU and the fourth 242-tone RU. A merger indication can be carried in the user field 1 corresponding to the first 242-tone RU, indicating that the 242-tone RU is merged with the fourth 242-tone RU. The merger indication can be one bit or multiple bits, which will not be described in detail.

[0195] For example, as shown in Table 5, when the frequency is greater than 80 MHz and less than or equal to 160 MHz, the merge indication method can also combine the location of the 484-tone RU and whether to merge to indicate some merge combinations.

[0196] Table 5: Commonly used merging combinations within 160MHz are as follows:

[0197]

[0198] In the second and fifth rows, the Multi-RU includes a 484-tone RU and a 996-tone RU, and a merge indication can be carried in the user field corresponding to the 484-toneRU, indicating that the 484-tone RU is merged with the 996-tone RU. The merge indication can be one bit or multiple bits, refer to the second embodiment, and will not be repeated.

[0199] Table 6 shows the combination between 996-tone RUs. The combination indication can be carried in the user field corresponding to the 996-tone RU as shown in the following table.

[0200] Table 6

[0201]

[0202] It should be noted that a one-bit merging indication can only indicate the merging status of RUs in one preset position. Of course, the merging indication can also include more bits, for example, 2 bits, and 2 bits can indicate the merging status of RUs in more preset positions.

[0203] Of course, the method of the embodiment of the present application can also be applied to the trigger frame (Triggerframe) for scheduling uplink transmission, for example Figure 5As shown, the trigger frame includes: a public domain and a site-by-site domain, wherein the site-by-site domain includes a user information field, wherein the user information field includes: an association identifier AID12 subfield indicating the site, and a resource unit allocation subfield indicating the RU allocated to the site. Optionally, the merge indication may be carried in the user information field of the trigger frame. For example, similar to method one of embodiment seven, the Multi-RU is (242+242), and the first 242-tone RU is allocated to 3 users, corresponding to user information fields 1 to 3, and the second 242-tone RU corresponds to user information fields 4 to 6. The AID12 subfields in user information fields 4 to 6 can be sequentially the same as the AID subfields in user fields 1 to 3, and it can be determined that the Multi-RU is allocated to these three users for use. For another example, similar to method three of embodiment seven, the Multi-RU is (242+242), and the first 242-tone RU is allocated to 3 users, corresponding to user information fields 1 to 3, and the second 242-tone RU corresponds only to 1 user information field 4. The AID12 field of the user information field 4 is the AID of the user field 1, then it is determined that the Multi-RU is allocated to these 3 users. Of course, the MU-MIMO transmission information can also be carried in the user information field 4, and the MU-MIMO transmission information indicates which users the Multi-RU is allocated to.

[0204] This embodiment focuses on the merging of large RUs, and supports merging large RUs and allocating them to one or more users for transmission. It can effectively support the merging of multiple discontinuous large RUs in a large bandwidth, and can improve the flexibility of large RU merging and spectrum efficiency. For example, for the next generation of 802.11ax, such as 802.11be, part of the 20MHz in 320MHz is unavailable, resulting in discontinuous available 20MHz channels. Using the 802.11ax protocol, only multiple continuous 20MHz channels can be allocated to one or more users. The discontinuous part of the 20MHz channel may be wasted. Using the method of this embodiment, discontinuous large RUs can be merged into Multi-RU and allocated to one or more users, thereby improving the spectrum efficiency of the system.

[0205] Embodiment 8 provides a communication device for implementing the method performed by the sending device in any of the above embodiments. It can be understood that the device can be an access point or a station, or a chip in an access point or a station. Fig.12 As shown, the communication device 1200 includes: a transceiver unit 1201 and a processing unit 1202 .

[0206] In the first example, the communication device is used to implement the method or function performed by the sending device in embodiment 1. For example, the processing unit is used to determine a PPDU, the PPDU includes a signaling field, the signaling field includes multiple user fields, and at least two RUs corresponding to user fields with the same STA ID in the multiple user fields are merged into a Multi-RU. The transceiver unit sends the PPDU.

[0207] In the second example, the communication device is used to implement the method or function performed by the sending device in the second embodiment. For example, the processing unit is used to perform step S101. The transceiver unit is used to perform step S102. The implementation method of the merge indication can refer to the above-mentioned second embodiment.

[0208] In the third example, the communication device is used to implement the method or function performed by the sending device in Example 3. For example, the processing unit is used to determine the PPDU, and the PPDU includes a signaling field, and the signaling field includes MU-MIMO transmission information for indicating: users who use Multi-RU for MU-MIMO transmission; or, indicating which users using Multi-RU for MU-MIMO are RU1 corresponding to the users, or, indicating that the users using Multi-RU for MU-MIMO are the first users corresponding to RU1. The transceiver unit sends the PPDU. Multi-RU includes RU1 and RU2. The implementation method of the MU-MIMO transmission information can refer to the aforementioned Example 3.

[0209] In the fourth example, the communication device is used to implement the method or function performed by the sending device in the fourth embodiment. For example, the processing unit is used to perform step S201. The transceiver unit is used to perform step S202. The implementation method of the merge indication can refer to the aforementioned fourth embodiment. The implementation method of the resource unit allocation subfield and the merge indication can refer to the aforementioned fourth embodiment.

[0210] In the fifth example, the communication device is used to implement the method or function performed by the sending device in the fifth embodiment. For example, the processing unit is used to perform step S301. The transceiver unit is used to perform step S302. Among them, the signaling field also includes a resource unit allocation subfield, and the implementation method of the resource unit allocation subfield and the merge indication can refer to the aforementioned fifth embodiment.

[0211] In the sixth example, the communication device is used to implement the method or function performed by the sending device in the sixth embodiment. For example, step S401 is performed. The transceiver unit is used to perform step S402. The implementation method of merging RU location information can refer to the aforementioned sixth embodiment.

[0212] In the seventh example, the communication device is used to implement the method or function performed by the sending device in the seventh embodiment. For example, the processing unit determines the PPDU; the PPDU includes a signaling field. The transceiver unit sends the PPDU. Among them, the signaling field also includes a resource unit allocation subfield, and the implementation method of the resource unit allocation subfield and the merge indication can refer to the aforementioned seventh embodiment.

[0213] Embodiment 9 provides a communication device for implementing the method performed by the receiving device in any of the above embodiments. It can be understood that the device can be an access point or a station, or a chip in an access point or a station. Fig.13 As shown, the communication device 1300 includes: a transceiver unit 1301 and a processing unit 1302 .

[0214] In the first example, the communication device is used to implement the method or function performed by the receiving device in the first embodiment. For example, the transceiver unit is used to receive a PPDU, the PPDU includes a signaling field, the signaling field includes multiple user fields, and at least two RUs corresponding to user fields with the same STA ID in the multiple user fields are merged into a Multi-RU. The processing unit is used to determine that at least two RUs corresponding to user fields with the same STA ID in the multiple user fields are merged into a Multi-RU.

[0215] In the second example, the communication device is used to implement the method or function performed by the receiving device in the second embodiment. For example, the transceiver unit is used to perform step S103. The processing unit is used to perform step S104. The implementation method of the merge indication can refer to the above-mentioned second embodiment.

[0216] In the third example, the communication device is used to implement the method or function performed by the receiving device in Example 3. For example, the processing unit is used to determine the PPDU, and the PPDU includes a signaling field, and the signaling field includes MU-MIMO transmission information for indicating: users who use Multi-RU for MU-MIMO transmission; or, indicating which users using Multi-RU for MU-MIMO are corresponding to RU1, or, indicating that the users using Multi-RU for MU-MIMO are the first few users corresponding to RU1. The transceiver unit sends the PPDU. Multi-RU includes RU1 and RU2. The implementation method of MU-MIMO transmission information can refer to the aforementioned Example 3.

[0217] In the fourth example, the communication device is used to implement the method or function performed by the receiving device in the fourth embodiment. For example, the transceiver unit is used to perform step S203. The processing unit is used to perform step S204. Among them, the signaling field also includes a resource unit allocation subfield, and the implementation method of the resource unit allocation subfield and the combined indication can refer to the aforementioned fourth embodiment.

[0218] In the fifth example, the communication device is used to implement the method or function performed by the receiving device in the fifth embodiment. For example, the transceiver unit is used to perform step S303. The processing unit is used to perform step S304. Among them, the signaling field also includes a resource unit allocation subfield, and the implementation method of the resource unit allocation subfield and the combined indication can refer to the aforementioned fifth embodiment.

[0219] In the sixth example, the communication device is used to implement the method or function performed by the receiving device in the sixth embodiment. For example, the transceiver unit is used to perform step S403. The processing unit is used to perform step S404. The implementation method of merging RU location information can refer to the aforementioned sixth embodiment.

[0220] In the seventh example, the communication device is used to implement the method or function performed by the receiving device in the seventh embodiment. For example, the processing unit determines the PPDU; the PPDU includes a signaling field. The transceiver unit sends the PPDU. Among them, the signaling field also includes a resource unit allocation subfield, and the implementation method of the resource unit allocation subfield and the merge indication can refer to the aforementioned seventh embodiment.

[0221] Fig.14 A possible structural diagram of a communication device 1400 in the above embodiment is shown, and the device 1400 may include: a processor 1402, a transceiver 1404, and optionally, a computer-readable storage medium / memory 1403, an input device 1405 and an output device 1406, and a bus 1401. Among them, the processor, the transceiver, the computer-readable storage medium, etc. are connected through the bus. The embodiment of the present application does not limit the specific connection medium between the above components.

[0222] In a possible implementation, the device 1400 may be configured as AP1 (e.g., AP105) in the aforementioned WLAN communication system, or a chip system or chip in an AP, or configured as a STA in a WLAN system. The device 1400 may execute the method and steps involving the transmitting end device in any of the above embodiments.

[0223] Exemplarily, the transceiver 1404 may be used to support the communication between the sending device and the receiving device in the above embodiment, and may execute Figures 4 to 10 The transmitting and receiving processes of the sending device and / or other processes used for the technology described in this application are involved.

[0224] For example, the transceiver 1404 may be used to execute S102, S202, or S302 or S402; of course, the transceiver 1404 may also be used to execute other processes and methods of the technology described in this application.

[0225] The processor 1402 is used to control and manage the actions of the above-mentioned sending device, and is used to execute the processing performed by the sending device in the above-mentioned embodiment, and can execute Figures 4 to 10 The processor 1402 may be responsible for managing the bus and executing programs or instructions stored in the memory. For example, the processor 1402 may be used to execute S101, S201, S301, or S401. Of course, the processor 1402 may also be used to execute other processes and methods of the technology described in this application.

[0226] The computer-readable storage medium / memory 1403 stores programs, instructions or data for executing the technical solution of the present application. For example, the computer-readable storage medium / memory 1403 may contain instructions sufficient to allow the device 1400 to execute the methods and functions in any of the above embodiments.

[0227] In another possible implementation, the device 1400 may be configured as an AP1 (e.g., AP105) in the aforementioned WLAN communication system, or a chip system or chip in an AP, or configured as a STA in a WLAN system. The device 1400 may execute the method and steps involving a receiving device in any of the above embodiments.

[0228] Exemplarily, the transceiver 1404 may be used to support the receiving device to communicate with the sending device in the above embodiment, and may execute Figures 4 to 10 The transceiver process of the receiving device and / or other processes used for the technology described in this application are involved.

[0229] For example, the transceiver 1404 may be used to execute S103, S203, or S303 or S403; of course, the transceiver 1404 may also be used to execute other processes and methods of the technology described in this application.

[0230] The processor 1402 is used to control and manage the actions of the above-mentioned sending device, and is used to execute the processing performed by the sending device in the above-mentioned embodiment, and can execute Figures 4 to 10 The processor 1402 may be responsible for managing the bus and executing programs or instructions stored in the memory. For example, the processor 1402 may be used to execute S104, S204, S304, or S404. Of course, the processor 1402 may also be used to execute other processes and methods of the technology described in this application.

[0231] The computer-readable storage medium / memory 1403 stores programs, instructions or data for executing the technical solution of the present application. For example, the computer-readable storage medium / memory 1403 may contain instructions sufficient to allow the device 1400 to execute the methods and functions in any of the above embodiments.

[0232] Understandably, Fig.10 Only a simplified design of the communication device 1400 is shown. In actual applications, the communication device 1400 may include any number of transceivers, processors, memories, etc., and all communication devices 1400 that can implement the present application are within the protection scope of the present invention.

[0233] The processor involved in the above-mentioned device 1400 can be a general-purpose processor, such as a general-purpose central processing unit (CPU), a network processor (Network Processor, referred to as NP), a microprocessor, etc., or an application-specific integrated circuit (application-specific integrated circuit, referred to as ASIC), or one or more integrated circuits for controlling the execution of the program of the present application. It can also be a digital signal processor (Digital Signal Processor, referred to as DSP), a field programmable gate array (Field-Programmable Gate Array, referred to as FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. The controller / processor can also be a combination that realizes a computing function, such as a combination of one or more microprocessors, a combination of DSP and microprocessors, etc. The processor usually performs logical and arithmetic operations based on program instructions stored in a memory.

[0234] The computer-readable storage medium / memory 1403 involved above may also store an operating system and other application programs. Specifically, the program may include a program code, and the program code includes a computer operation instruction. More specifically, the above-mentioned memory may be a read-only memory (ROM), other types of static storage devices that can store static information and instructions, a random access memory (RAM), other types of dynamic storage devices that can store information and instructions, a disk storage, and the like. The memory 1803 may be a combination of the above-mentioned storage types. And the above-mentioned computer-readable storage medium / memory may be in the processor, or may be outside the processor, or distributed on multiple entities including a processor or a processing circuit. The above-mentioned computer-readable storage medium / memory may be specifically embodied in a computer program product. For example, a computer program product may include a computer-readable medium in a packaging material.

[0235] Alternatively, device 1400 may also be configured as a general-purpose processing system, such as what is commonly referred to as a chip, which includes: one or more microprocessors that provide processor functionality; and an external memory that provides at least a portion of the storage medium, all of which are connected together with other supporting circuits through an external bus architecture.

[0236] The embodiment of the present application also provides a chip system, which includes a processor for supporting a sending device or a receiving device to implement the functions involved in any of the above embodiments, such as generating or processing the data and / or information involved in the above method. In one possible design, the chip system may also include a memory, which is used for the necessary program instructions and data for the sending end or the receiving end. When the processor runs the program instructions, the device on which the chip system is installed implements the method involved in any of the above embodiments. The chip system can be composed of chips, or it can include chips and other discrete devices.

[0237] The embodiment of the present application also provides a processor for coupling with a memory, the memory storing instructions, when the processor runs the instructions, the processor performs the method and function of the sending device or receiving device in any of the above embodiments. The embodiment of the present application also provides a computer program product containing instructions, when it runs on a computer, the computer performs the method and function of the sending device or receiving device in any of the above embodiments. The embodiment of the present application also provides a computer readable storage medium, the readable storage medium stores instructions, when the processor runs the instructions, the processor performs the method and function of the sending device or receiving device in any of the above embodiments.

[0238] An embodiment of the present application also provides a device for executing the methods and functions involving a receiving end or a transmitting end in any of the above embodiments.

[0239] The steps of the method or algorithm described in conjunction with the disclosure of the present application can be implemented in a hardware manner, or can be implemented by a processor executing software instructions. The software instructions can be composed of corresponding software modules, and the software modules can be stored in a RAM memory, a flash memory, a ROM memory, an EPROM memory, an EEPROM memory, a register, a hard disk, a mobile hard disk, a CD-ROM or any other form of storage medium well known in the art. An exemplary storage medium is coupled to the processor so that the processor can read information from the storage medium and can write information to the storage medium. Of course, the storage medium can also be a component of the processor. The processor and the storage medium can be located in an ASIC. In addition, the ASIC can be located in a user device. Of course, the processor and the storage medium can also be present in the user device as discrete components.

[0240] Those skilled in the art should be aware that in one or more of the above examples, the functions described in this application can be implemented using hardware, software, firmware, or any combination thereof. When implemented using software, these functions can be stored in a computer-readable medium or transmitted as one or more instructions or codes on a computer-readable medium. Computer-readable media include computer storage media and communication media, wherein communication media include any media that facilitates the transmission of a computer program from one place to another. The storage medium can be any available medium that a general or special-purpose computer can access.

[0241] The specific implementation methods described above further illustrate the purpose, technical solutions and beneficial effects of the present application in detail. It should be understood that the above description is only the specific implementation methods of the present application and is not intended to limit the scope of protection of the present application. Any modifications, equivalent substitutions, improvements, etc. made on the basis of the technical solutions of the present application should be included in the scope of protection of the present application.

Claims

1. A communication device for indicating a combination of multiple resource units Multi-RU allocated to one or more users for data transmission, characterized in that: The device comprises: A processing unit, configured to determine a physical layer protocol data unit PPDU, wherein the PPDU includes a signaling field, the signaling field includes a merge indication, which is used to indicate whether a first RU is merged with an adjacent second RU into a Multi-RU; the merge indication includes 2 bits, the merge indication takes a first value to indicate that the first RU is not merged with the adjacent second RU; the merge indication takes a second value to indicate that the first RU is merged with the second RU adjacent to the left; the merge indication takes a third value to indicate that the first RU is merged with the second RU adjacent to the right; the signaling field also includes a user field corresponding to the first RU, and the signaling field does not include a user field corresponding to the second RU; The transceiver unit is used to send the PPDU.

2. A communication device for indicating a combination of multiple resource units Multi-RU allocated to one or more users for data transmission, characterized in that: The device comprises: A transceiver unit, configured to receive a physical layer protocol data unit PPDU, wherein the PPDU includes a signaling field, the signaling field includes a merge indication, which is used to indicate whether a first RU is merged with an adjacent second RU into a Multi-RU, the signaling field also includes a user field corresponding to the first RU, and the signaling field does not include a user field corresponding to the second RU; the merge indication includes 2 bits, the merge indication takes a first value to indicate that the first RU is not merged with the adjacent second RU; the merge indication takes a second value to indicate that the first RU is merged with the second RU adjacent to the left; the merge indication takes a third value to indicate that the first RU is merged with the second RU adjacent to the right; A processing unit is used to determine whether the communication device is allocated a Multi-RU according to the signaling field.

3. The communication device according to claim 1 or 2, characterized in that: The signaling field also includes a resource unit allocation subfield, which indicates the size and location of multiple RUs allocated in one 20 MHz, and the multiple RUs include the first RU.

4. The communication device according to claim 3, characterized in that: The resource unit allocation subfield indicates that the corresponding 20MHz is divided into any one of the following: [106, -, 52, 52], [52, 52, -, 106], [106, -, 106], [52, 52, -, 52, 52]; wherein [N, M] indicates N-tone RU and M-tone RU, respectively; The second RU is a middle 26-tone RU, and the first RU is a 106-tone RU or a 52-tone RU adjacent to the middle 26-tone RU.

5. The communication device according to claim 3, characterized in that: The resource unit allocation subfield indicates that the corresponding 20 MHz is divided into any one of the following: [26, 26, 26, 26, -, 106], [26, 26, 52, -, 106], [52, 26, 26, -, 106], [106, -, 26, 26, 26, 26], [106, -, 52, 26, 26] or [106, -, 26, 26, 52], where [N, M] indicates N-tone RU and M-tone RU, respectively; The second RU is a middle 26-tone RU, and the first RU is a 106-tone RU adjacent to the middle 26-tone RU.

6. The communication device according to claim 1 or 2, characterized in that: The user field corresponding to the first RU includes the merging indication; If the merging indication indicates that the first RU and the second RU are merged into a Multi-RU, the Multi-RU is allocated to the user indicated by the user field corresponding to the first RU, and the PPDU also includes a data field, and the data field includes data carried on the Multi-RU.

7. The communication device according to claim 6, characterized in that: The first RU is a 106-tone RU, and the 106-tone RU corresponds to at least two user fields.

8. A method for indicating a combination of multiple resource units Multi-RU allocated to one or more users for data transmission, characterized in that: The method comprises: Determine a physical layer protocol data unit PPDU, the PPDU includes a signaling field, the signaling field includes a merge indication, which is used to indicate whether a first RU is merged with an adjacent second RU into a Multi-RU; the merge indication includes 2 bits, the merge indication takes a first value to indicate that the first RU is not merged with the adjacent second RU; the merge indication takes a second value to indicate that the first RU is merged with the second RU adjacent to the left; the merge indication takes a third value to indicate that the first RU is merged with the second RU adjacent to the right; the signaling field also includes a user field corresponding to the first RU, and the signaling field does not include a user field corresponding to the second RU; The PPDU is sent.

9. A method for indicating a combination of multiple resource units Multi-RU allocated to one or more users for data transmission, characterized in that: The method comprises: Receive a physical layer protocol data unit PPDU, the PPDU includes a signaling field, the signaling field includes a merge indication, which is used to indicate whether a first RU is merged with an adjacent second RU into a Multi-RU, the signaling field also includes a user field corresponding to the first RU, and the signaling field does not include a user field corresponding to the second RU; the merge indication includes 2 bits, the merge indication takes a first value to indicate that the first RU is not merged with the adjacent second RU; the merge indication takes a second value to indicate that the first RU is merged with the second RU adjacent to the left; the merge indication takes a third value to indicate that the first RU is merged with the second RU adjacent to the right; Whether Multi-RU is allocated is determined based on the signaling field.

10. The method according to claim 8 or 9, characterized in that: The signaling field also includes a resource unit allocation subfield, which indicates the size and location of multiple RUs allocated in one 20 MHz, and the multiple RUs include the first RU.

11. The method according to claim 10, characterized in that The resource unit allocation subfield indicates that the corresponding 20MHz is divided into any one of the following: [106, -, 52, 52], [52, 52, -, 106], [106, -, 106], [52, 52, -, 52, 52]; wherein [N, M] indicates N-tone RU and M-tone RU, respectively; The second RU is a middle 26-tone RU, and the first RU is a 106-tone RU or a 52-tone RU adjacent to the middle 26-tone RU.

12. The method according to claim 10, characterized in that The resource unit allocation subfield indicates that the corresponding 20 MHz is divided into any one of the following: [26, 26, 26, 26, -, 106], [26, 26, 52, -, 106], [52, 26, 26, -, 106], [106, -, 26, 26, 26, 26], [106, -, 52, 26, 26] or [106, -, 26, 26, 52], where [N, M] indicates N-tone RU and M-tone RU, respectively; The second RU is a middle 26-tone RU, and the first RU is a 106-tone RU adjacent to the middle 26-tone RU.

13. The method according to claim 8 or 9, characterized in that: The user field corresponding to the first RU includes the merging indication; If the merging indication indicates that the first RU and the second RU are merged into a Multi-RU, the Multi-RU is allocated to the user indicated by the user field corresponding to the first RU, and the PPDU also includes a data field, and the data field includes data carried on the Multi-RU.

14. The method according to claim 13, characterized in that The first RU is a 106-tone RU, and the 106-tone RU corresponds to at least two user fields.

15. A device for indicating a multi-resource unit (Multi-RU) merge, characterized in that: The device comprises: a processor and a memory, wherein the memory stores instructions, and when the processor executes the instructions, the device is controlled to execute the method according to any one of claims 8 to 14.

16. A computer-readable storage medium, characterized in that: The computer-readable storage medium includes instructions for executing the method of any one of claims 8 to 14.

17. A computer program product, characterized in that The method comprises instructions, which, when executed on a computer, cause the computer to execute the method according to any one of claims 8 to 14.

Images