User multiple-input multiple-output transmission

Abstract

To provide a communication device and a communication method for multi-user multiple-input multiple-output transmission.SOLUTION: A disclosed communication device includes: a circuit that generates a physical layer protocol data unit (PPDU) including a signal field representing resource unit (RU) allocation information for multiple other communication devices when operating; and a transmitter that transmits the PPDU to multiple other communication devices via two or more 80 MHz frequency segments when operating. When one of multiple other communication devices parks on one of two or more 80 MHz frequency segments, RU allocation information corresponding to one of the multiple other communication devices is shown in a signal field which is transmitted via one of two or more 80 MHz frequency segments.SELECTED DRAWING: Figure 6

Description

[Technical Field]

[0001] The present disclosure relates to a communication apparatus and method for multiple input multiple output (MIMO) transmission, and more particularly to a communication apparatus and method for multi-user multiple input multiple output (MU-MIMO) transmission in an extremely high throughput wireless local area network (EHT WLAN). [Background technology]

[0002] In the standardization of next-generation wireless local area networks (WLANs), a new wireless access technology that is backward compatible with IEEE 802.11a / b / g / n / ac / ax technologies is being discussed in the IEEE 802.11 working group and is named IEEE 802.11be Very High Throughput (EHT) WLAN.

[0003] IEEE 802.11be EHT WLAN is proposed to increase the maximum channel bandwidth to 320 MHz and the maximum number of spatial streams from 8 to 16 in order to improve spectral efficiency and provide significant peak throughput and capacity increases over 802.11ax high-efficiency (HE) WLAN.

[0004] However, there has been little discussion about communication devices and methods for efficient MU-MIMO transmission in EHT PPDUs with a maximum bandwidth of 320 MHz.

[0005] Therefore, what is needed is a communication apparatus and method that provides a viable technical solution for MU-MIMO in the context of EHT WLAN. Furthermore, other desirable features and characteristics will become apparent from the following detailed description and the appended claims, taken in conjunction with the accompanying drawings and this background of the disclosure. Summary of the Invention [Problem to be solved by the invention]

[0006] Non-limiting exemplary embodiments facilitate providing a communications apparatus and method for MU-MIMO transmission in the context of an EHT WLAN. [Means for solving the problem]

[0007] According to one embodiment of the present disclosure, a communications device is provided, comprising: a circuit that, in operation, generates a physical layer protocol data unit (PPDU) including a signal field indicating resource unit (RU) allocation information for a plurality of other communications devices; and a transmitter that, in operation, transmits the PPDU to the plurality of other communications devices on two or more 80 MHz frequency segments, wherein when one of the plurality of other communications devices parks on one of the two or more 80 MHz frequency segments, the RU allocation information corresponding to the one of the plurality of other communications devices is indicated in the signal field transmitted on one of the two or more 80 MHz frequency segments.

[0008] According to another embodiment of the present disclosure, there is provided a communications device comprising: a receiver that, in operation, receives a physical layer protocol data unit (PPDU) transmitted on two or more 80 MHz frequency segments, the PPDU including a signal field indicating resource unit (RU) allocation information for the communications device; and circuitry that, in operation, processes the PPDU, wherein when the communications device parks on one of the two or more 80 MHz frequency segments, the RU allocation information corresponding to the communications device is indicated in the signal field transmitted on one of the two or more 80 MHz frequency segments.

[0009] According to yet another embodiment of the present disclosure, there is provided a communication method, including: generating a physical layer protocol data unit (PPDU) including a signal field indicating resource unit (RU) allocation information for a plurality of other communication devices; and transmitting the PPDU to the plurality of other communication devices on two or more 80 MHz frequency segments, wherein if one of the plurality of other communication devices parks on one of the two or more 80 MHz frequency segments, the RU allocation information corresponding to the one of the plurality of other communication devices is indicated in the signal field transmitted on one of the two or more 80 MHz frequency segments.

[0010] It should be noted that the general or specific embodiments may be implemented as a system, a method, an integrated circuit, a computer program, a storage medium, or any selective combination thereof.

[0011] Further benefits and advantages of the disclosed embodiments will become apparent from the specification and drawings. Benefits and / or advantages may be obtained individually by various embodiments and features of the specification and drawings, and it is not necessary for all of them to be provided to obtain one or more of such benefits and / or advantages.

[0012] Embodiments of the present disclosure will be better understood and readily apparent to those skilled in the art from the following written description, by way of example only, taken in conjunction with the drawings in which: [Brief explanation of the drawings]

[0013] [Figure 1A] 1 is a schematic diagram of uplink and downlink single-user (SU) multiple-input multiple-output (MIMO) communication between an access point (AP) and a station (STA) in a MIMO wireless network. [Figure 1B] 1 is a schematic diagram of downlink multi-user (MU) communication between an AP and multiple STAs in a MIMO wireless network. [Figure 1C] 1 is a schematic diagram of trigger-based uplink MU communication between an AP and multiple STAs in a MIMO wireless network. [Figure 1D] 1 is a schematic diagram of trigger-based downlink multi-AP communication between multiple APs and STAs in a MIMO wireless network. [Figure 1E] 1 is a diagram showing the format of a PPDU (physical layer protocol data unit) used for downlink multi-user (MU) communication between an AP and multiple STAs in a HE WLAN. FIG. [Figure 1F] FIG. 10 shows the HE-SIG-B (HE Signal B) field in more detail. [Figure 2A] A diagram showing an exemplary format of an EHT basic PPDU. [Figure 2B] FIG. 1 illustrates a pre-EHT modulation field of an EHT basic PPDU with a bandwidth of 320 MHz according to one embodiment. [Figure 3] FIG. 1 illustrates an exemplary format of an EHT-SIG content channel. [Figure 4A] A diagram showing an example format of the common field of the EHT-SIG field of an EHT basic PPDU having a bandwidth of 320 MHz. [Figure 4B]A diagram showing an example format of the common field of the EHT-SIG field of an EHT basic PPDU having a bandwidth of 320 MHz. [Figure 5A] A diagram showing an example format of the common field of the EHT-SIG field of an EHT basic PPDU having a bandwidth of 320 MHz. [Figure 5B] A diagram showing an example format of the common field of the EHT-SIG field of an EHT basic PPDU having a bandwidth of 320 MHz. [Figure 6] 1 illustrates a simplified example of a communication device according to various embodiments. According to the present disclosure, the communication device may be implemented as an AP or a STA and configured for MU-MIMO transmission. [Figure 7] 1 is a flow diagram illustrating a communication method according to the present disclosure. [Figure 8] FIG. 1 illustrates an exemplary RU allocation under a 320 MHz bandwidth, according to one embodiment. [Figure 9] FIG. 1 is a diagram illustrating the configuration of a communication device such as an AP according to the present disclosure. [Figure 10] FIG. 1 illustrates the configuration of a communication device such as a STA according to the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0014] Those skilled in the art will appreciate that elements in the figures are illustrated for simplicity and clarity and have not necessarily been drawn to scale. For example, the dimensions of some elements in figures, block diagrams, or flowcharts may be exaggerated relative to other elements to help understand embodiments of the present invention.

[0015] Some embodiments of the present disclosure will now be described, by way of example only, with reference to the drawings in which like reference numbers and letters indicate similar or equivalent elements.

[0016] The following paragraphs describe certain exemplary embodiments with particular reference to access points (APs) and stations (STAs) for uplink or downlink control signaling in a multiple-input multiple-output (MIMO) wireless network.

[0017] In the context of IEEE 802.11 (Wi-Fi) technology, a station, synonymously referred to as a STA, is a communication device capable of using the 802.11 protocol. Based on the definition in IEEE 802.11-2016, a STA can be any device that includes an IEEE 802.11-compliant media access control (MAC) and physical layer (PHY) interface to the wireless medium (WM).

[0018] For example, an STA may be a laptop, a desktop personal computer (PC), a personal digital assistant (PDA), an access point, or a Wi-Fi phone in a wireless local area network (WLAN) environment. STAs may be fixed or mobile. In a WLAN environment, the terms "STA," "wireless client," "user," "user device," and "node" are often used interchangeably.

[0019] Similarly, an AP, which may be synonymously referred to as a wireless access point (WAP) in the context of IEEE 802.11 (Wi-Fi) technology, is a communications device that allows STAs in a WLAN to connect to a wired network. APs typically connect to a router (via the wired network) as standalone devices, but can also be integrated into or used within a router.

[0020] As mentioned above, a STA in a WLAN may function as an AP at other times, and vice versa. This is because a communication device in the context of IEEE 802.11 (Wi-Fi) technology may include both STA and AP hardware components. In this manner, the communication device may switch between STA mode and AP mode based on actual WLAN conditions and / or requirements.

[0021] In a MIMO wireless network, "multiple" refers to multiple antennas used simultaneously for transmission and multiple antennas used simultaneously for reception over a wireless channel. In this regard, "multiple-input" refers to multiple transmit antennas that input wireless signals into a channel, and "multiple-output" refers to multiple receive antennas that receive wireless signals from the channel to a receiver. For example, in an N×M MIMO network system, N is the number of transmit antennas and M is the number of receive antennas, and N may or may not be equal to M. For simplicity, the respective numbers of transmit and receive antennas will not be further discussed in this disclosure.

[0022] In a MIMO wireless network, single-user (SU) and multi-user (MU) communications can be deployed for communication between communication devices such as APs and STAs. MIMO wireless networks have advantages such as spatial multiplexing and spatial diversity, which enable higher data rates and robustness through the use of multiple spatial streams. According to various embodiments, the term "spatial stream" may be used interchangeably with the term "space-time stream" (i.e., STS).

[0023] FIG. 1A shows a schematic diagram of SU communication 100 between an AP 102 and a STA 104 in a MIMO wireless network. As shown, the MIMO wireless network may include one or more STAs (e.g., STA 104, STA 106, etc.). When SU ​​communication 100 on a channel is performed across the entire channel bandwidth, it is referred to as full-bandwidth SU communication. When SU ​​communication 100 on a channel is performed across a portion of the channel bandwidth (e.g., one or more 20 MHz subchannels in the channel are punctured), it is referred to as punctured SU communication. In SU communication 100, the AP 102 transmits multiple space-time streams using multiple antennas (e.g., four antennas shown in FIG. 1A), and all space-time streams are directed to a single communication device, i.e., the STA 104. For simplicity, the multiple space-time streams directed to the STA 104 are depicted as a grouped data transmission arrow 108 directed to the STA 104.

[0024] SU communication 100 can be configured for bidirectional transmission. As shown in FIG. 1A, in SU communication 100, STA 104 may transmit multiple space-time streams using multiple antennas (e.g., two antennas shown in FIG. 1A), with all space-time streams directed to AP 102. For simplicity, the multiple space-time streams directed to AP 102 are shown as grouped data transmission arrows 110 directed to AP 102.

[0025] Thus, the SU communication 100 shown in FIG. 1A enables both uplink and downlink SU transmission in a MIMO wireless network.

[0026] 1B shows a schematic diagram of downlink MU communication 112 between an AP 114 and multiple STAs 116, 118, and 120 in a MIMO wireless network. The MIMO wireless network may include one or more STAs (e.g., STA 116, STA 118, STA 120, etc.). The MU communication 112 can be orthogonal frequency division multiple access (OFDMA) communication or MU-MIMO communication. In the case of OFDMA communication over a channel, the AP 114 simultaneously transmits multiple streams to the STAs 116, 118, and 120 in the network in different resource units (RUs) within the channel bandwidth. In the case of MU-MIMO communication over a channel, the AP 114 uses multiple antennas to simultaneously transmit multiple streams to the STAs 116, 118, and 120 in the same RU(s) within the channel bandwidth using spatial mapping or precoding techniques. When RU(s) performing OFDMA or MU-MIMO communication occupy the entire channel bandwidth, the OFDMA or MU-MIMO communication is referred to as full-bandwidth OFDMA or MU-MIMO communication. When RU(s) performing OFDMA or MU-MIMO communication occupy a portion of the channel bandwidth (e.g., one or more 20 MHz subchannels in the channel are punctured), the OFDMA or MU-MIMO communication is referred to as punctured OFDMA or MU-MIMO communication. For example, two space-time streams may be directed to STA 118, another space-time stream may be directed to STA 116, and yet another space-time stream may be directed to STA 120. For simplicity, the two space-time streams directed to STA 118 are shown as grouped data transmission arrow 124, the space-time stream directed to STA 116 is shown as data transmission arrow 122, and the space-time stream directed to STA 120 is shown as data transmission arrow 126.

[0027] To enable uplink MU transmissions, trigger-based communication is provided in the MIMO wireless network. In this regard, Figure 1C shows a schematic diagram of trigger-based uplink MU communication 128 between an AP 130 and multiple STAs 132, 134, 136 in a MIMO wireless network.

[0028] Because there are multiple STAs 132, 134, 136 participating in trigger-based uplink MU communications, the AP 130 must coordinate the simultaneous transmissions of the multiple STAs 132, 134, 136.

[0029] 1C , the AP 130 simultaneously transmits trigger frames 139, 141, and 143 to the STAs 132, 134, and 136 to indicate user-specific resource allocation information (e.g., the number of space-time streams, the starting STS number, and the assigned RU) that each STA can use. In response to the trigger frames, the STAs 132, 134, and 136 may simultaneously transmit their respective space-time streams to the AP 130 according to the user-specific resource allocation information indicated in the trigger frames 139, 141, and 143. For example, two space-time streams may be directed from the STA 134 to the AP 130, another space-time stream may be directed from the STA 132 to the AP 130, and yet another space-time stream may be directed from the STA 136 to the AP 130. For simplicity, the two space-time streams directed from STA 134 to AP 130 are shown as grouped data transmission arrow 140, the space-time stream directed from STA 132 to AP 130 is shown as data transmission arrow 138, and the space-time stream directed from STA 136 to AP 130 is shown as data transmission arrow 142.

[0030] Trigger-based communication is also provided in MIMO wireless networks to enable downlink multi-AP communication. In this regard, Figure 1D shows a schematic diagram of downlink multi-AP communication 144 between a STA 150 and multiple APs 146, 148 in a MIMO wireless network.

