Apparatus and method for implementing multiple resource units for users in a wireless local area network

Abstract

An apparatus and method are provided for allocating multiple resource units (RUs) to users in a wireless local area network (WLAN) system. The transmitting device of the WLAN system includes: a transceiver that generates a Physical Layer Convergence Protocol (PLCP) Protocol Data Unit (PPDU) including a preamble and a payload, and transmits the generated PPDU to at least one receiving device; and a processor that controls the transceiver. The preamble includes multiple training fields and multiple signaling fields. Resource unit (RU) allocation information regarding the at least one receiving device is included in one of the multiple signaling fields. The RU allocation information includes a first subfield and a second subfield, the first subfield indicating the arrangement of RUs in the frequency domain corresponding to the PPDU, and the second subfield indicating a portion of the RUs to be combined to form multiple RUs.

Description

[0001] Cross-reference to related applications

[0002] This application relates to and claims priority to U.S. Provisional Patent Application No. 62 / 984,556, filed with the U.S. Patent and Trademark Office on March 3, 2020, and Korean Patent Application No. 10-2020-0069199, filed with the Korean Intellectual Property Office on June 8, 2020, the entire disclosure of which is incorporated herein by reference. Technical Field

[0003] This disclosure generally relates to wireless communication, and more specifically to wireless local area network (WLAN)-based communication for allocating resource units (RUs) to users. Background Technology

[0004] WLAN is a technology used to wirelessly connect two or more devices to each other in a local environment such as a building or campus. WLAN can operate in an infrastructure mode where an access point (AP) serves multiple user devices (such as smartphones and computers), and the AP can act as a gateway to a remote network (such as the Internet). WLAN can also be used alternatively as an ad hoc network between peer devices without an AP. In both cases, WLAN utilizes Orthogonal Frequency Division Multiplexing (OFDM) technology, where each user device communicates with the AP or another user device using a designated set of OFDM subcarriers (“subbands”) within the entire frequency band of the WLAN.

[0005] Currently, most WLAN technologies are based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard. The IEEE 802.11 standard has been developed into versions 802.11b, 802.11a, 802.11g, 802.11n, 802.11ac, and 802.11ax, and currently supports transmission speeds up to 1 Gbyte / s using OFDM technology. In version 802.11ac, data can be sent simultaneously to multiple users using a multi-user multiple-input multiple-output (MU-MIMO) scheme. However, WLAN systems using version 802.11ac only allow uplink signals to be sent from one user equipment to the access point (AP) at a time, which can lead to slower communication in congested areas.

[0006] Version 802.11ax (known as High Efficiency (HE)) addresses the issue of congested users by enabling simultaneous uplink communication from multiple user equipments (UEs) to the access point (AP) using Orthogonal Frequency Division Multiple Access (OFDMA). With OFDMA, each UE is assigned a Resource Unit (RU), which comprises a separate set of OFDM subcarriers. RUs are used for both downlink and uplink, allowing WLAN systems using 802.11ax (which also utilizes MU-MIMO) to efficiently support communication in localized areas with numerous users.

[0007] Furthermore, the proposed next-generation WLAN standard, 802.11be (Extreme High Throughput (EHT)), will support the 6 GHz unlicensed band, utilize up to 320 MHz of bandwidth per channel, introduce Hybrid Automatic Repeat Request (HARQ), and support up to 16×16 MIMO. Therefore, next-generation WLAN systems are expected to effectively support low latency and ultra-fast transmission with performance metrics similar to New Radio (NR) 5G technology. Summary of the Invention

[0008] Embodiments of the present invention provide an apparatus and method for effectively allocating multiple resource units (multi-RUs) to users in a wireless local area network (WLAN) system.

[0009] According to an aspect of the present invention, a transmitting device for a WLAN system is provided, the transmitting device comprising: a transceiver configured to generate a Physical Layer Convergence Protocol (PLCP) Protocol Data Unit (PPDU) including a preamble and a payload, and to transmit the generated PPDU to at least one receiving device; and a processor controlling the transceiver. The preamble includes a plurality of training fields and a plurality of signaling fields. RU allocation information for the at least one receiving device is included in one of the plurality of signaling fields. The RU allocation information includes a first subfield and a second subfield, the first subfield indicating the arrangement of RUs in the frequency domain corresponding to the PPDU, and the second subfield indicating a portion of the RUs to be combined to form a multi-RU network.

[0010] According to an aspect of the present invention, a receiving device for a WLAN system is provided, the receiving device comprising: a transceiver configured to receive a PPDU including a preamble and a payload, and to decode the payload based on the preamble; and a processor controlling the transceiver. The preamble includes a plurality of training fields and a plurality of signaling fields. RU allocation information for at least one receiving device is included in one of the plurality of signaling fields. The RU allocation information includes a first subfield and a second subfield, the first subfield indicating the arrangement of RUs in the frequency domain corresponding to the PPDU, and the second subfield indicating a portion of the RUs to be combined to form a multi-RU network.

[0011] According to an aspect of the present invention, a wireless communication method for a WLAN system is provided, wherein a transmitting device allocates RUs (Remote Roots) to at least one receiving device. The wireless communication method includes: generating a PPDU (Pre-Process Utility Unit) including a preamble and a payload; and transmitting the generated PPDU to at least one receiving device. The preamble includes a plurality of training fields and a plurality of signaling fields. RU allocation information for the at least one receiving device is included in one of the plurality of signaling fields. The RU allocation information includes a first subfield and a second subfield, the first subfield indicating the arrangement of RUs in the frequency domain corresponding to the PPDU, and the second subfield indicating a subset of RUs to be combined to form a multi-RU network.

[0012] According to an aspect of the present invention, a wireless communication method is provided for a receiving device in a WLAN system that receives RUs from a transmitting device. The wireless communication method includes: receiving a PPDU including a preamble and a payload; and decoding the payload based on the preamble. The preamble includes a plurality of training fields and a plurality of signaling fields. RU allocation information for at least one receiving device is included in one of the plurality of signaling fields. The RU allocation information includes a first subfield and a second subfield, the first subfield indicating the arrangement of RUs in the frequency domain corresponding to the PPDU, and the second subfield indicating RUs to be multiplexed.

[0013] According to various aspects of the present invention, a non-transitory computer-readable medium is provided, wherein each non-transitory computer-readable medium stores instructions that, when executed by a main processor in a transmitting or receiving device of a WLAN system, cause the transmitting or receiving device to perform the corresponding wireless communication method described above. Attached Figure Description

[0014] The embodiments of the inventive concept will be more clearly understood through the following detailed description taken in conjunction with the accompanying drawings, wherein similar reference numerals throughout the drawings refer to similar elements, wherein:

[0015] Figure 1 This is a view showing a wireless local area network (WLAN) system;

[0016] Figure 2 This is a block diagram illustrating a wireless communication device that transmits or receives Physical Layer Convergence Protocol (PLCP) Protocol Data Units (PPDUs);

[0017] Figure 3 This is a view showing the structure of a high-efficiency (HE) single-user (SU) PPDU;

[0018] Figure 4 This is a view showing the structure of the HE Extended Range (ER) SU PPDU;

[0019] Figure 5 This is a view showing the structure of HE based on the trigger-based (TB)PPDU;

[0020] Figure 6 This is a view showing the structure of a HE multi-user (MU) PPDU;

[0021] Figure 7 It shows Figure 6 A view of the structure of the HE-SIG-B field;

[0022] Figure 8 This is a view showing the HE MU PPDU arranged by frequency band;

[0023] Figure 9 It shows Figure 7 A view of the structure of the public fields;

[0024] Figure 10 It shows Figure 7 A view of examples of user-specific fields;

[0025] Figure 11 It shows Figure 7 Another example view of user-specific fields;

[0026] Figure 12 This is a view showing an example of the size and location of resource units (RUs) available in a 20MHz OFDMA PPDU;

[0027] Figure 13 This is a view showing an example of the size and location of the RUs available in a 40MHz OFDMA PPDU;

[0028] Figure 14 This is a view showing an example of the size and location of the RUs available in an 80MHz OFDMA PPDU;

[0029] Figure 15 This is a view showing the structure of the trigger frame;

[0030] Figure 16 This is a view showing the structure of an Extremely High Throughput (EHT) TB PPDU;

[0031] Figure 17 This is a view showing the structure of the EHT MU PPDU;

[0032] Figure 18 This is a view showing an example of allocating multiple RUs to a site (STA) in a 20MHz OFDMA PPDU formed by small RUs;

[0033] Figure 19 This is a view showing an example of allocating multiple RUs to a STA in an 80MHz OFDMA PPDU formed by large RUs;

[0034] Figure 20 This is a table showing the traditional RU layout index;

[0035] Figures 21 to 23 This is a table illustrating an RU arrangement index according to an embodiment of the present invention;

[0036] Figures 24A to 26D This is a view illustrating an example of forming RU allocation information according to an embodiment of the present invention;

[0037] Figure 27 This is a flowchart illustrating a wireless communication method in a WLAN system where a transmitting device allocates an RU to a receiving device; and

[0038] Figure 28 This is a flowchart illustrating a wireless communication method in a WLAN system where a receiving device receives a RU from a transmitting device. Detailed Implementation

[0039] In the following, embodiments of the inventive concept will be described in detail with reference to the accompanying drawings.

[0040] The terminology used in this specification is for describing embodiments and not for limiting the inventive concept. In this specification, unless otherwise specified, the singular forms include the plural forms. The described components, processes, operations, and / or elements do not exclude the presence or addition of one or more other components, processes, operations, and / or elements.

[0041] Unless otherwise defined, all terms used in this specification (including technical and scientific terms) may be used in the sense that would be normally understood by someone skilled in the art. Furthermore, unless specifically defined, terms defined in a general dictionary will not be interpreted ideologically or excessively.

[0042] Furthermore, in describing specific embodiments of the inventive concept, orthogonal frequency division multiplexing (OFDM) or OFDM-based wireless communication systems will be primarily described, particularly the IEEE 802.11 standard. However, the inventive concept can also be applied to other communication systems with similar technical backgrounds and channel types (e.g., cellular communication systems such as Long Term Evolution (LTE), LTE-A Advanced (LTE-A), New Radio (NR) / 5G, WiBro, or Global System for Mobile Communications (GSM) or long-range communication systems such as Bluetooth or Near Field Communication (NFC)).

[0043] In this document, the term "connection (combination)" and its derivatives refer to direct or indirect communication between two or more physically contacting or non-physically contacting components. The terms "transmit," "receive," and "communication" and their derivatives include all direct and indirect communication. The terms "comprising" and / or "including" as used in this document are intended to be non-limiting. "Or" means "and / or" collectively. "Related" and its derivatives mean including or being included. Connected to Hints, implied Connected to and Combination, can be with communication, and Cooperation, intervention, parallel placement, proximity Bind to have Features and Yes, they are related. A "controller" is a device, system, or part thereof that controls at least one operation. A controller can be implemented through hardware or a combination of hardware and software and / or firmware. Functions associated with a particular controller can be centralized or distributed, either locally or remotely.

