Integrated circuit for first communication device

Abstract

The present disclosure provides an integrated circuit for a first communication device comprising at least one input to input an electrical signal, and a control circuit to: receive a trigger frame from a second communication device, the trigger frame assigning a portion of a transmission opportunity (TXOP) to the first communication device; and transmitting more than one physical layer protocol data unit (PPDU) within the portion of the TXOP, the trigger frame including a user information field for the first communication device, the user information field including a resource unit allocation sub-field representing a frequency resource, the resource unit allocation sub-field including a resource unit allocation sub-field for the first communication device, the resource unit allocation sub-field representing a frequency resource. And the more than one PPDU is transmitted within the frequency resource, and after receiving the trigger frame, the second communication device no longer transmits a user information field for the first communication device within the portion of the TXOP.

Description

[0001] This application is a divisional application of the Chinese invention patent application with application date of November 29, 2019 and application number 201980087760.1. Technical Field

[0002] The present disclosure relates to a communication device and method for persistent allocation (PA), and more particularly, to a communication device and method for PA in an EHT WLAN (Extremely High Throughput Wireless Local Area Network). Background Art

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

[0004] In order to provide significant peak throughput and capacity increases over 802.11ax High-Efficiency (HE) WLANs in EHT WLANs, it is necessary to increase the maximum channel bandwidth from 160 MHz to 320 MHz, increase the maximum number of spatial streams from 8 to 16, and support multi-band operation.

[0005] However, communication apparatus and methods for persistent allocation (PA) in the context of EHT WLAN have not been discussed.

[0006] Therefore, there is a need for a communication device and method that provides a feasible technical solution for PA in the context of EHT WLAN.Furthermore, 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 the background of the disclosure. Summary of the invention

[0007] Non-limiting and exemplary embodiments facilitate providing a communication apparatus and a communication method for persistent allocation in the context of an EHT WLAN.

[0008] According to one embodiment of the present disclosure, a communication device is provided, comprising: a circuit, which generates a first transmission signal, the first transmission signal including user information of multiple users for downlink MU-MIMO allocation, each user information indicating a user-specific allocation, and also generates a second transmission signal, the second transmission signal including a common field, a user-specific field and a data field, the data field containing a transmission of the downlink MU-MIMO allocation; and a transmitter, which sends the first transmission signal and the second transmission signal, wherein the user-specific allocation of the downlink MU-MIMO allocation is determined to be persistent or non-persistent.

[0009] According to another embodiment of the present disclosure, a communication method is provided, including: generating a first transmit signal, the first transmit signal including user information of multiple users for downlink MU-MIMO allocation, each user information indicating a user-specific allocation; generating a second transmit signal, the second transmit signal including a common field, a user-specific field and a data field, the data field containing a transmission of the downlink MU-MIMO allocation, and sending the first transmit signal and the second transmit signal, wherein the user-specific allocation of the downlink MU-MIMO allocation is determined to be persistent or non-persistent.

[0010] According to another embodiment of the present disclosure, an integrated circuit for a first communication device is provided, the integrated circuit comprising: at least one input terminal, an input electrical signal, and a control circuit, controlling: receiving a trigger frame from a second communication device, the trigger frame allocating a portion of a transmission opportunity TXOP to the first communication device; and sending more than one physical layer protocol data unit PPDU within the portion of the TXOP, the trigger frame comprising a user information field for the first communication device, the user information field comprising a resource unit allocation subfield, the resource unit allocation subfield representing a frequency resource, and the more than one PPDU is sent within the frequency resource, and after receiving the trigger frame, the second communication device no longer sends the user information field for the first communication device within the portion of the TXOP.

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

[0012] Additional benefits and advantages of the disclosed embodiments will become apparent from the specification and drawings. Benefits and / or advantages may be obtained individually from various embodiments and features of the specification and drawings, and all of these embodiments and features do not need to be provided in order to obtain one or more of such benefits and / or advantages. BRIEF DESCRIPTION OF THE DRAWINGS

[0013] Embodiments of the present disclosure will be better understood and readily appreciated by those of ordinary skill in the art through the following written description (by way of example only) in conjunction with the accompanying drawings, in which:

[0014] Figure 1A A schematic diagram depicting uplink and downlink single-user MIMO communications between an access point (AP) and a station (STA) in a multiple-input multiple-output (MIMO) wireless network is depicted.

[0015] Figure 1BA schematic diagram depicts downlink MU-MIMO (MU-MIMO) communication between an AP and multiple STAs in a MIMO wireless network.

[0016] Figure 1C Schematic diagram depicting uplink MU-MIMO communication between an AP and multiple STAs in a MIMO wireless network.

[0017] Figure 1D The format of the PPDU (physical layer protocol data unit) used for downlink multi-user communication between an AP and multiple STAs in a HE WLAN is shown.

[0018] Figure 1E The HE-SIG-B (HE Signal B) field is depicted in more detail.

[0019] Figure 1F The format of the PPDU used for uplink multi-user communication between an AP and multiple STAs in a HE WLAN is shown.

[0020] Figure 2A An EHT MU PPDU is depicted.

[0021] Figure 2B An EHT TB (trigger-based) PPDU is depicted.

[0022] Figure 3A Schematic examples of communication devices according to various embodiments are shown. According to various embodiments of the present disclosure, the communication device may be implemented as an AP or a STA and configured for user-specific persistent allocation (PA).

[0023] FIG. 3B to FIG. 3E A flow chart illustrating a communication method according to various embodiments is shown.

[0024] Figure 4A Depicted is a flow chart illustrating communication between multiple STAs and an AP with uplink user-specific PAs through TXOPs (Transmission Opportunities) according to various embodiments.

[0025] Figure 4B Depicted is a flow diagram illustrating communication between multiple STAs and an AP with uplink user-specific PAs over two TXOPs in accordance with various embodiments.

[0026] Figure 5A and Figure 5B The format of an EHT basic trigger frame for uplink multi-user communication between an AP and a plurality of STAs in an EHT WLAN according to the first embodiment is shown.

[0027] Figure 5CThe PA trigger frame for uplink multi-user communication according to the first embodiment or the third embodiment is shown.

[0028] Figure 5D A data or management frame carrying a PA control subfield for uplink multi-user communication according to the first embodiment or the third embodiment is shown.

[0029] Figure 5E A MU-MIMO allocation including three user-specific allocations according to various embodiments is shown.

[0030] Fig. 6A A flow chart showing processing of a received EHT basic trigger frame at a STA according to a first embodiment is shown.

[0031] Figure 6B A flow chart showing processing of a received PA trigger frame at a STA according to the first embodiment is shown.

[0032] Figure 6C A flow chart illustrating processing of a received data or management frame carrying a PA Control subfield at a STA according to the first embodiment is shown.

[0033] Fig. 7A and Figure 7B The format of an EHT basic trigger frame for uplink multi-user communication between an AP and a plurality of STAs in an EHT WLAN according to the second embodiment is shown.

[0034] Figure 7C The PA trigger frame for uplink multi-user communication according to the second embodiment or the fourth embodiment is shown.

[0035] Fig.7D A data or management frame carrying a PA control subfield for uplink multi-user communication according to the second embodiment or the fourth embodiment is shown.

[0036] Fig. 8A A flow chart showing processing of a received EHT basic trigger frame at a STA according to a second embodiment is shown.

[0037] Figure 8B A flowchart showing processing of a received PA trigger frame at a STA according to the second embodiment or the fourth embodiment is shown.

[0038] Figure 8C A flow chart showing processing of a received data or management frame carrying a PA control field at a STA according to the second embodiment or the fourth embodiment is shown.

[0039] Fig.9ADepicted is a flow diagram illustrating communication over a TXOP between multiple STAs and an AP with uplink user-specific PAs in accordance with various embodiments.

[0040] Fig. 9B Depicted is a flow diagram illustrating communication between multiple STAs and an AP with uplink user-specific PAs over two TXOPs in accordance with various embodiments.

[0041] Fig. 10A A format of an EHT announcement frame for uplink or downlink multi-user communication between an AP and a plurality of STAs in an EHT WLAN according to a third embodiment is shown.

[0042] Fig. 10B The format of an EHT basic trigger frame for uplink multi-user communication between an AP and a plurality of STAs in an EHT WLAN according to the third embodiment is shown.

[0043] Fig.11 A flow chart showing processing of a received EHT basic trigger frame at a STA according to a third embodiment is shown.

[0044] Fig.12 A format of an EHT announcement frame for uplink or downlink multi-user communication between an AP and a plurality of STAs in an EHT WLAN according to a fourth embodiment is shown.

[0045] Fig.13 A flowchart illustrating processing of a received EHT Basic Trigger frame at a STA according to a fourth embodiment is shown.

[0046] Fig.14A and Fig. 14B A flow chart showing communication between an AP and a STA having a downlink user-specific PA according to the third embodiment or the fourth embodiment is shown.

[0047] Fig.15A The structure of the user information field of the downlink user-specific PA of the non-MU-MIMO allocation according to the third embodiment or the fourth embodiment is depicted.

[0048] Fig. 15B The structure of the user information field of the downlink user-specific PA allocated by MU-MIMO according to the third embodiment or the fourth embodiment is depicted.

[0049] Fig.16A A table showing how the number of EHT-SIG-B content channels depends on the channel bandwidth (CBW) and the value of L.

[0050] Fig. 16BA diagram showing the mapping of one or two EHT-SIG-B content channels in a 40 MHz EHT MU PPDU.

[0051] Fig. 16C A diagram showing the mapping of two EHT-SIG-B content channels in an 80 MHz EHT MU PPDU.

[0052] Fig.16D A diagram showing the mapping of two EHT-SIG-B content channels in an EHT MU PPDU of 80+80 MHz or 160 MHz.

[0053] Fig.16E A diagram showing the mapping of two EHT-SIG-B content channels in an EHT MU PPDU of 160+160 MHz or 320 MHz.

[0054] Fig.17A The EHT-SIG-B field according to the third embodiment or the fourth embodiment is depicted.

[0055] Fig. 17B Describes the basis Figure 3B The EHT-SIG-B field of the embodiment shown.

[0056] Fig.18A and Fig.18B The mapping between the PA presence subfield in the EHT signal A (EHT-SIG-A) field, the RU allocation subfield in the EHT-SIG-B field, the Center 26-Tone RU subfield, and the PA bitmap subfield is depicted.

[0057] Fig.19A A first example of the encoding structure of the common field according to the third embodiment or the fourth embodiment is depicted.

[0058] Fig.19B A second example of the encoding structure of the common field according to the third embodiment or the fourth embodiment is depicted.

[0059] Fig.19C Describes the basis Figure 3B A first example of the encoding structure of the common fields of the illustrated embodiment.

[0060] Fig.19D Describes the basis Figure 3B A second example of the encoding structure of the common fields of the illustrated embodiment.

[0061] Fig.19E Describes the basis Figure 3C A first example of the encoding structure of the common fields of the illustrated embodiment.

[0062] Fig.19F Describes the basis Figure 3C A second example of the encoding structure of the common fields of the illustrated embodiment.

[0063] Fig. 20A Shown according to Figure 3C An illustration of the reduction in user specific field overhead for the illustrated embodiment.

[0064] Fig. 20B Shown according to Figure 3C An illustration of the reduction of user specific field overhead in another example of the illustrated embodiment.

[0065] Fig. 20C Shown according to Figure 3C An illustration of the reduction of user specific field overhead in another example of the illustrated embodiment.

[0066] Fig.21 A flowchart showing processing of a received EHT MUPPDU at a STA according to the third embodiment or the fourth embodiment is shown.

[0067] Fig. 22 Depicted is a flow chart showing communication between a STA and an AP with a downlink user-specific PA according to a fifth embodiment.

[0068] Fig.23 An EHT-SIG-B field according to a fifth embodiment is depicted.

[0069] Fig.24A A first example of the encoding structure of the common field according to the fifth embodiment is depicted.

[0070] Fig. 24B A second example of the encoding structure of the common field according to the fifth embodiment is depicted.

[0071] Fig.25 A diagram showing a reduction in user specific field overhead according to a fifth embodiment is shown.

[0072] Fig.26 A flowchart illustrating processing of a received EHT MU PPDU at a STA according to a fifth embodiment is shown.

[0073] Fig. 27 A configuration of a communication device (eg, AP) according to various embodiments is shown.

[0074] Fig.28 A configuration of a communication device (eg, STA) according to various embodiments is shown.

[0075] Those skilled in the art will appreciate that the elements in the drawings are shown for simplicity and clarity and are not necessarily drawn to scale. For example, the size of some elements in the diagrams, block diagrams or flow charts may be exaggerated relative to other elements to help accurately understand the present embodiment. DETAILED DESCRIPTION

[0076] Some embodiments of the present disclosure will be described, by way of example only, with reference to the accompanying drawings. Like reference numerals and characters in the drawings indicate like elements or equivalents.

[0077] In the following paragraphs, certain exemplary embodiments are explained with reference to an access point (AP) and a station (STA) for uplink or downlink persistent assignment (PA), particularly in a multiple-input multiple-output (MIMO) wireless network.

[0078] 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. Based on the IEEE 802.11-2016 definition, a STA can be any device that contains a media access control (MAC) compliant with IEEE 802.11 and a physical layer (PHY) interface to the wireless medium (WM).

[0079] For example, in a wireless local area network (WLAN) environment, a STA can be a laptop, a desktop personal computer (PC), a personal digital assistant (PDA), an access point, or a Wi-Fi phone. 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.

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

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

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

[0083] In a MIMO wireless network, single-user communication and multi-user communication may be used for communication between communication devices such as an AP and a STA.

