Communication apparatus and communication method for control signaling

Abstract

The present disclosure provides a communication apparatus and a communication method for control signaling. The communication apparatus comprises: a circuitry configured to generate a transmission signal comprising a plurality of user fields and a data field, the data field comprising a plurality of resource units (RUs); a transmitter configured to transmit the generated transmission signal; wherein a single transmission scheme is applied to one or more of the plurality of RUs allocated to another communication apparatus; and wherein one or more of the plurality of user fields are addressed to the other communication apparatus, and the number of the one or more user fields addressed to the other communication apparatus is equal to the number of the one or more RUs allocated to the other communication apparatus; and the one or more user fields addressed to the other communication apparatus respectively correspond to the one or more RUs allocated to the other communication apparatus.

Description

TECHNICAL FIELD

[0001] The present disclosure relates to a communication apparatus and method for control signaling, and more particularly, to a communication apparatus and method for control signaling in an EHT WLAN (Extremely High Throughput WLAN). BACKGROUND

[0002] In the standardization of next generation wireless local area network (WLAN), a new radio access technology with backward compatibility to IEEE 802.11a / b / g / n / ac / ax technology has been discussed in IEEE 802.11 Working Group, and is named as Extremely High Throughput (EHT) WLAN.

[0003] In the EHT WLAN, in order to provide a significant peak throughput and capacity increase over 802.11ax high efficiency (HE) WLAN, it is expected to increase the maximum channel bandwidth from 160 MHz to 320 MHz, to increase the maximum number of spatial streams from 8 to 16, and to support multi-band operation. In addition, in order to improve the spectral efficiency on 11ax HE WLAN, it has been proposed to allow multiple contiguous or non-contiguous resource units (RUs) to be allocated to a single communication apparatus.

[0004] However, there is no discussion on a communication apparatus and method for control signaling, especially on efficient signaling support for allocating one or more RUs to a single communication apparatus in the context of EHT WLAN.

[0005] Therefore, there is a need for a communication apparatus and method that provides a feasible technical solution for control signaling in the context of EHT WLAN. In addition, other desirable features and characteristics will become apparent from the subsequent detailed description and the appended claims, taken in conjunction with the accompanying drawings and this background of the disclosure. SUMMARY

[0006] The non-limiting and exemplary embodiments facilitate providing a communication apparatus and communication method for control signaling in the context of EHT WLAN.

[0007] According to an embodiment of the disclosure, there is provided a communication apparatus comprising: circuitry that generates a transmission signal comprising a plurality of user fields and a data field, the data field comprising a plurality of resource units (RUs); and a transmitter that transmits the generated transmission signal, wherein a single transmission scheme is applied to one or more of the plurality of RUs allocated to another communication apparatus, and wherein one or more of the plurality of user fields are addressed to the other communication apparatus, and the number of the one or more user fields addressed to the other communication apparatus is equal to the number of the one or more RUs allocated to the other communication apparatus, and the one or more user fields addressed to the other communication apparatus respectively correspond to the one or more RUs allocated to the other communication apparatus.

[0008] According to another embodiment of the disclosure, there is provided a communication apparatus comprising: a receiver that receives a signal comprising a plurality of user fields and a data field, the data field comprising a plurality of RUs; and circuitry that processes the received signal, wherein a single transmission scheme is applied to one or more of the plurality of RUs allocated to the communication apparatus, and wherein one or more of the plurality of user fields are addressed to the communication apparatus, and the number of the one or more user fields addressed to the communication apparatus is equal to the number of the one or more RUs allocated to the communication apparatus, and the one or more user fields addressed to the communication apparatus respectively correspond to the one or more RUs allocated to the communication apparatus.

[0009] According to yet another embodiment of the disclosure, there is provided a communication method comprising: generating a transmission signal comprising a plurality of user fields and a data field, the data field comprising a plurality of RUs; and transmitting the generated transmission signal, wherein a single transmission scheme is applied to one or more of the plurality of RUs allocated to another communication apparatus, and wherein one or more of the plurality of user fields are addressed to the other communication apparatus, and the number of the one or more user fields addressed to the other communication apparatus is equal to the number of the one or more RUs allocated to the other communication apparatus, and the one or more user fields addressed to the other communication apparatus respectively correspond to the one or more RUs allocated to the other communication apparatus.

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

[0011] Other benefits and advantages of the disclosed embodiments will become apparent from the description and drawings. Benefits and / or advantages can be obtained from various embodiments and features, which need not be provided in order to obtain one or more of these benefits and / or advantages. BRIEF DESCRIPTION OF DRAWINGS

[0012] Embodiments of the present disclosure will be better understood and apparent from the following written description, taken in conjunction with the drawings, only as examples and not limiting, in which:

[0013] Figure 1A A diagram depicts uplink and downlink single-user (SU) MIMO communications between an access point (AP) and a station (STA) in a multiple-input multiple-output (MIMO) wireless network.

[0014] Figure 1B A diagram depicts downlink multi-user MIMO (MU-MIMO) communications between an AP and multiple STAs in a MIMO wireless network.

[0015] Figure 1C A diagram depicts uplink MU-MIMO communications between an AP and multiple STAs in a MIMO wireless network.

[0016] Figure 2A A diagram depicts an example format of an EHT MU PPDU (Physical Layer Protocol Data Unit) for downlink MU (multi-user) communications between an AP and multiple STAs in an EHT WLAN.

[0017] Figure 2B A table shows how the number of EHT-SIG-B (EHT Signal B) content channels depends on the bandwidth and L value according to various embodiments.

[0018] Figure 2C A diagram shows mapping of one or two EHT-SIG-B content channels in a 40MHz EHT MU PPDU.

[0019] Figure 2D A diagram shows mapping of two EHT-SIG-B content channels in an 80MHz EHT MU PPDU.

[0020] Figure 2E A diagram shows mapping of two EHT-SIG-B content channels in an 80+80MHz or 160MHz EHT MU PPDU.

[0021] Figure 2F A diagram shows mapping of two EHT-SIG-B content channels in a 160+160MHz or 320MHz EHT MU PPDU.

[0022] Figure 2G A diagram depicts an example format of an EHT TB (trigger-based) PPDU for uplink MU communications between an AP and multiple STAs in an EHT WLAN.

[0023] Figure 3A A schematic example of a communication apparatus is shown in accordance with various embodiments. The communication apparatus can be implemented as an AP or a STA and used for control signaling in accordance with various embodiments of the present disclosure.

[0024] Figure 3B A flowchart illustrating a communication method in accordance with various embodiments is shown.

[0025] Figure 4A A flowchart illustrating downlink MU communication between an AP and multiple STAs using an EHT MU PPDU in accordance with various embodiments is depicted.

[0026] Figure 4B An EHT-SIG-B field of an EHT MU PPDU is depicted in more detail.

[0027] Figure 5 A flowchart illustrating processing of a received EHT MU PPDU in accordance with one embodiment is depicted.

[0028] Figure 6 A flowchart illustrating processing of a received EHT MU PPDU in accordance with another embodiment is depicted.

[0029] Figure 7A A flowchart illustrating uplink MU communication between an AP and multiple STAs using an EHT trigger frame in accordance with various embodiments is depicted.

[0030] Figure 7B An example format of an EHT trigger frame is depicted.

[0031] Figure 7C A user info field of an EHT trigger frame is depicted in more detail.

[0032] Figure 8 A flowchart illustrating processing of a received EHT trigger frame in accordance with one embodiment is depicted.

[0033] Figure 9A An example Type 1 user info field of an EHT trigger frame is depicted.

[0034] Figure 9B An example Type 2 user info field of an EHT trigger frame is depicted.

[0035] Figure 10 A flowchart illustrating processing of a received EHT trigger frame in accordance with another embodiment is depicted.

[0036] Figure 11 A configuration of a communication device (e.g., an AP) in accordance with various embodiments is shown.

[0037] Figure 12 A configuration of a communication device (e.g., STA) according to various embodiments is shown.

[0038] Those skilled in the art will understand that the elements in the figures are shown for the purpose of simplicity and clarity and are not necessarily to scale. For example, the dimensions of some of the elements in the figures can be exaggerated relative to other elements to help to improve understanding of the present embodiments. DETAILED DESCRIPTION

[0039] Some embodiments of the present disclosure will be described with reference to the accompanying drawings, by way of example only. The same reference numbers in different drawings represent the same elements or parts.

[0040] In the following paragraphs, certain exemplary embodiments are explained with reference to access points (APs) and stations (STAs) for uplink or downlink control signaling, especially in multiple-input multiple-output (MIMO) wireless networks.

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

[0042] For example, a STA can 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. A STA can be fixed or mobile. In a WLAN environment, the terms “STA”, “wireless client”, “user”, “user equipment”, and “node” are often used interchangeably.

[0043] Likewise, an AP (interchangeably referred to as a wireless access point (WAP) in the context of IEEE 802.11 (Wi-Fi) technology) is a communication device that allows STAs in a WLAN to connect to a wired network. An AP is usually connected to a router (via a wired network) as a standalone device, but it can also be integrated with or used in a router.

[0044] As mentioned above, a STA in a WLAN can work as an AP at different occasions and vice versa. This is because a communication device can include both a STA hardware component and an AP hardware component in the context of IEEE 802.11 (Wi-Fi) technology. In this way, a communication device can switch between a STA mode and an AP mode based on actual WLAN conditions and / or requirements.

[0045] In a MIMO wireless network, "multiple" refers to multiple antennas used for transmission at the same time and multiple antennas used for reception at the same time over a radio channel. In this regard, "multiple-input" refers to multiple transmitter antennas that input a radio signal into the channel, and "multiple-output" refers to multiple receiver antennas that receive the radio signal from the channel and input it into the receiver. For example, in an N x M MIMO network system, N is the number of transmitter antennas and M is the number of receiver antennas, and N can or can not be equal to M. For simplicity, the respective number of transmitter antennas and receiver antennas are not further discussed in this disclosure.

[0046] In a MIMO wireless network, single-user (SU) communication and multi-user (MU) communication can be deployed for communication between communication devices such as APs and STAs. A MIMO wireless network has advantages of spatial multiplexing and spatial diversity, which enable higher data rates and robustness by using multiple spatial streams. According to various embodiments, the term "spatial stream" can be used interchangeably with the term "space-time stream" (or STS).

[0047] Figure 1A A diagram depicting SU-MIMO communication 100 between an AP 102 and a STA 104 in a MIMO wireless network is shown. As shown, the MIMO wireless network can include one or more STAs (e.g., STA 104, STA 106, etc.). In the SU-MIMO communication 100, the AP 102 transmits multiple space-time streams using multiple antennas (e.g., four antennas as shown), where all the 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 shown as a group of data transmission arrows 108 directed to the STA 104. Figure 1A

[0048] The SU-MIMO communication 100 can have bi-directional transmissions. As shown, in the SU-MIMO communication 100, the STA 104 can transmit multiple space-time streams using multiple antennas (e.g., two antennas as shown), where all the space-time streams are directed to the AP 102. For simplicity, the multiple space-time streams directed to the AP 102 are shown as a group of data transmission arrows 110 directed to the AP 102. Figure 1A Figure 1A

[0049] In this way, Figure 1A The SU-MIMO communication 100 depicted in FIG. 1A enables uplink and downlink SU transmissions in a MIMO wireless network.

[0050] Figure 1B ​​​A diagram depicting downlink MU-MIMO communication 112 between an AP 114 and multiple STAs 116, 118, 120 in a MIMO wireless network is illustrated. The MIMO wireless network can include one or more STAs (e.g., STA 116, STA 118, STA 120, etc.). In the downlink MU-MIMO communication 112, the AP 114 uses multiple antennas to simultaneously transmit multiple streams to the STAs 116, 118, 120 in the network via spatial mapping or precoding techniques. For example, two space-time streams can be directed to the STA 118, another space-time stream can be directed to the STA 116, and yet another space-time stream can be directed to the STA 120. For simplicity, the two space-time streams directed to the STA 118 are shown as grouped data transmission arrows 124, the space-time stream directed to the STA 116 is shown as data transmission arrow 122, and the space-time stream directed to the STA 120 is shown as data transmission arrow 126.