[0044] Furthermore, the various functions described below can be implemented or supported by one or more computer programs, each of which is formed by computer-readable program code and executed on a computer-readable recording medium. "Application" and "program" refer to one or more computer programs, software components, instruction sets, procedures, functions, objects, classes, instances, associated data, or portions thereof suitable for implementing segments of computer-readable program code. "Computer-readable program code" includes all types of computer code, including source code, object code, and executable code. "Computer-readable medium" includes all types of media accessible by a computer, such as read-only memory (ROM), random access memory (RAM), hard disk drives, optical discs (CDs), digital video discs (DVDs), and other types of storage. "Non-transitory" computer-readable media does not include wired, wireless, optical, or other communication links that transmit temporary electrical or other signals. Non-transitory computer-readable media includes media where data can be permanently stored and media where data can be stored and subsequently overwritten, such as rewritable optical discs or removable storage devices.

[0045] Figure 1 This is a view showing a wireless local area network (WLAN) system 100. Figure 2 This is a block diagram illustrating a wireless communication device 1100 that transmits or receives Physical Layer Convergence Protocol (PLCP) Protocol Data Units (PPDUs).

[0046] like Figure 1 As shown, WLAN system 100 may include access points (APs) 101 and 103. APs 101 and 103 can communicate with at least one network 130 (such as the Internet, an Internet Protocol (IP) network, or another data network). APs 101 and 103 can provide wireless connectivity to network 130 for multiple stations (STAs) 111 to 114 in their coverage areas 120 and 125. APs 101 and 103 can communicate with each other and with STAs 111 to 114 using Wi-Fi or other WLAN communication technologies. Note that, depending on the network type, other well-known terms such as "router" and "gateway" may be used instead of "AP". In a WLAN, an AP provides (sets up) a wireless channel. A STA can act as an AP in an ad hoc (peer-to-peer) WLAN network configuration. Therefore, in the following description, functions attributable to an AP may alternatively be performed by a STA in a peer-to-peer network configuration.

[0047] Furthermore, depending on the network type, the term "STA" may be used in place of other well-known terms such as "mobile station," "user station," "remote terminal," "user equipment (UE)," "wireless terminal," "user device," or "user." In the following description, "STA" is used as an example to refer to a wireless device wirelessly connected to an AP or connected to a wireless channel in a WLAN. Additionally, in the following description, STA is considered to be a mobile device (e.g., a mobile phone or smartphone). However, STA can also be a fixed device (e.g., a desktop computer, AP, media player, fixed sensor, or television set).

[0048] The approximate extents of coverage areas 120 and 125 are marked with dashed lines. Here, for convenience, coverage areas 120 and 125 are shown as circular. However, each of the coverage areas 120 and 125 associated with APs 101 and 103 may have another shape reflecting various variations in the wireless environment related to natural or man-made obstacles, or another irregular shape depending on the setup of APs 101 and 103.

[0049] As described in detail later, APs 101 and 103 may include circuitry and / or procedures for managing uplink multi-user (ULMU) or downlink multi-user (DLMU) transmissions in the WLAN system 100.

[0050] although Figure 1 An example of a WLAN system 100 is shown, but different implementations are possible in other embodiments. Figure 1 Various modifications can be made. For example, the WLAN system 100 can include any number of appropriately arranged APs and any number of STAs. Furthermore, AP 101 can communicate directly with any number of STAs. AP 101 can provide wireless broadband access to multiple STAs 111 to 114 via network 130.

[0051] Similarly, each of APs 101 and 103 can communicate directly with network 130 and can provide wireless broadband access to multiple STAs 111 to 114 via network 130. Furthermore, APs 101 and 103 can be configured to connect to desired external networks, such as external telephone networks or data networks.

[0052] like Figure 2 The image shows a wireless communication device that transmits or receives PPDUs. For example, Figure 2 The wireless communication device 1100 (“Device 1100”) may have both transmitting and receiving capabilities, but may primarily be a transmitting device (e.g., AP) or a receiving device (e.g., STA) with a transceiver capable of performing data communication. For example, Figure 2 The wireless communication device 1100 can be Figure 1Any of AP 101 and 103 or STA 111 to 114 shown, and / or can be applied to sensors, computers, smartphones, portable electronic devices, tablets, wearable devices, or the Internet of Things (IoT).

[0053] In the following text, the case where the wireless communication device 1100 is a transmitting device is used as an example. Similar aspects can be applied to receiving devices.

[0054] The wireless communication device 1100 may include a main processor 1130, a memory 1120, a transceiver 1140, and antenna arrays 1101 to 1104. The main processor 1130, memory 1120, transceiver 1140, and antenna arrays 1101 to 1104 may be directly or indirectly connected to each other.

[0055] The main processor 1130 can control the memory 1120 and the transceiver 1140. The PPDU format and multiple resource unit (RU) allocation information can be stored in the memory 1120. Additionally, the transceiver 1140 can generate PPDUs using the PPDU format and RU allocation information stored in the memory 1120. Furthermore, the transceiver 1140 can transmit the generated PPDUs to an external receiving device (e.g., a STA) via antenna arrays 1101 to 1104.

[0056] Here, according to an embodiment of the present invention, memory 1120 may store PPDU format 1121 including a multi-RU allocation signaling format, which will be described later. Additionally, memory 1120 may store processor-executable instructions for executing the multi-RU allocation module 1122 and the PPDU generation module 1123. These processor-executable instructions may be executed by the main processor 1130.

[0057] For example, according to embodiments of the present invention, the multi-RU allocation module 1122 may use an RU allocation algorithm, method, or strategy to allocate multiple RUs to users (e.g., STAs). The PPDU generation module 1123 may generate signaling and indications related to the multi-RU allocation in the control fields of the PPDU (hereinafter referred to as signaling fields; e.g., HE-SIG-A, HE-SIG-B, or EHT-SIG).

[0058] Transceiver 1140 may include signal processor 1150. Signal processor 1150 may include various modules (i.e., various transmission path modules) or various types of communication transmission units for generating PPDUs.

[0059] Specifically, the signal processor 1150 may include: a transmit first-in-first-out (TX FIFO) 1111, an encoder 1112, a scrambler 1113, an interleaver 1114, a constellation mapper 1115 capable of generating, for example, QAM signals, a guard interval and window insertion module 1116 capable of providing, for example, guard intervals in frequency to reduce interference in the spectrum and converting signals by windowing, and an inverse discrete Fourier transform (IDFT) 1117.

[0060] Transceiver 1140 may include circuitry known to those skilled in the art to implement the functions discussed herein. The corresponding functions may be performed using hardware, firmware, software logic, or a combination of hardware, firmware, and software logic, by methods known to those skilled in the art.

[0061] During a receive operation, transceiver 1140 can receive a PPDU including a preamble and a payload from the transmitting device. Transceiver 1140 can decode the payload based on the preamble of the received PPDU. To do this, transceiver 1140 can decode the preamble of the PPDU using an internal decoder (not shown) to identify the RU assigned to device 1100, and can decode the payload (the payload received from the transmitting device) sent to device 1100 based on the identified RU.

[0062] It should be noted that payload decoding can alternatively be performed by another component of device 1100 (e.g., main processor 1130). According to an embodiment of the inventive concept described below, the payload is decoded based on the preamble of the PPDU received by transceiver 1140.

[0063] In the following text, reference will be made to Figures 3 to 15 Describes the high-efficiency (HE) PPDU used in the IEEE 802 standard (e.g., version 802.11ax). References Figures 3 to 15 The described HE PPDU can be made by Figure 2 The wireless communication device 1100 is generated.

[0064] Figure 3 This is a view showing the structure of a HE single-user (SU) PPDU. Figure 4 This is a view showing the structure of the HE Extended Range (ER) SUPPDU. Figure 5 This is a view showing the structure of HE based on the triggered (TB)PPDU. Figure 6 This is a view showing the structure of a HE multi-user (MU) PPDU. Figure 7 It shows Figure 6 A view of the structure of the HE-SIG-B field. Figure 8 This is a view showing the HE MU PPDU arranged by frequency band. Figure 9It shows Figure 7 A view of the structure of the public fields. Figure 10 It shows Figure 7 A view showing examples of user-specific fields. Figure 11 It shows Figure 7 Another example view of user-specific fields. Figure 12 This is a view showing an example of the size and location of the RUs available in a 20MHz Orthogonal Frequency Division Multiple Access (OFDMA) PPDU. Figure 13 This is a view showing an example of the size and location of the RUs available in a 40MHz OFDMA PPDU. Figure 14 This is a view showing an example of the size and location of the RUs available in an 80MHz OFDMA PPDU. Figure 15 This is a view showing the structure of the trigger frame.

[0065] like Figures 3 to 6 As shown, each HE PPDU may include a preamble and a payload. The preamble includes multiple training fields and multiple signaling fields, and the payload includes a data field and a packet extension (PE) field.

[0066] Specifically, each HE PPDU may include a legacy short training field (L-STF) of length 8µs, a legacy long training field (L-LTF) of length 8µs, a legacy signal (L-SIG) field of length 4µs, a repeated L-SIG (RL-SIG) field of length 4µs, a high-efficiency signal A (HE-SIG-A) field of length 8µs, and HE-STF, HE-LTF, DATA field and PE field of length 4µs.

[0067] Figure 3 The HE SU PPDU does not include the HE-SIG-B field. Figure 6 The HE MU PPDU can further include the HE-SIG-B field. Figure 4 The HE ER SU PPDU does not include the HE-SIG-B field. However, the symbol for the HE-SIG-A field can be repeated to have a length of 16µs. Additionally, Figure 5 The HE TB PPDU does not include the HE-SIG-B field. However, the HE-STF symbol can be repeated to have a length of 8µs.

[0068] Here, the fields included in the preamble will be simply described as follows.

[0069] L-STF can include short training orthogonal frequency division multiplexing (OFDM) symbols and can be used for frame detection, automatic gain control (AGC), diversity detection, and coarse frequency / time synchronization.

[0070] L-LTF can include long-trained OFDM symbols and can be used for fine-grained frequency / time synchronization and channel estimation.

[0071] The L-SIG field can be used to send control information and can include information about the data rate and data length. For example, the L-SIG field can be sent repeatedly. The format of repeating the L-SIG field is called the RL-SIG field.

[0072] The HE-SIG-A field may include common control information for the receiving device, as shown below.

[0073] 1) Downlink (DL) / Uplink (UL) Indicators

[0074] 2) Basic Service Set (BSS) color field as the identifier of BSS

[0075] 3) A field indicating the remaining time of the current Transmission Opportunity (TXOP) period.

[0076] 4) Indicates the bandwidth field for 20 / 40 / 80 / 160 / 80+80MHz

[0077] 5) Indicates the field of modulation and coding scheme (MCS) applied to the HE-SIG-B field.

[0078] 6) A field indicating whether the HE-SIG-B field is modulated using a dual-carrier modulation scheme.

