Signaling design for ultra-high reliability transmission in wireless communication

Abstract

The invention provides a wireless communication method. The wireless communication method comprises the following steps: a processor of a device executes wireless communication with a physical layer protocol data unit (PPDU) by any of the following modes: generating and transmitting the PPDU; or receiving and processing the PPDU. Wherein a bit 19 of a user field, which is used for non-multi-user multiple input multiple output (MU-MIMO) allocation, of an ultra high reliability signal (UHR-SIG) field in the PPDU indicates whether unequal modulation UEQM or equal modulation EQM is applied in the PPDU.

Description

Technical field

[0001] The present invention relates generally to wireless communications, and more particularly to signaling design for ultra-high-reliability (UHR) transmission in wireless communications. [Background Technology]

[0002] Unless otherwise indicated herein, the approaches described in this section are not prior art to the claims listed below and are not admitted to be prior art by inclusion in this section.

[0003] In wireless communications (such as Wi-Fi (or WiFi)) based on the Institute of Electrical and Electronics Engineers (IEEE) specifications, the channel conditions of multiple spatial streams (SSs) may vary and can differ (for example, the delta signal-to-interference-and-noise ratio (SINR) between SSs is 10-15 dB). Therefore, the concept of unequal modulation (UEQM) on multiple spatial streams was proposed in the IEEE 802.11n specification. It is believed that UEQM on spatial streams can significantly improve system throughput. However, there are a large number of options for UEQM patterns, which increases complexity and is not conducive to implementation. In addition, additional modulation and coding schemes (MCS), UEQM for different spatial streams and / or frequency domain (FD), two times low-density parity check (2xLDPC), and distributed resource units (DRU) have been discussed as IEEE802.11bn physical-layer (PHY) features. Signaling schemes need to be designed to enable new and existing features in WLAN products based on the IEEE 802.11bn (and later) specifications. Therefore, a signaling design solution for ultra-high-reliability (UHR) transmission in wireless communications is needed. [Summary of the invention]

[0004] The following summary is for illustrative purposes only and is not intended to be limiting in any way. That is, the following summary is intended to introduce the concepts, highlights, benefits, and advantages of the novel and non-obvious technologies described herein. Selected embodiments are further described below in the detailed description. Therefore, the following summary is not intended to identify essential features of the claimed subject matter, nor is it intended to be used to determine the scope of the claimed subject matter.

[0005] An object of the present invention is to provide schemes, concepts, designs, techniques, methods and apparatus related to signaling design for UHR transmission in wireless communications. The above-mentioned problems may be avoided or otherwise alleviated by implementing one or more of the various proposed schemes described herein. For example, the various proposed signaling schemes may involve different signaling fields and different combinations thereof, such as non-MU-MIMO user field signaling, MU-MIMO user field signaling, trigger frame signaling (including common user information, special user information (Special User Info) and user information (User Info) fields), and UHR signal field (UHR-SIG) signaling with UEQM indication.

[0006] In one aspect, a method may involve a processor of an apparatus performing wireless communication of a physical layer protocol data unit (PPDU) by either: (i) generating and transmitting the PPDU, or (ii) receiving and processing the PPDU.

[0007] In one aspect, a method may involve a processor of an apparatus performing wireless communication of a trigger frame by either: (i) generating and transmitting the trigger frame, or (ii) receiving and processing the trigger frame.

[0008] In another aspect, an apparatus may include a transceiver configured for wireless communication and a processor coupled to the transceiver. The processor may perform wireless communication of a physical layer protocol data unit (PPDU) by either: (i) generating and transmitting the PPDU, or (ii) receiving and processing the PPDU.

[0009] In another aspect, an apparatus may include a transceiver configured for wireless communication and a processor coupled to the transceiver. The processor may perform wireless communication of a trigger frame by either: (i) generating and transmitting the trigger frame, or (ii) receiving and processing the trigger frame.

[0010] It is worth noting that although the description provided herein may be in the context of certain wireless access technologies, networks and network topologies, such as Wi-Fi, the concepts, schemes and any variants / derivatives thereof may be implemented in other types of wireless access technologies, networks and network topologies, such as but not limited to Bluetooth, ZigBee, fifth generation (5G) th The present invention also includes 5G (5th Generation, 5G) / New Radio (NR), Long-Term Evolution (LTE), LTE-Advanced, LTE-Advanced Pro, Internet of Things (IoT), Industrial Internet of Things (IIoT), and narrowband IoT (NB-IoT). Therefore, the scope of the present invention is not limited to the examples described herein.

Brief Description of the Drawings

[0011] The accompanying drawings are used to further understand the present invention and are incorporated into and constitute a part of this invention. The drawings illustrate embodiments of the present invention and, together with the description, serve to explain the principles of the present invention. It should be understood that the drawings are not necessarily drawn to scale, as some components may not be proportional to the dimensions in actual embodiments in order to clearly illustrate the concepts of the present invention.

[0012] Figure 1 is a schematic diagram of an example network environment in which various solutions and aspects of the present invention may be implemented.

[0013] Figure 2 is a schematic diagram of an example design according to the proposed solution of the present invention.

[0014] Figure 3 is a schematic diagram of an example design according to the proposed solution of the present invention.

[0015] Figure 4 is a schematic diagram of an example design according to the proposed solution of the present invention.

[0016] Figure 5 is a schematic diagram of an example design according to the proposed solution of the present invention.

[0017] Figure 6 is a schematic diagram of an example design according to the proposed solution of the present invention.

[0018] Figure 7 is a schematic diagram of an example design according to the proposed solution of the present invention.

[0019] Figure 8 is a schematic diagram of an example design according to the proposed solution of the present invention.

[0020] Figure 9 is a schematic diagram of an example design according to the proposed solution of the present invention.

[0021] Figure 10 is a schematic diagram of an example design according to the proposed solution of the present invention.

[0022] Figure 11 is a schematic diagram of an example design according to the proposed solution of the present invention.

[0023] Figure 12 is a schematic diagram of an example design according to the proposed solution of the present invention.

[0024] Figure 13 is a schematic diagram of an example design according to the proposed solution of the present invention.

[0025] Figure 14 is a schematic diagram of an example design according to the proposed solution of the present invention.

[0026] Figure 15 is a schematic diagram of an example design according to the proposed solution of the present invention.

[0027] Figure 16 is a schematic diagram of an example design according to the proposed solution of the present invention.

[0028] Figure 17 is a schematic diagram of an example design according to the proposed solution of the present invention.

[0029] Figure 18 is a schematic diagram of an example design according to the proposed solution of the present invention.

[0030] Figure 19 is a schematic diagram of an example design according to the proposed solution of the present invention.

[0031] Figure 20 is a schematic diagram of an example design according to the proposed solution of the present invention.

[0032] Figure 21 is a block diagram of an exemplary communication system according to a proposed solution of the present invention.

[0033] Figure 22 is an example flow chart of a proposed solution according to the present invention.

[0034] Figure 23 is an example flow chart of a proposed solution according to the present invention. [Specific implementation method]