[0051] Figure 1C A diagram depicting uplink MU-MIMO communication 128 between an AP 130 and multiple STAs 132, 134, 136 in a MIMO wireless network is illustrated. The MIMO wireless network can include one or more STAs (e.g., STA 132, STA 134, STA 136, etc.). In the uplink MU-MIMO communication 128, the STAs 132, 134, 136 simultaneously transmit respective streams to the AP 130 in the network using respective antennas via spatial mapping or precoding techniques. For example, two space-time streams can be directed from the STA 134 to the AP 130, another space-time stream can be directed from the STA 132 to the AP 130, and yet another space-time stream can be directed from the STA 136 to the AP 130. For simplicity, the two space-time streams directed from the STA 134 to the AP 130 are shown as grouped data transmission arrows 140, the space-time stream directed from the STA 132 to the AP 130 is shown as data transmission arrow 138, and the space-time stream directed from the STA 136 to the AP 130 is shown as data transmission arrow 142.

[0052] Due to the packet / PPDU (Physical Layer Protocol Data Unit) based transmission and distributed MAC scheme in 802.11 WLANs, there is no time scheduling (e.g., periodic time slot assignment similar to TDMA (Time Division Multiple Access) for data transmission) in 802.11 WLANs. Frequency and spatial resource scheduling is performed on a packet basis. In other words, resource allocation information is PPDU based.

[0053] In 11ax HE WLANs, only a single resource unit (RU) is allowed to be allocated to a STA. With the increase in maximum channel bandwidth from 160 MHz to 320 MHz, the increase in the maximum number of spatial streams from 8 to 16, and the increase in support for multi-band operation in EHT WLANs, it is an object of the present disclosure to substantially overcome existing challenges to provide a communication apparatus and method for control signaling that allows multiple contiguous or non-contiguous RUs to be allocated to a STA in order to improve spectral efficiency of EHT WLANs relative to 11ax HE WLANs.

[0054] If the MIMO wireless network has very high throughput, such as an EHT WLAN, a PPDU for downlink MU transmission (e.g., a downlink OFDMA (orthogonal frequency division multiple access) transmission including MU-MIMO transmission in a single RU (resource unit) and downlink full-bandwidth MU-MIMO transmission) can be referred to as an EHT MU PPDU 200, as shown in Figure 2A A PPDU for uplink MU transmission (e.g., an uplink OFDMA transmission including MU-MIMO transmission in a single RU and uplink full-bandwidth MU-MIMO transmission) can be referred to as an EHT TB PPDU, as shown in Figure 2B .

[0055] Figure 2AAn example format of an EHT MU PPDU 200 is depicted. Notably, the prefix “EHT” in the above fields can be changed accordingly if the IEEE 802.11 working group can use a new name for the next generation WLAN with extremely high throughput instead of “EHT WLAN”. The EHT MU PPDU 200 can 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 format identification field (FIF) 202, an EHT signal A (EHT-SIG-A) field 204, an EHT signal B (EHT-SIG-B) field 206, an EHT short training field (EHT-STF), an EHT long training field (EHT-LTF), a data field 170, and a packet extension (PE) field. The FIF 202 is mainly used to identify the format of the EHT PPDU. The EHT-SIG-A field 204 contains the necessary information for decoding the EHT-SIG-B field 206, e.g., the modulation and coding scheme (MCS) of the EHT-SIG-B, the number of EHT-SIG-B symbols, as indicated by arrow 204. The EHT-SIG-B field 206 provides OFDMA and MU-MIMO resource allocation information to allow STAs to find the corresponding resources to be used in the data field 210, as indicated by arrow 208. The EHT-STF, EHT-LTF, data field, and PE field can be grouped as an EHT modulation field. The EHT-SIG-B field 206 includes (or consists of) a common field (if present), followed by user-specific fields, which together are referred to as the EHT-SIG-B content channel.

[0056] According to various embodiments, the EHT-SIG-B field 206 of the EHT MU PPDU 200 is separately encoded on each L x 20 MHz subchannel, where L = 1 or 2. In the case of bandwidths greater than 20 MHz, an EHT-SIG-B field with L = 1 can have better EHT-SIG-B decoding performance compared to an EHT-SIG-B field with L = 2. This is because the channel estimation used to decode the EHT-SIG-B field is based on the L-LTF transmitted with a 20 MHz bandwidth. Channel estimation with interpolation is necessary to decode an EHT-SIG-B field with L = 2, which can degrade the performance of decoding an EHT-SIG-B field with L = 2. On the other hand, an EHT-SIG-B field with L = 2 can have less EHT-SIG-B overhead compared to an EHT-SIG-B field with L = 1, especially for larger bandwidths. Furthermore, if the intended STAs of the EHT MU PPDU 200 include at least one 20 MHz operating STA, an EHT-SIG-B field with L = 2 should not be used because an EHT-SIG-B field with L = 2 cannot be decoded by a 20 MHz operating STA. As a result, it is advantageous for the AP to determine the value of L on its own, and signaling can be included in the EHT-SIG-A field of the EHT MU PPDU 200 to indicate whether L takes the value of 1 or 2.

[0057] Figure 2B A table showing how the number of EHT-SIG-B content channels depends on the bandwidth and the value of L according to various embodiments is shown. As Figure 2B shown, in the case of a 20 MHz bandwidth, L can only be 1 because the EHT-SIG-B field is encoded on a per 20 MHz basis and there will only be one EHT-SIG-B content channel. In an embodiment with a 40 MHz bandwidth, the AP can assign a value of 1 or 2 for L. If L is set to “1”, there will be two EHT-SIG-B content channels. If L is set to “2”, there will be only one EHT-SIG-B content channel. In an embodiment with an 80 MHz, 80+80 MHz, 160 MHz, 160+160 MHz, or 320 MHz bandwidth, there will be two EHT-SIG-B content channels regardless of the value of L. More details will be provided below.

[0058] Figure 2C A diagram showing the mapping of one or two EHT-SIG-B content channels in a 40 MHz EHT MU PPDU is shown. The number of EHT-SIG-B content channels depends on the bandwidth and the value of L, as Figure 2BThe 40MHz channel includes two 20MHz sub-channels. When L = 1, there will be two EHT-SIG-B content channels (i.e., EHT-SIG-B content channel 1 and EHT-SIG-B content channel 2) that are transmitted in the 1st and 2nd 20MHz sub-channels, respectively. When L = 2, there will be only one EHT-SIG-B content channel.

[0059] Figure 2D The figure shows the mapping of two EHT-SIG-B content channels (i.e., EHT-SIG-B content channel 1 and EHT-SIG-B content channel 2) in an 80MHz EHT MU PPDU. When L = 1, in an 80MHz channel that includes four 20MHz sub-channels, EHT-SIG-B content channel 1 is duplicated and transmitted in the 1st and 3rd 20MHz sub-channels, while EHT-SIG-B content channel 2 is duplicated and transmitted in the 2nd and 4th 20MHz sub-channels. When L = 2, in an 80MHz channel that includes two 40MHz sub-channels, EHT-SIG-B content channel 1 is transmitted in the 1st 40MHz sub-channel, while EHT-SIG-B content channel 2 is transmitted in the 2nd 40MHz sub-channel.

[0060] Figure 2E The figure shows the mapping of two EHT-SIG-B content channels in an 80+80MHz or 160MHz EHT MU PPDU. When L = 1, in an 80+80MHz or 160MHz channel that includes eight 20MHz sub-channels, EHT-SIG-B content channel 1 is duplicated and transmitted in the 1st, 3rd, 5th, and 7th 20MHz sub-channels, while EHT-SIG-B content channel 2 is duplicated and transmitted in the 2nd, 4th, 6th, and 8th 20MHz sub-channels. When L = 2, in an 80+80MHz or 160MHz channel that includes four 40MHz sub-channels, EHT-SIG-B content channel 1 is duplicated and transmitted in the 1st and 3rd 40MHz sub-channels, while EHT-SIG-B content channel 2 is duplicated and transmitted in the 2nd and 4th 40MHz sub-channels.

[0061] Figure 2FA figure showing the mapping of two EHT-SIG-B content channels in a 160+160 MHz or 320 MHz EHT MU PPDU is shown. When L = 1, in a 160+160 MHz or 320 MHz channel comprising 16 20 MHz sub-channels, EHT-SIG-B content channel 1 is duplicated and transmitted in the 1st, 3rd, 5th, 7th, 9th, 11th, 13th, and 15th 20 MHz sub-channels, while EHT-SIG-B content channel 2 is duplicated and transmitted in the 2nd, 4th, 6th, 8th, 10th, 12th, 14th, and 16th 20 MHz sub-channels. When L = 2, in a 160+160 MHz or 320 MHz channel comprising eight 40 MHz sub-channels, EHT-SIG-B content channel 1 is duplicated and transmitted in the 1st, 3rd, 5th, and 7th 40 MHz sub-channels, while EHT-SIG-B content channel 2 is duplicated and transmitted in the 2nd, 4th, 6th, and 8th 40 MHz sub-channels.

[0062] Figure 2G An example format of an EHT TB PPDU 210 is depicted. The EHT TB PPDU 210 has a similar structure as the EHT MU PPDU 200, but without the EHT-SIG-B field 206. The EHT TB PPDU 210 can include an L-STF, an L-LTF, an L-SIG field, a FIF, an EHT-SIG-A field 212, an EHT-STF, EHT-LTFs, a data field 214, and a PE field. The EHT-STF, EHT-LTFs, data field 214, and PE field can be grouped as an EHT modulation field. The EHT TB PPDU 210 is used in an EHT WLAN for uplink MU transmission in response to a frame carrying trigger information. The frame carrying trigger information can be an EHT trigger frame. Information needed for the uplink MU transmission from one or more STAs is carried by the frame requesting the transmission. In a typical transmission of the EHT TB PPDU 210, EHT-SIG-A related information is duplicated from the previous frame carrying trigger information into the EHT-SIG-A field 212 of the EHT TB PPDU 210.

[0063] Due to the maximum number of spatial streams being 16, the maximum CBW being 320 MHz, and multi-band operation in EHT WLANs, the number of allocations and / or users supported in an EHT TB PPDU can increase significantly. As a result, the frame used to request an EHT TB PPDU transmission can have a much larger signaling overhead than the frame used to request an HE TB PPDU transmission. Devices and methods according to various embodiments can advantageously reduce the signaling overhead, especially when the bandwidth is greater than 20 MHz.

[0064] According to various embodiments, EHT WLAN supports control signaling that allows multiple contiguous or non-contiguous resource units (RUs) to be allocated to a single communication device.

[0065] Figure 3A A schematic partial cutaway view of a communication device 300 according to various embodiments is shown. According to various embodiments, the communication device 300 can be implemented as an AP or a STA.

[0066] As Figure 3A shown, the communication device 300 can include circuitry 314, at least one radio transmitter 302, at least one radio receiver 304, and at least one antenna 312 (for simplicity, only one antenna is depicted in the interest of illustration Figure 3A purposes). The circuitry 314 can include at least one controller 306 for software and hardware assisted execution of tasks for which the at least one controller 306 is designed, including controlling communications with one or more other communication devices in a MIMO wireless network. The circuitry 314 can also include at least one transmit signal generator 308 and at least one receive signal processor 310. The at least one controller 306 can control the at least one transmit signal generator 308 for generating PPDUs (e.g., EHT MU PPDUs or PPDUs containing EHT trigger frames if the communication device 300 is an AP, and EHT TB PPDUs if the communication device 300 is a STA, for example) for transmission by the at least one radio transmitter 302 to one or more other communication devices, and can control the at least one receive signal processor 310 for processing PPDUs (e.g., EHT TB PPDUs if the communication device 300 is an AP, and EHT MU PPDUs or PPDUs containing EHT trigger frames if the communication device 300 is a STA, for example) received by the at least one radio receiver 304 from one or more other communication devices under the control of the at least one controller 306. As Figure 3A shown, the at least one transmit signal generator 308 and the at least one receive signal processor 310 can be independent modules of the communication device 300 that communicate with the at least one controller 306 for the above-described functions. Alternatively, the at least one transmit signal generator 308 and the at least one receive signal processor 310 can be included in the at least one controller 306. It will be appreciated by those skilled in the art that the arrangement of these functional modules is flexible and can vary as actual needs and / or requirements dictate. Data processing, storage, and other related control devices can be provided on appropriate circuit boards and / or in chip sets. In various embodiments, the at least one radio transmitter 302, the at least one radio receiver 304, and the at least one antenna 312 can be controlled by the at least one controller 306.