[0079] 7) Field indicating the number of signs used in the HE-SIG-B field

[0080] 8) A field indicating whether to generate HE-SIG-B fields across the entire frequency band.

[0081] 9) Field indicating the number of signs in HE-LTF

[0082] 10) Fields indicating the length of the HE-LTF and the length of the cyclic prefix (CP) field.

[0083] 11) A field indicating whether additional OFDM symbols are provided for low-density parity-check (LDPC) coding.

[0084] 12) Fields that indicate control information regarding the PE field.

[0085] 13) A field indicating information about the Cyclic Redundancy Check (CRC) field of the HE-SIG-A field.

[0086] The HE-SIG-A field may further include various information items in addition to those mentioned in 1) to 13) above, or some information items mentioned in 1) to 13) above may be omitted. In environments other than the MU environment, other information items may be added to the HE-SIG-A field, or some information items in the HE-SIG-A field may be omitted.

[0087] The HE-SIG-B field can be used in the MU's PPDU. The HE-SIG-B field can be omitted from the SU's PPDU. Either the HE-SIG-A or HE-SIG-B field can include RU allocation information about at least one receiving device. References will follow below. Figures 7 to 11 Provide a detailed description of the HE-SIG-B field.

[0088] like Figure 7 As shown, the HE-SIG-B field can include public fields and user-specific fields. The public fields include public control information, and the user-specific fields include user-specific control information.

[0089] Here, public fields can be encoded separately from user-specific fields. Additionally, public fields may include RU allocation information and a corresponding "CRC subfield," which can be encoded using a single binary convolutional coding (BCC) block. User-specific fields may include information for decoding the payloads of two users (e.g., two STAs) and a corresponding "CRC subfield," which can also be encoded using a single BCC block.

[0090] For example, the HE-SIG-B field can be obtained by copying the HE-SIG-B field from another frequency band.

[0091] For example, refer to Figure 8 The HE-SIG-B field transmitted via a portion of the frequency band (e.g., the fourth band 784) may include control information for data fields used in another frequency band (e.g., the second band 782) and data fields used in the corresponding frequency band (i.e., the fourth band 784). Therefore, the HE-SIG-B field for a specific frequency band (e.g., the second band 782) may be in a format (i.e., a form) obtained by copying the HE-SIG-B field from another frequency band (e.g., the fourth band 784). Thus, the HE-SIG-B field can be transmitted in an encoded form throughout the RU.

[0092] On the other hand, such as Figure 9 As shown, the common fields of the HE-SIG-B field can include various subfields, such as the RU allocation subfield, the center 26-tone RU subfield, the CRC subfield, and the tail subfield.

[0093] Specifically, the RU allocation subfield can have N×8 bits (N is one of 1, 2, and 4). The RU allocation subfield can indicate the RU allocation in the frequency domain and the number of user fields (e.g., the number of STAs) in each RU. Additionally, RUs with a size not less than 106 subcarriers (106-tone) supporting MU-MIMO can indicate the number of multiplexed users by using MU-MIMO.

[0094] For 20MHz and 40MHz HE MU PPDUs, the variable N can be 1; for 80MHz HE MU PPDUs, N can be 2; for 160MHz or 80+80MHz HE MU PPDUs, N can be 4.

[0095] On the other hand, the center 26-toneRU subfield can have 1 bit and can be provided to indicate whether the entire bandwidth is 80MHz, 160MHz, or 80+80MHz. The CRC subfield can have 4 bits and can be used to detect errors in the common field data. In addition, the tail subfield can have 6 bits, which can be used to terminate the grid of the convolutional decoder and can be set to 0.

[0096] like Figure 10 and Figure 11 As shown, the user-specific fields of the HE-SIG-B field can include various subfields, such as the STA-ID subfield, the MCS subfield, and the encoding subfield.

[0097] The configuration of subfields of the user-specific field in the HE-SIG-B field can be changed depending on whether the user-specific field is a MU-MIMO allocation field.

[0098] For example, in Figure 10 In the HE-SIG-B field, when the user-specific fields are not MU-MIMO allocation fields (i.e., non-MU-MIMO), the user-specific fields of the HE-SIG-B field may include the STA-ID subfield (bits B0 to B10 = 11 bits), the NSTS subfield (bits B11 to B13 = 3 bits), the TX beamforming subfield (bit B14 = 1 bit), the MCS subfield (bits B15 to B18 = 4 bits), the dual-carrier modulation (DCM) subfield (bit B19 = 1 bit), and the coding subfield (bit B20 = 1 bit).

[0099] The value of the STA-ID subfield can be set to the value of the TXVECTOR parameter STA_ID. The NSTS subfield can be divided into two cases: when the STA-ID subfield is 2046 and when the STA-ID subfield is not 2046, and it can indicate the number of spatiotemporal streams. Therefore, when the STA-ID subfield is not 2046, the NSTS subfield can be set to 1 less than the number of spatiotemporal streams. On the other hand, when the STA-ID subfield is 2046, the NSTS subfield can be set to any value.

[0100] The TX beamforming subfield can be divided into two cases: one where the STA-ID subfield is 2046 and the other where the STA-ID subfield is not 2046, and can be used for transmit beamforming. Therefore, when the STA-ID subfield is not 2046, the TX beamforming subfield can be set to 1 (i.e., the case where the beamforming control matrix is ​​applied to the waveform transmitted by the SU) or 0 (other cases). On the other hand, when the STA-ID subfield is 2046, the TX beamforming subfield can be set to any value.

[0101] The MCS subfield can be divided into cases where the STA-ID subfield is 2046 and cases where the STA-ID subfield is not 2046, and can indicate the modulation and coding scheme. Therefore, when the STA-ID subfield is not 2046, the MCS subfield can be set to n (n = 0, 1, 2, ..., 11, or n = 12 to 15 are reserved). On the other hand, when the STA-ID subfield is 2046, the MCS subfield can be set to any value.

[0102] The DCM subfield can be divided into two cases: one where the STA-ID subfield is 2046 and another where the STA-ID subfield is not 2046, and it can indicate whether DCM is used. Therefore, when the STA-ID subfield is not 2046, the DCM subfield can be set to 1 (indicating that the corresponding payload of the HE MU PPDU user is modulated using DCM) or 0 (indicating that the corresponding payload of the HE MU PPDU user is not modulated using DCM). On the other hand, when the STA-ID subfield is 2046, the DCM subfield can be set to any value.

[0103] The encoding subfield can be divided into two cases: one where the STA-ID subfield is 2046 and the other where it is not 2046. It can also indicate whether BCC or LDPC is used. Therefore, when the STA-ID subfield is not 2046, the encoding subfield can be set to 0 (indicating BCC) or 1 (indicating LDPC). On the other hand, when the STA-ID subfield is 2046, the encoding subfield can be set to any value.

[0104] On the other hand, Figure 11 In the HE-SIG-B field, when the user-specific field is a MU-MIMO allocation field (i.e., MU-MIMO), the user-specific field of the HE-SIG-B field may include the STA-ID subfield (composed of bits B0 to B10–11), the space configuration subfield (composed of bits B11 to B14–4), the MCS subfield (composed of bits B15 to B18–4), the reservation subfield (composed of bits B19–1), and the encoding subfield (composed of bits B20–1).

[0105] The value of the STA-ID subfield can be set to the value indicated by the TXVECTOR parameter STA_ID. The space configuration subfield can be used to indicate the number of space streams for a user (e.g., STA) when allocating MU-MIMO.

[0106] The MCS subfield can indicate the modulation and coding scheme. Therefore, the MCS subfield can be set to n (n = 0, 1, 2, ..., 11, or n = 12 to 15 are reserved).

[0107] The reserved subfield can be reserved and set to 0. The encoded subfield can indicate whether BCC or LDPC is used. Therefore, the encoded subfield can be set to 0 (indicating the use of BCC) or 1 (indicating the use of LDPC).

[0108] exist Figure 11 In this context, the encoding subfield can be divided into two cases: when the STA-ID subfield is 2046 and when the STA-ID subfield is not 2046. The above description refers to the case where the STA-ID subfield is not 2046. That is, when the STA-ID subfield is 2046, the space configuration subfield, MCS subfield, reserved subfield, and encoding subfield can be set to any value.

[0109] Since the HE-SIG-B field can be formed as described above, its redundant description is omitted.

[0110] Refer again Figures 3 to 6 HE-STF can be used to improve automatic gain control estimation in multiple-input multiple-output (MIMO) or OFDMA environments.

[0111] HE-LTF can be used to estimate channels in MIMO or OFDMA environments.

[0112] The size of the Fast Fourier Transform (FFT) / Inverse Fast Fourier Transform (IFFT) applied to the HE-STF and the fields following the HE-STF can differ from the size of the FFT / IFFT applied to the fields preceding the HE-STF. For example, the size of the FFT / IFFT applied to the HE-STF and the fields following the HE-STF can be larger than the size of the FFT / IFFT applied to the fields preceding the HE-STF.

[0113] Therefore, the frequency band used by the field preceding HE-STF may not exactly coincide with the frequency band used by the fields following HE-STF. As an example, in Figures 3 to 6 The diagram shows that the frequency band used by the field before HE-STF is exactly the same as that used by the field after HE-STF.

[0114] The following discussion will briefly describe the fields included in the payload.

[0115] The data field may include data for at least one user. That is, the data field may carry Physical Layer Service Data Units (PSDUs) for at least one user.

[0116] Additionally, based on the RU allocation information included in the signaling field of the preamble, at least one RU comprising a different number of tones (i.e., subcarriers) can be arranged in the frequency domain of the data field.

[0117] That is, such as Figures 12 to 14 As shown, at least one RU can be arranged in the frequency domain of the data field. Figures 12 to 14 The horizontal axis of each element represents the frequency domain.

[0118] First of all, Figure 12 The diagram shows the arrangement of RUs available in a 20MHz OFDMA PPDU.

[0119] Specifically, in the leftmost band of the 20MHz frequency band, 6 tones (i.e., subcarriers) can be used as guard bands, and in the rightmost band of the 20MHz frequency band, 5 tones can be used as guard bands. Seven DC tones can be inserted into the center band (i.e., the DC band), and 26 subcarrier RUs corresponding to 13 tones can be provided on each side of the left and right sides of the DC band. Additionally, 26-subcarrier RUs, 52-subcarrier RUs, and 106-subcarrier RUs can be allocated to other frequency bands. Each RU can be allocated to a receiving device, i.e., a user.

[0120] For example, Figure 12 The RU arrangement can be used for both SU and MU cases. Therefore, as Figure 12As shown in the top part, multiple 26-subcarrier RUs can be arranged, and as... Figure 12 As shown in the bottom part, a 242 subcarrier RU can be arranged (in this case, 3 DC tones can be inserted into the center band).

[0121] exist Figure 12 Examples of various RU sizes have been proposed, namely, 26-subcarrier RU, 52-subcarrier RU, 106-subcarrier RU, and 242-subcarrier RU. Because the specific size of the RU can be increased, embodiments of the present invention are not limited to a specific size of the RU (i.e., the number of corresponding tones).