[0031] Since there are multiple APs 146, 148 participating in trigger-based downlink multi-AP MIMO communication, the master AP 146 needs to coordinate the simultaneous transmissions of the multiple APs 146, 148.

[0032] To do so, as shown in FIG. 1D , the master AP 146 simultaneously transmits trigger frames 147, 153 to the AP 148 and the STA 150 to indicate AP-specific resource allocation information (e.g., the number of space-time streams, the starting STS number, and the assigned RU) that each AP can use. In response to the trigger frames, the multiple APs 146, 148 may transmit their respective space-time streams to the STA 150 according to the AP-specific resource allocation information indicated in the trigger frame 147, and the STA 150 may receive all the space-time streams according to the AP-specific resource allocation information indicated in the trigger frame 153. For example, two space-time streams may be directed from the AP 146 to the STA 150, and two other space-time streams may be directed from the AP 148 to the STA 150. For simplicity, the two space-time streams directed from the AP 146 to the STA 150 are shown as grouped data transmission arrow 152, and the two space-time streams directed from the AP 148 to the STA 150 are shown as grouped data transmission arrow 154.

[0033] Due to the packet / PPDU (Physical Layer Protocol Data Unit) based transmission and distributed MAC (medium access control) scheme in 802.11 WLAN, time scheduling (e.g., periodic time slot allocation for data transmission like TDMA (time division multiple access)) does not exist in 802.11 WLAN. Scheduling of frequency and spatial resources is performed on a packet-by-packet basis. In other words, resource allocation information is on a PPDU-by-PPDU basis.

[0034] 1E illustrates the format of a PPDU 160 used for downlink MU communications between an AP and multiple STAs in an HE WLAN, such as OFDMA (Orthogonal Frequency Division Multiple Access) transmissions, including MU-MIMO transmissions in a single RU and full-bandwidth MU-MIMO transmissions. Such a PPDU 160 is referred to as an HE MU PPDU 160. The HE MU PPDU 160 may include a non-High Throughput Short Training Field (L-STF), a non-High Throughput Long Training Field (L-LTF), a non-High Throughput Signal (L-SIG) field, a Repeated L-SIG (RL-SIG) field, an HE Signal A (HE-SIG-A) field 162, an HE Signal B (HE-SIG-B) field 166, an HE Short Training Field (HE-STF), an HE Long Training Field (HE-LTF), a Data field 170, and a Packet Extension (PE) field. In the HE MU PPDU 160, the HE-SIG-B field 166 provides OFDMA and MU-MIMO resource allocation information, allowing STAs to look up the corresponding resources used in the Data field 160, as indicated by arrow 168. The HE-SIG-A field 162 contains information necessary to decode the HE-SIG-B field 166, such as the modulation and coding scheme (MCS) of the HE-SIG-B and the number of HE-SIG-B symbols, as indicated by arrow 164.

[0035] FIG. 1F shows the HE-SIG-B field 166 in more detail. The HE-SIG-B field 166 includes (or consists of) a common field 172 followed by a user-specific field 174, if present, collectively referred to as the HE-SIG-B content channel. The HE-SIG-B field 166 includes an RU assignment subfield that indicates RU information for each assignment. The RU information includes the RU location in the frequency domain, an indication of the RU assigned for non-MU-MIMO or MU-MIMO assignment, and the number of users in the MU-MIMO assignment. In the case of full-bandwidth MU-MIMO transmission, the common field 172 is not present. In this case, the RU information (e.g., the number of users in the MU-MIMO assignment) is signaled in the HE-SIG-A field 162.

[0036] User-specific field 174 includes (or consists of) one or more user field(s) for non-MU-MIMO assignment(s) and / or MU-MIMO assignment(s). The user fields include user information indicating user-specific assignments (i.e., user-specific assignment information). In the example shown in FIG. 1F, user-specific field 174 includes five user fields (user field 0, ..., user field 4), where user-specific assignment information for an assignment (allocation 0) is provided by user field 0, user-specific assignment information for a further assignment (allocation 1 for three MU-MIMO users) is provided by user field 1, user field 2, and user field 3, and user-specific assignment information for yet another assignment (allocation 2) is provided by user field 4.

[0037] When a MIMO wireless network has ultra-high throughput, such as an 802.11be EHT WLAN, the PPDU used for downlink MU transmission, downlink SU transmission, or uplink SU transmission may be referred to as an EHT basic PPDU 200, as shown in FIG. 2A.

[0038] According to various embodiments, an EHT WLAN supports non-triggered communication, as shown in Figures 1A and 1B, in which a communication device unilaterally transmits a PPDU to one other communication device or to two or more other communication devices.

[0039] 2A shows an example format of an EHT basic PPDU 200 that can be used for non-trigger-based communications. The EHT basic PPDU 200 may include an L-STF, an L-LTF, an L-SIG field, an RL-SIG field 201, a Universal Signal (U-SIG) field 202, an EHT Signal (EHT-SIG) field 204, an EHT-STF, an EHT-LTF, a data field 210, and a PE field. The L-STF, L-LTF, an L-SIG field, an RL-SIG field, an U-SIG field, and an EHT-SIG field may be grouped as a pre-EHT modulation field, and the EHT-STF, EHT-LTF, a data field, and a PE field may be grouped as an EHT modulation field. Both the U-SIG field 202 and the EHT-SIG field 204 are present in the EHT basic PPDU 200 transmitted to a single STA or multiple STAs. It is understood that if the IEEE 802.11 working group uses a new name for the next-generation WLAN with ultra-high throughput instead of "EHT WLAN," the prefix "EHT" in the above fields may change accordingly. The RL-SIG field 201 is primarily used to identify the PHY version starting with 802.11be. The U-SIG field 202, as indicated by arrow 204, contains information necessary for decoding the EHT-SIG field 204, such as the MCS of the EHT-SIG and the number of EHT-SIG symbols. The U-SIG field 202 and the EHT-SIG field 204 provide information necessary for decoding the data field 210, as indicated by arrows 207 and 208, respectively. When the EHT basic PPDU 200 is transmitted to multiple STAs, the EHT-SIG field 204 provides OFDMA and MU-MIMO resource allocation information to allow the STAs to determine the corresponding resources used in the data field 210.

[0040] According to various embodiments, the U-SIG field 202 has a duration of two orthogonal frequency-division multiplexing (OFDM) symbols. The data bits in the U-SIG field 202 are jointly coded and modulated in the same manner as the HE-SIG-A field of 802.11ax. The modulated data bits in the U-SIG field 202 are mapped to 52 data tones in each of the two OFDM symbols and replicated for each 20 MHz in each 80 MHz frequency segment in the same manner as the HE-SIG-A field of 802.11ax. The U-SIG field 202 may carry different information for each of the 80 MHz frequency segments. According to various embodiments, the term "frequency segment" may be used synonymously with the term "subchannel." A frequency segment may also be referred to as a frequency subblock.

[0041] In various embodiments, U-SIG field 202 may include two parts, U-SIG field 1 and U-SIG field 2, each containing 26 data bits. U-SIG field 202 includes all version-independent bits and a portion of version-dependent bits. All version-independent bits are included in U-SIG field 1 and have static positions and bit definitions across various physical layer (PHY) versions. The version-independent bits include a PHY version identifier (3 bits), a bandwidth (BW) field (3 bits), an uplink / downlink (UL / DL) flag (1 bit), a basic service set (BSS) color (e.g., 6 bits), and a transmission opportunity (TXOP) duration (e.g., 7 bits). The PHY version identifier in the version-independent bits is used to identify the exact PHY version starting with 802.11be, and the BW field is used to indicate the PPDU bandwidth. The effect of including all version-independent bits as part of the U-SIG field 202, i.e., U-SIG field 1, is that power efficiency can be improved since legacy STAs only need to parse U-SIG field 1. On the other hand, the version-dependent bits may have variable bit definitions for each PHY version. The portion of version-dependent bits included in the U-SIG field 202 may include PPDU format, punctured channel information, pre-FEC padding factor, PE disambiguity, and EHT-SIG-related bits used to interpret the EHT-SIG field 204, as well as spatial reuse-related bits used for coexistence with unintended STAs.

[0042] The EHT-SIG field 204 of the EHT basic PPDU 200 may contain the remaining version-dependent bits. It has a variable MCS and variable length. The EHT-SIG field 504 has a common field followed by a user-specific field, collectively referred to as the EHT-SIG content channel. The user-specific field contains one or more user fields. The common field may contain one or more RU allocation subfields that indicate RU allocation information for one or more STAs. The EHT-SIG field may vary for each 80 MHz frequency segment.

[0043] FIG. 2B shows a pre-EHT modulation field of an EHT basic PPDU 200 in a 320 MHz bandwidth according to one embodiment. The 320 MHz bandwidth includes four 80 MHz frequency segments and sixteen 20 MHz frequency segments (each 80 MHz frequency segment has four 20 MHz frequency segments). The U-SIG field 202 may carry different information for each of the four 80 MHz frequency segments. In other words, the U-SIG1, U-SIG2, U-SIG3, and U-SIG4 fields may be transmitted in each of the four 80 MHz frequency segments. The EHT-SIG field 204 may be different for each of the four 80 MHz frequency segments. In other words, the EHT-SIG1, EHT-SIG2, EHT-SIG3, and EHT-SIG4 fields may be transmitted in each of the four 80 MHz frequency segments. Additionally, the EHT-SIG field 204 of each 80 MHz frequency segment includes two EHT-SIG content channels (CC1 and CC2), each of which is replicated in every other 20 MHz subchannel within the 80 MHz frequency segment, as shown in FIG. 2B.

[0044] 3 illustrates an exemplary EHT-SIG content channel 300 including a common field 302 and a user-specific field 304. In one embodiment, the user-specific field 304 may be comprised of one or more user block field(s), with each user block field including one or two user fields. In this embodiment, user block field 1 includes two user fields, such as user field 1 and user field 2, user block field 2 includes two user fields, such as user field 3 and user field 4, and user block field 3 includes one user field 5, with a CRC field and tail bits added to each of the one or two user fields in user block fields 1-3 for error detection. In one embodiment, the last user block may be comprised of one or two user fields, depending on whether the total number of user fields allowed in the user-specific fields is odd or even.

[0045] According to various embodiments, the user-specific field may include multiple user fields, e.g., user fields 1-5, where each user field includes transmission parameters corresponding to the STA to which the corresponding RU or RU combination is assigned. For an RU or RU combination assigned for non-MU-MIMO transmission, there is a single corresponding user field, and for an RU or RU combination assigned for MU-MIMO transmission with N users, there are N corresponding user fields.

[0046] According to the present disclosure, there are two options for the common field 302 of the EHT-SIG field 204: Option 1 and Option 2. For common field Option 1, the common field 302 may include a header subfield 306, one or more RU allocation subfields 308, followed by a CRC field and tail bits. The number of bits in the header subfield 306 may depend on the bandwidth. For example, the header subfield 306 may be absent in a 20 MHz, 40 MHz, or 80 MHz bandwidth PPDU, and the header subfield 306 may have 8 bits for a 160 MHz bandwidth PPDU, 12 bits for a 240 MHz bandwidth PPDU, or 16 bits for a 320 MHz bandwidth PPDU. In various embodiments, the position of a "1" bit in the header subfield 306 indicates the start of the RU allocation(s) specified by each RU allocation subfield, and the total number of "1" bits in the header subfield 306 represents the total number of RU allocation subfields in the common field 302. The header subfield values ​​for each 80 MHz frequency segment can be different, advantageously allowing flexible indication and efficient signaling of RUs at any location.

[0047] The RU Allocation subfield 308 indicates one or more RU allocations, including the size of the RU(s) or RU combination(s) and their placement in the frequency domain, used in the EHT modulation field of the EHT Basic PPDU 200, and indicates the information necessary to calculate the number of users assigned to each RU or RU combination. The number N of RU Allocation subfields may be different for each 80 MHz frequency segment or each content channel.

[0048] In various embodiments of the present disclosure, a STA parks on an 80 MHz frequency segment, which is referred to as the listening 80 MHz frequency segment (L80). The STA's L80 may be the primary 80 MHz (P80) by default, or the STA's L80 may be an 80 MHz frequency segment other than P80 through a negotiation procedure between the STA and the AP. If a STA parks on an 80 MHz subchannel other than the primary 80 MHz, the STA's operation may be referred to as subchannel selective transmission (SST) operation. The RU allocation information for a STA is fully indicated in the EHT-SIG field transmitted in the STA's L80. As a result, the STA can obtain all of its RU allocation information by simply processing the pre-EHT modulation field transmitted in the STA's L80, and the STA's power consumption may be reduced.

[0049] In one embodiment, in an 80 MHz frequency segment with compressed mode enabled, the header subfield and the RU allocation subfield are absent in the common field. Such compressed mode in an 80 MHz frequency segment can be enabled if all STA(s) parked on the 80 MHz frequency segment are involved in non-OFDMA transmission. Non-OFDMA transmission refers to MU-MIMO transmission or SU transmission.

[0050] According to various embodiments, the MU-MIMO allocation for an RU or RU combination in the EHT basic PPDU is limited to a maximum of 16 spatial streams and a maximum of 8 users (i.e., N user≤ 8), the maximum number of spatial streams per user is 4, and the minimum RU size to support MU-MIMO is 242-tone RU. The EHT basic PPDU allows allocation of more than two RUs to a single STA. In various embodiments where an RU with a size of 242 tones or greater is defined as a large-size RU and an RU with a size of less than 242 tones is defined as a small-size RU, allowed small-size RU combinations may include (i) two adjacent 26-tone RUs (RU26) and 52-tone RUs (RU52) in a 20 MHz subchannel, and (ii) two adjacent RUs 26 and 106-tone RUs (RU106) in a 20 MHz subchannel, and allowed large-size RU combinations may include (i) one 242-tone RU (RU242) and one 484-tone RU (RU484) in an 80 MHz frequency segment, (ii) one RU484 and one 996-tone RU (RU996) in a 160 MHz frequency segment, and (iii) three RUs 996 in a 320 MHz channel. Tables 4-6 show values ​​for the RU allocation subfield 308 signaling allocation of small size RUs, small size RU combinations, large size RUs, and large size RU combinations, respectively, according to one embodiment.