[0067] The communication device 300 provides functionality needed for control signaling in downlink MU communications. For example, the communication device 300 can be an AP, and the circuitry 314 (e.g., at least one transmission signal generator 308 of the circuitry 314) can generate a transmission signal (e.g., an EHT MU PPDU) including a plurality of user fields (e.g., user fields of user-specific fields in an EHT-SIG-B field of the EHT MU PPDU) and a data field (e.g., in the EHT MU PPDU) including a plurality of RUs. The radio transmitter 302 can transmit the generated transmission signal, wherein a single transmission scheme is applied to one or more of the plurality of RUs allocated to another communication device (e.g., a STA), and wherein one or more of the plurality of user fields are addressed to the other communication device, and the number of the one or more user fields addressed to the other communication device is equal to the number of the one or more RUs allocated to the other communication device, and the one or more user fields addressed to the other communication device respectively correspond to the one or more RUs allocated to the other communication device. This can allow a plurality of contiguous or non-contiguous RUs to be allocated to the other communication device, and can advantageously enable efficient signaling support, and improve spectral efficiency of EHT WLANs over 11ax HE WLANs.

[0068] The communication device 300 can be a STA, and the radio receiver 304 can receive, from another communication device (e.g., an AP), a transmission signal (e.g., an EHT MU PPDU) including a plurality of user fields (e.g., user fields of user-specific fields in an EHT-SIG-B field of the EHT MU PPDU) and a data field (e.g., in the EHT MU PPDU) including a plurality of RUs. The circuitry 314 (e.g., at least one reception signal processor 310 of the circuitry 314) can process the received transmission signal, wherein a single transmission scheme is applied to one or more of the plurality of RUs allocated to the communication device (STA), and wherein one or more of the plurality of user fields are addressed to the communication device, and the number of the one or more user fields addressed to the communication device is equal to the number of the one or more RUs allocated to the communication device, and the one or more user fields addressed to the communication device respectively correspond to the one or more RUs allocated to the communication device.

[0069] The communication apparatus 300 provides functionality needed for control signaling in uplink MU communications. For example, the communication apparatus 300 can be a STA, and the radio receiver 304 can receive, from another communication apparatus (e.g., an AP), a signal (e.g., an EHT Trigger frame) including a plurality of user info fields (e.g., user info fields of a user info list field in an EHT Trigger frame). The circuitry 314 (e.g., at least one transmission signal generator 308 of the circuitry 314) can generate a transmission signal (e.g., an EHT TB PPDU) including a data field (e.g., a data field in an EHT TB PPDU), the data field including a plurality of RUs. The radio transmitter 302 can transmit, to the other transmission apparatus, the generated transmission signal, wherein a single transmission scheme is applied to one or more of the plurality of RUs allocated to the communication apparatus, and wherein one or more of the plurality of user info fields in the signal received from the other transmission apparatus are addressed to the communication apparatus, and the number of the one or more user info fields addressed to the communication apparatus can be less than the number of the one or more RUs allocated to the communication apparatus.

[0070] For example, the communication apparatus 300 can be an AP, and the circuitry 314 (e.g., at least one transmission signal generator 308 of the circuitry 314) can generate a transmission signal (e.g., an EHT Trigger frame) including a plurality of user info fields (e.g., user info fields of a user info list field in an EHT Trigger frame). The radio transmitter 302 can transmit, to the other transmission apparatus, the generated transmission signal. The radio receiver 304 can receive, from another communication apparatus (e.g., a STA), a signal (e.g., an EHT TB PPDU) including a data field (e.g., in an EHT TB PPDU), the data field including a plurality of RUs, wherein a single transmission scheme is applied to one or more of the plurality of RUs allocated to the other communication apparatus, and wherein one or more of the plurality of user info fields in the transmission signal are addressed to the other communication apparatus, and the number of the one or more user info fields addressed to the other communication apparatus can be less than the number of the one or more RUs allocated to the other communication apparatus.

[0071] Figure 3BA flowchart 316 illustrating a communication method for control signaling according to various embodiments is shown. In step 318, a transmit signal is generated including a plurality of user fields and a data field, the data field including a plurality of RUs. In step 320, the generated transmit signal is transmitted to another communication apparatus, wherein a single transmission scheme is applied to one or more of the plurality of RUs allocated to the other communication apparatus, and wherein one or more of the plurality of user fields are addressed to the other communication apparatus, and the number of the one or more user fields addressed to the other communication apparatus is equal to the number of the one or more RUs allocated to the other communication apparatus, and the one or more user fields addressed to the other communication apparatus respectively correspond to the one or more RUs allocated to the other communication apparatus.

[0072] In the following paragraphs, certain example embodiments are explained with reference to an AP and a plurality of STAs for control signaling in downlink MU communication.

[0073] Figure 4AA flow diagram 400 illustrating downlink MU communication between an AP 402 and multiple STAs 404, 406 using an EHT MU PPDU 410 is depicted in accordance with various embodiments. A contention-based channel access procedure (e.g., an enhanced distributed channel access (EDCA) procedure) is shown by block 408, and a short interframe space (SIFS) 411 is shown. The AP 402 can generate a transmit signal (e.g., an EHT MU PPDU) 410 including multiple user fields and a data field including multiple RUs. One or more of the multiple user fields are addressed to the STA 404, and a single transmission scheme is applied to the one or more RUs allocated to the STA 404 for transmission of an A-MPDU (aggregated MAC protocol data unit) to the STA 404, which can contain trigger information for requesting a subsequent EHT TB PPDU transmission from the STA 404. Similarly, one or more of the multiple user fields are addressed to the STA 406, and a single transmission scheme is applied to the one or more RUs allocated to the STA 406 for transmission of another A-MPDU to the STA 406, which can contain trigger information for requesting a subsequent EHT TB PPDU transmission from the STA 406. In accordance with the present disclosure, the number of the one or more user fields addressed to each of the STAs 404, 406 is equal to the number of the one or more RUs allocated to the STAs 404, 406, and the one or more user fields addressed to each of the STAs 404, 406 respectively correspond to the one or more RUs allocated to the STAs 404, 406. In another embodiment, the one or more user fields addressed to each of the STAs 404, 406 contain the same user-specific allocation information. In another embodiment, each of the multiple user fields is a Type 1 user field or a Type 2 user field, and contains signaling for indicating its type; and the one or more user fields addressed to each of the STAs 404, 406 include at least one Type 1 user field. In accordance with one embodiment, the Type 1 user field contains user-specific allocation information, while the Type 2 user field does not contain user-specific allocation information. In one embodiment, each of the at least one Type 1 user field contains signaling for indicating whether a single RU is allocated to each of the STAs 404, 406. In another embodiment, if the number of the one or more RUs allocated to each of the STAs 404, 406 is more than one, the one or more user fields addressed to each of the STAs 404, 406 include at least one Type 2 user field, and each of the at least one Type 2 user field contains signaling for indicating whether the one or more RUs allocated to each of the STAs 404, 406 are contiguous.The radio transmitter of the AP 402 can transmit the generated transmit signal 410 to the STAs 404, 406.

[0074] In an IEEE 802.11 network, SIFS is the time interval before a STA transmits an acknowledgement. The radio receivers of the STAs 404, 406 can receive their respective A-MPDUs in the transmit signal 410 based on the user-specific assignment information contained in the one or more user fields addressed to the STAs 404, 406 and the one or more RUs allocated to the STAs 404, 406, and the circuitry of the STAs 404, 406 can process the received A-MPDUs, respectively. After the last symbol of the transmit signal 410 is transmitted, the SIFS 411 can take effect, and at 413, the radio transmitters of the STAs 404, 406 can simultaneously transmit their respective EHT TB PPDUs 414, 415 based on the trigger information contained in the EHT MU PPDU 410 to acknowledge the successful reception of their respective A-MPDUs.

[0075] Figure 4B The EHT-SIG-B field 206 of the EHT MU PPDU 200 is depicted in more detail. The EHT-SIG-B field 206 includes (or consists of) a common field 420 (if present), followed by user-specific fields 422, which together are referred to as the EHT-SIG-B content channel. The common field 420 contains information about the RU assignment, such as the RU allocation to be used in the EHT modulation field, the RUs assigned for MU-MIMO, and the number of users in the MU-MIMO assignment. The user-specific fields 422 consist of one or more user block fields, each of which includes one or two user fields for the non-MU-MIMO assignment(s) and / or the MU-MIMO assignment(s). For example, the user-specific fields 422 can contain 3 user block fields 1-3, as shown in Figure 4B User block field 1 includes two user fields (e.g., user field 1 and user field 2), user block field 2 includes two user fields (e.g., user field 3 and user field 4), and user block field 3 includes one user field 5, each of which is appended with a cyclic redundancy check (CRC) for detecting errors and tail bits for padding the user block field to a user block field size. In one embodiment, the last user block can consist of one or two user fields, depending on whether the total number of user fields allowed in the user-specific fields 422 refers to an odd or even number.

[0076] According to the present disclosure, the user fields (e.g., user fields 1, 2, 3, 4, and 5) contain user information, i.e., user-specific allocation information, indicating user-specific allocation. For non-MU-MIMO allocation, the user-specific allocation information includes information on the number of spatial streams (NSTS), transmit beamforming (Tx BF), modulation and coding scheme (MCS), dual carrier modulation (DCM), and coding (e.g., error control coding). For MU-MIMO allocation, the user-specific allocation information includes information on spatial configuration, MCS, and coding (e.g., error control coding). According to one embodiment, more information on the subfields STA identifier (ID), NSTS, Tx BF, DCM, MCS, coding, and spatial configuration in the user fields for non-MU-MIMO allocation and MU-MIMO allocation can be found in Table 1 and Table 2, respectively. Table 1 indicates the user field format for non-MU-MIMO allocation, where BCC is binary convolutional code and LDPC is low density parity code.

[0077] (Binary Convolutional Code), and LDPC is low density parity code.

[0078]

[0079] Table 2 indicates the user field format for MU-MIMO allocation, where BCC is binary convolutional code and LDPC is low density parity code.

[0080]

[0081]

[0082] Conventionally, the user fields include a total of 21 bits according to the above format. In order to support up to 16 spatial streams in EHT WLAN, for non-MU-MIMO allocation, the number of bits for the NSTS subfield can be increased from 3 bits to 4 bits; while the number of bits for the spatial configuration subfield can be increased from 4 bits to 6 bits. For both non-MU-MIMO and MU-MIMO allocation, the user fields according to the present disclosure can contain a total of 22 bits, or in other words, one more bit compared to the conventional user fields.

[0083] According to the present disclosure, one or more RUs can be allocated to a STA in an EHT MU PPDU. A single transmission scheme is applied to the one or more RUs allocated to the STA in the EHT MU PPDU, where the transmission scheme is characterized by several parameters included in the user-specific allocation information, such as MCS and coding. The number of user fields addressed to the STA is the same as the number of RUs allocated to the STA. As such, the user fields addressed to the STA uniquely correspond to the RUs allocated to the STA. Specifically, this can be achieved by determining whether the ID of the STA matches the value of the STA ID subfield of the user field, and in response to the ID of the STA matching the value of the STA ID subfield, determining the allocated RU corresponding to the user field based on the RU allocation information in the common field and the location of the user field in the user-specific field in the same EHT-SIG-B channel. According to embodiments of the present disclosure, the one or more user fields corresponding to the one or more RUs allocated to the STA will contain the same user-specific allocation information, i.e., the one or more user fields corresponding to the one or more RUs allocated to the STA will have the same subfield values for the user-specific allocation information, since a single transmission scheme is applied to the one or more RUs. In one embodiment, if two or more consecutive RUs with the same RU size fit exactly into a single RU with a larger RU size, then the two or more consecutive RUs should not be allocated to the STA. For example, two consecutive 26-tone RUs fit exactly into a 52-tone RU, and four consecutive 26-tone RUs fit exactly into a 106-tone RU. This can advantageously maximize tone utilization and reduce the number of user fields in the EHT MU PPDU.