[0122] Continuing, in Figure 13 The diagram shows the arrangement of RUs available in a 40MHz OFDMA PPDU.

[0123] Specifically, in the leftmost band of the 40MHz band, 12 tones (i.e., subcarriers) can be used as guard bands, and in the rightmost band of the 40MHz band, 11 tones can be used as guard bands. Additionally, 5 DC tones can be inserted into the center band (i.e., the DC band). Furthermore, 26-subcarrier RUs, 52-subcarrier RUs, 106-subcarrier RUs, and 242-subcarrier RUs can be allocated to other bands. Each RU can be assigned to a receiving device, i.e., a user.

[0124] Figure 13 The RU arrangement can be used for both SU and MU cases. Therefore, as in Figure 13 As shown in the bottom part, a 484 subcarrier RU can be arranged (in this case, 5 DC tones can be inserted into the center band).

[0125] exist Figure 13 Examples of various RU sizes have been proposed, namely, 26-subcarrier RU, 52-subcarrier RU, 106-subcarrier RU, 242-subcarrier RU, and 484-subcarrier RU. Because the specific size of the RU can be increased, embodiments of the present invention are not limited to a specific size of the RU (i.e., the number of corresponding tones).

[0126] Finally, Figure 14 The diagram shows the arrangement of RUs available in an 80MHz OFDMA PPDU.

[0127] Specifically, in the leftmost band of the 80MHz frequency band, 12 tones (i.e., subcarriers) can be used as guard bands, and in the rightmost band of the 80MHz frequency band, 11 tones can be used as guard bands. Additionally, 7 DC tones can be inserted into the center band (i.e., the DC band). Furthermore, 26 subcarrier RUs, 52 subcarrier RUs, 106 subcarrier RUs, 242 subcarrier RUs, and 484 subcarrier RUs can be allocated to other frequency bands. Each RU can be assigned to a receiving device, i.e., a user.

[0128] Figure 14 The RU arrangement can be used for both SU and MU cases. Therefore, as in Figure 14 As shown in the bottom part, a 996 subcarrier RU can be arranged (in this case, 5 DC tones can be inserted into the center band).

[0129] exist Figure 14 Examples of various RU sizes are presented, namely, a 26-subcarrier RU (hereinafter referred to as RU26), a 52-subcarrier RU (hereinafter referred to as RU52), a 106-subcarrier RU (hereinafter referred to as RU106), a 242-subcarrier RU (hereinafter referred to as RU242), a 484-subcarrier RU (hereinafter referred to as RU484), and a 996-subcarrier RU (hereinafter referred to as RU996). Because the specific size of the RU can be increased, embodiments of the inventive concept are not limited to a specific size of the RU (i.e., the number of corresponding tones).

[0130] For example, the RU locations available in a 40MHz OFDMA PPDU are the same as two copies of the RU locations available in a 20MHz OFDMA PPDU. Furthermore, the RU locations available in an 80MHz OFDMA PPDU are the same as two copies of the RU locations available in a 40MHz OFDMA PPDU. An OFDMA PPDU can include combinations of different RU sizes within each RU242 boundary.

[0131] As mentioned above, at least one RU can be arranged differently in the frequency domain of the data field.

[0132] Refer again Figures 3 to 6 The PE field can have a duration of 4us, 8us, 12us or 16us, and additional receive processing time can be provided at the end of the HE PPDU.

[0133] Because the preamble and payload fields of the HE PPDU are formed as described above, one of the above-described HE PPDUs can be applied in the embodiments of the present invention.

[0134] For reference, when UL transmission operations are performed by one or more STAs (e.g., non-AP STAs) in the frequency domain, the AP can allocate different frequency resources as UL transmission resources to one or more STAs based on OFDMA. Here, frequency resources may refer to RUs and can be indicated by a trigger frame sent by the AP to the STA before the UL transmission operation.

[0135] Therefore, in order to send Figure 5 The HE TB PPDU requires a trigger frame. The trigger frame is in Figure 15 As shown in the image.

[0136] Specifically, the trigger frame can allocate a RU for UL multi-user transmission and can be sent from the AP to the STA. Additionally, the trigger frame can be formed from a MAC frame and can be included in a PPDU.

[0137] Trigger frames can be obtained through Figures 3 to 6 The PPDU shown is used for transmission, or a PPDU specifically designed for the corresponding trigger frame. For reference, when the trigger frame is transmitted via... Figures 3 to 6 When the PPDU shown is sent, the trigger frame can be included in the data field.

[0138] Specifically, such as Figure 15 As shown, the trigger frame may include a frame control field 400 (2 octets), a duration field 405 (2 octets), an RA field 410 (6 octets), a TA field 415 (6 octets), a common information field 420 (not less than 8 octets), separate user information fields 425-1 to 425-N (N is a natural number not less than 1, and each is not less than 5 octets), a padding field 430, and a frame check sequence (FCS) field 435 (not less than 4 octets).

[0139] First, the frame control field 400 may include information about the MAC protocol version and other additional control information items, and the duration field 405 may include time information for setting the network allocation vector (NAV) or information about the terminal's identifier (e.g., association ID (AID)). Additionally, the RA field 410 may include the address information of the receiving device (e.g., STA) that triggered the frame, and may be omitted if needed. The TA field 415 may include the address information of the sending device (e.g., AP) that triggered the frame, and the common information field 420 may include common control information applied to the receiving device (e.g., STA) that received the triggered frame.

[0140] For reference, the public information field 420 may include a field indicating the length of the L-SIG field of the UL PPDU transmitted in response to the corresponding trigger frame, or information controlling the content of the SIG-A field (i.e., the HE-SIG-A field) of the UL PPDU transmitted in response to the corresponding trigger frame. Additionally, the public information field 420 may include, as public control information, information about the length of the CP of the UL PPDU transmitted in response to the corresponding trigger frame, or information about the length of the LTF field.

[0141] The trigger frame may include individual user information fields 425-1 to 425-N (where N is a natural number not less than 1) corresponding to the number of receiving devices (e.g., STAs) receiving the trigger frame. For reference, each user information field may be referred to as a "RU allocation field". The trigger frame may include a padding field 430 and an FCS field 435.

[0142] Some fields in the trigger frame can be omitted and others can be added. Additionally, the length of each field can be changed to be different from what is illustrated.

[0143] As described above, since various HE PPDUs are used in the IEEE standard (version 802.11ax), embodiments of the inventive concept can be implemented in the signaling fields (e.g., HE-SIG-A and HE-SIG-B fields) of these various HE PPDUs.

[0144] That is, embodiments of the inventive concept relate to methods and apparatus for supporting MUs using OFDMA, and more specifically, to methods and apparatus for a transmitting device (e.g., AP) to allocate multiple RUs to at least one of a plurality of receiving devices (e.g., STAs) via OFDMA. Therefore, embodiments of the inventive concept provide a method and apparatus for forming a signaling field indicating information about the multiple RUs allocated to a receiving device (e.g., STA). However, embodiments of the inventive concept can be applied to cases where STAs transmit data to each other and to APs. Furthermore, embodiments of the inventive concept can be applied to environments supporting single users such as SU PPDUs, as well as DL OFDMA methods and ULOFDMA.

[0145] Furthermore, embodiments of the present invention can also be applied to version 802.11be, which is a next-generation WLAN standard. The method and apparatus for allocating multiple RUs according to embodiments of the present invention can be implemented in the signaling fields of the EHT PPDU (e.g., the Extremely High Throughput (EHT)-SIG field). Hereinafter, references... Figure 16 and Figure 17This will describe the EHT PPDU used in the IEEE standard (version 802.11be). For example, refer to... Figure 16 and Figure 17 The described EHT PPDU can be accessed via Figure 2 The wireless communication device 1100 is generated.

[0146] Figure 16 This is a view showing the structure of the EHT TB PPDU. Figure 17 This is a view showing the structure of the EHT MU PPDU.

[0147] like Figure 16 and Figure 17 As shown, each EHT PPDU may include a preamble and a payload. The preamble includes multiple training fields and multiple signaling fields, and the payload includes data fields.

[0148] Specifically, each EHT PPDU may include an 8µs L-STF, an 8µs L-LTF, a 4µs L-SIG field, a 4µs repeated L-SIG (RL-SIG) field, an 8µs general signal (U-SIG) field, an EHT-STF, an EHT-LTF, and a DATA field.

[0149] Figure 16 The EHT TB PPDU does not include the EHT-SIG field. However, the symbol for the EHT-STF can be repeated. Figure 17 The EHT MU PPDU can include multiple OFDM symbols and may further include an EHT-SIG field. Additionally, similar to the above... Figure 5 HE TB PPDU requires a trigger frame to send. Figure 16 The EHT TB PPDU. The trigger frame used to send the EHT TB PPDU can have the same characteristics as... Figure 15 It has a similar structure and function to the aforementioned trigger frame.

[0150] For example, each EHT PPDU may further include a PE field. However, according to embodiments conceived in the present invention, for ease of understanding, it is shown that each EHT PPDU does not include a PE field.

[0151] The fields included in each EHT PPDU will be briefly described as follows.

[0152] The fields “L-STF”, “L-LTF”, “L-SIG” and “RL-SIG” of each EHT PPDU are the same as or similar to the fields of the HE PPDU mentioned above; therefore, for the sake of brevity, a detailed description will be omitted.

[0153] The U-SIG field, which performs a function similar to the HE-SIG-A field of the HE PPDU, can be arranged adjacent to the RL-SIG field and can include two OFDM symbols that are commonly encoded.

[0154] For example, a U-SIG field can include "version-independent fields" and "version-dependent fields", and "version-dependent fields" can be arranged adjacent to "version-independent fields".

[0155] Here, "version-independent fields" can have static positions and bit definitions on different generation / physical versions.

[0156] Additionally, "version-independent fields" can include control information such as the following.

[0157] 1) PHY version identifier (consisting of three bits)

[0158] 2) Uplink (UL) / Downlink (DL) flags (consisting of one bit)

[0159] 3) BSS color field as the identifier of BSS

[0160] 4) TXOP duration (i.e., a field indicating the remaining time of the current TXOP period)

[0161] 5) Bandwidth field (can carry some puncturing information)

[0162] On the other hand, "version-related fields" can have variable bit definitions in each PHY version.

[0163] Additionally, "version-related fields" can include control information such as the following.

[0164] 1) PPDU type (field indicating PPDU type)

[0165] 2) EHT-SIG Modulation and Coding Scheme (MCS) (The field indicating the MCS is provided in the U-SIG field of the EHT PPDU, which is sent to the MU)

[0166] 3) Number of EHT-SIG symbols (a field indicating the number of symbols used in the EHT-SIG field and provided in the U-SIG field of the EHT PPDU, which is sent to the MU)

[0167] The U-SIG field may further include various information items in addition to the control information mentioned above, or it may exclude some of the information in the control information items mentioned above. In environments other than the MU environment, some information may be added to the U-SIG field, or some information in the U-SIG field may be omitted.