[0051] In this embodiment, according to Tables 4 to 6, #1 to #9 (from left to right in the table) are arranged in order of increasing absolute frequency. Among the RU allocation subfield values ​​of 32 to 54, a 78-tone RU (RU78) and a 132-tone RU (RU132) refer to two permitted small-size RU combinations of two adjacent RUs 26 and 52 and two adjacent RUs 26 and 106 in a 20 MHz subchannel, respectively. For signaling RUs or RU combinations with sizes larger than 242 tones, the last three digits of the letters y2y1y0 or the binary vector of the RU allocation subfield value may indicate the number of user fields in the EHT-SIG content channel that contain the corresponding RU allocation subfield. Otherwise, the binary vector y2y1y0 indicates the number of users multiplexed in the 242-tone RU. In one embodiment, the number of users N multiplexed in RU r or RU combination r is user (r) can be calculated based on the following formula:

[0052] N user (r)=4×y2+2×y1+y0+1 Equation (1) In other words, for a large size RU r or a large size RU combination r, if the character y2y1y0 is present in the RU assignment subfield, then N user (r) is indicated by its letter, and if the letter y2y1y0 is not present, N user (r) is 0. For small size RU r or small size RU combination r, the number of user fields N user (r) is 1. In one embodiment, a "-" in Tables 4 to 6 indicates that the RU is not assigned to a user, i.e., N user This means that (r)=0.

[0053] 4A shows example common fields for EHT-SIG Content Channel 1 (CC1) 402 and EHT-SIG Content Channel 2 (CC2) 404 transmitted in 80 MHz frequency segments used to signal large-size RU allocations and large-size RU combination allocations in a 320 MHz BW PPDU. In this example, three RUs or RU combinations are allocated: (i) a large-size RU allocation (RA1) 406 in the first and second 80 MHz frequency segments for MU-MIMO transmissions with four users, (ii) a large-size RU combination allocation (RA2) 408 in the third 80 MHz frequency segment for non-MU-MIMO transmissions, and (iii) a large-size RU allocation (RA3) 410 in the second 20 MHz subchannel of the third 80 MHz frequency segment for non-MU-MIMO transmissions. For a 320 MHz BW PPDU, CC1 and CC2 transmitted in the 80 MHz frequency segment each include a header subfield with 16 bits b0 to b15 and one or more RU allocation subfields indicating RU allocation information. The position of bit "1" in the header subfield indicates the starting point of the RU allocation(s) specified by each RU allocation subfield, and the RU allocation subfields indicate one or more RU allocations, including the size of the RU(s) or RU combination(s) and their placement in the frequency domain, used in the EHT modulation field of the 320 MHz BW PPDU.

[0054] In CC1 402, bits “1” are placed in b2 and b8 of its header subfield, indicating that the number of RU allocation subfields in CC1 402 is two and that the RU allocations specified by the two RU allocation subfields 412, 414 start from the third 20 MHz subchannel in the first 80 MHz frequency segment and the first 20 MHz subchannel in the third 80 MHz frequency segment, respectively. According to Tables 4-6, the first RU allocation subfield 412 of CC1 402 has a value of 169, indicating the allocation of an RU combination of a 484-tone RU and a 996-tone RU in a 160 MHz frequency segment, which contributes two user fields to the user-specific field of CC1 402. The second RU allocation subfield 414 of CC1 402 has a value of 128, indicating the allocation of an RU combination of a 242-tone RU and a 484-tone RU in an 80 MHz frequency segment, which contributes one user field to the user-specific field of CC1 402.

[0055] In contrast, in CC2 404, bits “1” are placed in b2 and b9 of the header subfield, indicating that the number of RU allocation subfields is two and that the RU allocations specified by the two RU allocation subfields 416, 418 start from the third 20 MHz subchannel in the first 80 MHz frequency segment and the second 20 MHz subchannel in the third 80 MHz frequency segment, respectively. Similar to CC1, the first RU allocation subfield 416 of CC2 404 has a value of 169, indicating an RU combination allocation of 484-tone RUs and 996-tone RUs in a 160 MHz frequency segment, which contributes two user fields to the user-specific field of CC2 404. The second RU allocation subfield 418 of CC2 404 has a value of 64, indicating a single RU allocation, which contributes one user field to the user-specific field of CC2 404. Note that for load balancing purposes, CC1 402 and CC2 404 each have three user fields in the user specific fields.

[0056] 4B shows example common fields in EHT-SIG CC1 422 and CC2 424 transmitted in 80 MHz frequency segments used to signal a mix of small- and large-size RU or RU combination allocations in a 320 MHz BW PPDU. In this example, five RU or RU combinations are allocated: (i) a large-size RU allocation (RA1) 426 for MU-MIMO transmission with four users in the first and second 80 MHz frequency segments, (ii) a large-size RU allocation (RA2) 428 in the third 80 MHz frequency segment, and (iii) three small-size RU or RU combination allocations (RA3-RA5) 430 in the second 20 MHz subchannel of the third 80 MHz frequency segment.

[0057] In CC1 422, bits "1" are placed in b2 and b8 of its header subfield, indicating that the number of RU allocation subfields in CC1 422 is two and that the RU allocations specified by the two RU allocation subfields 432, 434 start from the third 20 MHz subchannel in the first 80 MHz frequency segment and the first 20 MHz subchannel in the third 80 MHz frequency segment, respectively. According to Tables 4-6, the first RU allocation subfield 432 of CC1 422 has a value of 170, indicating the allocation of an RU combination of 484-tone RUs and 996-tone RUs in a 160 MHz frequency segment, which contributes three user fields to the user-specific field of CC1 422. The second RU allocation subfield 434 of CC1 422 has a value of 128, indicating the allocation of an RU combination of 242-tone RUs and 484-tone RUs in an 80 MHz frequency segment, which contributes one user field to the user-specific field of CC1 422.

[0058] On the other hand, in CC2 424, bits “1” are placed in b2 and b9 of the header subfield, indicating that the number of RU allocation subfields is two and that the RU allocations specified by the two RU allocation subfields 436 and 438 start from the third 20 MHz subchannel in the first 80 MHz frequency segment and the second 20 MHz subchannel in the third 80 MHz frequency segment, respectively. According to Tables 4-6, the first RU allocation subfield 432 of CC1 424 has a value of 168, indicating allocation of an RU combination of a 484-tone RU and a 996-tone RU in the 160 MHz frequency segment, which contributes one user field to the user-specific field of CC2 424. The second RU allocation subfield 438 of CC2 424 has a value of 46, indicating three small-size RUs or RU combinations of a 132-tone RU and two 52-tone RUs, which contribute three user fields to the user-specific field of CC2 424. Note that for load balancing purposes, CC1 422 and CC2 424 each have four user fields in their user specific fields.

[0059] For common field option 2, the common field 302 includes one or more RU allocation subfields 310, followed by a CRC field and tails bits, but does not include a header subfield. The number N of RU allocation subfields depends on the bandwidth. For example, a 20 MHz or 40 MHz BW PPDU has one RU allocation subfield, an 80 MHz BW PPDU has two, a 160 MHz BW PPDU has four, a 240 MHz BW PPDU has six, and a 320 MHz BW PPDU has eight. The RU allocation subfield 310 indicates the RU allocation(s) used in the EHT modulation field of the PPDU, including the size of the RU(s) or RU combinations and their placement in the frequency domain, as well as information necessary to calculate the number of users assigned to each RU or RU combination. According to this disclosure, the subcarrier index of an RU(s) or RU combination(s) shall be within the corresponding 20 MHz subchannel or shall overlap with the corresponding 20 MHz subchannel if the RU or RU combination is greater than 242-tone RU.

[0060] In one embodiment, in an 80 MHz frequency segment with compressed mode enabled, the RU Allocation subfield(s) are not present. Such compressed mode in an 80 MHz frequency segment can be enabled if all STA(s) parked on the 80 MHz frequency segment engage in non-OFDMA transmissions.

[0061] 5A shows example common fields in EHT-SIG CC1 502 and CC2 504 transmitted in 80 MHz frequency segments used to signal large-size RU allocations and large-size RU combination allocations in a 320 MHz BW PPDU. In this example, three RUs or RU combinations are allocated: (i) a large-size RU allocation (RA1) 506 in the first and second 80 MHz frequency segments for MU-MIMO transmissions with four users, (ii) a large-size RU allocation (RA2) 508 in the third 80 MHz frequency segment for non-MU-MIMO transmissions, and (iii) a large-size RU allocation (RA3) 510 in the second 20 MHz subchannel of the third 80 MHz frequency segment for non-MU-MIMO transmissions.

[0062] CC1 502 includes eight RU allocation subfields with values ​​of 96, 169, 229, 229, 128, 224, 96, and 96 corresponding to the first, third, fifth, seventh, ninth, eleventh, thirteenth, and fifteenth 20 MHz frequency segments, respectively, and CC2 504 includes eight RU allocation subfields with values ​​of 96, 169, 229, 229, 64, 224, 96, and 96 corresponding to the second, fourth, sixth, eighth, tenth, twelfth, fourteenth, and sixteenth 20 MHz frequency segments. According to Tables 4-6, an RU allocation subfield value of 96 indicates a 242-tone RU but zero users (corresponding to no user fields in the user-specific field), a value of 169 indicates an RU combination of a 484-tone RU and a 996-tone RU in a 160 MHz frequency segment with two user fields in the user-specific field, a value of 229 indicates an RU combination of a 484-tone RU and a 996-tone RU in a 160 MHz frequency segment with zero user fields in the user-specific field, a value of 128 indicates an RU combination of a 242-tone RU and a 484-tone RU in an 80 MHz frequency segment with one user field in the user-specific field, a value of 224 indicates an RU combination of a 242-tone RU and a 484-tone RU in an 80 MHz frequency segment with zero user fields in the user-specific field, and a value of 64 indicates a single RU allocation of a 242-tone RU with one user in the user-specific field. For load balancing purposes, CC1 502 and CC2 504 each have three user fields in their user-specific fields.

[0063] 5B shows example common fields in EHT-SIG CC1 512 and CC2 514 transmitted in 80 MHz frequency segments used to signal a mix of small- and large-size RU or RU combination allocations in a 320 MHz BW PPDU. In this example, five RU or RU combinations are allocated: (i) a large-size RU allocation (RA1) 516 for MU-MIMO transmission with four users in the first and second 80 MHz frequency segments, (ii) a large-size RU allocation (RA2) 518 in the third 80 MHz frequency segment, and (iii) three small-size RU or RU combination allocations (RA3-RA5) 520 in the second 20 MHz subchannel of the third 80 MHz frequency segment.

[0064] CC1 512 includes eight RU allocation subfields with values ​​of 96, 170, 229, 229, 128, 224, 96, and 96 corresponding to the first, third, fifth, seventh, ninth, eleventh, thirteenth, and fifteenth 20 MHz frequency segments, respectively, and CC2 514 includes eight RU allocation subfields with values ​​of 96, 168, 229, 229, 46, 224, 96, and 96 corresponding to the second, fourth, sixth, eighth, tenth, twelfth, fourteenth, and sixteenth 20 MHz frequency segments. According to Tables 4 to 6, an RU allocation subfield value of 96 indicates a 242-tone RU but zero users (corresponding to no user fields in the user-specific field), a value of 168 indicates an RU combination of a 484-tone RU and a 996-tone RU in a 160 MHz frequency segment with one user field assigned to the user-specific field, a value of 229 indicates an RU combination of a 484-tone RU and a 996-tone RU in a 160 MHz frequency segment with zero user fields assigned to the user-specific field, a value of 128 indicates an RU combination of a 242-tone RU and a 484-tone RU in an 80 MHz frequency segment with one user field assigned to the user-specific field, a value of 224 indicates an RU combination of a 242-tone RU and a 484-tone RU in an 80 MHz frequency segment with zero user fields assigned to the user-specific field, and a value of 46 indicates three small-size RUs or an RU combination of a 132-tone RU and two 52-tone RUs with three user fields assigned to the user-specific field. For load balancing purposes, CC1 512 and CC2 514 each have four user fields in their user specific fields.

[0065] As mentioned above, the RU allocation information for a STA shall be fully indicated in the EHT-SIG field transmitted in the STA's listening 80 MHz frequency segment (L80), so that the STA only needs to process the pre-EHT modulation field of the STA's L80.

[0066] According to the present disclosure, if a STA is an 80+80 MHz or 160 MHz operating STA, a 160+80 MHz or 240 MHz operating STA, or a 160+160 MHz or 320 MHz operating STA, the STA may have an RU allocation outside the STA's L80 used for the EHT modulation field of the EHT basic PPDU. Advantageously, this may be beneficial for frequency selective scheduling and load balancing among 80 MHz frequency segments if a large-size RU or RU combination can be assigned to the STA outside the STA's L80. In this manner, the STA's ability to receive RU allocations outside its L80 shall be indicated to the AP, for example, through an Operating Mode Indication (OMI) procedure. In various embodiments, for an 80+80 MHz operating STA using dual radios each handling two 80 MHz segments, the STA may suspend one radio that does not handle L80 for power savings. In that case, the STA may not be able to receive RU allocations outside its L80. For a 160+80 MHz operating STA using dual radios that handle the 160 MHz and 80 MHz frequency segments, respectively, the STA may suspend one radio that does not address L80 to save power. In that case, if the 80 MHz frequency segment is L80, the STA may be unable to receive RU allocations outside of that L80, but if the RU allocation is in a 160 MHz frequency segment that includes L80, the STA may be able to receive RU allocations outside of that L80. For a 160+160 MHz operating STA using dual radios that handle two 160 MHz frequency segments, respectively, the STA may suspend one radio that does not address L80 to save power. In that case, if the RU allocation is in a 160 MHz frequency segment that does not include L80, the STA may be unable to receive RU allocations outside of that L80, but if the RU allocation is in a 160 MHz frequency segment that includes L80, the STA may be able to receive RU allocations outside of that L80.