[0084] Figure 5A flowchart 500 illustrating processing of a received EHT MU PPDU according to one embodiment is depicted. The STA processes the EHT-SIG-B field of the received EHT MU PPDU to search for one or more RUs allocated to it. In step 502, the EHT-SIG-B content channel index i can be initialized to 1, indicating the first EHT-SIG-B content channel of the EHT-SIG-B field, and the allocated RU counter can be initialized to 0. In step 504, the user field index j can be initialized to 1, indicating the first user field of the EHT-SIG-B content channel i. In step 506, it can be determined whether the user field j is valid, which is invalid when the CRC check of the user block field containing the user field j fails. In response to determining that the user field j is valid, step 508 is performed. In step 508, it is determined whether the STA ID subfield value of the user field j matches the ID of the STA. In response to determining that the STA ID subfield value matches the ID of the STA, then step 510 is performed. In step 510, the allocated RU corresponding to the user field j is determined according to the RU allocation information in the common field and the position of the user field j in the user-specific field of the EHT-SIG-B content channel i. In step 512, the allocated RU counter can be incremented by 1. In step 514, it is determined whether the allocated RU counter is 1. In response to determining that the allocated RU counter is 1, indicating that one RU (the first RU) has been allocated to the STA, step 516 is performed to obtain the user-specific allocation information, and the processing is directed to step 522. In step 514, if the allocated RU counter is not equal to 1, indicating that more than one RU has been allocated to the STA, then step 518 is performed. In step 518, it is determined whether the user field j contains the same user-specific allocation information as previously obtained from another user field (e.g., user field j-2). If the user field j does not contain the same user-specific allocation information, then the received EHT MU PPDU can be identified as containing an error. Then, in step 520, the EHT MU PPDU is discarded. In step 518, if the user field j contains the same user-specific allocation information, then the processing is directed to step 522.

[0085] Returning to step 506, the user field j can be determined to be invalid, e.g., the CRC check of the user block field containing the user field j fails. In this case, the user field j is not further processed, and the processing of the received EHT MU PPDU will be directed to step 522. Similarly, in step 508, if the STA ID subfield value does not match the ID of the STA, then the user field j is not further processed, and the processing is directed to step 522.

[0086] In step 522, the user field index j can be incremented by 1. Then in step 524, it is determined whether the incremented index value j is greater than the total number of user fields in the EHT-SIG-B content channel i. If the incremented index value j is not greater than the total number of user fields in the EHT-SIG-B content channel i, indicating that at least one user field in the EHT-SIG-B content channel i has not been processed, step 506 is performed using the user field with the incremented index j. If the incremented index value j is greater than the total number of user fields in the EHT-SIG-B content channel i, step 526 is performed instead. In step 526, the index i is incremented by 1. In step 528, it is then determined whether the incremented index value i is greater than the total number of EHT-SIG-B content channels. If the incremented index value i is not greater than the total number of EHT-SIG-B content channels, indicating that at least one EHT-SIG-B content channel has not been processed, step 504 is performed using the user fields in the EHT-SIG-B content channel with the incremented index i. If the incremented index value i is greater than the total number of EHT-SIG-B content channels, indicating that all user fields in all EHT-SIG-B content channels have been processed, the processing of the received EHT MU PPDU can end.

[0087] According to embodiments of the present disclosure, one or more user fields corresponding to one or more RUs allocated to a STA should contain the same user-specific allocation information, i.e., one or more user fields corresponding to one or more RUs allocated to a STA should have the same subfield values. In response to determining in step 514 that the allocated RU counter is not 1, indicating that two or more RUs have been allocated to the STA, in step 518 it is determined whether user field j contains the same user-specific allocation information as obtained from another user field (e.g., user field j-2) previously. In response to determining that user field j contains the same user-specific allocation information, the user-specific allocation information of user field j is not obtained, and the index j is incremented by 1 in step 522, which can correspond to the next user field j+1 (if any). On the other hand, in response to determining that user field j does not contain the same user-specific allocation information, the received EHT MU PPDU can be identified as containing an error, and then discarded in step 520. This error can occur when decoding user fields corresponding to multiple RUs allocated to a STA but belonging to different user block fields.

[0088] According to the present disclosure, if more than one RU is allocated to a STA, all user fields corresponding to the more than one RU allocated to the STA should contain the same user-specific allocation information. In this case, it can be sufficient to obtain the user-specific allocation information from one of the user fields addressed to the STA, while each of the other user fields addressed to the STA can contain information that can help the STA search for and locate its user field. This can advantageously increase the power efficiency of the STA.

[0089] The first user field addressed to the STA refers to the EHT-SIG-B content channel with the lowest index i that contains at least one user field addressed to the STA; while the last user field addressed to the STA refers to the EHT-SIG-B content channel with the highest index i that contains at least one user field addressed to the STA. For example, in the case of a bandwidth of 40 MHz, an EHT MU PPDU with two EHT-SIG-B content channels with RU allocation subfields of 10 and 15, respectively, each RU allocation subfield value referring to the RU allocation pattern defined in IEEE P802.11ax / D5.0, can be received as follows: (i) the RU allocation subfield of EHT-SIG-B content channel 1 being set to 10 refers to the RU allocation pattern of 52-tone RU1, 52-tone RU2, 26-tone RU5, 52-tone RU3, 52-tone RU4, the 5 RUs corresponding to the 5 user fields (UFs) UF1 to UF5 in EHT-SIG-B content channel 1; (ii) the RU allocation subfield of EHT-SIG-B content channel 2 being set to 15 refers to the RU allocation pattern of 52-tone RU5, 52-tone RU6, 26-tone RU14, 52-tone RU7, 52-tone RU8, the 5 RUs corresponding to the 5 user fields UF1 to UF5 in EHT-SIG-B content channel 2. Assuming a non-contiguous RU allocation for the STA, with 4 RUs allocated to the STA, such as 52-tone RU1 and 52-tone RU3 from EHT-SIG-B content channel 1, and 26-tone RU14 and 52-tone RU8 from EHT-SIG-B content channel 2, the first user field addressed to the STA is UF1 in EHT-SIG-B content channel 1, and the last user field addressed to the STA is UF5 in EHT-SIG-B content channel 2.

[0090] According to embodiments of the present disclosure, there are two types of user fields: Type 1 user field contains user-specific assignment information; while Type 2 user field does not contain user-specific assignment information, but includes some RU allocation information, which assists another communication device (e.g., intended STA) to speed up searching its remaining user fields. Each user field contains signaling to indicate whether the user field is Type 1 user field or Type 2 user field, such as a UF Type subfield of the user field. For example, the UF Type subfield is set to 0 to indicate Type 1 user field, and set to 1 to indicate Type 2 user field. In one embodiment, when a single RU is allocated to a STA, Type 1 user field shall correspond to the allocated RU. In such an embodiment, the STA is able to determine the single RU allocation after identifying that the Single RU Assignment Flag subfield of its Type 1 user field is set to 1. Details of Type 1 user field subfields for non-MU-MIMO and MU-MIMO allocations can be found in Tables 3 and 4, respectively.

[0091] Table 3 indicates Type 1 user field subfields for non-MU-MIMO allocation in more detail.

[0092]

[0093]

[0094] Table 4 indicates Type 1 user field subfields for MU-MIMO allocation in more detail.

[0095]

[0096]

[0097] In another embodiment, when multiple non-contiguous RUs are allocated to a STA, the last user field addressed to the STA should be a Type 1 user field and each of the remaining user fields addressed to the STA should be a Type 2 user field. According to this embodiment, only one of the user specific fields includes user specific allocation information for the multiple RUs allocated to the STA. The Contiguous RU Assignment Flag subfield in the Type 2 user field can be set to 0 to indicate that multiple non-contiguous RUs are allocated to the STA. In such an embodiment, the STA is able to: (i) easily locate the next user field addressed to it after identifying a Type 2 user field addressed to the STA, (ii) determine the total number of RUs allocated after identifying a Type 1 user field addressed to the STA, (iii) obtain RU allocation information and user specific allocation information from all user fields addressed to the STA. Details of each subfield contained in the Type 2 user field can be found in Table 5. Details of the Assigned RU info subfield when the Contiguous RU Assignment Flag subfield is set to 0 to indicate that multiple non-contiguous RUs are allocated to the STA can be found in Table 6.

[0098] Table 5 indicates Type 2 user field subfields in more detail.

[0099]

[0100] Table 6 indicates the Assigned RU info subfield when the Contiguous RU Assignment Flag subfield is set to 0.

[0101]

[0102]

[0103] In one embodiment, when multiple contiguous RUs are allocated to a STA, there are two options of configuring the type of user fields addressed to the STA. The first option is that the last user field addressed to the STA should be a type 1 user field and each of the remaining user fields addressed to the STA should be a type 2 user field. According to this option, only one of the user specific fields includes user specific allocation information of the multiple RUs allocated to the STA. The contiguous RU allocation flag subfield in the type 2 user field can be set to 1 to indicate that multiple contiguous RUs are allocated to the STA. In such an embodiment, after identifying the first user field addressed to the STA, the STA can easily locate the remaining user fields addressed to it. This can advantageously minimize the specification impact as the same rule applies when multiple non-contiguous or contiguous RUs are allocated to the STA. In this embodiment, the second option of configuring the type of user fields addressed to the STA when multiple contiguous RUs are allocated to the STA is that the user fields addressed to the STA should instead be either type 1 user fields or type 2 user fields and the first user field addressed to the STA should be a type 2 user field. In this way, the STA can: (i) easily locate the remaining user fields addressed to it after identifying the first user field addressed to it; and (ii) obtain RU allocation information and user specific allocation information from any two adjacent type 1 user fields and type 2 user fields. This utilization of type 1 user fields and type 2 user fields can advantageously speed up the search for all user fields addressed to the STA when multiple contiguous RUs are allocated to the STA, thereby improving the power efficiency of the STA. The details of the allocated RU information subfield when the contiguous RU allocation flag subfield is set to 1 to indicate that multiple contiguous RUs are allocated to the STA can be found in Table 7. Table 7 indicates the allocated RU information subfield when the contiguous RU allocation flag subfield is set to 1.

[0104]

[0105]

[0106] Table 9 depicts an example EHT-SIG-B content channel including RU allocation assigned to three STAs (e.g., STA1, STA2, and STA3), where the bandwidth is 20 MHz. The EHT-SIG-B content channel can include a common field containing a RU allocation subfield and user-specific fields containing seven user fields (e.g., UF1 through UF7). The value of the RU allocation subfield in the common field is 10 refers to RU allocation of 52-tone RU1, 26-tone RU3, 26-tone RU4, 26-tone RU5, 52-tone RU3, 26-tone RU8, 26-tone RU9. Each RU allocation corresponds to one of the user fields UF1 through UF7. One example RU allocation of the seven RUs to the three STAs can be as follows: three non-contiguous RUs can be allocated to STA1, e.g., 52-tone RU1, 52-tone RU3, and 26-tone RU9 corresponding to UF1, UF5, and UF7, respectively; a single RU can be allocated to STA2, e.g., 26-tone RU8 corresponding to UF6; and three contiguous RUs can be allocated to STA3, e.g., 26-tone RU3, 26-tone RU4, and 26-tone RU5 corresponding to UF2 through UF4, respectively.

[0107] With respect to the three non-contiguous RUs allocated to STA1, the last user field addressed to STA1, i.e., UF7, is a Type 1 user field (UF Type subfield = 0), and each of the remaining user fields addressed to STA1, i.e., UF1 and UF5, is a Type 2 user field (UF Type subfield = 1). Specifically, in the Type 1 user field addressed to STA1 (UF7), the Single RU Allocation Flag subfield is set to 0, indicating multiple RUs are allocated to STA1. On the other hand, in the Type 2 user fields addressed to STA1 (UF1 and UF5), the Contiguous RU Allocation Flag subfield is set to 0, indicating multiple non-contiguous RUs are allocated to STA1, and the Number of Assigned RUs subfield is set to 3, indicating a total of three RUs are allocated to STA1. In this way, the Assigned RU Information subfields of UF1 and UF5 are Next Assigned RU subfields, indicating the next RU allocated to STA1. In this case, the Next Assigned RU subfield of UF1 is indicated as 52-tone RU3 corresponding to UF5, and the Next Assigned RU subfield of UF5 is indicated as 26-tone RU9 corresponding to UF7. In this way, after identifying UF1 and UF5 addressed to STA1 (Type 2 user fields), STA1 is able to easily locate the next user field addressed to it.