[0035] Detailed embodiments and implementations of the claimed subject matter are disclosed herein. However, it should be understood that the disclosed embodiments and implementations are merely illustrative of the claimed subject matter, which may be implemented in various forms. The present invention may be implemented in a variety of different forms and should not be construed as being limited to the exemplary embodiments and implementations described herein. On the contrary, these exemplary embodiments and implementations are provided to make the description of the present invention comprehensive and complete and to fully convey the scope of the present invention to those skilled in the art. In the following description, details of well-known features and technologies may be omitted to avoid unnecessarily obscuring the presented embodiments and implementations.

[0036] Overview

[0037] Embodiments according to the present invention relate to various technologies, methods, schemes, and / or solutions for signaling design for UHR transmission in wireless communications. According to the present invention, a variety of possible solutions can be implemented individually or in combination. That is, although these possible solutions are described individually below, two or more of these possible solutions can be implemented in some combination or another.

[0038] Figure 1 An example network environment 100 is shown in which various solutions and approaches based on the present invention may be implemented. Figures 2 to 23 An example of implementing various proposed solutions in a network environment 100 according to the present invention is shown. Figure 1 Figure 23 Describe the various proposed solutions.

[0039] refer to Figure 1 , the network environment 100 involves at least STA 110 and STA 120 wirelessly communicating. STA 110 and STA 120 can be access point (AP) STAs or non-AP STAs, or, as AP STAs or non-AP STAs. STA 110 and STA 120 can be configured or capable of operating in accordance with the same or different IEEE 802.11 standards (e.g., IEEE 802.11be and future standards). Each of STA 110 and STA 120 can be configured to communicate with each other in accordance with various proposed schemes described below using techniques related to signaling design for UHR transmission in wireless communications. It is worth noting that although various proposed schemes may be described separately or individually below, in actual implementation, some or all of the proposed schemes may be used in combination or implemented in other ways. Of course, each proposed scheme may be used separately or implemented in other ways.

[0040] According to various proposed schemes of the present invention, in the ultra-high reliability signaling (UHR-SIG) and SIGs of standards above UHR, some restrictions on unequal modulation (UEQM) of spatial streams (SS) can be assumed in multiple signaling schemes for the user field of non-multi-user multi-input-multiple-output (non-MU-MIMO) transmissions. Under the first scheme (Scheme 1), the 4-bit NSS subfield can be reused to jointly indicate<NSS,EQM,UEQM> According to the table described below, the NSS subfield can reuse the verification entry for UEQM mode indication. The MCS of the first spatial stream for equal modulation (EQM) or UEQM can be indicated by the 5-bit MCS subfield. Under the second scheme (Scheme 2), 5 bits can be used to jointly indicate<NSS,BFed,Coding,EQM,UEQM> Under the third scheme (Scheme 3), a 2-bit table may be used to indicate the UEQM mode. Since transmissions using UEQM may benefit from fine MCS levels, additional MCS indications may also be considered in the proposed signaling scheme described herein.

[0041] With regard to the overall consideration of UEQM for SSs, in order to limit the combinations of UEQM modes, the maximum number of SSs supported can be 4. Since the delta SINR can be as high as 15dB, the maximum difference in quadrature amplitude modulation (QAM) levels between SSs can be 2. In the above two cases, the UEQM modes can be further limited to <2, 3, 3> modes for <2, 3, 4> SSs (a total of 8 modes). For example, if the number of SSs is 4, the number of UEQM modes is 3. In addition, UEQM for SSs may require channel condition information, so only beamformed transmission (Tx BF) may be allowed. To reduce implementation complexity, UEQM can be applied only to symbols encoded by LDPC, and UEQM can be used for non-MU-MIMO transmissions (e.g., single-user (SU) and / or orthogonal frequency-division multiple-access (OFDMA) downlink (DL) transmissions).

[0042] Figure 2 An example design 200 is shown, Figure 3 An example design 300 of user fields for non-multi-user multiple-input multiple-output (non-MU-MIMO) allocation according to the proposed scheme of the present invention (Scheme 1 mentioned above) is shown. Figure 2 , the MCS field (5 bits in total) can be used to indicate all MCS levels in UHR transmission and transmission above UHR. The MCS field can include a 4-bit MCS field in EHT (Extreme High Throughput) and a 1-bit reserved bit. Since in IEEE802.11be, NSS values ​​exceeding 8 are validation bits (Validate bit). Therefore, these validation bits can be reused to indicate UEQM mode. For example, the 4-bit NSS subfield can be used to jointly indicate<NSS,EQM,UEQM> . In this case, the most significant bit (MSB) in the 4-bit NSS subfield can also be used as an indication of EQM and UEQM. Under the proposed scheme, additional bits can be added as reserved bits (e.g., bit B22). It is worth noting that since only beamformed (BFed) transmissions and LDPC coded symbols are allowed to apply UEQM, bits B20 and B21 can be rewritten (rephrase, also known as restatement) for other purposes. For example, bits B20 and B21 can be used to indicate the feedback information / type required in the block acknowledgment (BlockAck) frame to assist in link adaptation.

[0043] refer to Figure 3 Under the proposed scheme, the validation entry of the NSS subfield can be reused to indicate the number of SSs and the corresponding UEQM mode. In addition, the 4-bit table can also be viewed as a separate EQM and UEQM table based on the corresponding MSB value. For example, when the MSB value is 0, the remaining 3 bits can indicate the number of SSs and EQM in use; when the MSB value is 1, the remaining 3 bits can indicate the number of SSs and the corresponding UEQM mode. As another example of scheme 1, the table can be arranged by the number of SSs. In this case, the MSB may not be used as an indication of EQM and UEQM.

[0044] Figure 4An example design 400 according to the proposed scheme (Scheme 2 above) of the present invention is shown. Under the proposed scheme, there may be some limitations at UHR and above, such as: (1) support for up to 4 spatial streams (4SS) using binary convolutional coding (BCC); (2) support for up to 8 spatial streams (8SS) using LDPC; and (3) support for 8 UEQM modes (using LDPC). The total number of entries can be 32, so 5 bits may be sufficient to indicate all UEQM modes. In addition, 5 bits can be used to jointly indicate<NSS,BFed,Coding,EQM,UEQM> ,like Figure 4 shown.

[0045] Figure 5 An example design 500 is shown, Figure 5 An example design 500 according to the proposed scheme (Scheme 3 above) of the present invention is shown. Since UEQM may only be applied in Tx BF using LDPC codes, the BFed and Coding bits can be rephrase. The BFed and Coding bits can indicate 2 bits.<EQM,UEQM> For example, according to the NSS field, Figure 5 The 2 digits shown<EQM,UEQM> Tables can be used for UEEQM mode indication. For example, when the number of SSs indicated by the NSS field is 2, the first table can be used. When the number of SSs indicated by the NSS field is 3, the second table can be used. When the number of SSs indicated by the NSS field is 4, the third table can be used. Under the proposed scheme, a flag bit can be used as an indicator of EQM and UEAM. The flag bit can be the MSB in the NSS subfield (e.g., bit B19) or the newly added bit B22.

