Method and terminal for indicating multiple resource units

Abstract

The embodiments of the present invention relate to the field of wireless communication technology, and disclose a method and terminal for indicating multiple resource units. In the present invention, a PPDU sent by a second device is received, or a trigger frame sent by the second device for predetermining the first device to send a triggered physical layer protocol data unit is received; wherein, the PPDU and the trigger frame carry the UHR MCS of the first device; the UHR MCS of the first device includes an MCS indication for indicating at least two RUs allocated to the first device, and the MCS indication of the at least two RUs includes an MCS indication corresponding to a distributed RU and an MCS indication corresponding to a conventional RU. The MCS indication issued can fully utilize the scattered spectrum that appears in the conventional RU due to various reasons, and different RUs use different MCSs to fully demonstrate the gains of the distributed RU brought by frequency diversity and increased transmission power.

Description

Technical Field

[0001] The embodiments of the present invention relate to the field of wireless communication technology, and in particular to a method and terminal for indicating multiple resource units. Background Art

[0002] In the current standard, physical resources are allocated primarily in resource units (RUs). Prior to Wi-Fi 6 (including Wi-Fi 6), a terminal used only one RU. An RU is a set of multiple carriers contiguous in the frequency domain. An RU is defined as a group of 26, 52, 106, 242, 484, 996, or 2×996 subcarriers allocated for transmission. In Wi-Fi 7, a terminal can be allocated one RU or multiple RUs, referred to as multiple resource units (MRUs). An MRU is defined as a group of subcarriers containing multiple RUs, where an RU can be a 26-tone RU, 52-tone RU, 106-tone RU, 242-tone RU, 484-tone RU, 996-tone RU, or 2×996-tone RU.

[0003] To further improve the resource utilization efficiency of terminals, research on distributed resource units (dRUs) has gradually become the mainstream solution for the physical layer of next-generation Wi-Fi standards during discussions on next-generation standards. The subcarriers in a distributed resource unit are not adjacent to each other, but are separated by several subcarriers, with multiple subcarriers allocated to form a comb-like distribution. Signal transmission power is generally specified by spectral density. The number of carriers per unit spectral density in a comb-like distribution is smaller, allowing for higher transmission power. Therefore, the sparse subcarriers in the comb-like distribution can be transmitted with greater transmission power. On the other hand, the dRU can achieve greater frequency diversity gain. These two aspects combined give the distributed resource unit a greater advantage over the general RU.

[0004] The inventors discovered that the main issues discussed in the related art are: 1. How to construct a distributed RU (DRU) pattern with comb-shaped subcarriers; 2. How to coexist with DRUs and reference signals (pilot tones); and 3. How to combine DRUs that occupy a narrower bandwidth to create a DRU that occupies a wider bandwidth.

[0005] Each generation of Wi-Fi is compatible with previous generations. Therefore, when introducing dRUs, compatibility with legacy RUs (also known as regular RUs, also called rRUs) must be considered. For example, a terminal may support both rRUs and dRUs, or a combination of rRUs and dRUs may form a new MRU.

[0006] Because rRUs and dRUs are fundamentally different, dRUs have larger bandwidths, resulting in higher frequency gain. Furthermore, dRUs can transmit at higher power than rRUs. Therefore, when a terminal supports both dRUs and rRUs, different modulation and coding schemes (MCSs) must be applied to each. Furthermore, how to enable rRUs and dRUs to coexist properly as MRUs remains a technical gap in this field. Summary of the Invention

[0007] The purpose of the embodiments of the present invention is to provide a method and terminal for indicating multiple resource units, so that the device can still work normally when the MRU includes both distributed RUs and regular RUs, and indicate various corresponding MCSs for each RU.

[0008] To solve the above technical problems, an embodiment of the present invention provides a method for indicating the MCS of multiple resource units, including: receiving a physical layer protocol data unit PPDU sent by a second device, or receiving a trigger frame sent by the second device for predetermining the first device to send a trigger-based physical layer protocol data unit; wherein the PPDU and the trigger frame carry the ultra-high reliability modulation and coding strategy UHR MCS of the first device; the UHR MCS of the first device includes an MCS indication for indicating at least two RUs allocated to the first device; wherein the at least two RUs include at least one distributed RU and at least one regular RU; the MCS indications of the at least two RUs include an MCS indication corresponding to the distributed RU and an MCS indication corresponding to the regular RU.

[0009] An embodiment of the present invention also provides a terminal, comprising: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to execute the above-mentioned method of indicating multiple resource units.

[0010] An embodiment of the present invention further provides a computer-readable storage medium storing a computer program, which implements the above-mentioned method for indicating multiple resource units when executed by a processor.

[0011] In an embodiment of the present invention, a PPDU sent by a second device is received, or a trigger frame sent by the second device for predetermining the first device to send a triggered physical layer protocol data unit is received; wherein the PPDU and the trigger frame carry the ultra-high reliability modulation and coding strategy UHR MCS of the first device; the UHR MCS of the first device includes an MCS indication for indicating at least two RUs allocated to the first device; wherein the at least two RUs include at least one distributed RU and at least one conventional RU; the MCS indication of the at least two RUs includes an MCS indication corresponding to the distributed RU and an MCS indication corresponding to the conventional RU. The MCS indication issued in the above manner can make full use of the scattered spectrum that appears in the conventional RU due to various reasons, and the use of different MCSs can fully demonstrate the gains of the distributed RU brought by frequency diversity and increased transmission power, and the overall flexibility is greatly improved while taking into account stability. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] One or more embodiments are exemplarily illustrated by pictures in the corresponding drawings. These exemplifications do not constitute limitations on the embodiments. Elements with the same reference numerals in the drawings are represented as similar elements. Unless otherwise stated, the figures in the drawings do not constitute proportional limitations.

[0013] Figure 1 is a flow chart of trigger-based physical layer protocol data unit transmission according to an embodiment of the present invention;

[0014] Figure 2 It is a structural diagram of an electronic device according to another embodiment of the present invention. DETAILED DESCRIPTION

[0015] In order to make the purpose, technical solutions and advantages of the embodiments of the present invention clearer, each embodiment of the present invention will be described in detail below with reference to the accompanying drawings. However, it will be understood by those skilled in the art that in each embodiment of the present invention, many technical details are provided to enable the reader to better understand the present application. However, even without these technical details and various changes and modifications based on the following embodiments, the technical solutions claimed in this application can be implemented. The division of the following embodiments is for convenience of description and should not constitute any limitation on the specific implementation of the present invention. The various embodiments can be combined with each other and referenced to each other under the premise that there is no contradiction.

[0016] An embodiment of the present invention relates to a method for indicating multiple resource units, which can be applied to a first device. The first device here is an electronic device capable of wirelessly communicating with a second device, which can be a terminal device or a station device such as a mobile phone or a computer, or an access point device. In this embodiment, a PPDU sent by a second device is received, or a trigger frame sent by the second device for predetermining the first device to send a triggered physical layer protocol data unit is received; wherein the PPDU and the trigger frame carry the ultra-high reliability modulation and coding strategy UHR MCS of the first device, or called modulation and coding scheme, MCS; the UHR MCS of the first device includes an MCS indication for indicating at least two RUs allocated to the first device; wherein the at least two RUs include at least one distributed RU and at least one regular RU; the MCS indication of the at least two RUs includes an MCS indication corresponding to the distributed RU and an MCS indication corresponding to the regular RU. The MCS indication issued in the above manner can fully utilize the scattered spectrum that appears in the regular RU due to various reasons, and the use of different MCSs can fully demonstrate the gains brought by the frequency diversity and increased transmission power of the distributed RU, thereby greatly improving the overall flexibility while taking into account stability. The following is a detailed description of the implementation details of the method for indicating multiple resource units in this embodiment. The following content is only provided for ease of understanding and is not necessary for implementing this solution.

