Resource allocation signaling in wireless local area network preamble

Abstract

An apparatus for wireless communication, comprising: a memory that stores instructions; 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 including a resource unit (RU) allocation field that indicates a size and a location of each RU in a frequency resource, the SIG further including one or more user fields, each user field including information of a scheduled station (STA), wherein an MRU including multiple RUs is allowed to be allocated to one STA; and transmit the SIG.

Description

[0001] This application is a divisional application. The original application has the application number 202080092353.2 and the original application date is January 10, 2020. The entire contents of the original application are incorporated herein by reference. Technical Field

[0002] This invention relates to wireless communication, and more particularly to a novel method and apparatus for resource allocation signaling in WLAN. Background Technology

[0003] OFDMA modulation was first introduced in the IEEE 802.11ax standard. The description of the RU used for a given PPDU is given in its SIG-B field (and as shown in...). Figure 1 As shown, this field is defined in detail in the 802.11ax standard. It consists of two main subfields: a public field as described in the 802.11ax standard and a user-specific field.

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

[0005] As mentioned above, there are six RU sizes in the current 802.11ax standard (i.e., the prior art). During the allocation process, the scheduler can allocate only a single RU to a given STA in either a multi-user physical layer protocol data unit (MU-PPDU) (transmitted packet) or a single-user PPDU (SU-PPDU) transmission.

[0006] If an unassigned RU exists, it cannot be assigned to a STA that already has an assigned RU. Summary of the Invention

[0007] This invention aims to expand and improve the methods for using channel resources in WLAN.

[0008] Methods, apparatus, and computer-readable media for resource allocation signaling in ultra-high throughput wireless local area networks (WLANs) are disclosed.

[0009] Devices such as access points (APs) can generate signaling fields (SIGs). SIGs include a Resource Unit (RU) allocation field, which indicates the size and location of each RU in the frequency resource. SIGs also include one or more user fields, each containing information about a dispatch station (STA); where it is permissible to assign an MRU comprising multiple RUs (MRUs) to one or more (identical) STAs. This RU includes those defined in 802.11ax. The MRU can be a small MRU, comprising combinations of 26-RUs, 52-RUs, or 106-RUs in the 20 MHz band; or it can be a large MRU, comprising combinations of 242-RUs, 484-RUs, or 996-RUs in the transmission bandwidth.

[0010] In some examples, the MRU includes a first RU and a second RU. The device 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 include the same ID of the STA. The second user field may 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 in the MRU assigned to the STA.

[0011] Alternatively, the device may generate a common field for the SIG, which includes information about the number of small MRUs allocated in the corresponding 20 MHz band; and / or information about the number of large MRUs allocated in the transmission bandwidth.

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

[0013] Alternatively, the device may generate a common MRU field indicating which 26-RUs are included in the MRUs in the corresponding 20 MHz band; and / or a common MRU field indicating which 242-RUs are included in the MRUs in the transmission bandwidth.

[0014] Alternatively, the device may generate one or more common MRU fields, each indicating whether the actually allocated RU is in the MRU (which actually allocated RUs are in the MRU).

[0015] In addition, other information (such as channel puncturing information in U-SIG) can be used to indicate MRU allocation. This puncturing information indicates non-contiguous large RUs and one or more user fields corresponding to those non-contiguous large RUs, wherein each of the one or more user fields includes information about different stations.

[0016] One or more stations (e.g., wireless or mobile devices) can receive a WLAN preamble including a SIG. The one or more stations can then determine the MRUs, including multiple RUs assigned to the STA, based on the SIG. The aforementioned stations can then determine the MRUs assigned to the STA using the following: 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 include the same ID of the STA; the second user field may 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 in the MRUs assigned to the STA; or The SIG's common fields include information about the number of small MRUs allocated in the corresponding 20 MHz band; and / or information about the number of large MRUs allocated in the transmission bandwidth, or Single RU user fields and MRU user fields; the single RU user field corresponds to a RU that is not an MRU; the MRU user field corresponds to an MRU, and the MRU user field includes at least: STA_ID and an RU bitmap, which indicates the size and location of each RU included in the MRU; or Indicates which 26-RU common MRU fields are included in the MRUs within the corresponding 20 MHz band; and / or indicates which 242-RU common MRU fields are included in the MRUs within the transmission bandwidth; or One or more public MRU fields, each indicating whether an actually allocated RU is in the MRU (which actually allocated RUs are in the MRU); or Other information (such as punch information) indicates non-contiguous large RUs and one or more user fields corresponding to the non-contiguous large RUs, each of the one or more user fields including information about different stations.

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

[0018] A method performed by the aforementioned apparatus (including APs and stations) is also provided, as well as a computer-readable medium for resource allocation signaling.

[0019] Some examples of the methods, apparatuses, or non-transitory computer-readable media described herein may also include processing, features, methods, or instructions for resource allocation signaling in high-throughput WLAN preambles. The further scope of the applicability of the described systems, methods, apparatuses, or computer-readable media will become apparent from the following detailed description, claims, and accompanying drawings. Because various variations and modifications within the scope of the description will become apparent to those skilled in the art, the detailed description and specific examples are for illustrative purposes only. Attached Figure Description

[0020] The above and other objects and features of the present invention will become apparent from the following description, taken in conjunction with the accompanying drawings, in which: Figure 1 This is a diagram showing the SIG-B field (defined in detail in the 802.11ax standard); Figure 2 This is a diagram illustrating an example of a wireless local area network; Figure 3 This is a flowchart illustrating how scheduling information in a WLAN is transmitted on the transmitting side; Figure 4 This is a flowchart illustrating how scheduling information in a WLAN is transmitted on the receiving side; Figure 5 This is a diagram illustrating an example of the indicator structure of Embodiment 1; Figure 6 This is a diagram illustrating another example of resource allocation in an embodiment; Figure 7 This is a diagram illustrating another example of the indicator structure in the embodiment; Figure 8 This is a diagram illustrating another example of the indicator structure in the embodiment; Figure 9a , Figure 9b , Figure 9c This is a diagram showing an example of the public fields of EHT-SIG; Figure 10a This is a diagram illustrating an example of resource allocation and scheduling stations on a RU; Figure 10b It shows an instruction Figure 10a A diagram illustrating an example of the structure of the public fields of the EHT-SIG for resource allocation; Figure 11a This is a diagram illustrating an example of the structure of the user-specific field of EHT-SIG in an embodiment; Figure 11b This is a diagram illustrating an example of the structure of the MRU user field in the user-specific fields of EHT-SIG; Figure 12a and Figure 12b This is a diagram showing the structure of the user field in the user-specific fields of EHT-SIG; Figure 13 This is a graph showing the simulation results; Figure 14 This is a diagram illustrating another example of the instruction structure of a public MRU; Figure 15 This is a diagram illustrating an example of resource allocation and UR mapping in an embodiment; Figure 16 This is a diagram illustrating an example of resource allocation and UR mapping in an embodiment; Figure 17a This is a diagram illustrating another example of resource allocation in an embodiment; Figure 17b It is shown Figure 17a A diagram of the indicator structure for resource allocation in the system; Figure 17c It is shown Figure 17a Another diagram indicating the structure of resource allocation in the diagram; Figure 18 This is another diagram illustrating resource allocation and its instruction structure; Figure 19 This is a diagram illustrating an example of a transmission containing a hybrid MRU; Figure 20 This is a diagram illustrating another example of resource allocation in an embodiment; Figure 21 This is a block diagram of an access point according to an embodiment of the present invention; and Figure 22 This is a block diagram of a station according to an embodiment of the present invention. Detailed Implementation

[0021] In the following, a method according to an embodiment of the present invention will be described with reference to the accompanying drawings for using channel resources in 802.11be by allowing STAs to use multiple non-contiguous portions of the channel.

[0022] For ease of understanding, the terms that may appear in the following embodiments are explained as follows: AP access point ATaccess terminal BSSbasic service set BW bandwidth CC content channel DLdownlink downlink DSdistribution system EHText extremely high throughput ESS extended service set High efficiency LLC logical link control L-LTFNon-HT Long Training Field L-SIGNon-HT SIGNAL field (non-HT signal field) L-STFNon-HT Short Training field LTF long training field MACmedium access protocol (Media Access Protocol) MCS modulation and coding scheme MLD multi-link device MRU (Multiple Resource Units) MSmobile station MUmulti-user MU-MIMO (Multi-user Multiple Input, Multiple Output) NDP null data PPDU empty data PPDU Orthogonal Frequency Division Multiplexing (OFDM) Orthogonal Frequency Division Multiple Access (OFDMA) PHY physical layer PPDUPHY protocol data unit RARU allocation field RL-SIGRepeated Non-HT SIGNAL field RUresource unit SAP service access point SSsubscriber station User station STAstation station SUsingle user TDLS tunneled direct link setup TIDtraffic identifier TXOP transmission opportunity UE user equipment ULUplink uplink U-SIG Universal SIGNAL field WMwireless medium Figure 2 An example of a wireless local area network (WLAN) 100 according to various aspects of this disclosure is shown. The WLAN 100 supports resource allocation signaling or scheduling signaling in a WLAN preamble (e.g., an EHT WLAN preamble).

