Resource allocation signaling in wireless local area network preambles

Abstract

To provide a new method and apparatus for resource allocation signaling in a WLAN.SOLUTION: An apparatus for wireless communication comprises a memory storing instructions and a processor coupled to the memory, wherein the processor and the memory generate a signaling field (SIG) in a wireless local area network (WLAN). The SIG includes a resource unit (RU) allocation field and one or more user fields indicating the size and location of each RU in the frequency resource. Each user field includes information of a scheduled station (STA), and multiple RUs (MRUs) are assigned to one STA. The apparatus also transmits a SIG.SELECTED DRAWING: Figure 3

Description

[Technical Field]

[0001] The present invention relates to wireless communications, and more particularly to a novel method and apparatus for resource allocation signaling in a WLAN. [Background technology]

[0002] In the IEEE 802.11ax standard, OFDMA modulation was first introduced. The description of which RU is used for a given PPDU is given in its SIG-B field (and is defined in detail in the 802.11ax standard shown in Figure 1). This field consists of two main subfields, a common field and a user-specific field, as shown in the 802.11ax standard.

[0003] The 802.11ax standard limits each non-AP STA to use a single resource unit (RU) consisting of contiguous tones (subcarriers). Although various RU sizes are defined in the standard (e.g., 26, 52, 106, 242, 484, 996 tones), restricting allocations to a single RU limits the use of channel resources.

[0004] As mentioned above, in the current 802.11ax standard (i.e., prior art), there are six sizes of RUs. In the allocation process, the scheduler can only allocate a single RU to a given STA in an MU-PPDU (Multi-User Physical Protocol Data Unit—Transmitted Packet) or SU-PPDU (Single-User PPDU) transmission.

[0005] If there is an unassigned RU, it cannot be assigned to a STA that has already been given an RU. Summary of the Invention

[0006] The present invention contemplates extending and improving the way channel resources are utilized in a WLAN.

[0007] A method, apparatus, and computer-readable medium for resource allocation signaling in an ultra-high throughput wireless local area network (WLAN) are disclosed.

[0008] An apparatus such as an access point (AP) may generate a signaling information field (SIG). The SIG includes a RU assignment field indicating the size and location of each resource unit (RU) in a frequency resource. The SIG further includes one or more user fields, each of which includes information on a scheduled station (STA), and an MRU including multiple RUs (MRUs) can be assigned to one or more (same) STAs. The RU includes the RU defined in 802.11ax. The MRU is a small MRU including a combination of 26-RU, 52-RU, or 106-RU in a 20 MHz frequency segment, or the MRU is a large MRU including a combination of 242-RU, 484-RU, or 996-RU in a transmission bandwidth.

[0009] In some examples, the MRU includes a first RU and a second RU. The device may generate a first user field corresponding to the first RU and a second user field corresponding to the second RU. Both the first user field and the second user field include the same ID of the STA. The second user field may further include one or any combination of the following: the number of RUs assigned to the STA, or the size and position of each RU in the MRU assigned to the STA.

[0010] Alternatively, the device may generate a common field in the SIG containing information on the number of small MRUs allocated in the corresponding 20 MHz frequency segment and / or information on the number of large MRUs allocated in the bandwidth of the transmission.

[0011] Alternatively, the device may generate a single RU user field and an MRU user field. The single RU user field corresponds to an RU that is not an MRU. The MRU user field corresponds to an MRU that includes at least the following: an STA_ID and an RU bitmap indicating the size and location of each RU included in the MRU.

[0012] Alternatively, the device may generate a common MRU field indicating which 26-RUs are included in the MRU in the corresponding 20 MHz frequency segment and / or which 242-RUs are included in the MRU in the bandwidth of the transmission.

[0013] Alternatively, the device may generate one or more common MRU fields, each of which indicates whether an actual allocated RU is within the MRU (which actual allocated RU is within the MRU).

[0014] Furthermore, other information, such as channel puncturing information in a U-SIG, may be for indicating the MRU allocation, where the puncturing information indicates non-contiguous large RUs and one or more user fields corresponding to the non-contiguous large RUs, and each of the one or more user fields contains information of a different station.

[0015] One or more stations (e.g., wireless or mobile devices) may receive a WLAN preamble that includes a SIG. The one or more stations may then determine an MRU that includes multiple RUs assigned to the STA based on the SIG.Next, the station receives a first user field corresponding to the first RU and a second user field corresponding to the second RU, both of which contain the same ID of the STA, and the second user field may further contain one or any combination of the following: the number of RUs assigned to the STA, or the size and position of each RU in the MRU assigned to the STA; or a common field of the SIG containing information on small MRUs assigned in a corresponding 20 MHz frequency segment and / or the number of some of the large MRUs assigned in the bandwidth of the transmission; or a single RU user field and an MRU user field, where the single RU user field corresponds to an RU that is not an MRU, and the MRU user field contains at least the following: STA_ID and The MRU assigned to the STA may be determined by a single RU user field and an MRU user field corresponding to the MRU, including an RU bitmap indicating the size and position of each RU included in the MRU, or a common MRU field indicating which 26-RUs are included in the MRU in the corresponding 20 MHz frequency segment and / or which 242-RUs are included in the MRU in the transmission bandwidth, or one or more common MRU fields, each common MRU field indicating whether an actual assigned RU is within the MRU (which actual assigned RU is within the MRU), or other information such as puncturing information indicating non-contiguous large RUs and one or more user fields corresponding to the non-contiguous large RUs, wherein each of the one or more user fields includes information for a different station.

[0016] The above-mentioned fields in the SIG can be load balanced across two or more channel contents. The mapping between the MRU (if any) and the STA is indicated by the structure of the fields and the position of the fields in the SIG.

[0017] A method performed by an apparatus including an AP and a station is also provided, as is a computer-readable medium for resource allocation signaling.

[0018] Some examples of the methods, apparatus, or non-transitory computer-readable media described herein may further include processes, features, means, or instructions for resource allocation signaling in an ultra-high throughput WLAN preamble. Further scope of applicability of the described systems, methods, apparatus, or computer-readable media will become apparent from the following detailed description, claims, and drawings. The detailed description and specific examples are given for illustrative purposes only, as various changes and modifications within the scope of the description will be apparent to those skilled in the art. [Brief explanation of the drawings]

[0019] The above and other objects and features of the present invention will become apparent from the following description of preferred embodiments, which are given in conjunction with the accompanying drawings. [Figure 1] FIG. 1 shows the SIG-B field (and is defined in detail in the 802.11ax standard). [Figure 2] FIG. 1 illustrates an example of a wireless local area network. [Figure 3] 10 is a flowchart illustrating communication of scheduling information in a WLAN on the transmitting side. [Figure 4] 10 is a flowchart illustrating communication of scheduling information in a WLAN at a receiving side. [Figure 5] FIG. 2 is a diagram showing an example of a pointing structure according to the first embodiment. [Figure 6] FIG. 10 illustrates another example of resource allocation in one embodiment. [Figure 7] FIG. 10 illustrates another example of a pointing structure in one embodiment. [Figure 8] FIG. 10 illustrates an example of a pointing structure in one embodiment. [Figure 9a] FIG. 10 is a diagram illustrating an example of a common field of an EHT-SIG. [Figure 9b] FIG. 10 is a diagram illustrating an example of a common field of an EHT-SIG. [Figure 9c] FIG. 10 is a diagram illustrating an example of a common field of an EHT-SIG. [Figure 10a] FIG. 1 illustrates an example of resource allocation and stations scheduled on an RU. [Figure 10b] 10b shows an example of the structure of a common field in an EHT-SIG indicating the resource allocation of FIG. 10a. [Figure 11a] FIG. 10 illustrates an example of the structure of a user-specific field of an EHT-SIG in one embodiment. [Figure 11b] FIG. 10 is a diagram illustrating an example of a structure for an MRU user field in the user specific field of an EHT-SIG. [Figure 12a] FIG. 10 is a diagram showing the structure of the user field in the user specific field of the EHT-SIG. [Figure 12b] FIG. 10 is a diagram showing the structure of the user field in the user specific field of the EHT-SIG. [Figure 13] FIG. 10 is a diagram illustrating a simulation result. [Figure 14] FIG. 10 is a diagram illustrating another example of a common MRU instruction structure. [Figure 15] FIG. 1 illustrates an example of resource allocation and RU mapping in one embodiment. [Figure 16] FIG. 1 illustrates an example of resource allocation and RU mapping in one embodiment. [Figure 17a] FIG. 10 illustrates another example of resource allocation in one embodiment. [Figure 17b] 17b shows the instruction structure of the resource allocation in FIG. 17a. [Figure 17c] FIG. 17b shows another indication structure for the resource allocation in FIG. 17a. [Figure 18] FIG. 10 illustrates another example of resource allocation and its indication structure. [Figure 19] FIG. 10 illustrates an example of a transmission including a mixed MRU. [Figure 20] FIG. 10 illustrates another example of resource allocation in one embodiment. [Figure 21] 2 is a block diagram of an access point according to one embodiment of the present invention; [Figure 22] FIG. 2 is a block diagram of a station according to one embodiment of the present invention. DETAILED DESCRIPTION OF THE INVENTION

[0020] A method for utilizing channel resources in 802.11be by allowing STAs to use multiple non-contiguous portions of the channel according to one embodiment of the present invention will now be described with reference to the accompanying drawings.

[0021] For ease of understanding, terms that may appear in the following embodiments are explained below. AP: Access Point AT: Access Terminal BSS: Basic Service Settings BW: Bandwidth CC: Content Channel DL: Downlink DS: Distribution System EHT: Ultra High Throughput ESS: Extended Service Set HE: High Efficiency LLC: Logical Link Control L-LTF: Non-HT long training field L-SIG: Non-HT SIGNAL field L-STF: Non-HT short training field LTF: Long Training Field MAC: Medium Access Protocol MCS: Modulation and Coding Scheme MLD: Multi-Link Device MRU: Multiple Resource Unit MS: Mobile station MU: Multi-User MU-MIMO: Multi-user multiple input multiple output NDP: Null Data PPDU OFDM: Orthogonal Frequency Division Multiplexing OFDMA: Orthogonal Frequency Division Multiple Access PHY: Physical Layer PPDU: PHY Protocol Data Unit RA:RU assignment field RL-SIG: Repeated non-HT SIGNAL field RU: Resource Unit SAP: Service Access Point SS:Subscriber station STA: Station SU: Single User TDLS: Tunneled Direct Link Setup TID: Traffic Identifier TXOP: Transmission Opportunity UE: User Equipment UL: Uplink U-SIG: Universal Signal Field WM: Wireless medium