[0084] Figure 1A 1 is a schematic diagram of a single-user MIMO communication 100 between an AP 102 and a STA 104 in a MIMO wireless network. As shown, the MIMO wireless network may include one or more STAs (e.g., STA 104, STA 106, etc.). In the single-user MIMO communication 100, the AP 102 uses multiple antennas (e.g., Figure 1A The 4 antennas (shown) transmit multiple spatial streams, all of which are directed to a single communication device, namely, STA 104. For simplicity, the multiple spatial streams directed to STA 104 are shown as grouped data transmission arrows 108 directed to STA 104.

[0085] Single-user MIMO communication 100 may be configured for bidirectional transmission. Figure 1A As shown, in single-user MIMO communication 100, STA 104 may use multiple antennas (e.g., Figure 1A The 2 antennas (shown) transmit multiple spatial streams, all of which are directed toward the AP 102. For simplicity, the multiple spatial streams directed toward the AP 102 are shown as data transmission arrows 110 for packets directed toward the AP 102.

[0086] so, Figure 1A The single-user MIMO communication 100 described in the accompanying drawings can implement uplink single-user transmission and downlink single-user transmission in a MIMO wireless network.

[0087] Figure 1B A schematic diagram of downlink multi-user MIMO (MU-MIMO) communications between an AP 122 and a plurality of STAs 124, 126, 128 in a MIMO wireless network is depicted.

[0088] The MIMO wireless network may include one or more STAs (e.g., STA 124, STA 126, STA 128, etc.). In downlink MU-MIMO communication 120, AP 122 simultaneously transmits multiple streams to STAs 124, 126, 128 in the network using multiple antennas via spatial mapping or precoding techniques. For example, two spatial streams may be directed to STA 126, another spatial stream may be directed to STA 124, and yet another spatial stream may be directed to STA 128. For simplicity, the two spatial streams directed to STA 126 are shown as grouped data transmission arrows 132, the spatial stream directed to STA 124 is shown as data transmission arrows 130, and the spatial stream directed to STA 128 is shown as data transmission arrows 134.

[0089] Figure 1C A schematic diagram of uplink MU-MIMO communications 140 between an AP 142 and a plurality of STAs 144, 146, 148 in a MIMO wireless network is depicted.

[0090] The MIMO wireless network may include one or more STAs (e.g., STA 144, STA 146, STA 148, etc.). In uplink MU-MIMO communication 140, STAs 144, 146, 148 simultaneously transmit corresponding streams to AP 142 in the network using corresponding antennas via spatial mapping or precoding techniques. For example, two spatial streams may be directed from STA 146 to AP 142, another spatial stream may be directed from STA 144 to AP 142, and yet another spatial stream may be directed from STA 148 to AP 142. For simplicity, the two spatial streams directed from STA 146 to AP 142 are shown as grouped data transmission arrows 152, the spatial stream directed from STA 144 to AP 142 is shown as data transmission arrows 150, and the spatial stream directed from STA 148 to AP 142 is shown as data transmission arrows 154.

[0091] Due to the packet / PPDU (physical layer protocol data unit) based transmission and distributed MAC scheme in 802.11 WLAN, there is no time scheduling (e.g., TDMA (time division multiple access)-like periodic time slot allocation for data transmission) in 802.11 WLAN. Frequency and space resource scheduling is performed on a packet basis. In other words, resource allocation information is based on PPDU.

[0092] Figure 1DThe format of the PPDU 160 for downlink multi-user communication between an AP and multiple STAs in a HE WLAN is shown, for example, OFDMA (Orthogonal Frequency Division Multiple Access) transmission including MU-MIMO transmission in a single RU (Resource Unit) and full bandwidth MU-MIMO transmission. Such a PPDU 160 is referred to as a HE MU PPDU 160.

[0093] The HE MU PPDU 160 may include a non-high throughput short training field (L-STF), a non-high throughput long training field (L-LTF), a non-high throughput signal field (L-SIG), a repeated L-SIG field (RL-SIG), a HE signal A field (HE-SIG-A) field 162, a HE signal B field (HE-SIG-B) field 166, a HE short training field (HE-STF), a HE long training field (HE-LTF), a data field 170, and a packet extension (PE) field.

[0094] In the HE MU PPDU 160, the HE-SIG-B field 166 provides OFDMA and MU-MIMO resource allocation information to allow the STA to find the corresponding resources to be used in the data field 170, as indicated by arrow 168. The HE-SIG-A field 162 contains the necessary information for decoding the HE-SIG-B field 166, such as the MCS for the HE-SIG-B, the number of HE-SIG-B symbols, as indicated by arrow 164.

[0095] Figure 1E The HE-SIG-B field 166 is depicted in greater detail. The HE-SIG-B field 166 includes (or consists of) a common field 172 (if present), followed by a user-specific field 174, which are collectively referred to as the HE-SIG-B content channel.

[0096] The HE-SIG-B 166 contains an RU allocation subfield that indicates RU information for each allocation. The RU information includes the RU location in the frequency domain, an indication of the RU allocated to a non-MU-MIMO or MU-MIMO allocation, and the number of users in the MU-MIMO allocation. In the case of full-bandwidth MU-MIMO transmission, the common field 172 does not exist. In this case, the RU information (e.g., the number of users in the MU-MIMO allocation) is signaled in the HE-SIG-A field 162.

[0097] The user-specific field 174 includes (or is composed of) one or more user fields for (multiple) non-MU-MIMO assignments and / or (multiple) MU-MIMO assignments. The user field contains user information indicating a user-specific assignment (i.e., user-specific assignment information). Figure 1E In the example shown, the user-specific field 174 includes five user fields (user field 0, ..., user field 4), wherein user-specific allocation information for an allocation (allocation 0) is provided by user field 0, user-specific allocation information for a further allocation (allocation 1 with 3 MU-MIMO users) is provided by user field 1, user field 2, and user field 3, and user-specific allocation information for a further allocation (allocation 2) is provided by user field 4. Note that the MU-MIMO allocation (allocation 1) includes three user-specific allocations, indicated by user field 1, user field 2, and user field 3, respectively.

[0098] Figure 1F The format of the PPDU 180 used for uplink multi-user communication between an AP and multiple STAs in a HE WLAN is shown. This PPDU 180 is called a HE TB (trigger-based) PPDU 180.

[0099] The HE TB PPDU 180 may include L-STF, L-LTF, L-SIG, RL-SIG, HE-SIG-A field 182, HE-STF, HE-LTF, data field, and PE field.

[0100] The HE TB PPDU 180 is used for uplink multi-user transmission in response to a frame carrying trigger information. Instead of using the HE-SIG-B field, the information required for uplink multi-user transmission from one or more STAs is carried by the frame requesting the transmission. In a typical transmission of the HE TB PPDU 180, the HE-SIG-A related information is copied from the previous frame carrying the trigger information to the HE-SIG-A field 182 of the HE TB PPDU 180.

[0101] If the MIMO wireless network has a very high throughput, such as an EHT WLAN, the multi-user PPDU for downlink multi-user transmission may be referred to as an EHT MU PPDU 200. Figure 2A As shown; and the multi-user PPDU for uplink multi-user transmission can be called EHT TB PPDU, such as Figure 2B shown.

[0102] Figure 2AAn EHT MU PPDU 200 is depicted. The EHT MU PPDU 200 may include an L-STF, an L-LTF, an L-SIG, a format identification field (FIF) 201, an EHT signal A (EHT-SIG-A) field 202, an EHT signal B (EHT-SIG-B) field 206, an EHT-STF, an EHT-LTF, a data field 210, and a PE field. It is worth noting that if the IEEE 802.11 working group may use a new name instead of "EHT WLAN" for the next generation WLAN with extremely high throughput, the prefix "EHT" in the above fields may change accordingly. The FIF 201 is mainly used to identify the format of the EHT PPDU. The EHT-SIG-A field 202 contains the necessary information for decoding the EHT-SIG-B field 206, such as the MCS for the EHT-SIG-B, the number of symbols for the EHT-SIG-B, as shown by arrow 204. The EHT-SIG-B field 206 provides OFDMA and MU-MIMO resource allocation information to allow the STA to find the corresponding resources to be used in the data field 210, as shown by arrow 208. Figure 1D , the EHT-SIG-B field 206 includes (or consists of) a common field (if present) followed by a user-specific field, which are collectively referred to as the EHT-SIG-B content channel.

[0103] Due to the maximum number of spatial streams of 16, the maximum channel bandwidth (CBW) of 320 MHz and multi-band operation in the EHT WLAN, the number of allocations and / or the number of users supported in the EHT MU PPDU may increase significantly. Therefore, the EHT MU PPDU may have a much larger signaling overhead than the HE MU PPDU. Devices and methods according to various embodiments can advantageously reduce signaling overhead, especially when the CBW is greater than 20 MHz.

[0104] Figure 2B Shown is the format of the EHT TB PPDU 212. The EHT TB PPDU 212 may include L-STF, L-LTF, L-SIG, FIF, EHT-SIG-A field 214, EHT-STF, EHT-LTF, data field, and PE field.

[0105] The EHT TB PPDU 212 is used in the EHT WLAN for uplink multi-user transmission in response to a frame carrying trigger information. Instead of using the EHT-SIG-B field, the information required for uplink multi-user transmission from one or more STAs is carried by the frame requesting the transmission. In a typical transmission of the EHT TB PPDU 212, the EHT-SIG-A related information is copied from the previous frame carrying the trigger information to the EHT-SIG-A field 214 of the EHT TB PPDU 212.

[0106] Due to the maximum number of spatial streams of 16, the maximum CBW of 320 MHz and multi-band operation in the EHT WLAN, the number of allocations and / or the number of users supported in the EHT TB PPDU may increase significantly. Therefore, the frame for requesting EHT TB PPDU transmission may have a larger signaling overhead than the frame for requesting HE TB PPDU transmission. The devices and methods according to various embodiments can advantageously reduce the signaling overhead, especially when the CBW is greater than 20 MHz.

[0107] According to various embodiments, in addition to dynamic allocation, EHT WLAN also supports user-specific persistent allocation (PA). User-specific PA can be transmitted cyclically within a period of time while reducing control signaling requirements. User-specific PA is particularly suitable for traffic such as VoIP (Voice over Internet Protocol).

[0108] Figure 3A A schematic partial cross-sectional view of a communication device 300 according to various embodiments is shown. According to various embodiments, the communication device 300 may be implemented as an AP or a STA.

[0109] like Figure 3A As shown, the communication device 300 may include a circuit 314, at least one radio transmitter 302, at least one radio receiver 304, and at least one antenna 312 (for simplicity, for the purpose of illustration, in Figure 3AOnly one antenna is depicted in FIG. 3 ). The circuitry 314 may include at least one controller 306 for software and hardware assistance in performing the tasks that the at least one controller 306 is designed to perform, including controlling communications with one or more other communication devices in a MIMO wireless network. The circuitry 314 may also include at least one transmit signal generator 308 and at least one receive signal processor 310. At least one controller 306 may control at least one transmit signal generator 308 to generate a PPDU to be transmitted to one or more other communication devices through at least one radio transmitter 302 (e.g., if the communication device 300 is an AP, an EHT MU PPDU or a PPDU including a PA announcement frame, an EHT basic trigger frame, a PA trigger frame, a frame carrying a PA control subfield, or a multi-STA BlockAck frame, and, for example, if the communication device 300 is a STA, an EHT TB PPDU or a PPDU including a BlockAck frame), and control at least one receive signal processor 310 to process a PPDU received from one or more other communication devices through at least one radio receiver 304 under the control of the at least one controller 306 (e.g., if the communication device 300 is an AP, an EHT TB PPDU or a PPDU including a BlockAck frame, and, for example, if the communication device 300 is a STA, an EHT MU PPDU or a PPDU including a PA announcement frame, an EHT basic trigger frame, a PA trigger frame, a frame carrying a PA control subfield, or a multi-STA BlockAck frame). like Figure 3A As shown, at least one transmit signal generator 308 and at least one receive signal processor 310 can be independent modules of the communication device 300, which communicate with at least one controller 306 to implement the above functions. Alternatively, at least one transmit signal generator 308 and at least one receive signal processor 310 can be included in at least one controller 306. For those skilled in the art, the arrangement of these functional modules is flexible and can vary depending on actual needs and / or requirements. Data processing, storage and other related control devices can be arranged on appropriate circuit boards and / or in chipsets. In various embodiments, at least one radio transmitter 302, at least one radio receiver 304 and at least one antenna 312 can be controlled by at least one controller 306.

[0110] The communication device 300 provides functions required for a downlink user-specific PA. For example, the communication device 300 may be an AP, and the circuit 314 (e.g., at least one transmit signal generator 308 of the circuit 314) may generate a transmit signal including a common field (e.g., in the EHT-SIG-B field of the EHT MU PPDU), a user-specific field (e.g., in the EHT-SIG-B field of the EHT MU PPDU), and a data field (e.g., in the EHT MU PPDU), the common field including RU information of one or more user-specific allocations in the data field, the user-specific field including one or more user information, each user information indicating a user-specific allocation among the one or more user-specific allocations in the data field. The radio transmitter 302 may transmit the generated transmit signal. The user-specific field may not include (free from) user information of a downlink user-specific PA including initial or cyclic transmission in one or more user-specific allocations. In other words, user information of a downlink user-specific PA including initial or cyclic transmission among one or more user-specific allocations may not be included in the user-specific field. For example, only user information of a downlink non-user-specific PA may be included in the user-specific field. This can advantageously reduce communication overhead.

[0111] The communication device 300 may be a STA, and the radio receiver 304 may receive a transmission signal (e.g., an EHT MU PPDU) including a common field, a user-specific field, and a data field, the common field including RU information of one or more user-specific allocations in the data field, and the user-specific field including one or more user information, each user information indicating a user-specific allocation among the one or more user-specific allocations in the data field. The circuit 314 may process the received transmission signal. The user-specific field may not include user information of a downlink user-specific PA including initial or cyclic transmission among the one or more user-specific allocations.

[0112] The communication device 300 provides the functions required for the uplink user-specific PA. For example, the communication device 300 may be an AP, and the circuit 314 (e.g., at least one transmit signal generator 308 of the circuit 314) may generate a transmit signal including a frame for requesting EHT TB PPDU transmission from one or more STAs, the frame including one or more user-specific resource allocation information, each user-specific resource allocation information indicating a user-specific allocation in the data field of the requested EHT TB PPDU. The radio transmitter 302 may transmit the generated transmit signal. The frame may not include user-specific resource allocation information for the uplink user-specific PA including initial or cyclic transmission. In other words, user-specific resource allocation information for the uplink user-specific PA including initial or cyclic transmission may not be included in the frame. For example, only user-specific resource allocation information for uplink non-user-specific PAs may be included in the frame. This can advantageously reduce communication overhead.

[0113] For example, the communication device 300 may be a STA, and the radio receiver 304 may receive a transmission signal (e.g., a frame for requesting EHT TB PPDU transmission from one or more STAs). The transmission signal includes one or more user-specific resource allocation information, each user-specific resource allocation information indicating a user-specific allocation in a data field of the requested EHT TB PPDU. The circuit 314 may process the received transmission signal. The frame may not include user-specific resource allocation information for an uplink user-specific PA including initial or cyclic transmission. In other words, user-specific resource allocation information for an uplink user-specific PA including initial or cyclic transmission may not be included in the frame. For example, only user-specific resource allocation information for an uplink non-user-specific PA may be included in the frame. This may advantageously reduce communication overhead.

[0114] For example, the communication device 300 may be an AP, and the circuit 314 (e.g., at least one transmit signal generator 308 of the circuit 314) may generate a first transmit signal including user information for multiple users of a downlink MU-MIMO assignment, each user information indicating a user-specific assignment, and also generate a second transmit signal including a common field, a user-specific field, and a data field, the data field containing a transmission of the downlink MU-MIMO assignment. The radio transmitter 302 may transmit the first transmit signal and the second transmit signal, wherein the user-specific assignment of the downlink MU-MIMO assignment is determined to be persistent or non-persistent.

[0115] Figure 3BA flow chart 330 illustrating a communication method according to various embodiments is shown. At 332, a transmit signal may be generated. The transmit signal may include a common field, a user-specific signal field, and a data field, the common field including RU information for each of one or more allocations in the data field, and the user-specific field including one or more user information, each user information indicating a user-specific allocation among the one or more allocations in the data field. At 334, the generated transmit signal may be transmitted. The user-specific field may not include at least one user information of a persistent allocation including cyclic transmission among the one or more allocations.

[0116] According to various embodiments, a communication method may include: receiving a transmission signal including a common field, a user-specific field and a data field, the common field including RU information for each of one or more allocations in the data field, and the user-specific field including one or more user information, each user information indicating a user-specific allocation among the one or more allocations in the data field; wherein the user-specific field may not include at least one user information of a persistent allocation including cyclic transmission among the one or more allocations.

[0117] Figure 3C A flow chart 350 illustrating a communication method according to various embodiments is shown. In step 352, a transmit signal may be generated. The transmit signal may include at least one signal field content channel and a data field, each of the at least one signal field content channel including an RU allocation subfield including N fields and a cyclic transmission bitmap subfield including N bitmaps of N=1, 2, 4, or 8, wherein each of the N fields of the RU allocation subfield indicates RU information for one or more allocations within a corresponding tone range in the data field, and the nth (n=1, 2, ..., N) bitmap of the cyclic transmission bitmap subfield indicates whether each of the one or more allocations indicated by the nth field of the RU allocation subfield contains cyclic transmission. In step 354, the generated transmit signal is transmitted.

[0118] Figure 3D A flow chart 360 illustrating a communication method according to various embodiments is shown. At step 362, a frame including identification information identifying an uplink PA may be generated. At step 364, the generated frame is transmitted.

[0119] Figure 3EA flow chart 390 illustrating a communication method according to various embodiments is shown. In step 392, a first transmit signal is generated including user information for a plurality of users of a downlink MU-MIMO assignment, each user information indicating a user-specific assignment. In step 394, a second transmit signal is generated including a common field, a user-specific field, and a data field, the data field containing a transmission of the downlink MU-MIMO assignment. In step 396, the first transmit signal and the second transmit signal are transmitted, wherein the user-specific assignment of the downlink MU-MIMO assignment is determined to be persistent or not.

[0120] Figure 4A A flow chart 400 is depicted showing communication between multiple STAs (404, 406) and an AP 402 through a TXOP (transmission opportunity) according to various embodiments with an uplink user-specific PA. Box 408 shows a contention-based channel access process, such as an enhanced distributed channel access (EDCA) process, and a short interframe space (SIFS) 410 is shown. The AP 402 may generate a first frame 412 including complete information of an uplink user-specific PA for requesting an initial transmission of the uplink user-specific PA for STA 406. The complete PA information may include identification information and user-specific resource allocation information. In an embodiment, the identification information may be a PA identifier (PAID) of the uplink user-specific PA. In another embodiment, the identification information may be RU allocation information and user identification information of the uplink user-specific PA. In yet another embodiment, the identification information may be RU allocation information and spatial stream (SS) allocation information of the uplink user-specific PA. The first frame 412 may also include complete information of the uplink user-specific PA for requesting initial transmission of the uplink user-specific PA for the STA 404. The AP 402 may transmit the generated first frame 412 to the STAs 404 and 406.

[0121] At 414, STA 406 may receive the first frame 412 and store the complete information of the uplink user-specific PA (i.e., the identification information and user-specific resource allocation information of the uplink user-specific PA intended for STA 406), and accordingly send an EHT TB PPDU 418 to AP 402. STA 404 may also receive and store the complete information about the uplink user-specific PA (i.e., the identification information and user-specific resource allocation information of the uplink user-specific PA intended for STA 404), and accordingly send an EHT TB PPDU 416 to AP 402. EHT TB PPDUs 416 and 418 may be similar to those in FIG. Figure 2BThe format of the EHT TB PPDU 212 shown is the same. The AP 402 may receive the EHT TB PPDUs 416 and 418, and then send a multi-STA BlockAck frame 420 to the STAs 404 and 406. Thereafter, the AP 402 may request cyclic transmission of the uplink user-specific PA for the STA 404 and cyclic transmission of the uplink user-specific PA for the STA 406 by sending a second frame 422. The second frame 422 may carry identification information about the uplink user-specific PA for the STA 404 and identification information about the uplink user-specific PA for the STA 406. In various embodiments, the identification information of the uplink user-specific PA is included in the frame body of the second frame 422 to request cyclic transmission of the uplink user-specific PA, and the second frame 422 does not contain user-specific resource allocation information of the uplink user-specific PA. In various embodiments, identification information is included in a MAC header of the second frame 422 to request cyclic transmission of the uplink user-specific PA, and the second frame 422 does not contain user-specific resource allocation information of the uplink user-specific PA.

[0122] At 424, STA 406 may prepare an EHT TB PPDU 428 based on the stored user-specific resource allocation information for the uplink user-specific PA and send the EHT TB PPDU 428 to AP 402. The EHT TB PPDU 428 contains a cyclic transmission of the uplink user-specific PA for STA 406. STA 404 may also prepare an EHT TB PPDU 426 based on the stored user-specific resource allocation information for the uplink user-specific PA and send the EHT TB PPDU 426 to AP 402. The EHT TB PPDU 426 contains a cyclic transmission of the uplink user-specific PA for STA 404. The EHT TB PPDUs 426 and 428 may be identical to the EHT TB PPDUs 426 and 428. Figure 2B The format of the EHT TB PPDU 212 is the same as shown. AP 402 may receive EHT TB PPDUs 426 and 428 and then send a multi-STA BlockAck frame 430 to STAs 404 and 406. Figure 4A As shown, the cyclic transmission of the uplink user-specific PA may occur within the same TXOP as the initial transmission of the uplink user-specific PA. Figure 4BAs shown, the cyclic transmission may also occur in a TXOP different from the initial transmission of the uplink user-specific PA. That is, in an example, the uplink user-specific PA may exist until the end of the current TXOP. In another example, the uplink user-specific PA may exist for a predetermined number of service periods or beacon intervals. Figure 4B In the embodiment, the second frame 422 is sent by the AP 402 in a different TXOP than the first frame 412, and thus the cyclic transmission requested by the second frame 422 (e.g., the uplink user-specific PA transmission contained in the EHT TBPPDUs 426 and 428) also occurs in a different TXOP than the first frame 412. It can be understood that the transmission of the second frame 422 occurs within the time duration of the uplink user-specific PA existence for the STAs 404 and 406.

[0123] Figure 5A and Figure 5B The format of an EHT basic trigger frame 500 for uplink multi-user communication between an AP and multiple STAs in an EHT WLAN according to the first embodiment is shown. The EHT basic trigger frame 500 is a variant of the existing trigger frame and can be used as Figure 4A and Figure 4B The first frame 412 in the EHT basic trigger frame 500. The EHT basic trigger frame 500 uses the PAID of the uplink user-specific PA to identify the uplink user-specific PA. The EHT basic trigger frame 500 may include a frame control field, a duration field, an RA (receiving STA address) field, a TA (transmitting STA address) field, a common information field 502, one or more user information fields (such as a user information field 504), a padding field, and an FCS (frame check sequence) field. The frame control field, the duration field, the RA field, and the TA field may be grouped in the MAC header of the EHT basic trigger frame 500. The common information field 502, the one or more user information fields 504, and the padding field may be grouped in the frame body of the EHT basic trigger frame 500.

[0124] Figure 5AThe common information field 502 is also described in more detail. The common information field 502 contains common parameters for all STAs participating in the EHT TB PPDU transmission requested by the EHT basic trigger frame 500. The common information field 502 includes (or is composed of) a trigger type field 506, a UL (uplink) length field, a more TF (trigger frame) field, a CS (carrier sense) required field, a UL BW (bandwidth) field, a GI (guard interval) and LTF type field, a MU-MIMO LTF mode field, a HE-LTF symbol number and a midamble periodicity field, a UL STBC (space-time block coding) field, a LDPC (low-density parity check) additional symbol segment field, an AP TX (transmit) power field, a Pre-FEC (forward error correction) filling factor field, a PE inconsistency field, a UL spatial reuse (Spatial Reuse) field, a Doppler field, a UL HE-SIG-A2 reserved field, and a trigger-related common information field 508. The trigger-related public information field 508 may include (or be composed of) a PAID number field and a PAID tuple field. The PAID number field indicates the number of PAID subfields contained in the PAID tuple field. Alternatively, the trigger-related public information field 508 may include a starting PAID field, a PAID bitmap size field, and a PAID bitmap field. The PAID bitmap size field indicates the bit width of the PAID bitmap field. The starting PAID field contains the starting PAID of the PAID bitmap field. The PAID bitmap field indicates (multiple) PAIDs together with the starting PAID field. The EHT basic trigger frame 500 uses its PAID contained in the trigger-related public information field 508 to request cyclic transmission of an uplink user-specific PA. The trigger type field 506 may be assigned an arbitrary value to indicate that the trigger frame 500 is an EHT basic trigger frame. In various embodiments below, the trigger type field 506 is assigned an arbitrary value of 8 to indicate that the trigger frame 500 is an EHT basic trigger frame.

[0125] Figure 5BThe user information field 504 is described in more detail. The user information field 504 includes an AID12 field, an RU allocation field, a UL FEC codec type field, a UL MCS (Modulation and Coding Scheme) field, a UL DCM (Dual Carrier Modulation) field, an SS allocation field, a UL target RSSI (Received Signal Strength Indicator) field, and a trigger-related user information field 512. The trigger-related user information field 512 may include (or consist of) a 1-bit PA flag subfield, a PAID subfield 516, an MPDU MU interval factor subfield, a TID (Traffic Identifier) ​​aggregation restriction subfield, and a preferred AC (Access Category) subfield. Alternatively, the trigger-related user information field 512 may include (or consist of) a PAID subfield 516, an MPDU MU interval factor subfield, a TID aggregation restriction subfield, and a preferred AC subfield. The RU allocation field, the UL FEC codec type field, the UL MCS field, the UL DCM field, the SS allocation field, the UL target RSSI field, the MPDU MU spacing factor subfield, the TID aggregation restriction subfield, and the preferred AC subfield constitute the user specific resource allocation information 514 of the user information field 504. The user specific resource allocation information 514 may be obtained and stored by the STA for initial or recurring uplink user specific PA transmission, wherein an EHT TB PPDU based on the stored user specific resource allocation information 514 is sent to the AP requesting uplink user specific PA transmission.

[0126] As described above, the user information field 504 may include a PA flag subfield and a PAID subfield 516. The PA flag subfield (e.g., 1 bit) indicates whether the user information field 504 corresponds to an uplink user-specific PA, and the PAID subfield 516 (e.g., 7 bits) indicates the PAID of the uplink user-specific PA. The user information field with the PA flag subfield set to 0 indicates that the user information field does not correspond to an uplink user-specific PA. In this case, the PAID subfield 516 is retained. On the other hand, the user information field with the PA flag subfield set to 1 indicates that the user information field corresponds to an uplink user-specific PA. In this case, the PAID subfield 516 indicates the PAID of the uplink user-specific PA. In addition, the PA flag subfield of the user information field for random access should be set to 0. That is, uplink user-specific PAs for random access are not allowed.

[0127] Alternatively, the user information field 504 may include a PAID subfield 516 (e.g., 8 bits) indicating whether the user information field 504 corresponds to an uplink specific PA, or indicating a PAID of an uplink specific PA corresponding to the user information field. A user information field having a PAID subfield 516 set to 0 indicates that the user information field does not correspond to an uplink user specific PA. A user information field having a PAID subfield 516 set to any other value (e.g., 1 to 255) indicates a PAID of an uplink user specific PA. In addition, the PAID subfield of the user information field for random access should be set to 0. That is, uplink user specific PAs for random access are not allowed.

[0128] In the EHT basic trigger frame, no more than one user information field not used for random access will be addressed to a single STA. The (multiple) user information fields used for random access should be located after the (multiple) user information fields not used for random access. STAs with uplink user-specific PAs indicated in the common information field should not be addressed by user information fields not used for random access. In addition, more than one uplink user-specific PA assigned to a single STA should not be indicated in the common information field. Advantageously, this reduces the complexity of processing the received EHT basic trigger frame at the STA.

[0129] The first frame 412 may be in the format of an EHT basic trigger frame 500. For example, at 414, the STA 406 may receive the first frame 412 in the form of an EHT basic trigger frame 500. The STA 406 may store identification information and user-specific resource allocation information for an uplink user-specific PA of the STA 406. The identification information (e.g., PAID) may be retrieved from the PAID subfield 516 of the user information field, whose AID12 subfield value matches the AID (association identifier) ​​of the STA 406. The user-specific resource allocation information may also be retrieved from the user information field. The STA 406 may then send an EHT TB PPDU 418 to the AP 402 accordingly, wherein the EHT TB PPDU 418 is based on the stored user-specific resource allocation information.

[0130] Similarly, STA 404 may also receive a first frame 412 in the form of an EHT basic trigger frame 500. STA 404 may store identification information and user-specific resource allocation information of an uplink user-specific PA intended for STA 404. Identification information (e.g., PAID) may be retrieved from the PAID subfield of the user information field, whose AID12 subfield value matches the AID of STA 404. User-specific resource allocation information may also be retrieved from the user information field. STA 404 may then send an EHT TB PPDU 416 to AP 402 accordingly, wherein the EHT TB PPDU 416 is based on the stored user-specific resource allocation information.

[0131] The second frame 422 may also be in the format of the EHT basic trigger frame 500. For example, the STA 406 may receive the second frame 422 in the format of the EHT basic trigger frame 500. The STA 406 may obtain the common parameters from the common information field 502 of the EHT basic trigger frame 500 and determine whether the PAID stored by the STA 406 at 414 matches any PAID subfield value in the trigger-related common information field 508 of the common information field 502. If so, at 424, the STA 406 may prepare an EHT TB PPDU 428 based on the user-specific resource allocation information stored by the STA 406 at 414 and send the prepared EHT TB PPDU 428 to the AP 402.

[0132] Likewise, the STA 404 may receive a second frame 422 in the format of the EHT basic trigger frame 500. The STA 404 may obtain the common parameters from the common information field 502 of the EHT basic trigger frame 500 and determine whether the PAID stored by the STA 404 at 414 matches any PAID subfield value in the trigger-related common information field 508 of the common information field 502. If so, the STA 404 may prepare an EHT TB PPDU 426 based on the user-specific resource allocation information stored by the STA 404 at 414 and send the prepared EHT TB PPDU 426 to the AP 402.

[0133] The second frame 422 may also be in the form of Figure 5CThe form of the PA trigger frame 520 according to the first embodiment is shown. The PA trigger frame 520 may include (or be composed of) a frame control field, a duration field, an RA field, a TA field, a common information field, a padding field, and an FCS field. The common information field may include (or be composed of) a trigger type field, a more TF field, a CS required field, and a trigger-related common information field 522. The trigger-related common information field 522 may include (or be composed of) a PAID number field and a PAID tuple field. The PAID number field indicates the number of PAID subfields contained in the PAID tuple field. Alternatively, the trigger-related common information field 522 may include a start PAID field, a PAID bitmap size field, and a PAID bitmap field. The PAID bitmap size field indicates the bit width of the PAID bitmap field. The start PAID field contains the start PAID of the PAID bitmap field. The PAID bitmap field, together with the start PAID field, indicates the (multiple) PAIDs of the (multiple) uplink user-specific PAs. The PA trigger frame 520 requests cyclic transmission of the uplink user-specific PA using its PAID contained in the trigger-related common information field 522. In the PA trigger frame, more than one uplink user-specific PA assigned to a single STA should not be indicated in the common information field. Advantageously, this reduces the complexity of processing the received PA trigger frame at the STA.

[0134] The PA trigger frame 520 is only used to request cyclic transmission of one or more uplink user-specific PAs, such as EHTTB PPDUs 426 and 428. Only some common parameters (e.g., More TF subfield and CS Required subfield) are present in the common information field of the PA trigger frame 520, because other common parameters may not change before one or more uplink user-specific PAs expire and may be obtained from the first frame 412. In addition, user-specific resource allocation information required by one or more uplink user-specific PAs is not included in the PA trigger frame, because it may be obtained from the first frame 412. Advantageously, this reduces the channel overhead of the cyclic transmission of one or more uplink user-specific PAs.

[0135] The second frame 422 may also be in the form of Figure 5DThe form of a data or management frame 530 carrying a PA control subfield according to the first embodiment is shown. The data or management frame 530 may include (or consist of) a frame control field, a duration / ID field, four address fields, a sequence control field, a QoS (Quality of Service) field, an HT control field, a frame body field, and an FCS field. The HT control field may be a 32-bit HE variant HT control field, including (or consisting of) a VHT field (set to 1), an HE field (set to 1), a control ID field (set to a determined value, for example, 7, to indicate that the HT control field of the data or management frame 530 contains a PA control subfield) and a control information field 532. The 26-bit control information field may include (or consist of) an 8-bit PAID subfield and some common parameters 534, such as a 10-bit UL length subfield, a 5-bit DL TX power subfield, and a 3-bit HE-LTF symbol number subfield. It will be appreciated that other common parameters may be predetermined or implicitly signaled. The data or management frame 530 requests the cyclic transmission of the uplink user-specific PA using its PAID contained in the control information field 532. Similar to the PA trigger frame 520, the user-specific resource allocation information required by the uplink user-specific PA is not included in the data or management frame 530, as it can be obtained from the first frame 412. Advantageously, this reduces the channel overhead of the cyclic transmission of the uplink user-specific PA.

[0136] As described above, for the first embodiment, channel overhead can be further reduced. In the first frame, two or more user-specific PAs allocated by MU-MIMO may include the same PAID, which can be indicated in the second frame to request cyclic transmission from two or more STAs participating in the MU-MIMO allocation. In the example, the first frame can be used to assign the same PAID, the same RU, and the corresponding spatial stream to two or more user-specific PAs allocated by MU-MIMO. In another example, more than one first frame can be used to assign the same PAID, the same RU, and the corresponding spatial stream to two or more user-specific PAs allocated by MU-MIMO. Alternatively, in the first frame, the same PAID can be assigned to a group of user-specific PAs, which can be indicated in the second frame to request cyclic transmission of each user-specific PA in the group of user-specific PAs. However, assigning the same PAID to two or more user-specific PAs may reduce scheduling flexibility because the second frame indicating the same PAID will request cyclic transmission for all user-specific PAs with the same PAID.

[0137] In the first embodiment as described above, after the first frame requesting the initial transmission of the uplink user-specific PA is sent, the uplink user-specific PA may exist for a period of time. In an example, the uplink user-specific PA may exist until the end of the current TXOP. In another example, the uplink user-specific PA may exist for a predetermined number of service periods or beacon intervals. In yet another example, the common information field in the first frame may include signaling to indicate the time period during which the uplink user-specific AP whose initial transmission is requested by the first frame exists after the first frame is sent. For such an example, the uplink user-specific PA whose initial transmission is requested by the first frame has the same expiration time. Alternatively, the user information field corresponding to the uplink user-specific PA in the first frame may include signaling to indicate the time period during which the uplink user-specific PA exists after the first frame is sent. In an alternative example, the uplink user-specific PA whose initial transmission is requested by the first frame may have different expiration times.

[0138] In the first embodiment as described above, the AP may send a first frame to update the user-specific resource allocation information of the uplink user-specific PA before the uplink user-specific PA expires. If the user-specific resource allocation information of the uplink user-specific PA is updated before the uplink user-specific PA expires, and the expected STA fails to receive the update information, the information of the uplink user-specific PA will not match between the AP and the expected STA. If no EHT TB PPDU is received as a response to the first frame sent, the AP may be able to identify this mismatch. When the STA receives the first frame, the first frame includes complete information about the uplink user-specific PA for which the STA is one of the expected STAs, and the STA should start or reset the timer of the uplink user-specific PA and store or update the information about the uplink user-specific PA. Similarly, the STA can also store or update public parameters in the public information field through this process. Advantageously, this enables the AP to perform error recovery from information mismatch.

[0139] In the above example, the RU allocation is addressed to one or more STAs. If addressed to a single STA, the RU allocation is a non-MU-MIMO allocation, and if addressed to a STA group, the RU allocation is a MU-MIMO allocation. The RU allocation (i.e., non-MU-MIMO allocation or MU-MIMO allocation) includes one or more user-specific allocations. A non-MU-MIMO allocation includes a single user-specific allocation. A MU-MIMO allocation includes two or more user-specific allocations.

[0140] As described above, individual user-specific allocations for MU-MIMO allocations may be persistent or non-persistent. Individual user-specific PAs for MU-MIMO allocations may have different expiration times and may be independently renewed. Advantageously, user-specific PAs increase scheduling flexibility compared to RU-based PAs, where all user-specific allocations for MU-MIMO allocations are either persistent or non-persistent.

[0141] exist Figure 5E In the example shown, the MU-MIMO allocation includes three user-specific allocations 574 (user-specific allocation 1, ..., user-specific allocation 3), where user-specific allocation 1 is a user-specific PA with PAID=2, user-specific allocation 2 is a user-specific PA with PAID=5, and user-specific allocation 3 is not a user-specific PA.

[0142] Fig. 6AA flowchart 600 is shown showing the processing of a received EHT basic trigger frame at a STA according to a first embodiment. Processing may start at 602. At 604, common parameters are obtained from the common information field 502. At 606, it is determined whether the stored (multiple) PAIDs match any PAID subfield value in the common information field 502. If the stored (multiple) PAIDs match any PAID subfield value in the common information field 502, the processing may proceed to step 608. If the stored (multiple) PAIDs do not match any PAID subfield value in the common information field 502, the processing may proceed to step 614. At 608, it is determined whether the timer of the uplink user-specific PA with the matching PAID is running. If the timer of the uplink user-specific PA is running, the processing may proceed to step 610. Otherwise, the processing may end at step 636. At 610, user-specific resource allocation information stored by the STA is retrieved. At 614, the number of user information fields is calculated. At 616, the user information field counter is initialized to zero. At 620, it is determined whether the AID of the STA matches the AID12 subfield value of the user information field in the EHT basic trigger frame 500. If the AID of the STA matches the AID12 subfield value, the process may proceed to step 622. If the AID of the STA does not match the AID12 subfield value, the process may proceed to step 628. At 622, it is determined whether the user information field corresponds to an uplink user-specific PA by checking the PA flag subfield or the PAID subfield. If the user information field does not correspond to an uplink user-specific PA, the process may proceed to step 626. If the user information field corresponds to an uplink user-specific PA, the process may proceed to 624. At 626, the user-specific resource allocation information 514 is obtained from the user information field, whose AID12 subfield value matches the AID of the STA, for preparing the EHT TBPPDU. At 624, the PAID 516 and the user-specific resource allocation information 514 are obtained and stored by the STA. At 628, it is determined whether the AID12 subfield value of the user information field indicates a user information field for which a random access (RA) is eligible. If so, the process may proceed to step 630. Otherwise, the process may proceed to 632. At 630, a UORA (ULOFDMA-based random access) procedure is performed. At 632, a user information field counter is increased by 1. At 634, it is determined whether the user information field counter is equal to the number of user information fields in the EHT basic trigger frame 500. If the user information field counter is not equal to the number of user information fields in the EHT basic trigger frame 500, the process may return to step 620 again. If the user information field counter is equal to the number of user information fields in the EHT basic trigger frame 500, the process may end at 636.It can be appreciated that steps 620, 628, 632, and 634 form a loop for the STA to cycle through and read all user information fields present in the EHT basic trigger frame 500. At 612, based on the common parameters (e.g., the common parameters from the common information field 502) and the user-specific resource allocation information (e.g., if the processing is from step 610 or 624, the user-specific resource allocation information stored by the STA, or if the processing is from step 626, the user-specific resource allocation information 514 obtained from the user information field, whose AID12 subfield value matches the STA's AID), prepare the EHT TB PPDU. At 636, the process ends.

[0143] Figure 6B A flowchart 640 is shown illustrating processing of a received PA trigger frame 520 at a STA according to a first embodiment. Processing may start at step 642. At 644, some common parameters are obtained from the common information field of the PA trigger frame 520. At 646, it is determined whether the stored PAID(s) match any PAID subfield value in the trigger-related common information field 522 of the PA trigger frame 520. If the stored PAID(s) match the PAID subfield value contained in the trigger-related common information field 522 of the PA trigger frame 520, the processing may proceed to step 648. If the stored PAID(s) do not match any PAID subfield value, the processing may end at step 654. At 648, it is determined whether the timer of the uplink user-specific PA with the matching PAID is running. If it is determined that the timer is running, the processing may proceed to step 650. If it is determined that the timer is not running, the processing may end at step 654. At 650, user-specific resource allocation information and other common parameters stored by the STA are retrieved. At 652, an EHT TB PPDU is prepared based on the common parameters and the user-specific resource allocation information.

[0144] Figure 6CA flow chart 660 is shown illustrating processing of a received data or management frame 530 carrying a PA control subfield at a STA that is an intended recipient of the frame 530 according to a first embodiment. Processing may begin at step 662. At 664, common parameters 534 are obtained from the PA control subfield of the data or management frame 530. At 666, it is determined whether a timer of an uplink user-specific PA having a PAID indicated in the PA control subfield is running. If it is determined that the timer is running, processing may proceed to step 668. If it is determined that the timer is not running, processing may end at step 672. At 668, user-specific resource allocation information stored by the STA is retrieved. At 670, an EHT TB PPDU is prepared based on the common parameters 534 obtained from the PA control subfield of the data or management frame 530 and the retrieved user-specific resource allocation information.

[0145] Fig. 7A and Figure 7B The format of an EHT basic trigger frame 700 for uplink multi-user communication between an AP and multiple STAs in an EHT WLAN according to the second embodiment is shown. The EHT basic trigger frame 700 is a variant of the existing trigger frame and can be used as Figure 4A and Figure 4B The first frame 412 in the EHT basic trigger frame 500. Unlike the EHT basic trigger frame 500 that uses the PAID of the uplink user-specific PA to identify the uplink user-specific PA, the EHT basic trigger frame 700 uses the RU allocation information of the uplink user-specific PA as part of the identification information to identify the uplink user-specific PA. In one example, the RU allocation information of the uplink user-specific PA, together with the user identification information of the STA addressed by the uplink user-specific PA (e.g., the AID of the user), is used to identify the uplink user-specific PA. In another example, the RU allocation information of the uplink user-specific PA, together with the SS allocation information of the uplink user-specific PA (e.g., the starting spatial stream), is used to identify the uplink user-specific PA. The RU allocation information includes the RU position in the frequency domain. The EHT basic trigger frame 700 may include a frame control field, a duration field, an RA field, a TA field, a common information field 702, one or more user information fields (such as a user information field 704), a padding field, and an FCS field. The frame control field, the duration field, the RA field, and the TA field may be grouped in a MAC header of the EHT basic trigger frame 700. The common information field 702, the one or more user information fields 704, and the padding field may be grouped in a frame body of the EHT basic trigger frame 700.

[0146] Fig. 7AThe common information field 702 is also described in more detail. The common information field 702 contains common parameters for all STAs participating in the EHT TB PPDU transmission requested by the EHT basic trigger frame 700. The common information field 702 includes (or is composed of) a trigger type field 706, a UL length field, a more TF field, a CS required field, a UL BW field, a GI and LTF type field, a MU-MIMO LTF mode field, a HE-LTF symbol number and a midamble period field, a UL STBC field, an LDPC additional symbol segment field, an AP TX power field, a Pre-FEC filling factor field, a PE inconsistency field, a UL spatial multiplexing field, a Doppler field, a UL HE-SIG-A2 reserved field, and a trigger-related common information field 708. Unlike the trigger-related common information field 508 of the EHT basic trigger frame 500, the trigger-related common information field 708 of the EHT basic trigger frame 700 may include (or be composed of) a RU allocation number field and a RU allocation / AID12 tuple field. The RU allocation number field indicates the number of RU allocation / AID12 subfields in the RU allocation / AID12 tuple field. Then, the EHT basic trigger frame 700 can use the RU allocation information and user identification information of the uplink user-specific PA indicated in the trigger-related public information field 708 to request the cyclic transmission of the uplink user-specific PA. Alternatively, the trigger-related public information field 708 of the EHT basic trigger frame 700 may include (or be composed of) the RU allocation number field and the RU allocation / SS allocation tuple field. The RU allocation number field indicates the number of RU allocation / SS allocation subfields in the RU allocation / SS allocation tuple field. Then, the EHT basic trigger frame 700 can use the RU allocation information and SS allocation information of the uplink user-specific PA indicated in the trigger-related public information field 708 to request the cyclic transmission of the uplink user-specific PA. The trigger type field 706 can be assigned with an arbitrary value to indicate that the trigger frame 700 is an EHT basic trigger frame. In various embodiments below, the trigger type field 706 is assigned with an arbitrary value of 8 to indicate that the trigger frame 700 is an EHT basic trigger frame.

[0147] Figure 7BThe user information field 704 is described in more detail. The user information field 704 includes an AID12 field, an RU allocation field 716, a UL FEC codec type field, a UL MCS field, a UL DCM field, an SS allocation field, a UL target RSSI field, and a trigger-related user information field 712. Unlike the EHT basic trigger frame 500, the trigger-related user information field 712 may include (or be composed of) a 1-bit PA flag subfield 516, an MPDU MU interval factor subfield, a TID aggregation restriction subfield, and a preferred AC subfield. The RU allocation field 716, the UL FEC codec type field, the UL MCS field, the UL DCM field, the SS allocation field, the UL target RSSI field, the MPDU MU interval factor subfield, the TID aggregation restriction subfield, and the preferred AC subfield constitute the user-specific resource allocation information 714 of the user information field 704. The user-specific resource allocation information 714 may be obtained by the STA and stored for initial or recurring uplink user-specific PA allocation transmission, wherein an EHT TB PPDU based on the stored user-specific resource allocation information 714 is sent to the AP requesting uplink user-specific PA transmission. Unlike the trigger-related user information field 512 of the EHT basic trigger frame 500, the trigger-related user information field 712 of the EHT basic trigger frame 700 does not include a PAID subfield.

[0148] As described above, the user information field 704 may include a PA flag subfield. The PA flag subfield (e.g., 1 bit) indicates whether the user information field 704 corresponds to an uplink user-specific PA. A user information field having a PA flag subfield set to 0 indicates that the user information field does not correspond to an uplink user-specific PA. On the other hand, a user information field having a PA flag subfield set to 1 indicates that the user information field corresponds to an uplink user-specific PA. In this case, the RU allocation information contained in the RU allocation field of the user information field (e.g., the RU allocation field 716 of the user information field 704), together with the user identification information contained in the AID12 field of the user information field (e.g., the AID12 field 718 of the user information field 704) or the SS allocation information contained in the SS allocation field of the user information field (e.g., the SS allocation field 720 of the user information field 704), identifies the uplink user-specific PA. In addition, the PA flag subfield of the user information field for random access should be set to 0. That is, uplink user-specific PAs for random access are not allowed.

[0149] In the EHT basic trigger frame, no more than one user information field not used for random access will be addressed to a single STA. The (multiple) user information fields used for random access should be located after the (multiple) user information fields not used for random access. STAs with uplink user-specific PAs indicated in the common information field should not be addressed by user information fields not used for random access. In addition, more than one uplink user-specific PA assigned to a single STA should not be indicated in the common information field. Advantageously, this reduces the complexity of processing the received EHT basic trigger frame at the STA.

[0150] The first frame 412 may be in the format of the EHT basic trigger frame 700. For example, at 414, the STA 406 may receive the first frame 412 in the form of the EHT basic trigger frame 700. The STA 406 may store the user-specific resource allocation information for the uplink user-specific PA intended for the STA 406. Note that the identification information of the uplink user-specific PA (such as RU allocation information and SS allocation information) is part of the user-specific resource allocation information for the uplink user-specific PA. The user-specific resource allocation information may be retrieved from the user information field, whose AID12 subfield value matches the AID of the STA 406. The STA 406 may then send an EHT TB PPDU 418 to the AP 402 accordingly, wherein the EHT TB PPDU 418 is based on the stored user-specific resource allocation information.

[0151] Similarly, the STA 404 may also receive the first frame 412 in the form of the EHT basic trigger frame 700. The STA 404 may store the user-specific resource allocation information of the uplink user-specific PA intended for the STA 404. Note that the identification information of the uplink user-specific PA (such as RU allocation information and SS allocation information) is part of the user-specific resource allocation information of the uplink user-specific PA. The user-specific resource allocation information may be retrieved from the user information field, whose AID12 subfield value matches the AID of the STA 404. The STA 404 may then send an EHT TB PPDU 416 to the AP 402 accordingly, wherein the EHT TB PPDU 416 is based on the stored user-specific resource allocation information.

[0152] The second frame 422 may also be in the format of the EHT basic trigger frame 700. For example, the STA 406 may receive the second frame 422 in the format of the EHT basic trigger frame 700. The STA 406 may obtain the common parameters from the common information field 702 of the EHT basic trigger frame 700, and determine whether the RU allocation information stored by the STA 406 and the user identification information of the STA 406 at 414 match any RU allocation / AID12 field value in the trigger-related common information field 708 of the common information field 702, or whether the RU allocation information and the SS allocation information stored by the STA 406 at 414 match any RU allocation / SS allocation field value in the trigger-related common information field 708 of the common information field 702. If yes, then at 424, the STA 406 may prepare an EHT TB PPDU 428 based on the user-specific resource allocation information stored by the STA 406 at 414, and send the prepared EHT TB PPDU 428 to the AP 402.

[0153] Likewise, the STA 404 may receive a second frame 422 in the format of the EHT basic trigger frame 700. The STA 404 may obtain the common parameters from the common information field 702 of the EHT basic trigger frame 700, and determine whether the RU allocation information stored by the STA 404 and the user identification information of the STA 404 at 414 match any RU allocation / AID12 field value in the trigger-related common information field 708 of the common information field 702, or whether the RU allocation information and the SS allocation information stored by the STA 404 at 414 match any RU allocation / SS allocation field value in the trigger-related common information field 708 of the common information field 702. If so, the STA 404 may prepare an EHT TB PPDU 426 based on the user-specific resource allocation information stored by the STA 404 at 414, and send the prepared EHT TB PPDU 426 to the AP 402.

[0154] The second frame 422 may also be in the form of Figure 7CThe form of the PA trigger frame 720 according to the second embodiment is shown. The PA trigger frame 720 may include (or be composed of) a frame control field, a duration field, an RA field, a TA field, a common information field, a padding field, and an FCS field. The common information field may include (or be composed of) a trigger type field, a more TF field, a CS required field, and a trigger-related common information field 722. The trigger-related common information field 722 may include (or be composed of) a RU allocation number field and a RU allocation / AID12 tuple field. The RU allocation number field indicates the number of RU allocation / AID12 subfields in the RU allocation / AID12 tuple field. Unlike the PA trigger frame 520 that uses its PAID contained in the trigger-related common information field 522 to request cyclic transmission of an uplink user-specific PA, the PA trigger frame 720 may then use its RU allocation information and user identification information contained in the trigger-related common information field 722 to request cyclic transmission of an uplink user-specific PA. Alternatively, the trigger-related common information field 722 may include (or be composed of) a RU allocation number field and a RU allocation / SS allocation tuple field. The RU allocation number field indicates the number of RU allocation / SS allocation subfields in the RU allocation / SS allocation tuple field. Then, the PA trigger frame 720 may request cyclic transmission of the uplink user-specific PA using the RU allocation information and SS allocation information of the uplink user-specific PA indicated in the trigger-related common information field 722. In the PA trigger frame, more than one uplink user-specific PA assigned to a single STA should not be indicated in the common information field. Advantageously, this reduces the complexity of processing the received PA trigger frame at the STA.

[0155] The PA trigger frame 720 is only used to request cyclic transmission of one or more PAs, such as EHT TB PPDUs 426 and 428. There are only some common parameters in the common information field of the PA trigger frame 720, and other common parameters may not change before one or more PAs expire, and may be obtained from the first frame 412. In addition, in addition to the identification information for the one or more PAs, other user-specific resource allocation information required by the one or more PAs is not included in the PA trigger frame, because it can be obtained from the first frame 412. Advantageously, this reduces the channel overhead of the cyclic transmission of one or more uplink user-specific PAs.

[0156] The second frame 422 may also be in the form of Fig.7DThe form of a data or management frame 730 carrying a PA control subfield according to the second embodiment is shown. The data or management frame 730 may include (or be composed of) a frame control field, a duration / ID field, four address fields, a sequence control field, a QoS control field, an HT control field, a frame body field, and an FCS field. The HT control field may be a 32-bit HE variant HT control field, including (or consisting of) a VHT field (set to 1), an HE field (set to 1), a control ID field (set to a determined value, for example, 7, to indicate that the HT control field of the data or management frame 730 contains a PA control subfield) and a control information field. The 26-bit control information field may include (or be composed of) an 8-bit RU allocation subfield and some common parameters 734, such as a 10-bit UL length subfield, a 5-bit DL TX power subfield, and a 3-bit HE-LTF symbol number subfield. It will be appreciated that other common parameters may be predetermined or implicitly signaled. Unlike the data or management frame 530 that uses its PAID contained in the control information field 532 to request the cyclic transmission of the uplink user-specific PA, the data or management frame 730 can use its RU allocation information contained in the control information field 732 and the user identification information (e.g., MAC address) of the intended STA contained in one of the four address fields to request the cyclic transmission of the uplink user-specific PA. Similar to the PA trigger frame 720, other user-specific resource allocation information required for the uplink user-specific PA is not included in the data or management frame 530 because it can be obtained from the first frame 412. Advantageously, this reduces the channel overhead of the cyclic transmission of the uplink user-specific PA.

[0157] In the second embodiment as described above, after the first frame requesting the initial transmission of the uplink user-specific PA is sent, the uplink user-specific PA may exist for a period of time. In an example, the uplink user-specific PA may exist until the end of the current TXOP. In another example, the uplink user-specific PA may exist for a predetermined number of service periods or beacon intervals. In yet another example, the common information field in the first frame may include signaling to indicate the time period during which the uplink user-specific AP whose initial transmission is requested by the first frame exists after the first frame is sent. For such an example, the uplink user-specific PAs whose initial transmission is requested by the first frame have the same expiration time. Alternatively, the user information field corresponding to the uplink user-specific PA in the first frame may include signaling to indicate the time period during which the uplink user-specific PA exists after the first frame is sent. In another example, the uplink user-specific PAs whose initial transmission is requested by the first frame may have different expiration times.

[0158] In the second embodiment as described above, the AP may send a first frame to update the user-specific resource allocation information of the uplink user-specific PA before the uplink user-specific PA expires, and the user-specific resource allocation information does not include identification information (e.g., RU allocation information and SS allocation information). If the user-specific resource allocation information of the uplink user-specific PA is updated before the uplink user-specific PA expires, and the expected STA fails to receive the update information, the information of the uplink user-specific PA between the AP and the expected STA will not match. If the EHT TB PPDU is not received as a response to the first frame sent, the AP may be able to identify this mismatch. When the STA receives the first frame, the first frame includes complete information about the uplink user-specific PA for which the STA is the expected STA, and the STA should start or reset the timer of the uplink user-specific PA and store or update information about the uplink user-specific PA. Similarly, the STA can also store or update public parameters in the public information field through this process. Advantageously, this enables the AP to perform error recovery from information mismatch.

[0159] Fig. 8AA flowchart 800 is shown showing the processing of the received EHT basic trigger frame 700 at the STA according to the second embodiment. The processing may start at 802. At 804, the common parameters are obtained from the common information field 702. At 806, it is determined whether to request a cyclic transmission of the uplink user-specific PA intended for the STA. This can be done by checking whether the stored RU allocation information and the user identification information of the STA match any RU allocation / AID12 subfield value in the common information field 702, or checking whether the stored RU allocation information and the SS allocation information match any RU allocation / SS allocation subfield value in the common information field 702. If the cyclic transmission of the uplink user-specific PA intended for the STA is requested, the processing may proceed to step 808. Otherwise, the processing may proceed to step 814. At 808, it is determined whether the timer of the uplink user-specific PA is running. If the timer of the uplink user-specific PA is running, the processing may proceed to step 810. Otherwise, the processing may end at step 836. At 810, the user-specific resource allocation information stored by the STA is retrieved. At 814, the number of user information fields is calculated. At 816, the user information field counter is initialized to zero. At 820, it is determined whether the AID of the STA matches the AID12 subfield value of the user information field in the EHT basic trigger frame 700. If the AID of the STA matches the AID12 subfield value, the process may proceed to step 822. If the AID of the STA does not match the AID12 subfield value, the process may proceed to step 828. At 822, it is determined whether the PA flag subfield is set to 1. If the PA flag subfield is not set to 1, which means that the user information field does not correspond to an uplink user-specific PA, the process may proceed to step 826. If the PA flag subfield is set to 1, which means that the user information field corresponds to an uplink user-specific PA, the process may proceed to 824. At 826, the user-specific resource allocation information 714 is obtained from the user information field. At 824, the user-specific resource allocation information 714 is obtained from the user information field and stored by the STA. At 828, it is determined whether the AID12 subfield value of the user information field indicates a user information field for RA for which it is eligible. If so, the process may proceed to step 830. Otherwise, the process may proceed to 832. At 830, a UORA process is performed. At 832, a user information field counter is incremented by 1. At 834, it is determined whether the user information field counter is equal to the number of user information fields in the EHT basic trigger frame 700. If the user information field counter is not equal to the number of user information fields in the EHT basic trigger frame 700, the process may return to step 820 again. If the user information field counter is equal to the number of user information fields in the EHT basic trigger frame 700, the process may end at 836.It can be appreciated that steps 820, 828, 832, and 834 form a loop in which the STA cycles through and reads all user information fields present in the EHT basic trigger frame 700. At 812, based on the common parameters (e.g., the common parameters from the common information field 702) and the user-specific resource allocation information (e.g., the user-specific resource allocation information stored by the STA if the processing is from step 810 or 824, or the user-specific resource allocation information 714 obtained from the user information field if the processing is from step 826), the EHT TB PPDU is prepared. At 836, the process ends.

[0160] Figure 8B A flowchart 840 is shown showing the processing of the received PA trigger frame 720 at the STA according to the second embodiment. The processing may start at step 842. At 844, some common parameters are obtained from the common information field of the PA trigger frame 720. At 846, it is determined whether to request a cyclic transmission of the uplink user-specific PA intended for the STA. This can be done by checking whether the stored RU allocation information and the user identification information of the STA match any RU allocation / AID12 subfield value in the trigger-related common information field 722, or checking whether the stored RU allocation information and SS allocation information match any RU allocation / SS allocation subfield value in the trigger-related common information field 722. If the cyclic transmission of the uplink user-specific PA intended for the STA is requested, the processing may proceed to step 848. Otherwise, the processing may end at step 854. At 848, it is determined whether the timer of the uplink user-specific PA is running. If it is determined that the timer is running, the processing may proceed to step 850. If it is determined that the timer is not running, the processing may end at step 854. At 850, the stored user-specific resource allocation information and other common parameters are retrieved. At 852, an EHT TB PPDU is prepared based on the common parameters and the user-specific resource allocation information. At 854, the process ends.

[0161] Figure 8CA flow chart 860 is shown illustrating processing of a received data or management frame 730 carrying a PA control subfield at a STA that is an intended recipient of the frame 730 according to a second embodiment. Processing may start at step 862. At 864, a common parameter 734 is obtained from the PA control subfield of the data or management frame 730. At 866, a determination is made as to whether a timer of an uplink user-specific PA having RU allocation information indicated in the PA control subfield is running. If it is determined that the timer is running, processing may proceed to step 868. If it is determined that the timer is not running, processing may end at step 872. At 868, user-specific resource allocation information stored by the STA is retrieved. At 870, an EHT TB PPDU is prepared based on the common parameter 734 obtained from the PA control subfield of the data or management frame 730 and the retrieved user-specific resource allocation information. At 872, processing ends.

[0162] Fig.9A A flowchart 900 is depicted showing communication between multiple STAs (904, 906) and an AP 902 over a TXOP utilizing an uplink user-specific PA according to various embodiments. Block 908 shows a contention-based channel access process, such as an EDCA process, and a SIFS 910 is shown. The AP 902 may generate a first frame 912. Complete information of the uplink user-specific PA is announced in the first frame 912. The complete PA information may include identification information and user-specific resource allocation information. In an embodiment, the identification information may be a PAID of the uplink user-specific PA. In another embodiment, the identification information may be RU allocation information and user identification information of the uplink user-specific PA. In yet another embodiment, the identification information may be RU allocation information and SS allocation information of the uplink user-specific PA. In various embodiments, the identification information is included in the frame body of the frame together with the user-specific resource allocation information to identify the uplink user-specific PA. Figure 4A Unlike the first frame 412 in FIG. 1 , the first frame 912 does not request an initial transmission of an uplink user-specific PA. The AP 902 may send the generated first frame 912 to the STAs 404 and 906.

[0163] At 914, STA 906 may receive the first frame 912 and store the complete information of the uplink user-specific PA (ie, identification information and user-specific resource allocation information of the uplink user-specific PA intended for STA 906). Figure 4AUnlike the illustrated embodiment, STA 906 does not send an EHT TB PPDU to AP 902 because the first frame 912 does not request an initial transmission. STA 904 may also receive and store complete information about the uplink user-specific PA (i.e., identification information and user-specific resource allocation information of the uplink user-specific PA intended for STA 904).

[0164] Thereafter, the AP 902 may request transmission of an uplink user-specific PA for the STA 904 and transmission of an uplink user-specific PA for the STA 906 by sending a second frame 922. The second frame 922 may carry identification information of the uplink user-specific PA for the STA 904 to request initial or cyclic transmission of the uplink user-specific PA for the STA 904, and carry identification information of the uplink user-specific PA for the STA 906 to request initial or cyclic transmission of the uplink user-specific PA for the STA 906. In various embodiments, the identification information of the uplink user-specific PA is included in the frame body of the second frame 922 to request transmission of the uplink user-specific PA, and the frame does not include user-specific resource allocation information of the uplink user-specific PA. In various embodiments, the identification information is included in the MAC header of the second frame 922 to request transmission of the uplink user-specific PA, and the frame does not include user-specific resource allocation information of the uplink user-specific PA. Advantageously, since the second frame does not contain user-specific resource allocation information of the uplink user-specific PA, channel overhead for transmission of the uplink user-specific PA may be reduced.

[0165] At 924, STA 406 may prepare an EHT TB PPDU 918 based on the stored user-specific resource allocation information of the uplink user-specific PA and send the EHT TB PPDU 918 to AP 902. EHT TB PPDU 918 is a transmission for the uplink user-specific PA of STA 906. STA 904 may also prepare an EHT TB PPDU 916 based on the stored user-specific resource allocation information of the uplink user-specific PA and send the EHT TB PPDU 916 to AP 902. EHT TB PPDU 916 is a transmission for the uplink user-specific PA of STA 904. EHT TB PPDUs 916 and 918 may be transmitted together as shown in FIG. Figure 2B The format of the EHT TB PPDU 212 is the same as shown. AP 902 may receive the transmissions of EHT PPDUs 916 and 918 and then send a multi-STA BlockAck frame 920 to STAs 904 and 906. Fig.9AAs shown, the initial or cyclic transmission of the uplink user-specific PA can occur in the same TXOP as the first frame transmission. The initial or cyclic transmission can also occur in a different TXOP than the first frame transmission, such as Fig. 9B That is, in an example, the uplink user-specific PA may exist until the end of the current TXOP. In another example, the uplink user-specific PA may exist for a predetermined number of service periods or beacon intervals. Fig. 9B In the embodiment, the second frame 922 is sent by the AP 902 in a different TXOP than the first frame 912, and thus the transmission requested by the second frame 922 (e.g., uplink user-specific PA transmission of the EHT TB PPDUs 916 and 918) also occurs in a different TXOP than the first frame 912. It can be appreciated that the transmission of the second frame 922 occurs within the time duration when the uplink user-specific PA for the STAs 904 and 906 exists.

[0166] Fig. 10A FIG. 1 shows a format of an EHT announcement frame 1000 for uplink or downlink multi-user communication between an AP and multiple STAs in an EHT WLAN according to a third embodiment. The PA announcement frame 1000 includes complete information about one or more PAs and can be used as Fig.9A and Fig. 9B The first frame 912 in the PA announcement frame 1000. The PA announcement frame 1000 uses the PAID of the uplink user-specific PA to identify the uplink user-specific PA. The PA announcement frame 1000 may include a frame control field, a duration field, an RA field, a TA field, a common information field, one or more user information fields (such as user information field 1004), a padding field, and an FCS field. The frame control field, the duration field, the RA field, and the TA field may be grouped in a MAC header of the PA announcement frame 1000. The common information field, the one or more user information fields 1004, and the padding field may be grouped in a frame body of the PA announcement frame 1000.

[0167] Fig. 10AThe user information field 1004 is also depicted in more detail. The user information field 1004 includes a direction field 1006, an AID12 field, a PAID field 1002, a RU allocation field, a UL FEC codec type field, a UL MCS field, a UL DCM field, a SS allocation field, a UL target RSSI field, an MPDU MU spacing factor subfield, a TID aggregation restriction subfield, and a preferred AC subfield. The RU allocation field, the UL FEC codec type field, the UL MCS field, the UL DCM field, the SS allocation field, the UL target RSSI field, the MPDU MU spacing factor subfield, the TID aggregation restriction subfield, and the preferred AC subfield constitute the user-specific resource allocation information 1008 of the user information field 1004.

[0168] As described above, the user information field 1004 may include a direction field 1006. The direction field 1006 indicates whether the user information field 1004 corresponds to an uplink user-specific PA or a downlink user-specific PA. For example, a direction field value of 1 indicates a downlink user-specific PA, and a direction field value of 0 indicates an uplink user-specific PA. In the present embodiment, the direction field 1006 is set to 0 to indicate that the user information field 1004 corresponds to an uplink user-specific PA. The user information field 1004 may also include a PAID field 1002, which indicates the PAID of the uplink user-specific PA corresponding to the user information field 1004.

[0169] The first frame 912 may be in the format of a PA announcement frame 1000. For example, at 914, the STA 906 may receive the first frame 912 in the form of a PA announcement frame 1000. The STA 906 may store user-specific resource allocation information and identification information for an uplink user-specific PA intended for the STA 906. The identification information (e.g., PAID) may be retrieved from the PAID subfield 1002 of the user information field, whose AID12 subfield value matches the AID of the STA 906. The user-specific resource allocation information may also be retrieved from the user information field.

[0170] Likewise, the STA 904 may also receive the first frame 912 in the form of a PA announcement frame 1000. The STA 904 may store user-specific resource allocation information and identification information for an uplink user-specific PA intended for the STA 904. The identification information (e.g., PAID) may be retrieved from the PAID subfield 1002 of the user information field, whose AID12 subfield value matches the AID of the STA 904. The user-specific resource allocation information may also be retrieved from the user information field.

[0171] Fig. 10BFIG. 1 shows a format of an EHT basic trigger frame 1010 for uplink multi-user communication between an AP and multiple STAs in an EHT WLAN according to a third embodiment. The EHT basic trigger frame 1010 is a variant of an existing trigger frame and can be used as Fig.9A and Fig. 9B The second frame 922 in the EHT basic trigger frame 1010. The EHT basic trigger frame 1010 uses the PAID of the uplink user-specific PA to identify the uplink user-specific PA. The EHT basic trigger frame 1010 may include a frame control field, a duration field, an RA field, a TA field, a common information field, one or more user information fields (such as the user information field 1016), a padding field, and an FCS field. The frame control field, the duration field, the RA field, and the TA field may be grouped in the MAC header of the EHT basic trigger frame 1010. The common information field, one or more user information fields 1016, and the padding field may be grouped in the frame body of the EHT basic trigger frame 1010. The common information field of the EHT basic trigger frame 1010 (including all subfields of the common information field) is the same as Figure 5A The common information field 502 (including all subfields of the common information field 502) of the EHT basic trigger frame 500 shown is the same. The user information field 1016 may include (or consist of) an AID12 field, an RU allocation field, a UL FEC codec type field, a UL MCS field, a UL DCM field, an SS allocation field, a UL target RSSI field, and a trigger-related user information field 1012. The trigger-related user information field 1012 may include (or consist of) an MPDU MU interval factor subfield, a TID aggregation restriction subfield, and a preferred AC subfield. The RU allocation field, the UL FEC codec type field, the UL MCS field, the UL DCM field, the SS allocation field, the UL target RSSI field, the MPDU MU interval factor subfield, the TID aggregation restriction subfield, and the preferred AC subfield constitute the user-specific resource allocation information 1014 of the user information field 1016.

[0172] In the EHT basic trigger frame, no more than one user information field not used for random access will be addressed to a single STA. The (multiple) user information fields used for random access should be located after the (multiple) user information fields not used for random access. STAs with uplink user-specific PAs indicated in the common information field should not be addressed by user information fields not used for random access. In addition, more than one uplink user-specific PA assigned to a single STA should not be indicated in the common information field. Advantageously, this reduces the complexity of processing the received EHT basic trigger frame at the STA.

[0173] The second frame 922 may also be in the format of the EHT basic trigger frame 1010. For example, the STA 906 may receive the second frame 922 in the format of the EHT basic trigger frame 1010. The STA 906 may obtain the common parameters from the common information field of the EHT basic trigger frame 1010 and determine whether the (multiple) PAIDs stored by the STA 906 at 914 match any PAID subfield value in the trigger-related common information field. If so, at 924, the STA 906 may prepare an EHT TB PPDU 918 based on the user-specific resource allocation information stored by the STA 906 at 914 and send the prepared EHT TB PPDU 918 to the AP 902.

[0174] Likewise, the STA 904 may receive a second frame 922 in the format of the EHT basic trigger frame 1010. The STA 904 may obtain the common parameters from the common information field of the EHT basic trigger frame 1010 and determine whether the PAID(s) stored by the STA 914 matches any PAID subfield value in the trigger-related common information field. If so, the STA 904 may prepare an EHT TB PPDU 916 based on the user-specific resource allocation information stored by the STA 904 and send the prepared EHT TB PPDU 916 to the AP 902.

[0175] The second frame 922 may also be in the form of Figure 5C The form of the PA trigger frame 520 according to the third embodiment is shown. The PA trigger frame 520 is only used to request the transmission of one or more PAs, such as EHT TB PPDUs 916 and 918. There are only some common parameters in the common information field of the PA trigger frame 520, and before one or more PAs expire, other common parameters may not change and may be obtained from the first frame 912. In addition, the user-specific resource allocation information required by one or more PAs is not included in the PA trigger frame because it can be obtained from the first frame 912. Advantageously, this reduces the channel overhead of the transmission of the uplink user-specific PA.

[0176] The second frame 922 may also be in the form of Figure 5D The form of a data or management frame 530 carrying a PA control subfield according to the third embodiment is shown. The data or management frame 530 requests the transmission of an uplink user-specific PA using its PAID indicated in the control information field 532. Similar to the PA trigger frame 520, the user-specific resource allocation information required for the uplink user-specific PA is not included in the data or management frame 530 because it can be obtained from the first frame 912. Advantageously, this reduces the channel overhead of the transmission of the uplink user-specific PA.

[0177] As described above, for the third embodiment, channel overhead can be further reduced. In the first frame, two or more user-specific PAs allocated for uplink MU-MIMO may include the same PAID, which may be indicated in the second frame to request transmissions from two or more STAs participating in the uplink MU-MIMO allocation. In an example, the first frame may be used to assign the same PAID, the same RU, and corresponding spatial streams to two or more user-specific PAs allocated for uplink MU-MIMO. In another example, more than one first frame may be used to assign the same PAID, the same RU, and corresponding spatial streams to two or more user-specific allocations allocated for uplink MU-MIMO. Alternatively, in the first frame, the same PAID may be assigned to a group of user-specific PAs, which may be indicated in the second frame to request transmissions from each user-specific PA in the group of user-specific PAs.

[0178] In the third embodiment as described above, after the first frame announcing the uplink user-specific PA is sent, the uplink user-specific PA may exist for a time period. In an example, the uplink user-specific PA may exist until the end of the current TXOP. In another example, the uplink user-specific PA may exist for a predetermined number of service periods or beacon intervals. In yet another example, the common information field in the first frame may include signaling for indicating the time period in which the uplink user-specific AP announced by the first frame exists after the first frame is sent. For such an example, the uplink user-specific PAs announced by the first frame have the same expiration time. Alternatively, the user information field corresponding to the uplink user-specific PA in the first frame may include signaling for indicating the time period in which the uplink user-specific PA exists after the first frame is sent. In another example, the uplink user-specific PAs announced by the first frame may have different expiration times.

[0179] Fig.11A flowchart 1100 is shown showing processing of a received EHT basic trigger frame 1010 at a STA according to a third embodiment. Processing may start at 1102. At 1104, public parameters of a common information field from the EHT basic trigger frame 1010 are obtained. At 1106, it is determined whether the stored (multiple) PAIDs match any PAID subfield value in the common information field. If the stored (multiple) PAIDs match the PAID subfield value in the common information field, the process may proceed to step 1108. If the stored (multiple) PAIDs do not match any PAID subfield value in the common information field, the process may proceed to step 1114. At 1108, it is determined whether the timer of the uplink user-specific PA with the matching PAID is running. If the timer of the uplink user-specific PA is running, the process may proceed to step 1110. Otherwise, the process may end at step 1130. At 1110, the user-specific resource allocation information stored by the STA is retrieved. At 1114, the number of user information fields present in the EHT basic trigger frame 1010 is calculated. At 1116, the user information field counter is initialized to zero. At 1118, it is determined whether the AID of the STA matches the AID12 subfield value of the user information field in the EHT basic trigger frame 1010. If the AID of the STA matches the AID12 subfield value, the process may proceed to step 1120. If the AID of the STA does not match the AID12 subfield value, the process may proceed to step 1122. At 1120, user-specific resource allocation information is obtained from the user information field for preparing the EHT TB PPDU. At 1122, it is determined whether the AID12 subfield value of the user information field indicates a user information field for which RA is eligible. If so, the process may proceed to step 1124. Otherwise, the process may proceed to 1126. At 1124, a UORA process is performed. At 1126, the user information field counter is incremented by 1. At 1128, it is determined whether the user information field counter is equal to the number of user information fields in the EHT basic trigger frame 1010. If the user information field counter is not equal to the number of user information fields in the EHT basic trigger frame 1010, the process may return to step 1118 again. If the user information field counter is equal to the number of user information fields in the EHT basic trigger frame 1010, the process may end at 1130. It can be appreciated that steps 1118, 1122, 1126, and 1128 form a loop in which the STA cycles through and reads all user information fields present in the EHT basic trigger frame 1010.At 1112, based on the common parameters (e.g., the common parameters from the common information field of the EHT basic trigger frame 1010) and the user-specific resource allocation information (e.g., the user-specific resource allocation information stored by the STA if the processing is from step 1110, or the user-specific resource allocation information 1014 obtained from the user information field if the processing is from step 1120), prepare the EHT TB PPDU. At 1130, the process ends.

[0180] exist Figure 6B The flowchart 640 also shows the processing of the received PA trigger frame 520 at the STA according to the third embodiment.

[0181] Figure 6C Flowchart 660 also illustrates processing of a received data or management frame 530 carrying a PA Control subfield at a STA that is an intended recipient of the frame 530 according to the third embodiment.

[0182] In the third embodiment as described above, the AP may send a first frame to update the user-specific resource allocation information of the uplink user-specific PA before the uplink user-specific PA expires. If the user-specific resource allocation information of the uplink user-specific PA is updated before the uplink user-specific PA expires, and the expected STA fails to receive the update information, the information of the uplink user-specific PA will not match between the AP and the expected STA. If no EHT TB PPDU is received as a response to the second frame sent, the AP may be able to identify this mismatch. When the STA receives the first frame, the first frame has information about the uplink user-specific PA for which the STA is one of the expected recipients, and the STA should start or reset the timer of the uplink user-specific PA and store or update the information about the uplink user-specific PA. Similarly, the STA can also store or update public parameters in the public information field through this process. Advantageously, this enables the AP to perform error recovery from information mismatch.

[0183] Fig.12 FIG. 1 shows a format of an EHT announcement frame 1200 for uplink or downlink multi-user communication between an AP and multiple STAs in an EHT WLAN according to a fourth embodiment. The PA announcement frame 1200 includes complete information about one or more PAs and can be used as Fig.9A and Fig. 9BThe first frame 912 in the PA announcement frame 1200. The PA announcement frame 1200 may identify the uplink user-specific PA using the RU allocation information of the uplink user-specific PA and the user identification information of the STA addressed by the uplink user-specific PA. Alternatively, the PA announcement frame 1200 may identify the uplink user-specific PA using the RU allocation information of the uplink user-specific PA and the SS allocation information (e.g., the starting spatial stream). The PA announcement frame 1200 may include a frame control field, a duration field, an RA field, a TA field, a common information field, one or more user information fields (such as the user information field 1204), a padding field, and an FCS field. The frame control field, the duration field, the RA field, and the TA field may be grouped in a MAC header of the PA announcement frame 1200. The common information field, the one or more user information fields 1204, and the padding field may be grouped in a frame body of the PA announcement frame 1200.

[0184] Fig.12 The user information field 1204 is also depicted in more detail. The user information field 1204 includes the direction field 1026, the AID12 field, the RU allocation field 1202, the UL FEC codec type field, the UL MCS field, the UL DCM field, the SS allocation field, the UL target RSSI field, the MPDU MU spacing factor subfield, the TID aggregation restriction subfield, and the preferred AC subfield. The RU allocation field, the UL FEC codec type field, the UL MCS field, the UL DCM field, the SS allocation field, the UL target RSSI field, the MPDU MU spacing factor subfield, the TID aggregation restriction subfield, and the preferred AC subfield constitute the user-specific resource allocation information 1208 of the user information field 1204.

[0185] As described above, the user information field 1204 may include a direction field 1206. The direction field 1206 indicates whether the user information field 1204 corresponds to an uplink user-specific PA or a downlink user-specific PA. For example, a direction field value of 1 indicates a downlink user-specific PA, while a direction field value of 0 indicates an uplink user-specific PA. In this embodiment, the direction field 1206 is set to 0 to indicate that the user information field corresponds to an uplink user-specific PA. The user information field 1204 may also include an RU allocation field 1202 indicating RU allocation information, an SS allocation field 1212 indicating SS allocation information, and an AID12 field 1214 indicating user identification information. Unlike the PA announcement frame 1000 that uses the PAID indicated in the PAID field 1002 to identify the uplink user-specific PA corresponding to the user information field 1004, the PA announcement frame 1200 may use the RU allocation information indicated in the RU allocation field 1202 and the user identification information indicated in the AID12 field 1214 to identify the uplink user-specific PA corresponding to the user information field 1204. Alternatively, the PA announcement frame 1200 may use the RU allocation information indicated in the RU allocation field 1202 and the SS allocation information indicated in the SS allocation field 1212 to identify the uplink user-specific PA corresponding to the user information field 1204.

[0186] The first frame 912 may be in the format of the PA announcement frame 1200. For example, at 914, the STA 906 may receive the first frame 912 in the form of the PA announcement frame 1200. The STA 906 may store the user-specific resource allocation information of the uplink user-specific PA intended for the STA 906. Note that the identification information of the uplink user-specific PA (such as RU allocation information and SS allocation information) is part of the user-specific resource allocation information of the uplink user-specific PA. The user-specific resource allocation information may be retrieved from the user information field, whose AID12 subfield value matches the AID of the STA 906.

[0187] Likewise, the STA 904 may also receive the first frame 912 in the form of a PA announcement frame 1200. The STA 904 may store the user-specific resource allocation information of the uplink user-specific PA intended for the STA 904. Note that the identification information of the uplink user-specific PA (such as RU allocation information and SS allocation information) is part of the user-specific resource allocation information of the uplink user-specific PA. The user-specific resource allocation information may be retrieved from the user information field, whose AID12 subfield value matches the AID of the STA 904.

[0188] The second frame 922 may be in the format of an EHT basic trigger frame for uplink multi-user communication between an AP and a plurality of STAs in an EHT WLAN according to the fourth embodiment. The EHT basic trigger frame according to the fourth embodiment is a variant of an existing trigger frame and may be used as Fig.9A and Fig. 9B The second frame 922 in the EHT basic trigger frame according to the fourth embodiment may use RU allocation information and user identification information to identify the uplink user-specific PA. Alternatively, the EHT basic trigger frame according to the fourth embodiment may use RU allocation information and SS allocation information to identify the uplink user-specific PA. The EHT basic trigger frame according to the fourth embodiment may include a frame control field, a duration field, an RA field, a TA field, a common information field, one or more user information fields, a padding field, and an FCS field. The frame control field, the duration field, the RA field, and the TA field may be grouped in the MAC header of the EHT basic trigger frame. The common information field, one or more user information fields, and the padding field may be grouped in the frame body of the EHT basic trigger frame according to the fourth embodiment. The common information field (including all subfields of the common information field) of the EHT basic trigger frame according to the fourth embodiment is the same as Fig. 7A The common information field 702 (including all subfields of the common information field 702) of the EHT basic trigger frame 700 shown in FIG. 1 is the same as that of the common information field 702 (including all subfields of the common information field 702). Fig. 10B The user information field 1016 (including all subfields of the user information field 1016 ) of the illustrated EHT basic trigger frame 1010 are the same.

[0189] For example, the STA 906 may receive a second frame 922 in the format of the EHT basic trigger frame 500 according to the fourth embodiment. The STA 906 may obtain the common parameters from the common information field of the EHT basic trigger frame, and determine whether the RU allocation information and the user identification information stored by the STA 906 at 914 match any RU allocation / AID12 subfield value in the trigger-related common information field of the common information field, or whether the RU allocation information and the SS allocation information stored by the STA 906 at 914 match any RU allocation / SS allocation subfield value in the trigger-related common information field of the common information field. If yes, at 924, the STA 906 may prepare an EHT TB PPDU 918 based on the user-specific resource allocation information stored by the STA 906 at 914, and send the prepared EHT TB PPDU 918 to the AP 902.

[0190] Likewise, the STA 904 may receive a second frame 922 in the EHT basic trigger frame format according to the fourth embodiment. The STA 904 may obtain common parameters from the common information field of the EHT basic trigger frame, and determine whether the RU allocation information and user identification information stored by the STA 904 at 914 match any RU allocation / AID12 subfield value in the trigger-related common information field of the common information field, or whether the RU allocation information and SS allocation information stored by the STA 904 at 914 match any RU allocation / SS allocation subfield value in the trigger-related common information field of the common information field. If yes, the STA 904 may prepare an EHT TB PPDU 916 based on the user-specific resource allocation information stored by the STA 904 at 914, and send the prepared EHT TB PPDU 916 to the AP 902.

[0191] In the EHT basic trigger frame, no more than one user information field not used for random access will be addressed to a single STA. The (multiple) user information fields used for random access should be located after the (multiple) user information fields not used for random access. STAs with uplink user-specific PAs indicated in the common information field should not be addressed by user information fields not used for random access. In addition, more than one uplink user-specific PA assigned to a single STA should not be indicated in the common information field. Advantageously, this reduces the complexity of processing the received EHT basic trigger frame at the STA.

[0192] The second frame 922 may also be in the form of Figure 7C The format of the PA trigger frame 720 according to the second embodiment is shown.

[0193] The PA trigger frame 720 is only used to request the transmission of one or more uplink user-specific PAs, such as EHT TBPPDUs 916 and 918. There are only some common parameters in the common information field of the PA trigger frame 720, and other common parameters may not change before one or more PAs expire, and may be obtained from the first frame 912. In addition, in addition to the identification information of the one or more PAs, the user-specific resource allocation information required by the one or more PAs is not included in the PA trigger frame, because it can be obtained from the first frame 912. Advantageously, this reduces the channel overhead of the transmission of one or more uplink user-specific PAs.

[0194] The second frame 922 may also be in the form of Fig.7DThe form of a data or management frame 730 carrying a PA control subfield according to the fourth embodiment is shown. The data or management frame 730 requests the transmission of an uplink user-specific PA using its RU allocation information contained in the control information field 732 and the user identification information (e.g., MAC address) contained in one of the four address fields. Other user-specific resource allocation information required for the uplink user-specific PA is not included in the data or management frame 730 because it can be obtained from the first frame 912. Advantageously, this reduces the channel overhead of the transmission of the uplink user-specific PA.

[0195] In the fourth embodiment as described above, after the first frame announcing the uplink user-specific PA is sent, the uplink user-specific PA may exist for a period of time. In an example, the uplink user-specific PA may exist until the end of the current TXOP. In another example, the uplink user-specific PA may exist for a predetermined number of service periods or beacon intervals. In yet another example, the common information field in the first frame may include signaling for indicating the time period in which the uplink user-specific AP announced by the first frame exists after the first frame is sent. For such an example, the uplink user-specific PAs announced by the first frame have the same expiration time. Alternatively, the user information field corresponding to the uplink user-specific PA in the first frame may include signaling for indicating the time period in which the uplink user-specific PA exists after the first frame is sent. In an alternative example, the uplink user-specific PAs announced by the first frame may have different expiration times.

[0196] Fig.13A flowchart 1300 is shown showing the processing of a received EHT basic trigger frame at a STA according to a fourth embodiment. Processing may start at 1302. At 1304, public parameters from the common information field of the EHT basic trigger frame are obtained. At 1306, it is determined whether to request transmission of an uplink user-specific PA intended for the STA. This may be accomplished by checking whether the stored RU allocation information and user identification information match any RU allocation / AID12 subfield value in the common information field, or by checking whether the stored RU allocation information and SS allocation information match any RU allocation / SS allocation subfield value in the common information field. If transmission of an uplink user-specific PA intended for the STA is requested, the processing may proceed to step 1308. Otherwise, the processing may proceed to step 1314. At 1308, it is determined whether a timer for an uplink user-specific PA is running. If a timer for an uplink user-specific PA is running, the processing may proceed to step 1310. Otherwise, the processing may end at step 1330. At 1310, the user-specific resource allocation information stored by the STA is retrieved. At 1314, the number of user information fields present in the received EHT basic trigger frame is calculated. At 1316, the user information field counter is initialized to zero. At 1318, it is determined whether the AID of the STA matches the AID12 subfield value of the user information field in the received EHT basic trigger frame. If the AID of the STA matches the AID12 subfield value, the process may proceed to step 1320. If the AID of the STA does not match the AID12 subfield value, the process may proceed to step 1322. At 1320, user-specific resource allocation information is obtained from the user information field for preparing the EHT TB PPDU. At 1322, it is determined whether the AID12 subfield value of the user information field indicates a user information field for which the RA is eligible. If so, the process may proceed to step 1324. Otherwise, the process may proceed to 1326. At 1324, a UORA process is performed. At 1326, the user information field counter is incremented by 1. At 1328, it is determined whether the user information field counter is equal to the number of user information fields in the received EHT basic trigger frame. If the user information field counter is not equal to the number of user information fields in the received EHT basic trigger frame, the process may return to step 1318 again. If the user information field counter is equal to the number of user information fields in the received EHT basic trigger frame, the process may end at 1330. It can be appreciated that steps 1318, 1322, 1326, and 1328 form a loop in which the STA cycles through and reads all user information fields present in the received EHT basic trigger frame.At 1312, based on the common parameters (e.g., the common parameters from the common information field of the received EHT basic trigger frame) and the user-specific resource allocation information (e.g., the user-specific resource allocation information stored by the STA if the processing is from step 1310, or the user-specific resource allocation information obtained from the user information field if the processing is from step 1320), prepare the EHT TB PPDU. At 1330, the process ends.

[0197] exist Figure 8B The flowchart 840 also shows the processing of the received PA trigger frame 720 at the STA according to the fourth embodiment.

[0198] Figure 8C The flowchart 860 also illustrates the processing of a received data or management frame 730 carrying a PA Control subfield at a STA that is an intended recipient of the data and management frame 730 according to the fourth embodiment.

[0199] In the fourth embodiment as described above, the AP may send a first frame to update the user-specific resource allocation information of the uplink user-specific PA before the uplink user-specific PA expires, and the user-specific resource allocation information does not include identification information (e.g., RU allocation information and SS allocation information). If the user-specific resource allocation information of the uplink user-specific PA is updated before the uplink user-specific PA expires, and the expected STA fails to receive the update information, the information of the uplink user-specific PA between the AP and the expected STA will not match. If the EHT TBPPDU is not received as a response to the second frame sent, the AP may be able to identify this mismatch. When the STA receives the first frame, the first frame has complete information of the uplink user-specific PA for which the STA is one of the expected recipients, and the STA should start or reset the timer of the uplink user-specific PA and store or update information about the uplink user-specific PA. Similarly, the STA can also store or update public parameters in the public information field through this process. Advantageously, this enables the AP to perform error recovery from information mismatch.

[0200] According to the third embodiment or the fourth embodiment, the AP may send a PA announcement frame to announce the downlink user-specific PA information of one or more STAs. The user-specific allocation information of the downlink user-specific PA is not included in the EHT-SIG-B field of the EHT MU PPDU; however, the RU information of the downlink user-specific PA is included in the EHT-SIG-B field of the EHT MU PPDU, which can be used to help the intended STA identify the presence of the downlink user-specific PA in the EHT MU PPDU. In other words, the initial or cyclic transmission of the downlink user-specific PA is accompanied by partial control signaling (i.e., the RU information of the PA). Advantageously, the EHT-SIG-B overhead can be reduced.

[0201] Fig.14A and Fig. 14B A flowchart 1400 is shown showing communication between a STA 1404 and an AP 1402 with a downlink user-specific PA according to the third embodiment or the fourth embodiment. Box 1406 shows a contention-based channel access process and shows SIFS 1408. AP 1402 may send a PA announcement frame 1410, which may include downlink user-specific PA information for one or more STAs. At 1412, STA 1402 may store or update its own (multiple) downlink user-specific PA's RU information and user-specific allocation information. Then, AP 1402 may send an EHT MUPPDU 1414, which may include a transmission of a downlink user-specific PA for the STA and may include corresponding RU information, but does not include corresponding user-specific allocation information. At 1416, STA 1404 may receive the transmission of the downlink user-specific PA using the stored RU information and user-specific allocation information of the downlink user-specific PA. Then, STA 1404 may send a BlockAck frame 1418. The PA announcement frame and the EHT MU PPDU may be sent in different TXOPs.

[0202] The PA announcement frame 1410 may be in the form of Fig.12 The format of the PA announcement frame 1200 is shown. Fig.15A The structure of the user information field of the user-specific PA allocated for downlink non-MU-MIMO according to the third embodiment or the fourth embodiment is depicted. Fig. 15B The structure of the user information field of the user-specific PA for downlink MU-MIMO allocation according to the third embodiment or the fourth embodiment is depicted. As can be seen from both figures, the direction field is set to 1 to indicate a downlink user-specific PA.

[0203] According to the third embodiment or the fourth embodiment, the downlink user-specific PA may exist for a time period after the PA announcement frame announcing the downlink user-specific PA is sent. In an example, the downlink user-specific PA may exist until the end of the current TXOP. In another example, the downlink user-specific PA may exist for a predetermined number of service periods or beacon intervals. In yet another example, the common information field in the PA announcement frame may include signaling to indicate the time period in which the downlink user-specific AP announced by the PA announcement frame exists after the PA announcement frame is sent. For such an example, the downlink user-specific PAs announced by the PA announcement frame have the same expiration time. Alternatively, the user information field corresponding to the downlink user-specific PA in the PA announcement frame may include signaling to indicate the time period in which the downlink user-specific PA exists after the PA announcement frame is sent. In an alternative example, the downlink user-specific PAs announced by the PA announcement frame may have different expiration times.

[0204] When a STA receives a PA announcement frame announcing one or more downlink user-specific PAs for which the STA is one of the intended recipients (it should be understood that the EHT MU PPDU is used for downlink multi-user transmission and each allocation in the EHT MU PPDU has one or more intended STAs), the STA can start or reset the timer of each of the one or more downlink user-specific PAs, and store or update the RU information and user-specific allocation information of the one or more downlink user-specific PAs.

[0205] If the RU information and / or user-specific allocation information of the downlink user-specific PA is not there, the STA may not be able to correctly receive the transmission of the downlink user-specific PA. Thus, for the purpose of error recovery, according to an embodiment, advantageously, an example rule may be that at least one MPDU (MAC protocol data unit) that requires confirmation may be included in the transmission of the downlink user-specific PA, immediately following the most recently sent PA announcement frame announcing the downlink user-specific PA. If the AP does not receive a positive confirmation of the transmission of the downlink user-specific PA from the expected STA, it knows that the RU information and / or user-specific allocation information of the downlink user-specific PA may not be at the expected STA, and then the AP may not schedule another transmission of the downlink user-specific PA, and may resend the PA announcement frame to announce the downlink user-specific PA.

[0206] According to the third to fourth embodiments, the EHT-SIG-B field of the EHT MU PPDU 1414 is separately encoded on each L×20 MHz subchannel, where L=1 or 2. In the case where the CBW is greater than 20 MHz, the EHT-SIG-B field with L=1 may have better EHT-SIG-B decoding performance than the 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 sent with a 20 MHz bandwidth. For decoding the EHT-SIG-B field with L=2, channel estimation with interpolation is required, which may reduce the performance of decoding the EHT-SIG-B field with L=2. On the other hand, compared with the EHT-SIG-B field with L=1, the EHT-SIG-B field with L=2 may have less EHT-SIG-B overhead, especially for larger CBWs. In addition, if the intended STAs of the EHT MU PPDU 1414 include at least one 20 MHz operating STA, the EHT-SIG-B field of L=2 should not be used because the EHT-SIG-B field of L=2 cannot be decoded by the 20 MHz operating STA. As a result, the AP can advantageously determine the value of L at its own discretion, and signaling can be included in the EHT-SIG-A field of the EHT MU PPDU 1414 to indicate whether L takes the value of 1 or 2.

[0207] Fig.16A A table showing how the number of EHT-SIG-B content channels depends on the values ​​of CBW and L according to various embodiments. Fig.16A As shown, in the case where the CBW is 20MHz, L can only be 1 because the EHT-SIG-B field is encoded on a per 20MHz basis and there is only one EHT-SIG-B content channel. In an embodiment where the CBW is 40MHz, L can be assigned a value of 1 or 2 by the AP. 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 embodiments where the CBW is 80MHz, 80+80MHz, 160MHz, 160+160MHz, or 320MHz, there will be two EHT-SIG-B content channels regardless of the value of L. More details will be provided below.

[0208] Fig. 16B The figure shows the mapping of one or two EHT-SIG-B content channels in the EHT MU PPDU of 40 MHz. The number of EHT-SIG-B content channels depends on the value of CBW and L, as Fig.16AAs shown. The 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), which are transmitted in the 1st and 2nd 20MHz sub-channels respectively. When L=2, there will be only one EHT-SIG-B content channel.

[0209] Fig. 16C A diagram showing 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 EHT MU PPDU of 80 MHz. When L=1, in an 80 MHz channel including four 20 MHz sub-channels, EHT-SIG-B content channel 1 is duplicated and transmitted in the 1st and 3rd 20 MHz sub-channels, and EHT-SIG-B content channel 2 is duplicated and transmitted in the 2nd and 4th 20 MHz sub-channels. When L=2, in an 80 MHz channel including two 40 MHz sub-channels, EHT-SIG-B content channel 1 is transmitted in the first 40 MHz sub-channel, and EHT-SIG-B content channel 2 is transmitted in the second 40 MHz sub-channel.

[0210] Fig.16D A diagram showing the mapping of two EHT-SIG-B content channels in an EHT MU PPDU of 80+80MHz or 160MHz. When L=1, in an 80+80MHz or 160MHz channel containing eight 20MHz subchannels, EHT-SIG-B content channel 1 is duplicated and transmitted in the 1st, 3rd, 5th, and 7th 20MHz subchannels, and EHT-SIG-B content channel 2 is duplicated and transmitted in the 2nd, 4th, 6th, and 8th 20MHz subchannels. When L=2, in an 80+80MHz or 160MHz channel containing four 40MHz subchannels, EHT-SIG-B content channel 1 is duplicated and transmitted in the 1st and 3rd 40MHz subchannels, and EHT-SIG-B content channel 2 is duplicated and transmitted in the 2nd and 4th 40MHz subchannels.

[0211] Fig.16EA diagram showing mapping of two EHT-SIG-B content channels in an EHT MU PPDU of 160+160MHz or 320MHz. When L=1, in a 160+160MHz or 320MHz channel containing 16 20MHz subchannels, EHT-SIG-B content channel 1 is duplicated and transmitted in the 1st, 3rd, 5th, 7th, 9th, 11th, 13th, and 15th 20MHz subchannels, and EHT-SIG-B content channel 2 is transmitted in the 2nd, 4th, 6th, 8th, 10th, 12th, 14th, and 16th 20MHz subchannels. When L=2, in a 160+160 MHz or 320 MHz channel containing 8 40 MHz sub-channels, EHT-SIG-B content channel 1 is replicated and transmitted in the 1st, 3rd, 5th and 7th 40 MHz sub-channels, and EHT-SIG-B content channel 2 is replicated and transmitted in the 2nd, 4th, 6th and 8th 40 MHz sub-channels.

[0212] 17 depicts an EHT-SIG-B field 1700 according to the third embodiment or the fourth embodiment. The EHT-SIG-B field 1700 includes (or is composed of) a common field 1702 (if present), followed by a user-specific field 1704, which are collectively referred to as an EHT-SIG-B content channel.

[0213] The common field 1702 includes a RU allocation subfield 1706, a center 26-frequency-tuned RU subfield 1707, and a PA bitmap subfield 1708. The RU allocation subfield 1706 indicates RU information for each of the allocations including downlink user-specific PAs. The RU information includes the RU location in the frequency domain, an indication of the RU allocated to a non-MU-MIMO or MU-MIMO allocation, and the number of users in the MU-MIMO allocation.

[0214] The RU allocation subfield 1706 includes N fields, and the value of N depends on the values ​​of CBW and L. For various embodiments, for CBW=20MHz, N can only be 1. For CBW=40MHz, when L=1, N=1, and when L=2, N=2. Regardless of the value of L, for CBW=80MHz, N=2, and for CBW=160MHz or 80+80MHz, N=4, and for CBW=320MHz or 160+160MHz, N=8. Each of the N fields of the RU allocation subfield 1706 includes 8 bits of signaling to indicate the RU allocation within the corresponding frequency range. For example, when L=1 and CBW=80MHz, for EHT-SIG-B content channel 1, for the first field and the second field of the RU allocation subfield 1706, the corresponding frequency ranges are [-500:-259] and [17:258], respectively. For EHT-SIG-B content channel 2, for the first field and the second field of the RU allocation subfield 1706, the corresponding frequency modulation ranges are [-258:17] and [259:500], respectively.

[0215] In another example, when L=2 and CBW=80 MHz, for EHT-SIG-B content channel 1, the corresponding frequency ranges for the first field and the second field of the RU allocation subfield 1706 are [-500:-259] and [-258:17], respectively. For EHT-SIG-B content channel 2, the corresponding frequency ranges for the first field and the second field of the RU allocation subfield 1706 are [17:258] and [259:500], respectively. If a single RU of an 80 MHz PPDU overlaps with more than one frequency range [-500:-259], [-258:-17], [17:258], and [259:500], the allocation may be indicated by only one of the N fields of the RU allocation subfield in a single EHT-SIG-B content channel corresponding to one of the frequency ranges with which the RU overlaps in order to minimize EHT-SIG-B overhead.

[0216] The center 26-frequency-tuned RU subfield 1707 includes M bits, and the value of M depends on the CBW. Since the center 26-frequency-tuned RU subfield 1707 exists when the CBW is 80 MHz and above, M=0 when the CBW is 20 MHz or 40 MHz. When the CBW is 80 MHz, 80+80 MHz, or 160 MHz, M=1. When the CBW is 80 MHz, the center 26-frequency-tuned RU subfield 1707 in both EHT-SIG-B content channel 1 and EHT-SIG-B content channel 2 indicates whether the user is assigned to the center 26-frequency-tuned RU. When the CBW is 80+80 or 160 MHz, the center 26-tone RU subfield 1707 in the EHT-SIG-B content channel 1 indicates whether the user is assigned to the center 26-tone RU of the lower frequency 80 MHz; and the center 26-tone RU subfield 1707 in the EHT-SIG-B content channel 2 indicates whether the user is assigned to the center 26-tone RU of the higher frequency 80 MHz.

[0217] When the CBW is 160+160MHz or 320MHz, M=2. The first bit of the Center 26-Tone RU subfield 1707 in the EHT-SIG-B content channel 1 indicates whether the user is assigned to the Center 26-Tone RU of the lower frequency 80MHz within the lower frequency of 160MHz; and the first bit of the Center 26-Tone RU subfield 1707 in the EHT-SIG-B content channel 2 indicates whether the user is assigned to the Center 26-Tone RU of the higher frequency 80MHz within the lower frequency 160MHz. The second bit of the Center 26-Tone RU subfield 1707 in the EHT-SIG-B content channel 1 indicates whether the user is assigned to the Center 26-Tone RU of the lower frequency 80MHz within the higher frequency of 160MHz; and the second bit of the Center 26-Tone RU subfield 1707 in the EHT-SIG-B content channel 2 indicates whether the user is assigned to the Center 26-Tone RU of the higher frequency 80MHz within the higher frequency 160MHz.

[0218] The PA Bitmap subfield 1708 indicates whether each user-specific allocation specified by the RU Allocation subfield 1706 and the Center 26-Tone RU subfield 1707 (if applicable) is persistent. A bit of the PA Bitmap subfield 1708 is set to 1 to indicate that the user-specific allocation corresponding to the bit is persistent. A bit of the PA Bitmap subfield 1708 is set to 0 to indicate that the user-specific allocation corresponding to the bit is not persistent.

[0219] The PA bitmap subfield 1708 includes N bitmaps, which respectively correspond to the N fields of the RU allocation subfield 1706 in the same EHT-SIG-B content channel. As described above, when CBW=80, 80+80, or 160 MHz, the 1-bit center 26-tone RU subfield 1707 is present in the common field 1702. Fig.16A As shown, for CBW=80 MHz, the last bitmap (ie, the second bitmap) in the PA bitmap subfield 1708 indicates whether the user-specific allocation indicated by the Center 26-Tone RU subfield 1707 is persistent.

[0220] The EHT-SIG-A field may include a PA presence subfield for each EHT-SIG-B content channel. The PA presence subfield of the EHT-SIG-B content channel includes an N-bit bitmap, where the nth (n=1, 2, ..., N) bit indicates the presence of the nth bitmap of the PA bitmap subfield in the EHT-SIG-B content channel. The nth bit of the PA presence subfield in the EHT-SIG-A field is set to 0 to indicate that the nth bit of the PA bitmap subfield 1708 is not present in the EHT-SIG-B content channel; and is set to 1 to indicate that the nth bitmap of the PA bitmap subfield 1708 is present in the EHT-SIG-B content channel. Fig.18A As shown in Figure 1820, for CBW = 80MHz, the first bit and the second bit of the PA Presence subfield of the EHT-SIG-A field are set to 1 to indicate the presence of the first bitmap and the second bitmap of the PA Bitmap subfield 1708 in the EHT-SIG-B content channel. To minimize common field overhead, if all user-specific allocations indicated by the corresponding fields of the RU Allocation subfield 1706 and the Center 26-Tone RU subfield 1707 (if applicable) are not persistent, the bitmap of the PA Bitmap subfield 1708 may not be present.

[0221] When CBW=80+80 or 160 MHz, the last bitmap (i.e., the 4th bitmap) of the PA bitmap subfield 1708 in the EHT-SIG-B content channel also indicates whether the user-specific allocation indicated by the 1-bit center 26-frequency modulation RU subfield 1707 is persistent, as shown in FIG. Fig.18B 1840. Bits 1, 2, 3, and 4 of the PA Presence subfield of the EHT-SIG-A field are set to 1 to indicate that bitmaps 1, 2, 3, and 4 of the PA Bitmap subfield 1708 are present in the EHT-SIG-B content channel. If all user-specific allocations indicated by the corresponding fields of the RU Allocation subfield 1706 and the Center 26-Tone RU subfield 1707 (if applicable) are not persistent, then the bitmap of the PA Bitmap subfield 1708 is not present.

[0222] As described above, when CBW = 160 + 160 or 320 MHz, the 2-bit center 26-frequency-tone RU subfield 1707 is present in the common field 1702. In this case, the fourth bitmap of the PA bitmap subfield 1708 also indicates whether the user-specific allocation indicated by the first bit of the center 26-frequency-tone RU subfield 1707 is persistent, and the last bitmap of the PA bitmap subfield 1708 also indicates whether the user-specific allocation indicated by the second bit of the center 26-frequency-tone RU subfield 1707 is persistent. In order to minimize the common field overhead, if all user-specific allocations indicated by the corresponding fields of the RU allocation subfield 1706 and the corresponding bits of the center 26-frequency-tone RU subfield 1707 (if applicable) are not persistent, the bitmap of the PA bitmap subfield 1708 may not exist.

[0223] In the case of full bandwidth MU-MIMO transmission, the common field 1702 may not be present. In this case, the RU information for the MU-MIMO allocation (e.g., the number of users in the MU-MIMO allocation) may be signaled in the EHT-SIG-A field. Whether each of the user-specific allocations for the MU-MIMO allocation is persistent may also be signaled in the EHT-SIG-A field.

[0224] Fig.19A A first example of a coding structure of a common field 1702 according to the third embodiment or the fourth embodiment is depicted. As described above, the common field 1702 includes a RU allocation subfield 1706, a center 26-frequency-tuned RU subfield 1707, and a PA bitmap subfield 1708. In the first example, all subfields of the common field 1702 are jointly encoded. As described above, each of the N fields of the RU allocation subfield 1706 is 8-bit signaling, so the RU allocation subfield 1706 has N×17 bits, where N=1, 2, 4, or 8. The center 26-frequency-tuned RU subfield 1707 has M bits, where M=0, 1, or 2. Each of the N fields of the RU allocation subfield 1706 can indicate up to seventeen user-specific allocations. Therefore, in the first example, each of the PA bitmap subfields 1708 has a size of (N×17+M) bits.

[0225] The common field 1702 has a CRC (Cyclic Redundancy Check) subfield 1722 and a Tail subfield 1724 additionally used for BCC encoding / decoding purposes. The size of the CRC subfield 1722 is 4 bits, and the size of the tail subfield 1724 is 6 bits. That is, the size of the common field 1702 is the sum of the sizes of the RU allocation subfield 1706, the center 26-frequency-tuned RU subfield 1707, the PA bitmap subfield 1708, the CRC subfield 1722, and the tail subfield 1724. Therefore, in the first example, the size of the common field 1702 can be determined after decoding the EHT-SIG-A field because the values ​​of N and M can be derived from the values ​​of CBW and L indicated in the EHT-SIG-A field.

[0226] Fig.19B A second example of the coding structure of the common field 1702 according to the third embodiment or the fourth embodiment is depicted. The common field 1702 is divided into two common block fields, i.e., a first common block field 1710a and a second common block field 1710b, which are encoded separately. The first common block field 1710a includes an RU allocation subfield 1706 and a center 26-frequency modulation RU subfield 1707. The size of the first common block field 1710a can be derived after decoding the EHT-SIG-A field, because the values ​​of N and M can be derived from the values ​​of CBW and L indicated in the EHT-SIG-A field. The first common block field 1702a also includes a 4-bit CRC field 1722a and a 6-bit tail field 1724a for BCC encoding / decoding purposes. The second common block field 1702b includes a PA bitmap subfield 1708. The second common block field 1710b also includes a 4-bit CRC field 1722b and a 6-bit tail field 1724b for BCC encoding / decoding purposes.

[0227] In the second example, the size of the PA bitmap subfield 1708 is ( bits), where L n is equal to the number of user-specific allocations indicated by the nth field of the RU allocation subfield 1706. The size of the second common block field 1710b may be determined after the first common block field 1710a is decoded.

[0228] and Fig.19A Compared to the first example shown, Fig.19B The second example shown has a higher implementation complexity in terms of decoding of the common field 1702. Therefore, if the first example and the second example have the same common field overhead, the first example is preferred.

[0229] like Fig.19A and Fig.19BAs shown, in contrast, if Then the second example has less public field overhead than the first example. It can be observed that:

[0230] When N=1, if L1<7, the second example may be better. Otherwise, the first example is better;

[0231] When N = 2, if Then the second example is probably better. Otherwise the first example is better;

[0232] When N = 4, if then the second example is probably better. Otherwise the first example is better; and

[0233] When N = 8, if Then the second example may be better. Otherwise the first example is better.

[0234] Obviously, whether the first example or the second example is used for the common field of the EHT MU PPDU should be determined by the AP depending on the CBW and RU allocation of the EHT MU PPDU. As a result, it is beneficial to add 1 bit of signaling in the EHT-SIG-A field of the EHT MU PPDU for each EHT-SIG-B content channel to indicate whether the first example or the second example is used for the corresponding EHT-SIG-B content channel.

[0235] In FIG. 17 , the user-specific field 1704 includes (or is composed of) one or more user fields for (multiple) non-MU-MIMO allocations and / or (multiple) MU-MIMO allocations, for example, user field 0 (1710), user field 1 (1712), user field 2 (1714), user field 3 (1716), and user field 4 (1718).

[0236] The user field contains user information indicating a user-specific allocation (i.e., user-specific allocation information). For non-MU-MIMO allocation, the number of spatial streams (NSTS), transmit beamforming (Tx BF) information, MCS, DCM information, and error control codec information may be included. For MU-MIMO allocation, NSTS, starting spatial stream, MCS, and error control codec information may be included. One user field may be addressed to a STA (similar to the HE MU PPDU, in the EHT MU PPDU, a STA can only be addressed by a single user field. As a result, when a STA receives an EHT MU PPDU, once it recognizes its own user field, it will stop parsing the user-specific field). For example, user field 0 (1710) may provide user-specific allocation information for allocation 0. For example, user field 1 (1712), user field 2 (1714), and user field 3 (1716) may provide user-specific allocation information for allocation 1 with 3 MU-MIMO users. For example, user field 4 (1718) may provide user-specific allocation information for allocation 2.

[0237] Fig.19C Describes the basis Figure 3B A first example of the coding structure of the common field 502 of the illustrated embodiment. As described above, the common field 1702 includes a RU allocation subfield 1706, a center 26-frequency-tuned RU subfield 1707, and a PA bitmap subfield 1708. In the first example, all subfields of the common field 1702 are jointly encoded. As described above, each of the N fields of the RU allocation subfield 1706 is 8-bit signaling, so the RU allocation subfield 1706 has N×17 bits, where N=1, 2, 4, or 8. The center 26-frequency-tuned RU subfield 1707 has M bits, where M=0, 1, or 2. Each of the N fields of the RU allocation subfield 1706 can indicate up to seventeen user-specific allocations. Therefore, in the first example, each of the PA bitmap subfields 1708 has a size of (N×9+M) bits.

[0238] The common field 1702 has a CRC (Cyclic Redundancy Check) subfield 1722 and a tail subfield 1724 additionally used for BCC encoding / decoding purposes. The size of the CRC subfield 1722 is 4 bits, and the size of the tail subfield 1724 is 6 bits. That is, the size of the common field 1702 is the sum of the sizes of the RU allocation subfield 1706, the center 26-frequency-tuned RU subfield 1707, the PA bitmap subfield 1708, the CRC subfield 1722, and the tail subfield 1724. Therefore, in the first example, the size of the common field 1702 can be determined after decoding the EHT-SIG-A field because the values ​​of N and M can be derived from the values ​​of CBW and L indicated in the EHT-SIG-A field.

[0239] Fig.19D Describes the basis Figure 3B A second example of the coding structure of the common field 502 of the illustrated embodiment. The common field 1702 is divided into two common block fields, namely, a first common block field 1710a and a second common block field 1710b, which are encoded separately. The first common block field 1710a includes an RU allocation subfield 1706 and a center 26-frequency modulation RU subfield 1707. The size of the first common block field 1710a can be derived after decoding the EHT-SIG-A field, because the values ​​of N and M can be derived from the values ​​of CBW and L indicated in the EHT-SIG-A field. The first common block field 1702a also includes a 4-bit CRC field 1722a and a 6-bit tail field 1724a for BCC encoding / decoding purposes. The second common block field 1702b includes a PA bitmap subfield 1708. The second common block field 1710b also includes a 4-bit CRC field 1722b and a 6-bit tail field 1724b for BCC encoding / decoding purposes.

[0240] In the second example, each of the persistent allocation bitmap subfield 508 and the cyclic transmission bitmap subfield 509 has ( bits), where L n is equal to the number of allocations indicated by the nth field of the RU allocation subfield 506. The size of the second common block field 502b may be determined after the first common block field 502a is decoded.

[0241] and Fig.19C Compared to the first example shown, Fig.19D The second example shown has a higher implementation complexity in terms of decoding of the common field 1702. Therefore, if the first example and the second example have the same common field overhead, the first example is preferred.

[0242] like Fig.19C and Fig.19DAs shown, in contrast, if Then the second example has less public field overhead than the first example. It can be observed that:

[0243] When N=1, if L1<4, the second example may be better. Otherwise, the first example is better;

[0244] When N = 2, if Then the second example is probably better. Otherwise the first example is better;

[0245] When N = 4, if then the second example is probably better. Otherwise the first example is better; and

[0246] When N = 8, if Then the second example may be better. Otherwise the first example is better.

[0247] Advantageously, there is no user(s) field containing cyclically transmitted downlink persistent allocations, which may reduce overhead.

[0248] Fig.19E Describes the basis Figure 3C A first example of the coding structure of the common field 1702 of the illustrated embodiment. As described above, the common field 1702 includes a RU allocation subfield 1706, a center 26-frequency-tuned RU subfield 1707, and a PA bitmap subfield 1708. In the first example, all subfields of the common field 1702 are jointly encoded. As described above, each of the N fields of the RU allocation subfield 1706 is 8-bit signaling, so the RU allocation subfield 1706 has N×8 bits, where N=1, 2, 4, or 8. The center 26-frequency-tuned RU subfield 1707 has M bits, where M=0, 1, or 2. Each of the N fields of RU allocation.

[0249] The common field 1702 has a CRC (Cyclic Redundancy Check) subfield 1722 and a tail subfield 1724 additionally used for BCC encoding / decoding purposes. The size of the CRC subfield 1722 is 4 bits, and the size of the tail subfield 1724 is 6 bits. That is, the size of the common field 1702 is the sum of the sizes of the RU allocation subfield 1706, the center 26-frequency-tuned RU subfield 1707, the PA bitmap subfield 1708, the CRC subfield 1722, and the tail subfield 1724. Therefore, in the first example, the size of the common field 1702 can be determined after decoding the EHT-SIG-A field because the values ​​of N and M can be derived from the values ​​of CBW and L indicated in the EHT-SIG-A field.

[0250] Fig.19E Describes the basis Figure 3CA second example of the coding structure of the common field 1702 of the illustrated embodiment. The common field 1702 is divided into two common block fields, namely, a first common block field 1710a and a second common block field 1710b, which are encoded separately. The first common block field 1710a includes an RU allocation subfield 1706 and a center 26-frequency modulation RU subfield 1707. The size of the first common block field 1710a can be derived after decoding the EHT-SIG-A field, because the values ​​of N and M can be derived from the values ​​of CBW and L indicated in the EHT-SIG-A field. The first common block field 1702a also includes a 4-bit CRC field 1722a and a 6-bit tail field 1724a for BCC encoding / decoding purposes. The second common block field 1702b includes a PA bitmap subfield 1708. The second common block field 1710b also includes a 4-bit CRC field 1722b and a 6-bit tail field 1724b for BCC encoding / decoding purposes.

[0251] In the second example, the size of the PA bitmap subfield 1708 is ( bits), where L n is equal to the number of allocations indicated by the nth field of the RU allocation subfield 1706. The size of the second common block field 1710b may be determined after the first common block field 1710a is decoded.

[0252] and Fig.19E Compared to the first example shown, Fig.19F The second example shown has a higher implementation complexity in terms of decoding of the common field 1702. Therefore, if the first example and the second example have the same common field overhead, the first example is preferred.

[0253] like Fig.19E and Fig.19F As shown, in contrast, if Then the second example has less public field overhead than the first. It can be observed that:

[0254] When N=1, the first example is better;

[0255] When N = 2, if Then the second example is probably better. Otherwise the first example is better;

[0256] When N = 4, if then the second example is probably better. Otherwise the first example is better; and

[0257] When N = 8, if Then the second example may be better. Otherwise the first example is better.

[0258] Obviously, whether the first example or the second example is used for the common field of the EHT MU PPDU should be determined by the AP depending on the CBW and RU allocation of the EHT MU PPDU. As a result, it is beneficial to add 1 bit of signaling in the EHT-SIG-A field of the EHT MU PPDU for each EHT-SIG-B content channel to indicate whether the first example or the second example is used for the corresponding EHT-SIG-B content channel.

[0259] In FIG. 17 , the user-specific field 1704 includes (or is composed of) one or more user fields for (multiple) non-MU-MIMO allocations and / or (multiple) MU-MIMO allocations, for example, user field 0 (1710), user field 1 (1712), user field 2 (1714), user field 3 (1716), and user field 4 (1718).

[0260] The user field contains user information indicating a user-specific allocation (i.e., user-specific allocation information). For non-MU-MIMO allocations, the number of spatial streams (NSTS), transmit beamforming (Tx BF) information, modulation and coding scheme (MCS), dual carrier modulation (DCM) information, and error control coding information may be included. For MU-MIMO allocations, NSTS, starting spatial stream, MCS, and error control coding information may be included. One user field may be addressed to a STA (similar to the HE MU PPDU, in the EHT MU PPDU, a STA can only be addressed by a single user field. As a result, when a STA receives an EHT MU PPDU, once it recognizes its own user field, it will stop parsing the user-specific field). For example, user field 0 (1710) may provide user-specific allocation information for allocation 0. For example, user field 1 (1712), user field 2 (1714), and user field 3 (1716) may provide user-specific allocation information for allocation 1 with 3 MU-MIMO users. For example, user field 4 (1718) may provide user-specific allocation information for allocation 2.

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

[0262]

[0263] Table 1

[0264]

[0265]

[0266] Table 2

[0267] If the RU information and / or user-specific allocation information for its own persistent allocation is not here, the STA may not be able to correctly receive the cyclic transmission of the persistent allocation. In this way, for the purpose of error recovery, according to an embodiment, advantageously, an example rule may be that at least one MPDU (MAC (Media Access Control) Protocol Data Unit) that needs to be confirmed may be included in the initial transmission of the persistent allocation. If the AP does not receive a positive confirmation of the initial transmission of the persistent allocation from the STA, it knows that the RU information and / or user-specific allocation information for the persistent allocation may not exist at the STA, and then the AP may not schedule the cyclic transmission of the persistent allocation.

[0268] According to the third embodiment or the fourth embodiment, the user field of the downlink user-specific PA does not exist in the user-specific field, which can reduce overhead.

[0269] Fig. 20A A diagram 2000 showing the reduction of user-specific field overhead for the third to fourth embodiments is shown. The PA bitmap subfield 2002 is provided as 00101. User field 0 (2006) of the user-specific field provides non-MU-MIMO allocation 0, which is not persistent (according to the first bit in the PA bitmap subfield 2002 being 0), and therefore, user field 0 (2006) is provided in the user-specific field. User field 1 (2008), user field 2 (2010), and user field 3 (2012) provide three user-specific allocations of MU-MIMO allocation 1. The first user-specific allocation of MU-MIMO allocation 1 is not persistent (according to the second bit in the PA bitmap subfield 2002 being 0), and therefore, user field 1 (2008) is provided in the user-specific field. The second user-specific allocation of MU-MIMO allocation 1 is persistent (according to the third bit in the PA bitmap subfield 2002 being 1), and therefore, User Field 2 (2010) is not provided in the User Specific Field. The third user-specific allocation of MU-MIMO allocation 1 is not persistent (according to the fourth bit in the PA bitmap subfield 2002 being 0), and therefore, User Field 3 (2012) is provided in the User Specific Field. User Field 4 (2014) of the User Specific Field provides a non-MU-MIMO allocation 2, which is persistent (according to the fifth bit in the PA bitmap subfield 2002 being 1), and therefore, User Field 4 (2014) is not provided in the User Specific Field, which advantageously reduces overhead.

[0270] Fig. 20BA diagram 2200 showing the reduction of user specific field overhead for the third embodiment to the fourth embodiment is shown. The PA bitmap subfield 2002 is provided as 001. User field 0 (2006) of the user specific field provides allocation 0, which is not persistent (according to the first bit in the PA bitmap subfield 2002 being 0), and therefore, user field 0 (2006) is provided in the user specific field. User field 1 (2008), user field 2 (2010), and user field 3 (2012) provide allocation 1 with 3 MIMO users, which is not persistent (according to the second bit in the PA bitmap subfield 2002 being 0), and therefore, user field 1 (2008), user field 2 (2010), and user field 3 (2012) are provided in the user specific field. The third bit in the PA bitmap subfield 2002 is 1, so allocation 2 is PA, and therefore, user field 4 (2014) is not provided in the user specific field, which advantageously reduces overhead.

[0271] Fig. 20C A diagram 2050 of reduced user specific field overhead in another example of the first to fourth embodiments is shown. The PA bitmap subfield 2052 is provided as 010. User field 0 (2056) of the user specific field provides allocation 0, which is not persistent (according to the first bit in the PA bitmap field 2052 is 0), and therefore, user field 0 (2056) is provided in the user specific field. User field 1 (2058), user field 2 (2060), and user field 3 (2062) provide allocation 1 with 3 MIMO users, which is persistent (according to the second bit in the PA bitmap subfield 2052 is 1), so user field 1 (2058), user field 2 (2060), and user field 3 (2062) are not provided in the user specific field, which advantageously reduces overhead. The third bit in the PA bitmap subfield 2052 is 0, so allocation 2 is PA, and therefore, user field 4 (2064) is provided in the user specific field.

[0272] Fig.21A flowchart 2100 is shown showing processing of a received EHT MUPPDU at a STA according to the third embodiment or the fourth embodiment. Processing may start at 2102. At 2104, the EHT-SIG-A field and the EHT-SIG-B field of the received EHT MUPPDU may be demodulated and decoded. At 2106, the allocated (multiple) RUs may be determined; this may be done by checking the RU allocation subfield and the center 26-tone subfield (if present) of the EHT-SIG-B field. In the case of full-bandwidth MU-MIMO transmission, this step may be skipped. At 2108, the number of user fields in the user-specific field may be calculated; the PA presence subfield of the EHT-SIG-A field and the PA bitmap subfield of the EHT-SIG-B field may be considered to exclude user fields corresponding to downlink user-specific PAs. At 2110, the user field counter may be initialized to 0 (zero). At 2112, it may be determined whether the STA ID of the STA matches the value of the STA-ID subfield. If the STAID of the STA matches the value of the STA-ID subfield, the process may proceed to step 2116. If the STAID of the STA does not match the value of the STA-ID subfield, the process may proceed to step 2122. At 2116, user-specific allocation information may be obtained. At 2120, a corresponding allocated transmission may be received in the data field. At 2122, the user field counter may be increased by 1. At 2124, it may be determined whether the user field counter is equal to the number of user fields in the user-specific field. If it is determined that the user field counter is equal to the number of user fields in the user-specific field, the process may proceed to step 2126. If it is determined that the user field counter is not equal to the number of user fields in the user-specific field, the process may return to step 2112. At 2126, it may be determined whether any timer of the downlink user-specific PA is running. If it is determined that at least one timer for the downlink user-specific PA is running, the process may proceed to step 2128. If it is determined that no timer of the downlink user-specific PA is running, the process may end at step 2132. At 2128, it may be determined whether any of the allocated RUs for the downlink user-specific PAs matches the stored RU information for the downlink user-specific PAs with a running timer; the allocated RUs for the downlink user-specific PAs may be determined by checking the PA presence subfield of the EHT-SIG-A field and the PA bitmap subfield of the EHT-SIG-B field. If it is determined that one of the allocated RUs for the downlink user-specific PAs matches the stored RU information for the downlink user-specific PAs with a running timer, processing may proceed at step 2130.If it is determined that no allocated RU for the downlink user-specific PA matches the stored RU information of any downlink user-specific PA with a running timer, the process may end at 2132. At step 2130, the latest stored user-specific allocation information of the matching RU is retrieved, and the process proceeds at step 2120. At 2132, the process ends.

[0273] Fig. 22 A flow chart illustrating communication between a STA 2204 and an AP 2202 utilizing a downlink user-specific PA according to a fifth embodiment is depicted. Box 2206 illustrates a contention-based channel access process and illustrates SIFS 2208. The AP 2202 may send an EHT MU PPDU 2210, which may include an initial transmission of a downlink user-specific PA for the STA and may include corresponding RU information and user-specific allocation information. The AP 2202 may then send an EHT MU PPDU 2214, which may include a cyclic transmission of a downlink user-specific PA for the STA and may include corresponding RU information, but not corresponding user-specific allocation information. At 2216, the STA 2204 may receive the initial transmission of the downlink user-specific PA and store the RU information and user-specific allocation information for the downlink user-specific PA. The STA 2204 may then send a BlockAck frame 2218. At 2220 , STA 2204 may receive cyclic transmission of the downlink user-specific PA using the stored RU information and user-specific allocation information of the downlink user-specific PA. Then, STA 2204 may send a BlockAck frame 2222 .

[0274] Fig.23 An EHT-SIG-B field 2300 according to a fifth embodiment is depicted. The EHT-SIG-B field 2300 includes (or consists of) a common field 2302 (if present) followed by a user-specific field 2304, which are collectively referred to as the EHT-SIG-B content channel.

[0275] The common field 2302 includes a RU allocation subfield 2306, a center 26-tone RU subfield 2307, a PA bitmap subfield 2308, and a cyclic transmission bitmap subfield 2309. The RU allocation subfield 2306 indicates RU information for each of the user-specific allocations including a downlink user-specific PA.

[0276] The PA bitmap subfield 2308 of the common field 2302 is the same as the PA bitmap subfield 1708 of the common field 1702, as shown in Figure 17. The EHT-SIG-A field may include a PA bitmap present subfield for each EHT-SIG-B content channel.

[0277] The cyclic transmission bitmap subfield 2309 indicates whether each of the user-specific allocations specified by the RU allocation subfield 2306 contains an initial transmission or a cyclic transmission. One bit of the cyclic transmission bitmap subfield 2309 is set to 0 to indicate that the user-specific allocation corresponding to the bit contains an initial transmission. The initial transmission refers to the transmission of a non-user-specific PA or the initial transmission of a user-specific PA. If the user-specific allocation corresponding to the bit is not persistent, the bit of the cyclic transmission bitmap subfield 2309 is set to 0. The bit of the cyclic transmission bitmap subfield 2309 is set to 1 to indicate that the user-specific allocation corresponding to the bit contains a cyclic transmission. When the bit of the cyclic transmission bitmap subfield 2309 is set to 1, the user field of the user-specific allocation corresponding to the bit does not exist in the user-specific field 2304.

[0278] The cyclic transmission bitmap subfield 2309 includes N bitmaps, which respectively correspond to the N fields of the RU allocation subfield in the same EHT-SIG-B content channel. When CBW=80, 80+80 or 160MHz, the last bitmap of the cyclic transmission bitmap subfield 2309 also indicates whether the user-specific allocation indicated by the 1-bit center 26-frequency modulation RU subfield 2307 includes cyclic transmission. When CBW=160+160 or 320MHz, the fourth bitmap of the cyclic transmission bitmap subfield 2309 also indicates whether the user-specific allocation indicated by the first bit of the 2-bit center 26-frequency modulation RU subfield 2307 includes cyclic transmission, and the last bitmap of the cyclic transmission bitmap subfield 2309 also indicates whether the user-specific allocation indicated by the second bit of the 2-bit center 26-frequency modulation RU subfield 2307 includes cyclic transmission. If all user-specific allocations specified by the corresponding fields of the RU Allocations subfield 2306 and the corresponding bits of the Center 26-Tune RU subfield 2307 (if applicable) do not include cyclic transmissions, then the bitmap of the cyclic transmission bitmap subfield 2309 is not present.

[0279] like Fig.18A and Fig.18B As shown, the cyclic transmission bitmap subfield 2309 is mapped to the RU allocation subfield 2306 and the center 26-frequency modulation RU subfield 2307 in the same manner as the PA bitmap subfield 2308.

[0280] Alternatively, an initial transmission bitmap subfield may be provided, for example, in the common field 2302, which indicates whether each of the user-specific allocations specified by the RU allocation subfield 2306 contains an initial transmission or a cyclic transmission. A bit is set to 1 to indicate that the user-specific allocation corresponding to the bit contains an initial transmission. A bit is set to 0 to indicate that the user-specific allocation corresponding to the bit contains a cyclic transmission.

[0281] The EHT-SIG-A field may include a cyclic transmission presence subfield for each EHT-SIG-B content channel. The cyclic transmission presence subfield of the EHT-SIG-B content channel includes an N-bit bitmap, wherein the nth (n=1, 2, ..., N) bit indicates the presence of the nth bitmap of the cyclic transmission bitmap subfield 2309 in the EHT-SIG-B content channel. The nth bit of the cyclic transmission presence subfield in the EHT-SIG-A field is set to 0 to indicate that the nth bitmap of the cyclic transmission bitmap subfield 2309 does not exist in the EHT-SIG-B content channel; and is set to 1 to indicate that the nth bitmap of the cyclic transmission bitmap subfield 2309 exists in the EHT-SIG-B content channel. When the nth bit of the persistent allocation presence subfield of the EHT-SIG-A field is set to 0, the nth bit of the cyclic transmission presence subfield in the same EHT-SIG-B content channel will also be set to 0 (that is, the nth bitmap of the cyclic transmission bitmap subfield 2309 does not exist in the same EHT-SIG-B content channel).

[0282] In the case of full-bandwidth MU-MIMO transmission, the common field 2302 may not be present. In this case, the RU information of the MU-MIMO allocation (e.g., the number of users in the MU-MIMO allocation) may be signaled in the EHT-SIG-A field. In addition, whether each of the user-specific allocations of the MU-MIMO allocation is persistent may be signaled in the EHT-SIG-A field; and whether each of the user-specific allocations in the MU-MIMO allocation contains a cyclic transmission may also be signaled in the EHT-SIG-A field.

[0283] Fig.24A A first example of the encoding structure of the common field 2302 according to the fifth embodiment is depicted. Fig.23As mentioned in the specification, the common field 2302 includes a RU allocation subfield 2306, a center 26-frequency modulation RU subfield 2307, a PA bitmap subfield 2308, and a cyclic transmission bitmap subfield 2309. In the first example, all subfields of the common field 2302 are jointly encoded. As described above, each of the N fields of the RU allocation subfield 2306 is 8-bit signaling, so the RU allocation subfield 2306 has N×8 bits, where N=1, 2, 4, or 8. The center 26-frequency modulation RU subfield 2307 has M bits, where M=0, 1, or 2. Each of the N fields of the RU allocation subfield 2306 can indicate a maximum of seventeen allocations. Therefore, in the first example, each of the PA bitmap subfield 2308 or the cyclic transmission bitmap subfield 2309 has a size of (N×17+M) bits.

[0284] The common field 2302 has a CRC subfield 2322 and a tail subfield 2324 additionally used for BCC encoding / decoding purposes. The size of the CRC subfield 2322 is 4 bits, and the size of the tail subfield 2324 is 6 bits. That is, the size of the common field 2302 is the sum of the sizes of the RU allocation subfield 2306, the center 26-frequency-tuned RU subfield 2307, the PA bitmap subfield 2308, the cyclic transmission bitmap subfield 2309, the CRC subfield 2322, and the tail subfield 2324. Therefore, in the first example, the size of the common field 2302 can be determined after decoding the EHT-SIG-A field because the values ​​of N and M can be derived from the values ​​of CBW and L indicated in the EHT-SIG-A field.

[0285] Fig. 24B A second example of the coding structure of the common field 2302 according to the fifth embodiment is depicted. The common field 2302 is divided into two common block fields, i.e., a first common block field 2320a and a second common block field 2320b, which are encoded separately. The first common block field 2320a includes an RU allocation subfield 2306 and a center 26-frequency modulation RU subfield 2307. The size of the first common block field 2320a can be derived after decoding the EHT-SIG-A field, because the values ​​of N and M can be derived from the values ​​of CBW and L indicated in the EHT-SIG-A field. The first common block field 2320a also includes a 4-bit CRC field 2322a and a 6-bit tail field 2324a for BCC encoding / decoding purposes. The second common block field 2320b includes a PA bitmap subfield 2308 and a cyclic transmission bitmap subfield 2309. The second common block field 2320b also includes a 4-bit CRC field 2322b and a 6-bit tail field 2324b for BCC encoding / decoding purposes.

[0286] In the second example, each of the PA bitmap subfield 2308 and the cyclic transmission bitmap subfield 2309 has ( bits), where L n is equal to the number of user-specific allocations indicated by the nth field of the RU allocation subfield 2306. The size of the second common block field 2320b may be determined after the first common block field 2320a is decoded.

[0287] and Fig.24A Compared to the first example shown, Fig. 24B The second example shown has a higher implementation complexity in terms of decoding of the common field 2302. Thus, if the first example and the second example have the same common field overhead, the first example is preferred.

[0288] like Fig.24A and Fig. 24B As shown, in contrast, if Then the second example has less public field overhead than the first example. It can be observed that:

[0289] When N=1, if L1<12, the second example may be better. Otherwise, the first example is better;

[0290] When N = 2, if Then the second example is probably better. Otherwise the first example is better;

[0291] When N = 4, if then the second example is probably better. Otherwise the first example is better; and

[0292] When N = 8, if Then the second example may be better. Otherwise the first example is better.

[0293] Obviously, whether the first example or the second example is used for the common field of the EHT MU PPDU should be determined by the AP depending on the CBW and RU allocation of the EHT MU PPDU. As a result, it is beneficial to add 1 bit of signaling in the EHT-SIG-A field of the EHT MU PPDU for each EHT-SIG-B content channel to indicate whether the first example or the second example is used for the corresponding EHT-SIG-B content channel.

[0294] The user-specific field 2304 includes (or is composed of) one or more user fields for (multiple) non-MU-MIMO allocations and / or (multiple) MU-MIMO allocations. The user fields of the user-specific field 2304 are the same as the user fields of the user-specific field 1704, as shown in Figure 17.

[0295] When receiving an EHT MUPPDU containing the initial transmission of a downlink user-specific PA with the STA as the intended recipient, the STA may start or reset the timer of the downlink user-specific PA and store or update the RU information and user-specific allocation information of the downlink user-specific PA.

[0296] If the RU information and / or user-specific allocation information of the downlink user-specific PA is not present here, the STA may not be able to correctly receive the cyclic transmission of the downlink user-specific PA. In this way, for the purpose of error recovery, according to an embodiment, advantageously, an example rule may be that at least one MPDU that needs to be confirmed may be included in the initial transmission of the downlink user-specific PA. If the AP does not receive a positive confirmation of the initial transmission of the downlink user-specific PA from the STA, it knows that the RU information and / or user-specific allocation information of the downlink user-specific PA may not exist at the STA, and then the AP may not schedule the cyclic transmission of the downlink user-specific PA.

[0297] Fig.25An illustration 2500 of the reduction of user-specific field overhead of the fifth embodiment is shown. The cyclic transmission bitmap subfield 2504 is provided as 00101. User field 0 (2506) of the user-specific field provides non-MU-MIMO allocation 0, which is not persistent (according to the first bit in the PA bitmap subfield 2502 is 0), and therefore, user field 0 (2506) is provided in the user-specific field. User field 1 (2508) provides a first user-specific allocation of MU-MIMO allocation 1, which is persistent (according to the second bit in the PA bitmap subfield 2502 is 1). Since the second bit of the cyclic transmission bitmap subfield 2504 is 0, the transmission of the first user-specific allocation of MU-MIMO allocation 1 is not a cyclic transmission, so user field 1 (2508) is provided in the user-specific field. User field 2 (2510) provides a second user-specific allocation of MU-MIMO allocation 1, which is persistent (according to the third bit in the PA bitmap subfield 2502 is 1). Since the third bit of the cyclic transmission bitmap subfield 2504 is 1, the transmission according to the second user-specific allocation of MU-MIMO allocation 1 is a cyclic transmission, so that user field 2 (2510) is not provided in the user specific field. User field 3 (2512) provides the third user-specific allocation of MU-MIMO allocation 1, which is non-persistent (according to the fourth bit in the PA bitmap subfield 2502 is 0), so user field 3 (2512) is provided in the user specific field. User field 4 (2514) of the user specific field provides non-MU-MIMO allocation 2, which is persistent (according to the fifth bit in the PA bitmap subfield 2502 is 1). Since the fifth bit in the cyclic transmission bitmap subfield 2504 is 1, it indicates that the transmission according to the non-MU-MIMO allocation 2 is a cyclic transmission, so user field 4 (2514) is not provided in the user specific field, which advantageously reduces overhead.

[0298] Fig.26A flowchart 2600 showing processing of a received EHT MU PPDU at a STA according to a fifth embodiment is shown. Processing may start at 2602. At 2604, the EHT-SIG-A field and the EHT-SIG-B field of the received EHT MU PPDU may be demodulated and decoded. At 2606, the allocated (multiple) RUs may be determined; this may be done by checking the RU allocation subfield of the EHT-SIG-B field; in the case of full bandwidth MU-MIMO transmission, this step may be skipped. At 2608, the number of user fields in the user-specific field may be calculated; the cyclic transmission presence subfield of the EHT-SIG-A field and the cyclic transmission bitmap subfield of the EHT-SIG-B field may be considered to exclude user fields corresponding to cyclic transmissions. At 2610, the user field counter may be initialized to 0 (zero). At 2612, it may be determined whether the STAID of the STA matches the value of the STA-ID subfield. The STA ID is an identifier of the STA that uniquely identifies the STA in the BSS (Basic Service Set) associated with it. If the STAID of the STA matches the value of the STA-ID subfield, the process may proceed to step 2614. If the STAID of the STA does not match the value of the STA-ID subfield, the process may proceed to step 2622. At 2614, it may be determined whether the user field corresponds to a downlink user-specific PA; this may be done by checking the PA presence subfield of the EHT-SIG-A field and the PA bitmap subfield of the EHT-SIG-B field. If it is determined that the user field corresponds to a downlink user-specific PA, the process may proceed to step 2616. If it is determined that the user field does not correspond to a downlink user-specific PA, the process may proceed to step 2618. At 2616, user-specific allocation information may be obtained, and RU information and user-specific allocation information may be stored or updated, and a timer for a downlink user-specific PA may be started or reset. At step 2618, user-specific allocation information may be obtained. At 2620, a transmission corresponding to the allocation may be received in the data field. At 2622, the user field counter may be increased by 1. At 2624, it may be determined whether the user field counter is equal to the number of user fields in the user-specific field. If it is determined that the user field counter is equal to the number of user fields in the user specific field, then processing may proceed at step 2626. If it is determined that the user field counter is not equal to the number of user fields in the user specific field, then processing may return to step 2612. At 2626, it may be determined whether any timer for the downlink user specific PA is running. If it is determined that at least one timer for the downlink user specific PA is running, then processing may proceed at step 2628. If it is determined that no timer for the downlink user specific PA is running, then processing may end at step 2632.At 2628, it may be determined whether any allocated (multiple) RUs for cyclic transmission match the latest stored RU information for any downlink user-specific PA with a running timer; the allocated RUs for cyclic transmission may be determined by checking the cyclic transmission presence subfield of the EHT-SIG-A field and the cyclic transmission bitmap subfield of the EHT-SIG-B field. If one of the allocated (multiple) RUs for cyclic transmission matches the stored RU information for a downlink user-specific PA with a running timer, processing may proceed at step 2630. If it is determined that no allocated (multiple) RUs for cyclic transmission match the stored RU information for any downlink user-specific PA with a running timer, processing may end at 2632. At step 2630, the stored user-specific allocation information for the matching RU is retrieved, and processing proceeds at step 2620.

[0299] Fig. 27 FIG. 2 shows a configuration of a communication device 2700 (eg, an access point (AP)) according to various embodiments. Figure 3A A schematic example of a communication device is shown, Fig. 27 The communication device 2700 in the illustrative example includes at least one radio transmitter 2728, at least one radio receiver 2704, and multiple antennas 2702 (for simplicity, Fig. 27 Only one antenna is depicted in FIG) and circuit 2730. Circuit 2730 may include at least one controller 2712 for software and hardware assistance in performing the tasks that controller 2712 is designed to perform, including controlling communications with a downlink or uplink user-specific PA. Circuit 2730 may also include a receive signal processor 2706 and a transmit signal generator 2720. Controller 2712 may control receive signal processor 2706 and transmit signal generator 2720.

[0300] The receive signal processor 2706 may include a data demodulator and decoder 2710 that may demodulate and decode the data portion of the receive signal. The receive signal processor 2706 may also include a control demodulator and decoder 2708 that may demodulate and decode the control signaling portion of the receive signal (e.g., an EHT TB PPDU or BlockAck frame).

[0301] The controller 2712 may include a control signaling parser 2714 that may analyze the control signaling portion of the received signal. The controller 2712 may also include a scheduler 2716 that may determine RU information and user-specific allocation information for allocation. The scheduler 2716 may include a persistent scheduling circuit that determines RU information and user-specific allocation information associated with a downlink user-specific PA, and identification information and user-specific resource allocation information associated with an uplink user-specific PA.

[0302] The transmit signal generator 2720 may include an MPDU generator 2722, a control signaling generator 2724, and a PPDU generator 2726. The MPDU generator 2722 may generate an MPDU or an A-MPDU (aggregate MPDU), for example, a data frame and a management frame carrying a PA control subfield, an EHT basic trigger frame, a PA trigger frame, or a PA announcement frame. The control signaling generator 2724 may generate a control signaling field (e.g., EHT-SIG-A and EHT-SIG-B fields). The PPDU generator 1826 may generate a PPDU (e.g., an EHTMU PPDU).

[0303] Fig.28 FIG. 2 shows a configuration of a communication device 2800 (eg, a terminal, eg, a station (STA)) according to various embodiments. Figure 3A A schematic example of a communication device is shown, Fig.28 The communication device 2800 in the illustrative example includes at least one radio transmitter 2830, at least one radio receiver 2804, and one or more antennas 2802 (for simplicity, Fig.28 Only one antenna is depicted in FIG) and circuitry 2832. Circuitry 2832 may include at least one controller 2812 for software and hardware assistance in performing the tasks that controller 2812 is designed to perform, including controlling communications with a downlink or uplink user-specific PA. Circuitry 2832 may also include a receive signal processor 2806 and a transmit signal generator 2822. Controller 2812 may control receive signal processor 2806 and transmit signal generator 2822.

[0304] The received signal processor 2806 may include a data demodulator and decoder 2810 and a control demodulator and decoder 2808. The data demodulator and decoder 2810 may demodulate and decode the data portion of the received signal based on the RU information and the user-specific allocation information. The data portion of the received signal may include a multi-STA BlockAck acknowledgment frame, a PA announcement frame, an EHT basic trigger frame, a PA trigger frame, or a frame carrying a PA control subfield. The control demodulator and decoder 2808 may demodulate and decode the control signaling portion of the received signal (e.g., the EHT-SIG-A and EHT-SIG-B fields of the EHT MU PPDU).

[0305] The controller 2812 may include a control signaling parser 2814 and a scheduler 2818. The control signaling parser 2814 may analyze the control signaling portion of the received signal and may determine RU information and user-specific allocation information for a downlink user-specific PA. The control signaling parser 2814 may include a PA signaling parser 2816. The PA signaling parser 2816 may determine and store (e.g., in a memory 2820) or update RU information and user-specific allocation information for a downlink user-specific PA, or retrieve (e.g., from the memory 2820) user-specific allocation information for a downlink user-specific PA. The PA signaling parser 2816 may also determine and store (e.g., in a memory 2820) or update identification information and user-specific resource allocation information for an uplink user-specific PA, or retrieve (e.g., from the memory 2820) user-specific resource allocation information for an uplink user-specific PA.

[0306] The transmit signal generator 2822 may include a control signaling generator 2824, a PPDU generator 2826, and an MPDU generator 2828. The control signaling generator 2824 may generate a control signaling field (e.g., an EHT-SIG-A field). The PPDU generator 2826 may generate a PPDU (e.g., an EHT TB PPDU). The MPDU generator 2828 may generate an (A)-MPDU, e.g., a BlockAck frame.

[0307] As described above, the embodiments of the present disclosure provide an advanced communication system, a communication method, and a communication device, which can implement a user-specific PA in an extremely high throughput MIMO WLAN network and improve the physical layer throughput in the MIMO WLAN network.

[0308] The present disclosure can be implemented by software, hardware or software and hardware collaboration. Each functional block used in the description of each of the above embodiments can be partially or entirely implemented by an LSI such as an integrated circuit, and each process described in each embodiment can be partially or entirely controlled by the same LSI or a combination of LSIs. LSI can be formed as a chip alone, or a chip can be formed to include some or all of the functional blocks. LSI may include data input and output coupled thereto. Depending on the degree of integration, the LSI here may be referred to as IC, system LSI, super LSI or ultra LSI. However, the technology for implementing integrated circuits is not limited to LSI, and can be implemented by using a dedicated circuit, a general-purpose processor or a dedicated processor. In addition, an FPGA (field programmable gate array) that can be programmed after manufacturing LSI or a reconfigurable processor that can reconfigure the connection and setting of the circuit unit arranged inside the LSI can be used. The present disclosure can be implemented as digital processing or analog processing. If future integrated circuit technology replaces LSI due to the advancement of semiconductor technology or other derivative technologies, future integrated circuit technology can be used to integrate functional blocks. Biotechnology can also be applied.

[0309] The present disclosure may be implemented by any type of device, apparatus or system having a communication function, which is referred to as a communication device.

[0310] Some non-limiting examples of such communication devices include phones (e.g., cellular (cell) phones, smart phones), tablet computers, personal computers (PCs) (e.g., laptops, desktop computers, netbooks), cameras (e.g., digital still / video cameras), digital players (digital audio / video players), wearable devices (e.g., wearable cameras, smart watches, tracking devices), game consoles, digital book readers, telehealth / telemedicine (telehealth and medical) devices, and vehicles providing communication capabilities (e.g., cars, airplanes, ships), and various combinations thereof.

[0311] Communication devices are not limited to portable or transportable, and may also include any kind of non-portable or fixed device, equipment, or system, such as smart home devices (e.g., appliances, lighting, smart meters, control panels), vending machines, and any other "things" in an "Internet of Things (IoT)" network.

[0312] Communications may include exchanging data via, for example, cellular systems, wireless LAN systems, satellite systems, etc., and various combinations thereof.

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

[0314] Communications devices may also include infrastructure such as base stations, access points, and any other device, equipment, or system that communicates with or controls devices such as those in the above non-limiting examples.

[0315] It should be understood that, although some properties of the various embodiments have been described with reference to an apparatus, the corresponding properties also apply to the method of the various embodiments, and vice versa.

[0316] It will be appreciated by those skilled in the art that, without departing from the spirit or scope of the broadly described disclosure, various changes and / or modifications may be made to the disclosure shown in the specific embodiments. Therefore, the present embodiments are to be considered in all aspects as illustrative and not restrictive.

[0317] 1. A communication device, comprising:

[0318] a circuit that generates a transmission signal including a common field, a user-specific signal field, and a data field, the common field including RU information for each of one or more allocations in the data field, and the user-specific field including one or more user information, each indicating a user-specific allocation among the one or more allocations in the data field; and

[0319] a transmitter, which transmits the generated transmission signal;

[0320] The user-specific field does not include at least one user information of a persistent allocation including cyclic transmission among the one or more allocations.

[0321] 2. The communication device of claim 1, wherein the transmitted signal includes signaling for indicating the presence of at least one persistent allocation in the data field.

[0322] 3 . The communication device of claim 1 , wherein the common field includes signaling for indicating at least one persistent allocation in the data field.

[0323] 4 . The communication device of claim 1 , wherein the transmitted signal includes signaling for indicating the presence of at least one persistent allocation in a data field containing a cyclic transmission.

[0324] 5 . The communication device of claim 1 , wherein the common field includes signaling for indicating at least one persistent allocation in a data field containing cyclic transmission.

[0325] The communication device of claim 1 , wherein the persistent allocation exists for a time period after transmission of the generated transmit signal.

[0326] 7. The communication device according to claim 1, wherein the user-specific field does not include at least one user information for persistent allocation including initial transmission; and the user information for persistent allocation is included in a control frame previously sent by the communication device.

[0327] 8. The communication device of claim 7, wherein the persistent allocation exists for a period of time after transmission of the control frame.

[0328] 9 . The communication device according to claim 8 , wherein the time period is determined or indicated by signaling contained in the control frame.

[0329] 10. A communication device, comprising:

[0330] a receiver receiving a transmission signal including a common field, a user-specific signal field, and a data field, the common field including RU information for each of one or more allocations in the data field, and the user-specific field including one or more user information, each indicating a user-specific allocation among the one or more allocations in the data field; and

[0331] Circuit, processing the received transmission signal,

[0332] The user-specific field does not include at least one user information of a persistent allocation including cyclic transmission among the one or more allocations.

[0333] 11. The communication device of claim 10, wherein the transmitted signal includes signaling for indicating the presence of at least one persistent allocation in the data field.

[0334] 12. The communication device of claim 10, wherein the common field contains signaling for indicating at least one persistent allocation in the data field.

[0335] 13. The communication device of claim 10, wherein the transmitted signal includes signaling for indicating the presence of at least one persistent allocation in a data field containing a cyclic transmission.

[0336] 14. The communication apparatus of claim 10, wherein the common field includes signaling for indicating at least one persistent allocation in a data field containing a cyclic transmission.

[0337] 15. The communication device of claim 10, wherein the persistent allocation exists for a time period after transmission of the generated transmit signal.

[0338] 16. The communication device according to claim 10, wherein the user-specific field does not include at least one user information for persistent allocation including initial transmission; and the user information for persistent allocation is included in a control frame previously received by the communication device.

[0339] 17. The communication device of claim 16, wherein the persistent allocation exists within a time period after the control frame is received.

[0340] 18. The communication device according to claim 17, wherein the time period is determined or indicated by signaling contained in the control frame.

[0341] 19. A communication method, comprising:

[0342] generating a transmission signal including a common field, a user-specific signal field, and a data field, the common field including RU information for each of the one or more allocations in the data field, and the user-specific field including one or more user information, each indicating a user-specific allocation among the one or more allocations in the data field; and

[0343] sending the generated transmit signal;

[0344] The user-specific field does not include at least one user information of a persistent allocation including cyclic transmission among the one or more allocations.

[0345] 20. A communication method, comprising:

[0346] receiving a transmission signal including a common field, a user-specific signal field, and a data field, the common field including RU information for each of one or more allocations in the data field, and the user-specific field including one or more user information, each indicating a user-specific allocation among the one or more allocations in the data field;

[0347] The user-specific field does not include at least one user information of a persistent allocation including cyclic transmission among the one or more allocations.

[0348] 21. A communication device, comprising:

[0349] A circuit for generating a transmission signal including at least one signal field content channel and a data field, each of the at least one signal field content channel including a RU (resource unit) allocation subfield consisting of N fields and a cyclic transmission bitmap subfield consisting of N bitmaps of N=1, 2, 4 or 8; and

[0350] a transmitter, which transmits the generated transmission signal;

[0351] Each of the N fields of the RU allocation subfield indicates RU information for one or more allocations within the corresponding frequency range in the data field, and the nth (n=1, 2, ..., N) bitmap of the cyclic transmission bitmap subfield indicates whether each of the one or more allocations indicated by the nth field of the RU allocation subfield includes cyclic transmission.

[0352] 22. The communication device according to claim 21, wherein if one or more allocations indicated by the nth field of the RU allocation subfield do not include cyclic transmission, the nth (n=1, 2, ..., N) bitmap of the cyclic transmission bitmap subfield does not exist.

[0353] 23. A communication device according to claim 21, wherein the transmitted signal includes an N-bit cyclic transmission presence subfield for each of the at least one signal field content channel, and the nth (n=1, 2, ..., N) bit of the cyclic transmission presence subfield indicates the presence of the nth bit map of the cyclic transmission bit map subfield in each of the at least one signal field content channel.

[0354] 24. A communication device according to claim 21, wherein each of the at least one signal field content channels includes a persistent allocation bitmap subfield consisting of N bitmaps; and the nth (N=1, 2, ..., N) bitmap of the persistent allocation bitmap subfield indicates whether each of one or more allocations indicated by the n fields of the RU allocation subfield is persistent.

[0355] 25. The communication device of claim 24, wherein if one or more allocations indicated by the nth field of the RU allocation subfield are not persistent, the nth (n=1, 2, ..., N) bitmap of the persistent allocation bitmap subfield does not exist.

[0356] 26. A communication device according to claim 24, wherein the transmitted signal includes an N-bit persistent allocation existence subfield for each of the at least one signal field content channel, and the nth (n=1, 2, ..., N) bit of the N-bit persistent allocation existence subfield indicates the existence of the nth bit map of the persistent allocation bit map subfield in each of the at least one signal field content channel.

[0357] 27. A communication device according to claim 21, wherein the RU allocation subfield and the cyclic transmission bitmap subfield are encoded separately; and the size of the nth (n=1, 2, ..., N) bitmap of the cyclic transmission bitmap subfield depends on the number of one or more allocations indicated by the nth field of the RU allocation subfield.

[0358] 28. A communication device according to claim 21, wherein the RU allocation subfield and the cyclic transmission bitmap subfield are jointly encoded; and the size of each bitmap of the cyclic transmission bitmap subfield depends on the maximum number of one or more allocations that can be indicated by any field of the RU allocation subfield.

[0359] 29. The communication device of claim 21, wherein the transmitted signal includes signaling to indicate whether the RU allocation subfield and the cyclic transmission bitmap subfield of each of the at least one signal field content channel are encoded separately or jointly.

[0360] 30. A communication device according to claim 21, wherein each of the at least one signal field content channels includes an M-bit center 26-frequency modulation RU subfield, wherein for CBW=80, 80+80 or 160MHz, M=1, and for CBW=160+160 or 320MHz, M=2, and each bit of the M-bit center 26-frequency modulation RU subfield indicates whether the corresponding center 26-frequency modulation RU is allocated.

[0361] 31. The communication device of claim 30, wherein, when M=1, the last bitmap of the cyclic transmission bitmap subfield indicates whether the allocation indicated by the M-bit center 26-frequency modulation RU subfield includes cyclic transmission.

[0362] 32. A communication device according to claim 30, wherein, when M=2, the fourth bit map of the cyclic transmission bitmap subfield indicates whether the allocation indicated by the first bit of the M-bit center 26-frequency modulation RU subfield includes cyclic transmission; and the last bit map of the cyclic transmission bitmap subfield indicates whether the allocation indicated by the second bit of the M-bit center 26-frequency modulation RU subfield includes cyclic transmission.

[0363] 33. A communication device according to claim 21, wherein each of the at least one signal field content channels is encoded on each L*20 MHz frequency band, where L=1 or 2; and the number of at least one signal field content channel depends on the channel bandwidth (CBW) and the value of L.

[0364] The communication device according to claim 33 , wherein the transmitted signal includes signaling to indicate a value of L.

[0365] 35. A communication method, comprising:

[0366] generating a transmission signal including at least one signal field content channel and a data field, each of the at least one signal field content channel including a RU (resource unit) allocation subfield consisting of N fields and a cyclic transmission bitmap subfield consisting of N bitmaps of N=1, 2, 4 or 8; and

[0367] sending the generated transmit signal;

[0368] Each of the N fields of the RU allocation subfield indicates RU information for one or more allocations within the corresponding frequency range in the data field, and the nth (n=1, 2, ..., N) bitmap of the cyclic transmission bitmap subfield indicates whether each of the one or more allocations indicated by the nth field of the RU allocation subfield includes cyclic transmission.

[0369] 36. A communication device comprising:

[0370] A circuit that generates a frame including identification information identifying an uplink persistent assignment (PA); and

[0371] A transmitter transmits the generated frame.

[0372] 37. The communication device according to claim 36, wherein the identification information is a PA identifier (PAID) of an uplink PA.

[0373] 38. The communication apparatus according to claim 36, wherein the identification information is resource unit (RU) allocation information of the uplink PA.

[0374] 39. The communication apparatus according to claim 36, wherein the identification information is included in a frame body of the frame to request transmission of the uplink PA, and the frame does not contain user-specific resource allocation information of the uplink PA.

[0375] 40. The communication apparatus according to claim 36, wherein the identification information is included in a MAC header of the frame to request transmission of the uplink PA, and the frame does not contain user-specific resource allocation information of the uplink PA.

[0376] 41. The communication apparatus according to claim 36, wherein the identification information and user-specific resource allocation information are included in a frame body of the frame to identify the uplink PA.

[0377] 42. The communication apparatus according to claim 36, wherein the identification information and user-specific resource allocation information are included in a frame body of the frame to request initial transmission of the uplink PA.

[0378] 43. A communication method, comprising:

[0379] generating a frame including identification information identifying an uplink persistent assignment (PA); and

[0380] The generated frame is sent.

[0381] 44. The communication method according to claim 43, wherein the identification information is a PA identifier (PAID) of an uplink PA.

[0382] 45. The communication method according to claim 43, wherein the identification information is resource user (RU) allocation information of the uplink PA.

[0383] 46. ​​The communication method according to claim 43, wherein the identification information is included in a frame body of the frame to request transmission of the uplink PA, and the frame does not contain user-specific resource allocation information of the uplink PA.

[0384] 47. The communication method according to claim 43, wherein the identification information is included in a MAC header of the frame to request transmission of the uplink PA, and the frame does not contain user-specific resource allocation information of the uplink PA.

[0385] 48. The communication method according to claim 43, wherein the identification information and user-specific resource allocation information are included in a frame body of the frame to identify the uplink PA.

[0386] 49. The communication method according to claim 43, wherein the identification information and user-specific resource allocation information are included in a frame body of the frame to identify the uplink PA.

[0387] 50. A communication device comprising:

[0388] Circuit,

[0389] generating a first transmit signal comprising user information for a plurality of users for a downlink MU-MIMO assignment, each user information indicating a user-specific assignment, and

[0390] also generating a second transmit signal comprising a common field, a user specific field, and a data field, the data field containing a downlink MU-MIMO assigned transmission, and

[0391] A transmitter sends a first transmission signal and a second transmission signal,

[0392] Therein, the user-specific allocation of the downlink MU-MIMO allocation is determined to be persistent or non-persistent.

[0393] 51. The communication apparatus of claim 50, wherein the user-specific persistent allocation of the downlink MU-MIMO allocation in the data field in the second transmit signal is indicated by user information in the first transmit signal.

[0394] 52. The communication apparatus of claim 50, wherein when a data field in the second transmit signal includes a recurring transmission of a user-specific persistent allocation of the MU-MIMO allocation, the user-specific field does not include user information for the user-specific persistent allocation.

[0395] 53. The communication apparatus of claim 50, wherein the common field in the second transmit signal includes signaling indicating at least one user-specific persistent allocation in a data field in the second transmit signal.

[0396] 54. The communication apparatus of claim 50, wherein the common field in the second transmit signal includes signaling for indicating at least one user-specific persistent allocation in a data field in the second transmit signal comprising a cyclic transmission.

[0397] 55. The communication apparatus of claim 50, wherein the user-specific persistent allocation exists for a time period following transmission of a first transmit signal.

[0398] 56. The communication device according to claim 55, wherein the time period is determined or indicated by signaling included in the first transmission signal.

[0399] 57. A communication method comprising:

[0400] generating a first transmit signal, the first transmit signal comprising user information for a plurality of users for a downlink MU-MIMO assignment, each user information indicating a user-specific assignment;

[0401] generating a second transmit signal comprising a common field, a user specific field, and a data field, the data field comprising a downlink MU-MIMO assigned transmission, and

[0402] sending a first transmission signal and a second transmission signal,

[0403] Therein, the user-specific allocation of the downlink MU-MIMO allocation is determined to be persistent or non-persistent.

[0404] 58. The communication method of claim 57, wherein the user-specific persistent allocation of the downlink MU-MIMO allocation in the data field in the second transmit signal is indicated by user information in the first transmit signal.

[0405] 59. The communication method of claim 57, wherein when the data field in the second transmit signal includes a recurring transmission of a user-specific persistent allocation of a downlink MU-MIMO allocation, the user-specific field does not contain user information for the user-specific persistent allocation.

[0406] 60. The communication method of claim 57, wherein the common field in the second transmit signal includes signaling for indicating at least one user-specific persistent allocation in a data field in the second transmit signal.

[0407] 61. The communication method of claim 57, wherein the common field in the second transmit signal includes signaling for indicating at least one user-specific persistent allocation in a data field in the second transmit signal containing a cyclic transmission.

[0408] 62. The communication method of claim 57, wherein the user-specific persistent allocation exists for a time period following transmission of the first transmit signal.

[0409] 63. The communication method according to claim 62, wherein the time period is determined or indicated by signaling contained in the first transmission signal.

Claims

1. An integrated circuit for a first communication device, the integrated circuit comprising: at least one input terminal for receiving an electrical signal, and Control circuit, control: receiving a trigger frame from a second communication device, the trigger frame allocating a portion of a transmission opportunity TXOP to the first communication device; as well as sending more than one physical layer protocol data unit (PPDU) within the portion of the TXOP, the trigger frame comprising a user information field for the first communication device, the user information field comprising a resource unit allocation subfield, the resource unit allocation subfield indicating a frequency resource, and the more than one PPDU is sent within the frequency resource, and After receiving the trigger frame, the second communications device no longer transmits a user information field for the first communications device within the portion of the TXOP.

2. The integrated circuit according to claim 1, in, The trigger frame allocates the portion of the TXOP to the first communication device and the third communication device, and Another PPDU is sent from the third communications device within the portion of the TXOP.

3. The integrated circuit according to claim 1, in, The portion of the TXOP is allocated only to the first communications device.

4. The integrated circuit according to claim 1, in, The trigger frame includes no more than one user information field.

5. The integrated circuit according to claim 1, in, The more than one PPDUs are sent through a scheduled access.

6. The integrated circuit according to claim 1, in, The second communications device is responsible for error recovery based on the portion of the TXOP.

7. The integrated circuit according to claim 1, in, The trigger frame includes time duration information according to the portion of the TXOP.

8. The integrated circuit according to claim 7, in, The time duration information indicates a time duration from when the time duration information is received at the first communication device to when the portion of the TXOP ends.

9. The integrated circuit according to claim 1, in, Block acknowledgment information is received based on more than one PPDU within the portion of the TXOP.

10. The integrated circuit according to claim 1, in, When the first communications device receives the trigger frame, the first communications device starts or resets a timer for the portion of the TXOP.

11. The integrated circuit according to claim 1, in, The trigger frame is carried by an extremely high throughput EHT multi-user MU PPDU.

12. The integrated circuit according to claim 1, in, The trigger frame is used to set information in the more than one PPDUs, the information being related to the portion of the TXOP.

Images