[0023] WLAN 100 includes an access point (AP) 105 and stations (STAs) 110 labeled STA 1 through STA 6. STA 110 can represent devices such as wireless communication terminals, including mobile stations, telephones, personal digital assistants (PDAs), other handheld devices, netbooks, laptops, tablets, display devices (e.g., TVs, computer monitors, etc.), printers, etc. Although only one AP 105 is shown, WLAN 100 can have multiple APs 105. STA 110 can also be referred to as a mobile station (MS), mobile device, access terminal (AT), user equipment (UE), subscriber station (SS), or user unit. STA 110 is connected via communication link 1 15 is associated with and communicates with AP 105. Each AP 105 has a coverage area 125 such that STA 110 within this area is within the range of AP 105. STA 110 is distributed throughout coverage area 125. Each STA 110 is stationary, mobile, or a combination thereof. Devices in WLAN 100 can communicate on unlicensed spectrum, which may be a portion of the spectrum including bands traditionally used by Wi-Fi technology (e.g., 5 GHz band, 2.4 GHz band, 60 GHz band, 3.6 GHz band, and / or 900 MHz band). Unlicensed spectrum may also include other bands. One or more of STA 110 and / or AP 105 may include resource allocation signaling component 130, which enables STA 110 and / or AP 105 to signal resource allocation in a WLAN preamble, for example, as further discussed below with reference to the accompanying drawings.

[0024] Although Figure 2 Although not shown, STA 110 can be covered by multiple AP 105s and therefore can be associated with multiple AP 105s at different times. The set of individual AP 105s and associated STA 110s is called the basic service set (BSS). The extended service set (ESS) is the set of connected BSSs. The distribution system (DS) is used to connect AP 105s in the extended service set. The coverage area 125 of AP 105 can be divided into sectors that constitute only a part of the coverage area. WLAN 100 includes AP 105s of different types (e.g., metropolitan area, home network, etc.) with different sizes of coverage areas and overlapping coverage areas for different technologies. Although not shown, other devices can communicate with AP 105s.

[0025] While STA 110 can communicate with each other via AP 105 using communication link 115, STA 110 can also communicate directly with each other via direct wireless communication link 120. A direct wireless communication link can exist between STA 110 regardless of whether any of them is connected to AP 105. Examples of direct wireless communication link 120 include Wi-Fi direct connections, connections established using tunneled direct link setup (TDLS) links, and other peer-to-peer (P2P) group connections.

[0026] Figure 1The STA 110 and AP 105 shown communicate according to a WLAN wireless and baseband protocol, which includes the physical (PHY) layer and medium access control (MAC) layer from IEEE 802.11 and its various versions (including but not limited to 802.11b, 802.11g, 802.11a, 802.11n, 802.11ac, 802.11ad, 802.11ah, 802.11Z, 802.11ax, etc.).

[0027] Transmissions to / from STA 110 and AP 105 typically include uplink (UL) or downlink (DL) transmissions. In downlink transmissions, control information within a header is transmitted before data transmission. The information provided in the header is used by the device to decode subsequent data. High-throughput WLAN preambles can be used to schedule multiple devices (e.g., STA 110) for simultaneous single-user transmission (e.g., single-user orthogonal frequency division multiple access, SU OFDMA) and / or MU-MIMO transmissions. In one example, the EHT WLAN signaling field can be used to signal multiple receiving STA 110s to inform them of the resource allocation mode. The EHT WLAN signaling field includes a common field that can be decoded by multiple STA 110s, which includes a resource allocation field. The resource allocation field indicates the allocation of resource units to multiple STA 110s and indicates which resource units in the resource unit allocation correspond to MU-MIMO transmissions and which resource units correspond to OFDMA single-user transmissions. Following the common field, the EHT WLAN signaling field also includes a private user field assigned to a specific STA 110. The order in which the private user fields are generated corresponds to the order in which resource units are allocated (e.g., the first private user field corresponds to the first allocated resource unit). The EHT WLAN signaling field is sent to multiple STA 110s along with the WLAN preamble.

[0028] This does not limit the use of some of the above embodiments for uplink transmission; that is, some of the above features or solutions are used in triggers that initiate uplink transmission.

[0029] like Figure 3 As shown, an embodiment of a method for transmitting scheduling information in a WLAN is provided: 101. Devices such as access points generate SIGs (such as EHT-SIG) that include indication or scheduling information. The term "generate" may be replaced by "construct", "acquire", or "determine".

[0030] 102. The above device sends SIG.

[0031] Accordingly, such as Figure 4 As shown, another embodiment of a method for receiving scheduling information in a WLAN at a non-AP station is illustrated.

[0032] 201. Receive a PPDU, which includes a SIG (e.g., EHT-SIG). The SIG may take the form discussed in the following embodiments. The PPDU may include L-STF, L-LTF, L-SIG, RL-SIG, U-SIG, and EHT-SIG.

[0033] In the EHT preamble, a 2 OFDM symbol-long, jointly coded U-SIG can exist immediately following the RL-SIG. The U-SIG contains version-independent fields. The purpose of version-independent content is to achieve better coexistence between future 802.11 generations. In addition, the U-SIG may have some version-related fields. The U-SIG is transmitted using 52 data tones and 4 pilot tones per 20 MHz. In EHT PPDUs sent to multiple users, a variable modulation and coding scheme (MCS) and a variable-length EHT-SIG can exist immediately following the U-SIG.

[0034] 202. Handling SIG. Specifically, obtaining scheduling information based on SIG.

[0035] EHT-SIG is a field name to distinguish it from other SIG-B fields, such as VHT-SIG-B and HE-SIG-B. EHT-SIG can be renamed in other ways; that is, the name itself is not important, but the content and structure discussed and described in the following embodiments provide a solution for efficiently scheduling resources and stations.

[0036] First, in an embodiment, the Resource Unit (RU) allocation field, via EHT-SIG, indicates at least the sequence of RUs in the frequency domain (the size and location of each RU), and may also indicate the information needed to calculate the number of users allocated to each RU. EHT-SIG also includes one or more user fields, each containing information about a scheduling station (STA); wherein, it allows the allocation of multiple consecutive or non-consecutive RUs (which may be referred to as MRUs or MRUs) as defined in 802.11ax to one or more STAs. As used herein, "MRU" generally refers to an RU composed of, for example, multiple consecutive or non-consecutive RUs defined in 802.11ax. These RUs can be considered as newly defined RUs in next-generation 802.11ax (e.g., 802.11be).

[0037] Compared to 802.11ax, each RU allocation subfield in the EHT-SIG content channel corresponding to the 20 MHz band indicates RU allocation (including the size of the RU and its location in the frequency domain, as well as one or more combinations of multiple RUs, which will be used in the EHT modulation field of the EHT MU PPDU in the frequency domain), and may also indicate the information needed to calculate the number of users allocated to each RU (non-MRU) and each combination of multiple RUs (MRU). In a preferred embodiment, the subcarrier index of the RU satisfies the conditions in a table that can be defined in the 802.11be standard (the RU is associated with each RU allocation subfield for each EHT SIG content channel and PPDU bandwidth).

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

[0039] For example: 11000y3y2y1y0 indicates 242-RU, y3y2y1y0 indicates the number of stations on 242-RU, and the number of stations is equal to y3y2y1y0+1; 11001y2y1y0 indicates 484-RU, y3y2y1y0 indicates the number of stations on 484-RU, and the number of stations is equal to y3y2y1y0+1; 11010y3y2y1y0 indicates 996-RU, y3y2y1y0 indicates the number of stations on 996-RU, and the number of stations is equal to y3y2y1y0+1.

[0040] The following embodiments omit the differences in RAs (if any) between 802.11ax to simplify the solutions of the embodiments or examples. That is, the values ​​of RAs used in the following embodiments / examples can be replaced by new values ​​corresponding to 802.11be. In some embodiments, the number of RUs that can be combined into an MRU is limited. That is, a limited number of MRUs can be defined, each MRU representing the size and location of multiple subcarriers in a bandwidth that overlaps with multiple RUs defined in 802.11ax.

[0041] Based on the RUs (e.g., small RUs: 26, 52, or 106) defined in 802.11ax, some examples of MRU (combinations) include MRUs comprising {52,26} or {106,26} within the 20 MHz, 40 MHz, or 80 MHz frequency bands. In some examples, only combinations of consecutive small-sized RUs should be introduced; in others, non-consecutive configurations are also permitted. For large RUs: 242, 484, or 996, some reasonable preferred MRU (combinations) include: 1. 242+484 (continuous and discontinuous, within each 80 MHz segment); 2. 242+242 (in the case of drilling holes, not continuous); 3. 484 + 996; 4. 242+484+242+484; 5. 242 + 484 + 996; 6. 242+242+996 etc. Furthermore, based on some predefined MRUs (i.e., combinations of RUs defined in 802.11ax, also known as MRUs), an important issue is providing an efficient indication solution to indicate the allocation of MRUs and the corresponding information for scheduling stations on those MRUs. In other words, the problem is how to indicate the allocation that allows multiple RUs to be assigned to a station and the station's information, and accordingly, how the station obtains information on whether it is scheduled and on which RU or MRU it is assigned, so that the station can communicate on the assigned RU or MRU accordingly.

[0042] Furthermore, the AP determines RU allocation based on various criteria. For example, the AP may decide to use the RU with the highest SNR for a specific user, and these RUs are not necessarily consecutive. Additionally, all RUs in a transmission may contain the same data packets for a single station, and all RUs in the MRU, as well as other RUs in the PPDU, may be used for the same service type.

[0043] Specifically, in some embodiments, a single FEC with the same parameters (e.g., MCS, encoding, N_SS, etc.) can be assigned to a STA that has an MRU.