[0067] However, allocating small size RUs or RU combinations to a STA outside of the STA's L80 should not be allowed as there is no benefit in terms of frequency diversity scheduling.

[0068] In order to achieve the above technical advantages, an object of the present disclosure is to provide a communication apparatus and method for MU-MIMO transmission that substantially overcomes existing problems and enables transmitting an EHT basic PPDU to multiple STAs that may be parked in different 80 MHz frequency segments.

[0069] 6 shows a schematic, partially sectioned diagram of a communication device 600 according to the present disclosure. The communication device 600 may be implemented as an AP or a STA.

[0070] 6, the communications device 600 may include circuitry 614, at least one wireless transmitter 602, at least one wireless receiver 604, and at least one antenna 612 (for simplicity, only one antenna is shown in FIG. 6 for illustrative purposes). The circuitry 614 may include at least one controller 606 for use in software and hardware-assisted execution of tasks the at least one controller 606 is designed to perform, including control of OFDMA or non-OFDMA communications with one or more other communications devices in a MIMO wireless network. The circuitry 614 may further include at least one transmit signal generator 608 and at least one receive signal processor 610. The at least one controller 606 may control at least one transmit signal generator 608 for generating PPDUs (e.g., PPDUs used for non-trigger-based communication) to be transmitted to one or more other communication devices via the at least one wireless transmitter 602, and at least one receive signal processor 610 for processing PPDUs (e.g., PPDUs used for non-trigger-based communication) received from one or more other communication devices via the at least one wireless receiver 604 under the control of the at least one controller 606. The at least one transmit signal generator 608 and the at least one receive signal processor 610 may be standalone modules of the communication device 600 that communicate with the at least one controller 606 for the above-mentioned functions, as shown in FIG. 6 . Alternatively, the at least one transmit signal generator 608 and the at least one receive signal processor 610 may be included in the at least one controller 606. It will be apparent to those skilled in the art that the arrangement of these functional modules is flexible and may vary according to actual needs and / or requirements. Data processing, storage, and other related control devices may be provided on an appropriate circuit board and / or within a chipset. In various embodiments, in operation, the at least one wireless transmitter 602 , the at least one wireless receiver 604 , and the at least one antenna 612 may be controlled by the at least one controller 606 .

[0071] In operation, the communications device 600 provides functionality necessary for MU-MIMO transmission. For example, the communications device 600 may be an AP, and the circuit 614 (e.g., at least one transmit signal generator 608 of the circuit 614) may, in operation, generate a PPDU including a signal field indicating RU allocation information for multiple other communications devices. In operation, the wireless transmitter 602 may transmit the PPDU to the multiple other communications devices on two or more 80 MHz frequency segments, and if one of the multiple other communications devices parks on one of the two or more 80 MHz frequency segments, the RU allocation information corresponding to the one of the multiple other communications devices is indicated in the signal field transmitted on one of the two or more 80 MHz frequency segments.

[0072] The communication device 600 may be a STA, and the radio receiver 604 may, in operation, receive a PPDU including a signal field indicating RU allocation information for the communication device transmitted on two or more 80 MHz frequency segments. The circuit 314 (e.g., at least one receive signal processor 610 of the circuit 314) may, in operation, process the PPDU, and if the communication device is parked on one of the two or more 80 MHz frequency segments, the RU allocation information corresponding to the communication device is indicated in the signal field transmitted on one of the two or more 80 MHz frequency segments.

[0073] 7 shows a flow chart 700 illustrating a communication method for transmitting a generated PPDU according to the present disclosure. In step 702, a PPDU is generated, where the PPDU includes a signal field indicating RU allocation information for a plurality of other communication devices. In step 704, the generated PPDU is transmitted to the plurality of other communication devices on two or more 80 MHz frequency segments, where if one of the plurality of other communication devices is parked on one of the two or more 80 MHz frequency segments, the RU allocation information corresponding to the one of the plurality of other communication devices is indicated in the signal field transmitted on one of the two or more 80 MHz frequency segments.

[0074] According to the present disclosure, there are two options for MU-MIMO transmission: specifically, in option 1, only STAs parked in the same 80 MHz frequency segment are allowed to be multiplexed in MU-MIMO transmission; and in option 2, STAs parked in different 80 MHz frequency segments are allowed to be multiplexed in MU-MIMO transmission if they are capable of receiving MU-MIMO transmission. Advantageously, option 2 for MU-MIMO transmission improves scheduling flexibility. Note that because a STA cannot change its center frequency during reception of an EHT basic PPDU, STAs that support a maximum BW of 80 MHz and parked in different 80 MHz frequency segments are not allowed to be multiplexed in MU-MIMO transmission.

[0075] For Option 1 of MU-MIMO transmission, in which only STAs parked in the same 80 MHz frequency segment are allowed to be multiplexed in the MU-MIMO transmission, user fields corresponding to all STAs multiplexed in the MU-MIMO transmission are included in the user-specific field 304 of the EHT-SIG field 204. Option 1 of MU-MIMO transmission may use the RU assignment subfield formats shown in Tables 4 to 6. Table 1 shows exemplary user fields for Option 1 of MU-MIMO transmission. Note that, similar to 11ax, a STA determines whether a user field is for a MU-MIMO assignment or a non-MU-MIMO assignment based on the number of users multiplexed in the corresponding assignment, as indicated in the RU assignment subfield. Furthermore, similar to 11ax, a STA multiplexed in the MU-MIMO assignment obtains the starting stream index and the number of spatial streams according to the spatial configuration field value and the user field position in the user-specific field, as shown in Tables 8 to 13. Table 1: Example Format of the User Field of the EHT-SIG Field 204 for MU-MIMO Allocations [Table 1]

[0076] 8 shows an example RU allocation for a 320 MHz channel. In this example, five RUs are allocated: (i) RU allocation 1 (RA1) for MU-MIMO transmission with two users STA4 and STA7 in the first 80 MHz frequency segment, (ii) RA2 for STA3 in the first and second 20 MHz subchannels of the second 80 MHz frequency segment, (iii) RA3 for STA5 in the third and fourth 20 MHz subchannels of the second 80 MHz frequency segment, (iv) RA4 for MU-MIMO transmission with two users STA1 and STA2 in the third 80 MHz frequency segment, and (v) RA5 for STA6 in the fourth 80 MHz frequency segment. According to one embodiment, STA3, STA4, STA5, and STA7 support a bandwidth wider than 80 MHz (e.g., 160 MHz or 80 + 80 MHz). STA3 and STA5 are parked in the first 80 MHz frequency segment, STA4 and STA7 are parked in the second 80 MHz frequency segment, STA1 and STA2 are parked in the third 80 MHz frequency segment, and STA6 is parked in the fourth 80 MHz frequency segment. Note that in this embodiment, STA3, STA4, STA5, and STA7 have RU allocations outside of the L80 used for the EHT modulation field.

[0077] In the example RU allocation shown in FIG. 8, under Option 1 for MU-MIMO transmission, assuming Option 1 (with header subfield) for the common fields of EHT-SIG CC1 and EHT-SIG CC2 for each 80 MHz frequency segment, the header subfield, RU allocation subfield, and user-specific field can be set as follows: EHT-SIG CC1: ■Header subfields: First 80MHz frequency segment: 0000100000000000 Second 80MHz frequency segment: 10000000000000000 Third 80MHz frequency segment: 0000000010000000 Fourth 80MHz frequency segment: 00000000000001000 ■RU allocation subfield First 80MHz frequency segment: 72 (single-user RU484) Second 80MHz frequency segment: 80 (single user RU996) Third 80MHz frequency segment: 80 (single user RU996) Fourth 80MHz frequency segment: 80 (single user RU996) ■User-specific fields First 80MHz frequency segment: STA3 user field Second 80MHz frequency segment: User field for STA4 Third 80MHz frequency segment: STA1 user field Fourth 80MHz frequency segment: STA6 user field EHT-SIG CC2: ■Header subfields: First 80MHz frequency segment: 0000001000000000 Second 80MHz frequency segment: 10000000000000000 Third 80MHz frequency segment: 0000000010000000 Fourth 80MHz frequency segment: 00000000000001000 ■RU allocation subfield First 80MHz frequency segment: 72 (single-user RU484) Second 80MHz frequency segment: 80 (single user RU996) Third 80MHz frequency segment: 80 (single user RU996) Fourth 80MHz frequency segment: 98 (RU996 with zero user field in CC2) ■User-specific fields First 80MHz frequency segment: STA5 user field Second 80MHz frequency segment: STA7 user field Third 80MHz frequency segment: STA2 user field Fourth 80MHz frequency segment: zero user fields

[0078] In this example, STA3 and STA5, which are parked in the same 80 MHz frequency segment, are not multiplexed with MU-MIMO transmission. The header subfields of CC1 and CC2 transmitted in the first 80 MHz frequency segment have bit “1” positions in b5 and b7, respectively, which indicate that the users or STAs parked in the first 80 MHz frequency segment, i.e., STA3 and STA5, have their RU allocation information indicated in the RU Allocation subfield transmitted in the first 80 MHz frequency segment. A value of 72 in the RU Allocation subfield indicates RA2 and RA3, which respectively assign one user field to the user-specific fields of CC1 and CC2. Therefore, the single user field of STA3 in CC1 and CC2 is associated with RA2, and the single user field of STA5 in CC1 and CC2 is associated with RA3, resulting in non-MU-MIMO transmission to STA3 in RA2 and non-MU-MIMO transmission to STA5 in RA3.

[0079] According to Option 1 of MU-MIMO transmission, STAs parked in the same 80 MHz frequency segment, e.g., STA4 and STA7 parked in the second 80 MHz frequency segment, are permitted to be multiplexed in MU-MIMO transmission. The header subfields of CC1 and CC2 transmitted in the second 80 MHz frequency segment both have a bit “1” in b1, indicating that the users or STAs parked in the second 80 MHz frequency segment, i.e., STA4 and STA7, have RU allocation information indicated in the RU Allocation subfield transmitted in the second 80 MHz frequency segment. A value of 80 in the RU Allocation subfield indicates RA1, which assigns one user field to each user-specific field in CC1 and CC2. Therefore, because two user fields of STA4 and STA7 in CC1 and CC2 are associated with RA1, this results in MU-MIMO transmission to STA4 and STA7 in RA1.

[0080] Similarly, STA1 and STA2 parked in the third 80 MHz frequency segment are permitted to be multiplexed in MU-MIMO transmission. The header subfields of CC1 and CC2 transmitted in the third 80 MHz frequency segment both have bit “1” in b9, indicating that the users or STAs parked in the third 80 MHz frequency segment, i.e., STA1 and STA2, have RU allocation information indicated in the RU allocation subfield transmitted in the third 80 MHz frequency segment. A value of 80 in the RU allocation subfield indicates RA4, which assigns one user field to each user-specific field in CC1 and CC2. Therefore, two user fields for STA1 and STA2 in CC1 and CC2 are associated with RA4, which results in MU-MIMO transmission to STA1 and STA2 in RA4.

[0081] The header subfields of CC1 and CC2 transmitted in the fourth 80 MHz frequency segment both have a bit “1” position in b13, indicating that the user(s) or STA(s) parked in the fourth 80 MHz frequency segment, i.e., STA6, have RU allocation information indicated in the RU Allocation subfield transmitted in the fourth 80 MHz frequency segment. A value of 80 in the RU Allocation subfield of CC1 indicates RA5, which assigns one user field in the user-specific field of CC1, and a value of 98 in the RU Allocation subfield of CC2 indicates a dummy RU allocation, which assigns zero user fields in the user-specific field of CC2. Therefore, since a single user field of STA6 in CC1 and CC2 is associated with RA5, this results in non-MU-MIMO transmission to STA6 in RA5.

[0082] In the example RU allocation shown in FIG. 8, under option 1 for MU-MIMO transmission, assuming option 2 (no header subfield) for the common fields of EHT-SIG CC1 and EHT-SIG CC2 for each 80 MHz frequency segment, the RU allocation subfield and user-specific fields can be set as follows: EHT-SIG CC1: ■RU allocation subfield First 80 MHz frequency segment: 98 (RU996 with zero user fields in CC1), 98 (RU996 with zero user fields in CC1), 72 (RU484 with single user), 97 (RU484 with zero user fields in CC1), 98 (RU996 with zero user fields in CC1), 98 (RU996 with zero user fields in CC1), 98 (RU996 with zero user fields in CC1), 98 (RU996 with zero user fields in CC1) Second 80MHz frequency segment: 80 (single-user RU996), 98 (RU996 with zero user field in CC1), 97 (RU484 with zero user field in CC1), 97 (RU484 with zero user field in CC1), 98 (RU996 with zero user field in CC1), 98 (RU996 with zero user field in CC1), 98 (RU996 with zero user field in CC1), 98 (RU996 with zero user field in CC1) Third 80 MHz frequency segment: 98 (RU996 with zero user fields in CC1), 98 (RU996 with zero user fields in CC1), 97 (RU484 with zero user fields in CC1), 97 (RU484 with zero user fields in CC1), 80 (RU996 with single user), 98 (RU996 with zero user fields in CC1), 98 (RU996 with zero user fields in CC1), 98 (RU996 with zero user fields in CC1) Fourth 80 MHz frequency segment: 98 (RU996 with zero user fields in CC1), 98 (RU996 with zero user fields in CC1), 97 (RU484 with zero user fields in CC1), 97 (RU484 with zero user fields in CC1), 98 (RU996 with zero user fields in CC1), 98 (RU996 with zero user fields in CC1), 80 (RU996 with single user), 98 (RU996 with zero user fields in CC1) ■User-specific fields First 80MHz frequency segment: STA3 user field Second 80MHz frequency segment: STA4 user field Third 80MHz frequency segment: STA1 user field Fourth 80MHz frequency segment: STA6 user field EHT-SIG CC2: ■RU allocation subfield First 80 MHz frequency segment: 98 (RU996 with zero user fields in CC2), 98 (RU996 with zero user fields in CC2), 97 (RU484 with zero user fields in CC2), 72 (RU484 with single user), 98 (RU996 with zero user fields in CC2), 98 (RU996 with zero user fields in CC2), 98 (RU996 with zero user fields in CC2), 98 (RU996 with zero user fields in CC2) Second 80 MHz frequency segment: 80 (single user RU 996), 98 (RU 996 with zero user field in CC2), 97 (RU 484 with zero user field in CC2), 97 (RU 484 with zero user field in CC2), 98 (RU 996 with zero user field in CC2), 98 (RU 996 with zero user field in CC2), 98 (RU 996 with zero user field in CC2), 98 (RU 996 with zero user field in CC2) Third 80 MHz frequency segment: 98 (RU996 with zero user fields in CC2), 98 (RU996 with zero user fields in CC2), 97 (RU484 with zero user fields in CC2), 97 (RU484 with zero user fields in CC2), 80 (RU996 with single user), 98 (RU996 with zero user fields in CC2), 98 (RU996 with zero user fields in CC2), 98 (RU996 with zero user fields in CC2) Fourth 80 MHz frequency segment: 98 (RU996 with zero user fields in CC2), 98 (RU996 with zero user fields in CC2), 97 (RU484 with zero user fields in CC2), 97 (RU484 with zero user fields in CC2), 98 (RU996 with zero user fields in CC2), 98 (RU996 with zero user fields in CC2), 98 (RU996 with zero user fields in CC2), 98 (RU996 with zero user fields in CC2) ■User-specific fields First 80MHz frequency segment: STA5 user field Second 80MHz frequency segment: STA7 user field Third 80MHz frequency segment: STA2 user field Fourth 80MHz frequency segment: zero user fields