[0022] FIG. 2 illustrates an example of a wireless local area network (WLAN) 100 that supports resource allocation or scheduling signaling in a WLAN preamble (eg, an EHT WLAN preamble) in accordance with various aspects of the present disclosure.

[0023] The WLAN 100 includes an access point (AP) 105 and stations (STAs) 110, labeled STA1 through STA6. The STAs 110 may represent devices such as wireless communication terminals, including mobile stations, phones, personal digital assistants (PDAs), other handheld devices, netbooks, notebook computers, tablet computers, laptops, display devices (e.g., TVs, computer monitors, etc.), printers, etc. Although only one AP 105 is shown, the WLAN 100 may have multiple APs 105. The STAs 110 may also be referred to as mobile stations (MSs), mobile devices, access terminals (ATs), user equipment (UEs), subscriber stations (SSs), or subscriber units. The STAs 110 associate with and communicate with the APs 105 via communication links 115. Each AP 105 has a coverage area 125 such that the STAs 110 within that area are within range of the AP 105. The STAs 110 are dispersed throughout the coverage area 125. Each STA 110 may be fixed, mobile, or a combination thereof. Devices within the WLAN 100 may communicate via an unlicensed spectrum, which may be a portion of the spectrum including frequency bands traditionally used by Wi-Fi technology, e.g., the 5 GHz band, the 2.4 GHz band, the 60 GHz band, the 3.6 GHz band, and / or the 900 MHz band. The unlicensed spectrum may also include other frequency bands. One or more of the STAs 110 and / or APs 105 may include a resource allocation signaling component 130, which may enable the STAs 110 and / or APs 105 to signal resource allocations in a WLAN preamble, for example, as described further below in connection with the figures.

[0024] Although not shown in FIG. 2 , a STA 110 may be covered by more than one AP 105 and may therefore be associated with multiple APs 105 at different times. A single AP 105 and the associated set of STAs 110 is referred to as a basic service set (BSS). An extended service set (ESS) is a set of connected BSSs. A distribution system (DS) is used to connect APs 105 in an extended service set. The coverage area 125 of an AP 105 may be divided into sectors that make up only a portion of the coverage area. The WLAN 100 includes different types of APs 105 (e.g., metropolitan area, home network, etc.) with different sized and overlapping coverage areas for different technologies. Although not shown, other devices may communicate with the AP 105.

[0025] While the STAs 110 can communicate with each other through the AP 105 using communication link 115, the STAs 110 can also communicate with each other directly via direct wireless communication link 120. Direct wireless communication links can occur between the STAs 110 regardless of whether any of the STAs are connected to the AP 105. Examples of direct wireless communication links 120 include Wi-Fi direct connections, connections established by using a Wi-Fi Tunneled Direct Link Setup (TDLS) link, and other peer-to-peer (P2P) group connections.

[0026] The STAs 110 and APs 105 shown in FIG. 1 communicate according to WLAN radio and baseband protocols, including physical (PHY) and medium access control (MAC) layers from IEEE 802.11 and its various versions, including but not limited to 802.11b, 802.11g, 802.11a, 802.11n, 802.11ac, 802.11ad, 802.11ah, 802.11Z, 802.11ax, etc.

[0027] Transmissions between the STA 110 and the AP 105 often include UL (uplink) or DL ​​(downlink) transmissions. In downlink transmissions, control information in a header is transmitted before data transmission. The information provided in the header is used by devices to decode subsequent data. An ultra-high-throughput WLAN preamble may be used to schedule multiple devices, such as the STA 110, for single-user simultaneous transmissions (e.g., single-user orthogonal frequency division multiple access (SU OFDMA)) and / or MU-MIMO transmissions. In one example, an EHT WLAN signaling field may be used to signal a resource allocation pattern to multiple receiving STAs 110. The EHT WLAN signaling field includes a common field decodable by multiple STAs 110, which includes a resource allocation field. The resource allocation field indicates resource unit distribution to the multiple STAs 110 and indicates which resource units in the resource unit distribution correspond to MU-MIMO transmissions and which resource units correspond to OFDMA single-user transmissions. The EHT WLAN signaling field also includes, after the common field, a dedicated user field assigned to a specific STA 110. The order in which the dedicated user fields are generated corresponds to the assigned resource units (e.g., the first dedicated user field corresponds to the first assigned resource unit). The EHT WLAN signaling field is transmitted to multiple STAs 110 together with the WLAN preamble.

[0028] It is not limited that some of the embodiments can be used in uplink transmission, i.e. some of the features or solutions can be used to trigger uplink transmission.

[0029] As shown in FIG. 3, one embodiment includes a method for communicating scheduling information in a WLAN.

[0030] 101. A device such as an access point generates a SIG (such as an EHT-SIG) that includes instruction information or scheduling information. Generation may be replaced by construction, acquisition, or determination.

[0031] 102. Transmit the SIG by the device.

[0032] Therefore, as shown in FIG. 4, another embodiment includes a method for a non-AP station to receive scheduling information in a WLAN.

[0033] 201. Receive a PPDU including a SIG (such as an EHT-SIG). The SIG may have a structure described in the following embodiments. The PPDU may include an L-STF, an L-LTF, an L-SIG, an RL-SIG, a U-SIG, and an EHT-SIG.

[0034] In the EHT preamble, a jointly encoded U-SIG of two OFDM symbols length may immediately follow the RL-SIG. The U-SIG contains version-independent fields. The intention of the version-independent content is to achieve better coexistence between future 802.11 generations. In addition, the U-SIG may have some version-dependent fields. The U-SIG is transmitted using 52 data tones and 4 pilot tones per 20 MHz. In EHT PPDUs transmitted to multiple users, a variable modulation and coding scheme (MCS) and variable length EHT-SIG may immediately follow the U-SIG.

[0035] 202. Process the SIG. Specifically, obtain scheduling information based on the SIG.

[0036] EHT-SIG is the name of the field to distinguish it from other SIG-Bs such as VHT-SIG-B, HE-SIG-B, etc. EHT-SIG can be renamed in other ways, i.e., the name itself is not an issue, and the contents and structure explained and described in the following embodiments provide a solution for efficiently scheduling resources and stations.

[0037] First, in an embodiment, the resource unit (RU) allocation field in the EHT-SIG indicates at least the sequence of RUs in the frequency domain (the size and location of each RU) and may also indicate information necessary for calculating the number of users assigned to each RU. The EHT-SIG further includes one or more user fields, each containing information about scheduled stations (STAs). Multiple consecutive or non-consecutive RUs (which may be referred to as MRUs or MRUs) defined in 802.11ax can be assigned to one or more STAs. As used in this document, "MRU" generally refers to an RU that is a combination of multiple consecutive or non-consecutive RUs, for example, defined in 802.11ax. They may be understood as RUs newly defined in the next generation of 802.11ax, for example, 802.11be.

[0038] Compared to 802.11ax, each RU allocation subfield in the EHT-SIG content channel corresponding to a 20 MHz frequency segment indicates the RU assignment, including the size of the RUs and their arrangement in the frequency domain, as well as one or more combinations of multiple RUs used in the EHT modulation field of the EHT MU PPDU in the frequency domain, and may also indicate information necessary to calculate the number of users assigned to each RU (non-MRU) and each combination of multiple RUs (MRUs). In a preferred embodiment, the subcarrier index of the RU satisfies the conditions in a table that may be defined in the 802.11be standard (for each EHT SIG content channel and PPDU bandwidth, the RUs associated with each RU allocation subfield).

[0039] In the MU-MIMO format, one or more STAs may be assigned to the same MRU or 802.11ax RU (non-MRU). This means that part of the RA subfield content will define the number of STAs, similar to the 802.11ax definition: 11000y2y1y0, 11001y2y1y0, and 11010y2y1y0 for 242-RU, 484-RU, and 996-RU, respectively. However, in 802.11be, a maximum of 16 STAs per RU may be supported, and therefore embodiments may include an RU assignment field (RA) with a value of more than 8 bits, e.g., 9 or 10 bits, to support an indication of the number of stations.

[0040] For example, 11000y3y2y1y0 indicates a 242-RU, and the number of stations on the 242-RU is indicated by y3y2y1y0, which is equal to y3y2y1y0+1. 11001y2y1y0 indicates a 484-RU, and the number of stations on the 484-RU is indicated by y3y2y1y0, which is equal to y3y2y1y0+1. 11010y3y2y1y0 indicates a 996-RU, and the number of stations on the 996-RU is indicated by y3y2y1y0, which is equal to y3y2y1y0+1.

[0041] In the following embodiments, differences in RA (if any) from 802.11ax are omitted to simplify the solution of the embodiments or examples. That is, the RA values ​​used in the following embodiments / examples may be replaced by new values ​​corresponding to 802.11be. In some embodiments, the number of RUs that can be combined as an MRU is limited. That is, limited MRUs may be defined, and each MRU represents the size and position of multiple subcarriers in the bandwidth, which overlaps with multiple 802.11ax-defined RUs.

[0042] Based on the 802.11ax-defined RUs, e.g., 26, 52, or 106 small RUs, some example MRU combinations include MRUs with {52,26} or {106,26} within 20 MHz, 40 MHz, or 80 MHz bandwidths. In some examples, only contiguous small size RU combinations should be deployed, and in some examples, non-contiguous configurations are also possible. For 242, 484, or 996 large RUs, some reasonably preferred MRU combinations include the following: 1.242+484 (contiguous and non-contiguous within each 80MHz segment) 2.242+242 (non-contiguous if puncturing) 3.484+996 4.242+484+242+484 5.242+484+996 6.242+242+996 etc.

[0043] Furthermore, it is an important issue to provide an efficient indication solution to indicate the allocation of MRUs and the corresponding information of stations scheduled on the MRUs based on some predefined MRUs (i.e., a defined combination of 802.11ax RUs, which can also be referred to as MRUs). In other words, the issue is how to indicate the allocation and station information that allows multiple RUs to be allocated to one station, and therefore how a station can obtain whether it is scheduled and on which RU or MRU it is allocated, so that the station can communicate on the allocated RU or MRU accordingly.

[0044] Furthermore, RU assignments are determined by the AP according to various criteria. For example, the AP may decide to use the RU with the highest SNR for a particular user, and these RUs are not necessarily contiguous. Furthermore, all RUs in a transmission may contain the same data packet for a station, and all RUs in an MRU, along with other RUs in a PPDU, are for the same service type.

[0045] Specifically, in some embodiments, a single FEC with the same parameters (eg, MCS, coding, N_SS, etc.) may be assigned to STAs assigned to an MRU.