[0044] The small RU and large RU described above may not be assigned to the same MRU allocation, or it is not recommended to allocate an MRU that includes both small and large RUs. In a preferred embodiment, small RUs may not be allocated across multiple 20 MHz channels. In short, an MRU includes a combination of 26-RUs, 52-RUs, or 106-RUs in the 20 MHz band; or, an MRU includes a combination of 242-RUs, 484-RUs, or 996-RUs in the transmission bandwidth. However, an MRU may not include one of the 26-RUs, 52-RUs, and 106-RUs in the first 20 MHz band, or one of the 242-RUs, 484-RUs, or 996-RUs overlapping with another 20 MHz band.

[0045] Some embodiments may have exceptions, namely, a special small RU in the first 20 MHz channel may be combined with an RU in another 20 MHz channel.

[0046] In some embodiments, the MRU of a small RU is not limited to include only consecutive RUs. This allows the scheduler to allocate RUs based on SNR (e.g., CQI feedback), allowing any combination of MRUs to be efficient.

[0047] This is not limited to combinations of small RUs.

[0048] Assuming the RMS latency spread is ~ If CP = ~1μsec, then the coherent BW is ~1MHz. Therefore, the average SNR on a given RU does not imply the average SNR on its consecutive RUs.

[0049] In this embodiment, based on supporting multiple RUs / non-contiguous RUs, channel utilization is improved by enhancing the ability to utilize channel selectivity to make channel utilization more efficient. Furthermore, improved channel usage will increase the overall system throughput and performance.

[0050] Example 1 The differences between EHT-SIG in this embodiment and HE-SIG B specified in 802.11ax are as follows: Multiple user fields can point to the same STA. The common portion is included in the EHT-SIG and has a similar structure to the common portion of HE-SIG B. However, multiple user fields of a STA are included in the user-specific fields of the EHT-SIG. For example, a first user field is followed by a second user field replicated elsewhere. In short, the MRU includes a first RU and a second RU. Therefore, the EHT-SIG includes a first user field corresponding to the first RU and a second user field corresponding to the second RU. Both the first and second user fields include the same station ID.

[0051] The first user field can be similar to the user fields defined in 802.11ax, but there are different solutions for other copied user fields (denoted as the second user field or the copied second user field).

[0052] Specifically, in one example, the copied second user field is identical to the first user field. This example overcomes the bias specified in 802.11ax that only one user field / station is mapped to one RU, thus being cost-effective when designing new chips.

[0053] In another example, the copied second user field includes the STA_ID field and other subfields that carry new signaling content related to the MRU. Compared to the first example, this solution supports MRUSTA in a more convenient way.

[0054] In the example above, multiple user fields can have the same size as each other, such as 21, 22, or 23 bits. The first user field may be the same as or similar to the 802.11ax user field (with essentially the same content or structure).

[0055] Typically, there are no restrictions on the position of the combined second RU (corresponding to the copied user field); however, in some examples, rules are set for the position of the combined second RU / copied user field to reduce interference or inefficiency.

[0056] The content of other user fields can be one of the following: Example 1, keep it the same as the first user field; Example 2, including content different from the first user field, like this: Similar to the first user field, the first 11 bits are used for STA_ID.

[0057] Some of the other bits (e.g., 1 bit or 2 bits) are used to signal the type of the user field (i.e., the meaning of the following bits).

[0058] The remaining bits can have any combination of the following new contents related to the MRU: Two bits indicate N_RU—the number of RUs (including the first RU) allocated to the STA, or how many RUs are included in the MRUs allocated to the STA. Therefore, the STA may be able to recognize a failure to decode any user field and stop the decoding process. Reserve the other 8 bits; or Indicates the size and location of each RU in the MRU assigned to the STA. For example, in the following way: For small RUs: a 9-bit bitmap can indicate which 26-tone RUs (26-tone RUs) are part of the MRU allocation in the same 20 MHz channel. 52-tone RUs can be indicated with appropriate 2 bits; 106-tone RUs can be indicated with appropriate 4 bits. The 10th bit is reserved.

[0059] For large RUs: an 8-bit bitmap can indicate which 242-tone RUs are part of the MRU allocation in the same 80 MHz channel and the next 80 MHz channel. A 484-tone RU (2×242-tone RU) can be indicated with 2 bits; a 996-tone RU (4×242-tone RU) can be indicated with 4 bits. Bits 9 and 10 are reserved. In this embodiment, MRUs are limited to the 160 MHz boundary. The STA knows whether an MRU has been allocated to it after decoding the EHT-SIG. Therefore, no special signaling is needed for the MRU user field.

[0060] Figure 5 An example of the indication structure of Embodiment 1 is shown. The RU allocation (RA) field in the common part of EHT-SIG is set to "00000100", which indicates the allocation of the RU sequence [26, 26, 52, middle 26, 26, 26, 26, 26]. Therefore, the corresponding user-specific fields include 8 user fields (UFs). In this example, UF1 is mapped to the first 26-RU, including information about STA1, such as STA1's AID. UF2 is mapped to the second 26-RU, including information about another STA, and its content and structure may also be similar to the user fields in 802.11ax.

[0061] UF3 corresponds to 52-RU. UF3 includes a station information field, which is also set to the AID of STA1. The content of UF3 includes different examples: In one example, UF3 also includes a bitmap “101101000”, where each bit corresponds to a 26-RU and indicates which 26-RUs are in the MRUs allocated to STA1. In this example, “101101000” indicates that the first / third / fourth / sixth 26-RU is included as an MRU that is allocated to STA1.

[0062] In another example, UF3 may also include an N-RU field instead of a bitmap. The N-RU field indicates the number of RUs in the RU sequence [26,26, 52, middle 26, 26, 26, 26, 26, 26] that are combined into an MRU, which is assigned to STA1. In this example, the number of RUs is 3.

[0063] Figure 5 Other UFs are also described.

[0064] At the station side, the STA can learn from the RA field the size and location of the RU sequence corresponding to the 20 MHz allocation, and can also know whether the STA has been scheduled / assigned and which RU among one or more RUs the STA has been assigned to.

[0065] For example, the STA can know from "00000100" that the RU sequence corresponding to the 20 MHz allocation is the RU sequence [26,26, 52, middle 26, 26, 26, 26, 26]. Furthermore, based on UF1, UF3, and UF5, it can know that the STA is scheduled and is scheduled on the first, third, and fifth RUs in the aforementioned RU sequence (first, third, and fifth are the order in the sequence). That is, the MRU consists of "first 26-RU, second 52-RU, sixth 26-RU", and "first 26-RU, second 52-RU, sixth 26-RU" is the order in the 20 MHz tone plan.

[0066] Table 27-7 – Data and Pilot Subcarrier Index of RU in 20MHz HE PPDU and Non-OFDMA 20MHz HE PPDU

[0067] like Figure 6 As shown, another example of resource allocation in Embodiment 1 is illustrated, in which the first, third, fourth, and fifth 242-RUs are allocated to STA1 in 160MHz; and the sixth and eighth 242-RUs are allocated to STA2.

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

[0069] In the example, the common part of CC1 includes “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 includes “11000000(RA-2, 242(1)), 11001000(RA-4, 484(1)), 11000000(RA-6, 242(1)), 11000000(RA-8, 242(1))”. In CC1, “11000000(RA-1), 01110010(RA-3), 11000000(RA-5), 11000000(RA-7)” correspond to the first 20 MHz, the third 20 MHz, the fifth 20 MHz, and the seventh 20 MHz, respectively; in CC2, “11000000(RA-2), 11001000(RA-4), 11000000(RA-6), and 11000000(RA-8)” correspond to the second 20 MHz, the fourth 20 MHz, the sixth 20 MHz, and the eighth 20 MHz. “11000000” indicates the allocation of 242(1) (i.e., 242-RU with 1 user field), and “01110010” indicates the allocation of 484-RU with 0 user fields in the content channel containing the corresponding 8-bit RU allocation subfield “01110010”. "11001000" indicates the allocation of a 484-RU with one user field in the content channel containing the corresponding 8-bit RU allocation subfield "11001000". The common part of CC1 together with the common part of CC2 indicates the allocation of 160 MHz (i.e., the RU sequence [242, 242, 484, 242, 242, 242, 242]).

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

[0071] UF1 is the first user field containing the ID of STA1. UF4 and UF5 are second user fields containing the ID of STA1 (same as UF1) and a first bitmap, which is 8 bits long. Each bit in the first bitmap indicates whether the corresponding 242-RU is among the MRUs allocated to STA1 (e.g., 10111000 above indicates that the first, third, fourth, and fifth 242-RUs are allocated to STA1). UF6 and UF8 contain the same ID as STA2. In UF8, a second bitmap is preferably included, which is 8 bits long or the remaining bits besides the RUs already allocated in the first bitmap (i.e., 4 bits in this example). Each bit in the second bitmap indicates whether the corresponding 242-RU is among the MRUs allocated to STA1 (e.g., 10111000 above indicates that the first, third, fourth, and fifth 242-RUs are allocated to STA1). UF2 and UF7 are user fields for unallocated MRUs, which will not be discussed in detail here.

[0072] In this example, if RU r is a 484-tone RU or larger (which is the largest predefined RU in the MRU), then the number of users assigned to the MRU is equal to the number of user fields of that RU r in the MRU summed across two EHT-SIG-B content channels, i.e., Nuser(r, CC1) + Nuser(r, CC2), where r is the largest RU in the MRU. In the example above, 484-RUs and 242-RUs are included in the MRU assigned to STA1, and the number of users is determined by the 484-RU: n1(second 484-RU, CC1) + n2(second 484-RU, CC2) = 0 + 1 = 1. In this example, one station is assigned to the MRU, but there is no restriction on assigning multiple stations to the MRU.