[0083] The RU allocation subfields of CC1 and CC2 transmitted in the first 80 MHz frequency segment have an RU allocation subfield value of 72 in an arrangement corresponding to RA2 and RA3 (the third and fourth RU allocation subfield values ​​in CC1 and CC2, respectively). The value of 72 in the RU allocation subfield of CC1 indicates RA2, which assigns one user field to the user-specific field of CC1, and the value of 72 in the RU allocation subfield of CC2 indicates RA3, which assigns one user field to the user-specific field of CC2. The remaining RU allocation subfields of CC1 and CC2 have values ​​of 97 and 98, which indicate dummy RU allocation. Therefore, the single user field of STA3 in CC1 and CC2 is associated with RA2, and the single user field of STA5 in CC1 and CC2 is associated with RA3, resulting in non-MU-MIMO transmission to STA3 in RA2 and non-MU-MIMO transmission to STA5 in RA3.

[0084] According to the present disclosure, STA4 and STA7, parked in the second 80 MHz frequency segment, are permitted to be multiplexed in MU-MIMO transmission. The RU assignment subfields of CC1 and CC2 transmitted in the second 80 MHz frequency segment have a value of 80 (the first RU assignment subfield value in both CC1 and CC2) in an arrangement corresponding to RA1. The value of 80 in the RU assignment subfield indicates RA1, which assigns one user field to each user-specific field in CC1 and CC2. The remaining RU assignment subfields of CC1 and CC2 have values ​​of 97 and 98, indicating dummy RU assignment. Therefore, because two user fields of STA4 and STA7 in CC1 and CC2 are associated with RA1, this results in MU-MIMO transmission to STA4 and STA7 in RA1.

[0085] The RU allocation subfields of CC1 and CC2 transmitted in the third 80 MHz frequency segment have a value of 80 (the fifth RU allocation subfield value in both CC1 and CC2) in an arrangement corresponding to RA4. The 80 value in the RU allocation subfield indicates RA4, which assigns one user field to the user-specific fields of CC1 and CC2, respectively. The remaining RU allocation subfields of CC1 and CC2 have values ​​of 97 and 98, indicating dummy RU allocation. Therefore, two user fields for STA1 and STA2 in CC1 and CC2 are associated with RA4, which results in MU-MIMO transmission to STA1 and STA2 in RA4.

[0086] The RU Allocation subfield of CC1, transmitted in the fourth 80 MHz frequency segment, has a value of 80 (the seventh RU Allocation subfield value of CC1), in an arrangement corresponding to RA5. The value of 80 in the RU Allocation subfield of CC1 indicates RA5, which contributes one user field to the user-specific field of CC1. The remaining RU Allocation subfields of CC1 and CC2 have values ​​of 97 and 98, indicating dummy RU allocation. Therefore, a single user field for STA6 in CC1 and CC2 is associated with RA5, resulting in non-MU-MIMO transmission to STA6 in RA5.

[0087] According to the present disclosure, in Option 2 of MU-MIMO transmission, STAs parked on different 80 MHz frequency segments are allowed to be multiplexed in MU-MIMO transmission if they are capable of receiving MU-MIMO transmission, for example, if the STA supports a bandwidth wider than 80 MHz, such as 160 MHz, 80+80 MHz, 240 MHz, 160+80 MHz, 320 MHz, or 160+160 MHz. In various embodiments, in an 80 MHz frequency segment where at least one STA multiplexed in MU-MIMO transmission is parked, user fields corresponding to all STAs multiplexed in MU-MIMO transmission are included in the EHT-SIG field transmitted in the 80 MHz frequency segment. The user fields corresponding to STAs parked on different 80 MHz frequency segments are dummy user fields (having a special STA-ID 2046). The RU allocation subfields defined in Tables 4 to 6 and the user fields for MU-MIMO allocation defined in Table 1 can be used. The order of STAs multiplexed in MU-MIMO transmissions may be kept the same for each 80 MHz frequency segment in which at least one STA is multiplexed in MU-MIMO transmission, so that the same spatial configuration field can be set for all user fields of STAs multiplexed in MU-MIMO transmissions. Advantageously, when a single STA parked in an 80 MHz frequency segment is multiplexed in MU-MIMO transmissions, the STA can still correctly identify the user field for the MU-MIMO transmission and properly receive the MU-MIMO transmission.

[0088] Returning to the example RU allocation of Figure 8, five RUs are allocated: (i) RA1 for MU-MIMO transmission with two users STA4 and STA7 in the first 80 MHz frequency segment, (ii) RA2 for STA3 in the first and second 20 MHz subchannels of the second 80 MHz frequency segment, (iii) RA3 for STA3 in the third and fourth 20 MHz subchannels of the second 80 MHz frequency segment, (iv) RA4 for MU-MIMO transmission with two users STA1 and STA2 in the third 80 MHz frequency segment, and (v) RA5 for STA6 in the fourth 80 MHz frequency segment. According to one embodiment, STA5 and STA7 support a bandwidth wider than 80 MHz. STA4 and STA5 park in the first 80 MHz frequency segment. STA3 and STA7 are parked in the second 80 MHz frequency segment, STA1 and STA2 are parked in the third 80 MHz frequency segment, and STA6 is parked in the fourth 80 MHz frequency segment. Note that in this embodiment, STA5 and STA7 have RU allocations outside of L80, which is used for the EHT modulation field.

[0089] In the example RU allocation shown in FIG. 8, under Option 2 for MU-MIMO transmission, assuming Option 1 (with header subfield) for the common fields of EHT-SIG CC1 and EHT-SIG CC2 for each 80 MHz frequency segment, the header subfield, RU allocation subfield, and user-specific field can be set as follows: EHT-SIG CC1 ■Header subfields: First 80MHz frequency segment: 10000000000000000 Second 80MHz frequency segment: 10000000000000000 Third 80MHz frequency segment: 0000000010000000 Fourth 80MHz frequency segment: 00000000000001000 ■RU allocation subfield First 80MHz frequency segment: 81 (RU996 with two users) Second 80MHz frequency segment: 81 (RU996 with two users) Third 80MHz frequency segment: 80 (single user RU996) Fourth 80MHz frequency segment: 80 (single user RU996) ■User-specific fields First 80MHz frequency segment: STA4 user field, dummy user field Second 80MHz frequency segment: Dummy user field, STA7 user field Third 80MHz frequency segment: STA1 user field Fourth 80MHz frequency segment: STA6 user field EHT-SIG CC2 ■Header subfields: First 80MHz frequency segment: 0000001000000000 Second 80MHz frequency segment: 0000100000000000 Third 80MHz frequency segment: 0000000010000000 Fourth 80MHz frequency segment: 00000000000001000 ■RU allocation subfield First 80MHz frequency segment: 72 (single-user RU484) Second 80MHz frequency segment: 72 (single user RU484) Third 80MHz frequency segment: 80 (single user RU996) Fourth 80MHz frequency segment: 98 (RU996 with zero user field in CC2) ■User-specific fields First 80MHz frequency segment: STA5 user field Second 80MHz frequency segment: STA3 user field Third 80MHz frequency segment: STA2 user field Fourth 80MHz frequency segment: no user field

[0090] Note that STA4 and STA5, which are parked in the first 80 MHz frequency segment, have RU allocations in the first and second 80 MHz frequency segments, respectively, and STA3 and STA7, which are parked in the second 80 MHz frequency segment, have RU allocations in the second and first 80 MHz frequency segments, respectively.

[0091] According to the present disclosure, STAs parked on different 80 MHz frequency segments, e.g., STA4 and STA7 parked on the first and second 80 MHz frequency segments, respectively, are allowed to be multiplexed with MU-MIMO transmissions if they are capable of receiving MU-MIMO transmissions. In CC1, the header subfield of CC1 transmitted on the first or second 80 MHz frequency segment has a bit “1” in b1, indicating that a user or STA parked on the first or second frequency segment may have RU allocation information indicated in the RU Allocation subfield of the first or second 80 MHz frequency segment. A value of 81 in the RU Allocation subfield of CC1 transmitted on the first or second frequency segment indicates RA1, which adds two user fields, one for STA4 and one for STA7, to the user-specific field of CC1 transmitted on the first or second frequency segment. Because STA4 parks on the first 80 MHz frequency segment but STA7 does not, the user field corresponding to STA7 in CC1 transmitted on the first 80 MHz frequency segment is a dummy user field. Similarly, because STA7 is parked on the second 80 MHz frequency segment but STA4 is not, the user field corresponding to STA4 in CC1 transmitted on the second 80 MHz frequency segment is a dummy user field. Therefore, since two user fields for STA4 and STA7 in CC1 and CC2 are associated with RA1, this results in MU-MIMO transmission to STA4 and STA7 in RA1. The order of STA4 and STA7 is kept the same in the user-specific fields transmitted on the first and second 80 MHz frequency segments.

[0092] In CC2, the header subfield of CC2 transmitted in the first 80 MHz frequency segment has a bit “1” in b7, indicating that a user or STA parked in the first 80 MHz frequency segment may have RU allocation information indicated in the RU Allocation subfield of the first 80 MHz frequency segment. A value of 72 in the RU Allocation subfield of CC2 transmitted in the first 80 MHz frequency segment indicates RA3, which assigns one user field, namely, STA5, to the user-specific field of CC2 transmitted in the first 80 MHz frequency segment. Therefore, since a single user, STA5, of CC1 and CC2 is associated with RA3, this results in non-MU-MIMO transmission to STA5 in RA3. Meanwhile, the header subfield of CC2 transmitted in the second 80 MHz frequency segment has a bit “1” in b5, indicating that a user or STA parked in the second 80 MHz frequency segment may have RU allocation information indicated in the RU Allocation subfield of the second 80 MHz frequency segment. A value of 72 in the RU Allocation subfield of CC2 transmitted in the second frequency segment indicates RA2, which contributes one user field, namely, that for STA3, to the user-specific fields of CC2 transmitted in the second frequency segment. As such, a single user of STA3 on CC1 and CC2 is associated with RA2, which results in a non-MU-MIMO transmission to STA3 on RA2.

[0093] Furthermore, STA1 and STA2 parked in the third 80 MHz frequency segment are permitted to be multiplexed in MU-MIMO transmission. Both header subfields of CC1 and CC2 transmitted in the third 80 MHz frequency segment have bit "1" in b9, indicating that users or STAs parked in the third 80 MHz frequency segment may have RU allocation information indicated in the RU Allocation subfield transmitted in the third 80 MHz frequency segment. A value of 80 in the RU Allocation subfield indicates RA4, which adds one user field, i.e., one for STA1 and one for STA2, to each user-specific field of CC1 and CC2 transmitted in the third 80 MHz frequency segment. Therefore, two user fields for STA1 and STA2 in CC1 and CC2 are associated with RA4, which results in MU-MIMO transmission to STA1 and STA2 in RA4.

[0094] The header subfields of CC1 and CC2 transmitted in the fourth 80 MHz frequency segment both have a bit "1" position in b13, indicating that the user(s) or STA(s) parked in the fourth 80 MHz frequency segment may have RU allocation information indicated in the RU Allocation subfield transmitted in the fourth 80 MHz frequency segment. A value of 80 in the RU Allocation subfield of CC1 and a value of 98 in the RU Allocation subfield of CC2 indicate RA5, which contributes one user field and zero user fields, respectively, to the user-specific fields of CC1 and CC2 transmitted in the fourth 80 MHz frequency segment. Therefore, a single user field of STA6 in CC1 and CC2 is associated with RA5, resulting in non-MU-MIMO transmission to STA6 in RA5.