[0046] The small RUs and large RUs mentioned above may not be assigned to the same MRU allocation, or it is not preferable to assign an MRU that includes both small and large RUs. In a preferred embodiment, small RUs may not be assigned across multiple 20 MHz channels. Simply put, an MRU may include a combination of 26-RUs, 52-RUs, or 106-RUs in a 20 MHz frequency segment, or an MRU may include a combination of 242-RUs, 484-RUs, or 996-RUs in a transmission bandwidth. However, an MRU may not include one of 26-RUs, 52-RUs, and 106-RUs in a first 20 MHz band and one of 242-RUs, 484-RUs, or 996-RUs that overlap another 20 MHz band.

[0047] Some embodiments may have some exceptions where a special small RU in a first 20 MHz channel may be combined with an RU in another 20 MHz channel.

[0048] In some embodiments, the MRU of small RUs is not limited to being composed of only consecutive RUs, which may support the scheduler to allocate RUs based on SNR (e.g., CQI feedback) and is efficient in allowing any combination of MRUs.

[0049] This is not limited to small RU combinations.

[0050] Assuming an RMS delay spread of approximately 1 / 3CP = approximately μsec, the coherence BW is approximately 1 MHz. Therefore, the average SNR on a given RU does not imply anything about the average SNR on its neighboring RUs.

[0051] In this embodiment, based on the support of multiple RUs / non-contiguous RUs, channel utilization is improved by making it more efficient through the expanded ability to exploit channel selectivity, further improving channel utilization and increasing overall system throughput and performance. [Embodiment 1]

[0052] The EHT-SIG in this embodiment differs from the HE-SIG B specified in 802.11ax in the following.

[0053] Corresponding user fields can point to the same STA. The common part is included in the EHT-SIG, and is similar to the structure of the common part of the EHT-SIG B. However, multiple user fields for one STA are included in the user-specific fields of the EHT-SIG. For example, a first user field is followed by another duplicated second user field. Simply put, the MRU includes a first RU and a second RU. Therefore, the EHT-SIG includes a first user field corresponding to the first RU and a second user field corresponding to the second RU. Both the first user field and the second user field contain the same station ID.

[0054] The first user fields may be similar to the user fields defined in 802.11ax, but there may be different solutions for the duplicated second user fields or other duplicated user fields recorded as second user fields.

[0055] Specifically, in one example, the duplicated second user field is the same as the first user field, which overcomes the disadvantage of only one user field / station being mapped to one RU as described in 802.11ax, making it cost-effective when designing new chips.

[0056] In another example, the duplicated second user field includes a STA_ID field and other subfields that instead hold new signaling content related to the MRU. Compared to the first example, this solution supports MRU STAs in an easier way.

[0057] In the above example, the sizes of the user fields may be the same as each other, for example, 21, 22 or 23 bits. The first user field may be identical / similar to the user field of 802.11ax (the content or structure is mainly the same).

[0058] In general, the location of the combined second RU (corresponding to the duplicated user field) is not limited, but in some examples, the rule for the location of the combined second RU / duplicated user field is set to reduce interference or inefficiency.

[0059] The contents of the Other Users field can be one of the following: Example 1, remains the same as the first user field. Example 2, below, contains different content than the first user field. Like the first user field, the first 11 bits are for the STA_ID.

[0060] Some of the other bits (eg, 1 or 2) are used to signal the type of the user field (ie, the meaning of the following bits).

[0061] The remaining bits may have any combination of the following new content related to the MRU: Two bits indicate the number of RUs (including the first RU) assigned to the STA, or N_RU, which is the number of RUs included in the MRU assigned to the STA. Thus, the STA may be able to identify a failure to decode any of the user fields and stop the decoding process. The other 8 bits are reserved, or The size and location of each RU within the MRU assigned to the STA is indicated, for example:

[0062] For small RUs: A 9-bit bitmap may indicate which 26-tone RUs within the same 20 MHz channel are part of the MRU allocation. A 52-tone RU may be indicated by the appropriate 2 bits, and a 106-tone RU may be indicated by the appropriate 4 bits. The 10th bit is reserved.

[0063] For large RUs: An 8-bit bitmap may indicate which 242-tone RUs in the same 80 MHz channel and the next 80 MHz channel are part of the MRU allocation. A 484-tone RU may be indicated by 2 bits (2 x 242-tone RUs), and a 996-tone RU may be indicated by 4 bits (4 x 242-tone RUs). The 9th and 10th bits are reserved. The MRU is limited to a 160 MHz boundary in this embodiment. A STA can know whether it has been assigned an MRU after completing decoding of the EHT-SIG. Therefore, no special signaling is required for the MRU user field.

[0064] 5 shows an example of an indication structure in the first embodiment. The RU Allocation (RA) field in the common part of the EHT-SIG is set to "00000100," which represents the RU sequence allocation [26, 26, 52, center-26, 26, 26, 26, 26]. Therefore, eight user fields (UF) are included in the corresponding user-specific field. In this example, UF1 is mapped to the first 26-RU, which contains information about STA1, such as its AID. UF2 is mapped to the second 26-RU, which contains information about another STA, and its content and structure may be similar to the user field in 802.11ax.

[0065] UF3 corresponds to 52-RU, and UF3 includes a station information field, which is also set as the AID of STA1. The contents of UF3 include different examples.

[0066] In one example, UF3 further includes a bitmap "101101000," where each bit in the bitmap corresponds to a 26-RU, indicating which 26-RUs are present in the MRUs assigned / allocated to STA1. In this example, "101101000" means that the first, third, fourth, and sixth 26-RUs are included as MRUs assigned to STA1.

[0067] In another example, UF3 alternatively includes an N-RU field instead of a bitmap. The N-RU field indicates the number of RUs in the sequence of [26, 26, 52, center-26, 26, 26, 26, 26] RUs combined as the MRU assigned to STA1. In this example, the number of RUs is 3.

[0068] Other UFs are also illustrated in FIG.

[0069] On the station side, the STA can obtain the size and position of the sequence of RUs allocated corresponding to 20 MHz from the RA field, and can also obtain whether the STA is scheduled / assigned and to which of one or more RUs the STA is allocated.

[0070] For example, a STA may determine based on "00000100" that the sequence of RUs allocated corresponding to 20 MHz is the RU sequence [26, 26, 52, center-26, 26, 26, 26, 26], and further determine that the STA is scheduled on the first, third, and fifth RUs in the above sequence of RUs based on UF1, UF3, UF5 (first, third, and fifth are in order in this sequence). That is, the MRUs configured by "first 26-RU, second 52-RU, sixth 26-RU" and "first 26-RU, second 52-RU, sixth 26-RU" are in order in the 20 MHz tone plan. [Table 1]

[0071] As shown in Figure 6, another example of resource allocation in embodiment 1 is shown, where at 160 MHz, the first, third, fourth, and fifth 242-RUs are assigned to STA1, and the sixth and eighth 242-RUs are assigned to STA2.

[0072] There are different solutions for the content of the common part and the UF in the EHT-SIG, whose allocation is shown in Figure 6. The common part can be divided into two content channels (CC).

[0073] In this example, the intersection of CC1 includes "11000000(RA-1, 242(1)), 01110010(RA-3, 484(0)), 11000000(RA-5, 242(1)), 11000000(RA-7, 242(1))", and the intersection of CC2 includes "11000000(RA-2, 242(1)), 11001000(RA-4, 484(1)), 11000000(RA-6, 242(1)), 11000000(RA-8, 242(1))". In CC1, "11000000(RA-1), 01110010(RA-3), 11000000(RA-5), 11000000(RA-7)" correspond to the first, third, fifth, and seventh 20MHz, respectively, and in CC2, "11000000(RA-2), 11001000(RA-4), 11000000(RA-6), 11000000(RA-8)" correspond to the second, fourth, sixth, and eighth 20MHz. "11000000" indicates an allocation of 242(1), i.e., a 242-RU with one user field, "01110010" indicates an allocation of 484-RU with zero user fields in a content channel with a corresponding 8-bit RU allocation subfield of "01110010". "11001000" indicates an allocation of 484-RU with one user field in a content channel with a corresponding 8-bit RU allocation subfield of "11001000". The common part of CC1 together with the common part of CC2 indicates an allocation of 160 MHz, i.e., the sequence of RUs [242, 242, 484, 242, 242, 242, 242].

[0074] 7, EHT-SIG includes CC1 and CC2. CC1 includes UF1, UF5, and UF7, which correspond to RA1, RA5, and RA7, respectively. CC2 includes UF2, UF4, UF6, and UF8, which correspond to RA2, RA4, RA6, and RA8, respectively.

[0075] UF1 is a first user field containing the ID of STA1. UF4 and UF5 are second user fields containing the ID of STA1 (same as UF1) and a first bitmap, where the first bitmap is 8 bits, and each bit indicates whether the corresponding 242-RU is within the MRU assigned to STA1 (e.g., 10111000 indicates that the first, third, fourth, and fifth 242-RUs are assigned to STA1). UF6 and UF8 contain the same ID of STA2, and UF8 preferably contains a second bitmap, which is 8 bits or the remaining bits other than the RUs already assigned to the first bitmap (i.e., 4 bits in this example), and each bit of the 8 bits indicates whether there is a corresponding 242-RU in the MRU assigned to STA1 (e.g., 10111000 indicates that the first, third, fourth, and fifth 242-RUs are assigned to STA1).

[0076] UF2 and UF7 are user fields not assigned to MRU, and will not be described in detail here.

[0077] In this example, if RU r is an RU equal to or greater than 484 tones, the largest predefined RU in the MRU, the number of users assigned to the MRU is equal to the number of users field for this RU r in the MRU summed across both EHT-SIG-B content channels, i.e., Nuser(r, CC1) + Nuser(r, CC2), where r is the largest RU in the MRU. In the above example, the 484-RU and 242-RU are included in the MRU assigned to STA1, and the number of users is determined by the 484-RU: n1(second 484-RU, CC1) + n2(second 484-RU, CC2) = 0 + 1 = 1. In this example, one station in the MRU is assigned, but the MRU is not limited to having multiple stations assigned.