[0046] refer to Figure 6 ,Under the proposed scheme, the UEQM patterns within different numbers of SSs ,can be sorted according to the QAM level differences and ,start from the SS with smaller changes compared to the modulation of EQM, ,e.g., QAM / QAM / QAM / QAM, e.g. Figure 6As shown. For example, when the number of SSs indicated by the NSS field is 2, the first table can be used. When the number of SSs indicated by the NSS field is 3, the second table can be used. When the number of SSs indicated by the NSS field is 4, the third table can be used. In each table, the order of modulation of each SS in each row can be arranged in ascending order according to the difference from QAM. For the table corresponding to 4 SSs, if the UEQM mode table applies the first value (for example, "00"), QAM is applied to the first SS, the second SS, and the third SS, and QAM-1 is applied to the fourth SS. In addition, if the UEQM mode table applies the second value (for example, "01"), QAM is applied to the first SS, the second SS, and the third SS, and QAM-2 is applied to the fourth SS. In addition, if the UEQM mode table applies the third value (for example, "10"), QAM is applied to the first SS and the second SS, QAM-1 is applied to the third SS, and QAM-2 is applied to the fourth SS. For the table corresponding to 2 SSs, if the UEQM pattern table applies the first value (e.g., "00"), QAM is applied to the first SS and QAM-1 is applied to the second SS. Furthermore, if the UEQM pattern table applies the second value (e.g., "01"), QAM is applied to the first SS and QAM-2 is applied to the second SS. For the table corresponding to 3 SSs, if the UEQM pattern table applies the first value (e.g., "00"), QAM is applied to the first and second SSs, and QAM-1 is applied to the third SS. Furthermore, if the UEQM pattern table applies the second value (e.g., "01"), QAM is applied to the first and second SSs, and QAM-2 is applied to the third SS. Furthermore, if the UEQM pattern table applies the third value (e.g., "10"), QAM is applied to the first SS, QAM-1 is applied to the second SS, and QAM-2 is applied to the third SS.