[0095] Under Option 1 for MU-MIMO transmission, assuming Option 2 (without header subfields) for the common fields of EHT-SIG CC1 and EHT-SIG CC2 for each 80 MHz frequency segment, the RU allocation subfield and user specific fields can be set as follows: EHT-SIG CC1: ■RU allocation subfield First 80MHz frequency segment: 81 (RU996 with two users), 98 (RU996 with zero user fields in CC1), 97 (RU484 with zero user fields in CC1), 97 (RU484 with zero user fields in CC1), 98 (RU996 with zero user fields in CC1), 98 (RU996 with zero user fields in CC1), 98 (RU996 with zero user fields in CC1), 98 (RU996 with zero user fields in CC1) Second 80MHz frequency segment: 81 (RU996 with two users), 98 (RU996 with zero user fields in CC1), 97 (RU484 with zero user fields in CC1), 97 (RU484 with zero user fields in CC1), 98 (RU996 with zero user fields in CC1), 98 (RU996 with zero user fields in CC1), 98 (RU996 with zero user fields in CC1), 98 (RU996 with zero user fields in CC1) Third 80 MHz frequency segment: 98 (RU996 with zero user fields in CC1), 98 (RU996 with zero user fields in CC1), 97 (RU484 with zero user fields in CC1), 97 (RU484 with zero user fields in CC1), 80 (RU996 with single user), 98 (RU996 with zero user fields in CC1), 98 (RU996 with zero user fields in CC1), 98 (RU996 with zero user fields in CC1) Fourth 80 MHz frequency segment: 98 (RU996 with zero user fields in CC1), 98 (RU996 with zero user fields in CC1), 97 (RU484 with zero user fields in CC1), 97 (RU484 with zero user fields in CC1), 98 (RU996 with zero user fields in CC1), 98 (RU996 with zero user fields in CC1), 80 (RU996 with single user), 98 (RU996 with zero user fields in CC1) ■User-specific fields First 80MHz frequency segment: STA4 user field, dummy user field Second 80MHz frequency segment: Dummy user field, STA7 user field Third 80MHz frequency segment: STA1 user field Fourth 80MHz frequency segment: STA6 user field EHT-SIG CC2: ■RU allocation subfield First 80 MHz frequency segment: 98 (RU996 with zero user fields in CC2), 98 (RU996 with zero user fields in CC2), 97 (RU484 with zero user fields in CC2), 72 (RU484 with single user), 98 (RU996 with zero user fields in CC2), 98 (RU996 with zero user fields in CC2), 98 (RU996 with zero user fields in CC2), 98 (RU996 with zero user fields in CC2) Second 80 MHz frequency segment: 98 (RU996 with zero user fields in CC2), 98 (RU996 with zero user fields in CC2), 72 (RU484 with single user), 97 (RU484 with zero user fields in CC2), 98 (RU996 with zero user fields in CC2), 98 (RU996 with zero user fields in CC2), 98 (RU996 with zero user fields in CC2), 98 (RU996 with zero user fields in CC2) Third 80 MHz frequency segment: 98 (RU996 with zero user fields in CC2), 98 (RU996 with zero user fields in CC2), 97 (RU484 with zero user fields in CC2), 97 (RU484 with zero user fields in CC2), 80 (RU996 with single user), 98 (RU996 with zero user fields in CC2), 98 (RU996 with zero user fields in CC2), 98 (RU996 with zero user fields in CC2) Fourth 80 MHz frequency segment: 98 (RU996 with zero user fields in CC2), 98 (RU996 with zero user fields in CC2), 97 (RU484 with zero user fields in CC2), 97 (RU484 with zero user fields in CC2), 98 (RU996 with zero user fields in CC2), 98 (RU996 with zero user fields in CC2), 98 (RU996 with zero user fields in CC2), 98 (RU996 with zero user fields in CC2) ■User-specific fields First 80MHz frequency segment: STA5 user field Second 80MHz frequency segment: STA3 user field Third 80MHz frequency segment: STA2 user field Fourth 80MHz frequency segment: no user field

[0096] In CC1, the RU assignment subfield of CC1 transmitted in the first or second 80 MHz frequency segment has a value of 81 (first RU assignment subfield value) in a configuration corresponding to RA1. This indicates that users or STAs parked in the first or second 80 MHz frequency segment, in this case STA4 and STA7, may have RU assignment information indicated in the first or second 80 MHz frequency segment. The value of 81 indicates RA1, which adds two user fields, one for STA4 and one for STA7, to the user-specific field of CC1 transmitted in the first or second frequency segment. Because STA4 parks in the first 80 MHz frequency segment but STA7 does not, the user field corresponding to STA7 in the first 80 MHz frequency segment is a dummy user field. Similarly, because STA7 parks in the second 80 MHz frequency segment but STA4 does not, the user field corresponding to STA4 in the second 80 MHz frequency segment is a dummy user field. Therefore, since the two user fields of STA4 and STA7 in CC1 and CC2 are associated with RA1, this results in MU-MIMO transmission to STA4 and STA7 in RA1. The order of STA4 and STA7 is kept the same in the user-specific fields of the first and second 80 MHz frequency segments.

[0097] In CC2, the RU allocation subfield of CC2 transmitted in the first or second 80 MHz frequency segment has a value of 72 (the fourth or third RU allocation subfield value) in an arrangement corresponding to RA3 or RA2. This indicates that users or STAs parked in the first or second 80 MHz frequency segment, in this case STA5 and STA3, may have RU allocation information indicated in the first or second 80 MHz frequency segment. The value of 72 indicates RA3 or RA2, which adds one user field, i.e., for STA5 or STA3, to the user-specific field of CC2 transmitted in the first or second frequency segment. The remaining RU allocation subfields of CC1 and CC2 have values ​​of 97 and 98, indicating dummy RU allocation. Therefore, because the single user field for STA5 or STA3 in CC1 and CC2 is associated with RA3 or RA2, this results in non-MU-MIMO transmission to STA5 in RA3 and non-MU-MIMO transmission to STA3 in RA2.

[0098] The RU allocation subfields of CC1 and CC2 transmitted in the third 80 MHz frequency segment have a value of 80 (the fifth RU allocation subfield value in both CC1 and CC2) in a configuration corresponding to RA4. This indicates that users or STAs parked in the third 80 MHz frequency segment, i.e., STA1 and STA2, may have RU allocation information indicated in the third 80 MHz frequency segment. The value of 80 in the RU allocation subfield indicates RA4, which adds one user field, i.e., one for STA1 and one for STA2, to each user-specific field in CC1 and CC2 transmitted in the third 80 MHz frequency segment. The remaining RU allocation subfields of CC1 and CC2 have values ​​of 97 and 98, indicating dummy RU allocation. Therefore, because two user fields for STA1 and STA2 in CC1 and CC2 are associated with RA4, this results in MU-MIMO transmission to STA1 and STA2 in RA4.

[0099] The RU Allocation subfield of CC1 transmitted in the fourth 80 MHz frequency segment has a value of 80 (the seventh RU Allocation subfield value in both CC1 and CC2) in a configuration corresponding to RA5. This indicates that a user or STA parked in the fourth 80 MHz frequency segment, i.e., STA6, may have RU allocation information indicated in the fourth 80 MHz frequency segment. The value of 80 in the RU Allocation subfield of CC1 indicates RA5, which adds one user field, i.e., for STA6, to the user-specific field of CC1 transmitted in the fourth 80 MHz frequency segment. The remaining RU Allocation subfields of CC1 and CC2 have values ​​of 97 and 98, indicating dummy RU allocation. Therefore, since a single user of STA6 in CC1 and CC2 is associated with RA5, this results in non-MU-MIMO transmission to STA6 in RA5.

[0100] According to the present disclosure, in option 2 of MU-MIMO transmission, STAs parked on different 80 MHz frequency segments are allowed to be multiplexed in MU-MIMO transmissions if they are capable of receiving the MU-MIMO transmission, e.g., if the STA supports a bandwidth wider than 80 MHz. In various embodiments, in an 80 MHz frequency segment where at least one STA multiplexed in MU-MIMO transmission is parked, a user field corresponding to the at least one STA multiplexed in MU-MIMO transmission is included in the EHT-SIG field transmitted in the 80 MHz frequency segment. In one embodiment, a dummy user field is not used to indicate the user field corresponding to the STAs parked on different 80 MHz frequency segments. Advantageously, the signaling overhead of the EHT-SIG field may be reduced.

[0101] To achieve this, there are two options: Option 2A and Option 2B. In Option 2A, the RU allocation subfield format and the user field format may be redesigned. Therefore, as shown in Table 7, each RU allocation subfield in an 80 MHz frequency segment indicates whether a large-size RU or RU combination allocation to a single user is an MU-MIMO or non-MU-MIMO allocation. As shown in Table 2, the user field uses a starting stream index subfield (4 bits) and a number of spatial streams subfield (2 bits) to indicate the starting stream index and the number of spatial streams, respectively, instead of the spatial configuration subfield (6 bits). The coding subfield indicates whether binary convolutional coding (BCC) or low-density parity-check code (LDPC) is used. Advantageously, when a single STA parked in an 80 MHz frequency segment is multiplexed with MU-MIMO transmissions, the STA can still correctly identify the user field for the MU-MIMO allocation and properly receive the MU-MIMO transmissions. Table 2: Other exemplary formats of the user field of the EHT-SIG field 204 for MU-MIMO allocations [Table 2]

[0102] In Option 2B, the RU allocation subfield formats defined in Tables 4-6 may be reused, but the user field format for MU-MIMO allocation may be redesigned. In one embodiment, a format subfield is added to the user field to indicate whether the user field is for non-MU-MIMO or MU-MIMO allocation, and a starting stream index subfield (4 bits) and a number of spatial streams subfield (2 bits) are used to indicate the starting stream index and number of spatial streams, respectively, instead of the spatial configuration subfield (6 bits), as shown in Table 3. Advantageously, when a single STA parked on an 80 MHz frequency segment is multiplexed with MU-MIMO transmissions, the STA can still correctly identify the user field for MU-MIMO allocation and properly receive the MU-MIMO transmissions. Table 3: Yet another exemplary format of the user field of the EHT-SIG field 204 for MU-MIMO assignments [Table 3]

[0103] Returning to the example RU allocation of Figure 8, five RUs are allocated: (i) RA1 for MU-MIMO transmission with two users STA4 and STA7 in the first 80 MHz frequency segment, (ii) RA2 for STA3 in the first and second 20 MHz subchannels of the second 80 MHz frequency segment, (iii) RA3 for STA3 in the third and fourth 20 MHz subchannels of the second 80 MHz frequency segment, (iv) RA4 for MU-MIMO transmission with two users STA1 and STA2 in the third 80 MHz frequency segment, and (v) RA5 for STA6 in the fourth 80 MHz frequency segment. According to one embodiment, STA5 and STA7 support a bandwidth wider than 80 MHz. STA4 and STA5 are parked in the first 80 MHz frequency segment, STA3 and STA7 are parked in the second 80 MHz frequency segment, STA1 and STA2 are parked in the third 80 MHz frequency segment, and STA6 is parked in the fourth 80 MHz frequency segment. Note that in this embodiment, STA5 and STA7 have RU allocations outside of L80, which is used for the EHT modulation field.

[0104] In one embodiment, under Option 2A or Option 2B of MU-MIMO transmission, assuming Option 1 (with header subfield) of common fields of EHT-SIG CC1 and EHT-SIG CC2 for each 80 MHz frequency segment, the header subfield, RU allocation subfield, and user-specific field may be set as follows: EHT-SIG CC1: ■Header subfields: First 80MHz frequency segment: 10000000000000000 Second 80MHz frequency segment: 10000000000000000 Third 80MHz frequency segment: 0000000010000000 Fourth 80MHz frequency segment: 00000000000001000 ■RU Allocation Subfield (Option 2A) First 80MHz frequency segment: 102 (996 single-user RUs multiplexed with MU-MIMO allocation) Second 80MHz frequency segment: 102 (996 RUs of single users multiplexed with MU-MIMO allocation) Third 80MHz frequency segment: 102 (996 single-user RUs multiplexed with MU-MIMO allocation) Fourth 80MHz frequency segment: 80 (996 RUs with single users multiplexed in a non-MU-MIMO allocation) ■RU Allocation Subfield (Option 2B) First 80MHz frequency segment: 80 (single user RU996) Second 80MHz frequency segment: 80 (single user RU996) Third 80MHz frequency segment: 80 (single user RU996) Fourth 80MHz frequency segment: 80 (single user RU996) ■User-specific fields First 80MHz frequency segment: STA4 user field Second 80MHz frequency segment: STA7 user field Third 80MHz frequency segment: STA1 user field Fourth 80MHz frequency segment: STA6 user field EHT-SIG CC2: ■Header subfields: First 80MHz frequency segment: 0000001000000000 Second 80MHz frequency segment: 0000100000000000 Third 80MHz frequency segment: 0000000010000000 Fourth 80MHz frequency segment: 00000000000001000 ■RU Allocation Subfield (Option 2A) First 80MHz frequency segment: 72 (484 single-user RUs multiplexed with non-MU-MIMO allocation) Second 80MHz frequency segment: 72 (484 single-user RUs multiplexed with non-MU-MIMO allocation) Third 80MHz frequency segment: 102 (996 single-user RUs multiplexed with MU-MIMO allocation) Fourth 80MHz frequency segment: 98 (RU996 with zero user field in CC2) ■RU Allocation Subfield (Option 2B) First 80MHz frequency segment: 72 (single-user RU484) Second 80MHz frequency segment: 72 (single user RU484) Third 80MHz frequency segment: 80 (single user RU996) Fourth 80MHz frequency segment: 98 (RU996 with zero user field in CC2) ■User-specific fields First 80MHz frequency segment: STA5 user field Second 80MHz frequency segment: STA3 user field Third 80MHz frequency segment: STA2 user field Fourth 80MHz frequency segment: no user field

[0105] Note that STA4 and STA5, which are parked in the first 80 MHz frequency segment, have RU allocations in the first and second 80 MHz frequency segments, respectively, and STA3 and STA7, which are parked in the second 80 MHz frequency segment, have RU allocations in the second and first 80 MHz frequency segments, respectively.

[0106] According to the present disclosure, STAs parked on different 80 MHz frequency segments, for example, STA4 and STA7 parked on the first and second 80 MHz frequency segments, respectively, are allowed to be multiplexed with MU-MIMO transmissions if they are capable of receiving MU-MIMO transmissions. In CC1, the header subfield of CC1 transmitted on the first or second 80 MHz frequency segment has a bit “1” position in b1, which indicates that a user or STA parked on the first or second frequency segment, in this case STA4 or STA7, may have RU allocation information indicated in the RU allocation subfield of the first or second 80 MHz frequency segment.