[0073] exist Figure 8In the example, resource allocation is similar, but MRU1, which includes 484-RU, is allocated to two stations. In this example, the common part of CC1 includes "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 includes "11000000(RA-2, 242(1)), 11001000(RA-4, 484(1)), 11000000(RA-6, 242(1)), 11000000(RA-8, 242(1))". In CC1, “11000000(RA-1), 11001000(RA-3), 11000000(RA-5), 11000000(RA-7)” correspond to the first 20 MHz, the third 20 MHz, the fifth 20 MHz, and the seventh 20 MHz, respectively; in CC2, “11000000(RA-2), 11001000(RA-4), 11000000(RA-6), 11000000(RA-8)” correspond to the second 20 MHz, the fourth 20 MHz, the sixth 20 MHz, and the eighth 20 MHz. “11000000” indicates the allocation of 242(1) (i.e., 242-RU with 1 user field); “11001000” indicates the allocation of 484-RU with 1 user field in the content channel containing the corresponding 8-bit RU allocation subfield “11001000”. The common part of CC1, together with the common part of CC2, indicates the allocation of 160 MHz (i.e., the RU sequence [242, 242, 484, 242, 242, 242, 242]).

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

[0075] UF3 and UF4 correspond to the same 484-RUs in MRU1 assigned to two stations (indicated by RA3 and RA4) (e.g., STA1 and STA3), and should include the IDs of STA1 and STA3 respectively. If UF3 includes the ID of STA1, then UF3 is the second user field of STA1 (indicating that the second 484-RU is in MRU1), and UF3 also includes a first bit diagram, which is 8 bits, with each bit indicating whether the corresponding 242-RU is in the MRU assigned to STA1; UF4 includes the ID of STA3, and UF3 is the first user field of STA3.

[0076] Alternatively, if UF3 includes the ID of STA3, then UF3 is the first user field of STA3; UF4 may include the ID of STA1, UF3 is the second user field of STA1 (indicating that the second 484-RU is in MRU1), and UF4 also includes a first bit diagram, which is 8 bits in length, with each bit in the 8 bits indicating whether the corresponding 242-RU is in the MRU assigned to STA1.

[0077] UF5 corresponds to RA5 (indicating the fifth 242-RU). UF5 is the second user field that includes the ID of STA1 or STA3 (indicating the fifth 242-RU is in MRU1) and the first bit diagram. The first bit diagram is 8 bits, and each bit in the 8 bits indicates whether the corresponding 242-RU is in the MRU assigned to STA1 and STA3 (for example, the above 10111000 indicates that the first, third, fourth, and fifth 242-RUs are assigned to STA1 and STA3).

[0078] UF6 and UF8 include the same ID as STA2. In UF8, a second bitmap is preferably included, which is 8 bits or the remaining bits other than the RUs already allocated in the first bitmap (i.e., 4 bits in this example). Each bit in the 8 bits indicates whether the corresponding 242-RU is in the MRUs allocated to STA1 (e.g., 10111000 above indicates that the first, third, fourth, and fifth 242-RUs are allocated to STA1).

[0079] UF2 and UF7 are user fields for unassigned MRUs, which will not be discussed in detail here.

[0080] In this example, if RU r is a 484-tone RU or larger (which is the largest predefined RU in the MRU), then the number of users assigned to the MRU is equal to the number of user fields of that RU r in the MRU summed across two EHT-SIG-B content channels, i.e., Nuser(r, CC1) + Nuser(r, CC2), where r is the largest RU in the MRU. In the example above, 484-RUs and 242-RUs are included in the MRU assigned to STA1, and the number of users is determined by the 484-RU: n1(second 484-RU, CC1) + n2(second 484-RU, CC2) = 1 + 1 = 2. In this example, two stations are assigned in the MRU, but there is no restriction on assigning more than two stations to the MRU.

[0081] In Example 1, additional MRU information can be indicated by modifying the remaining bits in the copied user field; and this solution does not require adding additional entries to the RU allocation subfield; the MRU definition and signaling are relatively simple.

[0082] Example 2 In the second embodiment, the EHT-SIG includes a common field that accommodates additional RUs, and wherein the RU allocation includes combinations of RUs (MRUs). Furthermore, the user-specific field has a subfield defining the MRU allocation, which is different from the user-specific field in 802.11ax.

[0083] Figure 9a , Figure 9b , Figure 9c An example of the public fields of EHT-SIG is shown. In addition to the RA field and other information, the public fields of EHT-SIG include one or more fields (for example, the RA field corresponding to a 20 MHz segment or a 40 MHz segment may be longer than the RA field in the prior art to allow for more allocations or allow for the allocation of more STAs).

[0084] The aforementioned fields include a first field and / or a second field. The first field, N_MRU_1, corresponds to each 20 MHz segment present in the entire BW. This field occupies N×2 bits and indicates the number of MRUs present in each 20 MHz channel (small MRUs include small-sized RUs, such as 26-RU, 52-RU, or 106-RU). The second field, N_MRU_2, corresponds to the entire transmission bandwidth and indicates the number of larger-sized MRUs (how many MRUs) in the transmission bandwidth (large MRUs include, for example, 242-RU, 484-RU, or 996-RU). Specifically, because N_MRU_2 refers to the entire BW, N_MRU_2 is the same for CC1 and CC2. Since N_MRU_1 refers to each 20 MHz separately, N_MRU_1 is likely to be different for CC1 and CC2.