[0017] The first device will receive the PPDU sent by the second device, or receive a trigger frame (Trigger frame) sent by the second device for soliciting the first device to send a trigger-based (TB) physical layer protocol data unit (TB PPDU for short); wherein the PPDU and the trigger frame carry the ultra-high reliability modulation and coding strategy UHR MCS of the first device, or called modulation and coding scheme, MCS; the UHR MCS of the first device includes an MCS indication for indicating at least two RUs allocated to the first device; wherein the at least two RUs include at least one distributed RU and at least one regular RU; the MCS indication of the at least two RUs includes an MCS indication corresponding to the distributed RU and an MCS indication corresponding to the regular RU. The at least two RUs are called multi-resource units, including a first RU and a second RU, and the MCS indication of the at least two RUs includes a first MCS indication corresponding to the first RU and a second MCS indication corresponding to the second RU.

[0018] Whether it is a terminal or an access point, whether it is the first device on the PPDU receiving side or the second device on the PPDU sending side, supporting multiple resource units (multiple RU, MRU for short) is a capability for the device. A device with this capability can be allocated to use one RU or multiple RUs. Since the various embodiments of this application involve terminals that support multiple resource units, and since the MRU in this application can include both dRU and rRU, this inevitably means that the device's original capability description of supporting multiple resource units needs to be adjusted. In order to understand this application more efficiently, we first give examples of the impact on the capability of supporting multiple resource units in this case and the corresponding improvements.

[0019] In one example, the first device and the second device have the ability to support the multiple resource units to include distributed RUs and regular RUs at the same time. That is, supporting an MRU containing two or more dRUs is a capability of the terminal or access point. For example, one dRU occupies 40MHz bandwidth, and the other dRU occupies 20MHz bandwidth, and they together constitute an MRU. In some cases, the above capabilities have their own capability descriptions, such as using the parameter "SupportMultipledRUasMRU" to indicate support for an MRU containing two or more dRUs. This parameter is 1 for support and 0 for support. The 40MHz bandwidth and 20MHz bandwidth indications here are examples, and other bandwidth values are also applicable.

[0020] In one example, supporting an MRU consisting of DRUs of different sparsity levels is a capability of a terminal or access point. Alternatively, supporting an MRU consisting of DRUs of different patterns is a capability of a terminal or access point. Alternatively, supporting an MRU consisting of DRUs of different compositions is a capability of a terminal or access point, wherein the DRUs in the MRU cannot be generated by the same interleaving method or the same narrowband combination of DRUs. For example, the "SupportMultipleddRUasMRU" parameter indicates support for an MRU consisting of two or more different DRUs. A value of 1 indicates support, and a value of 0 indicates non-support.

[0021] In some cases, an MRU contains two or more RUs, at least one of which is an rRU and at least one of which is a dRU. Supporting this MRU is a capability of the terminal or access point. In some cases, the capability description "SupportrRUanddRUasMRU" indicates support for an MRU containing two or more RUs, one of which is a dRU and the other is an rRU. A value of 1 indicates support, and a value of 0 indicates non-support.

[0022] In some cases, an MRU contains two types of RUs, namely rRU and dRU; wherein the dRU and rRU use their own MCS index (MCS-index) respectively. That is, the rRU and dRU in the MRU are scheduled to apply different MCSs respectively. That is, the ability to apply different MCSs on the distributed RU and the regular RU is applied to the MCS indication corresponding to the distributed RU and the MCS indication corresponding to the regular RU. In some cases, the first device and the second device have the ability to apply different MCSs on the distributed RU and the regular RU contained in the multi-resource unit; that is, supporting the use of different MCSs or MCS-indexes for the rRU and dRU contained in an MRU at the same time is a capability of the terminal. In some cases, the above capability expression "SupportrTwoMCSforMRU" indicates support for an MRU containing two or more RUs, one of which is a dRU and the other is an rRU, and supports two types of MCSs or MCS-indexes. The item is 1 for support and 0 for non-support.

[0023] In some cases, at least one of the above capabilities is mandatory, meaning all Ultra High Reliability (UHR) terminals must support it. In some cases, the above capabilities are optional. In some cases, the above capabilities are mandatory, meaning all UHR terminals must support them.

[0024] In some cases, the capability descriptions above, such as "SupportrRUanddRUasMRU," are illustrative, meaning support or non-support of the capability, or activation or inactivation of the capability. Other descriptions may be used. In some cases, the value of at least one capability described above is not 1 or 0, but true or false, where true indicates support or activation, and false indicates inactivation or non-support.

[0025] In some cases, at least one of the above capabilities is included in a MAC capability element as a subfield, or is a subfield in a PHY capability element, or is in a transmit vector (TxVector), or a receive vector (RxVector), or is in a beacon, or is in a probe response frame, or is included in a management information base (MIB, full name Management Information Base), or is in a probe request frame, or is in a (re)association request frame, i.e., a (re)association response frame, i.e., a (re)association response frame.

[0026] In some cases, at least one capability of the above-mentioned terminal is determined by the terminal itself and reported to the access point. It is not configurable and cannot be changed. In some cases, at least one capability can be configured by the AP, or the configuration can be changed according to the working model of the terminal, or the capability mode of the terminal or the AP. For example, the AP updates the configuration of the capability in the MAC capability element, or the PHYcapabaility element, or the TxVector, or the ReVector, or the Beacon, or the proberesponse frame, or includes it in the MIB, or certain frames, and informs the terminal. The capability can be the AP's own capability configuration update, which is informed to at least one terminal. Or it can be a modification or update of the capability of a certain terminal, and the capability update information is informed to the terminal.

[0027] In some cases, the dRU and rRU are both included in one MRU. If the terminal or its associated access point has "SupportrTwoMCSforMRU" = 0, or is not configured, or has not received the "SupportrTwoMCSforMRU" indication that does not support the use of different MCSs for rRU and dRU, then the dRU and rRU in the MRU can only use the same MCS or MCS-index (meaning the MCS index in the MCS table). Otherwise, if the dRU and rRU are both included in one MRU and the terminal or its associated access point has "SupportrTwoMCSforMRU" = 1, then the dRU and rRU in the MRU can respectively apply different modulation and coding schemes (MCS) or modulation and coding scheme indices (MCS-index).

[0028] In some cases, both dRU and rRU are included in one MRU. If the terminal or its associated access point has "SupportrRUanddRUasMRU" = 0, or is not configured, or has not received "SupportrRUanddRUasMRU", the terminal or access point cannot schedule the use of an MRU that includes both dRU and rRU. Otherwise, if "SupportrTwoMCSforMRU" = 1, the terminal or access point can schedule the use of an MRU that includes both dRU and rRU.

[0029] In some cases, if the terminal or its associated access point "SupportMultipledRUasMRU" = 0, or is not configured, or has not received "SupportMultipledRUasMRU", the terminal or access point cannot schedule the use of an MRU containing multiple dRs. Otherwise, if "SupportMultipledRUasMRU" = 1, the terminal or access point can schedule the use of an MRU containing multiple dRs.

[0030] With the adjustment of the description of the capability of supporting multiple resource units in this application, the implementation details of the method for indicating multiple resource units in this embodiment are specifically described below. Receiving the physical layer protocol data unit PPDU sent by the second device, or receiving the trigger frame sent by the second device for scheduling the first device to send a trigger-based physical layer protocol data unit (TB PPDU), the information interaction process of the first device receiving the physical layer protocol data unit PPDU sent by the second device is relatively simple and will not be described in detail; the process of receiving the physical layer protocol data unit sent by the second device for scheduling the first device to send a trigger-based physical layer protocol data unit is as follows: Figure 1As shown, the first device receives a trigger frame sent by the second device for presetting a trigger-based physical layer protocol data unit (TB PPDU) sent by the first device, and the first device sends the trigger-based physical layer protocol data unit to the second device according to the trigger frame.