[0168] The EHT-SIG field, which performs a similar function to the HE-SIG-B field of the HE PPDU, can be arranged adjacent to the U-SIG field in the EHT PPDU, is sent to the MU, and can have a variable MCS and a variable length.

[0169] Specifically, the EHT-SIG field may include public fields and user-specific fields, the public fields including public control information and the user-specific fields including user-specific control information.

[0170] Here, public fields can be encoded separately from user-specific fields. Additionally, public fields may include RU allocation-related information described later (i.e., information including "RU allocation subfields" and "additional RU allocation subfields" described later), and user-specific fields may include information similar to that included in the user-specific fields of the HE-SIG-B field described above (i.e., user information about which each RU is assigned).

[0171] For example, in the common fields of the EHT-SIG field of the EHT PPDU sent to MU, at least one compression mode in which the "RU allocation subfield" is not provided can be provided. Additionally, the EHT-SIG field can be used primarily for MU's PPDU. However, unlike "HE PPDU", the EHT-SIG field can be used for SU's PPDU when the overhead of the U-SIG field increases.

[0172] Because the EHT-SIG field can be formed as described above, its detailed description will not be given.

[0173] As described above, since various EHT PPDUs can be used in the IEEE standard (i.e., 802.11be), and the preamble and payload fields of the EHT PPDU can be formed as described above, embodiments of the present invention can be implemented in the signaling fields (e.g., U-SIG field and EHT-SIG field) of the various EHT PPDUs mentioned above.

[0174] That is, since the method for allocating multiple RUs according to embodiments of the present invention (i.e., the method for forming signaling fields for multiple RU allocation) can be applied to both the signaling fields of HE PPDU and EHT PPDU, reference will be made below to... Figures 18 to 26. A method for allocating multiple RUs according to an embodiment of the present invention is described.

[0175] Figure 18 This is a view showing an example of allocating multiple RUs to a STA in a 20MHz OFDMA PPDU formed by small RUs. Figure 19 This is a view showing an example of allocating multiple RUs to a STA in an 80MHz OFDMA PPDU formed by large RUs. Figure 20 This is a table showing the traditional RU layout index. Figures 21 to 23 This is a table illustrating an RU arrangement index according to an embodiment of the present invention. Figures 24A to 26D This is a view illustrating an example of forming RU allocation information according to an embodiment of the present invention.

[0176] For example, the premise is that the method for forming the signaling field of the PPDU, which will be described later, can be applied to both HE PPDU and EHT PPDU.

[0177] The premise is that the RU can include: a single RU from 26 subcarrier RU, 52 subcarrier RU, 106 subcarrier RU, 242 subcarrier RU, 484 subcarrier RU and 996 subcarriers, or a multi-RU from 26+52 subcarrier RU (multi-RU of RU26+RU52), 52+26 subcarrier RU (multi-RU of RU52+RU26), 26+106 subcarrier RU (multi-RU of RU26+RU106), 106+26 subcarrier RU (multi-RU of RU106+RU26), 484+242 subcarrier RU (multi-RU of RU484+RU242) and 484+996 subcarrier RU (multi-RU of RU484+RU996).

[0178] First, refer to Figure 18 and Figure 19 Examples of allocating multiple RUs to a STA in a 20MHz OFDMA PPDU formed by small RUs and examples of allocating multiple RUs to a STA in an 80MHz OFDMA PPDU formed by large RUs are shown.

[0179] For example, to improve the efficiency of multi-RU allocation, RUs can be divided into small RUs and large RUs based on their size.

[0180] Here, the small RU can be one of 26 subcarrier RU, 52 subcarrier RU, and 106 subcarrier RU, while the large RU can be one of 242 subcarrier RU, 484 subcarrier RU, and 996 subcarrier RU.

[0181] On the other hand, in conventional technology, when seven RUs are arranged in a 20MHz OFDMA PPDU, one RU is assigned to each of the seven STAs so that each STA can receive data from the AP.

[0182] However, in embodiments of the present invention, multiple RUs (i.e., multiple RUs) are allocated to a specific STA using a multi-RU allocation method so that the STA can receive data from the AP.

[0183] Therefore, as Figure 18 As shown (in the case of a small RU), multiple RUs, such as RU26+RU52 (26 subcarrier RUs + 52 subcarrier RUs), are assigned to STA-2 so that STA-2 can receive data from the AP. Additionally, multiple RUs, such as RU52+RU26 (52 subcarrier RUs + 26 subcarrier RUs), are assigned to STA-4 so that STA-4 can receive data from the AP. One RU is assigned to the remaining STAs (i.e., STA-1, STA-3, and STA-5) so that STA-1, STA-3, and STA-5 can receive data from the AP.

[0184] In addition, such as Figure 19 As shown (in the case of a large RU), RU242+RU484 (i.e., 242 subcarrier RUs + 484 subcarrier RUs) are allocated to STA-2 so that STA-2 can receive data from the AP. As in conventional technology, one RU is allocated to the remaining STA (i.e., STA-1) so that STA-1 can receive data from the AP.

[0185] As described above, when a STA receives data through multiple RUs, the STA needs to know which multiple RU has been assigned to it via a signaling field. Therefore, according to an embodiment of the present invention, a method for forming a signaling field that indicates information about the multiple RUs assigned to the STA is proposed. (See also...) Figures 20 to 2 6. Describe the method in detail.

[0186] First, refer to Figure 20 Table T1, which describes the traditional RU layout index, is shown, and references are also provided. Figures 21 to 23 Table T2 is shown, describing an RU layout index according to an embodiment of the present invention. Therefore, a method for forming signaling fields according to an embodiment of the present invention is described with reference to T1 and T2.

[0187] For example, each of T1 and T2 visually shows the RU allocation information (e.g., one of the HE-SIG-A, HE-SIG-B, U-SIG, and EHT-SIG fields) included in the signaling fields of the PPDU.

[0188] According to an embodiment of the present invention, in order to transmit multi-RU allocation information via PPDU, a new N-bit "additional RU allocation subfield (hereinafter, used interchangeably with the second subfield)" is defined in the signaling field of the PPDU. According to an embodiment of the present invention, by combining the existing 8-bit "RU allocation subfield (hereinafter, used interchangeably with the first subfield)" and the N-bit "additional RU allocation subfield" (second subfield), a method for forming a signaling field capable of indicating multi-RU allocation information for each STA is proposed.

[0189] For ease of understanding, in an embodiment of the present invention, the case where “N bits” is “two bits” is taken as an example.

[0190] For example, when an embodiment of the present invention is applied to 802.11be, the RU allocation signaling in the common field of the EHT-SIG field can cover various supported RU combinations. An embodiment of the present invention implements a scheme to add a two-bit additional RU allocation subfield to the RU allocation subfield in the common field of the EHT-SIG field.

[0191] In this scenario, when each STA is assigned only one RU, the mapping scheme for RU allocation using the 8-bit RU allocation subfield in 802.11ax can be reused. This is because, although the multi-RU allocation signaling proposed in the embodiments of this invention is related to 802.11be, it can share the same logic as 802.11ax, thereby reducing the logic of non-APSTAs.

[0192] On the other hand, for convenience, methods for forming signaling fields using small multiple RUs and methods for forming signaling fields using large multiple RUs are described. Furthermore, it is assumed that small multiple RUs are formed by combinations of multiple consecutive RUs, and large multiple RUs are formed by combinations of multiple consecutive or discontinuous RUs.

[0193] First, refer to Figure 24A and Figure 24B Describes a method for forming signaling fields using small multiple RUs.

[0194] RU26+RU52 (RU26 is arranged in a lower frequency band than RU52), RU52+RU26 (RU52 is arranged in a lower frequency band than RU26), RU26+RU106 (RU26 is arranged in a lower frequency band than RU106), or RU106+RU26 (RU106 is arranged in a lower frequency band than RU26) can be used as small multi-RUs.