[0107] In Option 2A, according to the exemplary redesigned RU assignment subfield format in which each RU assignment subfield in an 80 MHz frequency segment indicates whether the large-size RU or RU combined assignment to a single user is a MU-MIMO assignment or a non-MU-MIMO assignment, the value of 102 in the RU assignment subfield of CC1 transmitted in each of the first and second frequency segments indicates RA1, which provides one single user field multiplexed with MU-MIMO transmission, i.e., one for STA4 and one for STA7, respectively, in the user-specific field of CC1 transmitted in each of the first and second frequency segments. In various embodiments, STA4 parks in the first 80 MHz frequency segment, but STA7 does not, so only the user field corresponding to STA4 appears in the user-specific field transmitted in the first 80 MHz frequency segment. Similarly, STA7 parks in the second 80 MHz frequency segment, but STA4 does not, so only the user field corresponding to STA7 appears in the user-specific field transmitted in the second 80 MHz frequency segment.

[0108] In CC2, the header subfield of CC2 transmitted on the first or second 80 MHz frequency segment has a bit "1" position at b7 or b5, indicating that a user or STA parked on the first or second frequency segment, in this case STA5 or STA3, may have RU allocation information indicated in the RU allocation subfield of the first or second 80 MHz frequency segment. A value of 72 in the RU allocation subfield of CC2 transmitted on the first or second frequency segment indicates RA3 or RA2, which gives the user-specific fields of CC2 transmitted on the first or second frequency segment one single user field multiplexed in non-MU-MIMO transmission, i.e., one for STA5 and STA3.

[0109] Furthermore, STA1 and STA2 parked in the third 80 MHz frequency segment are permitted to be multiplexed in MU-MIMO transmission. Both header subfields of CC1 and CC2 transmitted in the third 80 MHz frequency segment have bit “1” position in b9, indicating that users or STAs parked in the third 80 MHz frequency segment, i.e., STA1 and STA2, may have RU allocation information indicated in the RU Allocation subfield transmitted in the third 80 MHz frequency segment. A value of 102 in the RU Allocation subfield indicates RA4, which gives each user-specific field of CC1 and CC2 transmitted in the third 80 MHz frequency segment one single user field to be multiplexed in MU-MIMO transmission, i.e., one for STA1 and STA2, respectively.

[0110] The header subfields of CC1 and CC2 transmitted in the fourth 80 MHz frequency segment both have a bit "1" position in b13, which indicates that the user(s) or STA(s) parked in the fourth 80 MHz frequency segment, i.e., STA6, may have RU allocation information indicated in the RU Allocation subfield transmitted in the fourth 80 MHz frequency segment. A value of 80 in the RU Allocation subfield of CC1 indicates RA5, which gives one single user field to be multiplexed with non-MU-MIMO transmission in the user-specific fields of CC1 transmitted in the fourth 80 MHz frequency segment.

[0111] In Option 2B, in which the RU assignment subfield formats defined in Tables 4 through 6 are reused, a value of 80 in the RU assignment subfield transmitted in the first and second 80 MHz frequency segments indicates RA1, which assigns one single user field, i.e., one for STA4 and one for STA7, to the user-specific field of CC1 transmitted in each of the first and second frequency segments. In various embodiments of Option 2B, in which the user field format is redesigned to include a format field indicating whether the user field is for MU-MIMO assignment or non-MU-MIMO assignment, STA4 parks in the first 80 MHz frequency segment, so only the user field corresponding to STA4 is in the user-specific field transmitted in the first 80 MHz frequency segment. Similarly, STA7 parks in the second 80 MHz frequency segment, so only the user field corresponding to STA7 is in the user-specific field transmitted in the second 80 MHz frequency segment.

[0112] In CC2, the header subfield of CC2 transmitted on the first or second 80 MHz frequency segment has a bit "1" position at b7 or b5, which indicates that the user or STA parked on the first or second frequency segment, in this case STA5 or STA3, has RU allocation information indicated in the RU allocation subfield of the first or second 80 MHz frequency segment. A value of 72 in the RU allocation subfield of CC2 transmitted on the first or second frequency segment indicates RA3 or RA2, which gives the user-specific fields of CC2 transmitted on the first or second frequency segment one user field multiplexed in non-MU-MIMO transmission, i.e., the one for STA5 or STA3.

[0113] Furthermore, STA1 and STA2 parked in the third 80 MHz frequency segment are permitted to be multiplexed in MU-MIMO transmission. Both header subfields of CC1 and CC2 transmitted in the third 80 MHz frequency segment have bit “1” position in b9, indicating that users or STAs parked in the third 80 MHz frequency segment, i.e., STA1 and STA2, may have RU allocation information indicated in the RU Allocation subfield transmitted in the third 80 MHz frequency segment. In option 2B, a value of 80 in the RU Allocation subfield indicates RA4, which gives each user-specific field of CC1 and CC2 transmitted in the third 80 MHz frequency segment one single user field to be multiplexed in MU-MIMO transmission, i.e., one for STA1 and STA2, respectively.

[0114] The header subfields of CC1 and CC2 transmitted in the fourth 80 MHz frequency segment both have a bit "1" position in b13, which indicates that the user(s) or STA(s) parked in the fourth 80 MHz frequency segment, i.e., STA6, may have RU allocation information indicated in the RU Allocation subfield transmitted in the fourth 80 MHz frequency segment. The value of 80 in the RU Allocation subfield of CC1 indicates RA5, which provides one user field for STA6, which is multiplexed in non-MU-MIMO transmission, in the user-specific fields of CC1 transmitted in the fourth 80 MHz frequency segment.

[0115] Under Option 2A or Option 2B of MU-MIMO, assuming Option 2 (without header subfields) of the common fields of EHT-SIG CC1 and EHT-SIG CC2 for each 80 MHz frequency segment, the RU allocation subfield and user specific fields can be set as follows: EHT-SIG CC1 ■RU Allocation Subfield (Option 2A) First 80MHz frequency segment: 102 (RU996 with a single user multiplexed with MU-MIMO allocation), 98 (RU996 with zero user field in CC1), 97 (RU484 with zero user field in CC1), 97 (RU484 with zero user field in CC1), 98 (RU996 with zero user field in CC1), 98 (RU996 with zero user field in CC1), 98 (RU996 with zero user field in CC1), 98 (RU996 with zero user field in CC1), 98 (RU996 with zero user field in CC1) Second 80MHz frequency segment: 102 (RU996 with a single user multiplexed with MU-MIMO allocation), 98 (RU996 with zero user field in CC1), 97 (RU484 with zero user field in CC1), 97 (RU484 with zero user field in CC1), 98 (RU996 with zero user field in CC1), 98 (RU996 with zero user field in CC1), 98 (RU996 with zero user field in CC1), 98 (RU996 with zero user field in CC1), 98 (RU996 with zero user field in CC1) Third 80 MHz frequency segment: 98 (RU 996 with zero user field in CC1), 98 (RU 996 with zero user field in CC1), 97 (RU 484 with zero user field in CC1), 97 (RU 484 with zero user field in CC1), 102 (RU 996 with a single user multiplexed with MU-MIMO allocation), 98 (RU 996 with zero user field in CC1), 98 (RU 996 with zero user field in CC1), 98 (RU 996 with zero user field in CC1) Fourth 80MHz frequency segment: 98 (RU996 with zero user field in CC1), 98 (RU996 with zero user field in CC1), 97 (RU484 with zero user field in CC1), 97 (RU484 with zero user field in CC1), 98 (RU996 with zero user field in CC1), 98 (RU996 with zero user field in CC1), 80 (RU996 with single user multiplexed in non-MU-MIMO allocation), 98 (RU996 with zero user field in CC1) ■RU Allocation Subfield (Option 2B) First 80 MHz frequency segment: 80 (single-user RU 996), 98 (RU 996 with zero user fields in CC1), 97 (RU 484 with zero user fields in CC1), 97 (RU 484 with zero user fields in CC1), 98 (RU 996 with zero user fields in CC1), 98 (RU 996 with zero user fields in CC1), 98 (RU 996 with zero user fields in CC1), 98 (RU 996 with zero user fields in CC1) Second 80MHz frequency segment: 80 (single-user RU996), 98 (RU996 with zero user field in CC1), 97 (RU484 with zero user field in CC1), 97 (RU484 with zero user field in CC1), 98 (RU996 with zero user field in CC1), 98 (RU996 with zero user field in CC1), 98 (RU996 with zero user field in CC1), 98 (RU996 with zero user field in CC1) Third 80 MHz frequency segment: 98 (RU996 with zero user fields in CC1), 98 (RU996 with zero user fields in CC1), 97 (RU484 with zero user fields in CC1), 97 (RU484 with zero user fields in CC1), 80 (RU996 with single user), 98 (RU996 with zero user fields in CC1), 98 (RU996 with zero user fields in CC1), 98 (RU996 with zero user fields in CC1) Fourth 80 MHz frequency segment: 98 (RU996 with zero user fields in CC1), 98 (RU996 with zero user fields in CC1), 97 (RU484 with zero user fields in CC1), 97 (RU484 with zero user fields in CC1), 98 (RU996 with zero user fields in CC1), 98 (RU996 with zero user fields in CC1), 80 (RU996 with single user), 98 (RU996 with zero user fields in CC1) ■User-specific fields First 80MHz frequency segment: STA4 user field Second 80MHz frequency segment: STA7 user field Third 80MHz frequency segment: STA1 user field Fourth 80MHz frequency segment: STA6 user field EHT-SIG CC2: ■RU Allocation Subfield (Option 2A) First 80 MHz frequency segment: 98 (RU 996 with zero user field in CC2), 98 (RU 996 with zero user field in CC2), 97 (RU 484 with zero user field in CC2), 72 (RU 484 with single user multiplexed with non-MU-MIMO allocation), 98 (RU 996 with zero user field in CC2), 98 (RU 996 with zero user field in CC2), 98 (RU 996 with zero user field in CC2), 98 (RU 996 with zero user field in CC2) Second 80MHz frequency segment: 98 (RU996 with zero user field in CC2), 98 (RU996 with zero user field in CC2), 72 (RU484 with single user multiplexed with non-MU-MIMO allocation), 97 (RU484 with zero user field in CC2), 98 (RU996 with zero user field in CC2), 98 (RU996 with zero user field in CC2), 98 (RU996 with zero user field in CC2), 98 (RU996 with zero user field in CC2), 98 (RU996 with zero user field in CC2) Third 80MHz frequency segment: 98 (RU996 with zero user field in CC2), 98 (RU996 with zero user field in CC2), 97 (RU484 with zero user field in CC2), 97 (RU484 with zero user field in CC2), 102 (RU996 with single user multiplexed with MU-MIMO allocation), 98 (RU996 with zero user field in CC2), 98 (RU996 with zero user field in CC2), 98 (RU996 with zero user field in CC2) Fourth 80 MHz frequency segment: 98 (RU996 with zero user fields in CC2), 98 (RU996 with zero user fields in CC2), 97 (RU484 with zero user fields in CC2), 97 (RU484 with zero user fields in CC2), 98 (RU996 with zero user fields in CC2), 98 (RU996 with zero user fields in CC2), 98 (RU996 with zero user fields in CC2), 98 (RU996 with zero user fields in CC2) ■RU Allocation Subfield (Option 2B) First 80 MHz frequency segment: 98 (RU996 with zero user fields in CC2), 98 (RU996 with zero user fields in CC2), 97 (RU484 with zero user fields in CC2), 72 (RU484 with single user), 98 (RU996 with zero user fields in CC2), 98 (RU996 with zero user fields in CC2), 98 (RU996 with zero user fields in CC2), 98 (RU996 with zero user fields in CC2) Second 80 MHz frequency segment: 98 (RU996 with zero user fields in CC2), 98 (RU996 with zero user fields in CC2), 72 (RU484 with single user), 97 (RU484 with zero user fields in CC2), 98 (RU996 with zero user fields in CC2), 98 (RU996 with zero user fields in CC2), 98 (RU996 with zero user fields in CC2), 98 (RU996 with zero user fields in CC2) Third 80 MHz frequency segment: 98 (RU996 with zero user fields in CC2), 98 (RU996 with zero user fields in CC2), 97 (RU484 with zero user fields in CC2), 97 (RU484 with zero user fields in CC2), 80 (RU996 with single user), 98 (RU996 with zero user fields in CC2), 98 (RU996 with zero user fields in CC2), 98 (RU996 with zero user fields in CC2) Fourth 80 MHz frequency segment: 98 (RU996 with zero user fields in CC2), 98 (RU996 with zero user fields in CC2), 97 (RU484 with zero user fields in CC2), 97 (RU484 with zero user fields in CC2), 98 (RU996 with zero user fields in CC2), 98 (RU996 with zero user fields in CC2), 98 (RU996 with zero user fields in CC2), 98 (RU996 with zero user fields in CC2) ■User-specific fields First 80MHz frequency segment: STA5 user field Second 80MHz frequency segment: STA3 user field Third 80MHz frequency segment: STA2 user field Fourth 80MHz frequency segment: no user field

[0116] In Option 2A, according to the redesigned RU assignment subfield format in which each RU assignment subfield in an 80 MHz frequency segment indicates whether a large-size RU or RU combination assignment to a single user is an MU-MIMO assignment or a non-MU-MIMO assignment, the RU assignment subfield of CC1 transmitted in the first and second 80 MHz frequency segments has a value of 102 (first RU assignment subfield value) in an arrangement corresponding to RA1. This indicates that a user or STA parked in the first or second 80 MHz frequency segment, in this case STA4 or STA7, may have RU assignment information indicated in the first or second 80 MHz frequency segment. The value of 102 indicates RA1, which provides one single user field, i.e., for STA4 and STA7, multiplexed in the MU-MIMO transmission, in the user-specific field of CC1 transmitted in each of the first and second frequency segments. In various embodiments, because STA4 parks in the first 80 MHz frequency segment but STA7 does not, only the user field corresponding to STA4 is in the user-specific field transmitted in the first 80 MHz frequency segment. Similarly, STA7 is parked on the second 80 MHz frequency segment, but STA4 is not, so only the user field corresponding to STA7 is in the user-specific field transmitted on the second 80 MHz frequency segment.