[0031] "WiFi 8" is the next generation of WiFi characterized by ultra-high reliability. The Ultra-High Reliability Physical Layer Protocol Data Unit (UHR PPDU) is a physical layer protocol data unit (PPDU) transmitted on this basis. In addition, the physical layer protocol data unit (PPDU) will also be differentiated according to the usage scenario and transmission method. For example, the PPDU can be a multi-user physical layer protocol data unit (MU PPDU for short), which is mainly used for downlink multi-user transmission, or a trigger-based (TB) physical layer protocol data unit (TB PPDU for short).

[0032] In one example, when the PPDU is an ultra-high reliability physical layer protocol data unit (UHR PPDU), and the UHR PPDU is a multi-user physical layer protocol data unit, the UHR MCS of the first device will be carried by the user specific field in the UHR SIG field in the UHR PPDU; in the trigger frame, the UHR MCS of the first device will be carried by the user information field in the trigger frame. It can be seen that whether it is a multi-user physical layer protocol data unit or a trigger frame for a trigger-based physical layer protocol data unit (TB PPDU) scheduled to be sent by the first device, it carries the UHR MCS of the first device, and the UHR MCS of the first device includes an MCS indication for indicating at least two RUs allocated to the first device; wherein the at least two RUs include at least one distributed RU and at least one regular RU. In one example, for UHR MUPPDU, the UHR MCS for each user (terminal) is carried in the user specific field in the UHR SIG. For a trigger-based (TB) physical layer protocol data unit (PDU), the UHR MCS is carried in the User Info field of the TB PPDU specified in the trigger frame. In some cases, the UHR MCS is indicated by at least two MCSs, one for each dRU and one for each rRU. In some cases, the dRU and the rRU are included in a single MRU. In some cases, the dRU and the rRU are not included in a single MRU but are assigned to a single terminal.

[0033] In addition, when the first device and the second device perform link adaptation, in order to enable the rRU and dRU to coexist normally in the form of MRU, the link adaptation method should also be adjusted. Link adaptation is also called link adaptation or connection adaptation. When this function includes a high efficiency (HE) variant control field (HE variant control field is called HE variant control field) in the protocol data unit (PPDU), the MFB Requester (MFB request means MFB request, MRQ is the abbreviation of MFB requester, MFB is the abbreviation of MCSfeedback, MCS is the abbreviation of Modulation and Coding Scheme, MCS is Modulation and Coding Scheme) can be used. The implementation process of link adaptation is to request MCS estimation (estimate which specific MCS in the MCS table is the best in the current environment) through the MRQ field in the HE variant control field. The MFBResponder (MFB responder) can use the MFB field in the HE variant control field to provide the requested MCS estimate. Future Wi-Fi systems will include link adaptation functionality, known as ultra-high reliability link adaptation (ULA). The corresponding control field can be formatted as the Control Information subfield in the ULA Control subfield format.

[0034] To enable the first device and the second device to normally perform ultra-high reliability link adaptation, the first device may receive a request for MCS estimation initiated by the second device via the MRQ field carried in a UHR PPDU (which may be in the HE variant control field); the first device may provide the MCS estimation requested by the second device by sending a response (which may be carried in the HE variant control field) using the MFB field, thereby achieving ultra-high reliability link adaptation between the first device and the second device.

[0035] The control information subfield in the control subfield corresponding to the ultra-high reliability link adaptation (ULA control subfield) includes information about the UHR link adaptation step. Specifically, the control information subfield in the control subfield corresponding to the ultra-high reliability link adaptation includes at least one of the following or any combination thereof:

[0036] 1. The rRU / dRU subfield is used to indicate whether the current at least two RUs include a distributed RU. It can be defined as: Set to 0 if the control information field, the RU Allocation subfield and the PS160 jointly indicate the rRU or MRU (multiple rRU) to which the recommended UHR-MCS applies. In English, it is expressed as "Set to 0if the control information field, the RU Allocation subfield and the PS160 jointly indicate the rRU or MRU (multiple rRU) to which the recommended UHR-MCS applies". It can be used to indicate that the current MRU does not include a dRU. Set to 1 if the control information field, the RU Allocation subfield and the PS160 jointly indicate the dRU or MRU (multiple dRU) to which the recommended UHR-MCS applies. In English, it can be used to indicate that the current MRU includes a dRU.

[0037] 2. Indication used to indicate whether the current operation is performed as an ultra-high reliability (UHR) device or a high throughput (HT) device. This indicates whether the current operation is UHR link adaptation or HT link adaptation. This indication is called the ULA / HLA subfield and can be defined as 1 to indicate operation as a UHR device. Setting it to 0 indicates operation as a high throughput device.

[0038] 3. An indication of whether the current operation is performed as an ultra-high reliability device, which corresponds to whether the current operation is UHR link adaptation. This indication is called the ULA subfield and can be defined as 1 to indicate that it is operating as a UHR device and 0 to indicate that it is reserved.

[0039] 4. An indication of whether the current operation is performed as an Extreme High Throughput (EHT) device or an ultra-high reliability device, which corresponds to whether the current operation is performed as UHR link adaptation or EHT link adaptation. This indication is called the ELA / ULA subfield and can be defined as 1 to indicate operation as a UHR device and 0 to indicate operation as an EHT device.

[0040] 5. The first MCS indication corresponding to the first RU is the UHR-MCS recommended for the first RU in the MRU. If it is not an MRU and there is only one RU, it is the UHR-MCS recommended for this RU. Named UHR-MCS1, it can be defined as; "If the unsolicited MFB subfield is equal to 1 and the MRQ / UL UHR TB PPDU MFB subfield is equal to 0, or if the unsolicited MFB subfield is equal to 0 and the MRQ / UL UHR TB PPSU MFB subfield is equal to 0, the UHR-MCS subfield indicates the recommended UHR-MCS for the subsequent UHR MU PPDU sent to the STA that issued the recommendation, and is set to the UHR-MCS1 index. If the unsolicited MFB subfield is equal to 1 and the MRQ / UL UHR-TB PPDU MFB subfield is equal to 1, the UHR-MCS1 subfield indicates the recommended UHR-MCS for the UHR-TB PPDU sent from the STA, and is set to the UHR-MCS index." The definition is expressed in English as: "If the Unsolicited MFB subfield is equal to 1and the MRQ / UL UHR TB PPDU MFBsubfield is equal to 0or if the Unsolicited MFB subfield is equal to 0and theMRQ / UL UHR TB PPDU MFB subfield is equal to0,the UHR-MCS subfield indicates the recommended UHR-MCS for subsequent UHR MU PPDU(s)sent to the STA that isissuing this recommendation,and is set to the UHR-MCS1 index.

[0041] 6. The second MCS indication corresponding to the second RU is the recommended UHR-MCS for the second RU in the MRU. Named UHR-MCS2, it can be defined as an optional subfield if the MRU contains rRU and dRU, or only rRU, or only dRU. The above-mentioned UHR-MCS1 is recommended for the first RU or the first part of RU in the MRU. UHR-MCS2 is recommended for the second RU or the second part of RU in the MRU. The first part of RU is rRU and the second part of RU is dRU. Alternatively, the first part of RU is dRU and the second part of RU is rRU.

[0042] When the above information exists in the control information subfield in the ULA control subfield, an example of the format of the control information subfield in the ULA control subfield (Control Information subfield format in an ULA Control subfield) is shown in Table 1 below:

[0043]

[0044] In the table, B represents the bit number of the ULA control subfield. For example, B5 to B8 indicate that the four bits occupy bits 6 to 9 of the 32 bits. The values of the other Bs in the table are similar.