[0195] For example, according to an embodiment of the present invention, a subcarrier RU (e.g., a 52-subcarrier RU) arranged at at least one end of the frequency domain (e.g., arranged in column #1 or #9) may not be "multi-combined" with another RU. (In this document, when a first RU and a second RU are combined to form multiple RUs, the first RU and the second RU may be referred to as being "multi-combined" or simply "combined"). Alternatively, a subcarrier RU (e.g., a 52-subcarrier RU) arranged at at least one end of the frequency domain (e.g., arranged in column #1 or #9) may be combined with another RU. For convenience, according to an embodiment of the present invention, the example of a subcarrier RU (e.g., a 52-subcarrier RU) arranged at at least one end of the frequency domain (e.g., arranged in column #1 or #9) not being combined with another RU is provided.

[0196] For example, refer to Figure 24A and Figure 24B This shows the case where "RU allocation subfield = 6". Figure 24A This is the case shown in T1. Figure 24B This is the case shown in T2.

[0197] refer to Figure 24A In traditional technology, when "RU allocation subfield = 6", only one entry can exist (i.e., RU26, RU26, RU52, RU26, RU52, RU26, and RU26 out of the 7 STAs). In this case, it may not be possible to display multi-RU allocation information through the RU allocation subfield.

[0198] For reference, when a single RU is one of 106 subcarrier RU, 242 subcarrier RU, 484 subcarrier RU, and 996 subcarrier RU, multiple receiving devices (i.e., up to 16 receiving devices) can be assigned to that single RU, and when a single RU is one of 26 subcarrier RU and 52 subcarrier RU, only one receiving device can be assigned to that single RU. Therefore, when "RU allocation subfield = 6", each RU can be assigned to one receiving device (e.g., STA).

[0199] However, reference Figure 24B According to an embodiment of the present invention, multiple RUs can be defined by adding a new 2-bit "additional RU allocation subfield".

[0200] Specifically, when "Additional RU allocation subfield = 00", it can display cases where multiple RUs do not exist; when "Additional RU allocation subfield = 01", it can display cases where multiple RUs of RU26+RU52 exist (i.e., multiple RUs of 26+52). When "Additional RU allocation subfield = 10", it can display cases where multiple RUs of RU52+RU26 exist (i.e., multiple RUs of 52+26); when "Additional RU allocation subfield = 11", it can display cases where multiple RUs of RU26+RU52 and multiple RUs of RU52+RU26 exist simultaneously.

[0201] That is, according to an embodiment of the present invention, by adding a 2-bit "additional RU allocation subfield", the multi-RU allocation situation can be displayed as well as... Figure 24A The single RU allocation is shown in the figure.

[0202] For reference, when the multiple RU is one of 26+106 subcarrier RU, 106+26 subcarrier RU, 484+242 subcarrier RU, and 484+996 subcarrier RU, a maximum of 16 receiving devices can be assigned to that multiple RU, and when the multiple RU is one of 26+52 subcarrier RU and 52+26 subcarrier RU, only one receiving device can be assigned to that multiple RU. Therefore, when "RU allocation subfield = 6", each multiple RU (RU26+RU52 or RU52+RU26) can be assigned to one receiving device (e.g., STA).

[0203] For reference only. Figure 24B This assumes that the center 26-tone RU (RU26 arranged in column #5) has been excluded from the objects to be combined with multiple RUs. Figure 12 The diagram shows a table created by arranging 26 subcarriers (RUs) at the center of the frequency domain. That is, the central 26-tone RU may not be combined with the RU52 arranged adjacent to it, and may not form a multi-RU of RU26+RU52 or a multi-RU of RU52+RU26.

[0204] When assuming that a central 26-tone RU can form multiple RUs, the multiple RU allocation can be extended by adding bits to the "Additional RU Allocation Subfield" so that the addition of multiple RUs can be signaled.

[0205] For the sake of convenience, an embodiment of the present invention is used as an example to exclude the center 26-tone RU from the multi-RU combination (i.e., the center 26-tone RU may not be combined with the RU52 that is arranged adjacent to it).

[0206] refer to Figure 25A and Figure 25BThis shows the case where "RU allocation subfield = 128-191". For example, Figure 25A This is the case shown in T1. Figure 25B This is the case shown in T2.

[0207] refer to Figure 25A In conventional techniques, when "RU allocation subfield = 128-191", there can be 64 entries (e.g., RU106, RU26, and RU106). In this case, it may not be possible to display multi-RU allocation information through the RU allocation subfield.

[0208] For example, in Figure 25A The “RU allocation subfield” displays “10y2y1y0z2z1z0”. Here, y2y1y0 refers to the number of STAs that can be allocated to RU106 in columns #1 to #4, and can be defined as 2^2×y2+2^1×y1+y0+1 (up to 8 STAs). Additionally, z2z1z0 refers to the number of STAs that can be allocated to RU106 in columns #6 to #9, and can be defined as 2^2×z2+2^1×z1+z0+1 (up to 8 STAs). Therefore, based on the maximum number of STAs that can be allocated to RU106 in columns #1 to #4 and the maximum number of STAs that can be allocated to RU106 in columns #6 to #9, a total of 64 entries can exist (the number of indices 128 to 191 is also 64).

[0209] However, reference Figure 25B According to an embodiment of the present invention, multiple RUs can be defined by adding a new 2-bit "additional RU allocation subfield".

[0210] Specifically, when "Additional RU allocation subfield = 00", it can display cases where multiple RUs do not exist; when "Additional RU allocation subfield = 01", it can display cases where multiple RUs exist (RU106 + RU26, i.e., 106 + 26 multiple RUs); when "Additional RU allocation subfield = 10", it can display cases where multiple RUs exist (RU26 + RU106, i.e., 26 + 106 multiple RUs); and when "Additional RU allocation subfield = 11", it can display reserved RUs.

[0211] The number of entries for each index (00, 01, 10, or 11) in the second subfield can be 64, which is consistent with... Figure 25A The principle is the same as that described in [the text].

[0212] When the number of RU allocation cases (i.e., possible RU allocation cases) that can be indicated by a combination of eight bits of the first subfield and two bits of the second subfield (e.g., the sum of the number of cases corresponding to 00, 01, 10, and 11 of the second subfield) is greater than the number of RU allocation cases in a specific index of the first subfield (e.g., 128-191), a subindex that does not need to be indicated by two bits of the second subfield (e.g., the subindex corresponding to 11 in 128-191) can be indicated as reserved among the subindexes of the specific index (e.g., the subindex corresponding to 00, 01, 10, and 11 in 128-191).

[0213] Therefore, according to an embodiment of the present invention, by adding a 2-bit "additional RU allocation subfield," the multi-RU allocation situation can be displayed. Figure 25A The single RU allocation is shown in the figure.

[0214] like Figure 24B and Figure 25B As shown, according to an embodiment of the present invention, in Figures 21 to 23 All the small multi-RU combinations shown can be displayed via a 2-bit "Additional RU Assignment Subfield".

[0215] refer to Figures 26A to 26D This shows the case where "RU allocation subfield = 80-87".

[0216] refer to Figure 26A (As shown in T1), in conventional techniques, when "RU allocation subfield = 80-87", there can be 8 entries (i.e., RU106, RU26, RU52, RU26, and RU26). In this case, it may not be possible to display multi-RU allocation information through the RU allocation subfield.

[0217] For example, because Figure 26A The “RU allocation subfield” displays “01010y2y1y0”, so here, y2y1y0 refers to the number of STAs that can be allocated to RU106 in columns #1 to #4, and can be defined as 2^2×y2+2^1×y1+y0+1 (up to 8 STAs). Therefore, based on the maximum number of STAs that can be allocated to RU106 in columns #1 to #4, there can be a total of 8 entries (the number of indices 80 to 87 is also 8).

[0218] However, reference Figure 26B Multiple RUs can be defined using the newly added 2-bit "Additional RU Assignment Subfield".

[0219] Specifically, when "Additional RU allocation subfield = 00", it can display cases where multiple RUs do not exist; when "Additional RU allocation subfield = 01", it can display cases where multiple RUs of RU106 + RU26 exist (i.e., multiple RUs of 106 + 26). When "Additional RU allocation subfield = 10", it can display cases where multiple RUs of RU52 + RU26 exist (i.e., multiple RUs of 52 + 26); when "Additional RU allocation subfield = 11", it can display cases where multiple RUs of RU106 + RU26 and multiple RUs of RU52 + RU26 exist simultaneously.

[0220] The number of entries for each index (00, 01, 10, or 11) in the second subfield can be 8, which is consistent with... Figure 26A The principle is the same as that described in [the text].

[0221] exist Figure 26A or Figure 26B In this context, since the number of STAs that can be assigned to RU106 or RU106+RU26 is 8, therefore... Figure 26B The signaling field formation method cannot assign RU106 or RU106+RU26 to 16 STAs.

[0222] Therefore, refer to Figure 26C This demonstrates a method to support 16 STAs by adding 1 bit to the "RU allocation subfield".

[0223] Specifically, in Figure 26C The “RU allocation subfield” displays “01010y3y2y1y0”. Here, y3y2y1y0 refers to the number of STAs that can be allocated to RU106 or RU106+RU26, and can be defined as 2^3×y3+2^2×y2+2^1×y1+y0+1 (up to 16 STAs).

[0224] That is, by changing the method of forming the “RU allocation subfield” from the traditional y2y1y0 method to the y3y2y1y0 method obtained by adding 1 bit to the y2y1y0 method, more STAs (i.e., up to 8 to 16 STAs) can be supported.

[0225] However, in Figure 26C In this method, the "RU allocation subfield" of the traditional PPDU signaling field can be used differently, and the number of bits in the "RU allocation subfield" increases. Therefore, a method is needed that maintains the definition of the "RU allocation subfield" of the traditional PPDU signaling field while simultaneously supporting up to 16 STAs.

[0226] Therefore, refer to Figure 26DAccording to embodiments of the present invention, a method for RU or multi-RU allocation of up to 16 STAs is described by using an index indicated as “reserved” in the “RU allocation subfield” and the “additional RU allocation subfield”.

[0227] For example, the index "216-223", which is indicated as "reserved" in the "RU allocation subfield", can be used to support up to 16 STAs.

[0228] Specifically, such as Figure 26D As shown, when "RU allocation subfield = 80-87" and "additional RU allocation subfield = 0y3", the case where multiple RUs do not exist can be displayed. When "RU allocation subfield = 80-87" and "additional RU allocation subfield = 1y3", the case where multiple RUs of RU106+RU26 exist (i.e., multiple RUs of 106+26) can be displayed. When "RU allocation subfield = 216-223" and "additional RU allocation subfield = 0y3", the case where multiple RUs of RU52+RU26 exist (i.e., multiple RUs of 52+26) can be displayed. When "RU allocation subfield = 216-223" and "additional RU allocation subfield = 1y3", the case where multiple RUs of RU106+RU26 and multiple RUs of RU52+RU26 exist simultaneously can be displayed.

[0229] For example, when the index of the "Additional RU Allocation Subfield" is 0y3, the case of (00, 01) can exist, and when the index of the "Additional RU Allocation Subfield" is 1y3, the case of (10, 11) can exist.

[0230] Therefore, when the index of the "Additional RU Allocation Subfield" is 00 (i.e., y3 = 0), according to the calculation principle of y3y2y1y0, it can support 1 to 8 STA entries, and when the index of the "Additional RU Allocation Subfield" is 01 (i.e., y3 = 1), according to the calculation principle of y3y2y1y0, it can support 9 to 16 STA entries.

[0231] For example, when "RU allocation subfield = 80-87" and "additional RU allocation subfield = 00", RU106 can be allocated to 1 to 8 STAs, and when "RU allocation subfield = 80-87" and "additional RU allocation subfield = 01", RU106 can be allocated to 9 to 16 STAs. Therefore, a total of 16 entries can be displayed.

[0232] The same allocation method can be applied when "RU allocation subfield = 216-223" and "additional RU allocation subfield = 0y3".

[0233] When the index of the "Additional RU Allocation Subfield" is 10 (i.e., y3 = 0), according to the calculation principle of y3y2y1y0, it can support 1 to 8 STA entries. And when the index of the "Additional RU Allocation Subfield" is 11 (i.e., y3 = 1), according to the calculation principle of y3y2y1y0, it can support 9 to 16 STA entries.

[0234] For example, when "RU allocation subfield = 80-87" and "additional RU allocation subfield = 10", the multiple RUs of RU106+RU26 can be assigned to 1 to 8 STAs, and when "RU allocation subfield = 80-87" and "additional RU allocation subfield = 11", the multiple RUs of RU106+RU26 can be assigned to 9 to 16 STAs. Therefore, a total of 16 entries can be displayed.

[0235] The same allocation method can be applied when "RU allocation subfield = 216-223" and "additional RU allocation subfield = 1y3".

[0236] That is, according to an embodiment of the present invention, the combination of eight bits of the first subfield and two bits of the second subfield can indicate that the maximum number of receiving devices that can be assigned to an RU is 16.

[0237] like Figure 26B Similarly, according to an embodiment of the present invention, when a portion of the multiple RU allocatable cases in a specific index of the first subfield cannot be indicated by a combination of eight bits of the first subfield and two bits of the second subfield, the unindicable portion of the multiple cases can be indicated by a combination of eight bits of the index indicated as reserved in the first subfield and two bits of the second subfield.

[0238] Here, we will use “RU allocation subfield = 216-223” as an example to describe the meaning of “index indicated as reserved in the first subfield”.

[0239] like Figure 20 As shown in T1, "RU allocation subfield = 216-223" will be indicated as reserved. However, according to embodiments conceived in this invention, such as Figure 22 As shown, "RU allocation subfield = 216-223" can be used to supplement the display of multiple cases for the "80-87" index. That is, "indexes indicated as reserved in the first subfield" can refer to the indexes to be indicated as reserved; however, these indexes are used to supplement the display of multiple cases for other indexes as needed.

[0240] According to embodiments of the present invention, in appropriate cases, the number of multiple STAs in an RU (i.e., a single RU) or multiple RUs can be displayed as a combination of a reserved value of the "RU allocation subfield" and a 1-bit "additional RU allocation subfield".

[0241] For example, the 1-bit "Additional RU Allocation Subfield (y3)" can be used to display the number of multiple STAs in an RU (i.e., a single RU) or multiple RUs, and the remaining bits of the "Additional RU Allocation Subfield" can be used to display combinations of multiple RUs.

[0242] According to an embodiment of the present invention, the operation for forming a signaling field through a small number of RUs is implemented using the method described above. The following will describe the use of... Figures 21 to 23 The table T2 shown illustrates a method for forming signaling fields using large multiple RUs.

[0243] In a large multi-RU configuration, there can be RU484+RU242 (including both cases where RU484 is arranged in a lower frequency band than RU242 and cases where RU484 is arranged in a higher frequency band than RU242) and RU484+RU996 (including both cases where RU484 is arranged in a lower frequency band than RU996 and cases where RU484 is arranged in a higher frequency band than RU996).

[0244] Here, for reference Figure 23 This shows the cases where "RU allocation subfield = 224-239" and "RU allocation subfield = 240-255".

[0245] In traditional technologies, such as Figure 20 As shown in T1, reservations can be displayed when “RU allocation subfield = 224-255”.

[0246] However, reference Figure 23 According to an embodiment of the present invention, the reserved "RU allocation subfield" index can be indicated by eight bits in the related art (e.g., RU allocation subfield = "224-239" and "240-255"), and in Figure 20 The T1 is indicated as reserved) and two newly added "additional RU allocation subfields" are used to define large multi-RUs.

[0247] When "RU allocation subfield = 224-239", the multi-RU allocation of RU484+RU242 can be displayed.

[0248] When "Additional RU Allocation Subfield = 00", it displays the sequential arrangement of RU242, RU242, and RU484, and can also display multiple combinations of the second RU242 with RU484. When "Additional RU Allocation Subfield = 01", it displays the sequential arrangement of RU242, RU242, and RU484, and can also display multiple combinations of the first RU242 with RU484. When "Additional RU Allocation Subfield = 10", it displays the sequential arrangement of RU484, RU242, and RU242, and can also display multiple combinations of the second RU242 with RU484. When "Additional RU Allocation Subfield = 11", it displays the sequential arrangement of RU484, RU242, and RU242, and can also display multiple combinations of the first RU242 with RU484.

[0249] On the other hand, when “RU allocation subfield = 240-255”, the multi-RU allocation situation of RU484+RU996 can be displayed.

[0250] When "Additional RU Allocation Subfield = 00", it displays the sequential arrangement of RU484, RU484, and RU996, and can also display multiple combinations of the second RU484 with RU996. When "Additional RU Allocation Subfield = 01", it displays the sequential arrangement of RU484, RU484, and RU996, and can also display multiple combinations of the first RU484 with RU996. When "Additional RU Allocation Subfield = 10", it displays the sequential arrangement of RU996, RU484, and RU484, and can also display multiple combinations of the second RU484 with RU996. When "Additional RU Allocation Subfield = 11", it displays the sequential arrangement of RU996, RU484, and RU484, and can also display multiple combinations of the first RU484 with RU996.

[0251] According to embodiments of the present invention, in both of the above-described cases, the number of multiple STAs in a RU (i.e., a single RU) or multiple RUs can be displayed using only the reserved value of the "RU allocation subfield". Correspondingly, a two-bit "additional RU allocation subfield" can be used to display combinations of multiple RUs.

[0252] For example, in Figure 23 The “RU allocation subfield = 224-239” shows “1110y3y2y1y0”. Here, y3y2y1y0 refers to the number of STAs that can be allocated to the multi-RU RU484+RU242, and can be defined as 2^3×y3+2^2×y2+2^1×y1+y0+1 (up to 16 STAs).

[0253] Therefore, the number of cases for each index (00, 01, 10, or 11) of the second subfield of “RU allocation subfield = 224-239” can be 16.

[0254] In addition, Figure 23 The “RU allocation subfield = 240-255” shows “1111y3y2y1y0”. Here, y3y2y1y0 refers to the number of STAs that can be allocated to multiple RUs RU484+RU996, and can be defined as 2^3×y3+2^2×y2+2^1×y1+y0+1 (up to 16 STAs).

[0255] Therefore, the number of cases for each index (00, 01, 10, or 11) of the second subfield of “RU allocation subfield = 224-239” can be 16.

[0256] For example, the "RU allocation subfield" notifies each subchannel signal corresponding to 20MHz of information about RU allocation. The "RU allocation subfield" can set RU allocation information on a 20MHz subchannel basis.

[0257] Therefore, in order to signal multiple RU484+RU242 or multiple RU484+RU996 via "RU allocation subfield" + "additional RU allocation subfield", the index of "RU allocation subfield" + "additional RU allocation subfield" will be set so that multiple RUs are allocated through multiple 20MHz subchannels.

[0258] For example, to signal the multiple RUs of RU484+RU242, an entry (i.e., an index) indicating that a 242-tone RU (i.e., a 242-subcarrier RU) of a specific 20MHz subchannel is used by the multiple RUs of RU484+RU242 (i.e., 484+242 subcarrier RUs) needs to be added. Therefore, the corresponding entry can be added by using the reserved value of the "RU allocation subfield".

[0259] Specifically, it can be like Figure 23 The setup shown indicates the indices of the 20MHz "RU allocation subfield" and "additional RU allocation subfield" starting with multiple RU484+RU242 or multiple RU484+RU996 (e.g., "RU allocation subfield = 224-239" + "additional RU allocation subfield = 00 / 01 / 10 / 11" or "RU allocation subfield = 240-255" + "additional RU allocation subfield = 00 / 01 / 10 / 11"). According to embodiments conceived in the present invention, because the "RU allocation subfield" in the related art indicates an index reserved for future use (e.g., Figure 20The “RU allocation subfield = 116 or 117” is used as an index to indicate the 20MHz subchannels for multiple RUs of RU484+RU242 or multiple RUs of RU484+RU996 (e.g., Figure 23 (RU allocation subfield = 116 or RU allocation subfield = 117), so multiple RUs of RU484+RU242 or multiple RU484+RU996 can be allocated to a 20MHz subchannel provided after the first 20MHz of multiple RUs of RU484+RU242 or multiple RU484+RU996.

[0260] For example, when "RU allocation subfield = 224" and "additional RU allocation subfield = 10", it can display the arrangement of RU484, RU242 and RU242 in sequence, as well as the multiple combinations of the second RU242 with RU484.

[0261] That is, indexes related to multiple RUs are set in RU484 and the second RU242 (first sub-channel, second sub-channel and fourth sub-channel), and separate indexes can be set independently in the first RU242 (third sub-channel).

[0262] Specifically, in the first 20MHz sub-channel starting with multiple RUs (RU484+RU242), "RU allocation sub-field = 224" and "additional RU allocation sub-field = 10" can be set. In the second sub-channel provided after the first 20MHz sub-channel, "RU allocation sub-field = 116" and "additional RU allocation sub-field = 00" can be set, and in the fourth sub-channel, "RU allocation sub-field = 116" and "additional RU allocation sub-field = 00" can be set.

[0263] Because the third subchannel between the second and fourth subchannels is not a multi-RU of RU484+RU242, a separate RU can be allocated for the third subchannel, distinct from the multi-RU of RU484+RU242. For example, in the third subchannel, "RU allocation subfield = 113" and "additional RU allocation subfield = 00" can be set (when the STA is not allocated), "RU allocation subfield = 192" and "additional RU allocation subfield = 00" can be set (when the STA is different from the STA allocated with the multi-RU of RU484+RU242), or other indices can be set. On the other hand, besides the above methods, there is another method to signal the multi-RU of RU484+RU242 or the multi-RU of RU484+RU996 using "RU allocation subfield" + "additional RU allocation subfield".

[0264] Specifically, when the “RU allocation subfield” + “additional RU allocation subfield” is set to the following index: the index is indicated as “RU allocation subfield = 113” + “additional RU allocation subfield = 00” or reserved (e.g., “RU allocation subfield = 113” + “additional RU allocation subfield = 01 / 10 / 11”), it can be understood that the corresponding 20MHz subchannel is used for multiple RU484+RU242 or multiple RU484+RU996.

[0265] Specifically, when the "RU allocation subfield" + "additional RU allocation subfield" of the current 20MHz subchannel is set to an index corresponding to "113" + "00" or reserved, the work of determining whether there is an index of "RU allocation subfield" + "additional RU allocation subfield" corresponding to a large number of RUs in the 20MHz subchannel immediately preceding the corresponding subchannel (i.e., arranged in a lower frequency band) can be performed in advance. When it is determined that there is an index of "RU allocation subfield" + "additional RU allocation subfield" corresponding to a large number of RUs, the required 20MHz subchannel is calculated based on the corresponding 20MHz subchannel, and based on the calculation result, it can be determined whether the current 20MHz subchannel is allocated multiple RUs of RU484 + RU242 or multiple RUs of RU484 + RU996.

[0266] When the current 20MHz "RU allocation subfield" + "additional RU allocation subfield" is set to an index corresponding to "113" + "00" or reserved, if it is determined that there is no index of "RU allocation subfield" + "additional RU allocation subfield" corresponding to a large multi-RU immediately before the corresponding subchannel, the RU of the current 20MHz subchannel may not be allocated to any STA.

[0267] For example, if the "RU allocation subfield" + "additional RU allocation subfield" of the current 20MHz subchannel is set to an index corresponding to "113" + "00" or a reserved state, when it is determined that the index of the "RU allocation subfield" + "additional RU allocation subfield" of the 20MHz subchannel arranged immediately before the corresponding subchannel is "224" + "10", it can be determined that the current 20MHz subchannel is the second subchannel of RU484 in RU484 + RU242.

[0268] On the other hand, for example, when the "RU allocation subfield" + "additional RU allocation subfield" of the current 20MHz subchannel is set to an index corresponding to "113" + "00" or reserved, when it is determined that the index of the "RU allocation subfield" + "additional RU allocation subfield" of the 20MHz subchannel arranged immediately before the corresponding subchannel is "112" + "00", the RU of the current 20MHz subchannel may not be allocated to any STA.

[0269] As described above, according to embodiments of the present invention, large multi-RUs can be defined by an eight-bit index of a "RU allocation subfield" reserved in the related art and a newly added two-bit "additional RU allocation subfield".

[0270] That is, according to the embodiment of the present invention, the reserved value of the "RU allocation subfield" and the 2-bit "additional RU allocation subfield" can be used to display... Figure 21 and Figure 23 All the large multi-RU combinations shown.

[0271] As described above, according to an embodiment of the present invention, the method described above for forming signaling fields through large multiple RUs is used. Hereinafter, reference is made to... Figure 27 and Figure 28 This will describe the wireless communication methods in a WLAN system.

[0272] Figure 27 This is a flowchart illustrating a wireless communication method in a WLAN system where a transmitting device assigns a RU to a receiving device. Figure 28 This is a flowchart illustrating a wireless communication method in a WLAN system where a receiving device receives a RU from a transmitting device.

[0273] refer to Figure 2 and Figure 27 This illustrates a wireless communication method in a WLAN system where a transmitting device allocates a RU to a receiving device. Therefore, it is assumed that... Figure 2 The wireless communication device 1100 is a transmitting device (e.g., an access point).

[0274] First, in operation S100, a PPDU including a preamble and a payload is generated.

[0275] Specifically, transceiver 1140 can generate a PPDU including a preamble and a payload by using the PPDU format and multi-RU allocation information stored in memory 1120.

[0276] Here, the PPDU can be either an HE PPDU or an EHT PPDU. Additionally, the preamble can include multiple training fields and multiple signaling fields, and the payload can include data fields and packet extension fields.

[0277] One of the signaling fields (e.g., one of the HE-SIG-A field, HE-SIG-B field, U-SIG field, and EHT-SIG field) may include RU allocation information for at least one receiving device (e.g., STA).

[0278] Here, RU allocation information may include the first subfield ( Figures 21 to 23 The “RU allocation subfield” and the second subfield are shown. Figures 21 to 23 The “Additional RU Allocation Subfield” shown has a first subfield indicating the arrangement of RUs in the frequency domain corresponding to the PPDU, and a second subfield indicating the multiple combinations of RUs.

[0279] Transceiver 1140 can form a signaling field according to an embodiment of the present invention (i.e., Figures 21 to 26D The method for forming signaling fields described herein generates PPDUs by forming signaling fields for preambles.

[0280] When a PPDU is generated in operation S100, the generated PPDU is sent to at least one receiving device in operation S200.

[0281] Specifically, transceiver 1140 can transmit the generated PPDU to at least one external receiving device (e.g., STA) via antenna arrays 1101 to 1104.

[0282] Therefore, at least one external receiving device (e.g., STA) can use the RU assigned to it based on the PPDU received from the transmitting device (e.g., AP).

[0283] For example, a single RU or multiple RUs can be assigned to at least one external receiving device.

[0284] refer to Figure 2 and Figure 28 This illustrates a wireless communication method in a WLAN system where a receiving device receives a RU from a transmitting device. Therefore, it is assumed that... Figure 2 The wireless communication device 1100 is a receiving device (e.g., STA).

[0285] First, in operation S300, a PPDU including a preamble and a payload is received.

[0286] Specifically, transceiver 1140 can receive PPDUs from external transmitting devices (e.g., APs) via antenna arrays 1101 to 1104.

[0287] Here, the PPDU can be either an HE PPDU or an EHT PPDU. Additionally, the preamble can include multiple training fields and multiple signaling fields, and the payload can include data fields and PE fields.

[0288] One of the signaling fields (e.g., one of the HE-SIG-A field, HE-SIG-B field, U-SIG field, and EHT-SIG field) may include RU allocation information for at least one receiving device (e.g., STA).

[0289] Here, RU allocation information may include the first subfield ( Figures 21 to 23 The “RU allocation subfield” and the second subfield are shown. Figures 21 to 23 The “Additional RU Allocation Subfield” shown has a first subfield indicating the arrangement of RUs in the frequency domain corresponding to the PPDU, and a second subfield indicating the multiple combinations of RUs.

[0290] Transceiver 1140 can form a signaling field according to an embodiment of the present invention (i.e., Figures 21 to 26D The method for forming signaling fields described herein generates PPDUs by forming signaling fields for preambles.

[0291] When a PPDU is received in operation S300, the payload is decoded based on the preamble in operation S400.

[0292] Specifically, the transceiver 1140f can decode the payload based on the preamble of the received PPDU.

[0293] Therefore, the receiving device (e.g., STA) can distinguish the RU assigned to it based on the decoding result, and can use the RU for subsequent communication.

[0294] As described above, according to embodiments of the present invention, by forming a PPDU that efficiently allocates multiple RUs to users, spectral efficiency and data transmission rate in the physical layer can be improved.

[0295] Although various aspects of the inventive concept have been specifically shown and described with reference to embodiments thereof, it will be understood that various changes in form and detail may be made therein without departing from the spirit and scope of the inventive concept as defined by the appended claims and their equivalents.

Claims

1. A transmitting device of a wireless local area network system, the transmitting device comprising: a transceiver configured to generate a physical layer convergence protocol (PLCP) protocol data unit (PPDU) including a preamble and a payload, and transmit the generated PPDU to at least one receiving device; and a processor that controls the transceiver, wherein the preamble includes a plurality of training fields and a plurality of signaling fields, wherein resource unit (RU) allocation information for the at least one receiving device is included in a common field of one of the plurality of signaling fields, and wherein the RU allocation information includes a first subfield and a second subfield, the first subfield indicating an arrangement of RUs in a frequency domain corresponding to the PPDU, and the second subfield indicating whether at least one multi-RU is allocated and, in a case that the at least one multi-RU is allocated, which portion of the RUs indicated by the first subfield is to be combined to form the at least one multi-RU. the payload includes a data field, 2. The transmitting device of claim 1, wherein, wherein at least one RU is arranged in the frequency domain of the data field based on the RU allocation information, wherein the RUs include one single RU of 26, 52, 106, 242, 484, and 996 subcarriers, or one multi-RU of 26+52, 52+26, 26+106, 106+26, 484+242, and 484+996 subcarriers. when the single RU is one of the 106, 242, 484, and 996 subcarrier RUs, the single RU is allocable to up to 16 receiving devices, and 3. The transmitting device of claim 2, wherein, wherein, when the single RU is one of the 26 and 52 subcarrier RUs, the single RU is allocable to one receiving device. when the multi-RU is one of the 26+106, 106+26, 484+242, and 484+996 subcarrier RUs, the multi-RU is allocable to up to 16 receiving devices, and 4. The transmitting device of claim 2, wherein, wherein, when the multi-RU is one of the 26+52 and 52+26 subcarrier RUs, the multi-RU is allocable to one receiving device. the single RU or the multi-RU is allocable to the at least one receiving device.

5. The transmitting device of claim 2, wherein, the first subfield includes eight bits, the second subfield includes two bits, and 6. The transmitting device of claim 2, wherein, wherein a combination of the eight bits of the first subfield and the two bits of the second subfield is able to indicate a maximum number of receiving devices to which the RUs are allocated up to 16. ​ 7. The transmitting device of claim 6, wherein, When a number of RU allocable cases that can be indicated by the combination of the eight bits of the first subfield and the two bits of the second subfield is greater than a number of RU allocable cases in a particular index of the first subfield, sub-indices of the particular index that do not need to be indicated by the two bits of the second subfield are indicated as reserved.

8. The transmitting device of claim 6, wherein, When a number of RU allocable cases that can be indicated by the combination of the eight bits of the first subfield and the two bits of the second subfield is greater than a number of RU allocable cases in a particular index of the first subfield, sub-indices of the particular index that do not need to be indicated by the two bits of the second subfield are indicated as reserved.

9. The transmitting device of claim 2, wherein, The 52-subcarrier RU arranged in at least one of the two ends of the frequency domain is not combined with another RU.

10. The transmitting device of claim 2, wherein, The 26-subcarrier RU, the 52-subcarrier RU, and the 106-subcarrier RU are small RUs, and The 242-subcarrier RU, the 484-subcarrier RU, and the 996-subcarrier RU are large RUs.

11. The transmitting device of claim 10, wherein, The 26+52-subcarrier RU, the 52+26-subcarrier RU, the 26+106-subcarrier RU, and the 106+26-subcarrier RU are small multiple RUs, and The 484+242-subcarrier RU and the 484+996-subcarrier RU are large multiple RUs.

12. The transmitting device of claim 1, wherein, A single RU or multiple RUs can be allocated to the at least one receiving device.

13. The transmitting device of claim 1, wherein, The first subfield includes eight bits, the second subfield includes two bits, and The combination of the eight bits of the first subfield and the two bits of the second subfield can indicate a maximum number of receiving devices to which the RUs are allocated up to 16.

14. The transmitting device of claim 13, wherein, When a number of RU allocable cases that can be indicated by the combination of the eight bits of the first subfield and the two bits of the second subfield is greater than a number of RU allocable cases in a particular index of the first subfield, sub-indices of the particular index that do not need to be indicated by the two bits of the second subfield are indicated as reserved.

15. The transmitting device of claim 13, wherein, When a number of RU allocable cases that can be indicated by the combination of the eight bits of the first subfield and the two bits of the second subfield is greater than a number of RU allocable cases in a particular index of the first subfield, sub-indices of the particular index that do not need to be indicated by the two bits of the second subfield are indicated as reserved.

16. A receiving device of a wireless local area network system, the receiving device comprising: a transceiver configured to receive a physical layer convergence protocol (PLCP) protocol data unit (PPDU) including a preamble and a payload, and decode the payload based on the preamble; and a processor that controls the transceiver, wherein the preamble includes a plurality of training fields and a plurality of signaling fields, wherein resource unit (RU) allocation information for at least one receiving device is included in a common field of one of the plurality of signaling fields, and wherein the RU allocation information includes a first subfield and a second subfield. The RU allocation information includes a first subfield and a second subfield, the first subfield indicates an arrangement of RUs in a frequency domain corresponding to the PPDU, and the second subfield indicates whether at least one multi-RU is allocated and, in a case where the at least one multi-RU is allocated, which part of the RUs indicated by the first subfield is to be combined to form the at least one multi-RU.

17. The receiving device of claim 16, wherein, The payload includes a data field, The at least one RU is arranged in the frequency domain of the data field based on the RU allocation information, The RUs include one single RU of 26 subcarrier RUs, 52 subcarrier RUs, 106 subcarrier RUs, 242 subcarrier RUs, 484 subcarrier RUs, and 996 subcarrier RUs, or one multi-RU of 26+52 subcarrier RUs, 52+26 subcarrier RUs, 26+106 subcarrier RUs, 106+26 subcarrier RUs, 484+242 subcarrier RUs, and 484+996 subcarrier RUs.

18. The receiving device of claim 17, wherein, When the single RU is one of the 106 subcarrier RUs, the 242 subcarrier RUs, the 484 subcarrier RUs, and the 996 subcarrier RUs, the single RU is allocable to up to 16 receiving devices, and When the single RU is one of the 26 subcarrier RUs and the 52 subcarrier RUs, the single RU is allocable to one receiving device.

19. The receiving device of claim 17, wherein, When the multi-RU is one of the 26+106 subcarrier RUs, the 106+26 subcarrier RUs, the 484+242 subcarrier RUs, and the 484+996 subcarrier RUs, the multi-RU is allocable to up to 16 receiving devices, and When the multi-RU is one of the 26+52 subcarrier RUs and the 52+26 subcarrier RUs, the multi-RU is allocable to one receiving device.

20. The receiving device of claim 17, wherein, The single RU or the multi-RU is allocable to the receiving device.

Images