[0108] As for the single RU 26-tone RU8 allocated to the STA2, the user field (i.e., UF6) corresponding to the allocated RU is a type 1 user field (UF type subfield = 0). Specifically, in the type 1 user field (UF6) addressed to the STA2, the single RU allocation flag subfield is set to 1, indicating that a single RU is allocated to the STA2. As for the three consecutive RUs allocated to the STA3, the same rule as that for the non-consecutive RU allocation can be applied, that is, the last user field (i.e., UF4) addressed to the STA3 is a type 1 user field (UF type subfield = 0), and each of the remaining user fields (i.e., UF2 and UF3) addressed to the STA3 is a type 2 user field (UF type subfield = 1). Specifically, in the type 1 user field (UF4) addressed to the STA3, the single RU allocation flag subfield is set to 0, indicating that multiple RUs are allocated to the STA1. On the other hand, in the type 2 user fields (UF2 and UF3) addressed to the STA3, the consecutive RU allocation flag subfield is set to 1, indicating that multiple consecutive RUs are allocated to the STA1, and the number of allocated RUs subfield is set to 3, indicating that a total of three RUs are allocated to the STA3. In this way, the allocated RU information subfield of the UF2 or UF3 is a RU Position subfield, indicating the position of the RU corresponding to the user field among all the RUs allocated to the STA3. In this case, the RU Position subfield of the UF2 is indicated as the first RU, indicating that the RU corresponding to the UF2 is the first RU among the three RUs allocated to the STA3 (number of allocated RUs subfield = 3), while the RU Position subfield of the UF3 is indicated as the second RU, indicating that the RU corresponding to the UF3 is the second RU among the three RUs allocated to the STA3.

[0109] Table 10 and Table 11 depict an example EHT-SIG-B content channel 1 and an example EHT-SIG-B content channel 2 including RU assignments allocated to four STAs (e.g., STAl, STA2, STA3, and STA4, respectively), where the bandwidth is 40 MHz. Each EHT-SIG-B content channel can include a common field including a RU assignment subfield and a user-specific field including five user fields (e.g., UF1 to UF5). The value of the RU assignment subfield in the common field of EHT-SIG-B content channel 1 is 10, which refers to RU assignments of 52-tone RU1, 52-tone RU2, 26-tone RU5, 52-tone RU3, 52-tone RU4. Each RU assignment corresponds to one of the user fields UF1 to UF5 in EHT-SIG-B content channel 1. The value of the RU assignment subfield in the common field of EHT-SIG-B content channel 2 is 15, which refers to RU assignments of 52-tone RU5, 52-tone RU6, 26-tone RU14, 52-tone RU7, 52-tone RU8. One example RU allocation of the ten RUs to the four STAs can be as follows: three non-contiguous RUs can be allocated to STAl, e.g., 52-tone RU1, 26-tone RU14, and 52-tone RU8 corresponding to UF1 in EHT-SIG-B content channel 1 and UF5 and UF7 in EHT-SIG-B content channel 2, respectively; two non-contiguous RUs can be allocated to STA2, e.g., 52-tone RU2 and 52-tone RU7 corresponding to UF2 in EHT-SIG-B content channel 1 and UF4 in EHT-SIG-B content channel 2; a single RU can be allocated to STA3, e.g., 26-tone RU5 corresponding to UF3 in EHT-SIG-B content channel 1; and four contiguous RUs can be allocated to STA4, e.g., 52-tone RU3, 52-tone RU4, 52-tone RU5, and 52-tone RU6 corresponding to UF4 and UF5 in EHT-SIG-B content channel 1 and UF1 and UF2 in EHT-SIG-B content channel 2, respectively.

[0110] As for the three non-contiguous RUs allocated to STA1, the last user field addressed to STA1 (i.e., UF5 of EHT-SIG-B content channel 2) is a type 1 user field (UF type subfield = 0), and each of the remaining user fields addressed to STA1 (i.e., UF1 of EHT-SIG-B content channel 1 and UF3 of EHT-SIG-B content channel 2) is a type 2 user field (UF type subfield = 1). Specifically, in the type 1 user field addressed to STA1 (UF5 of EHT-SIG-B content channel 2), the UF in Different Conent Channel Flag subfield is set to 1, indicating that at least one user field addressed to STA1 exists in a different EHT-SIG-B content channel, and the Single RU Allocation Flag subfield is set to 0, indicating that multiple RUs are allocated to STA1. On the other hand, in the type 2 user fields addressed to STA1 (UF1 of EHT-SIG-B content channel 1 and UF3 of EHT-SIG-B content channel 2), the Contiguous RU Allocation Flag subfield is set to 0, indicating that multiple non-contiguous RUs are allocated to STA1, and the Number of Allocated RUs subfield is set to 3, indicating that a total of three RUs are allocated to STA1. In this way, the Allocated RU Information subfield refers to the Next Allocated RU subfield, indicating the next RU allocated to STA1. In this case, the Next Allocated RU subfield of UF1 of EHT-SIG-B content channel 1 is indicated as 26-tone RU 14 corresponding to UF3 of EHT-SIG-B content channel 2, and the Next Allocated RU subfield of UF3 of EHT-SIG-B content channel 2 is indicated as 52-tone RU 8 corresponding to UF7. In this way, after identifying UF1 of EHT-SIG-B content channel 1 and UF3 of EHT-SIG-B content channel 2 (type 2 user fields) addressed to STA1, STA1 is able to easily locate the next user field addressed to it.

[0111] Similarly, with respect to the two non-contiguous RUs allocated to STA2, the last user field addressed to STA2 (i.e., UF4 of EHT-SIG-B content channel 2) is a Type 1 user field (UF Type subfield = 0), and each of the remaining user fields addressed to STA2 (i.e., UF2 of EHT-SIG-B content channel 1) is a Type 2 user field (UF Type subfield = 1). Specifically, in the Type 1 user field addressed to STA1 (UF4 of EHT-SIG-B content channel 2), the UF in different content channel flag subfield is set to 1, indicating that at least one user field addressed to STA2 exists in a different EHT-SIG-B content channel, and the single RU allocation flag subfield is set to 0, indicating that multiple RUs are allocated to STA2. On the other hand, in the Type 2 user fields addressed to STA2 (UF2 of EHT-SIG-B content channel 1), the contiguous RU allocation flag subfield is set to 0, indicating that multiple non-contiguous RUs are allocated to STA1, and the number of allocated RU subfield is set to 2, indicating that a total of two RUs are allocated to STA2. As such, the allocated RU information subfield refers to the next allocated RU subfield, indicating the next RU allocated to STA2. In this case, the next allocated RU subfield of UF2 of EHT-SIG-B content channel 1 is indicated as the 52-tone RU7 corresponding to UF4 of EHT-SIG-B content channel 2. As such, after identifying UF2 of EHT-SIG-B content channel 1 addressed to STA2 (Type 2 user field), STA2 is able to easily locate the next user field addressed to it.

[0112] As for the single RU 26 tones RU5 allocated to the STA3, the user field corresponding to the allocated RU, i.e., UF3 of the EHT-SIG-B content channel 1, is a type 1 user field (UF type subfield = 0). Specifically, in the type 1 user field addressed to the STA3 (UF3 of the EHT-SIG-B content channel 1), the single RU allocation flag subfield is set to 1, indicating that a single RU is allocated to the STA3. As for the four consecutive RUs allocated to the STA4, the same rule as for the non-consecutive RU allocation can be applied, that is, the last user field addressed to the STA4, i.e., UF2 of the EHT-SIG-B content channel 2, is a type 1 user field (UF type subfield = 0), and each of the remaining user fields addressed to the STA3, i.e., UF4 and UF5 of the EHT-SIG-B content channel 1 and UF1 of the EHT-SIG-B content channel 2, is a type 2 user field (UF type subfield = 1). Specifically, in the type 1 user field addressed to the STA4 (UF2 of the EHT-SIG-B content channel 2), the UF in different content channels flag subfield is set to 1, indicating that at least one user field addressed to the STA4 exists in a different content channel, and the single RU allocation flag subfield is set to 0, indicating that multiple RUs are allocated to the STA4. On the other hand, in the type 2 user fields addressed to the STA4 (UF4 and UF5 of the EHT-SIG-B content channel 1 and UF1 of the EHT-SIG-B content channel 2), the consecutive RU allocation flag subfield is set to 1, indicating that multiple consecutive RUs are allocated to the STA4, and the number of allocated RUs subfield is set to 4, indicating that a total of four RUs are allocated to the STA4. In this way, the allocated RU information subfields of UF2 and UF3 are the RU position subfields, indicating the positions of the RUs corresponding to the user fields among all the RUs allocated to the STA4. In this case, the RU position subfields of UF4 and UF5 of the content channel 1 are indicated as the first RU and the second RU, indicating that the RUs corresponding to UF4 and UF5 of the EHT-SIG-B content channel 1 are the first RU and the second RU among the four RUs allocated to the STA4, respectively (number of allocated RUs subfield = 4), while the RU position subfield of UF1 of the EHT-SIG-B content channel 2 is indicated as the third RU, indicating that the RU corresponding to this user field is the third RU among the four RUs allocated to the STA4.

[0113] Figure 6A flowchart 600 illustrating processing of a received EHT MU PPDU according to one embodiment is depicted. The STA processes the EHT-SIG-B field of the received EHT MU PPDU to search for one or more RUs allocated to it. In step 602, the EHT-SIG-B content channel index i can be initialized to 1, indicating the first EHT-SIG-B content channel, and the allocated RU counter can be initialized to 0. In step 604, the user field index j can be initialized to 1, indicating the first user field of the EHT-SIG-B content channel i. In step 606, it can be determined whether the user field j is valid, when the CRC check of the user block field containing the user field j fails. In response to determining that the user field j is valid, step 608 is performed. However, if the user field j is not valid, the processing branches to step 636. In step 608, it is determined whether the STA ID subfield value of the user field j matches the ID of the STA. In response to determining that the STA ID subfield value matches the ID of the STA, then step 610 is performed. However, if the STA ID subfield does not match the ID of the STA, the processing branches to step 636. In step 610, the allocated RU corresponding to the user field j is determined according to the RU allocation information in the common field in the EHT-SIG-B content channel i and the position of the user field j in the user-specific field. In step 612, the allocated RU counter can be incremented by 1. In step 614, it is determined whether the UF type subfield of the user field j is set to 0, indicating a type 1 user field. If the user field j is a type 1 user field, step 616 is performed in which the user-specific allocation information is obtained. In step 618, it is determined whether the single RU allocation flag is set to 1 and the allocated RU counter is 1. This step 618 is used to identify whether the received EHT MU PPDU contains an error. In response to determining that the single RU allocation flag is set to 1 and the allocated RU counter is 1, indicating that only one RU is allocated to the STA and only one user field is identified, or in other words, the EHT MU PPDU does not contain an error, the processing can end.

[0114] Returning to step 614, if the user field j is a type 2 user field, then step 620 is performed instead. In step 620, it can be determined whether the consecutive RU allocation flag subfield of the type 2 user field j is set to 1. If the consecutive RU allocation flag subfield is not set to 1, indicating multiple non-consecutive RUs are allocated to the STA, then step 622 is performed. In step 622, the number of allocated RUs is determined according to the number of allocated RUs subfield, and the user field index j and EHT-SIG-B content channel index i are adjusted according to the next allocated RU subfield. Subsequently, the user field with the adjusted index j in the EHT-SIG-B content channel with the adjusted index i is used to perform in step 606. However, if the consecutive RU allocation flag subfield is set to 1 in step 620, indicating multiple consecutive RUs are allocated to the STA, then step 624 is performed instead. In step 624, the number of allocated RUs and the allocated RU counter are determined according to the number of allocated RUs subfield and the RU location subfield. In step 626, it can be determined whether the last user field addressed to the STA is valid, when the CRC check of the user block field containing the last user field fails, the last user field is not valid. If the last user field is valid, then step 616 is performed, in which the user-specific allocation information is obtained; while if the last user field is not valid, then the received EHT MU PPDU can be determined to contain errors, and the EHT MU PPDU is discarded in step 628.