[0045] In some cases, in the subfield represented by label B31 (representing the 32nd binary bit) in Table 1, HLA / ULA is the above-mentioned indication for indicating whether the current work is performed as an ultra-high reliability (UHR) device or as a high throughput (HighThroughput, HT) device, or is an indication for indicating whether the current work is performed as an ultra-high reliability device.

[0046] In one example, the BW (bandwidth) field in the control information subfield of the ULA control subfield is described as being associated with a recommended UHR-MCS / bandwidth, at which the MFB (MCS feedback) requester has reserved feedback. The bandwidth field in the control information subfield of the ULA control subfield has a width of three bits, with three different reserved bit values used to indicate the bandwidth to support puncturing by the first device. For example, the BW field has a width of three bits, with reserved bit values of 5, 6, and 7. To protect existing systems, puncturing is performed, where a portion of the Wi-Fi device's bandwidth is punctured, meaning that no signal is transmitted or received. Therefore, when transmitting a DRU, puncturing is supported at 80 MHz. Therefore, in some cases, when the total bandwidth is 80 MHz, the reserved bit value indicating the bandwidth is 5: 20 MHz + 20 MHz + 40 MHz, and 6: 40 MHz + 20 MHz + 20 MHz. Other numerical combinations such as 5, 6, and 7 are selected to indicate the above bandwidth conditions, which are also described in detail and will not be repeated here.

[0047] If an MRU contains both rRUs and dRUs, their various combinations may be pre-designed and listed in a table. In some cases, this method is applied to a UHR frame exchange sequence containing a PPDU containing a HE variant HT control field, or to a UHR link adaptation frame exchange sequence containing a PPDU containing a HE variant HT control field.

[0048] The UHR MAC Capabilities Information field contains the UHR Link Adaptation Support subfield. A UHR station (STA) shall set the UHR Link Adaptation Support subfield in the UHR MAC Capabilities Information field of its transmitted UHR Capabilities element to the value of "dot11UHRMCSFeedbackOptionImplemented".

[0049] In one example, at least two RUs include a first RU and a second RU, and the MCS indications of the at least two RUs include a first MCS indication corresponding to the first RU and a second MCS indication corresponding to the second RU; the second MCS indication corresponding to the second RU is used to indicate an offset, and the offset will be used to obtain the MCS index of the second RU after the first MCS indication corresponding to the first RU is applied. For example, in some cases, UHR-MCS1 follows the current EHT-MCS setting. For the above-mentioned UHR-MCS2, in some cases, UHR-MCS2 does not specifically indicate an MCS index, or UHR-MCS index, but indicates an offset. This offset, after acting on UHR-MCS1, represents the MCS index of UHR-MCS2, which is used to indicate the MCS index acting on the second RU in the MRU, or the MCS index acting on the second part of the RU in the MRU. The offset will obtain the MCS index of the second RU after the first MCS indication corresponding to the first RU is applied, which can be: MCS index of UHR-MCS2 = MCS index of UHR-MCS1 + the offset; or MCS index of UHR-MCS2 = MCS index of UHR-MCS1 - the offset; or the offset is 4 bits, where the first bit on the left indicates positive or negative, 1 indicates negative, 0 indicates positive, and the remaining three bits indicate numerical values. This is just an example, and the offset can be another number of bits; or the offset is 4 bits, indicating a positive integer, used for the offset value. Additional signaling indicates adding or subtracting the offset. This is just an example, and the offset can be another number of bits. For those cases where there is no second MCS indication, in some cases the offset is not configured, or the offset is a fixed value, such as 0, or 15, indicating that there is no MCS that acts solely on the second RU in the MRU. The second RU in the MRU and the first RU of the MRU use the same MCS index.

[0050] In one example, the MCS indication carries multiple MCS index recommendation values corresponding to the RU. The MCS index recommendation value will be used as a recommended value to influence the selection result when selecting the corresponding MCS index for the RU. For example, in some cases, the MCS index indicated in the above UHR-MCS1 or UHR-MCS2 is only a suggestion or a recommended value. The device that receives the MCS index can adopt other MCS index values. Or if two MCS index values are recommended, the device that receives the MCS index can only use the same MCS for the MRU. In some cases, the MCS index indicated in the above UHR-MCS1 or UHR-MCS2 is a suggestion or a recommended value. The device that receives the MCS index must adopt other MCS index values. Or if two MCS index values are recommended, the device that receives the MCS index can only use the corresponding one MCS for each RU in the MRU. In some cases, the MCS index indicated in the above UHR-MCS1 or UHR-MCS2 is a suggestion or a recommended value. Whether the device that receives the MCS index can adopt (or use, or apply) other MCS index values is configurable. This bit exists in the control information subfield of the ULA control subfield. If it is 1, it is mandatory; if it is 0, it is not mandatory.

[0051] The following examples illustrate some field definitions in link adaptation. The HLA / ULA subfield shall be set to 1 to indicate that theControl Information subfield is an ULA Control subfield and shall be set to 0 to indicate that the Control Information subfield is an HLA Control subfield. The English expression is: “The HLA / ULA subfield shall be set to 1to indicate that theControl Information subfield is an ULA Control subfield and shall be set to0to indicate that the Control Information subfield is an HLA Controlsubfield”. The ULA / ELA subfield shall be set to 1to indicate that the control information subfield is an UHRcontrol subfield and shall be set to 0to indicate that the controlinformation subfield is an ULA subfield”. The English expression is: “The ULA / ELA subfield shallbe set to 1to indicate that the control information subfield is an UHRcontrol subfield and shall be set to 0to indicate that the controlinformation subfield is an ULA subfield”. The ULA subfield shall be set to 1 to indicate that the control information subfield is a UHRcontrol subfield and the value 0 is reserved. The English statement is: "The ULA subfield shall be set to 1 to indicate that the control information subfield is a UHR control subfield and vlaue 0 is reserved." The MFB requester can set the MRQ / ULUHR TB PPDU MFB subfield to 1 and the Unsolicited MFB subfield to 0 in the ULA control subfield of the frame to request the STA to provide link adaptation feedback. In each request, the MFB requester shall set the MSI field to a value between 0 and 6. For the MFB requester, how to choose the MSI value is implementation-dependent.The English statement is: “The MFB requester may set the MRQ / UL UHRTB PPDU MFB subfield to 1and Unsolicited MFB subfield to 0in the ULA Control subfield of a frame to request a STA to provide link adaptation feedback. Ineach request, the MFB requester shall set the MSI field to a value rangingfrom 0to 6. For the MFB requester, how to choose the MSI value is implementation dependent”. The receiver shall interpret more than one instance of anULA Control subfield with the MRQ / UL EHT TB PPDU MFB subfield equal to 1andUnsolicited MFB subfield equal to 0within a single PPDU shall be interpreted by the receiver as a single request for link adaptation feedback”. The English statement is: “The appearance of more than one instance of anULA Control subfield with the MRQ / UL EHT TB PPDU MFB subfield equal to 1andUnsolicited MFB subfield equal to 0within a single PPDU shall be interpreted by the receiver as a single request for link adaptation feedback”. If the values are the same, it is considered a single request for link adaptation feedback. If the values are different, for example, if some are rRUs and some are dRUs, they are replied to separately or in a single frame. In addition, the MFB requester should specify the RU type, rRU or M-rRU index, dRU or M-dRU index, and bandwidth for the link adaptation feedback request.The English expression is: "The MFB requester shall specify the RU type, rRU or M-rRU index, dRU, or M-dRU index and bandwidth requesting the link adaptation feedback".