[0078] 8, the resource allocation is similar, but MRU1, which contains 484-RUs, is assigned to two stations. In this example, the intersection of CC1 includes "11000000(RA-1, 242(1)), 11001000(RA-3, 484(1)), 11000000(RA-5, 242(1)), 11000000(RA-7, 242(1))" and the intersection of CC2 includes "11000000(RA-2, 242(1)), 11001000(RA-4, 484(1)), 11000000(RA-6, 242(1)), 11000000(RA-8, 242(1))". In CC1, "11000000(RA-1), 11001000(RA-3), 11000000(RA-5), 11000000(RA-7)" correspond to the first, third, fifth, and seventh 20MHz, respectively, and in CC2, "11000000(RA-2), 11001000(RA-4), 11000000(RA-6), 11000000(RA-8)" correspond to the second, fourth, sixth, and eighth 20MHz, respectively. "11000000" indicates a 242-RU allocation with 242(1), i.e., one user field, and "11001000" indicates a 484-RU allocation with one user field in the content channel with the corresponding 8-bit RU allocation subfield "11001000". The common part of CC1 together with the common part of CC2 indicates an allocation of 160 MHz, i.e., the sequence of RUs [242, 242, 484, 242, 242, 242, 242].

[0079] UF1 corresponds to the first 242-RU in MRU1, which is the first user field containing the ID of STA1.

[0080] In UF3, UF4 corresponds to the same 484-RU in MRU1 assigned to two stations (indicated by RA3 and RA4), e.g., STA1 and STA3, and should contain the ID of STA1 and the ID of STA3, respectively. If UF3 contains the ID of STA1, UF3 is the second user field of STA1 (indicating that the second 484-RU is in MRU1) and further contains a first bitmap of 8 bits, where each bit of the 8 bits indicates whether the corresponding 242-RU is in the MRU assigned to STA1, and UF4 contains the ID of STA3, and UF3 is the first user field of STA3.

[0081] Alternatively, if UF3 includes the ID of STA3, UF3 is the first user field of STA3, UF4 may include the ID of STA1, and UF3 is the second user field of STA1 (indicating that the second 484-RU is within MRU1), and further includes a first bitmap of 8 bits, each bit of which indicates whether the corresponding 242-RU is within the MRU assigned to STA1.

[0082] UF5, which corresponds to RA5 (indicating the fifth 242-RU), is a second user field that includes the ID of STA1 or STA3 (indicating that the fifth 242-RU is in MRU1) and a first bitmap of 8 bits, where each bit of the 8 bits indicates whether the corresponding 242-RU is in the MRU assigned to STA1 and STA3 (e.g., 10111000 indicates that the first, third, fourth, and fifth 242-RUs are assigned to STA1 and STA3).

[0083] UF6 and UF8 contain the same ID of STA2, and UF8 preferably contains a second bitmap, which is 8 bits or the remaining bits other than the RUs already assigned to the first bitmap (i.e., 4 bits in this example), and each bit of the 8 bits indicates whether there is a corresponding 242-RU in the MRU assigned to STA1 (e.g., 10111000 indicates that the first, third, fourth, and fifth 242-RUs are assigned to STA1). UF2 and UF7 are user fields not assigned to MRUs, and details will not be described here.

[0084] In this example, if RU r is an RU equal to or greater than 484 tones, the largest predefined RU in the MRU, the number of users assigned to the MRU is equal to the number of users field for this RU r in the MRU summed across both EHT-SIG-B content channels, i.e., Nuser(r, CC1) + Nuser(r, CC2), where r is the largest RU in the MRU. In the above example, the 484-RU and 242-RU are included in the MRU assigned to STA1, and the number of users is determined by the 484-RU: n1(second 484-RU, CC1) + n2(second 484-RU, CC2) = 1 + 1 = 2. In this example, two stations in the MRU are assigned, but the MRU is not limited to having more than two stations assigned.

[0085] In embodiment 1, additional MRU information can be indicated by modifying the remaining bits in the duplicated user field, and this solution does not require additional entries in the RU allocation subfield, and the MRU definition and signaling are simple. [Embodiment 2]

[0086] In a second embodiment, the EHT-SIG includes a common field that accommodates additional RUs and where the RU allocation includes a combination of RUs (MRU), plus a user-specific field with a subfield that defines the MRU allocation, which is different from the user-specific field in 802.11ax.

[0087] 9a, 9b, and 9c show an example of a common field of an EHT-SIG, which includes one or more fields other than the RA field and other information (e.g., the RA field corresponding to a 20 MHz segment or a 40 MHz segment may be longer than in the prior art to allow for more allocations or to allow for more STAs to be assigned).

[0088] The one or more fields include a first field and / or a second field. The first field, N_MRU_1, corresponds to each 20 MHz present in the entire BW and occupies N×2 bits. The first field indicates the number of MRUs present in each 20 MHz channel (small MRUs include small-sized RUs such as 26 RUs, 52 RUs, or 106 RUs). The second field, N_MRU_2, corresponds to the entire transmission bandwidth and indicates the number (how many) of larger-sized MRUs (large MRUs include RUs such as 242-RUs, 484-RUs, or 996 RUs) in the transmission bandwidth. Specifically, N_MRU_2 refers to the entire BW and is the same for both CC1 and CC2. N_MRU_1 refers to each 20 MHz individually and is therefore most likely to be different between CC1 and CC2.

[0089] Details are as follows:

[0090] The N_MRU_1 field (N×Nb bits), which may also be referred to as the number of small MRUs field, indicates the number (how many) of small MRUs allocated / present in the corresponding 20 MHz channel / frequency segment. This field may be located following each of the RU Allocation (RA) subfields in each content channel (CC) of the EHT-SIG. The total overhead of the N_MRU_1 field in the EHT-SIG may be N×Nb bits, where N is the number of 20 MHz channels in CC1 or CC2, and Nb is 1 or 2. A small MRU is an RU combined with several small RUs having a size of 26, 52, or 106. It is not limited that the RUs in a small MRU may include small RUs of different sizes, and it is not limited that a small MRU may be larger than 106; however, the small MRU may be within 20 MHz; otherwise, a larger RU, such as a 242-RU, 484-RU, 996-RU, or 2×996 RU, may be indicated. It may be likely that only a single MRU is available per 20 MHz frequency segment. Therefore, this field may require either 1 or 2 bits, so that if 1 bit is implemented, a "1" indicates that an MRU is present in the corresponding 20 MHz frequency segment, and a "0" indicates that an MRU is not present in the corresponding 20 MHz frequency segment. This may also be useful in embodiment 3 below.

[0091] The N_MRU_2 field, which may also be referred to as the number of large MRU fields, indicates the number of large MRU allocations present in the entire BW. This field may be located before the end of each CRC and CC in the EHT-SIG. The total overhead of the N_MRU_2 field in the EHT-SIG may be 2 bits, where N is the number of 20 MHz frequency segments. A large MRU is an RU combined by several large RUs with sizes of either 242, 484, or 996. It is not limited that the RUs within a large MRU may contain large RUs of different sizes, and it is not limited that a large MRU may be greater than 996, but the large MRU is within the entire bandwidth of the transmission.

[0092] Figure 9a shows the structure of the common part of EHT-SIG B in 20 MHz bandwidth transmission.

[0093] Figure 9b shows the structure of the common part of EHT-SIG B in 40 MHz bandwidth transmission.

[0094] 9c shows the structure of the common part of EHT-SIG B in an 80 MHz bandwidth transmission. Other structures of the common part of EHT-SIG B in other bandwidths are similar and will not be repeated here.

[0095] FIG. 10a illustrates an example of resource allocations and stations scheduled on RUs. FIG. 10b illustrates the structure of the common field of the EHT-SIG showing the resource allocation of FIG. 10a. The common field includes an RU allocation subfield "00000100" indicating an allocation representing [26, 26, 52, center 26, 26, 26, 26]. The first field "10" indicates that there are two MRUs in the corresponding 20 MHz channel (STA1's MRU and STA2's MRU in FIG. 9a above). The second field "00" indicates that there is no MRU for the large RU. The common field further includes an RU allocation subfield "00001011" indicating an allocation representing [52, 26, 26, center 26, 52, 52]. The first field "10" indicates that there are two MRUs in the corresponding 20 MHz channel (STA3's MRU and STA4's MRU in FIG. 9a above). The second field "00" indicates that there is no MRU for the large RU.

[0096] Figure 11a illustrates an example of the structure of the user-specific field of the EHT-SIG in this embodiment. The user-specific field includes two subfields: an MRU user-specific field (which normally precedes the single-RU specific field) and a single-RU specific field. The single-RU specific field includes one or more single-RU user fields assigned on a single RU, where a single RU is a normal RU that is not combined with other RUs. The MRU user field corresponding to an MRU includes at least the following: an STA_ID and an RU bitmap indicating the size and location of each RU included in the MRU. Figure 11b illustrates an example of the structure for the MRU user field in the user-specific field of the EHT-SIG.

[0097] 12a and 12b, following the example of Fig. 10a, the structure of the user field in the user specific field of the EHT-SIG is shown. The MRU user field contains the following information: STA_ID (11 bits), MCS (4 bits), coding (1 bit), RU bitmap (this RU bitmap indicates RUs that belong to the same MRU allocation), CRC and Termination (10 bits).

[0098] Specifically, the RU bitmap, which indicates the size and location of each RU included in the MRU, can be indicated in at least two ways. As an example, for small RUs, there are nine 26-tone RUs, so the RU bitmap in each CC contains 9 bits, with each bit mapping to a 26-RU (see Figure 12a).

[0099] Alternatively, in another example, a sequence of RUs is shown based on the RU allocation field (e.g., Figure 10b), and the number of RUs in each 20 MHz frequency segment can be extracted from the common field. The RU bitmap in each CC includes several bits. The number of bits is equal to the number of RUs in the allocation of the 20 MHz frequency segment. Each bit maps to an RU in the sequence of RUs (see Figure 12b). Because the sequence of RUs in the first 20 MHz frequency segment includes 8 RUs, the RU bitmap in CC1 includes 8 bits. Each bit maps to an RU in the 8 RUs. Because the sequence of RUs in the first 20 MHz frequency segment includes 6 RUs, the RU bitmap in CC2 includes 6 bits, and each bit maps to an RU in the 6 RUs.

[0100] In another example, for a large RU, there are 16 242-tone RUs within a 320 MHz bandwidth (BW), and similarly, the RU bitmap in the user field of the EHT-SIG may include 16 bits, each bit mapping a 242-tone RU and indicating whether the MRU contains a 242-tone RU.

[0101] In the above embodiment 2, by separating the MRU user-specific field and single-RU-specific field, MRU information can be added, the same error probability of SIG-B per STA remains the same, and the overall size is reduced for MRUs consisting of three or more RUs. [Embodiment 3]

[0102] In some embodiments, a new RU size is defined, and this new size is called MRU.

[0103] Thus, the RU Allocation subfield contains an entry / index that indicates the allocation that includes the MRU.