[0085] Details are as follows: The N_MRU_1 field (N×Nb bits), also known as the small MRU quantity field, indicates the number of small MRUs allocated / present in the corresponding 20 MHz channel / band. This field can be located after the RU allocation (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×Nb bits, where N is the number of 20 MHz channels in CC1 or CC2, and Nb is 1 or 2. A small MRU is an RU consisting of several small RUs of any size of 26, 52, or 106. There is no restriction that the RUs in a small MRU include small RUs of different sizes, nor is there a restriction that a small MRU can be larger than 106, but the small MRU must be within 20 MHz; otherwise, larger RUs can be indicated, such as 242-RU, 484-RU, 996RU, or 2×996 RU. Only one MRU may be available per 20 MHz band. Therefore, this field may require 1 or 2 bits. Thus, if 1 bit is implemented, a "1" indicates the presence of an MRU in the corresponding 20 MHz band, while a "0" indicates the absence of an MRU in the corresponding 20 MHz band. This may also be helpful in Example 3 later.

[0086] The N_MRU_2 field, also known as the large MRU quantity field, indicates the number of large MRU allocations present throughout the entire bandwidth. This field can be located before the CRC and tail of each CC in the EHT-SIG. The total overhead of the N_MRU_2 field in the EHT-SIG can be 2 bits, where N is the number of 20 MHz bands. A large MRU is an RU consisting of several large RUs of any size of 242, 484, or 996. There is no restriction on the inclusion of large RUs of different sizes within a large MRU, nor is there a restriction that a large MRU can be larger than 996, but the large MRUs must be present throughout the entire transmission bandwidth.

[0087] Figure 9a The structure of the common part of EHT-SIG B in 20MHz bandwidth transmission is shown.

[0088] Figure 9b The structure of the common part of EHT-SIG B in 40MHz bandwidth transmission is shown.

[0089] Figure 9c The structure of the common portion of EHT-SIG B in 80MHz bandwidth transmission is shown. The structures of other common portions of EHT-SIG B in other bandwidths are similar and will not be repeated here.

[0090] Figure 10a An example of resource allocation and scheduling stations on a RU is described. Figure 10bDescribes instructions Figure 10a The structure of the common fields of the EHT-SIG for resource allocation. The common fields include: the RU allocation subfield "00000100", which indicates an allocation representing [26, 26, 52, middle 26, 26, 26, 26]. The first field "10" indicates the presence of 2 MRUs in the corresponding 20 MHz channel (as described above). Figure 9a The MRUs of STA1 and STA2 are listed in the table. The second field "00" indicates that there is no MRU with a large RU. The common fields also include the RU allocation subfield "00001011", which indicates an allocation representing [52, 26, 26, middle 26, 52, 52]. The first field "10" indicates that there are 2 MRUs in the corresponding 20 MHz channel. Figure 9a (MRUs in STA3 and STA4). The second field "00" indicates that there is no MRU with a large RU.

[0091] Figure 11a This example illustrates the structure of the user-specific field in the EHT-SIG of this embodiment. The user-specific field includes two subfields: MRU user-specific fields are typically placed before single RU-specific fields. Single RU User-Specific Fields. Single RU user-specific fields include one or more single RU user fields assigned on a single RU, which is a general RU that is not combined with other RUs. MRU User Fields correspond to MRUs and include at least: STA_ID and an RU bitmap that indicates the size and location of each RU included in the MRU. Figure 11b An example of the structure of the MRU user field in the EHT-SIG user-specific fields is shown.

[0092] Figure 12a and Figure 12b It shows the following Figure 10a The structure of the user field in the example EHT-SIG user-specific fields. The MRU user field contains the following information: STA_ID (11 bits), MCS (4 bits), encoding (1 bit), RU bitmap (indicating RUs belonging to the same MRU allocation), CRC, and trailer (10 bits).

[0093] Specifically, the RU bitmap indicating the size and location of each RU included in the MRU can be indicated in at least two ways. For example, for a small RU, there are nine 26-tone RUs, so the RU bitmap in each CC consists of nine bits, with each bit mapping one 26-RU, see [link to relevant documentation]. Figure 12a .

[0094] 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 band can be extracted from the public fields. The RU bitmap in each CC consists of several bits. The number of bits equals the number of RUs in the 20 MHz band allocation. Each bit maps to a RU in the RU sequence; see [link to relevant documentation]. Figure 12b Because the RU sequence in the first 20 MHz band includes 8 RUs, the RU bitmap in CC1 consists of 8 bits. Each bit maps to one of the 8 RUs. Because the RU sequence in the first 20 MHz band includes 6 RUs, the RU bitmap in CC2 consists of 6 bits, with each bit mapping to one of the 6 RUs.

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

[0096] In the above embodiment 2, by separating the MRU user-specific field and the single RU user-specific field, MRU information can be added, and the total size is reduced for an MRU consisting of 3 or more RUs, provided that the error probability of SIG-B is the same for each STA.

[0097] Example 3 In some embodiments, a new RU size is defined, which is called an MRU.

[0098] Therefore, the RU-allocation subfield includes entries / indexes that indicate allocations including MRUs.

[0099] In this embodiment, because each RU or MRU only requires a single user field, the number of user-specific fields is not increased. That is, there is no need to include multiple user fields to correspond to one MRU.

[0100] As mentioned above, RU allocation is determined by the AP based on various criteria. When determining the preferred RU or MRU, the resources required by the transit station are taken into account.

[0101] Table 1 below shows the required resources (especially less than 20 MHz) and examples of preferred RUs or MRUs based on the required resources.

[0102] Table 1

[0103] The new table for the RU allocation subfield is based on one or more of the RU / MRUs mentioned above, and the number of MRUs and the position of each RU within the MRUs can also be considered. The more flexible the MRUs, the more indexes are needed. Preferred RUs / MRUs can be defined and restricted to reduce the complexity of the RU allocation subfield.

[0104] Table 2 below is another example of the required resources (especially greater than 20 MHz, supporting 320 MHz bandwidth) and the preferred RU or MRU based on the required resources.

[0105] Table 2

[0106] To reduce the complexity of instructions and more efficiently meet resource requirements, a preferred MRU is provided. See also Figure 13 Simulation results show that the SNR gain obtained by combining the optimal 26-RU with RU>26 to form an MRU is negligible. In particular, the combination of the optimal 26-RU with a given 26-RU results in an SNR of >3dB.

[0107] Therefore, for the 20 MHz band, in the example, the preferred MRU includes a combination of an intermediate 26-RU and its consecutive 52-RU / 106-RU, or a combination of two 26-RUs different from the already defined 52-RU. It can also be referred to as an aggregated intermediate 26-RU and its consecutive 52-RU or 106-RU, or an aggregated non-consecutive 26-RU.

[0108] However, even with the above constraints, too many entries are still needed to support other MRU combinations, so in some cases expanding the RU allocation table may be impractical.

[0109] Table 3

[0110] Referring to Table 3, too many entries are needed to support other MRU combinations, such as two concurrent MRUs consisting of 2×26-RUs. Therefore, in Alternative Embodiment 3, instead of expanding the RU allocation subfield to a large dimension, a new field is included to indicate the size and location of each RU aggregated in the MRU; this new field can be called the common MRU. Examples are as follows... Figure 14 As shown.

[0111] The common MRU field exists only if any MRU is present in the PPDU (in any 20 MHz channel). Therefore, the common MRU field can be signaled in the U-SIG prior to the EHT-SIG, or signaled as an additional bit / field in the common field of the EHT-SIG.

[0112] For small MRUs: The public MRU field is encoded separately.

[0113] This public MRU field includes three bitmap subfields, as shown below: MRU_1 – can be 9 bits, indicating which 26-RUs are included in the first MRU.

[0114] MRU_2 – can be 7 bits, indicating which 26-RUs are included in the second MRU.

[0115] MRU_3 – can be 5 bits, indicating which 26-RUs are included in the third MRU.

[0116] Therefore, an additional 21 bits (22 bits including signaling bits indicating the presence of an MRU) are required to signal any combination of up to 3 MRUs per 20 MHz band.

[0117] Because the number of user fields in user-specific fields has been reduced, additional bits will be saved subsequently.

[0118] In this embodiment, although the public MRU field may seem expensive, we should remember that a greater amount of additional bits will be saved later due to the reduced number of user fields in the user-specific fields.

[0119] For large MRU: For RU>=242 tones, the large MRU is identified by the corresponding RU allocation subfield.

[0120] In this case, the public MRU field (bitmap) indicates which other RUs (>242) correspond to the same MRU.

[0121] MRU_1 — Can be 8 bits (9th bit omitted): Indicates which 242-RUs belong to the MRU. MRU_2 - omitted MRU_3 - omitted Similar to the case of small MRUs, the overhead of user-specific fields is also reduced. That is, for the indicated MRU, one or more user fields are included, and the station ID is not repeated in different user fields. When a station determines which RUs / MRUs are assigned to the station, the quantity, station, or user field indicated by the RU allocation field still applies.

[0122] User-specific fields are included in the EHT-SIG, where each RU / MRU, indicated by the RU allocation subfield and / or the common MRU field, is mapped to one or more user fields, typically with user fields mapped sequentially to MRUs / RUs. Since the positions of RUs within an MRU may alternate, there should be rules governing the mapping between MRUs and the one or more user fields assigned to them. In the example, the position of the MRU is defined by the position of the first RU in the lowest frequency domain. See also... Figure 17a Based on the frequency order of 26-RU1, 26-RU2, and 52-RU2, MRU1 is an MRU in which 26-RU1 is the lowest RU, MRU2 is an MRU in which 26-RU2 is the lowest RU, and MRU3 is an MRU in which 52-RU2 is the lowest RU.

[0123] One or more user fields of an MRU / RU can be mapped to an MRU / RU in a manner similar to that in 802.11ax. The location of the user fields of the MRU will be... Figure 15 and Figure 16 The two examples in the text show that the lowest frequency RU is consistent. In another interpretation, each user field of the MRU points to the first RU of the MRU (the RU with the lowest frequency).

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

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

[0126] for Figure 15 For example, MRU1 includes 26-RU-1 and 26-RU-3, and the sequence / order of MRU / RU is [MRU1, 26-RU 2, 26-RU 4, 26-RU 5, 52-RU 3, 52-RU 4]. User fields are mapped to MRU / RU in sequence. For Figure 16 For example, MRU1 includes 52-RU 2 and 26-RU 5, and the sequence / order of MRU / RU is [26-RU1, 26-RU 2, MRU1, 52-RU 3, 52-RU 4], with user fields mapped to MRU / RU in sequence.

[0127] Figure 17a An example of an RU / MRU allocation is shown, which includes three M-RUs in a 20 MHz band. See also Figure 17b The complete public field "1 0 0 0 0 1 1 1 0 0 0 0 0 1 1 0 1 0 0 1 1 1 0 0 1 1 11 1" includes the MRU indicator, the RU allocation subfield, the first MRU bitmap, the second MRU bitmap, and the third MRU bitmap. Details are as follows: The MRU indicator is 1 bit and indicates whether any MRUs exist in the allocation. The RU allocation subfield can be 8, 9, or 10 bits, indicating the sequence of RUs corresponding to the 20 MHz band (the size and location of each RU). In this example, "00000111" indicates an allocation of [26, 26, 52, middle 26, 52, 52].

[0128] The first MRU bitmap is labeled MRU_1, indicating which 26-RUs are in the first MRU. In this example, 100000011 indicates that the first, eighth, and ninth 26-RUs are combined into the first MRU. The first MRU bitmap typically starts with 1 (MSB is 1), indicating that the MRU includes the 26-RUs at the left edge.

[0129] The second MRU bitmap is labeled MRU_2, indicating which 26-RUs are in the second MRU. In this example, 0100011 indicates that the second, sixth, and seventh 26-RUs are combined into the second MRU. Only 6 bits are needed, so the MSB is 0.

[0130] The third MRU bitmap is labeled MRU_3, indicating which 26-RUs are in the third MRU. In this example, 00111 indicates that the second, sixth, and seventh 26-RUs are combined into the second MRU. Only 3 bits are needed, so 2 MSB is 0.

[0131] exist Figure 17c In the same example based on RU / MRU allocation, the following alternative solution is provided: The RU allocation field in the EHT-SIG common field indicates the size and location of the RU in the frequency band, and the EHT-SIG common field also includes one or more common MRU fields, each indicating the RU (i.e., the allocated RU) within the MRU, as indicated by the RU allocation field. This is consistent with... Figure 17b The difference lies in the granularity used for MRU indication. Preferably, the length of the common MRU field decreases sequentially, and the order of the common MRU fields is based on the first RU in the MRU in the frequency domain.

[0132] For example, the RU allocation field is set to 0 0 0 0 0 1 1 1.

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

[0134] The number of bits required for this solution may be more than Figure 17b The bits in that are much shorter. See also Figure 17c MRU_1 is 6 bits, MRU_2 is 4 bits, and MRU_3 is 2 bits.

[0135] RU allocation field: 0 0 0 0 0 1 1 1 The common MRU field 1 (MRU_1) indicates which RU is in the first MRU. For example, 0 0 0 1 0 0 0 0 1. Only 6 bits are needed for 1 0 0 0 0 1, so the 3 MSBs can be set to 0 or used for other functions, and sometimes the first 3 bits can be omitted.

[0136] Public MRU field 2 (MRU_2): 0 0 0 1 0 0 1. Only 4 bits are needed, so the 3 MSBs can be set to 0, used for other functions, or omitted.

[0137] Public MRU field 3 (MRU_3): 0 0 0 1 1. Only 2 bits are needed, so 3 MSB can be set to 0 or used for other functions.

[0138] The order of the common MRU fields is consistent with the order of the first RU in the frequency domain MRU. See also Figure 17a .

[0139] Figure 18 A solution is provided to indicate the RU / MRU allocation per 160 MHz BW for a large MRU. In this example, there are two MRUs: one MRU includes 242-RU 1, 242-RU 3, 242-RU 4, and 242-RU 7 (shown in gray); the other MRU includes 242-RU 5, 242-RU 6, and 242-RU 8.

[0140] EHT-SIG comprises CC1 and CC2. EHT-SIG information can be divided into CC1 and CC2 to reduce overhead and improve information robustness.

[0141] The common fields of CC1 include: RU allocation information (field) for each 20 MHz or 40 MHz band with an odd number. For example, in this example, the 20 MHz band is 1 1 1 0 0 xxx.

[0142] The common fields of CC2 include: RU allocation information (field) for each 20 MHz or 40 MHz band with an even number. For example, in this example, the 20 MHz band is 1 1 1 0 0 xxx.

[0143] In alternative solutions, the aforementioned public fields may be omitted in other solutions, or indicated in a manner described in other embodiments.

[0144] MRU_1 is valid and has a length of 8 bits.

[0145] The MRU_1 field in CC1 also corresponds to the odd-numbered 20 MHz or 40 MHz segments. Figure 18 In the example, the first four bits are mapped to the 1st, 3rd, 5th, and 7th 20 MHz segments in the main 160 MHz or unique 160 MHz BW, respectively. If the BW is 320 MHz, the following four bits are mapped to the 9th, 11th, 13th, and 15th 20 MHz segments, respectively.

[0146] The MRU_1 field in CC2 also corresponds to the even-numbered 20 MHz or 40 MHz segments. Figure 18 In the example, the first four bits are mapped to the 1st, 3rd, 5th, and 7th 20 MHz segments in the main 160 MHz or unique 160 MHz BW, respectively. If the BW is 320 MHz, the following four bits are mapped to the 9th, 11th, 13th, and 15th 20 MHz segments, respectively.

[0147] Similarly, the MRU_2 field indicates the RU in MRU_2 in a similar way to the MRU_1 field.

[0148] In some solutions, MRU_2 and MRU_3 are omitted based on the MRU signal bits and RA subfield in the common part.

[0149] Figure 19 An example of a transmission involving hybrid MRUs (large MRUs and small MRUs) is provided. In this example, 242-RU 2 is allocated as follows: Figure 17a and Figure 17b The small MRU, the other 242-RU are allocated in, for example Figure 18 In the large MRU.

[0150] The RA field (including RA 2 of 242-RU 2) is used in conjunction with... Figure 18 A similar approach is found in the public section of EHT-SIG.

[0151] In CC2, a small MRU_1 / 2 / 3 field can be added to the position of the MRU field corresponding to RA2.

[0152] In this embodiment, by providing a common subfield with an MRU bitmap, several technical advantages are achieved: any combination of MRUs can be defined, extending the RU allocation subfield can be avoided, making the implementation more practical, and reducing the overall overhead in EHT-SIG.

[0153] Example 4 In this embodiment, MRUs can be assigned to a single station, and preamble puncturing is also considered. This embodiment is applicable to systems such as 996-RU or 1992-RU (2 996-RU) or 3984-RU (2 In the case of a large RU (RU>484) allocation (996-RU), where some of these RUs within the 20 MHz segment are punctured, the available information about channel puncturing is used to define the large punctured RU as a single RU, rather than several smaller RUs. This information is available in the field preceding EHT-SIG, which may be called "U-SIG" and can be indicated by 2 or more bits. The common portion of EHT-SIG does not include information about puncturing of the sub-channels (20 MHz).

[0154] Assume puncturing occurs frequently (especially in dense networks). Referring to RU>484, puncturing information is included in the SIG (possibly defined in the U-SIG). This puncturing information is used to define or indicate discontinuous large RUs (RUs after puncturing). Therefore, the SIG can also include a single user-specific field (in the EHT-SIG), where one or more user fields are included to correspond to discontinuous large RUs. These user fields each include information about different stations. Therefore, these stations are assigned to discontinuous large RUs via MU-MIMO.

[0155] Figure 20An example of the above embodiment in a 160 MHz bandwidth is shown. In this example, a first 996-RU is allocated to STA1, where a second 242-RU is punctured, this allocation being equal to the allocation of the first 242-RU and the second 484-RU to STA1. A second 996-RU is allocated to STA2, where the second 242-RU is punctured, and a sixth and eighth 242-RU are allocated to STA2. In this example, the frequency resource allocated to STA1 can be defined or considered as a punctured 996-RU (shown as the primary 80 MHz). A single user-specific field (where different user fields have different station information) can be included in the EHT-SIG to correspond to the punctured 996-RU, instead of the case in Embodiment 1, i.e., two user fields are required for the two RUs, where the first user field corresponds to the first 242-RU and the second user field corresponds to the second 484-RU, and the first and second user fields include the same station ID. Similarly, the frequency resource allocated to STA2 can also be defined or considered as a punctured 996-RU (shown as the secondary 80 MHz). Instead of the case in Example 1, a single RU can be included in the EHT-SIG to correspond to the punched 996-RU, i.e., two RUs require two user fields, where the first user field corresponds to the sixth 242-RU and the second user field corresponds to the eighth 242-RU.

[0156] When the STA learns that it has been assigned RU-996, the STA already knows that the RU has been punched.

[0157] Reduce expenses Furthermore, any receiver that supports the methods proposed above (especially Huawei devices) can easily decode signals defined by the same proposed methods, thereby disclosing the use of the invention by competitor transmitters.

[0158] Example 5 As described in Example 3, a new table can be defined, wherein the newly defined MRU is also indicated by an index / bit sequence defined in the RU allocation subfield.

[0159] The RU allocation subfield (RA) 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 are supported; that is, one or more of the MRUs listed above can be in the RU allocation and indicated by the index corresponding to the RU allocation. More bits are needed to indicate the number of stations when more stations can be allocated to a RU or MRU. When indicating the number of MRUs and stations on the MRUs in the RU allocation, the mapping between the RU / MRU and user fields is indicated by the sequence of RU / MRUs and the sequence of station / user fields, i.e., a sequential one-to-one mapping.

[0160] As mentioned above, RU allocation is determined by the AP based on various criteria. When determining the preferred RU or MRU, the resources required by the transit station are taken into account.

[0161] To reduce the complexity of the table, preferred or restricted allocations of RU or MRU are defined in the table, and inefficient RU / MRU allocations are not allowed.

[0162] Table 4 below shows the required resources (especially less than 20 MHz) and examples of preferred RUs or MRUs based on the required resources.

[0163] Table 4

[0164] The new index table for the RU allocation subfield may need to consider the preferred RU / MRU mentioned above, and may also consider the number of MRUs and the position of each RU in the MRU. The more flexible the MRU, the more indexes are needed.

[0165] Table 5 below is another example of required resources (especially greater than 20 MHz, supporting 320 MHz bandwidth) and preferred RUs or MRUs based on the required resources, with the preferred RUs or MRUs requiring entries in the index table of the RU allocation subfield.

[0166] Table 5

[0167] The above-mentioned maximum consecutive M 242-RUs (large MRUs) are defined and mapped to indices. The large MRUs start from the initial 242-RU in the frequency domain, and the starting RA of the M×242 (the first RA in the common part of the EHT-SIG of the M×242 MRUs) corresponds to the initial 242-RU. The large MRU can be punched in the frequency domain by the second RA corresponding to 20 MHz after the initial 242-RU.

[0168] Table 6 below may further restrict large MRU, which requires entries in the index table of the RU allocation subfield.

[0169] Table 6

[0170] This can further reduce the size of the MRU.

[0171] The number of entries required for each large MRU can be based on the number of stations that can be allocated on the large MRU. For example, when there are 16 stations supporting MU-MIMO, the number of entries per large MRU could be 16. There is no restriction on the value of the index; the 2, 3, or 4 bits in the index are used to indicate the number of stations on the large MRU.

[0172] Based on the above solutions, for Figure 6 In the example above, 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. RU allocation can be indicated by the following common parts of the EHT-SIG: The common parts of CC1 include “RA-1, indicating 5×242 MRU (n1)”; RA-3, indicating 5×242 MRU (n1); RA-5, indicating 5×242 MRU (n1); RA-7, indicating 242 (n4)”; The common parts of CC2 include “RA-2, indicating 242 (n2); RA-4, indicating 5×242 MRU (n1); RA-6, indicating 3×242 MRU (n3); RA-8, indicating 3×242 MRU (n3)”.

[0173] n1, n2, n3, and n4 are the number of stations on the large MRU in CC1 or CC2.

[0174] In the above embodiments, only the common parts of EHT-SIG were discussed; user-specific fields may be similar to the 802.11ax solution. The sequence of user fields is located in the corresponding user-specific fields of the EHT-SIG and maps to the RU or MRU in the allocation indicated by the RA field.

[0175] In some special cases, in addition to the MRU indicated by the RA field, other types of MRUs can also be indicated by the user field.

[0176] Example 6 Implementations can be combined in ways that work and modified in ways that still work or work better; some examples are provided below. In Implementation 6a, a signaling method for a small RU is provided, wherein the indication field in the common part of the EHT-SIG consists of two fields (the existing RA field and the additional signaling assigned to the MRU).

[0177] This method allows any combination of small RUs to be defined as an MRU, while preserving the definition of the 20 MHz allocation mapping for 802.11ax (RU allocation subfield).

[0178] The instruction includes the RA field and additional signaling indicating which RUs defined in the RA field are assigned as MRUs.

[0179] For example, if we want to assign the following mapping {26, 26+52, 26, 26, 52 in the middle}; Among them, the second 26-RU and the second 52-RU include the MRU. We first indicate the 8-bit RA field '00000101', which defines the allocation mapping of {26, 26, 52, middle 26, 26, 26, 52}. Then, specifically, the MRU consisting of the second 26-RU and the second 52-RU is indicated.

[0180] In this method, a single user-specific field will be indicated in the EHT-SIG for each MRU, as specified in the above embodiments.

[0181] Example 6a In this embodiment, a method is provided to indicate MRU allocation using a bitmap, wherein each bit corresponds to a specific RU defined in the RA field.

[0182] Each 20 MHz may include up to 4 MRUs, therefore the MRU allocation field will include 4 parts. In alternative solutions, 1, 2, or 3 MRUs may be allowed.

[0183] The first part—the first MRU—can be any combination of RUs defined in the RA field.

[0184] The maximum number of RUs in 20 MHz is 9, so we use 9 bits to cover all possible allocations. The actual number of bits used for MRU allocation will be equal to the number of RUs defined in the RA field, starting from the LSB or MSB (9 bits). If the number of RUs defined in the RA field is less than 9, the redundant bits are irrelevant bits.

[0185] For example, the RA field '00000101' defines the RU allocation of [26, 26, 52, middle 26, 26, 26, 52]. Bitmap 0 0 1 1 0 0 0 means that the second 52-RU and the middle 26-RU are assigned as MRUs, while two irrelevant bits will be added to the bitmap.

[0186] The second part – the second MRU – can be any combination of those RUs defined in the RA field and not included in the first MRU.

[0187] The maximum number of RUs not included in the first MRU is 7, therefore we use a 7-bit bitmap. The actual number of bits used for the second MRU will be equal to the number of RUs defined in the RA field starting from the LSB or MSB (7 bits) minus the number of RUs included in the first MRU. Redundant bits are irrelevant bits.

[0188] For example, according to the allocation defined in the previous section, bits Figure 1 1 0 0 0 means that the first 26-RU and the second 26-RU are assigned as MRU, and two irrelevant bits will be added to the bitmap.

[0189] Part Three – The Third MRU can be any combination of those RUs defined in the RA field and not included in the First MRU and the Second MRU.

[0190] The maximum number of RUs not included in the first and second MRUs is 5, therefore we use a 5-bit bitmap. The actual number of bits used for the second MRU will be equal to the number of RUs defined in the RA field starting from the LSB or MSB (5 bits) minus the number of RUs included in the first and second MRUs. Redundant bits are irrelevant bits.

[0191] For example, based on the allocations defined in the first two parts, bitmap 0 1 1 means that the seventh 26-RU and the fourth 52-RU are allocated as MRUs.

[0192] Part Four – The fourth MRU can be any combination of those RUs defined in the RA field and not included in the first MRU, second MRU, and third MRU.

[0193] The maximum number of RUs not included in the first MRU, second MRU, and third MRU is 3, so we use a 3-bit bitmap.

[0194] In this example, the common fields of EHT-SIG include: one or more RA fields (each RA field is 8 bits) and one or more MRU allocation fields (9 bits, 7 bits, 5 bits, and 3 bits respectively).

[0195] In some alternative solutions, if a restriction mode for the MRU is defined, the embodiment can be modified accordingly, for example, by including only the bits of the RUs that are allowed to be aggregated into the MRU. For example, when only 26RU-3, 26RU-4, 26RU-5, 26RU-6, and 26RU-7 are allowed to be aggregated into the MRU, the first MRU allocation field and the second MRU allocation field can occupy 5 bits and 3 bits, respectively.

[0196] Example 6b In this embodiment, a method similar to that of Embodiment 6a is provided, where all bits of the bitmap for each portion defined in Embodiment 6a are used to indicate the allocated MRU, with no irrelevant bits. Each bit in the bitmap corresponds to a specific 26-RU, while RUs greater than 26 are indicated by consecutive bits in the bitmap. For example, to allocate the first 52-RU and the last 52-RU as the first MRU, we would define the bitmap '1 1 0 0 0 0 0 1 1', where the first two "1"s correspond to the first 52-RU and the last two "1"s correspond to the last 52-RU.

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

[0198] Example 6c In this embodiment, a method similar to that of Embodiments 6a and 6b is provided, wherein the number of MRUs is indicated in the EHT-SIG by the N_MRU field. If the N_MRU field is set to zero, it means that no MRUs are allocated, and the public fields of the EHT-SIG will not include bitmaps. If the N_MRU field is set to a number between 1 / 2 / 3 / 4, then 1 / 2 / 3 / 4 MRUs are allocated as defined in Embodiments 6a and 6b, and the corresponding number of bitmaps will be included.

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

[0200] Example 6d In this embodiment, an additional resource allocation table is defined, which includes all defined MRU combinations. This can be an MRA field—a multi-resource allocation field. Each entry definition in the MRA can include a mapping of a single MRU or a combination of MRUs. This mapping defines only the MRUs, while the complete allocation mapping for 20 MHz is defined by the RA field.

[0201] For example, if we want to assign the following 20 MHz mapping: [26, 26, 52 + the middle 26, 26, 26, 52]; Then the RA field '00000101' will indicate the mapping of [26, 26, 52, middle 26, 26, 26, 52]. Furthermore, new MRA entries can be defined, where the second 52-RU and the middle 26-RU are assigned as a single MRU.

[0202] The new MRA field will not indicate any individual RU, but only the MRU, so any RA field entry that assigns the second 52-RU and the middle 26-RU can be combined with the MRA field that assigns those RUs as MRUs.

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

[0204] The number of N bits defines the size of the MRA table with 2^N bit options for MRU mapping.

[0205] Figure 21 This is a block diagram of an access point according to another embodiment of the present invention. Figure 21 The access point 100 includes an interface 101, a processing unit 102, and a memory 103. The processing unit 102 controls the operation of the access point 100. The memory 103 may include read-only memory and random access memory, and provides instructions and data to the processing unit 102. A portion of the memory 103 may also include nonvolatile random access memory (NVRAM). All components of the access point 100 are coupled together using a bus system 109, which, in addition to a data bus, includes a power bus, a control bus, and a status signal bus. However, for clarity, in... Figure 21 In this context, various buses are labeled as Bus System 109.

[0206] The methods for sending the various frames disclosed in the above embodiments of the present invention can be applied to or implemented by the processing unit 102. During implementation, each step of the above methods can be performed using integrated logic circuits in the hardware of the processing unit 102 or instructions in software form. The processing unit 102 can be a general-purpose processor, a digital signal processor, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or another programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component, and can implement or execute the various methods, steps, and logic block diagrams disclosed in the embodiments of the present invention. The general-purpose processor can be a microprocessor, any conventional processor, etc. The steps of the methods disclosed with reference to the embodiments of the present invention can be directly executed by a hardware processor, or can be executed by using a combination of hardware and software modules in the processor. The software modules can reside in storage media that are well-established in the field, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, or registers. The storage medium is located in memory 103. The processing unit 102 reads information from memory 103 and performs the steps of the above methods with reference to the hardware of the processing unit 102.

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

[0208] The methods for sending the various frames disclosed in the above embodiments of the present invention can be applied to or implemented by the processing unit 112. In implementation, each step of the above methods can be performed using integrated logic circuits in the hardware of the processing unit 112 or instructions in software form. The processing unit 112 can be a general-purpose processor, a digital signal processor, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or another programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component, and can implement or execute the various methods, steps, and logic block diagrams disclosed in the embodiments of the present invention. The general-purpose processor can be a microprocessor, any conventional processor, etc. The steps of the methods disclosed with reference to the embodiments of the present invention can be directly executed by a hardware processor, or can be executed by using a combination of hardware and software modules in the processor. The software modules can reside in storage media mature in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, or registers. The storage medium is located in memory 113. The processing unit 112 reads information from memory 113 and performs the steps of the above methods with reference to the hardware of the processing unit 112.

[0209] Specifically, memory 113 stores received information that enables processing unit 112 to perform the method described in the above embodiments.

[0210] The specific embodiments described above in conjunction with the accompanying drawings are examples and do not represent the only achievable examples or those within the scope of the claims. When used in this specification, the terms "example" and "exemplary" mean "serving as an example, instance, or illustration," rather than "preferred" or "superior to other examples." Specific details are included to provide an understanding of the described techniques. However, these techniques can be practiced without these specific details. In some instances, well-known structures and apparatuses are shown in block diagram form to avoid obscuring the concepts of the described examples.

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

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

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

[0214] Computer-readable media include computer storage media and communication media, with communication media including any media used to transfer computer programs from one place to another. Storage media can be any available medium accessible by a general-purpose computer or a special-purpose computer. By way of example and not limitation, computer-readable media can include RAM, ROM, EEPROM, flash memory, CD-ROM or other optical disc storage, disk 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 accessible by a general-purpose computer or a special-purpose computer, or a general-purpose or special-purpose processor. Furthermore, any connection is appropriately referred to as computer-readable media. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technology (such as infrared, radio, and microwave, etc.), then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technology (such as infrared, radio, and microwave, etc.) is included in the definition of media. As used herein, disk and disc include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk, and Blu-ray disc, wherein disks typically reproduce data magnetically, while discs reproduce data using laser light. Combinations of these are also included within the scope of computer-readable media.

[0215] The above description of this disclosure is provided to enable those skilled in the art to make or use this disclosure. Various modifications to this disclosure will be apparent to those skilled in the art without departing from its scope, and the general principles defined herein can be applied to other variations. Therefore, this disclosure should not be limited to the examples and designs described herein, but should be given the broadest scope in accordance with the principles and novel features disclosed herein.

[0216] It should be understood that the terms "embodiment" or "one embodiment" mentioned throughout this specification do not imply that a particular feature, structure, or characteristic associated with that embodiment is included in at least one embodiment of the invention. Therefore, "in an embodiment" or "in one embodiment" appearing throughout this specification do not refer to the same embodiment. Furthermore, these particular features, structures, or characteristics can be combined in one or more embodiments using any suitable method. In the various embodiments of the invention, the sequence numbers of the processes described above do not imply an execution order. The execution order of the processes described above should be determined based on their function and internal logic and should not be construed as any limitation on the implementation process of the embodiments of the invention.

[0217] Those skilled in the art will recognize that, in conjunction with the examples described in the embodiments disclosed in this specification, the units and algorithm steps can be implemented by electronic hardware, computer software, or a combination thereof. To clearly illustrate the interchangeability between hardware and software, the composition and steps of each example have been described above in general terms of functionality. Whether these functions are implemented in hardware or software depends on the design constraints of the specific application and technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementations should not be considered beyond the scope of this invention.

[0218] Those skilled in the art will clearly understand that, for convenience and brevity, the detailed working process of the above-described systems, devices, and units can be referred to the corresponding processes in the above-described method embodiments, and will not be described in detail here.

[0219] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the described apparatus embodiments are merely examples. For example, the unit division is only a logical functional division, and may be other divisions in actual implementation. For example, multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Furthermore, the mutual coupling or direct coupling or communication connection shown or discussed can be implemented through some interface. Indirect coupling or communication connection between apparatuses or units can be implemented in an electronic, mechanical, or other form.

[0220] The units described as separate portions may or may not be physically separated, and the portions shown as units may or may not be physical units; they may be located in one location or distributed across multiple network units. Some or all units can be selected according to actual needs to achieve the purpose of the solution in the embodiments of the present invention.

[0221] Furthermore, the functional units in the embodiments of the present invention can be integrated into one processing unit, or each unit can exist physically independently, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

Claims

1. A device for wireless communication, characterized in that, include: Memory that stores instructions; as well as A processor coupled to the memory, wherein the processor is configured to execute instructions in the memory to cause the processor to: Generate a signaling field (SIG), the SIG including a resource unit (RU) allocation field and one or more user fields, the RU allocation field indicating the size and location of an RU or multiple resource unit (MRU) in a frequency resource, and each of the one or more user fields including a station identifier (STA ID) of a dispatch station (STA). The MRU includes multiple RUs and is assigned to the same STA or multiple STAs, and the RU assignment field indicates the size and location of each RU included in the MRU; The one or more user fields include a single RU user field and an MRU user field; the single RU user field corresponds to an RU that is not an MRU; the MRU user field corresponds to an MRU; Send the SIG.

2. A device for wireless communication, characterized in that, include: Memory that stores instructions; as well as A processor coupled to the memory, wherein the processor is configured to execute instructions in the memory to cause the processor to: The received signaling field (SIG) includes a resource unit (RU) allocation field and one or more user fields. The RU allocation field indicates the size and location of an RU or multiple resource unit (MRU) in a frequency resource. Each of the one or more user fields includes a station identifier (STA ID) of a dispatch station (STA). The MRU includes multiple RUs and is assigned to the same STA or multiple STAs, and the RU assignment field indicates the size and location of each RU included in the MRU; The one or more user fields include a single RU user field and an MRU user field; the single RU user field corresponds to an RU that is not an MRU; the MRU user field corresponds to an MRU; Process the SIG.

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

4. The apparatus according to claim 1 or 2, characterized in that, The common fields of the SIG include information on the number of small MRUs allocated in the corresponding 20MHz band; and / or information on the number of large MRUs allocated in the transmission bandwidth.

5. The apparatus according to claim 1 or 2, characterized in that, The SIG includes a common MRU field that indicates which 26-RUs are included in the MRUs in the corresponding 20 MHz band; and / or indicates which 242-RUs are included in the MRUs in the transmission bandwidth.

6. The apparatus according to claim 1 or 2, characterized in that, The SIG includes one or more public MRU fields, each public MRU field indicating which RUs are actually allocated in the MRU.

7. The apparatus according to claim 1 or 2, characterized in that, The SIG includes punch information indicating non-contiguous large RUs and one or more user fields corresponding to the non-contiguous large RUs, each of the one or more user fields including information about different stations.

8. A method for wireless communication, characterized in that, include: Generate a signaling field (SIG), the SIG including a resource unit (RU) allocation field and one or more user fields, the RU allocation field indicating the size and location of an RU or multiple resource unit (MRU) in a frequency resource, and each of the one or more user fields including a station identifier (STA ID) of a dispatch station (STA). The MRU includes multiple RUs and is assigned to the same STA or multiple STAs, and the RU assignment field indicates the size and location of each RU included in the MRU; The one or more user fields include a single RU user field and an MRU user field; the single RU user field corresponds to an RU that is not an MRU; the MRU user field corresponds to an MRU; Send the SIG.

9. A method for wireless communication, characterized in that, include: The received signaling field (SIG) includes a resource unit (RU) allocation field and one or more user fields. The RU allocation field indicates the size and location of an RU or multiple resource unit (MRU) in a frequency resource. Each of the one or more user fields includes a station identifier (STA ID) of a dispatch station (STA). The MRU includes multiple RUs and is assigned to the same STA or multiple STAs, and the RU assignment field indicates the size and location of each RU included in the MRU; The one or more user fields include a single RU user field and an MRU user field; the single RU user field corresponds to an RU that is not an MRU; the MRU user field corresponds to an MRU; Process the SIG.

10. The method according to claim 8 or 9, characterized in that, The MRU is a small MRU, which includes a combination of 26-RU, 52-RU, or 106-RU in the 20 MHz band; or, the MRU is a large MRU, which includes a combination of 242-RU, 484-RU, or 996-RU in the transmission bandwidth.

11. The method according to claim 8 or 9, characterized in that, The common fields of the SIG include information on the number of small MRUs allocated in the corresponding 20MHz band; and / or information on the number of large MRUs allocated in the transmission bandwidth.

12. The method according to claim 8 or 9, characterized in that, The SIG includes a common MRU field that indicates which 26-RUs are included in the MRUs in the corresponding 20 MHz band; and / or indicates which 242-RUs are included in the MRUs in the transmission bandwidth.

13. The method according to claim 8 or 9, characterized in that, The SIG includes one or more public MRU fields, each public MRU field indicating which RUs are actually allocated in the MRU.

14. The method according to claim 8 or 9, characterized in that, The SIG includes punch information indicating non-contiguous large RUs and one or more user fields corresponding to the non-contiguous large RUs, each of the one or more user fields including information about different stations.

15. A non-transitory computer-readable medium, characterized in that, The computer-readable storage medium is used to store instructions that, when executed by a processor, cause the processor to: Generate a signaling field (SIG), the SIG including a resource unit (RU) allocation field and one or more user fields, the RU allocation field indicating the size and location of an RU or multiple resource unit (MRU) in a frequency resource, and each of the one or more user fields including a station identifier (STA ID) of a dispatch station (STA). The MRU includes multiple RUs and is assigned to the same STA or multiple STAs, and the RU assignment field indicates the size and location of each RU included in the MRU; The one or more user fields include a single RU user field and an MRU user field; the single RU user field corresponds to an RU that is not an MRU; the MRU user field corresponds to an MRU; Send the SIG.

16. A non-transitory computer-readable medium, characterized in that, The computer-readable storage medium is used to store instructions that, when executed by a processor, cause the processor to: The received signaling field (SIG) includes a resource unit (RU) allocation field and one or more user fields. The RU allocation field indicates the size and location of an RU or multiple resource unit (MRU) in a frequency resource. Each of the one or more user fields includes a station identifier (STA ID) of a dispatch station (STA). The MRU includes multiple RUs and is assigned to the same STA or multiple STAs, and the RU assignment field indicates the size and location of each RU included in the MRU; The one or more user fields include a single RU user field and an MRU user field; the single RU user field corresponds to an RU that is not an MRU; the MRU user field corresponds to an MRU; Process the SIG.

17. The non-transitory computer-readable medium according to claim 15 or 16, characterized in that, The MRU is a small MRU, which includes a combination of 26-RU, 52-RU, or 106-RU in the 20 MHz band; or, the MRU is a large MRU, which includes a combination of 242-RU, 484-RU, or 996-RU in the transmission bandwidth.

18. The non-transitory computer-readable medium according to claim 15 or 16, characterized in that, The common fields of the SIG include information on the number of small MRUs allocated in the corresponding 20 MHz band; and / or information on the number of large MRUs allocated in the transmission bandwidth.

19. The non-transitory computer-readable medium according to claim 15 or 16, characterized in that, The SIG includes a common MRU field that indicates which 26-RUs are included in the MRUs in the corresponding 20 MHz band; and / or indicates which 242-RUs are included in the MRUs in the transmission bandwidth.

20. The non-transitory computer-readable medium according to claim 15 or 16, characterized in that, The SIG includes one or more public MRU fields, each public MRU field indicating which RUs are actually allocated in the MRU.

21. The non-transitory computer-readable medium according to claim 15 or 16, characterized in that, The SIG includes punch information indicating non-contiguous large RUs and one or more user fields corresponding to the non-contiguous large RUs, each of the one or more user fields including information about different stations.

Images