[0052] In some cases, the 802.11 standard defines a resource unit (RU). All carriers occupying a portion of a frequency band (or contiguous carriers, excluding the pilot tone for channel estimation and the DC component) are called regular resource units (rRUs). Distributed resource units (dRUs) are called distributed resource units. These units select a tone every few signals (tones), or a carrier every few OFDM (Orthogonal Frequency Division Multiplexing) carriers, resulting in a comb-like distribution in the frequency domain. Multiple dRUs can be interleaved.

[0053] The specific MFB requester should specify the specific RU type, whether it is rRU, M-rRU, dRU, or M-dRU, and the bandwidth. Among them, M-rRU is multiple general resource units, that is, MRU. M-dRU is multiple distributed resource units. In some cases, M-rRU and M-dRU are collectively referred to as MRU. In some cases, the bandwidth is the working bandwidth of the device, and in some cases, the bandwidth is the bandwidth occupied by dRU. For example, in some cases, the device operates at 80MHz, but the allocated dRU is only 40MHz. The above bandwidth indicates the bandwidth occupied by dRU, which is 40MHz.

[0054] In some cases, an M-RU contains at least one rRU or dRU. In some cases, the bandwidth is the working bandwidth of the device or the bandwidth occupied by the MRU.

[0055] The PPDU carrying the MRQ (MCS request) should contain the rRU or MRU, or dRU, used to obtain the MFB (MCS feedback), where the MRU can include the rRU and dRU.

[0056] The STA that receives the MFB may use the received MFB to calculate an appropriate UHR-MCS or Nss (number of spatial streams) for the rRU, dRU, or each rRU and dRU (which may be included in the MRU).

[0057] The unsolicited UHR-MCS, NSS, bandwidth, and RU or MRU, or dRU estimates reported in an ULA Control subfield sent by a STA are computed based on the most recent PPDU received by the STA that matches the description indicated by the PPDU format, Tx Beamforming, and Coding Type subfields and RU type in the same ELA Control subfield, where MRU at least contains one of {rRU or dRU}.

[0058] In the unsolicited MFB response, the PPDU format, coding type, and Tx beamforming subfields are set based on the RXVECTOR parameter of the received PPDU. The UHR-MCS, RU or MRU, or dRU, or RU type, bandwidth, and NSS are estimated from these parameters as follows: The RU or MRU subfield and the PS160 subfield together indicate a regular RU or M-rRU to which the recommended EHT-MCS applies. The dRU or M-dRU subfield and the PS160 subfield together indicate a dRU or M-dRU to which the recommended UHR-MCS applies. The recommended RU or MRU or dRU should be part of a dRU or within the RU or MRU or dRU bandwidth or bandwidth of the received EHT PPDU. The RU Type subfield indicates whether the recommended rRU type is a dRU or rRU to which the recommended UHR-MCS applies. A value of 0 indicates an rRU, and a value of 1 indicates a dRU.Note:“In an unsolicited MFB response,the PPDU Formats,CodingType,and Tx Beamforming subfields are set according to the RXVECTORparameters of the received PPDU from which the UHR-MCS,RU or MRU,or dRU,or RUtype,bandwidth,and NSS are estimated,as follows:--The RU or MRU subfield andthe PS160 subfield jointly indicate the regular RU or M-rRU to which therecommended EHT-MCS is applied orwithin an RU or MRU or a dRU bandwidth or a bandwidth in which the receivedEHT PPDU is located.--Value 0indicatesrRU,and Value 1indicates dRU”.

[0059] In the case of snowflakes, RU snowflakes(RU type field)Specify a list of MFQs or PPDUs in RU fields.

[0060] For either a solicited or an unsolicited response, the recommended UHR-MCSand NSS subfields of the ULA Control subfield shall be selected from the UHR-MCS and NSS set supported by the recipient STA or by the tranmitting STA,orby both the receiving STA and the transmitting STA".

[0061] The UHR-MCS1 or UHR-MCS1 subfield and UHR-MCS2 subfield of the ULAControl subfield may be used to obtain a suitable transmission rate, based on the PPDU of the RXVECTOR used for MFB estimation, wherein the data rate achieves an estimated frame error rate of 10% or less for an MPDU of 3895 octets length.

[0062] A non-access point UHR STA may set the Unsolicited MFB subfield to 1 and the MRQ / UL UHR TB PPDU MFB to 1 in the ULA Control field it sends to the AP to indicate that the NSS, UHR-MCS, bandwidth, and RU allocation in the ULA Control field represent the recommended MFB for subsequent UHR TB PPDUs sent by the STA issuing the recommendation. When the AP sends a trigger frame addressed to a STA, the AP shall not exceed the recommended RU or MRU size or dRU size or dRU bandwidth indicated in the most recently received RU allocation and the PS160 subfield and / or the RU Type field of the ULA Control field. The English expression is: "A non-AP UHRSTA may set the Unsolicited MFB subfield to 1and the MRQ / UL UHR TB PPDU MFB to 1in the ULA Control field it transmits to the AP to indicate that the NSS,UHR-MCS,bandwidth,and RU allocation in the ULA Control field represent therecommended MFB for subsequent UHR TB PPDU(s)sent by the STA that is issuing this recommendation.The AP should not exceed the recommended RU or MRU size or dRU size,or dRU bandwidth indicated in the most recently received RUAllocation and PS160 subfield and / or the RU type field of the ULA Controlfield when it sends a triggering frame addressed to the STA".

[0063] In some cases, a device is allocated at least one dRU resource and at least one rRU resource, but is not called an MRU. The method disclosed in this invention can still be used to indicate the MCS of the corresponding rRU and dRU. In some cases, the method disclosed in this invention is not limited to UHR devices. Future Wi-Fi devices that use multiple RUs can also apply the method disclosed in this invention.

[0064] Next, the signaling indications during uplink and downlink transmission, such as the signaling indications during uplink and downlink transmission between a terminal or station device (STA) and an access point device (AP), are discussed separately. The signaling indications during uplink and downlink transmission are also divided into two types. For UHR MU PPDU, the UHR MCS for each user (terminal) is carried in the user-specific field in the UHR SIG. For the trigger-based (trigger based, abbreviated as tb) physical layer protocol data unit UHR TB PPDU, the UHR MCS is carried in the user information field user Info field in the UHR TB PPDU predetermined in the trigger frame. In some cases, the above-mentioned UHR MCS is at least two MCS indications, which are applied to the corresponding dRU and rRU respectively. In some cases, the dRU and the rRU are included in one MRU. In some cases, the dRU and the rRU are not included in one MRU, but are only assigned to one terminal.

[0065] For the user data indication in the SIG in the UHR MU PPDU, the User Specific field needs to be modified as follows:

[0066] The SIG (Signal Field) field may be called the UHR SIG field in future Wi-Fi implementations. The user-specific field of the UHR SIG field, used to indicate the MCS indication of at least two RUs allocated to the first device, includes multiple user fields. These multiple user fields are used to determine the MCS index and beamforming parameters of the at least two RUs allocated to the first device. These multiple user fields are transmitted over the full bandwidth of the payload PPDU, only on the primary channel bandwidth of the payload PPDU, or only on the temporary primary channel bandwidth of the payload PPDU.

[0067] In some cases, the User SIG field (U-SIG) in the UHR SIG field overflows, and 80MHz OFDMA uses MUPPDU transmission for MU-MIMO data. In some cases, the User Specific field in the UHR SIG field contains information (STA-ID, MCS, Coding, Spatial Configuration). In some cases, the specific value assigned to the user field includes the terminal STA-ID 1441, UHR-MCS10, LDPC (Low-density Parity-check), and no Tx beamforming (no Tx beamforming), indicating that the STA-ID is 1441, the MRU (484+242-tone MRU 2 (242-[gap 242]-484)) modulation and coding scheme is UHR-MCS10. The specific parameters can be found in the table. The coding scheme is LDPC, and there is no transmit beamforming. SS0: Indicates that spatial stream 0 is the first spatial stream. SS1: Indicates that spatial stream 1 is the second spatial stream. For devices with STA ID 1442, the following applies: STA-ID 1442, 242-tone RU 2, modulation and coding scheme UHR-MCS 4, BCC coding, 2SS transmitted over two spatial streams, with transmit beamforming.