[0104] In this embodiment, only a single user field is required for each RU or MRU, so the user-specific fields are not augmented, i.e., multiple user fields are not required to be included corresponding to the MRU.

[0105] As mentioned, RU assignments are determined by the AP according to various criteria: The resource needs of a station in transmission are considered when determining a preferred RU or MRU.

[0106] Table 1 below is an example of required resources (specifically, less than 20 MHz) and a preferred RU or MRU based on the required resources. [Table 1] [Table 2]

[0107] The new table of RU allocation subfields is based on one or more of the above RU / MRUs, and may also take into account the number of MRUs and the position of each RU within the MRU. The more flexible the MRU, the more indexes are required. Preferred RU / MRUs may be defined and limited to reduce the complexity of the RU allocation subfield.

[0108] Table 2 below is another example of required resources (specifically, greater than 20 MHz, with 320 MHz bandwidth supported) and preferred RUs or MRUs based on the required resources. [Table 2] [Table 3]

[0109] To reduce instruction complexity and more efficiently meet resource needs, a preferred MRU is provided. Referring to Figure 13, simulation results show that combining the best 26-RU with an RU > 26 to form an MRU results in a slight SNR gain, with the best 26-RU combined with a given 26-RU resulting in an SNR of > 3 dB.

[0110] Thus, for a 20 MHz frequency segment, in one example, a preferred MRU includes a combination of an intermediate 26-RU and its adjacent 52-RU / 106-RU, or a combination of two 26-RUs different from the already defined 52-RU, which may also be referred to as an aggregated intermediate 26-RU, its contiguous 52-RU or 106-RU, or an aggregated non-contiguous 26-RU.

[0111] However, even with the above constraints, expanding the RU allocation table may be impractical in some situations because too many entries would be required to support other MRU combinations. [Table 3] [Table 4]

[0112] Referring to Table 3, too many entries are required to support other MRU combinations, e.g., two simultaneous 2x26-RU MRUs. Therefore, instead of expanding the RU allocation subfield to a larger dimension, alternative embodiment 3 includes a new field to indicate the size and location of each RU aggregated in the MRU, which may be called a common MRU. An example is shown in Figure 14.

[0113] This common MRU field is only present if there are any MRUs in the PPDU (in any of the 20 MHz channels). Therefore, the common MRU field can be signaled either in the U-SIG before the EHT-SIG or as an additional bit / field in the common field of the EHT-SIG.

[0114] For small MRU: This common MRU field is encoded separately. This common MRU field contains three bitmap subfields as follows: MRU_1: May be 9 bits, indicates which 26-RUs are contained in the first MRU. MRU_2: May be 7 bits, indicates which 26-RUs are contained in the second MRU. MRU_3: May be 5 bits, indicates which 26-RUs are contained in the third MRU.

[0115] Therefore, an additional 21 (22 bits including signaling bits indicating whether an MRU is / is present) are required to signal any combination of up to 3 MRUs per 20 MHz frequency segment.

[0116] The amount of additional bits will be saved later by reducing the number of user fields in the user specific field.

[0117] It should be noted that in this embodiment, the common NRU fields may appear as high overhead, but a greater amount of additional bits is saved later due to the reduction in the number of user fields in the user-specific fields.

[0118] For large MRU: A large MRU is identified by a corresponding RU allocation subfield with RU≧242 tones.

[0119] In this case, the common MRU field (bitmap) indicates which other RUs (>242) correspond to the same MRU. MRU_1: Can be 8 bits (the 9th bit is omitted), indicates which 242-RUs belong to the MRU. MRU_2:Omitted. MRU_3:Omitted.

[0120] As with the small MRU case, the user-specific field overhead is also reduced. That is, for an indicated MRU, one or more user fields are included, and no station ID is repeated in different user fields. The number of stations or user fields indicated by the RU assignment field still comes into play when a station decides which RU / MRU to assign to it.

[0121] The user-specific field is included in the EHT-SIG, and each RU / MRU and / or common MRU field indicated by the RU assignment subfield is a mapping to one or more user fields. Typically, user fields are mapped to MRUs / RUs in order. Because the location of RUs within an MRU may be alternated, some rules should be established for the mapping of MRUs and one or more user fields assigned to the MRUs. In one example, the location of an MRU is specified by the location of the first RU in the lowest frequency region. Referring to Figure 17a, based on the frequency orders of 26-RU1, 26-RU2, and 52-RU2, MRU1 is the RU for which 26-RU1 is the lowest, MRU2 is the RU for which 26-RU2 is the lowest, and MRU3 is the RU for which 52-RU2 is the lowest.

[0122] One or more user fields of an MRU / RU may be mapped to the MRU / RU in a manner similar to 802.11ax. The user field position of an MRU is according to the RU with the lowest frequency, as shown in the two examples in Figures 15 and 1010. In another understanding, each user field of an MRU is directed to the first RU (the RU located at the lowest frequency) of the MRU.

[0123] For MRUs larger than 242-RU (or 106RU), MU-MIMO is supported, and the number of user fields corresponding to the MRU is also indicated. When the content is divided into CC1 and CC2, the number of user fields corresponding to the MRU in CC1 and CC2 is indicated, respectively.

[0124] In this solution, the STA can decode the user-specific field in a similar manner to 802.11ax. When decoding the user-specific field, the STA uses the RU / MRU allocation or structure (signaled in the common field) to obtain the user field on the RU / MRU. If necessary, the remaining RUs of the same MRU are omitted.

[0125] In the example of Figure 15, MRU1 includes 26-RU-1 and 26-RU-3, the sequence / order positions of the MRU / RU are [MRU1, 26-RU-2, 26-RU-4, 26-RU-5, 52-RU3, 52-RU4], and the user fields are mapped to the MRU / RUs in order. In the example of Figure 16, MRU1 includes 52-RU2 and 26-RU5, the sequence / order positions of the MRU / RU are [26-RU1, 26-RU2, MRU1, 52-RU3, 52-RU4], and the user fields are mapped to the MRU / RUs in order.

[0126] Figure 17a shows an example of an RU / MRU allocation including three M-RUs in a 20 MHz frequency segment. The complete common field "100000111100000011010001100111" includes an MRU indication, an RU allocation subfield, a first MRU bitmap, a second MRU bitmap, and a third MRU bitmap, as shown in Figure 17b. Details are provided below.

[0127] The MRU indication, which is one bit, indicates whether there is any MRU in the allocation.

[0128] The RU Allocation subfield, which can be 8, 9, or 10 bits, indicates the sequence of each RU (size and position of each RU) corresponding to the 20 MHz frequency segment. In this example, "00000111" indicates an allocation of [26, 26, 52, middle - 26, 52, 52].

[0129] The first MRU bitmap, denoted as MRU_1, indicates which 26-RUs are in the first MRU. In this example, 100000011 indicates that the first, eighth, and ninth 26-RUs are combined into the first MRU. The first MRU bitmap typically starts with 1 (the MSB is 1), which indicated the MRU containing the 26-RU at the left edge.

[0130] The second MRU bitmap, denoted as MRU_2, indicates which 26-RUs are in the second MRU. In this example, 0100011 indicates that the second, sixth, and seventh 26-RUs are combined as the second MRU. Only 6 bits are required, so the MSB is 0.

[0131] The third MRU bitmap, denoted as MRU_3, indicates which 26-RUs are in the third MRU. In this example, 00111 indicates that the second, sixth, and seventh 26-RUs are combined as the second MRU. Only three bits are required, so the two most significant bits are 0.

[0132] In Figure 17c, based on the same example of RU / MRU allocation, the following alternative solution is provided: the RU allocation field in the common field of the EHT-SIG indicates the size and location of the RU in the frequency segment, and the common field of the EHT-SIG further includes one or more common MRU fields, each of which indicates that the RU indicated by the RU allocation field (i.e., the allocated RU) is in the MRU. This differs from Figure 17b in that granularity is used to indicate the MRU. The length of the common MRU fields preferably decreases in order, and the order of the common MRU fields is based on the first RU in the MRU in the frequency domain.

[0133] For example, the RU allocation field is set as 00000111.

[0134] Common MRU field: Using a bitmap corresponding to the actual number of RUs, each bit indicates whether the RU indicated by the RU allocation field is in the MRU. Unused bits are set to "0".

[0135] The bits required for this solution may be much shorter than in Figure 17b: see Figure 17c: 6 bits for MRU_1, 4 bits for MRU_2, and 2 bits for MRU_3.

[0136] RU Allocation field: 00000111

[0137] Common MRU field 1, MRU_1, indicates which RU is in the first MRU, for example 000100001. Only 6 bits of 100001 are required, so the 3 MSBs are set to 0, or in the case of other functions the first 3 bits may be omitted.

[0138] Common MRU field 2, MRU_2: 0001001. Only 4 bits are required, so the 3 MSBs can be set to 0 or omitted for other functions.

[0139] MRU_3:00011, which is common MRU field 3. Only 2 bits are required, so the 3 MSBs can be set to 0 or can be for other functions.

[0140] The order of the common MRU fields follows the order of the first RUs within the MRU in the frequency domain, see Figure 17a.

[0141] Figure 18 provides a solution showing the RU / MRU allocation per 160 MHz BW for a large MRU. In this example, there are two MRUs, one MRU containing 242-RU1, 242-RU3, 242-RU4, and 242-RU7 (shown in gray). The other MRU contains 242-RU5, 242-RU6, and 242-RU8.

[0142] The EHT-SIG includes CC1 and CC2. The information of the EHT-SIG may be divided into CC1 and CC2 to reduce overhead and increase the robustness of the information.

[0143] The CC1 common field contains RU allocation information (fields) per 20 MHz frequency segment or per 40 MHz frequency segment for odd-numbered 20 MHz or 40 MHz frequency segments. For example, in this example, for 20 MHz frequency segments, it is 11100xxx.

[0144] The CC2 common field contains RU allocation information (fields) per 20 MHz frequency segment or per 40 MHz frequency segment for even-numbered 20 MHz or 40 MHz frequency segments. For example, in this example, for 20 MHz frequency segments, it is 11100xxx.

[0145] In alternative solutions, the common fields mentioned above may be omitted by other solutions or may be shown in the manner described in other embodiments.

[0146] MRU_1 is valid and is 8 bits in length.

[0147] The MRU_1 field in CC1 also corresponds to odd-numbered 20 MHz or 40 MHz segments. In the example of Figure 18, the first four bits map to the first, third, fifth, and seventh 20 MHz segments, respectively, in the primary 160 MHz or only 160 MHz BW. If the BW is 320 MHz, the next four bits map to the ninth, eleventh, thirteenth, and fifteenth 20 MHz segments, respectively.