[0115] Returning to step 618, which is used to identify whether the EHT MU PPDU can contain an error when processing the user fields. Specifically, in step 618, if one of (i) the single RU allocation flag subfield is not set to 1 and (ii) the allocated RU counter is not 1 is determined, step 630 is performed. In step 630, if it is determined that the single RU allocation flag is set to 1 but the allocated RU counter is greater than 1, indicating that a single RU should be allocated to the STA but more than one user field has been identified by the STA, then in this case the EHT MU PPDU is identified as containing an error and is discarded in step 628. Otherwise, step 632 is performed. In step 632, if it is determined that the single RU allocation flag is set to 0 but the allocated RU counter is 1, indicating that multiple RUs should be allocated to the STA but only one user field has been identified by the STA, then in this case the EHT MU PPDU is identified as containing an error and is discarded in step 628. Otherwise, in step 634, it is checked whether the allocated RU counter matches the number of allocated RUs obtained from step 622, indicating that it is the last user field (type 1 user field) addressed to the STA, and the EHT MU PPDU does not contain an error, and thus the processing can end.

[0116] In step 636, the user field index j can be incremented by 1. In step 628, it is then determined whether the incremented user field index value j is greater than the total number of user fields in the EHT-SIG-B content channel i. If the incremented user field index value j is not greater than the total number of user fields in the EHT-SIG-B content channel i, indicating that at least one user field in the EHT-SIG-B content channel i has not been processed, then step 606 is performed using the user field with the incremented index j. If the incremented user field index value j is greater than the total number of user fields in the EHT-SIG-B content channel i, then step 640 is performed instead. In step 640, the EHT-SIG-B content channel index i is incremented. In step 642, it is then determined whether the incremented index value i is greater than the total number of EHT-SIG-B content channels. If the incremented index value i is not greater than the total number of EHT-SIG-B content channels, indicating that at least one EHT-SIG-B content channel has not been processed, then step 604 is performed using the first user field in the EHT-SIG-B content channel with the incremented index i. If the incremented index value i is greater than the total number of EHT-SIG-B content channels, indicating that all user fields in all EHT-SIG-B content channels have been processed, then the processing of the received EHT MU PPDU can end.

[0117] In the following paragraphs, certain example embodiments are explained with reference to an AP and a plurality of STAs for control signaling in uplink MU communications.

[0118] An EHT trigger frame can be used to request EHT TB PPDU transmission in uplink MU communications, as well as to carry user-specific RU allocation information and user-specific assignment information. Figure 7A A flow diagram 700 illustrating uplink MU communications between an AP 702 and a plurality of STAs 704, 706 using an EHT trigger frame is depicted in accordance with various embodiments. Block 708 illustrates a contention-based channel access procedure, e.g., an EDCA procedure, and illustrates a SIFS 711. The AP 702 can generate a transmit signal (e.g., an EHT trigger frame) 710 including a plurality of user information fields (e.g., user information fields of a User Info List field in an EHT trigger frame). One or more of the plurality of user information fields are addressed to the STA 704. Similarly, one or more of the plurality of user information fields are addressed to the STA 706. In one embodiment, the one or more user information fields addressed to each of the STAs 704, 706 contain the same user-specific assignment information. In another embodiment, each of the plurality of user information fields is a Type 1 user information field or a Type 2 user information field, and contains signaling to indicate its type; and the one or more user information fields addressed to each of the STAs 704, 706 comprise a single Type 1 user information field. According to one embodiment, the Type 1 user information field contains user-specific assignment information, while the Type 2 user information field does not contain user-specific assignment information. In one embodiment, the Type 1 user information field addressed to each of the STAs 704, 706 contains signaling to indicate whether a single RU is allocated to each of the STAs 704, 706. The Type 1 user information field addressed to each of the STAs 704, 706 also contains signaling to indicate whether multiple contiguous RUs having the same RU size are allocated to each of the STAs 704, 706. In another embodiment, if multiple contiguous RUs or multiple non-contiguous RUs having different RU sizes are allocated to each of the STAs 704, 706, the one or more user information fields addressed to each of the STAs 704, 706 comprise at least one Type 2 user information field. Each of the at least one Type 2 user information field contains signaling to indicate one or more additional RUs allocated to each of the STAs 704, 706. A radio transmitter of the AP 702 can transmit the generated transmit signal 710 to the STAs 704, 706.

[0119] The radio receivers of the STAs 704, 706 can receive the transmit signal 710, and the circuitry of the STAs 704, 706 can process the received transmit signal 710, respectively. After the last symbol of the transmit signal 710 is transmitted, a SIFS 711 can take effect, and at 712, the radio transmitters of the STAs 704, 706 can simultaneously transmit their respective EHT TB PPDUs 714, 715 based on the user-specific RU allocation information and user-specific allocation information contained in the one or more user info fields addressed to the STAs 704, 706.

[0120] Figure 7B An example format of an EHT trigger frame 700 is depicted. The EHT trigger frame 720 can include a frame control field, a duration field, a RA (recipient STA address) field, a TA (transmitter STA address) field, a common info field 722, a user info list field 724 containing one or more user info fields, a padding field, and a FCS (frame check sequence) field. The frame control field, the duration field, the RA field, and the TA field can be grouped in a MAC header of the EHT trigger frame 720. The common info field 722, the user info list field 724, and the padding field can be grouped in a frame body of the EHT trigger frame 720. The common info field 722 contains common parameters for all STAs participating in the uplink MU communication requested by the EHT trigger frame 720. Figure 7C The user info field 724a of the EHT trigger frame is depicted in more detail. The user info list field 724 can contain one or more user info fields, such as the user info field 724a, each of which can include an AID 12 subfield, an RU allocation subfield, an UL FEC (forward error correction) coding type subfield, an UL MCS subfield, an UL DCM (dual carrier modulation) subfield, a spatial stream (SS) allocation subfield 728, an UL target RSSI (received signal strength indicator) subfield, and a trigger-related user info subfield 730. Each user info field 724a contains user-specific RU allocation information and user-specific allocation information, where the user-specific RU allocation information includes information about the RU allocation subfield 726. Specifically, in the uplink MU communication, the user-specific allocation information includes at least information about the UL FEC coding type subfield, the UL MCS subfield, the UL DCM subfield, the SS allocation subfield, and the UL target RSSI subfield. The RU allocation field can have a size of 9 bits to support a 320 MHz bandwidth, and the SS allocation subfield can have a size of 8 bits to support up to 16 spatial streams.

[0121] According to the present disclosure, one or more RUs can be allocated to a STA in an EHT TB PPDU; and a single transmission scheme is applied to the one or more RUs allocated to the STA in the EHT TB PPDU. According to one embodiment, the number of user info fields addressed to a STA is the same as the number of RUs allocated to the STA. In this way, the user info fields addressed to a STA uniquely correspond to the RUs allocated to the STA. All user fields addressed to a STA should contain the same user-specific allocation information, i.e., all subfields of the user info fields addressed to a STA except the RU allocation subfield should have the same subfield values. In one embodiment, all user info fields addressed to a STA are placed contiguously in the user info list field. This can advantageously speed up the search for all user info fields addressed to a STA, thereby can improve the power efficiency of the STA. In one embodiment, if two or more contiguous RUs with the same RU size fit exactly into a single RU with a larger size, the two or more contiguous RUs should not be allocated to a STA. For example, two contiguous 26-tone RUs fit exactly into a 52-tone RU, and four contiguous 26-tone RUs fit exactly into a 106-tone RU. This can advantageously maximize tone utilization.

[0122] Table 8 depicts an example user info list field in an EHT trigger frame including RU assignment allocated to four STAs (e.g., STA1, STA2, STA3, and STA4), where the bandwidth is 40 MHz. For example, the user info list field can include ten user info fields. Each user info field includes an RU assignment subfield indicating RU assignment information. The user info list field can indicate RU assignments such as 52-tone RU1, 52-tone RU2, 26-tone RU5, 52-tone RU3, 52-tone RU4, 52-tone RU5, 52-tone RU6, 26-tone RU14, 52-tone RU7, and 52-tone RU8, where each of the ten RUs corresponds to one user info field based on the RU assignment subfield. All user info fields (UIFs) addressed to STAs are placed contiguously in the user info list field. For example, the first three user info fields (i.e., UIF1-UIF3) are addressed to STA1, corresponding to three non-contiguous RU assignments (e.g., 52-tone RU1, 26-tone RU14, and 52-tone RU8) for STA1; the next two user info fields (i.e., UIF4 and UIF5) are addressed to STA2, corresponding to two non-contiguous RU assignments (e.g., 52-tone RU2 and 52-tone RU7) for STA2; UIF6 is addressed to STA3, corresponding to a single RU assignment (e.g., 26-tone RU5) for STA3; and the contiguous user info fields (i.e., UIF7-UIF10) are addressed to STA4, corresponding to four contiguous RU assignments (e.g., 52-tone RU3, 52-tone RU4, 52-tone RU5, and 52-tone RU6) for STA4.

[0123] Table 8 indicates the user info fields in the user info list field of the EHT trigger frame, and their corresponding AID 12 subfields and RU assignment subfields.

[0124]

[0125]

[0126] Figure 8A flowchart illustrating the processing of a received EHT trigger frame according to one embodiment is depicted. The STA processes the user info list field in the EHT trigger frame to search for one or more RUs allocated to it. In step 802, the UIF counter and the allocated RU counter can be initialized to 0, the UIF counter counts the number of user info fields in the user info list field that have been processed. In step 804, it can be determined whether the AID 12 subfield of the user info field matches the AID (association identifier) of the STA. In response to determining that the AID 12 subfield matches the ID of the STA, step 806 is performed. However, if the AID subfield does not match the ID of the STA, the processing turns to 814. In step 806, the allocated RU is determined according to the RU allocation subfield. In step 808, the allocated RU counter can be incremented by 1. In step 810, it is determined whether the allocated RU counter is 1. In response to determining that the allocated RU counter is 1, indicating that one RU (the first RU) has been allocated to the STA, step 812 is performed and the user specific allocation information is obtained. After obtaining the user specific allocation information, the processing points to step 814. On the other hand, in step 810, in response to determining that the allocated RU counter is not equal to 1, in particular, greater than 1, indicating that more than one RU has been allocated to the STA, the processing points to step 814.

[0127] In step 814, the UIF counter is incremented by 1. In step 816, it is determined whether the UIF counter is equal to the total number of user info fields in the EHT trigger frame. In response to the UIF counter not being equal to the total number of user info fields in the EHT trigger frame, indicating that not all user info fields in the EHT trigger frame have been processed, the step 804 is performed using the consecutive user info field. However, in step 816, if the UIF counter is equal to the total number of user info fields in the EHT trigger frame, indicating that all user info fields in the EHT trigger frame have been processed, the processing of the received EHT trigger frame can end.

[0128] According to embodiments of the present disclosure, there are two types of user info fields in an EHT trigger frame: a type 1 user info field contains user-specific allocation information and is used as the first user info field addressed to a STA; while a type 2 user info field does not contain user-specific allocation information and is used as any subsequent user info field addressed to a STA, especially for the case that multiple consecutive RUs with different RU sizes or multiple non-consecutive RUs are allocated to the STA. Each user info field contains signaling to indicate whether the user info field is a type 1 user info field or a type 2 user info field, such as a UIF type subfield. For example, the UIF type subfield is set to 0 to indicate a type 1 user info field and is set to 1 to indicate a type 2 user info field. In one embodiment, when a single RU or multiple consecutive RUs with the same RU size are allocated to a STA or allocated for random access, a single type 1 user field is used to carry user-specific RU allocation information and user-specific allocation information. In another embodiment, when multiple consecutive RUs with different RU sizes or multiple non-consecutive RUs are allocated to a STA or allocated for random access, a type 1 user field or one or more type 2 user info fields are used to carry user-specific RU allocation information and user-specific allocation information. In another embodiment, an AID 12 subfield of a type 1 user info field or a type 2 user info field is set to a first special value (e.g., 0) to indicate that the type 1 user info field or the type 2 user info field allocates one or more random access RUs to an associated STA; and is set to a second special value (e.g., 2045) to indicate that the type 1 user info field or the type 2 user info field allocates one or more random access RUs to an unassociated STA. By utilizing type 1 user info fields and type 2 user info fields to carry user-specific RU allocation information, the number of user info fields addressed to a STA is less than the number of RUs allocated to the STA when two or more RUs are allocated to the STA. This can advantageously reduce channel overhead.