[0068] In some cases, a terminal is assigned an MRU that contains two types of RUs, namely dRU and rRU. The terminal is instructed to act on at least two MCSs, one on the dRU and the other on the rRU. For example, the UHR SIG field contains two user fields whose STA-ID is 1441, as shown in Table 2 below:

[0069]

[0070] The first user field is: STA-ID 1441, UHR-MCS 9, LDPC, no Tx beamforming; the second user field is: STA-ID 1441, UHR-MCS10, LDPC, no Tx beamforming. The 484+242-tone MRU 2 (242-[gap 242]-484) contains two RUs: one RU using 484-tone (dRU) and one RU using 242-tone (rRU). The dRU and rRU use different MCSs: the dRU uses UHR-MCS10, and the rRU uses UHR-MCS9. Note that 484-tone is just a name for the dRU and does not mean that the future dRU will actually contain 484 subcarriers or that the dRU will occupy 40 MHz of bandwidth. The 242-tone RU here means that the RU occupies 20 MHz of bandwidth. The dRUs in the MRU are ordered in the frequency domain, or in order of precedence. For example, a 484+242-tone MRU 2 (242-[gap 242]-484) contains two RUs: the 484dRU is in a slightly lower frequency band, and the 242 is in a slightly higher frequency band for the rRU. This creates a low-to-high order. The STA fields in the received UHR SIG field also follow a precedence order. For example, if the content {STA-ID1441, UHR-MCS10, LDPC, no Tx beamforming} is received first, it corresponds to the 484dRU. If the content {STA-ID1441, UHR-MCS9 LDPC, no Tx beamforming} is received later, it corresponds to the 242rRU.

[0071] In some cases, when the MRU contains multiple rRUs or dRUs, a corresponding user field can be transmitted to each dRU or rRU to determine its modulation coding and beamforming parameters. That is, multiple user fields can be transmitted to a terminal in the UHR-SIG, corresponding to the parameters of different RUs in the MRU. In some cases, only two user fields are transmitted, one corresponding to the dRU in sequence and the other corresponding to the rRU in sequence to a terminal. In some cases, all the user fields are transmitted on the entire bandwidth of the loaded PPDU. In some cases, all the userfields in the UHR-SIG are transmitted only on the main channel bandwidth of the loaded PPDU. In some cases, all the user fields are transmitted only on the temporary main channel bandwidth of the loaded PPDU, such as in the case of slave channel access.

[0072] In some cases, the user field is transmitted only within the bandwidth of the PPDU that carries the user field information. For example, {STA-ID 1441, UHR-MCS10, LDPC, no Tx beamforming} is transmitted only within the 40 MHz bandwidth occupied by the 484-tonedRU to STA-ID 1441. {STA-ID 1441, UHR-MCS 9LDPC, no Tx beamforming} is transmitted only within the 20 MHz bandwidth occupied by the 242-tone rRU to STA-ID 1441.

[0073] In some cases, the user encoding block in the user field of the UHR-SIG contains at least one user field of a terminal. Each user field corresponds to the transmission mode of an RU in the MRU, such as modulation and coding, and whether beamforming is used. In some cases, the user encoding block in the UHR-SIG contains all the parameters of the user field in the user field of a terminal, such as all the parameters in the MU-MIMO case (STA-ID, MCS, Coding, Spatial Configuration). Of course, the same applies to the SU case and the non-OFDMA case.

[0074] In some cases, the user encoding block in the UHR-SIG contains at least one user field for a terminal. Partial parameters of the user field in the user field of one terminal, such as at least the STA-ID and MCS, or at least the MCS, are included. As shown in the following table, one user field contains the complete information {STA-ID 1441, EHT-MCS10, UHR-MCS 9, LDPC, no Tx beamforming}, while the other user field only contains {UHR-MCS10}. The combination is shown in Table 3.

[0075]

[0076] In some cases, such as single-user transmission (UHR SU transmission), the UHR-SIG content includes at least one User field for the terminal scheduled to the MRU, where the User field is included in the common encoding block. Multiple User fields are applied to the corresponding RUs. For example, the dRU in the MRU uses the MCS in its corresponding User field, and the rRU in the MRU uses the MCS in its corresponding User field.

[0077] It is worth noting that the above design of the user field of MRU is also applicable to non-MU-MIMO allocation, such as TB-PPDU, and will not be repeated here.

[0078] Next, the User Info field in the trigger frame is modified. The trigger frame now includes RU allocation and uses the UL MCS to determine the modulation and coding scheme. This is shown in Table 4 below:

[0079]

[0080] For the case where the MRU contains two types of dRU and rRU, we can reuse the trigger dependent user information field. In one example, the MCS indication for indicating at least two RUs allocated to the first device in the user information field in the trigger frame includes a first uplink MCS indication field, a reserved field, and a trigger dependent user information field; the first uplink MCS indication field is used to indicate the MCS of the regular RU allocated to the first device; the reserved field is used to indicate whether there are both distributed RUs and regular RUs in at least two RUs; the trigger dependent user information includes a second uplink MCS indication field; the second uplink MCS indication field is used to indicate the MCS of the distributed RU allocated to the first device.

[0081] Specifically, UL MCS2 can be included in the Trigger-Dependent User Info. In Tables B21 to B24 above, the UL MCS, or including B25 DCM, collectively indicates the MCS of the first RU of the MRU indicated in the RU Allocation. In this case, the UL MCS can be referred to as UL UHR-MCS1. The indicated second MCS, UL UHR-MCS2, is included in the Trigger-Dependent User Info.

[0082] In some cases, or using the joint indication of the B39 reserved field, B39=1 means that when the MRU contains dRU and rRU, two MCSs are used and applied to the dRU and rRU respectively. And the second MCS, UL UHR-MCS2, is in the Trigger dependent user info. B39=0 means that two MCSs are not used for simultaneous transmission and only B21 B24, UL MCS or MCS containing B25 DCM joint indication are used on the MRU / RU indicated by RU Allocation. Among them, UL LUHR-MCS1 and UL UHR-MCS2 are applied to multiple RUs in the MRU in a certain order, such as from high frequency to low frequency, UL UHR-MCS1 corresponds to the relatively high-frequency RU in the MRU, and UL UHR-MCS2 corresponds to the relatively low-frequency RU in the MRU; or from low frequency to high frequency.

[0083] In some cases, the MCS indication in the user info field is applied according to the type. UL UHR-MCS1 indicates the MCS of the rRU in the MRU, and UL UHR-MCS1 is applied to the rRU in the MRU. UL UHR-MCS2 indicates the MCS of the dRU in the MRU, and UL UHR-MCS2 is applied to the dRU in the MRU, or in the reverse order.

[0084] In some cases, a trigger frame may contain multiple User Info fields for the same terminal (with the same AID 12). These fields are applied to multiple RUs in the MRU in the order they were received, such as from high frequency to low frequency, or from low frequency to high frequency. Alternatively, the first received User Info field is applied to the rRU in the MRU, and the second received User Info field for the same terminal is applied to the dRU in the MRU, or vice versa.

[0085] In some cases, the above method is not limited to the UHR-SIG of Wi-Fi 8. In the future, any MRU containing multiple RUs can apply the above method.