[0148] The MRU_1 field in CC2 also corresponds to even-numbered 20 MHz or 40 MHz segments. In the example of Figure 18, the first four bits map to the first, third, fifth, and seventh 20 MHz segments, respectively, in the primary 160 MHz or only 160 MHz BW. If the BW is 320 MHz, the next four bits map to the ninth, eleventh, thirteenth, and fifteenth 20 MHz segments, respectively.

[0149] Similarly, the MRU_2 field indicates the RU in MRU2 in a similar manner as the MRU_1 field.

[0150] In some solutions, MRU_2 and MRU_3 are omitted based on the MRU signal bit and the RA subfield in the intersection.

[0151] Figure 19 provides an example of a transmission involving mixed MRUs (large and small MRUs). In this example, 242-RU2 is assigned as a small MRU, such as in Figures 17a and 14b, and the other 242-RU is assigned as a large MRU, such as in Figure 18.

[0152] The RA field (including RA2 for 242-RU2) is located in the common part of the EHT-SIG in a manner similar to that shown in FIG.

[0153] A small MRU_1 / 2 / 3 field may be added in CC2 in place of the MRU field corresponding to RA2.

[0154] In this embodiment, by providing a common subfield with the MRU bitmap, many technical advantages are obtained, namely, any combination of MRUs can be defined, expansion of the RU allocation subfield can be avoided, implementation is practical, and the overall overhead in the EHT-SIG is reduced. [Embodiment 4]

[0155] In this embodiment, an MRU can be assigned to one station, and preamble puncturing is also taken into account. This embodiment works when allocating large RUs, such as 996-RU, 1992-RU (2*996-RU), or 3984-RU (4*996-RU) large RUs (RUs > 484), with some of their 20 MHz portions punctured. In this case, information already available about channel puncturing is used to define the punctured large RU as a single RU instead of several smaller RUs. This information may be available in a field preceding the EHT-SIG, which may be called the "U-SIG," and may be indicated by two or more bits. The common part of the EHT-SIG does not contain information about subchannel (20 MHz) puncturing.

[0156] It is assumed that puncturing typically occurs (especially in dense networks). Referring to RU>484, puncturing information is included in the SIG (likely defined in the U-SIG), and the puncturing information is used to define or indicate non-contiguous large RUs (punctured RUs). Therefore, the SIG may further include a single-user-specific field (in the EHT-SIG) that includes one or more user fields corresponding to the non-contiguous large RUs. Each of the one or more user fields includes information for different stations. Therefore, these stations are assigned to non-contiguous large RUs by MU-MIMO.

[0157] Figure 20 shows an example of the above embodiment in a 160 MHz bandwidth. In this example, the first 996-RU is assigned to STA1, of which the second 242-RU is punctured. This assignment is equivalent to the first 242-RU and the second 484-RU being assigned to STA1. The second 996-RU is assigned to STA2, of which the second 242-RU is punctured. The sixth 242-RU and the eighth 242-RU are assigned to STA2. In this example, the frequency resource assigned to STA1 may be defined or considered as one punctured 996-RU (shown as the primary 80 MHz). Instead of embodiment 1, a single user-specific field (in which different user fields have information for different stations) may be included corresponding to the punctured 996-RU in the EHT-SIG, i.e., two user fields requesting two RUs, where the first user field corresponds to the first 242-RU and the second user field corresponds to the second 484-RU, and the first and second user fields include the same station ID. Similarly, the frequency resource allocated to STA2 may also be defined or considered as one punctured 996-RU (denoted as secondary 80 MHz). Instead of embodiment 1, i.e., two user fields requesting two RUs, where the first user field corresponds to the sixth 242-RU and the second user field corresponds to the eighth 242-RU, a single RU corresponding to the punctured 996-RU in the EHT-SIG may be included.

[0158] When a STA recognizes that RU-996 has been assigned, it already knows that this RU is punctured, reducing overhead.

[0159] Furthermore, any receiver that supports the proposed method (specifically, a Huawei device) can easily decode signals defined by the same proposed method, thus disclosing the use of the present invention by competitor transmitters. [Embodiment 5]

[0160] As mentioned in embodiment 3, a new table may be defined in which the newly defined MRU is also indicated by a defined index / bit sequence in the RU allocation subfield.

[0161] The RU assignment subfield (RA) can be 8, 9, 10, or more bits, corresponding to 20 MHz. The more bits in the RA, the more MRUs can be supported; i.e., one or more of the listed MRUs can be present in the RU assignment, indicated by the index corresponding to the RU assignment. If more stations can be assigned to an RU or MRU, more bits are required to indicate the number of stations. Once the MRU in the RU assignment and the number of stations on the MRU are indicated, the mapping between the RU / MRU and user fields is indicated by the sequence of RU / MRU and the sequence of station / user fields, i.e., a one-to-one mapping by order.

[0162] As mentioned, RU assignments are determined by the AP according to various criteria: The resource needs of a station in transmission are considered when determining a preferred RU or MRU.

[0163] To reduce the complexity of the table, a preferred or limiting allocation of RUs or MRUs is defined in the table, and inefficient allocation of RUs / MRUs is not allowed.

[0164] Table 4 below is an example of required resources (specifically less than 20 MHz) and a preferred RU or MRU based on the required resources. [Table 4] [Table 5]

[0165] The new index table for the RU allocation subfield may need to take into account the above preferred RU / MRU, the number of MRUs, and the position of each RU in the MRU. The more flexible the MRU, the more indexes are required.

[0166] Table 5 below is another example of a preferred RU or MRU based on required resources (specifically, greater than 20 MHz, with 320 MHz bandwidth supported) and an entry in the index table of the RU allocation subfield. [Table 5] [Table 6]

[0167] The largest M consecutive 242-RUs (large MRUs) in the above are defined and mapped to an index, where the large MRU starts from the starting 242-RU in the frequency domain, and the starting RA corresponds to M×242 (the first RA in the common part of the EHT-SIG indicates the M×242 MRU), and this large MRU can be punctured by a second RA corresponding to 20 MHz following the starting 242-RU in the frequency domain.

[0168] Large MRUs can be further qualified in Table 6 below, which requires an entry in the index table of the RU allocation subfield. [Table 6] [Table 7] Large MRUs can be further reduced.

[0169] The entries required for each large MRU may be based on the number of stations that can be assigned on the large MRU. For example, if 16 stations of MU-MIMO are supported, each large MRU may have 16 entries. The value of the index is not limited, and 2, 3, or 4 bits in the index may be used to indicate the number of stations on the large MRU.

[0170] Based on the above solution, in the example of Figure 6, at 1660 MHz, the first, third, fourth, and fifth 242-RUs are assigned to STA1, and the sixth and eighth 242-RUs are assigned to STA2. The RU assignments can be indicated by the common part of the EHT-SIG as follows: The common part of CC1 includes "RA-1 indicating 5 × 242 MRU (n1)); RA-3 indicating 5 × 242 MRU (n1); RA-5 indicating 5 × 242 MRU (n1); RA-7 indicating 242 (n4)"; The intersection of CC2 includes "RA-2 indicating 242(n2); RA-4 indicating 5×242MRU(n1); RA-6 indicating 3×242MRU(n3); RA-8 indicating 3×242MRU(n3)".

[0171] n1, n2, n3, n4 are the numbers of stations on the large MRU in CC1 or CC2.

[0172] In the above embodiment, only the common part of the EHT-SIG is described, and the user-specific field may be the same as the 802.11ax solution. The sequence of the user field is placed in the user-specific field of the corresponding EHT-SIG, and the mapping in the RU or MRU in the allocation is indicated by the RA field.

[0173] In some special situations, other types of MRUs than those indicated by the RA field may be indicated by the user field. [Embodiment 6]

[0174] The embodiments can be combined in a way that it can work, and can be modified in a way that it still works or works better, and the following are some examples: In embodiment 6a, a signaling method for small RUs is provided, in which the indication field in the common part of the EHT-SIG consists of two fields, namely the existing RA field and additional signaling of MRU allocation.

[0175] This method allows any combination of small RUs to be defined as MRUs while maintaining the definition of the 802.11ax 20 MHz allocation map (RU allocation subfield).

[0176] The indication consists of an RA field and additional signaling indicating which RU defined in the RA field is assigned as the MRU.

[0177] For example, the following mapping: {26,26+52,center 26,26,26,52} and want to allocate a mapping in which the second 26-RU and the second 52-RU include the MRU, first {26,26,52,center26,26,26,52} indicates an 8-bit RA field of "00000101" that defines the allocation map of Next, an MRU consisting of a second 26-RU and a second 52-RU will be specifically shown.

[0178] In this method, a single-user specific field will be indicated in the EHT-SIG for each MRU, see the single-user specific field specified in the embodiment. [Embodiment 6a]

[0179] In this embodiment, a method is provided for indicating MRU allocation using a bitmap where each bit corresponds to a particular RU defined in the RA field.

[0180] Each 20 MHz can contain up to 4 MRUs, so the MRU allocation field consists of 4 parts. Alternative solutions allow for 1, 2 or 3 MRUs.

[0181] First Part: The first MRU can be any combination of RUs defined in the RA field.

[0182] The maximum number of RUs in 20 MHz is 9, so 9 bits are used to cover all possible allocations. The actual number of bits used for MRU allocation is equal to the number of RUs defined in the RA field starting from the LSB or MSB of the 9 bits. If the number of RUs defined in the RA field is less than 9, the redundant bits are don't care bits.

[0183] For example, the RA field "00000101" defines the following RU allocation: [26,26,52,center 26,26,26,52].

[0184] A bitmap of 0011000 means that the middle 26-RUs of the second 52-RU are allocated as MRUs and two don't care bits are added to the bitmap.

[0185] Second Part: The second MRU can be any combination of RUs defined in the RA field and not included in the first MRU.

[0186] The maximum number of RUs excluding the first MRU is 7, therefore a 7-bit bitmap is used. The actual number of bits used for the second MRU is equal to the number of RUs defined in the RA field minus the number of RUs that make up the first MRU starting from the LSB or MSB of the 7 bits, with the redundant bits being don't care bits.

[0187] For example, following the allocations defined in the previous section, a bitmap of 11000 means that the first and second 26-RUs are allocated as MRUs and two don't care bits are added to the bitmap.

[0188] Third Part: The third MRU may be any combination of RUs defined in the RA field and not included in the first and second MRUs.

