RESOURCE ALLOCATION SIGNALING IN WIRELESS LOCAL AREA NETWORK PREAMBLE

Abstract

A wireless communication apparatus comprising: a memory that stores instructions; and a processor coupled with the memory, wherein the processor and memory are configured to: generate a signaling field, SIG, in a wireless local area network, WLAN, the SIG comprising a resource unit allocation field, RU, indicating a size and location of each RU in a frequency resource, the SIG further comprising one or more user fields, each user field comprising information of a programmed station, STA; wherein an MRU comprising multiple RUs is permitted to be allocated to an STA; and transmit the SIG.

Description

RESOURCE ALLOCATION SIGNALING IN WIRELESS LOCAL AREA NETWORK PREAMBLE ML / t / ZUZZ / U í 1Z44 FIELD OF INVENTION The present invention relates to wireless communication, and more particularly to a new method of signaling resource allocation in a WLAN and apparatus. BACKGROUND OF THE INVENTION The IEEE 802.11ax standard first introduced OFDMA modulation. The description of which RUs are used for a given PPDU is provided in its SIG-B field (and is defined in detail in the 802.11ax standard, illustrated in Figure 1). This field is composed of two main subfields: the common field and the user-specific field, as shown in the 802.11ax standard. The 802.11ax standard limits each non-AP STA to using a single resource unit (RU) composed of contiguous tones (subcarriers). Although several RU sizes are defined in the standard (e.g., 26, 52, 106, 242, 484, 996 tones), restricting allocation to a single RU limits channel resource utilization. As mentioned earlier, the current 802.11ax standard (i.e., the previous technology) has six RU sizes. During the allocation process, the programmer can only assign a single RU to a given STA in a MU-PPDU (Multi-User Physical Protocol Data Unit - the transmitted packet) or SU-PPDU (Single-User PPDU) transmission. If there is an unassigned RU, it cannot be assigned to an STA that has already received an RU. BRIEF DESCRIPTION OF THE INVENTION The present invention is intended to expand and improve the method of utilizing channel resources in WLAN. Computer-readable methods, devices, and media for resource allocation signaling in an extremely high-performance wireless local area network (WLAN) are disclosed. A device such as an access point (AP) can generate a signaling field, SIG. The SIG comprises a resource unit (RU) assignment field, indicating the size and location of each RU within a frequency resource. The SIG further comprises one or more user fields, each user field containing information about a programmed station (STA); where a multiple RU comprising multiple RUs (MRU) is permitted to be assigned to one or more STAs. The RU comprises a RU defined in 802.11ax. MRU can be a small MRU comprising a combination of 26-RU, 52-RU, or 106-RU in a 20 MHz frequency segment; or a large MRU comprising a combination of 242-RU, 484-RU, or 996-RU in the transmission bandwidth. In some examples, the MRU comprises a first RU and a second RU. Device 5 can generate a first user field corresponding to the first RU and a second user field corresponding to the second RU. Both the first and second user fields comprise the same STA ID. The second user field can also include one or any combination of the following: the number of RUs assigned to the STA; or the size and location of each RU within the MRU assigned to the STA. Alternatively, the device can generate a common GIS field comprising information for a small MRU allocated in a corresponding 20 MHz frequency segment; and / or information for a large number of MRUs allocated in the transmission bandwidth. Alternatively, the device can generate a single RU user field and an MRU user field. The single RU user field corresponds to a RU that is not an MRU. The MRU user field corresponds to an MRU, comprising at least the following: a STA_ID, and a RU bitmap indicating the size and location of each RU contained within the MRU. Alternatively, the device can generate a Common-MRU field indicating which 20 26-RUs are included in an MRU in a corresponding 20 MHz frequency segment; and / or a Common-MRU field indicating which 242-RUs are included in an MRU in a transmission bandwidth. Alternatively, the device can generate one or more common-MRU fields, each common-MRU field indicating whether an actual assigned RU is in an MRU (which 25 actual assigned RUs are in an MRU). In addition, other information such as channel drilling information in a U-GIS can be used to indicate MRU assignment. Drilling information indicates a large non-contiguous RU and one or more user fields corresponding to the large non-contiguous RU, where each of the one or more user fields comprises information from a different station. One or more stations (e.g., mobile or wireless devices) can receive the WLAN preamble, including the SIG. One or more stations can then determine an MRU, which comprises multiple RUs assigned to the STA based on the SIG. The stations can then determine an MRU assigned to the STA by: 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 comprising the same STA ID; 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 location of each RU in the MRU assigned to the STA; or a common SIG field comprising information for the assigned small MRU in a corresponding 20 MHz frequency segment; and / or information for a number of the assigned large MRUs in the transmission bandwidth, or a single-RU user field and an MRU user field; the single-RU user field corresponds to a RU that is not an MRU; the MRU user field corresponds to an MRU, comprising at least the following: a STAJD and a RU bitmap indicating the size and location of each RU comprised in the MRU;or a Common MRU field indicating which 26-RUs are comprised in an MRU in a corresponding 20 MHz frequency segment; and / or a Common MRU field indicating which 242-RUs are comprised in an MRU in a transmission bandwidth; or one or more Common MRU fields, each Common MRU field indicating whether an actual assigned RU is in an MRU (which actual assigned RUs are in an MRU); or other information such as piercing information indicating a non-contiguous large RU and one or more user fields corresponding to the non-contiguous large RU, each of one or more user fields comprising information from a different station. The aforementioned fields in the GIS can have a balanced load across the content of two or more channels. The mapping between the MRU (RU if it exists) and the STA is indicated by the field structure and the field locations in the GIS. Methods executed by the apparatus, including the AP and stations, are also provided; computer-readable means for signaling and resource allocation are also provided. Some examples of the non-transient computer-readable methods, devices, or media described herein may also include processes, features, means, or instructions for resource allocation signaling in an extremely high-performance WLAN preamble. A further scope of applicability of the systems, methods, devices, or computer-readable media described herein will become apparent from the following detailed description, claims, and drawings. The detailed description and specific examples are provided for illustrative purposes only, as various changes and modifications within the scope of the description will become apparent to those skilled in the art. ML / t / ZUZZ / U í Ί Z44 BRIEF DESCRIPTION OF THE FIGURES The foregoing, as well as other objectives and features of the present invention, will become apparent from the following description of the preferred embodiments provided in conjunction with the accompanying drawings, in which: Figure 1 is a diagram illustrating the GIS-B field (and defined in detail in the 802.11ax standard); Figure 2 is a diagram showing an example of a wireless local area network; Figure 3 is a flowchart that illustrates how to communicate scheduling information in WLAN on one transmission side; Figure 4 is a flowchart illustrating how to communicate scheduling information in WLAN on a receiving side; Figure 5 is a diagram that illustrates an example of a modality 1 indication structure; Figure 6 is a diagram that illustrates another example of resource allocation in a 15 modality; Figure 7 is a diagram that illustrates another example of an indication structure in a modality; Figure 8 is a diagram that illustrates another example of an indication structure in a modality; Figures 9a, 9b, 9c are diagrams that illustrate examples of the common field of the EHT- NEXT; Figure 10a is a diagram that illustrates an example of resource allocation and the scheduled station in the RU(s); Figure 10b is a diagram illustrating an example of a common EHT-SIG field 25 structure which indicates the resource allocation of Figure 10a; Figure 11a is a diagram illustrating an example of the user-specific field structure of the EHT-SIG in one mode; Figure 11b is a diagram that illustrates an example of the structure for the MRU user field in the user-specific field of an EHT-SIG; Figure 12a and Figure 12b are diagrams that illustrate a structure of user fields in a specific user field of an EHT-SIG; Figure 13 is a diagram that illustrates simulation results; Figure 14 is a diagram that illustrates another example of an indication structure of a Common-Uniform Rectilinear Motion (CMR) motion; Figure 15 is a diagram that illustrates an example of resource allocation and RU mapping in one modality; ML / t / ZUZZ / U í 1Z44 Figure 16 is a diagram that illustrates an example of resource allocation and RU mapping in one modality; Figure 17a is a diagram that illustrates another example of resource allocation in one modality; Figure 17b is a diagram illustrating a structure indicating the allocation of resources in Figure 17a; Figure 17c is a diagram that illustrates another resource allocation indication structure in Figure 17a; Figure 18 is a diagram that illustrates another example of resource allocation and its 10 indication structure; Figure 19 is a diagram that illustrates an example of a transmission containing a mixed type of MRU; Figure 20 is a diagram that illustrates another example of resource allocation in one modality; Figure 21 is a block diagram of an access point according to an embodiment of the present invention; and Figure 22 is a block diagram of a station according to an embodiment of the present invention. DETAILED DESCRIPTION OF THE INVENTION A method of utilizing the channel resources in 802.11 will be explained hereafter with reference to the accompanying drawings, allowing STAs to utilize multiple, non-contiguous portions of the channel according to an embodiment of the present invention. For ease of understanding, the following explains terms that may appear in the following formats: MA / t / ZUZZ / U / 1Z44 25 AP access point AT access terminal BSS basic services suite BW bandwidth CC content channel 30 DL downlink DS distribution system EHT extremely high throughput ESS extended services suite HE high efficiency 35 LLC logical link control L-LTF Long Training Field No-HT L-SIG L-STF Non-HT Signal Field Short Training Field Non-HT LTF Long Training Field MAC Medium Access Protocol 5 MCS Modulation and Coding Scheme MLD Multi-Link Device MRU Multiple Resource Units MS Mobile Station MU Multi-User 10 MU-MIMO Multi-User Multiple-Input Multiple-Output NDP PPDU Null Data OFDM Orthogonal Frequency Division Multiplexing OFDMA Orthogonal Frequency Division Multiple Access PHY Physical Layer 15 PPDU Protocol Data Unit PHY RA RU Allocation Field RL-SIG Non-HT Signal Field Repeated RU Resource Unit SAP Service Access Point 20 SS Subscriber Station STA Subscriber Station SU Single User TDLS Tunneled Direct Link Configuration TID Traffic Identifier 25 TXOP Transmit Opportunity UE User Equipment UL Uplink U-SIG Universal Signal Field WM Wireless Medium 30 Figure 2 illustrates an example of a wireless local area network (WLAN) 100 that supports resource allocation signaling or scheduling signaling in a WLAN preamble (for example, a WLAN EHT preamble) in accordance with various aspects of this disclosure. WLAN 100 includes one access point (AP) 105 and stations (STAs) 110 labeled STA 1 through STA 6. The STAs 110 can represent devices such as wireless communication terminals, including mobile stations, telephones, 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 illustrated, WLAN 100 can have multiple APs 105. The STAs 110 can also be referred to as a mobile station (MS), mobile device, access terminal (ATs), user equipment (UE), subscriber station (SS), or subscriber unit. The STAs 110 associate and communicate with the AP 105 through a communication link 115. Each AP 105 has a coverage area 125 so 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 is stationary, mobile, or a combination of both. Devices in WLAN 100 can communicate over unlicensed spectrum, which may be a portion of the spectrum that includes frequency bands traditionally used by Wi-Fi technology, such as the 5 GHz band, the 2.4 GHz band, the 60 GHz band, the 3.6 GHz band, and / or the 900 MHz band. Unlicensed spectrum may also include other frequency bands. One or more of the STAs 110 and / or APs 105 may comprise a resource allocation signaling component 130, which may allow the STAs 110 and / or APs 105 to signal resource allocations in a WLAN preamble, for example, as further discussed below with reference to the figures. Although not shown in Figure 2, a STA 110 can be covered by more than one AP 105 and can therefore be associated with multiple AP 105s at different times. A single AP 105 and its associated set of STA 110s are 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 AP 105s within an Extended Service Set. A coverage area for an AP 105 can be divided into sectors that constitute only a portion of the coverage area. WLAN 100 includes AP 105s of different types (e.g., metropolitan area, home network, etc.), with varying coverage area sizes and overlapping coverage areas for different technologies. Although not shown, other devices can communicate with the AP 105. Although STAs 110 have the ability to communicate with each other through AP 105 using communication links 115, STAs 110 can also communicate directly with each other through direct wireless communication links 120. Direct wireless communication links can occur between STAS 110 regardless of whether any of the STAs are connected to an AP 105. Examples of direct wireless communication links 120 include direct Wi-Fi connections, connections established using a Tunneled Direct Link Setup (TDLS) Wi-Fi Connection, and other peer-to-peer (P2P) group connections. ML / t / ZUZZ / U í 1Z44 The STAs 110 and APs 105 shown in Figure 1 communicate according to the IEEE 802.11 baseband and radio protocol including physical (PHY) and media access control (MAC) layers, 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. Transmissions to / from STAs 110 and APs 105 often include UL (uplink) or DL ​​(downlink) transmissions. In downlink transmissions, control information within a header is transmitted prior to data transmissions. The information provided in a header is used by a device to decode subsequent data. Extremely high-performance WLAN preambles can be used to program multiple devices, such as STAs 110, for simultaneous single-user transmissions (e.g., single-user orthogonal frequency-division multiple access (SU OFDMA)) and / or MU-MIMO transmissions. For example, the WLAN EHT signaling field can be used to signal a resource allocation pattern to multiple receiving STAs 110.The WLAN EHT signaling field includes a common field that is decodable by multiple STA110s. This common field includes a resource allocation field. The resource allocation field indicates resource unit distributions to the multiple STA110s and specifies which resource units in a resource unit distribution correspond to MUMIMO transmissions and which correspond to single-user OFDMA transmissions. Following the common field, the WLAN EHT signaling field also includes dedicated user fields that are assigned to a specific STA110. The order in which the dedicated user fields are generated corresponds to the assigned resource units (for example, the first dedicated user field corresponds to the first assigned resource unit). The WLAN EHT signaling field is transmitted with a WLAN preamble to the multiple STA110s. It is not limited that some of the modes may be used in uplink transmission, that is, some of the features or solutions are used in a trigger that triggers an uplink transmission. One modality comprises a method for communicating programming information in WLAN, as illustrated in Figure 3: 101. Generate a GIS (such as an EHT-GIS) comprising indication information or programming information, through a device such as an access point. The verb generate may be replaced by construct, obtain, or determine. 102. Transmit the GIS, through the device. Therefore, another modality comprises a method on a non-AP station, receiving programming information on WLAN, as illustrated in Figure 4. MA / t / ZUZZ / U í Ί Z44 201. Receive a PPDU, which includes a GIS (such as EHT-GIS). The GIS may be in the analyzed structure in the following forms. A PPDU may include L-STF, L-LTF, L-GIS, RL-GIS, a U-GIS, and an EHT-GIS. There may be a two-symbol OFDM U-SIG, co-encoded in the EHT preamble immediately following the RL-SIG. The U-SIG contains version-independent fields. The intent 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. There may be a variable-length modulation and coding scheme (MCS) and EHT-SIG immediately following the U-SIG in an EHT PPDU sent to multiple users. 202. Process the GIS. Specifically, obtain scheduling information based on the GIS. EHT-SIG is a field name used to differentiate it from other GIS-Bs, such as VHT15 GIS-B and HE-GIS-B. EHT-SIG can be renamed in other ways; that is, the name itself is not important, but the content and structures analyzed and described in the following modalities provide the solution for efficient scheduling of resources and stations. First, in the modalities, through the EHT-SIG, a resource unit (RU) assignment field indicates at least one sequence of RUs (size and location of each RU) in a frequency domain, and may also indicate information necessary to calculate the number of users assigned to each RU. The EHT-SIG further comprises one or more user fields, each user field comprising information for a programmed station (STA); where multiple contiguous or non-contiguous RUs defined in 802.11ax (probably referred to as MRU, or MRU) are permitted to be assigned to one or more STAs. “MRU” as used herein generally refers to the RU that is a combination of the multiple contiguous or non-contiguous RUs defined, for example, in 802.11ax. These can be taken as newly defined RUs in the next generation of 802.11ax, for example, 802.11be. Compared to 802.11ax, each RU Assignment subfield in a 30-channel EHT-SIG content corresponding to a 20 MHz frequency segment indicates the RU assignment, including the size of the RU(s) and their placement in the frequency domain, and one or more combinations of multiple RUs, to be used in the EHT modulated fields of the EHT MU PPDU in the frequency domain. It may also indicate information necessary to calculate the number of users assigned to each RU (non-MRU) and each combination of multiple RUs (MRU). In preferred modes, the subcarrier indices of the RUs meet the conditions in a table that can be defined in MA / t / ZUZZ / U í 1Z44 an 802.11be standard (RUs associated with each RU Allocation subfield for each EHT GIS content channel and PPDU bandwidth). One or more STAs can be assigned to the same MRU or RU (non-MRU) in an 802.11ax MU-MIMO format. This means that part of the RA subfield will define the number of STAs, similar to the 802.11ax definitions: 11000y2y1y0, 11001y2y1y0, and 11010y2y1y0 for 242-RU, 484-RU, and 996-RU, respectively. However, in 802.11be, a maximum of 16 STAs per RU can be supported; therefore, the modes may include an RU assignment (RA) field with a value of more than 8 bits, for example, 9 or 10 bits, to support the indication of the number of stations. For example: 11000y3y2y1 y0, indicating a 242-RU, in which the number of stations in the 242-RU is indicated by y3y2y1y0, which is equal to y3y2y1y0+1; 11001y2y1y0 indicating a 484-RU, in which the number of stations in the 484-RU is indicated by y3y2y1y0, which is equal to y3y2y1y0+1; 11010 y3 y2y1y0, indicating a 996-RU, in which the number of stations in the 99615 RU is indicated by y3y2y1 y0, which is equal to y3y2y1 y0+1. The following modalities omit the difference (if any) in the RA between 802.11ax and 802.11be to make the modality solutions or examples more concise. That is, RA values ​​used in the following modality / examples can be replaced by new values ​​corresponding to 802.11be. In some modalities, the number of RUs that can be combined as an MRU is limited. That is, the limitation of MRUs can be defined; each MRU represents a size of multiple subcarriers and the location of those multiple subcarriers in the bandwidth, which overlaps multiple RUs as defined by 802.11ax. Based on the RUs defined in 802.11ax, for example, small RUs: 26, 52, or 106, 25, some examples of MRU combinations include: an MRU comprising {52, 26}, or {106, 26} within a 20 MHz band, a 40 MHz band, or an 80 MHz band. In some examples, only contiguous combinations of small RUs should be introduced; in some examples, non-contiguous configurations are also permitted. For large RUs: 242, 484, or 996, some reasonable preferred MRU combinations include: 1.242+484 (contiguous and non-contiguous, within each 80 MHz segment); 2. 242+242 (Perforated, non-contiguous case); 3.484+996; 4. 242+484+242+484; 5. 242+484+996; 6. 242+242+996, etc. MA / t / ZUZZ / U / 1Z44 Furthermore, based on a certain predefined MRU (i.e., a defined combination of 802.11ax RUs, also referred to as an MRU), a key issue is providing an efficient indication solution to display the MRU assignment and the corresponding information of the station scheduled within that MRU. In other words, Problem 5 lies in how to indicate the assignment and station information that allows for multiple RUs to be assigned to a station, and consequently, how the station knows whether it is scheduled and on which RU or MRU it is assigned, so that the station communicates on the assigned RU or MRU accordingly. Even now, the allocation of RUs is decided by the AP according to several criteria. For example, the AP may decide to use the RUs with the highest SNR for a specific 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 the MRU and those in the PPDU are for the same type of service. Specifically, in some of the modalities, a single FEO with the same 15 parameters (such as MCS, encoding, N_SS etc.) can be assigned to an STA assigned with the MRU. The aforementioned small and large RUs may not be assigned to the same MRU allocation, or it may be preferable not to allocate an MRU that includes both small and large RUs. Small RUs may not be allocated across multiple 20 channels of 20 MHz in preferred configurations. In simpler terms, the MRU comprises a combination of 26-RU, 52-RU, or 106-RU in a 20 MHz frequency segment; or the MRU comprises a combination of 242-RU, 484-RU, or 996-RU in a transmission bandwidth. However, the MRU may not comprise a combination of 26-RU, 52-RU, and 106-RU in the first 20 MHz and a combination of 242-RU, 484-RU, or 996-RU overlapping another 20 MHz. Some modes may have a certain exception which consists of a special small RU in a first 20 MHz channel being able to be combined with a RU in another 20 MHz channel. In some configurations, it is not restricted that MRUs of small RUs are comprised only of contiguous RUs. This can support programmers assigning RUs based on SNR (e.g., CQI feedback), and it would be efficient to allow any combination of MRUs. This is not limited to combinations of small RUs. Assuming the RMS delay spread is ~1 / 3CP = ~1 psec, then the coherence bandwidth is ~1 MHz. Therefore, an average SNR in a given RU does not imply approximately the average SNR in its adjacent RU. MA / t / ZUZZ / U í Ί Z44 In configurations based on support for multiple RUs / non-contiguous RUs, channel utilization is improved, making it more efficient due to the enhanced leverage of channel selectivity. Furthermore, improved channel utilization leads to increased overall system performance. Mode 1 An EHT-SIG in this mode is different from the HE-SIG B specified in 802.11ax, hereinafter: A corresponding multiple user field is allowed to point to the same STA. A common part is included in the EHT-SIG, and it is similar in structure to the common part of 10 HE-SIG B. However, multiple user fields for a STA are included within a user-specific field of the EHT-SIG. For example, a first user field is followed by duplicate second user fields. In simpler terms, an MRU comprises a first RU and a second RU. The EHT-SIG therefore comprises a first user field corresponding to the first RU and a second user field corresponding to the second RU. Both the first and second user fields contain the same station ID. The first user field may be similar to the user field as defined in 802.11ax, but there are different solutions for the other duplicate user fields, registered as a second duplicate user field(s), or the second user field. Specifically, in one example, the second duplicate user field is the same as the first user field. This example overcomes the drawback of having only one user / station field mapped to a RU, as defined in 802.11ax, thus being cost-efficient when designing a new chip. In another example, the second set of duplicate user fields includes the STAJD field and other subfields that carry new MRU-related signaling content instead. Compared to the first example, this solution supports MRU STAs more easily. In the examples mentioned above, the size of the user fields can be the same for everyone, for example, 21, 22, or 23 bits. The first user field could be identical or similar to the 802.11ax user field (the content or structure is essentially the same). Generally, the location of the second combined RU (corresponding to the duplicate user field) is not limited; but in some examples, the location rules for the second combined RU / duplicate user field are established to reduce interference or inefficiency. The content of other user fields can be one of the following: Example 1, remains the same as the first user field; Example 2 includes content that is different from the first user field such that: The first 11 bits are for STAID as in the first user field. Some of the other bits (e.g., 1 or 2) are used to signal the type of the user field (i.e., the meaning of the following bits). The remaining bits can have any combination of the following new content related to MRU: Two bits indicate N_RU – the number of RUs assigned to the STA (including the first RU), or how many RUs are included in the MRU assigned to the STA. Therefore, the STA can identify a failure to decode any of the user fields and stop the decoding process. Another 8 bits are reserved; these indicate the size and location of each RU in the MRU assigned to the STA. For example, in the following format: For small RUs, a 9-bit bitmap can indicate which 26-tone RUs on the same 20 MHz channel are part of the MRU allocation. A 52-tone RU can be indicated by the appropriate 2 bits; a 106-tone RU can be indicated by the appropriate 4 bits. The 10th bit is reserved. For large RUs: an 8-bit bitmap can indicate which 242-tone RUs on the same 80 MHz channel and the next 80 MHz channel are part of the MRU allocation. A 484-tone RU can be indicated by 2 bits (2 x 242-tone RU); a 996-tone RU can be indicated by 4 bits (4 x 242-tone RU). The 9th and 10th bits are reserved. The MRU is confined to 160 MHz limits in this mode. An STA can know if a MRU is assigned to this field after it has finished decoding EHT-SIG. Therefore, no special signaling is required for the MRU user field. Figure 5 illustrates an example of modality 1 indication structure. A RU assignment field (RA) in the common part of EHT-SIG is set to “00000100”, which represents the assignment of a sequence of RUs [26, 26, 52, center-26, 26, 26, 26, 26]. Therefore, in a specific user field, eight user fields (UFs) are included. In this example, UF1 is mapped to the first 26-RU, including information from STA1, such as STA1's AID. UF2 is mapped to the second 26-RU, including information from another STA; its content and structure could also be similar to a user field in 802.11ax. ML / t / ZUZZ / U / Ί Z44 UF3 corresponds to 52-RU. UF3 comprises a station information field that is also designated as the AID of STA1. The content of UF3 includes various examples: In one example, UF3 also includes a bitmap “101101000”, each bit of the bitmap corresponds to a 26-RU respectively, indicating which 26-RUs are in the MRU assigned / distributed to STA1. In the example, “101101000” means that the first / third / fourth / sixth 26-RUs are comprised as an MRU, which is assigned to STA1. In another example, UF3 alternatively includes an N-RU field instead of the bitmap. The N-RU field indicates the number of RUs in the RU sequence [26, 26, 52, center-26, 26, 26, 26, 26] that are combined as an MRU, which is assigned to STA1. In this example, the number of RUs is 3. Other UFs are also described in Figure 5. On the station side, an STA can obtain the size and location of the sequence of assigned RUs corresponding to 20 MHz of the RA field, and can also find out if the STA is programmed / assigned and in which of one or more RUs the STA is assigned. For example, STAs can obtain the assigned RU sequence corresponding to 20 MHz as a sequence of RUs [26, 26, 52, center-26, 26, 26, 26, 26], based on “00000100”, and also know that the STA is programmed and scheduled on the first, third, and 5th RUs in the above sequence of RUs (the first, third, and 5th being the order in the sequence) based on UF1, UF3, UF5. That is, the MRU comprised of “first 26-RU, second 52-RU, 6th 26-RU”, “first 26-RU, second 52-RU, 6th 26-RU” is the order in the 20 MHz tone plane. ML / t / ZUZZ / U í 1Z44 Table 27-7 Pilot subcarrier data and indices for RUs in a 20 MHz HE PPDU and in a PPDU 20 MHz non-OFDMA HE RU type RU index and subcarrier range 26-tone RU RUI [-121:-96] RU2 [-95:-'O] RU' [-6S: —43[ RU[-42:-1-] RU5 [-16: -4 4: 16] RUÓ [1' 42] RU' [43:63] RUS [%: 95] RUS [96: 121] RU 52-tone RUI [-121:-70] RU2 [-63:-1-] RU' [U: 6S] RU[-0: 121] RU 106-tone RUI [-122:-Π RU2 [Γ: 122[ RU 242-tone RUI [—122: —2, 2:122] The index of A subcarrier of 0 corresponds to the DC tone. Negative subcarrier indices correspond to subcarriers with frequencies lower than the DC tone, and positive subcarrier indices correspond to subcarriers with frequencies higher than the DC tone. RU 5 is the RU of 26 middle tones As shown in Figure 6, another example of resource allocation in mode 1 is illustrated, at 160 MHz, the first, third, fourth, and fifth 242-RUs are assigned to STA1; the sixth and eighth 242-RUs are assigned to STA2. There are different solutions for the content of the common part and the UFs in the EHT-SIG indicating the allocation in figure 6. The common part can be divided into two content channels (CC). In the example, the common part of CC1 comprises “11000000 (RA-1,242(1)), 01110010 (RA-3, 484(0)), 11000000 (RA-5, 242(1)), 11000000 (RA-7, 242(1))”; the common part of CC2 comprises “11000000 (RA-2, 242(1)), 11001000 (RA-4, 484(1)), 11000000 (RA-6, 242(1)), 11000000 (RA-8,242(1))”. The “11000000 (RA-1), 01110010 (RA-3), 11000000 (RA-5), 11000000 (RA-7)” in CC1 correspond to the first 20 MHz, the third 20 MHz, the fifth 20 MHz and the seventh 20 MHz respectively; The “11000000 (RA-2), 11001000 (RA-4), 11000000 (RA-6) and 11000000 (RA-8)” in CC2 correspond to the second 20 MHz, the fourth 20 MHz, the sixth 20 MHz and the eighth 20 MHz. The “11000000” indicates an allocation of 242(1), that is, 242-RU with 1 user field, “01110010” indicates an allocation of 484-RU with 0 user fields in the content channel that contains the corresponding 8-bit RU Allocation subfield “01110010”.“11001000” indicates a 484-RU allocation with 1 user field in the content channel containing the corresponding 8-bit RU Allocation subfield “11001000”. The common portion of CC1 together with the common portion of CC2 indicates the allocation of 160 MHz, i.e., the sequence of RUs [242, 242, 484, 242, 242, 242, 242]. See Figure 7. In the EHT-SIG, CC1 and CC2 are included. CC1 comprises UF1, UF5, and UF7, corresponding to RA1, RA5, and RA7, respectively. CC2 comprises UF2, UF4, UF6, and UF8, corresponding to RA2, RA4, RA6, and RA8, respectively. UF1 is the first user field comprising the ID of STA1. UF4 and UF5 are second user fields comprising the ID of STA1 (same for UF1) and a first bitmap, which is 8 bits, each of the 8 bits indicating whether a corresponding 242-RU 10 is in the MRU assigned to STA1 (for example 10111000 indicates that the first, third, 4th, 5th 242-RUs are assigned to STA1). UF6 and UF8 include the same ID as STA2. UF8 prefers to include a second bitmap, which is 8 bits or remaining bits except for the RUs already assigned in the first bitmap (i.e., 4 bits in this example). Each of the 8 bits indicates whether a corresponding 242-RU is in the MRU assigned to STA1 (for example, 10111000 indicates that the first, third, fourth, and fifth 242-RUs are assigned to STA1). UF2 and UF7 are user fields that are not assigned to an MRU; their details are not discussed here. In this example, if RU r is a 484-tone or larger RU, which is the largest predefined RU in an MRU, then the number of users assigned to MRU 20 equals the number of User fields for this RU r in the MRU summed across both EHT-SIG-B channel contents, i.e., Nuser(r, CC1) + Nuser(r, CC2), where r is the largest RU in the MRU. In the previous example, a 484-RU and a 242-RU are included in an MRU assigned to STA1; the number of users is determined by the 484-RU: n1 (the second 484-RU, CC1) + n2 (the second 484-RU, CC2) = 0 + 1 = 1. In this example, one station is assigned to MRU 25, but there is no restriction on multiple stations being assigned to the MRU. In the example in Figure 8, the resource allocation is similar, but the MRU1 which includes the 484-RU is allocated to two stations. In this example, the common part of CC1 comprises “11000000 (RA-1, 242(1)), 11001000 (RA-3, 484(1)), 11000000 (RA-5, 242(1)), 11000000 (RA-7, 242(1))”; the common part of CC2 comprises “11000000 (RA-2, 242(1)), 11001000 (RA-4, 484(1)), 11000000 (RA-6, 242(1)), 11000000 (RA-8, 242(1))”. The “11000000 (RA-1), 11001000 (RA-3), 11000000 (RA-5), “11000000 (RA-7)” in CC1 corresponds to the first 20 MHz, the third 20 MHz, the fifth 20 MHz, and the seventh 20 MHz, respectively; “11000000 (RA-2), 11001000 (RA-4), 11000000 (RA-6), 11000000 (RA-8)” in CC2 corresponds to the second 20 MHz, the fourth 20 MHz, the sixth 20 MHz, and the eighth 20 MHz. 35 “11000000” indicates an allocation of 242(1), i.e., 242-RU with 1 user field; “11001000” indicates an allocation of 484-RU with 1 user field in the content channel MA / t / ZUZZ / U / Ί Z44 containing the corresponding 8-bit RU Assignment subfield “11001000”. The common part of CC1 together with the common part of CC2 indicates the assignment of 160 MHz, i.e. the sequence of RUs [242, 242,484, 242, 242, 242, 242]. UF1 corresponds to the first 242-RU in MRU1, it is the first field of 5 user comprising the ID of STA1. UF3 and UF4 correspond to the same 484-RU in MRU1 assigned to two stations (indicated by RA3 and RA4), for example, STA1 and STA3, and should include the ID of STA1 and the ID of STA3, respectively. If UF3 includes the ID of STA1, then UF3 is a second user field for STA1 (indicating that the second 484-RU is in MRU1), also including a first bitmap, which has 8 bits, each of the 8 bits indicating whether a corresponding 242-RU is in the MRU assigned to STA1; UF4 includes the ID of STA3, so UF3 is a first user field for STA3. Alternatively, if UF3 includes the STA3 ID, UF3 is a first user field for STA3; UF4 can include the STA1 ID, UF3 is a second user field for STA1 (indicating that the second 484-RU is in the MRU), also including a first bitmap, which has 8 bits, each of the 8 bits indicating whether a corresponding 242-RU is in the MRU assigned to STA1. UF5 corresponds to RA5 (indicating the 5th 242-RU), it is a second user field comprising the ID of STA1 or STA3 (indicating that the 5th 242-RU is in MRU1) 20 and a first bitmap, which has 8 bits, each of the 8 bits indicating whether a corresponding 242-RU is in the MRU assigned to STA1 and STA3 (for example 10111000 indicates that the first, third, 4th, 5th 242-RUs are assigned to STA1 and STA3). UF6 and UF8 include the same ID as STA2. In UF8, it is preferred to include a second bitmap, which has 8 bits or remnant bits except for the RUs already assigned in the first bitmap (i.e., 4 bits in this example). Each of the 8 bits indicates whether a corresponding 242-RU is in the MRU assigned to STA1 (e.g., 10111000 indicates that the first, third, 4th, 5th 242-RUs are assigned to STA1). UF2 and UF7 are user fields that are not assigned to an MRU; the details are not discussed here. In this example, if RU r is a 484-tone or larger RU, which is the largest predefined RU in an MRU, then the number of users assigned to the MRU equals the number of User fields for this RU r in the integrated MRU 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 previous example, a 484-tone RU and a 242-tone RU are included in a 35 MRU assigned to STA1. The number of users is determined by the 484-tone RU: n1 (the second 484-tone RU, CC1) + n2 (the second 484-tone RU, CC2) = 1 + 1 = 2. In this example, two stations are assigned in the MRU, but this does not represent a limit to the number of stations that can be assigned to the MRU. In mode 1, by modifying the remaining bits in duplicate user fields, it is possible to indicate additional MRU information; and this solution does not require additional 5 entries in the RU Assignment subfield; and the definition and signaling of MRU is simple. Mode 2 In the second mode, the EHT-SIG includes a common field that accommodates additional RUs, and in which the RU assignment comprises combinations of RUs (MRU). 10 Additionally, a user-specific field has a subfield that defines MRU assignments, which is different from the 802.11ax user-specific field. Figures 9a, 9b, and 9c illustrate an example of the EHT-SIG common field. In the EHT-SIG common field, one or more fields are included in addition to an RA field and other information (for example, the RA field corresponding to a 20 MHz segment or a 40 MHz segment may be longer than in the prior art to allow more allocations or to allow more STAs to be allocated). One or more fields comprise a first field and / or a second field. The first field, NMRU1, corresponds to each 20 MHz segment in the overall bandwidth, which occupies N x 2 bits. The first field indicates the number of MRUs (a small MRU 20 comprises a RU of a small size, such as a 26-RU, a 52-RU, or a 106-RU) present in each 20 MHz channel. The second field, N_MRU_2, corresponds to the entire transmission bandwidth. It indicates the number of larger MRUs (a large MRU comprises a RU such as a 242-RU, a 484-RU, or a 996-RU) present in the transmission bandwidth. Specifically, NMRU2 is the same 25 for both CC1 and CC2 since it refers to the entire bandwidth. N MRU1 refers to each 20 MHz separately, so it is most likely to be different between CC1 and CC2. The details are as follows: The N_MRU_1 field (N x Nb bits) – which can also be called a small MRU field number – indicates the number of small MRUs assigned / existing in the corresponding 20 MHz channels / frequency segment. This field can be located following each RU assignment (RA) subfield in each content channel (CC) of the EHT-SIG. The total overhead of the N_MRU_1 field in the EHT-SIG can be N x 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 a RU combined from several small RUs with sizes of either 26, 52, or 106. There is no limitation on the RUs in a small MRU including different sizes of small RUs, nor is there a limitation on the small MRU being able to MA / t / ZUZZ / U / 1Z44 can be larger than 10⁶, but a small MRU is within 20 MHz; otherwise, a larger RU such as a 242-RU, 484-RU, 996-RU, or 2x996-RU can be indicated. It is likely that only a single MRU is available per 20 MHz frequency segment. Therefore, this field may require either 1 bit or 2 bits, so that if 1 bit is implemented, then 'T' indicates that there is an MRU in a corresponding 20 MHz frequency segment and 'O' indicates that there is no MRU in a corresponding 20 MHz frequency segment. This may also be useful later with Mode 3. The N_MRU_2 field—also known as the large MRU field number—indicates the number (quantity) of large MRU allocations existing across the entire bandwidth. This field may be located before the CRC and Tails fields of each CC, respectively, in the EHT-SIG. The total overhead in the N_MRU_2 field in the EHT-SIG can be 2 bits, where N is the number of 20 MHz frequency segments. A large MRU is a RU combined from several large RUs with sizes of either 242, 484, or 996. There is no limit to the number of different sizes of RUs within a large MRU, nor is there a limit to the size of the large MRU itself, but a large MRU is within the full transmission bandwidth. Figure 9a illustrates a structure of a common EHT-SIG B part in a 20 MHz bandwidth transmission. Figure 9b illustrates a structure of a common part of EHT-SIG B in a 40 MHz bandwidth transmission. Figure 9c illustrates a common part structure of EHT-SIG B in an 80 MHz bandwidth transmission. Other common part structures of EHT-SIG B in other bandwidths are similar and will not be repeated here. Figure 10a describes an example of resource allocation and the programmed station 25 in the RU(s). Figure 10b describes a common field structure of the EHT-SIG, which indicates the resource allocation of Figure 10a. The common field comprises: an RU allocation subfield “00000100” indicating the allocation represented by [26, 26, 52, center 26, 26, 26, 26]. The first field “10” indicates that there are 2 MRUs in the corresponding 20 MHz channel (the MRU for STA1 and the MRU for STA2 in Figure 9a above). The second field “00” indicates that there are no large RU MRUs. The common field also includes a RU assignment subfield “00001011” which indicates the assignment it represents [52, 26, 26, center 26, 52, 52]. The first field “10” indicates that there are 2 MRUs in the corresponding 20 MHz channel (the MRU for STA3 and STA4 in Figure 9a). The second field “00” indicates that there are no large RU MRUs. Figure 11a describes an example of a user-specific field structure of the EHT-SIG in this mode. The user-specific field includes 2 sub-fields: ML / t / ZUZZ / U í 1Z44 A user-specific MRU field normally precedes a single-RU-specific field. A single-RU-specific field comprises one or more of the single-RU user fields assigned in a single-RU, which is a normal RU not combined with any other RU(s). An MRU user field corresponding to an MRU comprises at least the following: a STAJD and a RU bitmap indicating the size and location of each RU included in the MRU. Figure 11b illustrates an example of the structure of the MRU user field in the EHT-SIG user-specific field. Figure 12a and Figure 12b illustrate a user field structure in a specific EHT-SIG user field, following the example in Figure 10a. The MRU user field contains the following information: a STAJD (11 bits), MCS (4 bits), Encoding (1 bit), a RU bitmap, said RU bitmap indicates RUs that belong to the same MRU allocation, CRC & Queue 15 (10 bits). Specifically, the RU bitmap indicating the size and location of each RU within the MRU can be indicated by at least two methods. For example, for small RUs there are 9 26-tone RUs, therefore the RU bitmap in each CC includes 9 bits, each bit mapping to a 26-RU, see Figure 12a. Alternatively, in another example, based on the RU allocation field indicating the RU sequence (e.g., Figure 10b), the number of RUs in each 20 MHz frequency segment can be extracted from the common field. The RU bitmap in each CC comprises several bits. The number of bits equals the number of RUs in the allocation of the 20 MHz frequency segments. Each bit maps one RU to the respective RU sequence; see Figure 12b. The RU bitmap in CC1 comprises 8 bits because the RU sequence in the first 20 MHz frequency segment comprises 8 RUs. Each bit maps one RU to the 8 RUs. The RU bitmap in CC2 comprises 6 bits because the RU sequence in the first 20 MHz frequency segment comprises 6 RUs; each bit maps one RU to the 6 RUs. In another example, for large RUs there are 16 242-tone RUs in a bandwidth (BW) of 320 MHz; similarly, the RU bitmap in a user field of an EHT-SIG may comprise 16 bits, each bit mapping to a 242-tone RU, indicating whether the 242-tone RU is included in the MRU. In the previous mode 2, by separating the MRU user-specific fields and the 35 RU-Unique user-specific fields, MRU information can be added, the same MA / t / ZUZZ / U í 1Z44 probability of error of SIG-B by STA. For MRU consisting of 3 or more RUs, the total size is reduced. Mode 3 In some modalities, new RU sizes are defined; this new size is called an MRU. Therefore, the RU allocation subfield comprises entries / indices indicating the allocation including the MRU. In this mode, the user-specific field will not be incremented because only one user field is required for each RU or MRU. In other words, it is not necessary to include multiple user fields corresponding to one MRU. As mentioned, the allocation of RUs is decided by the AP according to several criteria. The resources required by a station in a transmission are considered when determining the preferred RU or MRU. Table 1 below is an example of the required resources (especially smaller than 20 MHz) and the preferred RU or MRU based on the required resources. Table 1 Recursos más requiados (número de subportadoras) por una estación RU / MRUs / ancho de banda completo 1x26 26-RU 2x26 26+26 MRU; 52-RU; 3x26 26+26+26 MRU; 52+26 MRU 4x26 26+26+26+26 MRU; 52+26+26 MRUs; 52+52 MRUs; 106-RU 5x26 26+26+26+26+26 MRU; 26+26+26+52 MRUs; 26+52+52 MRUs; 106+26 MRUs; etc... 6x26 26+26+26+26+26+26 MRU; 26+26+26+26+52 MRUs; 26+26+52+52 MRUs; 106+26+26 MRUs; 106+52 MRUs, etc. 7x26 26+26+26+26+26+26+26 MRU; 26+26+26+26+26+52 MRUs; 26+26+26+52+52 MRUs; 106+26+26+26 MRUs; 106+52+26 MRUs, etc. 8x26 26+26+26+26+26+26+26+26 MRU; 26+26+26+26+26+26+52 MRUs; 26+26+26+26+52+52 MRUs; 106+26+26+26+26 MRUs; 106+26+52+26 MRUs; 106+106 MRUs, etc. 9x26 26+26+26+26+26+26+26+26+26 MRU; 26+26+26+26+26+26+26+52 MRUs; 26+26+26+26+26+52+52 MRUs; 106+26+26+26+26+26 MRUs; 106+26+26+52+26 MRUs; 106+26+106 MRUs; 242-RU; ancho de banda completo en una PPDU de 20 MHz, etc... The new RU Assignment subfield table is based on one or more of the previous RUs / MRUs, and the number of MRUs and the locations of each RU within the MRU can also be considered. The more flexible the MRU, the more indexes are required. Preferred RUs / MRUs can be defined and limited to reduce the complexity of the RU Assignment subfield. Table 2 below is another example of the required resources (especially larger than 20 MHz, a bandwidth of 320 MHz is supported) and the preferred RU or MRU based on the required resources. Table 2 Most required resources (number of subcarriers) by a station RU / MRUs 1x242 242-RU; full bandwidth on a 20 MHz PPDU 2x242 242+242 MRU; 484-RU; full bandwidth on a 40 MHz PPDU 3x242 242+242+242 MRU; 484+242 MRU 4x242 242+242+242+242 MRU; 242+242+484 MRU; 484+484 MRU; 996-RU; full bandwidth on one 80 MHz PPDU 5x242 242+242+242+242+242 MRU; 242+242+242+484 MRU; 242+484+484 MRU; 996+242 MRU, etc. 6x242 242+242+242+242+242+242 MRU; 242+242+242+242+484 MRU; 242+242+484+484 MRU; 242+242+996 MRU, 996+484 MRU 7x242 242+242+242+242+242+242+242 MRU; 242+242+242+242+242+484 MRU; 242+242+242+484+484 MRU; 242+242+242+996 MRU; 996+484+242 MRU 8x242 242+242+242+242+242+242+242+242 MRU; 242+242+242+242+242+242+484 MRU; 242+242+242+242+484+484 MRU; 242+242+242+242+996 MRU; 996+484+242+242 MRU; 2x996-RU; Full bandwidth at 160 MHz 9x242 ...2x996+242 MRU 10x242 ...2x996+484 MRU 11x242 ...2x996+484+242 MRU 12x242 ...2x996+996 MRU 13x242 ...2x996+996+242 MRU 14x242 ...2x996+996+484 MRU 15x242 ...2x996+996+484+242 MRU 16x242 ...full bandwidth at a 320 MHz PPDU To reduce the complexity of the indication and meet resource requirements more efficiently, preferred MRUs are provided. See Figure 13; simulation results show that combining the best 26-RU with a RU>26 to form an MRU produces negligible SNR gain in the case where the best 26-RU is combined with a specific 26RU that provides an SNR >3dB. Therefore, for a 20 MHz frequency segment, in one example, a preferred MRU includes a combination of a mid-26-RU and its adjacent 52-RU / 106-RU, or a combination of two 26-RUs that are different from the 52-RU already defined. It can also be referred to as an aggregated mid-26-RU and its adjacent 52-RU or 106-RU, or an aggregated non-adjacent 26-RU. But even with the above restrictions, there are still too many entries required to support other combinations of MRU, so expanding the RU Allocation table may not be practical in some situations. Table 3 ML / t / ZUZZ / U í 1Z44 # Combination Additional entries required in an 802.11be RA subfield Remark 1 Single MRU: 52-RU interior + 26-RU middle 48 There are 10 entries for each 52RU+26-RU middle in the RA subfield 2 Single MRU: 106-RU + 26-RU middle 96 Including MU-MIMO 3 Single MRU: 2x26 384 Including MU-MIMO when the allocation contains RU-106 Too many entries, you may want to consider canceling MUMIMO for 106-RU 4 Single MRU: 2x26 (without MU-MIMO) 214 5 Two MRUs: 2x26 + 2x26 Hundreds Too many entries require a lot of overhead, therefore making it impractical 6 Other MRU combinations Tens of thousands See Table 3. There are too many entries required to support other MRU combinations, for example, two concurrent 2x26-RU MRUs. Therefore, instead of expanding the RU Allocation subfield to an enormous dimension, in Alternative Mode 3, a new field is included to indicate the size and location of each RU added to an MRU, which can be called a Common-MRU. Examples are illustrated in Figure 14. This Common MRU field exists only if any MRU exists in the PPDU (in any of the 20 MHz channels). Therefore, the Common MRU field can be signaled either in a U-SIG prior to the EHT-SIG, or as additional bits / fields in the common field of the EHT-SIG. For small MRUs: This Common-MRU Field is coded separately. This Common-MRU Field comprises 3 bitmap subfields, as follows: MRU_1 - can be 9 bits, indicates which 26-RUs are included in a 5 MRU. MRU_2 - can be 7 bits, indicates which 26-RUs are included in a 2nd MRU. MRU3 - can be 5 bits, indicates which 26-RUs are included in a 3rd MRU. Thus, an additional 21 bits (22 bits including the signaling bit that indicates whether an MRU is present / exists) are required to signal any combination of up to 3 MRUs per 20 MHz frequency segment. The amount of additional bits will be saved later due to the reduction in the number of user fields in the user-specific field. In this mode, although the common NRU field may appear as a high overhead, it should be kept in mind that a larger amount of additional bits can be saved later due to the reduction in the number of user fields in the user-specific field. For large MRUs; Large MRUs are identified by the corresponding RU Assignment subfield for RU>=242 tones. 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-RU belongs to the MRU MRU 2 - omitted MRU3 - omitted Similar to the small MRU case, the overhead of the user-specific field is also reduced. That is, for a specified MRU, one or more user fields are included, and no station ID is repeated in different user fields. Station numbers or user fields indicated by the RU assignment fields continue to function when the station determines which RU / MRU is assigned to it. User-specific fields are included in the EHT-SIG. Each RU / MRU indicated by the RU Assignment subfield and / or Common MRU Field is mapped to one or more user fields. Generally, user fields are mapped to the MRU / RU sequentially. Because the location of RUs within the MRU can vary, there should be some rules for mapping the MRU and one or more user fields assigned to it. In one example, the MRU location is specified by the ML / t / ZUZZ / U í 1Z44 location of the first RU in the lowest frequency domain. See Figure 17a, based on the frequency order of 26-RU 1, 26-RU 2 and 52-RU 2, MRU 1 is the one in which 26-RU 1 is the lowest RU, MRU 2 is the one in which 26-RU 2 is the lowest RU, MRU 3 is the one in which 52-RU 2 is the lowest RU. One or more user fields of an MRU / RU can be mapped to the MRU / RU in a similar way in 802.11ax. A user field location of an MRU will correspond to the RU of the lowest frequency, as shown in the two examples in Figures 15 and 1010. In other words, each user field of an MRU points to the first RU (the RU located at the lowest frequency) of the MRU. For MRUs larger than 242-RU (or 106-RU), MU-MIMO is supported; the corresponding user field number for the MRU is also indicated. When the content is split for CC1 and CC2, the corresponding user field number for the MRU in CC1 and CC2 is indicated respectively. In this solution, a STA can decode the user-specific field similarly to how it does in 802.11ax. When the user-specific field is decoded, the STAs use the RU / MRU mapping or structure (signaled in the common field) to obtain the user fields in the RU / MRU. When necessary, the other RUs in the same MRU are omitted. For example, in Figure 15, MRU1 comprises 26-RU-1 and 26-RU-3; the sequence / order location of the MRU / RU is [MRU1, 26-RU2, 26-RU4, 26-RU5, 52-RU3, 52-RU4]. The user fields are mapped to the MRU / RU in sequence. For example, in Figure 16, MRU1 comprises 52-RU2 and 26-RU5; the sequence / order location of the MRU / RU is [26-RU1, 26-RU2, MRU1, 52-RU3, 52-RU4]. The user fields are mapped to the MRU / RU in sequence. Figure 17a illustrates an example of RU / MRU assignment, which comprises 3 M-RUs in a 20 MHz frequency segment. The complete common field “1 000001 1 1 1000 00011010001100111” comprises, see Figure 17b, an MRU indication, an RU assignment subfield, a first MRU bitmap, a second MRU bitmap, and a third MRU bitmap. Details are shown below: The MRU indication, which is 1 bit, indicates whether there is any MRU in the allocation; The RU assignment subfield, which can be 8, 9, or 10 bits, indicates the sequence of RUs (size and location of each RU) corresponding to the 20 MHz frequency segment. In the example, “00000111” indicates the assignment of [26, 26, 52, half26, 52, 52]. The first MRU bitmap, labeled MRU_1, indicates which 26-RU is in the first MRU. In the example, 100000011 indicates that the first, 8th, and 9th 26-RUs are ML / t / ZUZZ / U í 1Z44 combined as the first MRU. The first MRU bitmap usually starts with 1 (MSB is 1), which indicates that the MRU comprises the 26-RU on the left edge. The second MRU bitmap, labeled MRU_2, indicates which 26-RU is in the second MRU. In the example, 0100011 indicates that the 2nd, 6th, and 7th 26-RUs are combined as the second MRU. Only 6 bits are required, therefore MSB is 0. The third MRU bitmap, labeled MRU_3, indicates which 26-RU is in the third MRU. In the example, 00111 indicates that the second, sixth, and seventh 26-RUs are combined as the second MRU. Only three bits are required, therefore two MSBs are 0. Figure 17c, based on the same RU / MRU allocation example, provides an alternative solution: The RU_allocation field in the common field of an EHT-SIG indicates the size and location of RU(s) for a frequency segment, and the common field of an EHT-SIG further comprises one or more common MRU fields. Each common MRU field indicates that a RU specified by the RU allocation field (i.e., an allocated RU) is in an MRU. This differs from Figure 17b in that it uses granularity for MRU indication. It is preferred that the length of the common MRU fields decreases in order, with the order of the common MRU fields based on the first RU in the frequency-domain MRU. For example, the RU allocation field is set to 0 0 0 0 0 1 1 1. The common MRU field: Using a bitmap that corresponds to the actual number of RUs, each bit indicates whether a RU indicated by the RU_allocation field is in an MRU. Unused bits are set to 0'. The bits required in the solution can 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. The RU_allocation field: 0 0 0 0 0 1 1 1 MRU-Common 1 field, MRU1, indicating which RU is in the first MRU. For example, 0 0 0 1 0 0 0 0 1. Only 6 bits are required 1 0 0 0 0 1, therefore 3 MSBs can be set to 0 or for another function, sometimes the first 3 bits can be omitted. Common MRU Field 2, MRU_2: 0 0 0 1 0 0 1. Only 4 bits are required, therefore 3 MSBs can be set to 0, or for another function, or can be omitted. Common MRU Field 3, MRU 3:0 0 0 1 1. Only 2 bits are required, therefore 3 MSBs can be set to 0, or for other functions. The order of the common-motion field is in accordance with the order of the first RU in the frequency-domain motion. See Figure 17a. Figure 18 provides an indication solution for the allocation of RU / MRU per 160 MHz bandwidth for a large MRU. In this example, there are two MRUs; one MRU comprises the 242ML / t / ZUZZ / U í 1Z44 RU 1, 242-RU 3, 242-RU 4 and 242-RU 7 (shown in gray). The other MRU comprises 242-RU 5, 242-RU 6 and 242-RU 8. The EHT-SIG comprises CC1 and CC2. The EHT-SIG information can be divided into CC1 and CC2 to reduce overhead and increase the robustness of the information. The common field of CC1 comprises: RU (field) allocation information for 20 MHz frequency segments or 40 MHz frequency segments, for odd-numbered 20 MHz or 40 MHz frequency segments. For example, in this example, 1 1 1 0 0 xxx for 20 MHz frequency segments. The CC2 common field comprises: RU (field) allocation information for 10 frequency segments of 20 MHz or for 40 MHz frequency segments, for even-numbered 20 MHz or 40 MHz frequency segments. For example, in this example, 1 1 1 0 0 xxx for 20 MHz frequency segments. In alternative solutions, the common field above may be omitted by other solutions, or it may be indicated in the manner described in the other modalities. MRU_1 is valid and has a length of 8 bits. The MRU_1 field in CC1 also corresponds to the odd-numbered 20 MHz or 40 MHz segments. In the example in Figure 18, the four starting bits are mapped to the 1st, 3rd, 5th, and 7th 20 MHz segments in the primary 160 MHz or the single 160 MHz bandwidth. If the bandwidth is 320 MHz, the next four bits are mapped to the 9th, 14th, 13th, and 15th 20 MHz segments. The MRU_1 field in CC2 also corresponds to the even-numbered 20 MHz or 40 MHz segments. In the example in Figure 18, the four starting bits are respectively mapped to the 1st, 3rd, 5th, and 7th 20 MHz segments in the primary 160 MHz or the single 160 MHz bandwidth. If the bandwidth is 320 MHz, the next four bits are respectively mapped to the 9th, 11th, 13th, and 15th 20 MHz segments. Similarly, the MRU 2 field indicates the RUs in MRU2 through the similar method of the MRU_1 field. In some solutions, MRU_2 and MRU_3 are omitted based on the MRU signal bit and the RA subfield in the common part. Figure 19 provides an example of a transmission containing a mixed type of MRU (large MRU and small MRU). In this example, the 242-RUs are assigned as small MRUs as in Figures 17a and 14b, and another 242-RUs are assigned to the large MRU, as in Figure 18. RA fields (including RA 2 for 242-RU 2) are located in common part 35 of EHT-SIG in a manner similar to figure 18. MA / t / ZUZZ / U í Ί Z44 The small MRU_1 / 2 / 3 field can be added in the location of the MRU field corresponding to RA2 in CC2. In this mode, by providing a Common subfield with the MRU bitmap, many technical advantages are obtained: any combination of MRUs can be defined, the expansion of the RU Assignment subfield can be avoided, the implementation can be made practical, and the additional overall overhead in EHT-SIG can be reduced. Mode 4 In this mode, MRUs are allowed to be assigned to a station, and preamble perforation is also considered. This mode works when assigning a large RU (RU > 484), such as a 996-RU, a 1992-RU (2 * 996-RU), or a 3984-RU (2 * 996-RU), where some of the 20 MHz portions within them are perforated. In this case, the existing channel perforation information is used to define a large perforated RU as a single RU instead of several smaller RUs. This information may be available in a field preceding the EHT-SIG, which can be called "U-SIG," and may be indicated by two or more bits. The common portion of the EHT-SIG does not include information regarding sub-channel perforation (20 MHz). Assuming that perforation is common (especially in dense networks), and referring to RU>484, perforation information is included in a GIS (likely to be defined in U-GIS). This perforation information is used to define or indicate a large, non-contiguous RU (perforated RU). Consequently, the GIS may also include a unique user-specific field (in EHT-GIS) in which one or more user fields corresponding to the large, non-contiguous RU are included. One or more user fields contain information from a different respective station. These stations are then assigned to the large, non-contiguous RU by MU-MIMO. Figure 20 shows an example of the above mode in a bandwidth of 160 MHz. In the example, the first 996-RU is assigned to STA1, in which the second 242-RU is punched out. This assignment, like that of the first 242-RU and the second 484-RU, is assigned to STA1. A second 996-RU is assigned to STA2, in which the second 242-RU is punched out. The sixth and eighth 242-RUs are assigned to STA2. In the example, the frequency resource assigned to STA1 can be defined or considered as a punched-out 996-RU (shown as 80 MHz primary). A single user-specific field (in which a different user field with information from different stations) can be included corresponding to the 996-RU drilled in an EHT-SIG, instead of modality 1, i.e., two RUs requiring two user fields, where a first user field 35 corresponds to the 1st 242-RU, a second user field corresponds to the 2nd 484-RU, the first user field and the second user field comprise the same ID of MA / t / ZUZZ / U í 1Z44 stations. Similarly, the frequency resource assigned to STA2 can also be defined or considered as a perforated 996-RU (shown as 80 MHz secondary). A single RU corresponding to the perforated 996-RU can be included in the EHT-SIG, instead of mode 1, i.e., two RUs requiring two user fields, where the first user field corresponds to the 6th 242-RU, and the second user field corresponds to the 8th 242-RU. When an STA observes that RU-996 is assigned to it, it already knows that this RU is perforated. Reduce overload Furthermore, any receiver that supports the suggested method (specifically Huawei's device) can easily decode the signals that are defined by the same suggested method, thereby disclosing the use of the invention by a competing transmitter. Mode 5 As mentioned in mode 3, a new table can be defined, where the newly defined MRU is also indicated by the bit / index sequences defined in the RU Assignment subfield. The RU Assignment (RA) subfield can be 8 bits, 9 bits, 10 bits, or more bits, corresponding to a 20 MHz segment. The more bits in the RA, the more MRUs can be supported; that is, one or more of the MRUs listed above can be in a RU assignment and can be indicated by the index corresponding to the RU assignment. The more stations that can be assigned to a RU or MRU, the more bits are required to indicate the number of stations. Once the MRU in the RU assignment and the number of stations in the MRU have been specified, the mapping between the RU / MRU and the user fields is indicated by the sequence of the RU / MRU and the sequence of the stations / user fields—that is, a one-to-one mapping. As mentioned, the allocation of RUs is decided by the AP according to several criteria. The resources required by a station in a transmission are determined when the preferred RU or MRU is established. To reduce the complexity of the table, the preferred or limited allocation of RU or MRU is defined in the table; an inefficient allocation of RU / MRU is not allowed. Table 4 below is an example of the required resources (especially less than 20 MHz) and the preferred RU or MRU based on the required resources. MA / t / ZUZZ / U í Ί Z44 Table 4 ML / t / ZUZZ / U / Ί Z44 Most required resources (number of subcarriers) by a station RU / MRUs / preferred full bandwidth 1x26 26-RU 2x26 52-RU 3x26 52 MRU adjacent+26 MRU average 4x26 106-RU 5x26 106+ 26 MRU average 6x26 106+52 MRU 7x26 106+52+26 MRU average 8x26 106+106 MRU 9x26 242-RU; full bandwidth in a 20 MHz PPDU A new index table for the RU Allocation subfield may require considering the previous preferred RUs / MRUs, and the MRU number and locations of each RU within the MRU may also be considered. The more flexible the MRU, the more indexes are required. Table 5 below is another example of the required resources (especially those greater than 20 MHz, a bandwidth of 320 MHz is supported), and the preferred RU or MRU based on the required resources, which need an entry in the RU Allocation subfield index table. Table 5 Most required resources (number of subcarriers) by a station Preferred RU / MRUs 1x242 242-RU; full bandwidth in a 20 MHz PPDU 2x242 484-RU; full bandwidth in a 40 MHz PPDU 3x242 Maximum 3 242-RU (an MRU initiated by a starting 242-RU where the first RA indicates that it corresponds to 3x242, can be punctuated by a second RA corresponding to 20 MHz following the starting 242-RU in frequency) 4x242 Maximum 4 contiguous 242-RUs (996-RU); full bandwidth on an 80 MHz PPDU; 5x242 Maximum 5 contiguous 242-RUs 6x242 Maximum 6 contiguous 242-RUs, can be drilled 7x242 Maximum 7 contiguous 242-RUs 8x242 Maximum 8 contiguous 242-RUs 9x242 Maximum 9 contiguous 242-RUs 10x242 Maximum 10 contiguous 242-RUs 11x242 Maximum 11 contiguous 242-RUs 12x242 Maximum 12 contiguous 242-RUs 13x242 Maximum 13 contiguous 242-RUs 14x242 Maximum 14 contiguous 242-RUs 15x242 Maximum 15 242-RUs contiguous 16x242 full bandwidth in a 320 MHz PPDU The maximum of contiguous M 242-RUs (a large MRU) in the previous part is defined and mapped to an index. The large MRU starts in the frequency domain from a starting 242-RU where a starting RA indicates that it corresponds to the Mx242 (the first RA in the common part of EHT-SIG indicating the Mx242 MRU). This large MRU can be punctuated by a second RA corresponding to 20 MHz following the starting 242-RU in the frequency domain. The large MRU may be further limited in the following Table 6, which requires an entry in the table indexes of the RU Allocation subfield: Table 6 Most required resources (number of subcarriers) by a station Preferred RU / MRUs 1x242 242-RU; full bandwidth in a 20 MHz PPDU 2x242 484-RU; full bandwidth in a 40 MHz PPDU 3x242 Maximum 3 contiguous 242-RUs (an MRU initiated by a starting 242-RU where the first RA indicates that it corresponds to the 3x242, can be perforated by a second RA corresponding to 20 MHz following the starting 242-RU in frequency) 4x242 Maximum 4 contiguous 242-RUs (996-RU); full bandwidth in an 80 MHz PPDU; 5x242 Maximum 5 contiguous 242-RUs 6x242 Maximum 6 contiguous 242-RUs, can be perforated 7x242 Maximum 7 contiguous 242-RUs 8x242 Maximum 8 contiguous 242-RUs ML / t / ZUZZ / U í Ί Z44 Large MRUs can be further reduced. The required entries for each large MRU can be based on the number of stations that can be assigned to the large MRU. For example, when 16 MU-MIMO stations are supported, the entry for each large MRU can be 16. The index values ​​are not limited; 2, 3, or 4 bits in the index are used to indicate the number of stations in the large MRU. Based on the previous solution, in the examples in Figure 6, at 160 MHz, the first, third, fourth, and fifth 242-RUs are assigned to STA1; the sixth and eighth 242-RUs are assigned to STA2. The RU assignment can be indicated by the common part of EHT-SIG hereafter: the common part of CC1 comprises “RA-1, indicating 5x242 MRU(n1)); RA-3, indicating 5x242 MRU(n1); RA-5, indicating 5x242 MRU(n1); RA-7, indicating 242(n4)”; The common part of CC2 comprises “RA-2, indicating 242(n2); RA-4, indicating 5x242 MRU(n1); RA-6, indicating 3x242 MRU(n3); RA-8, indicating 3x242 MRU(n3)”. The n1, n2, n3, n4 is the number of stations in the large MRU in CC1 or CC2. In the aforementioned mode, only the common portion of the EHT-SIG is disclosed; the user-specific field can be similar to the 802.11ax solution. A sequence of user fields is placed in the user-specific field of a corresponding EHT-SIG, mapping to the RU or MRU in the assignment indicated by the RA field. In a certain special situation, in addition to the MRU indicated by the RA field, another type of MRU may be indicated by the user fields. Modality 6 The modes can be combined in a way that allows them to function and be amended in a way that still works or works better; the following are some examples. Mode 6a provides a signaling method for small RUs where the indication field in the common part of EHT-SIG consists of two fields: the existing RA field and the additional MRU allocation signaling. This method allows defining any combination of small RUs as MRUs while maintaining the 802.11ax 20 MHz allocation map definition (the RU Allocation subfield). The indication consists of the RA field and additional signaling indicating which RUs that are defined in the RA field are assigned as MRU. For example, if you want to assign the following map {26, 26+52, center 26, 26, 26, 52}; where the second 26-RU and the second 52-RU comprise an MRU, first an 8-bit RA field '00000101' is indicated which defines the allocation map of {26, 26, 52, center 26, 26, 26, 52}; and then the MRU comprised of the second 26-RU and the second 52-RU is specifically indicated. In this method, the unique user-specific field will be indicated in EHT-SIG by MRU, see the unique user-specific field specified in the modality. Modality 6a In this mode, the method is provided to indicate the assignment of MRU using a bit map where each bit corresponds to a specific RU that is defined in the RA field. Each 20 MHz can include up to 4 MRUs, therefore the MRU allocation field will comprise 4 parts. In alternative solutions, 1, 2, or 3 MRUs may be allowed. The first part - the first MRU can be any combination of RUs defined in the RA field. The maximum number of RUs in 20 MHz is 9; therefore, 9 bits are used to cover all possible assignments. The actual number of bits used for MRU assignment will be equal to the number of RUs defined in the RA field, starting from the 9-bit LSB or MSB. If the number of RUs defined in the RA field is less than 9, the redundant bits are irrelevant. For example, the field RA Ό000010T defines a RU assignment of [26, 26, 52, center 26, 26, 26, 52]; And a bitmap of 0 0 1 1 0 0 0 means that the second 52-RU and the central 26-RU are assigned as MRU while two non-important bits will be added to the bitmap. Part 2 - the second MRU can be any combination of those RUs defined in the RA field and not included in the first MRU. MA / t / ZUZZ / U / 1Z44 The maximum number of RUs, excluding the first MRU, is 7, so a 7-bit bitmap is used. The actual number of bits used for the second MRU will be equal to the number of RUs defined in the RA field minus the number of RUs comprising the first MRU, starting from the 7-bit LSB or MSB; redundant bits are unimportant bits. For example, following the assignment defined in the previous section, a bitmap of 1 0 0 0 means that the first and second 26-RUs are assigned as MRU while two bits that don't matter will be added to the bitmap. Part 3 - the third MRU can be any combination of those RUs defined in the RA field and are not included in the first and second MRUs. The maximum number of RUs, excluding the first and second MRUs, is 5, so a 5-bit bitmap is used. The actual number of bits used for the second MRU will be equal to the number of RUs defined in the RA field minus the number of RUs comprising the first and second MRUs, starting from the 5-bit LSB or MSB. Redundant bits are considered irrelevant. For example, following the allocation defined in the previous two sections, a bitmap of 0 1 1 means that the 7th 26-RU and 4th 52-RU are allocated as MRU. Part 4 - the fourth MRU can be any combination of those RUs defined in the RA field and are not included in the first, second, and third MRUs. The maximum number of RUs excluding the first, second and third MRUs is 3, therefore a 3-bit bitmap is used. In this example, the common field of EHT-SIG comprises: one or more RA fields, each RA field being 8 bits, and one or more MRU assignment fields, which can be 9, 7, 5, 3 bits respectively. In some alternative solutions, if MRU limit modes are defined, this 25 mode can also be revised accordingly, such as only including bits for the RU that is allowed to be added to the MRU. For example, if only 26RU-3, 26RU-4, 26RU-5, 26RU-6, and 26RU-7 are allowed to be added to an MRU, a first MRU allocation field and a second MRU allocation field could occupy 5 bits and 3 bits, respectively. Modality 6b In this mode, a similar method to mode 6a is provided, except that all bits in the bitmap of each part defined in mode 6a are used to indicate an assigned MRU, with no unimportant bits. Each bit in the bitmap corresponds to a specific 26-RU, while RUs larger than 26 will be 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 '1 1000001 T' would be defined where ML / t / ZUZZ / U í 1Z44 the first two 1s correspond to the 1st 52-RU and the last two 1s correspond to the last 52-RU. In this method, the common EHT-SIG field consists of 8 bits from the RA field and 9+7+5+3 bits from the MRU allocation field. Modality 6c In this mode, a method similar to modes 6a and 6b is used, where the number of MRUs is indicated in EHT-SIG by an NMRU field. If an NMRU field is set to zero, this means that no MRUs are assigned, and a common EHT-SIG field will not include any bitmaps. If an NMRU field is set to a number between 1, 2, 3, or 4, then 10, 1, 2, 3, or 4 MRUs are assigned, and a corresponding number of bitmaps will be included as defined in modes 6a and 6b. In this method, the common EHT-SIG field consists of: one or more RA fields (8 bits) and zero or 9 or 9+7 or 9+7+5 or 9+7+5+3 bits of an MRU allocation field according to the number of MRUs indicated by the N_MRU bits. 6d modality In this mode, an additional resource allocation table is defined, which includes all defined combinations of MRUs. This can be an MRA field – a Multiple Resource Allocation field. Each MRA entry defines a map that can comprise a single MRU or a combination of MRUs. The map defines only MRUs, while a complete 20 MHz allocation map is defined by an RA field. For example, if the following 20 MHz map is to be allocated [26, 26, 52 + center 26, 26, 26, 52]; then the RA field of '00000101' will indicate the map of [26, 26, 52, center 26, 26, 26, 52]; and a new MRA entry can be defined where the second 52-RU and the central 26-RU are assigned as a single MRU. The new MRA field will not indicate any unique RUs, only MRUs, therefore any RA field entry where the 2nd 52-RU and the central 26-RU are assigned can be combined with the MRA field where those RUs are assigned as MRUs. In this method, the common part of EHT-SIG comprises one or more RA fields (each RA field is 8 bits) and additional Nbits of the MRA field. The number of Nbits defines an MRA table size with options of 2ANbits of the MRU map. Figure 21 is a block diagram of an access point according to another embodiment of the present invention. The access point in Figure 21 comprises an interface 101, a processing unit 102, and a memory 103. The processing unit 102 controls an operation of the access point 100. The memory 103 may include read-only memory and random-access memory, and provides instructions and data to 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 together using a bus system 109, and in addition to a data bus, the bus system 109 further comprises a power bus, a control bus, and a status signal bus. However, for clarity of description, several buses are referred to as the bus system 109 in Figure 21. The methods for sending the various above pictures disclosed in the preceding embodiments 10 of the present invention can be applied to, or implemented through, the processing unit 102. In an implementation process, each step of the above methods can be completed by means of a hardware integrated logic circuit in the processing unit 102 or an instruction in a software form. The processing unit 102 can be a general-purpose processor 15, a digital signal processor, an application-specific integrated circuit, a field-programmable gate array or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component, and can implement or execute various methods, steps, and logic block diagrams disclosed in the embodiments of the present invention.The general-purpose processor may be a microprocessor, any conventional processor, or the like. The steps of the method disclosed with reference to the embodiments of the present invention may be directly executed by a hardware processor, or they may be executed using a combination of processor hardware and a software module. The software module may be located in a field-mature storage medium, such as random-access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, or a register. The storage medium is located in memory. The processing unit reads information from memory and completes the steps of the preceding methods with reference to the hardware of the processing unit. Figure 22 is a block diagram of a station according to another embodiment of the present invention. The station comprises an interface 111, a processing unit 112, and a memory 113. The processing unit 112 controls an operation of the station 110. The memory 113 may include a read-only memory and a random-access memory, and provides instruction and data to the processing unit 112. A portion 35 of the memory 113 may further include a non-volatile random-access memory (NVRAM). All components of station 110 are coupled together using a bus system ML / t / ZUZZ / U í 1Z44 In addition to a data bus, the 119 bus system also comprises a power bus, a control bus, and a status signal bus. However, for clarity of description, several buses are labeled as the 119 bus system in Figure 22. The methods for receiving the various diagrams disclosed in prior embodiments of the present invention may be applied to, or implemented by, the processing unit 112. In an implementation process, each step of the above methods may be completed by means of a hardware integrated logic circuit in the processing unit 112 or an instruction in a software form. 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 other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component, and may implement or execute various methods, steps, and logic block diagrams disclosed in this embodiment of the present invention.The general-purpose processor may be a microprocessor, any conventional processor, or the like. The steps of the method disclosed with reference to the embodiments of the present invention may be directly executed by a hardware processor, or they may be executed using a combination of processor hardware and a software module. The software module may be located in a field-mature storage medium, such as random-access memory, flash memory, read-only memory, programmable read-only memory, electrically programmable memory, or a register. The storage medium is referenced in memory 113. The processing unit 112 reads information from memory 113 and completes the steps of the preceding methods with reference to the hardware of the processing unit 112. Specifically, memory 113 stores stored information that allows processing unit 112 to execute the methods mentioned in the previous modes. The detailed description provided above in connection with the accompanying drawings describes examples and does not represent the only examples that may be implemented or that are within the scope of the claims. The terms “example” and “exemplary,” when used in this description, mean that it serves as an example, case, or illustration, and not “preferred” or “more convenient than other examples.” The detailed description includes specific details for the purpose of providing an understanding of the techniques described. These techniques, however, may be practiced without these specific details. In some cases, well-known structures and apparatus are shown in block diagram form to avoid obscuring the concepts of the described examples. Information and signals can be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips referred to in the description above can be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof. The various illustrative blocks and components described in connection with this disclosure may be implemented or run 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, for example, a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a core DSP, or any other such configuration. The functions described herein may be implemented in hardware, processor-executed software, firmware, or any combination thereof. If implemented in processor-executed software, the functions may be stored in 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 the accompanying disclosure and claims. For example, due to the nature of software, the functions described above may be implemented using processor-executed software, hardware, firmware, wiring, or combinations thereof. Features that implement functions may also be physically located in various positions, including 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 employed on its own, or that any combination of two or more of the listed items may be employed. For example, if a composition is described as containing components A, B, and / or C, the composition may contain A only; B only; C only; A and B in combination; A and C in combination; B and C in combination; or A, B, and C in combination. Also, as used herein, including in the claims, “O” as used in a list of items (for example, a list of items prefixed with a phrase such as “at least one of” or “one or more of”) indicates a disjunctive list, so that, for example, a list of “at least one of A, B, or C” means AoBoCoABoACoBCo ABC (i.e., A and B and C). Computer-readable media includes both computer storage media and communication media, including any medium that facilitates the transfer of a computer program from one location to another. A storage medium can be any available medium that can be accessed by a general-purpose or special-purpose computer. By way of example, and without limitation, computer-readable media may include RAM, ROM, EEPROM, flash memory, CD-ROM or other optical disc storage, magnetic optical disc storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a general-purpose or special-purpose computer or processor.Also, any connection is appropriately 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, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium. "Disk" and "disc," as used herein, include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk, and Blu-ray disc, where disks generally reproduce data magnetically, while discs reproduce data optically using a laser. Combinations of the above are also included within the scope of computer-readable medium. The preceding description of the disclosure is provided to enable a person skilled in the art to make or use the disclosure. Various modifications to the disclosure will be readily apparent to such persons skilled in the art, and the generic principles defined herein may be applied to other variations without departing from the scope of the disclosure. Therefore, the disclosure shall not be limited to the examples and designs presented herein, but shall be given the broadest scope consistent with the novel principles and features disclosed herein. It should be understood that a modality or modality mentioned throughout the specification does not mean that particular characteristics, structures, or features related to that modality are included in at least one modality of the present invention. Therefore, a modality or modality appearing throughout the specification does not refer to the same modality. Furthermore, these particular characteristics, structures, or features may be combined in one or more modalities using any appropriate method. Sequence numbers of the preceding processes do not signify execution sequences in various modalities of the present invention. The execution sequences of the processes should be determined according to the functions and internal logic of the processes and should not be interpreted as any limitation on the processes of implementing the modalities of the present invention. A person skilled in the art may be aware that, in combination with the examples described in the embodiments disclosed in this specification, algorithm units and steps can be implemented by electronic hardware, computer software, or a combination thereof. To clearly describe the interchangeability between hardware and software, the foregoing has generally described the compositions and steps of each example according to the functions. Whether the functions are executed by hardware or software depends on the particular applications and the design constraints of the technical solutions. A person skilled in the art may use different methods to implement the described functions for each particular application, but such implementation should not be considered to be beyond the scope of the present invention. An expert in the technique can clearly understand that, for the purpose of a brief and convenient description, for a detailed working process of the above system, apparatus and unit, reference can be made to a corresponding process in the modalities of the above method, and the details are not described here again. In the various embodiments provided in this application, it should be understood that the disclosed system, apparatus, and method may be implemented in other ways. For example, the embodiment of the apparatus described is merely an example. For example, the unit division is only a logical function division and may be a different division in the actual implementation. For example, a plurality of units or components may be combined or integrated into another system, or some features may be ignored or not implemented. Furthermore, the deployed or analyzed mutual couplings, direct couplings, or communication connections may be implemented through various interfaces. Indirect couplings or communication connections between the apparatus or units may be implemented electronically, mechanically, or otherwise. The units described as separate parts may or may not be physically separate, and parts deployed as units may or may not be physical units; they may be located in one position or distributed across a plurality of network units. Some or all of the units may be selected according to the actual needs to achieve the objectives of the solutions in the modalities of the present invention. ML / t / ZUZZ / U í 1Z44 Furthermore, functional units in the embodiments of the present invention may be integrated into a 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 a hardware form, or it may be implemented in the form of a software functional unit.

Claims

1. A wireless communication apparatus, characterized in that it comprises: a memory that stores instructions; and a processor coupled with the memory, wherein the processor and the memory are configured to: generate a signaling field, SIG, in a wireless local area network, WLAN, the SIG comprising a resource unit allocation field, RU, indicating a size and location of each RU in a frequency resource, the SIG further comprising one or more user fields, each user field comprising information of a programmed station, STA; wherein an MRU, which comprises multiple RUs, is permitted to be assigned to one or more STAs; transmit the SIG.

2. A wireless communication apparatus, characterized in that it comprises: a memory that stores instructions; and a processor coupled with the memory, wherein the processor and the memory are configured to: receive a signaling field, SIG, in a wireless local area network, WLAN, the SIG comprising a resource unit allocation field, RU, indicating a size and location of each RU in a frequency resource, the SIG further comprising one or more user fields, each user field comprising information of a programmed station, STA; wherein an MRU which comprises multiple RUs is permitted to be assigned to the same or more STAs; process the SIG.

3. The apparatus according to claim 1 or 2, characterized in that the MRU is a small MRU, which comprises the combination of 26-RU, 52-RU, or 106-RU in a frequency segment of 20 MHz; or, the MRU is a large MRU which comprises the combination of 242-RU, 484-RU, or 996-RU in a transmission bandwidth.

4. The apparatus according to claim 1 or 2, characterized in that the MRU comprises a first RU and a second RU, the SIG comprises 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 comprising the same STA ID. ML / t / ZUZZ / U í 1Z44 5. The apparatus according to claim 4, characterized in that the second user field further includes one or any combination of the following: the number of RUs assigned to the STA; or, the size and location of each RU in the MRU assigned to the STA.

6. The apparatus according to claim 1 or 2, characterized in that a common GIS field comprises information for a small MRU allocated in a corresponding 20 MHz frequency segment; and / or information for a number of a large MRU allocated in a transmission bandwidth.

7. The apparatus according to claim 1 or 2, characterized in that the GIS comprises a single RU user field and an MRU user field; the single RU user field corresponds to a RU that is not an MRU; an MRU user field corresponds to an MRU, comprising at least the following: a STAJD and a RU bitmap indicating the size and location of each RU included in the MRU.

8. The apparatus according to claim 1 or 2, characterized in that the SIG comprises a Common-MRU field indicating which 26-RUs are included in an MRU in a corresponding 20 MHz frequency segment; and / or indicating which 242-RUs are included in an MRU in a transmission bandwidth.

9. The apparatus according to claim 1 or 2, characterized in that the GIS comprises one or more common MRU fields, each common MRU field indicating which actual assigned RUs are in an MRU.

10. The apparatus according to claim 1 or 2, characterized in that the GIS comprises drilling information, indicating a large non-contiguous RU and one or more user fields corresponding to the large non-contiguous RU, each of one or more user fields comprising information from a different station.

11. A method for wireless communication, characterized in that it comprises: generating a signaling field, SIG, in a wireless local area network, WLAN, the SIG comprising a resource unit allocation field, RU, indicating a size and location of each RU in a frequency resource, the SIG further comprising one or more user fields, each user field comprising information of a programmed station, STA; wherein an MRU which comprises multiple RUs is permitted to be allocated to the same or more STAs; transmitting the SIG.

12. A method for wireless communication, characterized in that it comprises: receiving a signaling field, SIG, in a wireless local area network, WLAN, the SIG comprising a resource unit allocation field, RU, indicating a size and location of each RU in a frequency resource, the SIG further comprising one or more MA / t / ZUZZ / U / ΊZ44 user fields, each user field comprising information of a programmed station, STA; wherein an MRU, which comprises multiple RUs, is permitted to be assigned to the same or more STAs; processing the SIG. 5 13. The method according to claim 11 or 12, characterized in that the MRU is a small MRU comprising a combination of 26-RU, 52-RU, or 106-RU in a frequency segment of 20 MHz; or, the MRU is a large MRU comprising a combination of 242-RU, 484-RU, or 996-RU in a transmission bandwidth.

14. The method according to claim 11 or 12, characterized in that the 10 MRU comprises a first RU and a second RU, the EHT-SIG comprises 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 comprising the same STA ID.

15. The method according to claim 14, characterized in that the second 15 user field further includes one or any combination of the following: the number of RUs assigned to the STA; or the size and location of each RU in the MRU assigned to the STA.

16. The method according to claim 11 or 12, characterized in that a common field of the GIS comprises information for a small MRU allocated in a corresponding 20 MHz frequency segment; and / or, information for a number of a large MRU allocated in a transmission bandwidth.

17. The method according to claim 11 or 12, characterized in that the GIS comprises a single RU user field and an MRU user field; the single RU user field corresponds to a RU which is not an MRU; an MRU user field corresponds to an MRU, comprising at least the following: a STA ID and a RU bitmap indicating the size and location of each RU contained in the MRU.

18. The method according to claim 11 or 12, characterized in that the GIS comprises a Common-MRU field indicating which 26-RUs are included in an MRU in a corresponding 20 MHz frequency segment; and / or indicating which 242-RUs 30 are included in an MRU in a transmission bandwidth.

19. The method according to claim 11 or 12, characterized in that the GIS comprises one or more common MRU fields, each common MRU field indicating which actual assigned RUs are in an MRU.

20. The method according to claim 11 or 12, characterized in that the SIG 35 comprises drilling information, indicating a large non-contiguous RU and one or more MA / t / ZUZZ / U í Ί Z44 user fields corresponding to the large non-contiguous RU, each of one or more user fields comprising information from a different station.

21. A non-transient computer-readable storage medium characterized in that it comprises instructions which, when executed by a computer unit, carry out the steps of the method in accordance with any of claims 11 to 20.

Images