[0086] In one example, the terminal responds to the UHR TB PPDU of the trigger frame. The MCS parameter of the dRU in the MRU is set to the value of the UL UHR-MCS2 subfield in the User Info field of the trigger frame. The MCS parameter of the rRU in the MRU is set to the value of the UL UHR-MCS1 subfield in the User Info field of the trigger frame.

[0087] In addition, in some cases, it may be necessary to recreate the MCS table. For example, in the trigger frame, one user corresponds to one user info field, or in the UHR-SIG, one terminal only contains one user field. However, when the MRU allocated by the access point to the terminal includes rRU and dRU, the corresponding modulation mode table contains two modulation modes, which are applied to dRU and rRU respectively. In other words, when the MRU allocated in the user info field or UHR-SIG includes rRU and dRU, an MCS table is used to list the various possibilities of the MCS used by the rRU and the dRU, and the number is used as the MCS-index to indicate the MCS-index. The MCS index corresponds to the respective MCSs in the new MCS table that are applied to the rRU and the dRU in the MRU.

[0088] Regarding the offset mentioned above, a further detailed description is given here. In some cases, the method including at least two MCS indications in the above method does not use at least two, or at least two sets of MCS indications about RU. Instead, an original MCS indication is used, and the other indication is an offset about the original indication. Because the dRU and rRU of a terminal use the same channel for transmission, the MCS of the dRU is not much different from the MCS of the rRU. This difference is the offset. In some cases, the offset is represented by binary code 0001, which means a forward offset of one MCS-index, that is, the MCS-index of the original indication is added by one. 1001 means a reverse offset of one MCS-index, that is, the MCS-index of the original indication is subtracted by one. Two examples are given below to illustrate. In the first example, a user encoding block in the UHR-SIG contains the parameters (STA-ID, MCS, Coding, SpatialConfiguration) of the first user field indicating the MU-MIMO situation, which is applied to the first part of the RU in the MRU. Another user field carries an offset relative to the MCS in the first user field, which can be represented by binary coding or bitmap. The offset is applied to the second part of RUs in conjunction with the parameter (MCS) of the first user field. The first part of RUs is rRU and the second part of RUs is dRU. Or the first part of RUs is dRU and the second part of RUs is rRU. In the second example, the User Info field in the trigger frame contains the UL MCS indicating the MCS of the first part of RUs in the corresponding RU allocation, which is applied to the first part of RUs in the MRU indicated by RUallocation. Trigger Dependent User info carries an offset relative to the UL MCS, which can be represented by binary coding or bitmap. The offset is applied to the second part of RUs in conjunction with the parameter (MCS) of the UL MCS. The first part of RUs is rRU and the second part of RUs is dRU. Or the first part of RUs is dRU and the second part of RUs is rRU. In some cases, the offset can be jointly indicated by Trigger Dependent User info and the B39 reserved bit.

[0089] The case where the first RU is a dRU and the second RU is also a dRU will be explained through the following examples: In one example, a user encoding block in the UHR-SIG contains the first user field indicating the parameters (STA-ID, MCS, Coding, Spatial Configuration) of the MU-MIMO situation, which is applied to the first part of RUs in the MRU. Another user field carries MCS, which is applied to the second part of RUs in the MRU. The first part of RUs is a dRU and the second part of RUs is a dRU. When the first RU and the second RU are both distributed RUs, the first RU and the second RU have different patterns, or different sparsity, or different bandwidths, or different compositions. In one example, the User Info field in the trigger frame contains the UL MCS indicating the MCS of the first part of RUs in the corresponding RU allocation, which is applied to the first part of RUs in the MRU indicated by the RU allocation. The Trigger Dependent Userinfo carries MCS information and is applied to the second part of RUs. The first part of RUs is a dRU and the second part of RUs is a dRU. The two parts of dRU have different patterns, or different sparsity, or different bandwidths, or different configurations. In some cases, the offset can be jointly indicated by Trigger Dependent User info and B39 reserved bit. In one example, a user encoding block in UHR-SIG contains parameters (STA-ID, MCS, Coding, Spatial Configuration) indicating the MU-MIMO situation in the first user field, which is applied to the first part of RU in the MRU. Another user field carries an offset relative to the MCS in the first user field, which can be represented by binary coding or bitmap. The offset is applied to the second part of RU in conjunction with the parameter (MCS) of the first user field. The first part of RU is a dRU, and the second part of RU is also a dRU. The two dRUs have different patterns, or different sparsity, or different bandwidths, or different configurations. In one example, the User Info field in the trigger frame contains a UL MCS indicating the MCS of the first part of RU in the corresponding RU allocation, which is applied to the first part of RU in the MRU indicated by RU allocation.The Trigger Dependent User Info carries an offset relative to the UL MCS, which can be represented by binary encoding or bitmap. This offset is applied to the second RU in conjunction with the UL MCS parameter (MCS). The first RU is a dRU, and the second RU is a dRU. The two dRUs have different patterns, or different sparsity, or different bandwidths, or different configurations. In some cases, the offset can be jointly indicated by the Trigger Dependent User Info and the B39 reserved bit.

[0090] In some cases, the above scheme is applicable to SU PPDU or ER (Extended Range) SU PPDU, and at least one MCS indication (multiple MCS indexes, or offset-based) applied to the MRU is included in the User field.

[0091] In some cases, the AP has energy-saving capabilities, and this capability is enabled. The AP can operate in high-capacity mode or low-capacity mode. When the AP sends an ICF (initial control frame) containing AP energy-saving information or a beacon containing AP energy-saving information to the terminal, the terminal does not make corresponding adjustments based on the AP's energy-saving information. The ICF (initial control frame) and beacon play the role of advertisement (notification). In some cases, the terminal plays a configuration role based on the ICF (initial control frame) or beacon. At this time, the terminal makes corresponding adjustments based on the ICF (initial control frame) or beacon. For example, the working bandwidth, the number of spatial streams, the frame format, and the enablement or disablement of a certain connection. In some cases, the ICF (initial control frame) or beacon contains a timer or time indication, indicating that the AP will adjust the working mode after a period of time (the indicated time, or when the timer is 0, or after a certain number of TBTTs), and the terminal needs to make adjustments after this time point. In some cases, the terminal needs to make adjustments before this time point.

[0092] In some cases, the ICF is a trigger frame containing AP energy saving information (trigger frame). In some cases, the ICF is a MU-RTS trigger frame containing AP energy saving information.

[0093] In some cases, AP energy-saving information refers to the capability mode of the AP, including at least one of the following: working bandwidth, number of spatial streams, MCS, frame format, connection enable / disable, wake-up / sleep interval (period), and data rate. In some cases, the capability mode of the AP refers to the maximum value of at least one of the above items supported in the corresponding mode. For example, the maximum working bandwidth and the maximum number of spatial streams supported in a certain working mode. In some cases, the ICF or beacon contains a bit indicating that the current AP energy-saving information is used for announcement (the bit is 1) or configuration of the receiving terminal (the bit is 0). In some cases, the IFC contains two groups of AP energy-saving information, one group for announcing the current capability mode of the AP (notification), and one group for configuring the corresponding parameters of the current terminal at this time (configuration).

[0094] In some cases, if the terminal's operating mode, as determined by the ICF or beacon, exceeds or exceeds the AP's energy-saving information, the terminal will make adjustments. Otherwise, the terminal will not make adjustments. For example, if the terminal currently operates at 160MHz bandwidth, the AP will adjust its capability mode to operate at 80MHz. If the terminal receives the corresponding beacon or ICF, the operating bandwidth will be adjusted to 80MHz. For other terminals operating at, for example, 40MHz, no adjustments will be made.

[0095] In some cases, the AP is attached to a multi-link device. In some cases, the ICF frame includes at least one of the following: operating bandwidth, number of spatial streams, MCS, frame format, connection enable / disable, wake-up / sleep interval (period), and data rate. Certain parameters of the ICF frame are unicast, multicast, or broadcast. Alternatively, at least one of the above parameters may be included in a beacon or probe response frame.