[0189] The maximum number of RUs excluding the first and second MRUs is 5, therefore a 5-bit bitmap is used. The actual number of bits used for the second MRU is equal to the number of RUs defined in the RA field minus the number of RUs that make up the first and second MRUs starting from the LSB or MSB of the 5 bits, with the redundant bits being don't care bits.

[0190] For example, following the allocations defined in the previous two sections, a bitmap of 011 means that the seventh 26-RU and the fourth 52-RU are allocated as MRUs.

[0191] Fourth Part: The fourth MRU may be any combination of RUs defined in the RA field and not included in the first, second, and third MRUs.

[0192] The maximum number of RUs excluding the first, second, and third MRUs is 3, so a 3-bit bitmap is used.

[0193] In this example, the common fields of the EHT-SIG include one or more RA fields, where each RA field is 8 bits, and one or more MRU allocation fields, which can be 9, 7, 5, or 3 bits, respectively.

[0194] In some alternative solutions, if a limited mode of MRU is defined, this embodiment may also be revised accordingly, for example, to include only bits of RUs that can be aggregated into the MRU. For example, if only 26RU-3, 26RU-4, 26RU-5, 26RU-6, and 26RU-7 can be aggregated into the MRU, the first MRU allocation field and the second MRU allocation field may occupy 5 bits and 3 bits, respectively. [Embodiment 6b]

[0195] In this embodiment, a method similar to that of embodiment 6a is provided, except that all bits in the bitmap of each portion defined in embodiment 6a are used to indicate the assigned MRU, excluding don't-care bits. Each bit in the bitmap corresponds to a specific 26-RU, and RUs greater than 26 are indicated by consecutive bits in the bitmap. For example, to assign the first 52-RU and the last 52-RU as the first MRU, a bitmap of "110000011" is defined, where the first two 1's correspond to the first 52-RU and the last two 1's correspond to the last 52-RU.

[0196] In this method, the common field of the EHT-SIG consists of an 8-bit RA field and a 9+7+5+3-bit MRU allocation field. [Embodiment 6c]

[0197] In this embodiment, the number of MRUs is indicated by the N_MRU field in the EHT-SIG in a similar manner to embodiments 6a and 6b. If the N_MRU field is set to zero, it means that no MRUs are allocated and the common fields of the EHT-SIG do not contain any bitmaps. If the N_MRU field is set to 1 / 2 / 3 / 4, it means that 1 / 2 / 3 / 4 MRUs are allocated and the corresponding number of bitmaps are included as defined in embodiments 6a and 6b.

[0198] In this method, the common field of the EHT-SIG consists of one or more RA fields (8 bits) and an MRU allocation field of zero, 9, 9+7, 9+7+5, or 9+7+5+3 bits depending on the number of MRUs indicated by the N_MRU bits. [Embodiment 6d]

[0199] In this embodiment, an additional resource allocation table is defined, which contains all defined combinations of MRUs. It can be an MRA field, i.e., a multiple resource allocation field. Each entry in the MRA defines a map, which can contain a single MRU or a combination of MRUs. The map defines only the MRU, while the complete 20 MHz allocation map is defined by the RA field.

[0200] For example, if a map of 20MHz or less is assigned,

[0201] [26,26,52+center 26,26,26,52] An RA field of "00000101" indicates a map of [26,26,52,middle 26,26,26,52], and a new MRA entry can be defined in which the second 52-RU and the middle 26-RU are allocated as a single MRU.

[0202] The new MRA field does not indicate any single RU, but only MRUs, so any RA field entries in which the second 52-RU and the central 26-RU are assigned can be combined with MRA fields in which those RUs are assigned as MRUs.

[0203] In this method, the common part of the EHT-SIG includes one or more RA fields (each RA field is 8 bits) and an additional N-bit MRA field.

[0204] The number of N bits defines the size of the MRA table, which has 2^N bit options for the MRU map.

[0205] FIG. 21 is a block diagram of an access point according to another embodiment of the present invention. The access point in FIG. 21 includes an interface 101, a processing unit 102, and a memory 103. The processing unit 102 controls the operation of the access point 100. The memory 103 may include read-only memory and random access memory and provides instructions and data for the processing unit 102. A portion of the memory 103 may further include non-volatile random access memory (NVRAM). All components of the access point 100 are coupled to each other using a bus system 109, which, in addition to a data bus, further includes a power bus, a control bus, and a status signal bus. However, for clarity of explanation, various buses are illustrated in FIG. 21 as the bus system 109.

[0206] The various frame transmitting methods disclosed in the above-described embodiments of the present invention may be applied to or implemented by the processing unit 102. In the implementation process, each step of the above-described method may be completed by an integrated logic circuit of hardware or instructions in software form in the processing unit 102. The processing unit 102 may be a general-purpose processor, a digital signal processor, an application-specific integrated circuit, a field programmable gate array or another programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component, and may implement or execute the various methods, steps, and logic block diagrams disclosed in the embodiments of the present invention. The general-purpose processor may be a microprocessor or any conventional processor, etc. The steps of the methods disclosed with reference to the embodiments of the present invention may be directly executed by a hardware processor or may be executed using a combination of processor hardware and software modules. The software modules may be located in a storage medium well-established in the art, such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory, an electrically erasable programmable memory, or a register. The storage medium may be located in the memory 103. The processing unit 102 reads the information in the memory 103 and completes the method steps described above in relation to the hardware of the processing unit 102 .

[0207] FIG. 22 is a block diagram of a station according to another embodiment of the present invention. The station includes an interface 111, a processing unit 112, and a memory 113. The processing unit 112 controls the operation of the station 110. The memory 113 may include read-only memory and random access memory and provides instructions and data for the processing unit 112. A portion of the memory 113 may further include non-volatile random access memory (NVRAM). All components of the station 110 are coupled to each other using a bus system 119, which, in addition to a data bus, further includes a power bus, a control bus, and a status signal bus. However, for clarity of explanation, the various buses are depicted in FIG. 22 as the bus system 119.

[0208] The methods for receiving various frames disclosed in the above-described embodiments of the present invention may be applied to or implemented by the processing unit 112. In the implementation process, each step of the above-described method may be completed by an integrated logic circuit of hardware or instructions in software form in the processing unit 112. The processing unit 112 may be a general-purpose processor, a digital signal processor, an application-specific integrated circuit, a field programmable gate array or another programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component, and may implement or execute the various methods, steps, and logic block diagrams disclosed in the present embodiments of the present invention. The general-purpose processor may be a microprocessor or any conventional processor, etc. Each step of the method disclosed with reference to the embodiments of the present invention may be performed directly by a hardware processor or may be performed using a combination of processor hardware and software modules. The software modules may be located in a storage medium well-established in the art, such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory, an electrically erasable programmable memory, or a register. The storage medium may be located in the memory 113. The processing unit 112 reads the information in the memory 113 and completes the method steps described above in relation to the hardware of the processing unit 112 .

[0209] In particular, the memory 113 stores received information that enables the processing unit 112 to perform the methods mentioned in the above embodiments.

[0210] The detailed description set forth above in connection with the accompanying drawings describes examples and does not represent the only examples that may be implemented or within the scope of the claims. The terms "example" and "exemplary," as used herein, mean "serving as an example, instance, or illustration" and do not mean "preferred" or "advantageous over other examples." The detailed description includes specific details for the purpose of providing an understanding of the described techniques. However, these techniques may be practiced without these specific details. In some instances, well-known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.

[0211] Information and signals may be represented using any of a variety of different technologies and techniques. For example, the data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0212] The various example blocks and components described in connection with the disclosure herein may be implemented or performed using a general-purpose processor, a digital signal processor (DSP), an ASIC, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof, designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but alternatively, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

[0213] The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored on or transmitted as one or more instructions or code on a computer-readable medium. Other examples and implementations are within the scope and spirit of this disclosure and the appended claims. For example, depending on the nature of the software, the functions described above may be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination thereof. Features implementing the functions may also be physically located in various locations, including being distributed so that portions of the functions are implemented in different physical locations. As used herein, including in the claims, the term "and / or," when used in a list of two or more items, means that any one of the listed items may be used alone, or a combination of two or more of the listed items may be used. For example, if a configuration is described as including components A, B, and / or C, the configuration may include A alone; B alone; C alone; a combination of A and B; a combination of A and C; a combination of B and C; or a combination of A, B, and C. Also, as used in this specification, including the claims, "or" used in a list of items (e.g., a list of items followed by a phrase such as "at least one of" or "one or more of") indicates a disjunctive list, such as "at least one of A, B, or C" meaning the list A, or B, or C, or AB, or AC, or BC, or ABC (i.e., A and B and C).

[0214] Computer-readable media includes both computer storage media and communication media, including any medium that facilitates transfer of a computer program from one place to another. Storage media may be any available medium that can be accessed by a general-purpose or special-purpose computer. By way of example, and not limitation, computer-readable media may include RAM, ROM, EEPROM, flash memory, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to hold or store desired program code means in the form of instructions or data structures and that can be accessed by a general-purpose or special-purpose computer or a general-purpose or special-purpose processor. Also, any connection is properly termed a computer-readable medium. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included within the definition of medium. Disk and disc, as used herein, includes compact discs (CDs), laser discs, optical discs, digital versatile discs (DVDs), floppy disks, and Blu-ray discs, although disks typically reproduce data magnetically, while discs reproduce data optically using lasers. Combinations of the above are also included within the scope of computer-readable media.

[0215] The previous description of the disclosure is provided to enable any person skilled in the art to make or use the disclosure. Various modifications to the disclosure will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the scope of the disclosure. Thus, the disclosure is not intended to be limited to the examples and designs described herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

[0216] It should be understood that "an embodiment," or "an embodiment" as used throughout the specification, does not imply that a particular feature, structure, or characteristic related to that embodiment is included in at least one embodiment of the present invention. Thus, the appearances of "in one embodiment" or "in an embodiment" throughout this specification do not refer to the same embodiment. Furthermore, these particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. The sequence numbers of the processes described above do not imply an execution order in various embodiments of the present invention. The execution order of the processes should be determined according to the function and internal logic of each process and should not be construed as any limitation on the implementation process of the embodiments of the present invention.

[0217] Those skilled in the art may recognize that, in combination with the examples described in the embodiments disclosed herein, the units and algorithm steps may be implemented by electronic hardware, computer software, or a combination thereof. To clearly describe the compatibility between hardware and software, the above description generally describes the components and steps of each embodiment according to their functions. Whether these functions are performed by hardware or software depends on the specific application and the design constraints of the technical solution. Those skilled in the art may use different methods to implement the described functions for each specific application, but such implementations should not be considered to go beyond the scope of the present invention.