[0117] In CC2, the RU allocation subfields of CC2 transmitted in the first and second 80 MHz frequency segments have a value of 72 in the corresponding arrangement to RA3 and RA2 (the fourth and third RU allocation subfield values, respectively). This indicates that the user or STA parked in the first or second 80 MHz frequency segment, in this case STA5 or STA3, has the RU allocation information indicated in the first or second 80 MHz frequency segment. The value of 72 indicates RA3 or RA2, which gives the user-specific field of CC2 transmitted in the first or second frequency segment one single user field multiplexed in the non-MU-MIMO transmission, i.e., the one for STA5 or STA3.

[0118] The RU Allocation subfields of CC1 and CC2 transmitted in the third 80 MHz frequency segment have a value of 102 in an arrangement corresponding to RA4 (the fifth RU Allocation subfield value in both CC1 and CC2). This indicates that users or STAs parked in the third 80 MHz frequency segment, i.e., STA1 and STA2, may have RU allocation information indicated in the third 80 MHz frequency segment. The value of 102 in the RU Allocation subfield indicates RA4, which gives each user-specific field of CC1 and CC2 transmitted in the third 80 MHz frequency segment one single user field to be multiplexed in the MU-MIMO transmission, i.e., one for STA1 and STA2, respectively.

[0119] The RU Allocation subfield of CC1 transmitted in the fourth 80 MHz frequency segment has a value of 80 (the seventh RU Allocation subfield value in both CC1 and CC2) in an arrangement corresponding to RA5. This indicates that a user or STA parked in the fourth 80 MHz frequency segment, i.e., STA6, may have RU allocation information indicated in the fourth 80 MHz frequency segment. The value of 80 in the RU Allocation subfield of CC1 indicates RA5, which gives one user field, i.e., for STA6, multiplexed in non-MU-MIMO transmissions to the user-specific fields of CC1 transmitted in the fourth 80 MHz frequency segment.

[0120] FIG. 9 illustrates a configuration of a communications device 900, such as an AP, according to various embodiments. Similar to the schematic example of communications apparatus 600 shown in FIG. 6, communications apparatus 900 includes circuitry 902, at least one wireless transmitter 910, at least one wireless receiver 912, and at least one antenna 914 (for simplicity, only one antenna is shown in FIG. 9). Circuitry 902 may include at least one controller 908 for use in software- and hardware-assisted execution of tasks designed by controller 908 to perform OFDMA or non-OFDMA communications. Circuitry 902 may further include a transmit signal generator 904 and a receive signal processor 906. At least one controller 908 may control transmit signal generator 904 and receive signal processor 906. Transmit signal generator 904 may include a frame generator 922, a control signaling generator 924, and a PPDU generator 926. Frame generator 922 may generate MAC frames, e.g., data frames or trigger frames. The control signaling generator 924 may generate a control signaling field of a generated PPDU (e.g., a U-SIG field and an EHT-SIG field of an EHT Basic PPDU). The PPDU generator 926 may generate a PPDU (e.g., an EHT Basic PPDU).

[0121] The receive signal processor 906 may include a data demodulator and decoder 934 that may demodulate and decode a data portion of the received signal (e.g., a data field of an EHT Basic PPDU). The receive signal processor 906 may further include a control demodulator and decoder 934 that may demodulate and decode a control signaling portion of the received signal (e.g., a U-SIG field and an EHT-SIG field of an EHT Basic PPDU). The at least one controller 908 may include a control signal analyzer 942 and a scheduler 944. The scheduler 944 may determine RU information, user-specific allocation information regarding allocation of downlink SU or MU transmissions, and trigger information regarding allocation of uplink MU transmissions. The control signal analyzer 942 may analyze the control signaling portion of the received signal and the trigger information regarding allocation of uplink MU transmissions shared by the scheduler 944 to assist the data demodulator and decoder 932 in demodulating and decoding the data portion of the received signal.

[0122] FIG. 10 illustrates a configuration of a communications device 1000, such as a STA, according to various embodiments. Similar to the schematic example of communications device 600 shown in FIG. 6, communications device 1000 includes circuitry 1002, at least one wireless transmitter 1010, at least one wireless receiver 1012, and at least one antenna 1014 (only one antenna is shown in FIG. 10 for simplicity). Circuitry 1002 may include at least one controller 1008 for use in software- and hardware-assisted execution of tasks designed by controller 1008 to perform OFDMA or non-OFDMA communications. Circuitry 1002 may further include a receive signal processor 1004 and a transmit signal generator 1006. At least one controller 1008 may control receive signal processor 1004 and transmit signal generator 1006. Receive signal processor 1004 may include a data demodulator and decoder 1032 and a control demodulator and decoder 1034. The control demodulator and decoder 1034 may demodulate and decode the control signaling portion of the received signal (e.g., the U-SIG field and the EHT-SIG field of the EHT Basic PPDU). The data demodulator and decoder 1032 may demodulate and decode the data portion of the received signal (e.g., the data field of the EHT Basic PPDU) according to the RU information and the user-specific allocation information of its own allocation.

[0123] The at least one controller 1008 may include a control signal analyzer 1042, a scheduler 1044, and a trigger information analyzer 1046. The control signal analyzer 1042 may receive a control signaling portion of a received signal (e.g., a U-SIG field and an EHT-SIG field of an EHT Basic PPDU) and may assist the data demodulator and decoder 1032 in demodulating and decoding a data portion of the received signal (e.g., a data field of an EHT Basic PPDU). The trigger information analyzer 1048 may analyze trigger information related to its own uplink allocation from a received trigger frame included in the data portion of the received signal. The transmit signal generator 1004 may include a control signaling generator 1024 that may generate a control signaling field of a generated PPDU (e.g., a U-SIG field of an EHT Basic PPDU). The transmit signal generator 1004 may further include a PPDU generator 1026 that generates a PPDU (e.g., an EHT Basic PPDU). The transmit signal generator 1004 may further include a frame generator 1022 that may generate MAC frames, such as data frames.

[0124] As described above, the embodiments of the present disclosure provide an advanced communication system, communication method and communication device for MU-MIMO transmission in an ultra-high throughput WLAN network, and improve the spectral efficiency in the MIMO WLAN network.

[0125] The present disclosure can be realized by software, hardware, or software cooperating with hardware. Each functional block used in the description of each embodiment above can be partially or completely realized by an LSI such as an integrated circuit, and each process described in each embodiment can be partially or completely controlled by the same LSI or a combination of LSIs. The LSI can be formed as a separate chip, or a single chip can be formed to include some or all of the functional blocks. The LSI can include data inputs and outputs coupled thereto. The LSI referred to herein may be referred to as an IC, system LSI, super LSI, or ultra LSI depending on the level of integration. However, the technology for implementing an integrated circuit is not limited to LSI, and it can be realized using dedicated circuits, general-purpose processors, or dedicated processors. Also, a field programmable gate array (FPGA), which can be programmed after LSI fabrication, or a reconfigurable processor, which can reconfigure the connections and settings of circuit cells arranged within LSI, can be used. The present disclosure can be realized as digital processing or analog processing. If future integrated circuit technology replaces LSI as a result of advances in semiconductor technology or other derivative technologies, the functional blocks can be integrated using future integrated circuit technology. Biotechnology can also be applied.

[0126] The present disclosure may be implemented by any type of apparatus, device or system having communication capabilities, referred to as a communications apparatus.

[0127] A communication device may include a transceiver and processing / control circuitry. The transceiver may include and / or function as a receiver and a transmitter. The transceiver as a transmitter and receiver may include an RF (radio frequency) module, which includes an amplifier, an RF modulator / demodulator, etc., and one or more antennas.

[0128] Some non-limiting examples of such communication devices include telephones (e.g., cellular phones, smartphones), tablets, personal computers (PCs) (e.g., laptops, desktops, netbooks), cameras (e.g., digital still / video cameras), digital players (digital audio / video players), wearable devices (e.g., wearable cameras, smart watches, tracking devices), game consoles, digital book readers, telehealth / telemedicine (remote health and medicine) devices, and vehicles (e.g., automobiles, airplanes, ships) that provide communication capabilities, and various combinations thereof.

[0129] Communication devices are not limited to being portable or mobile, but may also include any type of non-portable or fixed apparatus, device, or system, such as smart home devices (e.g., appliances, lights, smart meters, control panels), vending machines, and any other "things" in an "Internet of Things" (IoT) network.

[0130] Communications may include, for example, data exchange via cellular systems, wireless LAN systems, satellite systems, and the like, as well as various combinations thereof.

[0131] A communications apparatus may include devices such as a controller or a sensor coupled to a communications device that performs the communications functions described in this disclosure. For example, a communications apparatus may include a controller or a sensor that generates control or data signals used by the communications device to perform the communications functions of the communications apparatus.

[0132] Communications equipment may also include infrastructure facilities such as base stations, access points, and any other equipment, devices, or systems that communicate with or control equipment such as those in the non-limiting examples above.

[0133] Although some features of the various embodiments have been described with reference to devices, it will be understood that corresponding features also apply to the methods of the various embodiments, and vice versa.

[0134] It will be apparent to those skilled in the art that numerous variations and / or modifications may be made to the present disclosure as illustrated in the specific embodiments without departing from the spirit or scope of the disclosure as broadly described. The present embodiments are therefore to be considered in all respects as illustrative and not restrictive. Table 4: RU subfield values ​​corresponding to allocation of small size RUs according to one embodiment [Table 4] Table 5: RU subfield values ​​corresponding to small size RU combinations and large size RU allocations according to one embodiment [Table 5A] [Table 5B] Table 6: RU subfield values ​​corresponding to allocation of large size RU combinations according to one embodiment [Table 6A] [Table 6B] Table 7: RU allocation subfield with information on whether a large size RU or combined RU allocation to a single user is a MU-MIMO or non-MU-MIMO allocation. [Table 7A] [Table 7B] Table 8: Spatial configuration index for two or three users according to one embodiment [Table 8] Table 9: Space configuration index for four users according to one embodiment [Table 9] Table 10: Space configuration index for 5 users according to one embodiment [Table 10] Table 11: Space configuration index for six users according to one embodiment [Table 11] Table 12: Space configuration index for seven users according to one embodiment [Table 12] Table 13: Space configuration index for 8 users according to one embodiment [Table 13]

Claims

1. generating a physical layer protocol data unit (PPDU) including a signal field including a resource unit (RU) allocation subfield, the value of which can be set to indicate a combination of a plurality of RUs; The RU combination is a small size RU combination or a large size RU combination, the small size RU combination includes only small size RUs, which are defined as RUs having a size less than 242 tones; the large size RU combination includes only large size RUs, defined as RUs having a size of 242 tones or greater; a circuit for generating the PPDU; a transmitter for transmitting the PPDU to a plurality of other communication devices in two or more 80 MHz frequency sub-blocks; Equipped with When one other communication device among the plurality of other communication devices parks in one 80 MHz frequency sub-block among the two or more 80 MHz frequency sub-blocks, a first RU allocation sub-field corresponding to the one other communication device among the RU allocation sub-fields is included in the signal field transmitted in the one 80 MHz frequency sub-block. Communication equipment.

2. The first RU allocation subfield indicates an RU located outside the one 80 MHz frequency subblock. The communication device according to claim 1 .

3. The first RU allocation subfield indicates an RU located inside the one 80 MHz frequency sub-block. The communication device according to claim 1 .

4. Among the plurality of other communication devices, only two or more other communication devices that park in the same 80 MHz frequency sub-block among the two or more 80 MHz frequency sub-blocks are allowed to be multiplexed in a multi-user multiple-input multiple-output (MU-MIMO) transmission. The communication device according to claim 1 .

5. Among the plurality of other communication devices, two or more other communication devices parked on different 80 MHz frequency sub-blocks of the two or more 80 MHz frequency sub-blocks are allowed to be multiplexed in the MU-MIMO transmission if the two or more other communication devices are capable of receiving the MU-MIMO transmission. The communication device according to claim 1 .

6. When at least one other communication device among the two or more other communication devices parks in one sub-block among the two or more 80 MHz frequency sub-blocks, the signal field transmitted in the one sub-block includes a user field corresponding to the two or more other communication devices. The communication device according to claim 5 .

7. each of the user fields that does not correspond to the at least one other communication device is a dummy user field; The communication device according to claim 6.

8. At least one other communication device among the two or more other communication devices parks in one sub-block among the two or more 80 MHz frequency sub-blocks, and the signal field transmitted in the one sub-block includes one or more user fields corresponding to the at least one other communication device. The communication device according to claim 5 .

9. 1. A communication method performed by a communication device, comprising: generating a physical layer protocol data unit (PPDU) including a signal field indicating a resource unit (RU) allocation subfield that can be set to a value indicating a combination of RUs; The RU combination is a small size RU combination or a large size RU combination, the small size RU combination includes only small size RUs, which are defined as RUs having a size less than 242 tones; the large size RU combination includes only large size RUs, defined as RUs having a size of 242 tones or greater; generating the PPDU; transmitting the PPDU to a plurality of other communication devices in two or more 80 MHz frequency sub-blocks; Including, When one other communication device among the plurality of other communication devices parks in one 80 MHz frequency sub-block among the two or more 80 MHz frequency sub-blocks, a first RU allocation sub-field corresponding to the one other communication device among the RU allocation sub-fields is included in the signal field transmitted in the one sub-block. Communication method.

10. A process for generating a physical layer protocol data unit (PPDU) including a signal field indicating a resource unit (RU) allocation subfield that can be set to a value indicating a combination of RUs consisting of a plurality of RUs, The RU combination is a small size RU combination or a large size RU combination, the small size RU combination includes only small size RUs, which are defined as RUs having a size less than 242 tones; the large size RU combination includes only large size RUs, defined as RUs having a size of 242 tones or greater; generating the PPDU; transmitting the PPDU to a plurality of other communication devices in two or more 80 MHz frequency sub-blocks; Control the When one other communication device among the plurality of other communication devices parks in one 80 MHz frequency sub-block among the two or more 80 MHz frequency sub-blocks, a first RU allocation sub-field corresponding to the one other communication device among the RU allocation sub-fields is included in the signal field transmitted in the one sub-block. Integrated circuit.

Images