[0129] Figure 9AAn example Type 1 User Info field 900 of an EHT Trigger frame is depicted. The Type 1 User Info field 900 can include (or consist of) an AID 12 subfield, an RU allocation subfield 902, an UL FEC Encoding Type subfield, an UL MCS subfield, an UL DCM subfield, an SS Allocation subfield, an UL Target RSSI subfield, and a Trigger-Related User Info subfield 906. The Trigger-Related User Info field 906 can further include a UIF Type subfield (set to 0 to indicate Type 1 User Info field), a Contiguous RUs with Same RU Size Flag subfield 910, and an Allocated RU Number subfield 912. As in uplink MU communications, user-specific allocation information includes at least information about the UL FEC Encoding Type subfield, the UL MCS subfield, the UL DCM subfield, the SS Allocation subfield, and the UL Target RSSI subfield of the EHT Trigger frame, while user-specific RU allocation information, such as the Allocated RU used as the first RU allocated to the STA, can be included in the RU allocation subfield 902 of the EHT Trigger frame. The Contiguous RUs with Same RU Size Flag subfield 910 is set to 1 to indicate that a single RU or multiple contiguous RUs with the same RU size are allocated to the STA. When the UIF Type subfield 908 is set to 0 (Type 1 User Info field) and the Contiguous RUs with Same RU Size Flag subfield 910 is set to 1, the Allocated RU Number subfield indicates the number of contiguous RUs allocated to the STA; when the UIF Type subfield 908 is set to 0 (Type 1 User Info field) and the Contiguous RUs with Same RU Size Flag subfield 910 is set to 0, the Allocated RU Number indicates the number of remaining RUs allocated to the STA; and when the UIF Type subfield 908 is set to 0 (Type 1 User Info field), the Contiguous RUs with Same RU Size Flag subfield 910 is set to 1, and the Allocated RU Number subfield is set to 1, only a single RU is allocated to the STA.

[0130] Figure 9BAn example Type 2 User Info field of the EHT Trigger frame 920 is depicted. The Type 2 User Info field 920 can include (or consist of) an AID 12 subfield, a Number of RU Allocation subfield 922, RU Allocation subfields 924a, 924b, 924c, and a Trigger-Related User Info subfield 926. The Trigger-Related User Info field 926 can further include a UIF Type subfield (set to 1 to indicate a Type 2 User Info field) and an Allocated RU Number subfield 930. The Type 2 User Info field does not contain user-specific allocation information and its related fields, thus, RU Allocation subfields such as RU Allocation subfield 1 924a, RU Allocation subfield 2 924b, and RU Allocation subfield 3 924c can be implemented in the Type 2 User Info field 920, where each RU Allocation subfield can indicate an RU allocated to a STA. The Number of RU Allocation subfield 922 can indicate the number of RU Allocation subfields included in the Type 2 User Info field 920, in this case, the Number of RU Allocation subfield 922 is 3, indicating three RU Allocation subfields 924a, 924b, 924c in the Type 2 User Info field 920. The Allocated RU Number subfield in the Type 2 User Info field 920 indicates the number of remaining RUs allocated to a STA in addition to the three RUs included in the RU Allocation subfields 924a, 924b, 924c.

[0131] Table 12 depicts an example User Info List field including RU allocations allocated to three STAs (e.g., STA1, STA2, and STA3), where the bandwidth is 20 MHz. The User Info List field can indicate RU allocations such as 52-tone RU1, 26-tone RU3, 26-tone RU4, 26-tone RU5, 52-tone RU3, 26-tone RU8, and 26-tone RU9. One example RU allocation of the seven RUs to the three STAs can be as follows: three non-contiguous RUs can be allocated to STA1, e.g., 52-tone RU1, 52-tone RU3, and 26-tone RU9; a single RU can be allocated to STA2, e.g., 26-tone RU8; and three contiguous RUs can be allocated to STA3, e.g., 26-tone RU3, 26-tone RU4, and 26-tone RU5. In this example using Type 1 User Info fields and Type 2 User Info fields, the User Info List field can include four User Info fields (e.g., UIF1 through UIF4) to carry the RU allocation information of the seven RUs.

[0132] As to the three non-contiguous RUs allocated to STA1, the Type 1 User Info field is used as the first User Info field addressed to STA1 (UIF Type subfield = 0) and as UF1 in the User Info List field, which contains the user-specific allocation information and the first allocated RU information, i.e., the 52-tone RU1 in the RU Allocation subfield. Specifically, in the Type 1 User Info field addressed to STA1, the Contiguous RU with Same RU Size subfield is set to 0, indicating that multiple contiguous RUs with different RU sizes or multiple non-contiguous RUs are allocated to STA1, and the Number of Allocated RUs subfield is set to 2, indicating that there are two remaining RUs allocated to STA1. The Type 2 User Info field is used as any subsequent User Info field addressed to STA1 (UIF Type subfield = 1) and as UF2 in the User Info List field, which contains the two remaining RUs among the three non-contiguous RUs allocated to STA1, i.e., the 52-tone RU3 and the 26-tone RU9 in the RU Allocation subfields 1 and 2, respectively. Specifically, in the Type 2 User Info field addressed to STA1, the Number of RU Allocations subfield is set to 2, indicating that two RU allocations are included in the Type 2 User Info field, and the Number of Allocated RUs is set to 0, indicating that no remaining RUs are allocated to STA1.

[0133] With respect to the single RU allocated to STA2, the Type 1 User Info field is used as the first User Info field (UIF Type subfield = 0) addressed to STA2 and as UIF3 in the User Info List field, which contains user-specific allocation information and allocated RU information, i.e., 26-tone RU8 in the RU Allocation subfield. Specifically, in the Type 1 User Info field addressed to STA2, both the Contiguous RU Flag subfield and the Number of Allocated RUs subfield with the same RU size are set to 1, indicating a single RU allocation. With respect to the three contiguous RUs allocated to STA3, the Type 1 User Info field is used as the first User Info field (UIF Type subfield = 0) addressed to STA3 and as UIF4 in the User Info List field, which contains user-specific allocation information and first allocated RU information, i.e., 26-tone RU3 in the RU Allocation subfield. Specifically, in the Type 1 User Info field addressed to STA3, the Contiguous RU Flag subfield with the same RU size is set to 1, indicating multiple contiguous RUs with the same RU size are allocated to STA3. In this case, the Number of Allocated RUs subfield is to indicate the number of contiguous RUs with the same RU size allocated to the STA, and the Number of Allocated RUs subfield is set to 3, indicating that there are three contiguous RUs with the same size allocated to STA3. In this way, allocation information of subsequent contiguous RUs with the same RU size does not need to be included in one or more additional User Info fields, and channel overhead can be reduced.

[0134] Table 13 depicts an example User Info List field including RU allocations allocated to four STAs (e.g., STA1, STA2, STA3, and STA4), where the bandwidth is 20 MHz. The User Info List field can indicate RU allocations such as 52-tone RU1, 52-tone RU2, 26-tone RU5, 52-tone RU3, 52-tone RU4, 52-tone RU5, 52-tone RU6, 26-tone RU14, 52-tone RU7, and 52-tone RU8. One example RU allocation allocating ten RUs to the four STAs is as follows: three non-contiguous RUs can be allocated to STA1, e.g., 52-tone RU1, 26-tone RU14, and 52-tone RU8; two non-contiguous RUs can be allocated to STA2, e.g., 52-tone RU2 and 52-tone RU7; a single RU can be allocated to STA3, e.g., 26-tone RU5; and four contiguous RUs can be allocated to STA4, e.g., 52-tone RU3, 52-tone RU4, 52-tone RU5, and 52-tone RU3. In this example using Type 1 User Info fields and Type 2 User Info fields, the User Info List field can include six User Info fields (e.g., UIF1-UIF6) to carry RU allocation information of the ten RUs.

[0135] With respect to the three non-contiguous RUs allocated to STA1, a Type 1 User Info field is used as the first User Info field addressed to STA1 (UIF Type subfield = 0), as UIF1 in the User Info List field, which contains user-specific allocation information and first allocated RU information, i.e., 52-tone RU1 in the RU Allocation subfield. Specifically, in the Type 1 User Info field addressed to STA1, the Contiguous RUs with Same RU Size flag subfield is set to 0, indicating that multiple contiguous RUs or multiple non-contiguous RUs with different RU sizes are allocated to STA1, and the Number of Allocated RUs subfield is set to 2, indicating that two remaining RUs are allocated to STA1. A Type 2 User Info field is used as any subsequent User Info field addressed to STA1 (UIF Type subfield = 1), and as UIF2 in the User Info List field, which indicates the two remaining RUs among the three non-contiguous RUs allocated to STA1, i.e., 26-tone RU14 and 52-tone RU8 in RU Allocation subfields 1 and 2, respectively. Specifically, in the Type 2 User Info field addressed to STA1, the Number of RU Allocations subfield is set to 2, indicating that two RU allocations are included in the Type 2 User Info field, and the Number of Allocated RUs is set to 0, indicating that no remaining RUs are allocated to STA1.

[0136] With respect to the three non-contiguous RUs allocated to STA1, a Type 1 User Info field is used as the first User Info field addressed to STA1 (UIF Type subfield = 0), as UIF1 in the User Info List field, which contains user-specific allocation information and first allocated RU information, i.e., 52-tone RU1 in the RU Allocation subfield. Specifically, in the Type 1 User Info field addressed to STA1, the Contiguous RUs with Same RU Size flag subfield is set to 0, indicating that multiple contiguous RUs or multiple non-contiguous RUs with different RU sizes are allocated to STA1, and the Number of Allocated RUs subfield is set to 2, indicating that two remaining RUs are allocated to STA1. A Type 2 User Info field is used as any subsequent User Info field addressed to STA1 (UIF Type subfield = 1), and as UIF2 in the User Info List field, which indicates the two remaining RUs among the three non-contiguous RUs allocated to STA1, i.e., 26-tone RU14 and 52-tone RU8 in RU Allocation subfields 1 and 2, respectively. Specifically, in the Type 2 User Info field addressed to STA1, the Number of RU Allocations subfield is set to 2, indicating that two RU allocations are included in the Type 2 User Info field, and the Number of Allocated RUs is set to 0, indicating that no remaining RUs are allocated to STA1.

[0137] Regarding the single RU allocated to STA3, the Type 1 User Info field is used as the first User Info field (UIF Type subfield = 0) addressed to STA2 and as UIF5 in the User Info List field, which contains user-specific allocation information and single allocated RU information, i.e., 26-tone RU5 in the RU Allocation subfield. Specifically, in the Type 1 User Info field addressed to STA3, both the Contiguous RU Flag subfield and the Number of Allocated RUs subfield with the same RU size are set to 1, indicating single RU allocation. Regarding the four contiguous RUs allocated to STA4, the Type 1 User Info field is used as the first User Info field (UIF Type subfield = 0) addressed to STA4 and as UIF6 in the User Info List field, which contains user-specific allocation information and first allocated RU information, i.e., 52-tone RU3 in the RU Allocation subfield. Specifically, in the Type 1 User Info field addressed to STA4, the Contiguous RU Flag subfield with the same RU size is set to 1, indicating multiple contiguous RUs with the same RU size are allocated to STA4. In this case, the Number of Allocated RUs subfield is the number of contiguous RUs with the same RU size allocated to the STA, and the Number of Allocated RUs subfield is set to 4, indicating that there are four contiguous RUs with the same RU size allocated to STA3. In this way, allocation information of the subsequent contiguous RUs with the same size does not need to be included in one or more additional User Info fields, and channel overhead can be reduced.