[0047] Figure 7 The example designs 700 under the above-described schemes 1, 2, and 3 are shown. That is, Figure 7 The above described scheme 1 is shown (in Figure 7 Scheme 2 (marked as "S1") Figure 7 Scheme 3 (marked as "S2" in Figure 7 Design summary under the label “S3” in the figure.

[0048] Option 1 could involve a joint<Nss,EQM,UEQM> Table. The verification bit in IEEE 802.11be can be reused. When using UEQM transmission, the BFed and Coding bits can be reformulated for other purposes. Under Scheme 1, one bit is added (total 23 bits) to serve as a reserved bit (total 23 bits).

[0049] Option 2 could involve a joint<Nss,BFed,Coding,EQM,UEQM> Table. The NSS, BFed, and Coding bits in IEEE 802.11be can be redefined. There may be no need to expand the number of bits in the user field of IEEE 802.11be because bit B21 can be used as a reserved bit (22 bits in total).

[0050] Scheme 3 can use a flag bit to indicate EQM and UEQM, and redefine the BFed and Coding bits for use in a 2-bit table. One bit in the NSS subfield can be reused. The BFed and Coding bits can be reformulated as a 2-bit table (the UEQM mode depends on the number of supported spatial streams). Under Scheme 3, an additional bit can be added for use as a reserved bit (a total of 23 bits).

[0051] Under the various proposed schemes according to the present invention, there may be some considerations regarding MCS indication, UEQM indication for SS, and 2xLDPC coding indication. It is worth noting that although IEEE 802.11be applies a 4-bit MCS table, if new MCS levels are added in IEEE 802.11bn, the 4-bit MCS table may not be enough. Therefore, it may be reasonable to extend one bit for MCS indication (for example, making it a 5-bit table). In addition, under the proposed scheme, UEQM for multiple SSs (up to 4SSs) with limited QAM modes can be supported. It may be desirable to explicitly indicate: (a) whether UEQM is applied to the SS; and / or (b) whether 2xLDPC is applied. The indication of these functions may be specific to different STAs, so they can be indicated in the user information field of the PPDU.

[0052] Figure 8 An example design 800 is shown according to the proposed scheme of the present invention. Design 800 may involve the first option (Option 1) of MCS in the user field for non-MU-MIMO configuration, UEQM for SS, and 2xLDPC indication. Figure 8In part (A), UEQM on different SSs may be used only in Tx BF using LDPC codes. By restating the BFed and Coding bits, the UEQM mode can be expressed as a 2-bit table. On the other hand, in IEEE 802.11bn, a maximum of 8 SSs are considered, so the MSB of the NSS subfield may be reused as a UEQM indicator. Under the proposed scheme, with respect to the UEQM on SS bit, a value of "1" may indicate that UEQM is applied to the SS, and bits B20-21 are redefined as the UEQM mode table; a value of "0" may indicate that EQM is applied. With respect to the 2XLDPC bit, a value of "1" may indicate that the transmission coding using LDPC may use a code size (also called codeword length) of 2x1944; a value of "0" may indicate that the transmission coding using LDPC uses a code size different from 2x1944. If BCC coding is used for transmission, this 2XLDPC bit may be reserved. Reference Figure 8 In part (B), eight UEQM modes are considered. Different table designs can be proposed for different options. The UEQM mode for SS can be represented by reformulating the BFed and Coding bits.

[0053] Figure 9 An example design 900 is shown under a proposed scheme according to the present invention. Design 900 may involve the second option (Option 2) of MCS indication of the user field for non-MU-MIMO configuration, UEQM indication for SS, and 2xLDPC indication. In IEEE 802.11be, NSS values ​​exceeding 8 are validation bits. Under the proposed scheme, the MSB of the NSS subfield may be redefined as the UEQM indicator. Reference Figure 9 In part (A), the NSS subfield may be restated as a UEQM mode indicator. Regarding the UEQMon SS bit, a value of "1" may indicate that UEQM is applied to SS, and bits B16-18 are redefined as the UEQM mode table; a value of "0" may indicate that EQM is applied. Regarding the 2XLDPC bit, a value of "1" may indicate that the transmission coding using LDPC may use a code size of 2x1944; a value of "0" may indicate that the transmission coding using LDPC may use a code size different from 2x1944. If BCC encoding is used for transmission, this 2XLDPC bit is reserved. Reference Figure 9 In part (B), the UEQM mode for SS can be expressed by restating the NSS subfield.

[0054] Figure 10An example design 1000 according to the proposed scheme of the present invention is shown. Design 1000 may involve a third option (Option 3) of MCS indication for non-MU-MIMO configuration, UEQM indication for SS, and 2xLDPC indication. Option 3 may be considered a variation of Option 2. Figure 10 , the coding bits and 2XLDPC bits can be combined into a forward error correction (FEC) coding table. The NSS subfield can be restated as a UEQM mode indicator. Regarding the UEQMon SS bit, a value of "1" can indicate that UEQM is applied to SS, and bits B16-18 are redefined as the UEQM mode table; a value of "0" can indicate that EQM is applied.

[0055] Figure 11 An example design 1100 according to the proposed scheme of the present invention is shown. Design 1100 may involve MCS indication and 2xLDPC indication for MU-MIMO user fields. Since UEQM for SS is not applicable to MU-MIMO scenarios, MU-MIMO signaling design may only consider MCS and 2XLDPC. In addition, since only 8 SS are supported in IEEE 802.11bn, the Spatial Configuration subfield may reuse the 4-bit table of IEEE 802.11ax (reduced from 6 bits in IEEE 802.11be). Reference Figure 11 , MCS indication and 2XLDPC indication can fit in the 22-bit MU-MIMO user field. To match the user field length, a reserved bit can be added. Regarding the 2XLDPC bit, the value "1" can indicate that the transmission coding using LDPC can use a code size of 2x1944; the value "0" can indicate that the transmission coding using LDPC can use a code size different from 2x1944. If BCC coding is used for transmission, this 2XLDPC bit can be reserved. It is worth noting that the coding bit and the 2XLDPC bit can be combined into a 2-bit FEC coding table.

[0056] Figure 12An example design 1200 is shown under a proposed scheme according to the present invention. Design 1200 may involve a first option (option 1) of a DRU indication in a common field of a trigger frame. In IEEE 802.11be, bits B56-B62 are extremely high throughput (EHT) reserved bits. In IEEE 802.11bn, to indicate a DRU (distributed resource unit), 4 bits may be selected from B56-B62 as a per 80 MHz DRU indicator. Each of the 4 bits indicates whether the corresponding 80 MHz uses a DRU. Under the proposed scheme, the unused bits may remain reserved or used to indicate other UHR functions, such as aggregate physical-layer protocol data unit (APPDU), dynamic subchannel / subband operation (DSO) and / or in-device coexistence (IDC).

[0057] Figure 13 An example design 1300 is shown according to the proposed scheme of the present invention. Design 1300 may involve the second option (Option 2) of the DRU indication in the Special User Info field of the trigger frame. Figure 13 , the DRU indication can also be indicated in the special user information field. In this case, 4 bits selected from bits B25-B39 can be used as a per 80 MHz DRU indicator (Per 80dRU indicator). Each of the 4 bits indicates whether the corresponding 80 MHz uses a DRU. Under the proposed scheme, the unused bits can remain as reserved bits, ignore and validate bits, or can be used to indicate other UHR functions, such as APPDU, DSO and / or IDC.

[0058] Figure 14An example design 1400 according to the proposed scheme of the present invention is shown. Design 1400 may involve a 2xLDPC indication and SS allocation subfield of the user field in the trigger frame. In IEEE 802.11be, 4 bits are used to indicate the starting SS. In IEEE 802.11bn, considering a maximum of 8 SSs, 3 bits are used to indicate the starting SS. Under the proposed scheme, 1 bit in the SS Allocation subfield may be reduced. This bit may be used for the 2xLDPC indication. This bit may be Figure 14 If DRU is indicated, the SS allocation subfield can be restated to indicate the distributed bandwidth and number of SSs used by the user corresponding to the user field, such as Figure 14 As shown in Option 1 and Option 2. Under the proposed scheme, coding bits and 2XLDPC bits can be combined.

[0059] Figure 15 An example design 1500 is shown for a proposed scheme according to the present invention. Design 1500 may relate to a UHR-SIG common field for a PPDU in non-OFDMA transmission. In IEEE 802.11be, the length of the user field for non-MU-MIMO is 22 bits. If the User Info field is extended, the length of the UHR-SIG common field needs to be reduced to accommodate the OFDM symbol boundary (e.g., common field + user information field + tail + cyclic redundancy check (CRC) = 52 bits for SU). For example, if the user information field is 23 bits, the length of the UHR-SIG common field may be reduced by 1 bit. If the user information field is 24 bits, the length of the UHR-SIG common field may be reduced by 2 bits in the disregard subfield.

[0060] Figure 16An example design 1600 is shown under a proposed scheme according to the present invention. Design 1600 may relate to a first option (option 1) of applying UEQM indication to FD in the UHR-SIG common field. Under the proposed scheme, applying UEQM indication to FD may be indicated by an additional bit, which may be selected from the Disregard bits (e.g., the previous bits B13-B16 in the EHT-SIG common field). The Punctured ChannelInfo field in the Universal Signaling (U-SIG) field may indicate the size and position of the resource unit (RU) or multi-RU (MRU) of the applied QAM level. The allowed UEQM operation may not exceed the allowed RU or MRU mode. Regarding the UEQM on FD bit, a value of "1" may indicate that UEQM is applied to FD, and bits B20-B21 in the user information field are redefined as a UEQM mode table (for example, may be reused or redefined as a UEQM mode different from the UEQM mode for SS), and B19 is set to 0; a value of "0" may indicate that EQM is applied.

[0061] Figure 17 An example design 1700 is shown for a proposed scheme according to the present invention. Design 1700 may relate to a second option (Option 2) for indicating the application of UEQM on FD in the UHR-SIG common field. Under the proposed scheme, two bits may be used to indicate the application of UEQM on SS and the application of UEQM on FD. In this case, UEQM on FD may involve splitting the bandwidth. Under Option 2, the 1-bit 'UEQM on SS' indicator in the non-MU-MIMO user field may be saved. Therefore, the non-MU-MIMO user field may maintain the same length as defined in the IEEE 802.11be specification (e.g., 22 bits).

[0062] Figure 18An example design 1800 according to the proposed scheme of the present invention is shown. Design 1800 may involve an indication of the application of UEQM to SS and FD in the UHR-SIG common field. Under the proposed scheme, a 4-bit bitmap may be applied to indicate the application of UEQM to SS and FD. In this case, the UEQM for FD may divide the bandwidth into 4 parts. For example, if the bandwidth (BW) of the PPDU is 320MHz, each bit may represent the corresponding 80MHz. As another example, if the BW of the PPDU is 160MHz, each bit may represent the corresponding 40MHz. The representation of the bitmap may start from lower frequency to higher frequency. According to the above-mentioned proposed scheme and option 2, the 1-bit 'UEQM on SS' indicator in the non-MU-MIMO user field may be saved. In this case, the non-MU-MIMO user field may maintain the same length as defined in the IEEE 802.11be specification (e.g., 22 bits). Reference Figure 18 Regarding the bitmap for applying UEQM to FD, when all bits are "1", UEQM to SS can be applied; when all bits are "0", EQM can be applied; when not all bits are "1" or "0", UEQM to FD can be applied. In this case, a bit with a value of "1" may indicate a frequency position where QAM is applied, and a bit with a value of "0" may indicate a frequency position where QAM-x level is applied.

[0063] According to the proposed scheme of the present invention, a separate bit can be applied to indicate 2xLDPC, and there may be no entries reserved for other coding modes (e.g., 4xLDPC or other LDPC coding schemes). According to the proposed scheme, with respect to the 2xLDPC bit, a value of "1" can indicate that the transport coding using LDPC can use a code size of 2x1944; a value of "0" can indicate that the transport coding using LDPC can use a code size different from 2x1944. Alternatively, with respect to the Coding bit, a value of "0" can indicate that the transport coding uses BCC; a value of "1" can indicate that the transport coding uses LDPC. It is worth noting that this may be an uncommon combination (Coding bit set to 0, 2xLDPC bit set to 1) that can be used to indicate a new coding mode (e.g., 4xLDPC or other LDPC coding schemes). The same approach can be applied to the non-MU-MIMO and MU-MIMO user fields and the user information field in the trigger frame.

[0064] Figure 19An example design 1900 is shown under a proposed scheme according to the present invention. Design 1900 may relate to a MU-MIMO user field. Under the proposed scheme, a new coding mode may be indicated by setting the Coding bit of a subfield to "0" and the 2xLDPC bit to "1" (e.g., a subfield in the MU-MIMO user field). Note that the position of each subfield may be modified. Under the proposed scheme, the bits used as the Coding bit, 2xLDPC bit, and Reserved bit in the MU-MIMO user field may be different. See Figure 19 In the first option, bit B20 can be used as a coding bit, bit B21 can be used as a 2xLDPC bit, and bit B22 can be a reserved bit. In the second option, bit B20 can be used as a reserved bit, bit B21 can be used as a coding bit, and bit B22 can be used as a 2xLDPC bit. In the first option, if the coding bit is set to 0 and the 2xLDPC bit is set to 0, BCC mode is used; if the coding bit is set to 1 and the 2xLDPC bit is set to 0, LDPC mode is used; if the coding bit is set to 1 and the 2xLDPC bit is set to 1, 2xLDPC mode is used; if the coding bit is set to 0 and the 2xLDPC bit is set to 1, 4xLDPC or other LDPC coding modes are used.

[0065] Figure 20 An example design 2000 is shown according to a proposed solution of the present invention. Design 2000 may involve triggering the user field in a frame. Under the proposed solution, the position of each subfield may be modified. Figure 20 , bits B26-B31 in the user field may have different indication options.

[0066] In view of the above, some characteristics of the various proposed solutions can be summarized.

[0067] First, a 4-bit bitmap (eg, bits B56-B59) in the common information field can be used for DRU indication. For example, each bit in the 4-bit bitmap can indicate whether the corresponding 80 MHz in the 320 MHz bandwidth is used for DRU or regular resource unit (RRU).

[0068] Secondly, except for the Disregard bit in the common field for non-OFDMA transmission in the UHR-SIG, other fields may remain the same as the common field for non-OFDMA transmission in the EHT-SIG. For example, bits B0-B2 may be used as a Spatial Reuse subfield, bits B4-B5 may be used as a Guard Interval (GI) + Long Training Field (LTF) size subfield, bits B6-B8 may be used as a Number of UHR-LTF Symbols subfield, bit B9 may be used as an LDPC Extra Symbol Segment subfield, bits B10-B11 may be used as a Pre-FEC Padding Factor subfield, bit B12 may be used as a PE Disambiguity subfield, bits B13-B15 may be used as a Disregard subfield, and bits B16-B18 may be used as a Number of non-OFDMA Users subfield.

[0069] Third, the signaling design for the MU-MIMO user field in the UHR-SIG field may involve 23 bits, including: bits B0-B10 for the STA identification (STA-ID) subfield, bits B11-B15 for the MCS subfield, bits B16-B19 for the spatial configuration subfield, bit B20 for the resolution subfield, bit B21 for the coding subfield, and bit B22 for the 2xLDPC subfield. In this design, when the coding subfield indicates LDPC as the coding mode, bit B22 of the 2xLDPC subfield may be set to: (a) "1" to indicate the use of LDPC with a code size of 2x1944 for transmit coding; or (b) "0" to indicate the use of LDPC with a code size of 648, 1296, or 1944 for transmit coding.

[0070] Fourth, the signaling design for the MU-MIMO user field in the UHR-SIG field may involve 23 bits, including: bits B0-B10 used as the STA-ID subfield, bits B11-B15 used as the MCS subfield, bits B16-B18 used as the Number of Spatial Streams (NSS) subfield, bit B19 used as the UEQM subfield, bits B20-B21 used as the UEQM mode subfield (or bit B20 used as the BFed subfield and bit B21 used as the Coding subfield), and bit B22 used as the 2xLDPC subfield. In this design, for UEQM indication, bit B19 can be set to: (a) "1" to indicate the application of UEQM, and bits B20-B21 are redefined to indicate the UEQM mode; or (b) "0" to indicate the application of EQM (bits B20 and B21 are used for the BFed and Coding bits, respectively). In addition, when the Coding subfield indicates LDPC, for 2xLDPC indication, bit B22 can be set to: (a) "1" to indicate that LDPC with a code size of 2x1944 is used for transport coding; or (b) "0" to indicate that LDPC with a code size of 648, 1296, or 1944 is used for transport coding.

[0071] Fifth, a UHR Variant User Information field design may be used, including: bits B0-B11 for the AID12 subfield, bits B12-B19 for the RU Allocation subfield, bit B20 for the Uplink (UL) FEC Coding Type subfield, bits B21-B25 for the UL UHR-MCS subfield, bit B26 for the 2xLDPC subfield, bits B27-B31 for the Spatial Stream Allocation subfield, bits B32-B38 for the UL Target Received Power subfield, bit B39 for the PS160 subfield, and a variable number of bits for the Trigger Dependent User Info subfield. Furthermore, the design of the Spatial Stream Allocation subfield may depend on whether the 80 MHz frequency sub-block corresponding to the user in the UHR Variant User Information field uses an RRU or a DRU. That is, in the case of a DRU, one bit in the Spatial Stream Allocation subfield in the UHR Variant User Information field may indicate the number of spatial streams (e.g., 1ss or 2ss). For example, in the case of an RRU, bits B0-B2 of the spatial stream allocation subfield may indicate the starting stream index (Starting Stream Index), and bits B3-B4 of the spatial stream allocation subfield may indicate the number of spatial streams. On the other hand, in the case of a DRU, bits B0-B1 of the spatial stream allocation subfield may indicate the distribution bandwidth BW, bits B2-B3 of the spatial stream allocation subfield may be reserved bits, and bit B4 may indicate the number of spatial streams.

[0072] Figure 21An example system 2100 is shown, which includes at least an example apparatus 2110 and an example apparatus 2120 consistent with at least one embodiment of the present invention. Each of apparatus 2110 and apparatus 2120 can perform various functions to implement the schemes, techniques, processes, and methods described herein related to signaling design for UHR transmission in wireless communications, including the various schemes related to the various proposed designs, concepts, schemes, systems, and methods described above, as well as the processes described below. For example, apparatus 2110 can be implemented in STA 110, while apparatus 2120 can be implemented in STA 120, and vice versa.

[0073] Each of device 2110 and device 2120 can be part of an electronic device, which can be a non-AP STA or an AP STA, such as a portable or mobile device, a wearable device, a wireless communication device, or a computing device. When implemented in a STA, each of device 2110 and device 2120 can be implemented in a smartphone, a smartwatch, a personal digital assistant, a digital camera, or a computing device, such as a tablet, a notebook, or a laptop computer. Each of device 2110 and device 2120 can also be part of a machine-type device, which can be an Internet of Things device, such as a fixed or stationary device, a home device, a wired communication device, or a computing device. For example, each of device 2110 and device 2120 can be implemented in a smart thermostat, a smart refrigerator, a smart door lock, a wireless speaker, or a home control center. When implemented in or as a network device, device 2110 and / or device 2120 can be implemented in a network node (e.g., an AP in a WLAN).

[0074] In some embodiments, each of the apparatus 2110 and the apparatus 2120 may be implemented in the form of one or more integrated circuit (IC) chips, such as, but not limited to, one or more single-core processors, one or more multi-core processors, one or more reduced instruction set computing (RISC) processors, or one or more complex instruction set computing (CISC) processors. In the various schemes described above, each of the apparatus 2110 and the apparatus 2120 may be implemented in or as a STA or AP. For example, each of the apparatus 2110 and the apparatus 2120 may include Figure 21 At least some components shown, such as processor 2112 and processor 2122. In addition, device 2110 and device 2120 may also include one or more other components not related to the solution proposed by the present invention (for example, internal power supply, display device and / or user interface device). Therefore, for the sake of simplicity and brevity, these components of device 2110 and device 2120 are not shown in FIG. Figure 21 Not shown in the figure, nor described below.

[0075] In one aspect, each of processor 2112 and processor 2122 can be implemented in the form of one or more single-core processors, one or more multi-core processors, one or more RISC processors, or one or more CISC processors. That is, even though "processor" is used herein to refer to processor 2112 and processor 2122, in some embodiments, processor 2112 and processor 2122 can each include multiple processors, while in other embodiments, processor 2112 and processor 2122 can each include a single processor. In another aspect, each of processor 2112 and processor 2122 can be implemented in the form of hardware (and, optionally, firmware) having electronic components, where the electronic components include, for example, but not limited to, one or more transistors, one or more diodes, one or more capacitors, one or more resistors, one or more inductors, one or more memristors, and / or one or more variable capacitors, which are configured and arranged to achieve specific purposes in accordance with the present invention. In other words, in at least some embodiments, each of processor 2112 and processor 2122 is a special-purpose machine specifically designed, arranged, and configured to perform specific tasks, including tasks related to signaling design for UHR transmissions in wireless communications in accordance with various embodiments of the present invention.

[0076] In some embodiments, the device 2110 may further include a transceiver 2116 connected to the processor 2112. The transceiver 2116 includes a transmitter capable of wirelessly transmitting data and a receiver capable of wirelessly receiving data. In some embodiments, the device 2120 may further include a transceiver 2126 connected to the processor 2122. The transceiver 2126 may include a transmitter capable of wirelessly transmitting data and a receiver capable of wirelessly receiving data. It is worth noting that although the transceiver 2116 and the transceiver 2126 are shown in the figure as being external to the processor 2112 and the processor 2122 and being separate from the processor 2112 and the processor 2122, respectively, in some embodiments, the transceiver 2116 may be integrated into the processor 2112 as a system on chip (SoC), and the transceiver 2126 may be integrated into the processor 2122 as a SoC.

[0077] In some embodiments, the device 2110 may further include a memory 2114 connected to the processor 2112, the memory 2114 being accessible by the processor 2112 and storing data therein. In some embodiments, the device 2120 may further include a memory 2124 connected to the processor 2122, the memory 2124 being accessible by the processor 2122 and storing data therein. Each of the memory 2114 and the memory 2124 may include a random-access memory (RAM), such as dynamic RAM (DRAM), static RAM (SRAM), thyristor RAM (T-RAM), and / or zero-capacitor RAM (Z-RAM). Alternatively, each of the memory 2114 and the memory 2124 may include a read-only memory (ROM), such as a mask ROM, a programmable ROM (PROM), an erasable programmable ROM (EPROM), and / or an electrically erasable programmable ROM (EEPROM). Alternatively, each of memory 2114 and memory 2124 may include a non-volatile random-access memory (NVRAM), such as flash memory, solid-state memory, ferroelectric RAM (FeRAM), magnetoresistive RAM (MRAM), and / or phase-change memory.

[0078] Each of device 2110 and device 2120 can be a communication entity capable of communicating with each other using various proposed schemes according to the present invention. For illustrative purposes and not limitation, a description of the capabilities of device 2110 (as STA 110) and device 2120 (as STA 120) is provided below in the context of example processes 2200 and 2300. It is worth noting that although detailed descriptions of the capabilities, functions, and / or technical features of either device 2110 or device 2120 are provided below, these descriptions can also be applied to the other of device 2110 and device 2120, although a detailed description thereof is not provided for the sake of brevity. It is also worth noting that although the example embodiments described below are provided in the context of a WLAN, these example embodiments can also be implemented in other types of networks.

[0079] Example Process

[0080] Figure 22 An example process 2200 is shown according to an embodiment of the present invention. The process 2200 may represent one aspect of implementing the various proposed designs, concepts, schemes, systems and methods described above. More specifically, the process 2200 may represent one aspect related to the concepts and schemes proposed in the present invention regarding the signaling design of UHR transmission in wireless communications. The process 2200 may include one or more operations, actions or functions, as shown by one or more boxes 2210 and sub-boxes 2212 and 2214. Although shown as separate boxes, the various boxes of the process 2200 may be divided into more boxes, combined into fewer boxes, or eliminated, depending on the desired implementation. In addition, the boxes / sub-boxes of the process 2200 may be arranged as follows: Figure 22 2. The process 2200 is performed in the order shown, or may be performed in a different order. In addition, one or more blocks / subblocks of process 2200 may be repeated or performed repeatedly. Process 2200 may be implemented by apparatus 2110 and apparatus 2120, and any variants thereof. For illustrative purposes only and not limiting, process 2200 is described below in an environment where apparatus 2110 is implemented in or as STA110 (acting as a non-AP STA of a wireless network) and apparatus 2120 is implemented in or as STA120 (acting as an AP STA of a wireless network), such as a WLAN in network environment 100 according to one or more IEEE 802.11 standards. Process 2200 may begin at block 2210.

[0081] At 2210, process 2200 may involve processor 2112 of device 2110 performing wireless communications (e.g., with device 2120) with a PPDU via transceiver 2116. Performing wireless communications may be represented by 2212 and 2214. The wireless communications may be performed via signaling indicating UEQM information for one or more spatial streams associated with the PPDU transmission.

[0082] At 2212 , process 2200 may involve processor 2112 generating and sending a PPDU.

[0083] At 2214 , process 2200 may involve processor 2112 receiving and processing the PPDU.

[0084] In some embodiments, bit 19 (B19) of the User field for non-MU-MIMO allocations of the UHR-SIG field in the PPDU may indicate whether UEQM or EQM is applied to a spatial stream of the PPDU.

[0085] In some embodiments, in response to B19 indicating that UEQM is applied, bits 20 and 21 (B20-B21) of the User field for non-MU-MIMO allocation may indicate a UEQM mode, where the UEQM mode is indicated depending on the corresponding number of spatial streams indicated in the NSS field in the User field for non-MU-MIMO allocation.

[0086] In some embodiments, the number of bits in the User field for non-MU-MIMO allocations in the UHR-SIG field of the PPDU may be 23. In some embodiments, bits 11-15 (B11-B15) in the User field for non-MU-MIMO allocations in the UHR-SIG field of the PPDU may be used to indicate the MCS, and bits 16-18 (B16-B18) may be used as the NSS field, which are set to the number of spatial streams transmitted by the PPDU minus 1. In some embodiments, bit 22 (B22) in the User field for non-MU-MIMO allocations in the UHR-SIG field of the PPDU may be used to indicate whether the LDPC codeword length for the PPDU is 2x1944. For example, when bit B22 is set to 1, it may indicate that the LDPC codeword length is 2x1944. Additionally, when bit B22 is set to 0, it may indicate that the LDPC codeword length is less than and different from 2x1944. In some embodiments, bit 21 (B21) is set to 0 and bit 22 (B22) is set to 1 in the user field of the UHR-SIG field for non-MU-MIMO allocation in the PPDU may indicate that a new coding mode is used for the PPDU that is different from the BCC mode and the LDPC mode with a codeword length less than or equal to 2x1944.

[0087] In some embodiments, the common field for non-OFDMA in the UHR-SIG field of the PPDU may be 19 bits.

[0088] In some embodiments, the number of bits in the User Field for MU-MIMO Allocation within the UHR-SIG field of the PPDU may be 23. In some embodiments, bits 11-15 (B11-B15) in the User Field for MU-MIMO Allocation within the UHR-SIG field are used to indicate the MCS, and bits 16-19 (B16-B19) are used to indicate the spatial stream configuration. In some embodiments, one bit in the User Field for MU-MIMO Allocation within the UHR-SIG field is used to indicate whether the LDPC codeword length for the PPDU is 2x1944, wherein when the bit is set to 1, it indicates that the LDPC codeword length is 2x1944, and when the bit is set to 0, it indicates that the LDPC codeword length is less than and different from 2x1944. In some embodiments, this bit may be bit 22 (B22) in the User Field for MU-MIMO Allocation within the UHR-SIG field.

[0089] In some embodiments, bit 21 (B21) of the user field for MU-MIMO allocation in the UHR-SIG field of the PPDU is set to 0 and bit 22 (B22) is set to 1, indicating that a new coding mode different from the BCC mode and the LDPC mode with a codeword length less than or equal to 2x1944 is used for the PPDU.

[0090] Figure 23 An example process 2300 according to an embodiment of the present invention is shown. Process 2300 may represent one aspect of implementing the various designs, concepts, schemes, systems and methods proposed above. More specifically, process 2300 may represent one aspect of the proposed concepts and schemes for signaling design of UHR transmissions related to the present invention. Process 2300 may include one or more operations, actions or functions, as shown by one or more blocks 2310 and sub-blocks 2312 and 2314. Although shown as separate blocks, the various blocks of process 2300 may be divided into more blocks, combined into fewer blocks, or eliminated depending on the desired implementation. In addition, the blocks / sub-blocks of process 2300 may be arranged as follows: Figure 232. The process 2300 is performed in the order shown, or may be performed in a different order. In addition, one or more blocks / subblocks of process 2300 may be repeated or iteratively performed. Process 2300 may be implemented by apparatus 2110 and apparatus 2120, as well as variations thereof. For illustrative purposes only and not limiting, process 2300 is described below in an environment where apparatus 2110 is implemented in or as STA110 (acting as a non-AP STA of a wireless network) and apparatus 2120 is implemented in or as STA120 (acting as an AP STA of a wireless network), such as a WLAN in network environment 100 according to one or more IEEE 802.11 standards. Process 2300 may begin at block 2310.

[0091] At 2310, process 2300 may involve processor 2112 of device 2110 performing wireless communication (e.g., with device 2120) via transceiver 2116 with a trigger frame. The trigger frame is used to request a trigger-based (TB) PPDU. Performing wireless communication may be represented by 2312 and 2314.

[0092] At 2312 , process 2200 involves processor 2112 generating and sending a trigger frame.

[0093] At 2314 , process 2200 involves processor 2112 receiving and processing a trigger frame.

[0094] In some embodiments, bits 56-59 (B56-B59) in the UHR Common Information field of the trigger frame may be used to indicate a distributed resource unit (DRU) or a regular resource unit (RRU). Furthermore, each bit may indicate whether the requested 80 MHz frequency sub-block is for a DRU or an RRU. Bits 56-59 (B56-B59) in the UHR Common Information field of the trigger frame function as a 4-bit bitmap, with each bit in the 4-bit bitmap indicating whether the corresponding 80 MHz frequency sub-block is for a DRU or an RRU.

[0095] In some embodiments, bits 27-31 (B27-31) in the UHR User Info field in the trigger frame are used as the SS allocation field.

[0096] In some embodiments, in response to B56-59 indicating that the RRU is used (for example, B56-59 indicates that the RRU is used in the corresponding one or more 80 MHz frequency sub-blocks of the TB-PPDU), the first three bits of bits 27-31 (B27-31) in the UHR User Info field in the trigger frame indicate the starting spatial stream index, and the remaining two bits of bits 27-31 (B27-31) indicate the number of spatial streams.

[0097] In some embodiments, in response to B56-59 indicating that DRU is used (for example, B56-59 indicates that DRU is used in the corresponding one or more 80 MHz frequency sub-blocks of the TB-PPDU), the first two bits of bits 27-31 (B27-31) in the UHR user information field in the trigger frame indicate the distribution bandwidth, the last two bits of bits 27-31 (B27-31) are reserved bits, and the remaining one bit of bits 27-31 (B27-31) indicates the number of spatial streams.

[0098] In some embodiments, one bit in the UHR User Information field of the trigger frame can be used to indicate whether the LDPC codeword length of the TB PPDU is 2x1944. For example, when this bit is set to 1, it indicates that the LDPC codeword length is 2x1944. In addition, when this bit is set to 0, it indicates that the LDPC codeword length is less than and different from 2x1944. In some embodiments, this bit can be bit B26 of the UHR User Information field in the trigger frame.

[0099] In some embodiments, bit 20 (B20) is set to 0 and bit 26 (B26) is set to 1 in the UHR user information field of the trigger frame, which may indicate that a new coding mode is applied to the TB PPDU, which is different from the BCC mode and the LDPC mode with a codeword length less than or equal to 2x1944.

[0100] Additional Notes

[0101] The subject matter described herein sometimes illustrates different components contained within or connected to other different components. It should be understood that the architecture depicted in this manner is merely an example, and in fact many other architectures can be implemented to achieve the same functionality. In a conceptual sense, any component arrangement that achieves the same functionality is effectively "associated" so as to achieve the desired functionality. Therefore, any two components combined here to achieve a particular functionality can be considered to be "associated" with each other so as to achieve the desired functionality, regardless of the architecture or intermediate components. Similarly, any two components so associated can also be considered to be "operably connected" or "operably coupled" to each other to achieve the desired functionality, and any two components that can be so associated can also be considered to be "operably coupled" to each other to achieve the desired functionality. Specific examples of operable coupling include, but are not limited to, physically pairable and / or physically interacting components and / or wirelessly interactive and / or wirelessly interactive components and / or logically interacting and / or logically interacting components.

[0102] In addition, with respect to the use of substantially any plural and / or singular terms herein, those skilled in the art can translate from the plural to the singular and / or from the singular to the plural as appropriate to the context and / or application. For clarity, various singular / plural permutations may be expressly set forth herein.

[0103] Furthermore, those skilled in the art will appreciate that the terms used herein, and particularly in the appended claims, such as the bodies of the appended claims, are generally intended to be “open-ended” terms, e.g., the term “including” should be interpreted as “including but not limited to,” the term “comprising” should be interpreted as “including but not limited to,” the term “having” should be interpreted as “having at least,” etc. Those skilled in the art will further appreciate that if a specific number of an introduced claim element is intended, such intent will be explicitly recited in the claim, and in the absence of such recitation, such intent is absent. For example, to aid understanding, the appended claims may contain the use of the introductory phrases “at least one” and “one or more” to introduce claim elements. However, the use of such phrases should not be construed to imply that a claim element introduced by the indefinite article “a” or “an” is limited to any particular claim containing such introduced claim element to only one such element, even when the same claim contains the introductory phrases “one or more” or “at least one” and an indefinite article such as “a” or “an.” For example, “a” and / or “an” should be interpreted to mean “at least one” or “one or more.” The same applies to the use of definite articles used to introduce claim elements. Furthermore, even if a specific number of an introduced claim element is explicitly recited, one skilled in the art will recognize that such a statement should be interpreted to mean at least the recited number, e.g., the recitation "two elements" without other qualifiers means at least two elements or two or more elements. Furthermore, where similar "at least one of A, B, and C, etc." is used, for its purposes, generally such a construction will be understood by one skilled in the art to be the convention, e.g., "a system having at least one of A, B, and C" will include but is not limited to a system having A alone, B alone, C alone, A and B together, A and C together, B and C together, and / or A, B, and C together, etc. Where similar "at least one of A, B, or C, etc." is used, for its purposes, generally such a construction will be understood by one skilled in the art to be the convention, e.g., "a system having at least one of A, B, or C" will include but is not limited to a system having A alone, B alone, C alone, A and B together, A and C together, B and C together, and / or A, B, and C together, etc. Those skilled in the art will further understand that any transitional word and / or phrase that actually represents two or more alternatives, whether in the specification, claims, or drawings, should be understood to include the possibility of one of the multiple terms, any of the multiple terms, or both terms. For example, the phrase "A or B" will be understood to include the possibility of "A" or "B" or "A and B".

[0104] It will be appreciated that various embodiments of the present invention have been described herein for illustrative purposes and that various modifications may be made without departing from the scope and spirit of the present invention. Therefore, the various embodiments disclosed herein are not intended to be limiting, and the true scope and spirit of the present invention are determined by the appended claims.

Claims

1. A wireless communication method, comprising: The processor of the device performs wireless communication with a physical layer protocol data unit (PPDU) by any of the following means: Generate and send the PPDU; or Receive and process the PPDU.

2. The method according to claim 1, wherein Bit 19 of the User field for non-Multi-User Multiple Input Multiple Output (MU-MIMO) allocation of the Ultra High Reliability Signal (UHR-SIG) field in the PPDU indicates whether Unequal Modulation (UEQM) or Equal Modulation (EQM) is applied in the PPDU.

3. The method according to claim 2, wherein: In response to bit 19 indicating that UEQM is applied, bits 20 and 21 of the user field for non-MU-MIMO allocation indicate the UEQM mode, and the UEQM mode is indicated depending on the corresponding number of spatial streams indicated in the NSS field in the user field for non-MU-MIMO allocation.

4. The method according to claim 1, wherein The number of bits of the user field for non-MU-MIMO allocation in the UHR-SIG field in the PPDU is 23.

5. The method according to claim 4, wherein: Bits 11-15 in the user field for non-MU-MIMO allocation in the UHR-SIG field of the PPDU are used to indicate the MCS, and bits 16-18 serve as the NSS field and are set to the number of spatial streams used for transmission of the PPDU minus 1.

6. The method of claim 4, wherein: Bit 22 in the user field for non-MU-MIMO assignment in the UHR-SIG field is used to indicate whether the LDPC codeword length used for the PPDU is 2x1944, wherein when bit 22 is set to 1, it indicates that the LDPC codeword length is 2x1944, and when bit 22 is set to 0, it indicates that the LDPC codeword length is less than and different from 2x1944.

7. The method of claim 4, wherein: In the user field for non-MU-MIMO allocation in the UHR-SIG field, bit 21 is set to 0 and bit 22 is set to 1, indicating that a new coding mode other than the BCC mode and the LDPC mode with a codeword length less than or equal to 2×1944 is used for the PPDU.

8. The method of claim 1, wherein: The number of bits of the common field for non-OFDMA in the UHR-SIG field of the PPDU is 19 bits.

9. The method of claim 1, wherein: The number of bits of the user field for MU-MIMO allocation in the UHR-SIG field of the PPDU is 23.

10. The method of claim 9, wherein: Bits 11-15 of the user field for MU-MIMO allocation in the UHR-SIG field are used to indicate the MCS, and bits 16-19 are used to indicate the spatial stream configuration.

11. The method of claim 9, wherein: One bit in the user field for MU-MIMO allocation in the UHR-SIG field is used to indicate whether the LDPC codeword length for the PPDU is 2x1944, wherein when the bit is set to 1, it indicates that the LDPC codeword length is 2x1944, and when the bit is set to 0, it indicates that the LDPC codeword length is less than and different from 2x1944.

12. The method of claim 11, wherein: The bit is bit 22 of the user field for MU-MIMO allocation in the UHR-SIG field.

13. The method of claim 9, wherein: Bit 21 of the user field for MU-MIMO assignment in the UHR-SIG field of the PPDU is set to 0 and bit 22 is set to 1, indicating that a new coding mode other than the BCC mode and the LDPC mode with a codeword length less than or equal to 2×1944 is used for the PPDU.

14. A wireless communication method, comprising: The processor of the device performs wireless communication with the trigger frame by any of the following means: generating and sending the trigger frame; or The trigger frame is received and processed. The trigger frame is used to request a trigger-based TBPPDU.

15. The method of claim 14, wherein: Bits 56-59 in the UHR common information field of the trigger frame are used as a 4-bit bitmap, and each bit in the 4-bit bitmap indicates whether the corresponding 80 MHz frequency sub-block uses a distributed resource unit DRU or a regular resource unit RRU.

16. The method according to claim 15, wherein Bits 27-31 in the UHR user information field in the trigger frame are used as the SS allocation field.

17. The method according to claim 15, wherein: In response to bits 56-59 indicating that one or more 80 MHz frequency sub-block RRUs corresponding to the TB-PPDU are used, the first three bits of bits 27-31 in the user information field in the trigger frame indicate a starting spatial stream index, and the remaining two bits of bits 27-31 indicate the number of spatial streams.

18. The method according to claim 15, wherein In response to bits 56-59 indicating that one or more 80 MHz frequency sub-block DRUs corresponding to the TB-PPDU are used, the first two bits of bits 27-31 in the UHR user information field in the trigger frame indicate the distribution bandwidth, the last two bits of bits 27-31 are reserved bits, and the remaining one bit of bits 27-31 indicates the number of spatial streams.

19. The method of claim 14, wherein: One bit in the UHR user information field of the trigger frame is used to indicate whether the LDPC codeword length used for the TB PPDU is 2x1944, where when the bit is set to 1, it indicates that the LDPC codeword length is 2x1944, and when the bit is set to 0, it indicates that the LDPC codeword length is less than and not equal to 2x1944.

20. The method of claim 19, the bit is bit 26 in a UHR User Information field of the trigger frame.

21. The method of claim 14, wherein: Bit 20 is set to 0 and bit 26 is set to 1 in the UHR User Information field of the trigger frame, indicating that a new coding mode different from the BCC mode and the LDPC mode with a codeword length less than or equal to 2×1944 is used for the TB PPDU.

Images