[0218] For the purpose of simple and concise description, those skilled in the art will clearly understand that for the detailed operation processes of the aforementioned systems, devices and units, reference may be made to the corresponding processes in the aforementioned method embodiments, and the details will not be described again herein.

[0219] In some embodiments provided herein, it should be understood that the disclosed systems, devices, and methods may be implemented in other ways. For example, the described device embodiments are merely examples. For example, the division of units is merely a division of logical functions, and other divisions may occur in actual implementation. For example, multiple units or components may be combined or integrated into another system, and some functions may be omitted or not performed. In addition, the shown or described interconnections, i.e., direct connections or communication connections, may be implemented via some interfaces. Indirect connections or communication connections between devices or units may be implemented in electronic, mechanical, or other forms.

[0220] The units described as separate parts may or may not be physically separate, and the parts shown as units may or may not be physical units, and may be located in one place or distributed over multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the solutions of the embodiments of the present invention.

[0221] Furthermore, the functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit. The integrated unit may be implemented in the form of hardware or in the form of a software functional unit. [Other possible items] [Item 1] 1. An apparatus for wireless communication, comprising: a memory for storing instructions; a processor coupled to the memory, wherein the processor and the memory: Generating a signaling field (SIG) in a wireless local area network (WLAN), the SIG including an RU assignment field indicating the size and location of each resource unit (RU) in a frequency resource, the SIG further including one or more user fields, each user field including information of a scheduled station (STA), and an MRU including multiple RUs can be assigned to one or more of the same STAs; transmitting said SIG; The apparatus is configured to: [Item 2] 1. An apparatus for wireless communication, comprising: a memory for storing instructions; a processor coupled to the memory, wherein the processor and the memory: Receiving a signaling field (SIG) in a wireless local area network (WLAN), the SIG including an RU assignment field indicating the size and location of each resource unit (RU) in a frequency resource, the SIG further including one or more user fields, each user field including information of a scheduled station (STA), and an MRU including multiple RUs can be assigned to one or more of the same STAs; processing the SIG; The apparatus is configured to: [Item 3] 3. The device of claim 1, wherein the MRU is a small MRU including a combination of 26-RU, 52-RU, or 106-RU in a 20 MHz frequency segment, or the MRU is a large MRU including a combination of 242-RU, 484-RU, or 996-RU in the transmission bandwidth. [Item 4] 3. The device of claim 1, wherein the MRU includes a first RU and a second RU, the SIG includes a first user field corresponding to the first RU and a second user field corresponding to the second RU, and both the first user field and the second user field include the same ID of the STA. [Item 5] The second user field is: the number of RUs assigned to said STA, or the size and location of each RU in the MRU assigned to the STA; Item 5. The device of item 4, further comprising one or any combination of: [Item 6] 3. The device of claim 1, wherein the common field of the SIG includes information on the number of small MRUs allocated in the corresponding 20 MHz frequency segment and / or information on the number of the large MRUs allocated in the bandwidth of the transmission. [Item 7] The device described in item 1 or 2, wherein the SIG includes a single RU user field and an MRU user field, the single RU user field corresponds to an RU that is not an MRU, and the MRU user field corresponds to an MRU that includes at least the following: an STA_ID and an RU bitmap indicating the size and position of each RU included in the MRU. [Item 8] 3. The apparatus of claim 1, wherein the SIG includes a common MRU field indicating which 26 RUs are included in the MRU in the corresponding 20 MHz frequency segment and / or which 242 RUs are included in the MRU in the bandwidth of the transmission. [Item 9] 3. The apparatus of claim 1, wherein the SIG includes one or more common MRU fields, each common MRU field indicating which actual allocated RUs are within the MRU. [Item 10] 3. The apparatus of claim 1, wherein the SIG includes puncturing information indicating non-contiguous large RUs and one or more user fields corresponding to the non-contiguous large RUs, and each of the one or more user fields includes information of a different station. [Item 11] 1. A method for wireless communication, comprising: generating a signaling field (SIG) in a wireless local area network (WLAN), the SIG including an RU assignment field indicating the size and location of each resource unit (RU) in a frequency resource, the SIG further including one or more user fields, each user field including information of a scheduled station (STA), and an MRU including multiple RUs can be assigned to one or more of the same STAs; transmitting the SIG; A method comprising: [Item 12] 1. A method for wireless communication, comprising: receiving a signaling information (SIG) in a wireless local area network (WLAN), the SIG including an RU assignment field indicating a size and a location of each resource unit (RU) in a frequency resource, the SIG further including one or more user fields, each user field including information of a scheduled station (STA), and an MRU including multiple RUs can be assigned to one or more of the same STAs; processing the SIG; A method comprising: [Item 13] Item 13. The method of item 11 or 12, wherein the MRU is a small MRU including a combination of 26-RU, 52-RU, or 106-RU in a 20 MHz frequency segment, or the MRU is a large MRU including a combination of 242-RU, 484-RU, or 996-RU in the transmission bandwidth. [Item 14] Item 13. The method of item 11 or 12, wherein the MRU includes a first RU and a second RU, the EHT-SIG includes a first user field corresponding to the first RU and a second user field corresponding to the second RU, and both the first user field and the second user field include the same ID of the STA. [Item 15] The second user field is: the number of RUs assigned to said STA, or the size and location of each RU in the MRU assigned to the STA; Item 13. The method of item 12, further comprising one or any combination of: [Item 16] Item 13. The method of item 11 or 12, wherein the common field of the SIG includes information on the number of small MRUs allocated in the corresponding 20 MHz frequency segment and / or information on the number of the large MRUs allocated in the bandwidth of the transmission. [Item 17] Item 13. The method of claim 11, wherein the SIG includes a single RU user field and an MRU user field, the single RU user field corresponds to an RU that is not an MRU, and the MRU user field corresponds to an MRU that includes at least the following: an STA_ID and an RU bitmap indicating the size and position of each RU included in the MRU. [Item 18] Item 13. The method of item 11 or 12, wherein the SIG includes a common MRU field indicating which 26 RUs are included in the MRU in the corresponding 20 MHz frequency segment and / or which 242 RUs are included in the MRU in the bandwidth of the transmission. [Item 19] Item 13. The method of item 11 or 12, wherein the SIG includes one or more common MRU fields, each common MRU field indicating which actual allocated RU is within the MRU. [Item 20] Item 13. The method of item 11 or 12, wherein the SIG includes puncturing information indicating non-contiguous large RUs and one or more user fields corresponding to the non-contiguous large RUs, each of the one or more user fields including information of a different station.

Claims

1. 1. A method for wireless communication, comprising: receiving a signaling field (SIG), the SIG including a resource unit (RU) allocation field indicating a size and location of a resource unit (RU) or a minimum resource unit (MRU) in a frequency resource, and one or more user fields, each of the one or more user fields including a STA identifier (STA_ID) of a scheduled station (STA); The MRU including a plurality of RUs is assigned to one or more STAs, and the RU assignment field indicates the size and location of each RU included in the MRU; the one or more user fields include a single RU user field and an MRU user field, the single RU user field corresponding to an RU that is not an MRU, and the MRU user field corresponding to an MRU; processing the SIG; A method comprising:

2. 2. The method of claim 1, wherein the MRU is a small MRU comprising a combination of 26-RU, 52-RU, or 106-RU in a 20 MHz frequency segment, and the MRU is a large MRU comprising a combination of 242-RU, 484-RU, or 996-RU in a transmission bandwidth.

3. 2. The method of claim 1, wherein the common field of the SIG includes at least one of information on the number of small MRUs allocated in a corresponding 20 MHz frequency segment and information on the number of large MRUs allocated in a transmission bandwidth.

4. 2. The method of claim 1, wherein the SIG includes a common MRU field that indicates which 26-RUs are included in the MRU in the corresponding 20 MHz frequency segment and which 242-RUs are included in the MRU in the bandwidth of the transmission.

5. The method of claim 1 , wherein the SIG includes one or more common MRU fields, the common MRU fields indicating which RUs are within an MRU.

6. 2. The method of claim 1, wherein the SIG includes puncturing information indicating non-consecutive large RUs and one or more user fields corresponding to the non-consecutive large RUs, the one or more user fields including information of different stations.

7. 1. An apparatus for wireless communication, comprising: a memory for storing instructions; a processor coupled to the memory, the processor comprising: A procedure for receiving a signaling field (SIG), the SIG including a resource unit (RU) allocation field indicating a size and a location of an RU or an MRU in a frequency resource, and one or more user fields, each of the one or more user fields including a STA identifier (STA_ID) of a scheduled station (STA); The MRU including a plurality of RUs is assigned to one or more STAs, and the RU assignment field indicates the size and location of each RU included in the MRU; the one or more user fields include a single RU user field and an MRU user field, the single RU user field corresponding to an RU that is not an MRU, and the MRU user field corresponding to an MRU; a step of processing the SIG; 20. An apparatus configured to execute the instructions in the memory to cause the processor to execute:

8. 8. The apparatus of claim 7, wherein the MRU is a small MRU including a combination of 26-RU, 52-RU, or 106-RU in a 20 MHz frequency segment, or the MRU is a large MRU including a combination of 242-RU, 484-RU, or 996-RU in a transmission bandwidth.

9. 8. The apparatus of claim 7, wherein the common field of the SIG includes at least one of information on the number of small MRUs allocated in a corresponding 20 MHz frequency segment and information on the number of large MRUs allocated in a transmission bandwidth.

10. 8. The apparatus of claim 7, wherein the SIG includes a common MRU field that indicates at least one of which 26-RUs are included in the MRU in a corresponding 20 MHz frequency segment and which 242-RUs are included in the MRU in a bandwidth of transmission.

11. The apparatus of claim 7 , wherein the SIG includes one or more common MRU fields, the common MRU fields indicating which RUs are within an MRU.

12. 8. The apparatus of claim 7, wherein the SIG includes puncturing information indicating non-consecutive large RUs and one or more user fields corresponding to the non-consecutive large RUs, the one or more user fields including information of different stations.

13. 1. An apparatus for wireless communication, comprising: a memory for storing instructions; An apparatus comprising: a processor coupled to the memory, the processor configured to execute instructions in the memory that cause the processor to perform the method of any one of claims 1 to 6.

14. 10. A non-transitory computer-readable storage medium configured to store instructions that, when executed by a processor, cause the processor to perform the method of any one of claims 1 to 6.

15. A computer program causing a computer unit to carry out the steps of the method according to any one of claims 1 to 6.

Images