[0138] Figure 10A flowchart illustrating processing of a received EHT trigger frame according to another embodiment is depicted. The STA processes the user info list field in the EHT trigger frame to search for one or more RUs allocated to it. In step 1002, a UIF counter and an allocated RU counter can be initialized to 0, the UIF counter counts the number of user info fields in the user info list field that have been processed. In step 1004, it can be determined whether the AID 12 subfield of the user info field matches the AID of the STA. In response to determining that the AID 12 subfield matches the AID of the STA, step 1006 is performed. However, if the AID subfield does not match the AID of the STA, processing branches to 1026. In step 1006, it is determined whether the UIF type subfield of the user info field is set to 0, which means a type 1 user info field. If the user info field is a type 1 user info field, step 1008 is performed. In step 1008, the allocated RU counter is incremented by 1. In step 1010, the allocated RU is determined according to the RU assignment subfield of the user info field. In step 1012, the user specific assignment information is then obtained. In step 1014, it is determined whether the contiguous RU with same RU size flag subfield is set to 1. In response to determining that the contiguous RU with same RU size flag subfield is set to 1, indicating a single RU or multiple contiguous RUs with the same RU size are allocated to the STA, step 1016 is performed. However, if the contiguous RU with same RU size subfield is set to 0, indicating multiple contiguous RUs with different RU sizes or multiple non-contiguous RUs are allocated to the STA, processing can branch to step 1026. In step 1016, it is determined whether the allocated RU number subfield is set to 1. In response to determining that the allocated RU number subfield is set to 1, indicating a single RU is allocated to the STA in this case, processing can end. If the allocated RU number subfield is not equal to 1, step 1018 is performed instead. In step 1018, all remaining allocated RUs are determined according to the RU assignment subfield and the allocated RU number subfield.

[0139] Returning to step 1006, the user info field is a type 2 user info field, step 1020 is performed instead. In 1020, the allocated RU counter is incremented according to the RU assignment number subfield. In step 1022, one or more remaining allocated RUs are determined according to the RU assignment number subfield and the corresponding one or more RU assignment subfields. In step 1024, it is determined whether the allocated RU number subfield is set to 0. In response to determining that the allocated RU number subfield is set to 0, indicating no remaining RUs are allocated to the STA, processing can end. If the allocated RU number subfield is not 0, processing can branch to 1026.

[0140] In step 1026, the UIF counter is incremented by 1. In step 1028, it is determined whether the UIF counter is equal to the total number of user information fields in the EHT trigger frame. In response to the UIF counter not being equal to the total number of user information fields in the EHT trigger frame, it is indicated that not all user information fields in the EHT trigger frame have been processed, and then step 1004 is performed using the consecutive user information field. However, in step 1028, if the UIF counter is equal to the total number of user information fields in the EHT trigger frame, it is indicated that all user information fields in the EHT trigger frame have been processed, and then the processing of the received EHT trigger frame can end.

[0141] Figure 11 A configuration of a communication device 1100 (e.g., an AP) according to various embodiments is shown. Similar to the illustrative example of the communication apparatus 300 shown in FIG. 3, the communication apparatus 1100 includes circuitry 1102, at least one radio transmitter 1110, at least one radio receiver 1112, at least one antenna 1114 (for simplicity, only one antenna is depicted in Figure 11 the circuitry 1102 can include at least one controller 1108 for software and hardware-assisted execution of tasks of the controller 1108 designed to perform communications for control signaling. The circuitry 1102 can also include a transmit signal generator 1104 and a receive signal processor 1106. The at least one controller 1108 can control the transmit signal generator 1104 and the receive signal processor 1106. The transmit signal generator 1104 can include an MPDU generator 1122, a control signaling generator 1124, and a PPDU generator 1126. The MPDU generator 1122 can generate A-MPDUs, e.g., data frames or EHT trigger frames. The control signaling generator 1124 can generate control signaling fields of a PPDU to be generated, e.g., EHT-SIG-A and EHT-SIG-B fields of an EHT MU PPDU. The PPDU generator 1126 can generate a PPDU, e.g., an EHT MU PPDU.

[0142] The receiving signal processor 1106 may include a data demodulator and decoder 1134, which can demodulate and decode the data portion of the received signal (e.g., the data field of an EHT TB PPDU). The receiving signal processor 1106 may also include a control demodulator and decoder 1134, which can demodulate and decode the control signaling portion of the received signal (e.g., the EHT-SIG-A field of an EHT TB PPDU). At least one controller 1108 may include a control signaling parser 1142 and a scheduler 1144. The scheduler 1144 can determine RU information and user-specific dispatch information for dispatching downlink MU transmissions, as well as trigger information for dispatching uplink MU transmissions. The control signaling parser 1142 can analyze the control signaling portion of the received signal and the trigger information for dispatching uplink MU transmissions shared by the scheduler 1144, and assist the data demodulator and decoder 1132 in demodulating and decoding the data portion of the received signal.

[0143] Figure 12 The configuration of a communication device 1200 (e.g., STA) according to various embodiments is shown. Similar to the schematic example of the communication device 300 shown in FIG3, the communication device 1200 includes circuitry 1202, at least one radio transmitter 1210, at least one radio receiver 1212, and at least one antenna 1214 (for simplicity, in...). Figure 12 (Only one antenna is depicted in the image). Circuit 1202 may include at least one controller 1208 for software and hardware-assisted execution of tasks designed to perform communication for control signaling. Circuit 1208 may also include a receive signal processor 1204 and a transmit signal generator 1206. At least one controller 1208 may control the receive signal processor 1204 and the transmit signal generator 1206. The receive signal processor 1204 may include a data demodulator and decoder 1232 and a control demodulator and decoder 1234. The control demodulator and decoder 1234 may demodulate and decode the control signaling portion of the received signal (e.g., the EHT-SIG-A and EHT-SIG-B fields of an EHT MU PPDU). The data demodulator and decoder 1232 may demodulate and decode the data portion of the received signal (e.g., the data fields of an EHT MU PPDU) based on its own assigned RU information and user-specific assignment information.

[0144] At least one controller 1208 may include a control signaling parser 1242, a scheduler 1244, and a trigger information parser 1246. The control signaling parser 1242 may analyze the control signaling portion of a received signal (e.g., the EHT-SIG-A and EHT-SIG-B fields of an EHT MU PPDU), and an auxiliary data demodulator and decoder 1932 may demodulate and decode the data portion of the received signal (e.g., the data fields of an EHT MU PPDU). The trigger information parser 1948 may analyze trigger information for its own uplink dispatch from received trigger frames (e.g., EHT trigger frames) in MU communication. The transmit signal generator 1204 may include a control signaling generator 1224 that may generate control signaling fields (e.g., the EHT-SIG-A field of an EHT TB PPDU) for the PPDU to be generated. The transmit signal generator 1204 may also include a PPDU generator 1226 that generates PPDUs (e.g., EHT TB PPDUs). The transmit signal generator 1204 may also include an MPDU generator 1222 that can generate A-MPDUs, such as data frames.

[0145] As described above, embodiments of this disclosure provide an advanced communication system, communication method, and communication apparatus for control signaling in extremely high throughput MIMO WLAN networks, and improve spectral efficiency in MIMO WLAN networks.

[0146] This disclosure can be implemented through software, hardware, or a combination of software and hardware. Each functional block used in the description of each of the above embodiments can be implemented partially or entirely by an LSI (such as an integrated circuit), and each process described in each embodiment can be controlled partially or entirely by the same LSI or a combination of LSIs. An LSI can be formed as a single chip, or a chip can be formed to include some or all of the functional blocks. An LSI can include data inputs and outputs coupled thereto. Depending on the level of integration, the LSI here can be referred to as an IC, a system LSI, a super LSI, or an ultra-LSI. However, the technology for implementing integrated circuits is not limited to LSIs and can be implemented using dedicated circuits, general-purpose processors, or special-purpose processors. Furthermore, FPGAs (Field-Programmable Gate Arrays) that can be programmed after the LSI is manufactured, or reconfigurable processors in which the connections and settings of circuit cells disposed within the LSI can be reconfigured, can be used. This disclosure can be implemented as digital or analog processing. If future integrated circuit technologies replace LSIs due to advancements in semiconductor technology or other derivative technologies, these functional blocks can be integrated using future integrated circuit technologies. Biotechnology can also be applied.

[0147] The present disclosure can be implemented by any kind of apparatus, device, or system with a communication function (referred to as a communication apparatus).

[0148] The communication apparatus can include a transceiver and a processing / control circuit. The transceiver can include and / or function as a receiver and a transmitter. As the transmitter and the receiver, the transceiver can include an RF (Radio Frequency) module (including an amplifier, an RF modulator / demodulator, and the like) and one or more antennas.

[0149] Some non-limiting examples of such a communication apparatus include a telephone (e.g., cellular (cell) phone, smart phone), a tablet, a personal computer (PC) (e.g., laptop, desktop, netbook), a camera (e.g., digital still / video camera), a digital player (digital audio / video player), a wearable device (e.g., wearable camera, smart watch, tracking device), a game console, a digital book reader, a remote health / telemedicine device, and a vehicle that provides a communication function (e.g., automobile, airplane, ship), and various combinations thereof.

[0150] The communication apparatus is not limited to be portable or movable, and can also include any kind of non-portable or stationary apparatus, device, or system, such as a smart home device (e.g., appliance, lighting, smart meter, control panel), a vending machine, and any other "thing" in an "Internet of Things (IoT)" network.

[0151] The communication can include exchanging data through, for example, a cellular system, a wireless LAN system, a satellite system, and the like, and various combinations thereof.

[0152] The communication apparatus can include a device such as a controller or a sensor that is coupled to a communication device that performs a communication function described in the present disclosure. For example, the communication apparatus can include a controller or a sensor that generates a control signal or a data signal used by a communication device that performs a communication function of the communication apparatus.

[0153] The communication apparatus can also include infrastructure such as a base station, an access point, and any other apparatus, device, or system that communicates with or controls the apparatuses in the above-described non-limiting examples.

[0154] It should be appreciated that although some attributes of various embodiments have been described with reference to devices, corresponding attributes also apply to methods of various embodiments, and vice versa.

[0155] Those skilled in the art will appreciate that the disclosure shown in the specific embodiments can be varied and / or modified without departing from the spirit or scope of the broadly described disclosure. Accordingly, the current embodiments are considered illustrative and not restrictive, in all respects.

[0156] Table 9 indicates an example EHT-SIG-B content channel for a bandwidth of 20 MHz.

[0157]

[0158] Table 10 indicates an example EHT-SIG-B content channel 1 for a bandwidth of 40 MHz.

[0159]

[0160]

[0161] Table 11 indicates an example EHT-SIG-B content channel 2 for a bandwidth of 40 MHz.

[0162]

[0163] Table 12 indicates an example user info list field for a bandwidth of 20 MHz

[0164]

[0165]

[0166] Table 13 indicates an example user info list field for a bandwidth of 40 MHz.

[0167]

[0168]

Claims

1. A communication apparatus comprising: a transmitter that transmits a trigger frame including a user field containing an association identifier (12 AID 12) subfield and signaling for indicating a plurality of resource units (RUs); and a receiver that receives a trigger-based TB physical layer protocol data unit (PPDU) transmitted using the plurality of RUs from a station identified by the AID 12 subfield, wherein if two or more consecutive RUs of the same size fit exactly into a single RU of a larger size, the two or more consecutive RUs are not allocated as the plurality of RUs to the STA.

2. The communication apparatus of claim 1, wherein, the plurality of RUs having the same RU size.

3. The communication apparatus of claim 1, wherein the plurality of RUs having different RU sizes.

4. The communication apparatus of claim 1, wherein, the plurality of RUs being a plurality of consecutive RUs.

5. The communication apparatus of claim 1, wherein the plurality of RUs being a plurality of non-consecutive RUs.

6. The communication apparatus of claim 1, wherein the plurality of RUs being indicated by a set of two subfields in the user field.

7. The communication apparatus of claim 1, wherein the trigger frame including a first type of user field and a second type of user field, the second type of user field not carrying a portion of user-specific information carried in the first type of user field.

8. A communication method comprising: transmitting a trigger frame including a user field containing an association identifier (12 AID 12) subfield and signaling for indicating a plurality of resource units (RUs); and receiving a trigger-based TB physical layer protocol data unit (PPDU) transmitted using the plurality of RUs from a station identified by the AID 12 subfield, wherein if two or more consecutive RUs of the same size fit exactly into a single RU of a larger size, the two or more consecutive RUs are not allocated as the plurality of RUs to the STA.

Images