[0096] In this embodiment, a PPDU sent by a second device is received, or a trigger frame sent by the second device for predetermining the first device to send a triggered physical layer protocol data unit is received; wherein, the PPDU and the trigger frame carry the ultra-high reliability modulation and coding strategy UHR MCS of the first device, or called the modulation and coding scheme (MCS); the UHRMCS of the first device includes an MCS indication for indicating at least two RUs allocated to the first device; wherein, the at least two RUs include at least one distributed RU and at least one conventional RU; the MCS indication of the at least two RUs includes an MCS indication corresponding to the distributed RU and an MCS indication corresponding to the conventional RU. The MCS indication issued in the above manner can make full use of the scattered spectrum that appears in the conventional RU due to various reasons, and the use of different MCSs can fully demonstrate the gains brought by the frequency diversity and increased transmission power of the distributed RU, and the overall flexibility is greatly improved while taking into account stability.

[0097] The steps of the above method are divided only for the purpose of clear description. During implementation, they can be combined into one step or some steps can be split and decomposed into multiple steps. As long as they include the same logical relationship, they are all within the scope of protection of this application; adding insignificant modifications or introducing insignificant designs to the algorithm or process without changing the core design of the algorithm and process are all within the scope of protection of this application.

[0098] It is worth noting that all modules involved in this embodiment are logical modules. In actual applications, a logical unit can be a physical unit, a part of a physical unit, or a combination of multiple physical units. In addition, to highlight the innovations of the present invention, this embodiment does not include units that are not closely related to solving the technical problems proposed by the present invention. However, this does not mean that other units do not exist in this embodiment.

[0099] Another embodiment of the present invention relates to a terminal, such as Figure 2 As shown, it includes at least one processor 201; and a memory 202 that is communicatively connected to the at least one processor; wherein the memory 202 stores instructions that can be executed by the at least one processor 201, and the instructions are executed by the at least one processor 201 to enable the at least one processor 201 to execute the indication method of multiple resource units as described above.

[0100] The memory 202 and processor 201 are connected using a bus. The bus can include any number of interconnected buses and bridges, connecting various circuits of one or more processors 201 and memory 202. The bus can also connect various other circuits such as peripheral devices, voltage regulators, and power management circuits. These are all well known in the art and are therefore not described further herein. The bus interface provides an interface between the bus and the transceiver. The transceiver can be a single component or multiple components, such as multiple receivers and transmitters, providing a unit for communicating with various other devices over a transmission medium. Data processed by the processor 201 is transmitted over a wireless medium via an antenna. Furthermore, the antenna receives data and transmits it to the processor 201.

[0101] The processor 201 is responsible for managing the bus and general processing, and can also provide various functions, including timing, peripheral interfaces, voltage regulation, power management, and other control functions. The memory 202 can be used to store data used by the processor 201 when performing operations.

[0102] Another embodiment of the present invention relates to a computer-readable storage medium storing a computer program, which implements the above method embodiment when executed by a processor.

[0103] That is, those skilled in the art will understand that all or part of the steps in the above-mentioned embodiments can be implemented by instructing the relevant hardware through a program, which is stored in a storage medium and includes a number of instructions for causing a device (which may be a single-chip microcomputer, chip, etc.) or a processor to execute all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned storage medium includes: a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, etc., various media that can store program code.

[0104] Those skilled in the art will appreciate that the above-mentioned embodiments are specific examples for implementing the present invention, and that in actual applications, various changes may be made thereto in form and detail without departing from the spirit and scope of the present invention.

Claims

1. A method for indicating multiple resource units, characterized in that: Applied to a first device, comprising: receiving a physical layer protocol data unit (PPDU) sent by a second device, or receiving a trigger frame sent by the second device for prescribing the first device to send a trigger-based physical layer protocol data unit; The PPDU and the trigger frame carry an ultra-high reliability modulation and coding strategy UHR MCS of the first device; The UHR MCS of the first device includes an MCS indication for indicating at least two RUs allocated to the first device; The at least two RUs include at least one distributed RU and at least one regular RU; The MCS indications of the at least two RUs include an MCS indication corresponding to the distributed RU and an MCS indication corresponding to the regular RU; The at least two RUs include a first RU and a second RU, and the MCS indications of the at least two RUs include a first MCS indication corresponding to the first RU and a second MCS indication corresponding to the second RU.

2. The method for indicating multiple resource units according to claim 1, wherein: The at least two RUs are referred to as a multi-resource unit; The first device and the second device have the capability of supporting the multiple resource units to include distributed RUs and regular RUs at the same time.

3. The method for indicating multiple resource units according to claim 2, wherein: The first device and the second device have the capability of applying different MCSs on the distributed RU and the regular RU included in the multi-resource unit; The capability of applying different MCSs on the distributed RU and the regular RU included in the multiple resource unit is used to apply the MCS indication corresponding to the distributed RU and the MCS indication corresponding to the regular RU.

4. The method for indicating multiple resource units according to claim 2, wherein: The method further comprises: When the first device performs link adaptation with the second device, receiving a request for MCS estimation initiated by the second device through the MRQ field in the PPDU; providing the MCS estimate requested by the second device by sending a response carrying an MFB field; The control information subfield of the control subfield corresponding to the link adaptation includes at least one of the following or any combination thereof: An indication for indicating whether the current multi-resource unit includes a distributed RU, an indication for indicating whether the current work is performed as an ultra-high reliability device or as a high-throughput device, an indication for indicating whether the current work is performed as an ultra-high reliability device or as an extremely high-throughput device, an indication for indicating whether the current work is performed as an ultra-high reliability device or as an extremely high-throughput device, a first MCS indication corresponding to the first RU, and a second MCS indication corresponding to the second RU.

5. The method for indicating multiple resource units according to claim 2, wherein: The second MCS indication corresponding to the second RU is used to indicate an offset, and the offset will be used to obtain the MCS index of the second RU after being acted upon by the first MCS indication corresponding to the first RU.

6. The method for indicating multiple resource units according to claim 1, wherein: The MCS indication corresponding to the distributed RU and the MCS indication corresponding to the regular RU carry multiple MCS index recommendation values corresponding to the RU. The MCS index recommendation value will serve as a recommended value to affect the selection result when selecting the corresponding MCS index for the RU.

7. The method for indicating multiple resource units according to claim 6, wherein: The method further includes: when the first RU and the second RU are both distributed RUs, the first RU and the second RU have different styles, or different sparsity levels, or different bandwidths, or different configurations.

8. The method for indicating multiple resource units according to claim 1, wherein: When the PPDU is an ultra-high reliability physical layer protocol data unit (UHR PPDU), and the UHR PPDU is a multi-user physical layer protocol data unit, the UHR MCS of the first device will be carried by a user-specific field in a UHR SIG field in the UHR PPDU; In the trigger frame, the UHR MCS of the first device will be carried by the user information field in the trigger frame.

9. The method for indicating multiple resource units according to claim 1, wherein: The MCS indication for indicating at least two RUs allocated to the first device in the user information field in the trigger frame includes a first uplink MCS indication field, a reserved field, and a trigger-dependent user information field; The first uplink MCS indication field is used to indicate the MCS of the regular RU allocated to the first device; The reserved field is used to indicate whether a distributed RU and a regular RU exist in the at least two RUs; The trigger-dependent user information field includes a second uplink MCS indication field; The second uplink MCS indication field is used to indicate the MCS of the distributed RU allocated to the first device.

10. A terminal, characterized in that: include: at least one processor; as well as, a memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to perform the multiple resource unit indication method according to any one of claims 1 to 9.

Images