Apparatus and method for communication based on extended bandwidth and multiple resource units

Abstract

Apparatus and methods for communication based on extended bandwidth and multiple resource units are provided. A method of communication based on an extended bandwidth and multiple resource units includes: allocating at least one resource unit (RU) within the bandwidth to a second device; generating at least one subfield defining the at least one RU; and generating a trigger frame including a user information field including the at least one subfield, and transmitting a PPDU including the trigger frame to the at least one second device, in which the step of generating comprises: setting at least seven bits associated with the at least one RU, and when the bandwidth comprises at least four sub-bands, setting at least two bits to a value defining a sub-band comprising the at least one RU.

Description

[0001] This application is a divisional application of an invention patent application with an application date of May 14, 2021, application number 202110528524.8, and invention name “Device and method for communication based on extended bandwidth and multiple resource units”.

[0002] This application is related to and claims U.S. Provisional Application No. 63 / 025,279 filed on May 15, 2020, U.S. Provisional Application No. 63 / 073,628 filed on September 2, 2020, U.S. Provisional Application No. 63 / 089,275 filed on October 8, 2020, U.S. Provisional Application No. 63 / 094,686 filed on October 21, 2020, and U.S. Provisional Application No. 63 / 094,686 filed on October 27, 2020. The invention claims priority from U.S. Provisional Application No. 63 / 106,128 filed on November 3, 2020, U.S. Provisional Application No. 63 / 109,024 filed on November 3, 2020, U.S. Provisional Application No. 63 / 118,788 filed on November 27, 2020, and Korean Patent Application No. 10-2021-0009755 filed in the Korean Intellectual Property Office on January 22, 2021, the disclosures of which are incorporated herein by reference in their entirety. Technical Field

[0003] The present disclosure relates generally to wireless communications, and more particularly, to an apparatus and method for communication based on extended bandwidth and multiple resource units (multi-RUs) in a wireless local area network (WLAN) system. Background Art

[0004] WLAN is a technology for wirelessly connecting two or more devices to each other, where the devices are located in a local environment such as a building or campus. WLAN can be in infrastructure mode, where an access point (AP) serves multiple user devices such as smartphones and laptops, where the AP can serve as a gateway to a remote network (usually the Internet). Alternatively, WLAN operates as an ad hoc network between peer devices without an AP. In either case, WLAN employs orthogonal frequency division multiplexing (OFDM) technology, where each user device communicates with the AP or another user device using an allocated set of OFDM subcarriers 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 evolved into 802.11b, 802.11a, 802.11g, 802.11n, 802.11ac, and 802.11ax versions, and can support transmission speeds of up to 1 Gigabyte per second by using OFDM technology. In version 802.11ac, data can be sent to multiple users simultaneously through a multi-user multiple input multiple output (MU-MIMO) scheme. In 802.11ax (referred to as "high efficiency" (HE) only), multiple access is achieved by using orthogonal frequency division multiple access (OFDMA) technology to provide available subcarriers to users in a separate manner, combined with the application of MU-MIMO. WLAN systems that apply 802.11ax can effectively support communications in crowded areas and outdoors.

[0006] Another latest version, 802.11be (Extreme High Throughput (EHT)), plans to support 6 GHz unlicensed band, bandwidth up to 320 MHz per channel, hybrid automatic repeat request (HARQ), and up to 16×16 MIMO. Therefore, the next generation WLAN system is expected to effectively support low latency and ultra-fast transmission with performance indicators similar to the New Radio (NR) 5G technology. Summary of the invention

[0007] Embodiments of the inventive concept provide an apparatus and method for efficiently allocating multiple RUs to users within an extended uplink bandwidth in a wireless local area network (WLAN) system.

[0008] According to an aspect, a method for communicating with at least one second device by a first device in a WLAN system may include: allocating at least one resource unit (RU) within a bandwidth to the second device. Generating at least one subfield defining the at least one RU. This may involve setting at least two bits to a value defining a subband including the at least one RU in a subband. When the bandwidth includes at least four subbands, generating a trigger frame including a user information field, wherein the user information field includes the at least one subfield. Sending a physical layer protocol data unit including the trigger frame to the at least one second device.

[0009] According to another aspect, a first device configured to communicate with at least one second device in a WLAN system may include: a transceiver configured to send a PPDU to the at least one second device. The transceiver includes a signal processor, wherein the signal processor is configured to: allocate at least one RU to the second device within a bandwidth, generate at least one subfield defining the at least one RU, generate a trigger frame including a user information field, wherein the user information field includes the at least one subfield, and generate the PPDU including the trigger frame. The signal processor is configured to set at least 7 bits associated with at least one RU, and when the bandwidth includes at least four subbands, set at least two bits to a value defining a subband including the at least one RU.

[0010] According to another aspect, a method for communicating with a first device by a second device in a WLAN system may include: receiving a PPDU from the first device; extracting common information from the PPDU and extracting an uplink bandwidth field from the common information; extracting user information from the PPDU and extracting at least one subfield from the user information; and identifying at least one RU within a bandwidth based on the uplink bandwidth field and the at least one subfield. The step of identifying the at least one RU includes: when the bandwidth includes at least four subbands, identifying the subband including the at least one RU based on at least a first bit and a second bit of the at least one subfield.

[0011] According to another aspect, a method for communicating with at least one second device by a first device in a WLAN system may include: allocating at least one RU within a bandwidth of 320 MHz to the second device; and generating at least one subfield defining the at least one RU, wherein the step of generating includes setting at least eight bits associated with the at least one RU, and when the bandwidth is 320 MHz and the total bandwidth of the at least one RU is equal to or less than 160 MHz, setting a first bit having a value representing one of a lower 160 MHz and an upper 160 MHz including the at least one RU. As described above, a trigger frame is generated and a PPDU is transmitted.

[0012] On the other hand, a method for communicating with at least one second device by a first device in a WLAN system includes: allocating at least one RU within a bandwidth including N subbands to the second device; generating at least one subfield defining the at least one RU, wherein the generating step includes: setting K bits associated with the at least one RU, and setting M additional bits, wherein the M additional bits have values ​​that jointly define a subband in the subband including the at least one RU, wherein the M <N<K。 BRIEF DESCRIPTION OF THE DRAWINGS

[0013] Embodiments of the inventive concept will be more clearly understood through the following detailed description in conjunction with the accompanying drawings, in which like reference numerals represent like elements throughout, wherein:

[0014] Figure 1 is a diagram illustrating a wireless local area network (WLAN) system;

[0015] Figure 2 is a block diagram illustrating a wireless communication device that transmits or receives a physical layer convergence protocol (PLCP) protocol data unit (PPDU);

[0016] Figure 3 is a diagram showing the structure of a High Efficiency (HE) Single User (SU) PPDU;

[0017] Figure 4 is a diagram showing the structure of a HE extended range (ER) SU PPDU;

[0018] Figure 5 is a diagram showing the structure of a PPDU based on a HE trigger (TB);

[0019] Figure 6 is a diagram showing the structure of a HE multi-user (MU) PPDU;

[0020] Figure 7 It is shown Figure 6 An illustration of the structure of the HE-SIG-B field;

[0021] Figure 8 is a diagram showing arrangement of HE MU PPDUs by frequency band;

[0022] Fig.9A and Fig. 9B is a diagram showing an example of RUs and their indexes available in a 20 MHz OFDMA PPDU;

[0023] Fig. 10A and Fig. 10B is a diagram showing an example of RUs and their indexes available in a 40 MHz OFDM APPDU;

[0024] Fig.11A and Fig. 11B is a diagram showing an example of RUs and their indexes available in an 80 MHz OFDM APPDU;

[0025] Fig. 12A and Fig. 12B is a diagram showing an example of an index of RUs available in a 160 MHz OFDM APDU;

[0026] Fig.13A , Fig. 13B , Fig. 13C , Fig.13D and Fig.13E is a diagram showing an example of an index of RUs available in a 320 MHz OFDMA PPDU;

[0027] Fig.14 is a diagram showing the structure of a trigger frame;

[0028] Fig.15 is a diagram showing an example of a common information field;

[0029] Fig.16A and Fig. 16B is a diagram showing various examples of user information fields;

[0030] Fig.17 is a message flow diagram illustrating a communication method based on extended bandwidth and multiple RUs according to an embodiment;

[0031] Fig.18 Shows a small multi-RU that can be allocated to a STA in an OFDMA 20MHz EHT PPDU according to an embodiment;

[0032] Fig.19 Shows a small multi-RU that may be allocated to a STA in an OFDMA 40MHz EHT PPDU according to an embodiment;

[0033] Fig. 20 Shows a small multi-RU allocable to a STA in an OFDMA 80MHz EHT PPDU according to an embodiment;

[0034] Fig.21A and Fig.21B Shows a small multi-RU allocable to a STA in an OFDMA 160MHz EHT PPDU according to an embodiment;

[0035] Fig.22A , Fig. 22B and Fig. 22C Shows a small multi-RU allocable to a STA in an OFDMA 320MHz EHT PPDU according to an embodiment;

[0036] Fig.23 shows a large multi-RU allocable to a STA in an OFDMA 80 MHz EHT PPDU according to an embodiment;

[0037] Fig.24 shows a large multi-RU allocable to a STA in an OFDMA 160 MHz EHT PPDU according to an embodiment;

[0038] Fig.25A , Fig.25B and Fig.25C shows a large multi-RU allocable to a STA in an OFDMA 320MHz EHT PPDU according to an embodiment;

[0039] Fig.26 is a flow chart illustrating a communication method based on extended bandwidth and multiple RUs according to an embodiment;

[0040] Fig. 27 is a flow chart illustrating a communication method based on extended bandwidth and multiple RUs according to an embodiment;

[0041] Fig.28A and Fig.28B is a diagram illustrating an example of a user information field according to an example embodiment;

[0042] Fig.29A and Fig.29B is a diagram illustrating an RU allocation subfield according to an embodiment;

[0043] Fig.30 shows the value of a multi-RU including a 996-subcarrier RU and a 484-subcarrier RU and the RU allocation subfield according to an embodiment;

[0044] Fig.31 shows the value of a multi-RU including a 996-subcarrier RU, a 484-subcarrier RU, and a 242-subcarrier RU and the RU allocation subfield according to an embodiment;

[0045] Fig.32 shows the value of a multi-RU including two 996-subcarrier RUs and one 484-subcarrier RU and the RU allocation subfield according to an embodiment;

[0046] Fig.33 shows the value of a multi-RU including three 996-subcarrier RUs and the RU allocation subfield according to an embodiment;

[0047] Fig.34 shows the value of a multi-RU including three 996-subcarrier RUs and one 484-subcarrier RU and the RU allocation subfield according to an embodiment; and

[0048] Fig.35 is a diagram illustrating an RU allocation subfield according to an embodiment. DETAILED DESCRIPTION

[0049] Hereinafter, embodiments of the inventive concept will be described in detail with reference to the accompanying drawings.

[0050] The terms used herein are used to describe embodiments and are not used to limit the inventive concept. In this article, unless specifically described, the singular includes the plural. The components, processes, operations and / or elements described do not exclude the existence or addition of one or more other components, processes, operations and / or elements.

[0051] Unless otherwise defined, all terms used herein (including technical and scientific terms) may be used with the meanings generally understood by those skilled in the art. In addition, unless specifically defined, terms defined in commonly used dictionaries will not be ideally or excessively interpreted.

[0052] In addition, when describing the embodiments of the present invention in detail, OFDM or OFDM-based wireless communication systems, especially IEEE 802.11 standards, will be mainly described. However, the present invention can also be applied to other communication systems with similar background technologies and channel types (e.g., cellular communication systems such as long term evolution (LTE), advanced LTE (LTE-A), new radio (NR) / 5G, wireless broadband (WiBro) or global system for mobile communications (GSM) or remote communication systems such as Bluetooth or near field communication (NFC)).

[0053] Here, the term "connect (combination)" and similar words refer to direct or indirect communication between two or more components that are in physical contact or not in physical contact. The terms "send", "receive" and "communication" and similar words include all direct and indirect communications. "Including" and / or "including" used here means including but not limited to this. "Or" is a collective term meaning "and / or". "Related to ~" and similar words refer to including, being included in ~, connected to ~, meaning, meaning in ~, connected to ~, combined with ~, can communicate with ~, cooperate with ~, insert, place in parallel, close to ~, bound to ~, have the characteristics of ~, and have a relationship with ~. "Controller" refers to a device, system or part thereof that controls at least one operation. The controller can be implemented by hardware or a combination of hardware and software and / or firmware. The functions associated with a specific controller can be centralized or decentralized locally or remotely.

[0054] In addition, the various functions described below can be implemented or supported by one or more computer programs, and each program is formed by a computer-readable program code and executed in a computer-readable recording medium. "Application" and "program" refer to one or more computer programs, software components, instruction sets, processing, functions, objects, classes, instances, related data or computer programs, software components, instruction sets, processing, functions, objects, classes, instances and related data parts suitable for implementing computer-readable program code segments. "Computer-readable program code" includes all types of computer codes including source code, object code and execution code. "Computer-readable medium" includes all types of media that can be accessed by a computer, such as read-only memory (ROM), random access memory (RAM), hard drive, compact disk (CD), digital video disk (DVD) and other types of memory. "Non-temporary" computer-readable medium does not include wired, wireless, optical or other communication links that send temporary electrical signals or other signals. Non-temporary computer-readable media include media that can permanently store data and media that can store data and can be overwritten later, such as rewritable optical disks or removable storage devices.

[0055] Here, the terms "subcarrier" and "tone" are used interchangeably, and the "size of RU" refers to the number of subcarriers of the RU.

[0056] Here, "the leftmost side of a band" refers to the range of frequencies within the band starting from the lowest frequency within the band.

[0057] Figure 1 is a diagram illustrating a wireless local area network (WLAN) system 100 . Figure 2 1 is a block diagram showing a wireless communication device 1100 that transmits or receives a physical layer convergence protocol (PLCP) protocol data unit (PPDU). Figure 1 As shown, WLAN system 100 may include access point (AP) 101 and access point (AP) 103. AP 101 and AP 103 may communicate with at least one network 130, such as the Internet, an Internet Protocol (IP) network, or a dedicated data network.

[0058] AP 101 and AP 103 may provide wireless connections to network 130 for multiple stations (STAs) 111 to 114 in their coverage areas 120 and 125. AP 101 and AP 103 may communicate with each other and with STAs 111 to 114 by using WiFi or other WLAN communication technologies. Herein, an AP may be referred to as a first device or a transmitting device, and a STA may be referred to as a second device or a receiving device.

[0059] For example, other well-known terms such as "router" and "gateway" may be used instead of "AP" depending on the network type. In addition, in a WLAN, an AP is provided for a wireless channel. In some scenarios, an AP may operate as a STA, such as when a first AP communicates with a second AP and the second AP operates as a STA based on control information provided by the first AP.

[0060] In addition, depending on the network type, "STA" may be used instead of other well-known terms such as "mobile station", "user station", "remote terminal", "user equipment", "wireless terminal", "user device" or "user". For convenience, here, "STA" is used to represent a remote wireless device that is wirelessly connected to an AP or connected to a wireless channel in a WLAN. Here, a STA is considered to be a mobile device (e.g., a mobile phone or a smart phone). In other examples, a STA is a fixed device (e.g., a desktop computer, an AP, a media player, a fixed sensor, or a television).

[0061] Approximate ranges of the coverage areas 120 and 125 are marked with dotted lines. Here, for simplicity of explanation, the coverage areas 120 and 125 are shown as circles. However, each of the coverage areas 120 and 125 associated with the APs 101 and 103 may have another shape reflecting a change in the wireless environment associated with natural or artificial obstacles or another irregular shape according to the settings of the APs 101 and 103.

[0062] As described in detail later, AP 101 and AP 103 may include circuits and / or programs for managing transmissions of uplink multi-users (ULMU) or downlink multi-users (DLMU) in WLAN system 100.

[0063] In other examples, the WLAN system 100 may include any number of appropriately arranged APs and any number of STAs. In addition, the AP 101 may communicate directly with any number of STAs. The AP 101 may provide wireless broadband access to multiple STAs 111 to 114 via the network 130.

[0064] Similarly, each of AP 101 and AP 103 may communicate directly with network 130 and may provide wireless broadband access to a plurality of STAs 111 to 114 via network 130. In addition, AP 101 and AP 103 may be configured to connect to varying external networks, such as an external telephone network or a data network.

[0065] like Figure 2As depicted in FIG. 1 , a wireless communication device for sending a PPDU or receiving a PPDU is shown. For example, Figure 2 The wireless communication device 1100 may be a transmitting device (eg, an AP) or a receiving device (eg, a STA) having a transceiver capable of performing data communication. That is, Figure 2 The wireless communication device 1100 may be Figure 1 The AP 101 and AP 103 shown and one of the plurality of STAs 111 to 114 may be applied to, for example, a computer, a smart phone, a portable electronic device, a tablet, a wearable device, or a sensor for the Internet of Things (IoT). In the following description, STA is an example of a "receiving device". In addition, the terms "user" and "STA" may be used interchangeably. In addition, AP is an example of a "transmitting device" in the following description.

[0066] For ease of explanation, the following takes the case where the wireless communication device 1100 is a transmitting device as an example.

[0067] 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, the memory 1120, the transceiver 1140, and the antenna arrays 1101 to 1104 may be directly or indirectly connected to each other.

[0068] The main processor 1130 may control the memory 1120 and the transceiver 1140. The PPDU format and multiple resource unit (RU) allocation information may be stored in the memory 1120. The transceiver 1140 may generate a PPDU by using the PPDU format and multiple RU allocation information stored in the memory 1120. The transceiver 1140 may transmit the generated PPDU to an external receiving device through the antenna arrays 1101 to 1104.

[0069] Here, the memory 1120 may store a PPDU format 1121 including a RU allocation signaling format according to an embodiment of the present invention, which will be described later. The memory 1120 may store processor executable instructions for executing the RU allocation module 1122 and the PPDU generation module 1123. The processor executable instructions may be executed by the main processor 1130, in which case the circuits of the main processor 1130 perform the functions of the RU allocation module 1122 and the PPDU generation module 1123; therefore, these modules may be interchangeably referred to as RU allocation circuits 1122 and PPDU generation circuits, respectively.

[0070] For example, according to an embodiment of the inventive concept, the RU allocation module 1122 may use an RU allocation algorithm, method, or strategy to allocate at least one RU (e.g., a single RU or multiple RUs) to a user. The PPDU generation module 1123 may generate signaling and indications related to the allocation of at least one RU in a trigger frame of a PPDU.

[0071] On the other hand, the transceiver 1140 may include a signal processor 1150. The signal processor 1150 may include various transmission path modules or various types of communication transmission units that generate a portion of the PPDU.

[0072] 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, which can, for example, generate QAM symbols; a guard interval and windowing insertion module 1116, which can, for example, provide a guard interval in frequency to reduce interference in the spectrum and transform the signal by windowing; and an inverse discrete Fourier transformer (IDFT) 1117.

[0073] Note that the transceiver 1140 may include components known to those skilled in the art as shown in the figure. The corresponding components may be implemented according to methods known to those skilled in the art by using hardware, firmware, software logic, or a combination of hardware, firmware, and software logic.

[0074] When the wireless communication device 1100 is a receiving device, Figure 2 The transceiver 1140 shown in FIG. 1 may include components in a receive path.

[0075] That is, when the wireless communication device 1100 is a receiving device, the transceiver 1140 may receive a PPDU including a trigger frame from a transmitting device. The transceiver 1140 may decode the trigger frame included in the received PPDU. That is, the transceiver 1140 may decode the trigger frame by an internal decoder (not shown) to identify the RU allocated to the receiving device, decode the trigger frame, identify at least one RU allocated to the uplink bandwidth and the receiving device, and send the PPDU to the transmitting device based on the identified at least one RU. Optionally, the decoding may be performed by a component other than the transceiver 1140 (e.g., the main processor 1130).

[0076] In the following, reference will be made to Figures 3 to 6 Describes the High Efficiency (HE) PPDU used in the Institute of Electrical and Electronics Engineers (IEEE) standard (i.e., 802.11ax). For example, Figure 2 The wireless communication device 1100 generates a reference Figures 3 to 15 HE PPDU described.

[0077] Figure 3 is a diagram showing the structure of an HE single user (SU) PPDU. Figure 4 is a diagram showing the structure of a HE extended range (ER) SU PPDU. Figure 5 2 is a diagram showing the structure of a HE trigger based PPDU. Figures 3 to 6 As shown, each HE PPDU may include a preamble and a payload, wherein the preamble includes a plurality of training fields and a plurality of signaling fields, and the payload includes a data (DATA) field and a packet extension (PE) field.

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

[0079] Figure 3 The HE SU PPDU does not include the HE-SIG-B field, and Figure 6 The HE MU PPDU may also include a HE-SIG-B field. Figure 4 The HE ER SU PPDU does not include the HE-SIG-B field. However, the symbols of the HE-SIG-A field can be repeated with a length of 16 μs. In addition, Figure 5 The HE TB PPDU does not include the HE-SIG-B field. However, the symbol of the HE-STF can be repeated with a length of 8 μs.

[0080] Here, the fields included in the preamble will be briefly described as follows.

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

[0082] The L-LTF may include long training OFDM symbols and may be used for fine frequency / time synchronization and channel estimation.

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

[0084] The HE-SIG-A field may include the following control information commonly used by receiving devices.

[0085] 1) Downlink (DL) / Uplink (UL) indicator

[0086] 2) Basic Service Set (BSS) Color field as an identifier of the BSS

[0087] 3) A field indicating the remaining time of the current transmission opportunity (TXOP) cycle

[0088] 4) Bandwidth field indicating 20 / 40 / 80 / 160 / 80+80MHz

[0089] 5) A field indicating the modulation and coding scheme (MCS) applied to the HE-SIG-B field

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

[0091] 7) Field indicating the number of symbols used for the HE-SIG-B field

[0092] 8) Field indicating whether the HE-SIG-B field is generated over the entire band

[0093] 9) Field v indicates the number of symbols of HE-LTF

[0094] 10) A field indicating the length of the HE-LTF and the length of the cyclic prefix (CP) field

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

[0096] 12) Field indicating control information about the PE field

[0097] 13) A field indicating information about a cyclic redundancy check (CRC) field of the HE-SIG-A field

[0098] The HE-SIG-A field may also include various information items other than 1) to 13) above, or may not include some of the information items in 1) to 13) above. In environments other than the MU environment, some information items may be added to the HE-SIG-A field, or some information items in the HE-SIG-A field may be omitted.

[0099] The HE-SIG-B field may be used for the PPDU for the MU. Therefore, the HE-SIG-B field may be omitted from the PPDU for the SU. For example, because the HE-SIG-A field or the HE-SIG-B field may include RU allocation information about at least one receiving device for downlink transmission. The PE field may have a duration of 4 μs, 8 μs, 12 μs, or 16 μs, and additional reception processing time may be provided at the end of the HE PPDU.

[0100] Figure 7 is a diagram showing the structure of an EHT TB PPDU. Figure 8 is a diagram showing the structure of an EHT MU PPDU. Embodiments of the inventive concept may also be applied to 802.11be, which is a next-generation WLAN standard. Therefore, since the method and apparatus for allocating RUs according to embodiments of the inventive concept may be implemented in a signaling field (e.g., an Extremely High Throughput (EHT)-SIG field) of an EHT PPDU, hereinafter, reference is made to Fig.18 and Fig.19 , the EHT PPDU used in the IEEE standard (ie, 802.11be) will be described. For reference, refer to Figure 7 and Figure 8 The EHT PPDU described can be Figure 2 The wireless communication device 1100 is used to generate.

[0101] As in Figure 7 and Figure 8 As shown in , each EHT PPDU may include a preamble and a payload, the preamble includes a plurality of training fields and a plurality of signaling fields, and the payload includes a data field.

[0102] Each EHT PPDU may include an L-STF having a length of 8 μs, an L-LTF having a length of 8 μs, an L-SIG field having a length of 4 μs, a repeated L-SIG (RL-SIG) field having a length of 4 μs, a universal signal (U-SIG) field having a length of 8 μs, an EHT-STF, an EHT-LTF, and a data field.

[0103] Figure 7 The EHT TB PPDU does not include the EHT-SIG field. However, the symbol of the EHT-STF may be repeated. Figure 8 The EHTMU PPDU may consist of multiple OFDM symbols and may also include an EHT-SIG field. Figure 5 The above HE TBPPDU, Figure 7The EHT TB PPDU may require a trigger frame to send the EHT TB PPDU. The trigger frame for sending the EHT TB PPDU may have the same Fig.14 The structure and function of the trigger frame are similar to the structure and function of the trigger frame.

[0104] For example, a PE field may also be included in each EHT PPDU. However, the drawings herein show an EHT PPDU without a PE field.

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

[0106] Since the "L-STF", "L-LTF", "L-SIG field" and "RL-SIG field" of each EHT PPDU are the same as or similar to the "L-STF", "L-LTF", "L-SIG field" and "RL-SIG field" of the above-mentioned HEPPDU, their detailed description will be omitted.

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

[0108] The U-SIG field may include “version-independent fields” and “version-dependent fields”, and the “version-dependent fields” may be arranged adjacent to the “version-independent fields”.

[0109] Here, a "version-independent field" may have a static position and bit definition across different generations / different physical versions.

[0110] In addition, the "version-independent field" may include, for example, the next control information, as follows:

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

[0112] 2) Uplink (UL) flag / Downlink (DL) flag (consisting of one bit)

[0113] 3) BSS Color field as the identifier of the BSS

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

[0115] 5) Bandwidth field (may carry partial "puncturing" information, where a "punctured" subset of frequencies within the bandwidth field are unused frequencies.) Puncturing of frequencies may typically be implemented to avoid interference with another AP using those frequencies.

[0116] On the other hand, the "Release Dependent Field" may have a variable bit definition in each PHY version.

[0117] In addition, the "version-related field" may include the following next control information, for example:

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

[0119] 2) EHT-SIG Modulation and Coding Scheme (MCS) (a field indicating the MCS and provided in the U-SIG field of the EHT PPDU sent to the MU)

[0120] 3) The number of EHT-SIG symbols (a field indicating the number of symbols used for the EHT-SIG field and provided in the U-SIG field of the EHT PPDU transmitted to the MU).

[0121] The U-SIG field may also include various information items other than the above control information, or may not include some of the information in the above control information items. In environments other than the MU environment, some information may be added to the U-SIG field, or some information of the U-SIG field may be omitted.

[0122] The EHT-SIG field, which performs a function similar to that of the HE-SIG-B field of the HE PPDU, may be arranged adjacent to the U-SIG field in the EHT PPDU transmitted to the MU, and may have a variable MCS and a variable length.

[0123] The EHT-SIG field may include a common field and a user-specific field, wherein the common field includes common control information and the user-specific field includes user-specific control information.

[0124] Here, the common field may be encoded separately from the user-specific field. In addition, the common field may include RU allocation related information for downlink transmission (e.g., information including the "RU allocation subfield" and the "additional RU allocation subfield" described later), and the user-specific field may include information similar to that included in the user-specific field of the HE-SIG-B field described above (ie, user information allocated for each RU).

[0125] For example, in a common field of the EHT-SIG field of the EHT PPDU transmitted to the MU, at least one compression mode may be provided in which the 'RU allocation subfield' is not provided. In addition, the EHT-SIG field may be basically used for the PPDU for the MU. However, unlike the 'HE PPDU', when the consumption of the U-SIG field increases, the EHT-SIG field may be used to transmit the PPDU of the SU.

[0126] Fig.9A and Fig. 9B is a diagram showing an example of RUs and their indexes available in a 20 MHz OFDMA PPDU; Fig. 10A and Fig. 10B is a diagram showing an example of RUs and their indexes available in a 40 MHz OFDMA PPDU; Fig.11A and Fig. 11B is a diagram showing an example of RUs and their indexes available in an 80 MHz OFDM APPDU; Fig. 12A and Fig. 12B is a diagram showing an example of indexes of RUs available in a 160 MHz OFDMA PPDU. Fig.13A , Fig. 13B , Fig. 13C , Fig.13D and Fig.13E 320MHz OFDMA PPDU RU index example. Fig.9A , Fig. 10A and Fig.11A As shown in , at least one RU may be arranged in the frequency domain of the data field ( Fig.9A , Fig. 10A and Fig.11A The horizontal axis of each represents the frequency domain). Fig. 9B , Fig. 10B , Fig. 11B , Fig. 12A , Fig. 12B , Fig.13A , Fig. 13B , Fig. 13C , Fig.13D and Fig.13E In the embodiment, a subcarrier index of zero may correspond to a DC-tone, a subcarrier index of negative may correspond to a subcarrier with a frequency lower than DC-tone, and a subcarrier index of positive may correspond to a subcarrier with a frequency higher than DC-tone.

[0127] First, in Fig.9A, the arrangement of RUs available in a 20MHz OFDMA PPDU is shown. In the leftmost band of the 20MHz band, six subcarriers (i.e., subcarriers) may be used as a guard band, and in the rightmost band of the 20MHz band, five subcarriers may be used as a guard band. In addition, 26-subcarrier RUs, 52-subcarrier RUs, and 106-subcarrier RUs may be allocated to other bands. Seven direct current (DC) subcarriers may be inserted into the center band (i.e., the DC band), and a 26-subcarrier RU corresponding to 13 subcarriers may be provided on each of the left and right sides of the DC band. Each RU may be allocated to a receiving device (i.e., a user).

[0128] For example, Fig.9A The RU arrangement can be used for the case for SU as well as for the case for MU. Fig.9A As shown in the uppermost portion of FIG, multiple 26-subcarrier RUs may be arranged, and as shown in FIG. Fig.9A As shown in the lowermost portion of , a 242-subcarrier RU including 242L and 242R may be arranged (in this case, three DC subcarriers may be inserted into the center band).

[0129] exist Fig.9A Various sizes of RUs are suggested in the example of , namely, 26-subcarrier RU, 52-subcarrier RU, 106-subcarrier RU, and 242-subcarrier RU. In other examples, the size of the RU may be different.

[0130] Reference Fig. 9B , can be ordered from the lowest frequency Fig.9A For example, the 26-subcarrier RU may be indexed as the first RU RU1 to the ninth RU RU9, the 52-subcarrier RU may be indexed as the first RU RU1 to the fourth RU RU4, the 106-subcarrier RU may be indexed as the first RU RU1 and the second RU RU2, and the 242-subcarrier RU may be indexed as the first RU RU1. The fifth RU is Fig. 9B The center 26-subcarrier RU in.

[0131] As in Fig. 10A As shown in , the arrangement of RUs available in a 40MHz OFDMA PPDU is shown. In the leftmost band of the 40MHz band, 12 subcarriers (i.e., subcarriers) can be used as guard bands, and in the rightmost band of the 40MHz band, 11 subcarriers can be used as guard bands. In addition, five DC subcarriers can be inserted into the center band (i.e., DC band). In addition, 26-subcarrier RU, 52-subcarrier RU, 106-subcarrier RU, and 242-subcarrier RU can be allocated to other bands. Each RU can be allocated to a receiving device (i.e., a user).

[0132] Note that, Fig. 10A The RU arrangement can be used for the case for SU as well as for the case for MU. Fig. 10A As shown in the lowermost portion of , a 484-subcarrier RU including 484L and 484R may be arranged (in this case, five DC subcarriers may be inserted into the center band).

[0133] exist Fig. 10A Various sizes of RUs are suggested in the example of , namely 26-subcarrier RU, 52-subcarrier RU, 106-subcarrier RU, 242-subcarrier RU and 484-subcarrier RU. In other examples, the size of the RU may be different.

[0134] Reference Fig. 10B , can be ordered from the lowest frequency Fig. 10A For example, a 26-subcarrier RU may be indexed as a first RU RU1 to an 18th RU RU18, a 52-subcarrier RU may be indexed as a first RU RU1 to an eighth RU RU8, a 106-subcarrier RU may be indexed as a first RU RU1 to a fourth RU RU4, a 242-subcarrier RU may be indexed as a first RU RU1 and a second RU RU2, and a 484-subcarrier RU may be indexed as a first RU RU1.

[0135] exist Fig.11A , the arrangement of RUs available in an 80MHz OFDMA PPDU is shown.

[0136] Specifically, in the leftmost band of the 80MHz band, 12 subcarriers (i.e., subcarriers) may be used as a guard band, and in the rightmost band of the 80MHz band, 11 subcarriers may be used as a guard band. In addition, 26-subcarrier RU, 52-subcarrier RU, 106-subcarrier RU, 242-subcarrier RU, and 484-subcarrier RU may be allocated to other frequency bands. Each RU may be allocated to a receiving device (i.e., a user).

[0137] Fig.11A The RU arrangement of can be used in cases involving SU as well as in cases involving MU. Fig.11A As shown in the lowermost part of , a 996-subcarrier RU including 996L and 996R can be arranged (in this case, five DC tones can be inserted into the center frequency band).

[0138] exist Fig.11AVarious sizes of RUs are suggested in the example of FIG, namely, 26-subcarrier RU ("RU26"), 52-subcarrier RU ("RU52"), 106-subcarrier RU ("RU106"), 242-subcarrier RU ("RU242"), 484-subcarrier RU ("RU484"), and 996-subcarrier RU ("RU996"). However, in other embodiments, the RU size may be different.

[0139] Reference Fig. 11B , can be ordered from the lowest frequency Fig.11A For example, the 26-subcarrier RU may be indexed as the first RU RU1 to the thirty-seventh RU RU37, the 52-subcarrier RU may be indexed as the first RU RU1 to the sixteenth RU RU16, the 106-subcarrier RU may be indexed as the first RU RU1 to the eighth RU RU8, the 242-subcarrier RU may be indexed as the first RU RU1 to the fourth RU RU4, the 484-subcarrier RU may be indexed as the first RU RU1 and the second RU RU2, and the 996-subcarrier RU may be indexed as the first RU RU1. The center 26-subcarrier RU may be used in HE (i.e., 802.11ax), but may not be used in EHT (i.e., 802.11be). In some embodiments, as in Fig. 11B As shown in , the center 26-subcarrier RU may be indexed as the nineteenth RU RU19. Therefore, the indexing of RUs in the EHT may be compatible with the indexing of RUs in the HE.

[0140] Reference Fig. 12A and Fig. 12B , the RUs in the 160MHz OFDMA PPDU may be indexed sequentially starting from the lowest frequency. For example, the 26-subcarrier RUs may be indexed as the first RU RU1 to the seventy-fourth RU RU74. Fig. 11B As described above, the center 26-subcarrier RU in the 20 MHz bandwidth may not be used. Fig. 12A The nineteenth RURU19 and the fifty-sixth RU RU56.

[0141] refer to Fig.13A , Fig. 13B , Fig. 13C , Fig.13D and Fig.13E , the RUs in the 320 MHz bandwidth may be indexed sequentially starting from the lowest frequency. For example, the 26-subcarrier RUs may be indexed as the first RU RU1 to the one hundred and forty-eighth RU RU148. Fig. 11BAs described above, the center 26-subcarrier RU in the 20 MHz bandwidth may not be used. Fig.13A and Fig. 13B The nineteenth RU RU19, the fifty-sixth RU RU56, the ninety-third RU RU93 and the one hundred and thirtieth RURU130.

[0142] In some embodiments, the RU positions available in a 40MHz OFDMA PPDU may be the same as two copies of the RU positions available in a 20MHz OFDMA PPDU. In addition, the RU positions available in an 80MHz OFDMA PPDU may be the same as two copies of the RU positions available in a 40MHz OFDMA PPDU. In addition, the RU positions available in a 160MHz OFDMA PPDU may be the same as two copies of the RU positions available in an 80MHz OFDMA PPDU. In addition, the RU positions available in a 320MHz OFDMA PPDU may be the same as two copies of the RU positions available in a 160MHz OFDMA PPDU. Therefore, in the 160MH bandwidth, the 52-subcarrier RU can be indexed as the first RU RU1 to the thirty-second RU RU32, the 106-subcarrier RU can be indexed as the first RU RU1 to the sixteenth RU RU16, the 242-subcarrier RU can be indexed as the first RU RU1 to the eighth RU RU8, the 484-subcarrier RU can be indexed as the first RU RU1 to the fourth RU RU4, and the 996-subcarrier RU can be indexed as the first RU RU1 and the second RU RU2. Similarly, in a 320MHz bandwidth, a 52-subcarrier RU can be indexed as a first RU RU1 to a sixty-fourth RU RU64, a 106-subcarrier RU can be indexed as a first RU RU1 to a thirty-second RU RU32, a 242-subcarrier RU can be indexed as a first RU RU1 to a sixteenth RU RU16, a 484-subcarrier RU can be indexed as a first RU RU1 to an eighth RURU8, and a 996-subcarrier RU can be indexed as a first RU RU1 to a fourth RU RU4.

[0143] As described above, at least one RU may be differently arranged in the frequency domain of the data field.

[0144] Fig.14 is a diagram showing the structure of a trigger frame. For example, when UL transmission to an AP is to be performed by one or more STAs, the AP may allocate different frequency resources as UL transmission resources to the one or more STAs based on OFDMA. Here, an example of a frequency resource is an RU, which may be indicated by a trigger frame sent by the AP to the STA before the UL transmission.

[0145] Therefore, in order to send Figure 5 HE TB PPDU or Figure 7 The EHT TB PPDU is first sent to the STA as follows Fig.14 The trigger frame shown. The trigger frame can set the uplink bandwidth and allocate RUs to UL multi-user transmission. The trigger frame can be formed by a MAC (Media Access Control) frame and can be included in the PPDU.

[0146] Available through Figures 3 to 8 The trigger frame is sent by using the PPDU shown or a PPDU specially designed for the corresponding trigger frame. Figures 3 to 8 When the illustrated PPDU sends a trigger frame, the trigger frame may be included in the data field.

[0147] As in Fig.14 As shown in , the trigger frame may include a frame control field 400 (2 octets), a duration field 405 (2 octets), an RA (receive address) field 410 (6 octets), a TA (transmit address) field 415 (6 octets), a common information field 420 (not less than 8 octets), individual user information fields 425-1 to individual user information fields 425-N (N is a natural number of 1 or greater, and each information field is 5 or more octets), a padding field 430 and a frame check sequence (FCS) field 435 (not less than 4 octets).

[0148] The frame control field 400 may include information about the version of the MAC protocol and other additional control information items. The duration field 405 may include time information for setting a network allocation vector (NAV) or information about an identifier of a terminal (e.g., an association ID (AID)). The RA field 410 may include address information of a receiving device of a corresponding trigger frame and may be omitted when unnecessary. The TA field 415 may include address information of a transmitting device that transmits a corresponding trigger frame.

[0149] The TA field 415 may include a field indicating the length of the L-SIG field of the UL PPDU transmitted to the corresponding trigger frame or information controlling the content of the SIG-A field (that is, the HE-SIG-A field) of the UL PPDU transmitted to the corresponding trigger frame. In addition, the TA field 415 may include information about the length of the CP of the UL PPDU transmitted to the corresponding trigger frame or information about the length of the LTF field as common control information.

[0150] The common information field 420 may include common information of a receiving device (e.g., STA) for receiving the corresponding trigger frame. The trigger frame may include individual user information fields 425-1 to 425-N (N is a natural number not less than 1) corresponding to the number of receiving devices receiving the trigger frame. For reference, the individual user information field may be referred to as a "user information list field". The trigger frame may include a padding field 430 and an FCS field 435.

[0151] In other examples, some fields of the trigger frame may be omitted, and other fields may be added. In addition, the length of each field may be different from the length shown.

[0152] Embodiments of the inventive concept relate to a method and apparatus for supporting MU communication using OFDMA. An AP may allocate at least one RU to at least one of a plurality of receiving devices (e.g., STAs) in an extended bandwidth through OFDMA. A method and apparatus for providing a trigger frame including information about an uplink bandwidth and at least one RU allocated to a receiving device will be described later. In addition, a method and apparatus for identifying an uplink bandwidth and at least one RU allocated from a trigger frame will be described. For example, as later referred to Fig.17 As described, the AP may allocate at least one RU to at least one STA, generate a trigger frame for uplink transmission, and send the generated trigger frame to the at least one STA. The STA may receive a trigger frame from the AP, identify at least one RU for uplink OFDMA allocated to the STA, and send data (e.g., PPDU) to the AP based on the identified at least one RU. However, an embodiment of the present invention may be applied to a case where a STA sends data to another STA and a case where an AP sends data to a STA. In addition, an embodiment of the present invention may be applied to a case where a single RU and downlink OFDMA and uplink OFDMA are supported. Information about the uplink bandwidth and the RU allocated to the receiving device may be provided to the receiving device through the common information field 420 and the user information field of the trigger frame. In the following, reference will be made to Fig.15 , Fig.16A and Fig. 16B The common information field 420 and the user information field are described.

[0153] Fig.15 is a diagram illustrating an example of a common information field, wherein the common information field contains information commonly applicable to a plurality of STAs. Fig.16A and Fig. 16B is a diagram showing an example of each user information field.

[0154] Reference Fig.15, the common information field may include a subfield sequence from the first subfield 151 to the last subfield 168. The STA may set the value of the uplink bandwidth subfield 420_1 in the multiple subfields included in the common information field, and the STA may identify the uplink bandwidth based on the value of the uplink bandwidth subfield 420_1. The uplink bandwidth subfield 420_1 may have a length L1 for defining various uplink bandwidths. For example, the length L1 of the uplink bandwidth subfield 420_1 in the HE may be 2 bits to indicate one of 20MHz, 40MHz, 80MHz, and 160MHz. In the EHT, the length L1 of the uplink bandwidth subfield 420_1 may be at least 3 bits to indicate one of the four bandwidths supported by the HE and an extended bandwidth (e.g., a bandwidth of up to 320MHz). Here, unless otherwise specified, the uplink bandwidth may be simply referred to as bandwidth. In other examples, the common information field includes Fig.15 Field(s) not shown in and / or may be omitted from the common information fields Fig.15 At least one field shown in .

[0155] Reference Fig.16A , a first example of a user information field may include subfields such as an AID12 field 425_1a and an RU allocation subfield 425_2a. In order to specify an STA, the AP may set a value of the AID12 field 425_1a, and the STA may recognize that the user information field is a user information field of the STA based on the value of the AID12 field 425_1a. In addition, in order to define at least one allocated RU, the AP may set a value of the RU allocation subfield 425_2a, and the STA may recognize the at least one RU allocated to the STA based on the value of the RU allocation subfield 425_2a.

[0156] The RU allocation subfield 425_2a may have a length L2a for defining various RU allocations. For example, the length L2a of the RU allocation subfield 425_2a in the HE may be 8 bits to indicate a single RU that can be allocated to the STA within a bandwidth of up to 160 MHz. However, in the EHT, the RU allocation subfield 425_2a may indicate not only a single RU that can be allocated to the STA within a bandwidth of up to 320 MHz, but also multiple RUs, and therefore, the length of the RU allocation subfield 426_2a may be longer than at least 8 bits. As will be described later, Fig.28A As described, the RU allocation subfield 425_2a for EHT may have a length of 9 bits.

[0157] Reference Fig. 16B, the user information field may include multiple subfields, wherein the multiple subfields include the AID12 field 425_1b and the RU allocation subfield 425_2b. Fig. 16B As shown in FIG, the user information field may also include a PS160 subfield 425_3 indicating a primary subband or a secondary subband. Fig. 16B is shown as Fig.16A The PS160 subfield 425_3 may correspond to a reserved area (eg, B39) of the user information field, but in other examples, the PS160 subfield 425_3 may be arranged in the same Fig. 16B The positions shown are different positions.

[0158] As will be referred to later Fig.28B As described above, the PS160 subfield 425_3 can be used together with the RU allocation subfield 425_2b to define various RU allocations. Therefore, the length L2b of the RU allocation subfield 425_2b is comparable to Fig.16A The length L2a of the RU allocation subfield 425_2b may be shorter. For example, the length L2b of the RU allocation subfield 425_2b may be 8 bits. In order to define at least one allocated RU, the AP may set the values ​​of the RU allocation subfield 425_2b and the PS160 subfield 425_3, and the STA may identify the at least one RU allocated to the STA based on the values ​​of the RU allocation subfield 425_2b and the PS160 subfield 425_3. Fig.17 is a message flow diagram illustrating a communication method based on extended bandwidth and multi-RU according to an embodiment. Fig.17 An example of operations of the AP 10 and the STA 20 communicating with each other is shown. The AP 10 may communicate with at least one STA including the STA 20 included in the coverage area.

[0159] Reference Fig.17 In operation S10, the AP 10 may generate an uplink bandwidth field. For example, the AP 10 may determine a bandwidth to be used by at least one STA including the STA 20 in uplink transmission. Fig.15 As described, in the EHT, the uplink bandwidth field may have a length of at least 3 bits, and the AP 10 may determine a bandwidth of one of 20 MHz, 40 MHz, 80 MHz, 160 MHz, and 320 MHz and set the uplink bandwidth field to a value corresponding to the determined bandwidth.

[0160] In operation S20, the AP 10 may allocate at least one RU to at least one STA. For example, the AP 10 may allocate a single RU to the STA 20, or may allocate multiple RUs to the STA 20. For EHT, the AP 10 may allocate a single RU to the STA 20 in the same manner as in the HE. Figures 18 to 25C An example is described in which the AP 10 allocates multiple RUs to the STA 20 in a given bandwidth in the EHT.

[0161] In operation S30, the AP 10 may generate at least one subfield. For example, the AP 10 may generate at least one subfield included in the trigger frame based on the at least one RU allocated in operation S20. Fig.16A As described above, the RU allocation subfield in the EHT may have a length of at least 9 bits, and in operation S30, the AP 10 may set the RU allocation subfield to a value corresponding to the at least one RU allocated. Fig. 16B As described above, the RU allocation subfield in the EHT may have a length of 8 bits, the user information field may include a PS160 subfield, and in operation S30, the AP 10 may set the RU allocation subfield and the PS160 subfield to a value corresponding to the at least one RU allocated. Fig.26 An example of operation S30 is described.

[0162] In operation S40, the AP 10 may generate a trigger frame and a PPDU. For example, the AP 10 may generate a common information field including the uplink bandwidth field generated in operation S10 and a user information field including the at least one subfield generated in operation S30. The AP 10 may generate a trigger frame including the common information field and the user information field, and may generate a PPDU including the trigger frame.

[0163] In operation S50, the AP 10 may transmit the PPDU, and the STA 20 may receive the PPDU. In operation S60, the STA 20 may extract the trigger frame. The STA 20 may extract the trigger frame from the PPDU received in operation S50.

[0164] In operation S70, STA 20 may extract the uplink bandwidth field and the at least one subfield. STA 20 may extract the common information field and the user information field from the trigger frame extracted in operation S60. STA 20 may extract the uplink bandwidth field having a length of at least 3 bits from the common information field, identify the user information field of STA 20 based on the AID12 field, and extract the at least one subfield from the identified user information field.

[0165] In operation S80, the STA 20 may identify the at least one RU. The STA 20 may identify the bandwidth based on the uplink bandwidth field extracted in operation S70, and identify the at least one RU allocated to the STA 20 based on the identified bandwidth and the at least one subfield extracted in operation S70. Fig. 27 An example of operation S80 is described.

[0166] In operation S90, the STA 20 may transmit the PPDU and the AP 10 may receive the PPDU. The STA 20 may perform uplink transmission on the at least one RU identified in operation S80 and may transmit the PPDU to the STA 20. The AP 10 may receive the PPDU on the at least one RU allocated to the STA 20 within the bandwidth.

[0167] Fig.18 1 shows a small multi-RU that can be allocated to a STA in an OFDMA 20MHz EHT PPDU according to an embodiment. Specifically, Fig.18 The table shows the index and combination of small multi-RUs that can be allocated in a bandwidth of 20 MHz. Fig.29A and Fig.29B As described, the value of the RU Allocation subfield may be as described in Fig.18 The order of the indices shown is increasing. Fig.18 In the example, the index of a single RU can be Fig. 9B The indexes shown in correspondence.

[0168] Reference Fig.18 , a multi-RU including a 52-subcarrier RU and a 26-subcarrier RU may have three different combinations and may be indexed as a first multi-RU MRU1 to a third multi-RU MRU3. Fig.18 As shown in , the first multi-RU MRU1 may include a second 52-subcarrier RU and a second 26-subcarrier RU, the second multi-RU MRU2 may include a second 52-subcarrier RU and a fifth 26-subcarrier RU, and the third multi-RU MRU3 may include a third 52-subcarrier RU and an eighth 26-subcarrier RU.

[0169] A multi-RU including a 106-subcarrier RU and a 26-subcarrier RU may have two different combinations and may be indexed as a first multi-RU MRU1 and a second multi-RU MRU2. Fig.18 As shown in FIG, a first multi-RU MRU1 may include a first 106-subcarrier RU and a fifth 26-subcarrier RU, and a second multi-RU MRU2 may include a second 106-subcarrier RU and a fifth 26-subcarrier RU.

[0170] Fig.19 1 shows a small multi-RU that can be allocated to a STA in an OFDMA 40MHz EHT PPDU according to an embodiment. Specifically, Fig.19 The table shows the index and combination of small multi-RUs that can be allocated in a bandwidth of 40 MHz. In some embodiments, as later referred to Fig.29A and Fig.29B As described, the value of the RU allocation subfield can be Fig.19 The indices are shown in increasing order. Fig.19 In the example, the index of a single RU can be Fig. 10B The indices shown correspond.

[0171] Reference Fig.19 , a multi-RU including a 52-subcarrier RU and a 26-subcarrier RU may have six different combinations and may be indexed as a first multi-RU MRU1 to a sixth multi-RU MRU6. Fig.19 As shown, the first multi-RU MRU1 may include a second 52-subcarrier RU and a second 26-subcarrier RU, the second multi-RU MRU2 may include a second 52-subcarrier RU and a fifth 26-subcarrier RU, the third multi-RU MRU3 may include a third 52-subcarrier RU and an eighth 26-subcarrier RU, the fourth multi-RU MRU4 may include a sixth 52-subcarrier RU and an eleventh 26-subcarrier RU, the fifth multi-RU MRU5 may include a sixth 52-subcarrier RU and a fourteenth 26-subcarrier RU, and the sixth multi-RU MRU6 may include a seventh 52-subcarrier RU and a seventeenth 26-subcarrier RU.

[0172] The multi-RU including a 106-subcarrier RU and a 26-subcarrier RU may have four different combinations and may be indexed as a first multi-RU MRU1 to a fourth multi-RU MRU4. Fig.19 As shown, the first multi-RU MRU1 may include a first 106-subcarrier RU and a fifth 26-subcarrier RU, the second multi-RU MRU2 may include a second 106-subcarrier RU and a fifth 26-subcarrier RU, the third multi-RU MRU3 may include a third 106-subcarrier RU and a fourteenth 26-subcarrier RU, and the fourth multi-RU MRU4 may include a fourth 106-subcarrier RU and a fourteenth 26-subcarrier RU.

[0173] Fig. 20 1 shows a small multi-RU that can be allocated to a STA in an OFDMA 80MHz EHT PPDU according to an embodiment. Specifically, Fig. 20 The table shows the index and combination of small multi-RUs that can be allocated in the bandwidth of 80MHz. In some embodiments, as later referred to Fig.29A and Fig.29B As described, the value of the RU allocation subfield can be Fig. 20 The order of the indices shown is increasing. Fig. 20 In the example, the index of a single RU can be Fig. 11B The indices shown correspond.

[0174] Reference Fig. 20 , a multi-RU including a 52-subcarrier RU and a 26-subcarrier RU may have 12 different combinations and may be indexed as a first multi-RU MRU1 to a twelfth multi-RU MRU12. Fig. 20 As shown, the first multi-RU MRU1 may include a second 52-subcarrier RU and a second 26-subcarrier RU, the second multi-RU MRU2 may include a second 52-subcarrier RU and a fifth 26-subcarrier RU, the third multi-RU MRU3 may include a third 52-subcarrier RU and an eighth 26-subcarrier RU, the fourth multi-RU MRU4 may include a sixth 52-subcarrier RU and an eleventh 26-subcarrier RU, the fifth multi-RU MRU5 may include a sixth 52-subcarrier RU and a fourteenth 26-subcarrier RU, and the sixth multi-RU MRU6 may include a seventh 52-subcarrier RU and a seventeenth 26-subcarrier RU. In addition, the seventh multi-RU MRU7 may include the tenth 52-subcarrier RU and the twenty-first 26-subcarrier RU, the eighth multi-RU MRU8 may include the tenth 52-subcarrier RU and the twenty-fourth 26-subcarrier RU, the ninth multi-RU MRU9 may include the eleventh 52-subcarrier RU and the twenty-seventh 26-subcarrier RU, the tenth multi-RU MRU10 may include the fourteenth 52-subcarrier RU and the thirtieth 26-subcarrier RU, the eleventh multi-RU MRU11 may include the fourteenth 52-subcarrier RU and the thirty-third 26-subcarrier RU, and the twelfth multi-RU MRU6 may include the fifteenth 52-subcarrier RU and the thirty-sixth 26-subcarrier RU.

[0175] A multi-RU including a 106-subcarrier RU and a 26-subcarrier RU may have eight different combinations and may be indexed as a first multi-RU MRU1 to an eighth multi-RU MRU8. Fig.19As shown, the first multi-RU MRU1 may include the first 106-subcarrier RU and the fifth 26-subcarrier RU, the second multi-RU MRU2 may include the second 106-subcarrier RU and the fifth 26-subcarrier RU, the third multi-RU MRU3 may include the third 106-subcarrier RU and the fourteenth 26-subcarrier RU, and the fourth multi-RU MRU4 may include the fourth 106-subcarrier RU and the fourteenth 26-subcarrier RU. In addition, the fifth multi-RU MRU5 may include the fifth 106-subcarrier RU and the twenty-fourth 26-subcarrier RU, the sixth multi-RU MRU6 may include the sixth 106-subcarrier RU and the twenty-fourth 26-subcarrier RU, the seventh multi-RU MRU7 may include the seventh 106-subcarrier RU and the thirty-third 26-subcarrier RU, and the eighth multi-RU MRU8 may include the eighth 106-subcarrier RU and the thirty-third 26-subcarrier RU.

[0176] Like a multi-RU including one 52-subcarrier RU and one 26-subcarrier RU and a multi-RU including one 106-subcarrier RU and one 26-subcarrier RU, a multi-RU including only small RUs (i.e., 26-subcarrier RU, 52-subcarrier RU, and 106-subcarrier RU) may be referred to as a small multi-RU. In some embodiments, only some of the small multi-RUs may be used in a bandwidth equal to or greater than 80 MHz. For example, Fig. 20 As shown, some of the multi-RUs including a 52-subcarrier RU and a 26-subcarrier RU (i.e., MRU1, MRU6, MRU7, and MRU12) and some of the multi-RUs including a 106-subcarrier RU and a 26-subcarrier RU (i.e., MRU2, MRU3, MRU6, and MRU7) may not be used in a bandwidth equal to or greater than 80 MHz.

[0177] Fig.21A and Fig.21B 1 shows a small multi-RU that can be allocated to a STA in an OFDMA 160MHz EHT PPDU according to an embodiment. Specifically, Fig.21A and Fig.21B The table shows the index and combination of small multi-RUs that can be allocated in the bandwidth of 160MHz. In some embodiments, as later referred to Fig.29A and Fig.29B As described, the value of the RU allocation subfield can be Fig.21A and Fig.21B The indexes are shown in increasing order.

[0178] Reference Fig.21A, a multi-RU including a 52-subcarrier RU and a 26-subcarrier RU may have 24 different combinations and may be indexed as a first multi-RU MRU1 to a twenty-fourth multi-RU MRU24. Fig.21B , a multi-RU including a 106-subcarrier RU and a 26-subcarrier RU may have 16 different combinations and may be indexed as a first multi-RU MRU1 to a sixteenth multi-RU MRU16.

[0179] Fig.22A , Fig. 22B and Fig. 22C 1 shows a small multi-RU that can be allocated to a STA in an OFDMA 320MHz EHT PPDU according to an embodiment. Specifically, Fig.22A , Fig. 22B and Fig. 22C The table shows the index and combination of small multi-RUs that can be allocated in the bandwidth of 320MHz. In some embodiments, as later referred to Fig.29A and Fig.29B As described, the value of the RU allocation subfield can be Fig.22A , Fig. 22B and Fig. 22C The indices are shown in increasing order.

[0180] Reference Fig.22A and Fig. 22B , a multi-RU including a 52-subcarrier RU and a 26-subcarrier RU may have 48 different combinations and may be indexed as a first multi-RU MRU1 to a forty-eighth multi-RU MRU48. Fig. 22C , a multi-RU including a 106-subcarrier RU and a 26-subcarrier RU may have 32 different combinations and may be indexed as a first multi-RU MRU1 to a thirty-second multi-RU MRU32.

[0181] Fig.23 1 shows a large multi-RU that can be allocated to a STA in an OFDMA 80MHz EHT PPDU according to an embodiment. Specifically, Fig.23 The table shows the index and combination of large multi-RUs that can be allocated in the bandwidth of 80MHz. In some embodiments, as later referred to Fig.29A and Fig.29B As described, the value of the RU allocation subfield can be Fig.23 The indexes are shown in increasing order.

[0182] Reference Fig.23 , a multi-RU including a 484-subcarrier RU and a 242-subcarrier RU may have four different combinations and may be indexed as a first multi-RU MRU1 to a fourth multi-RU MRU4.

[0183] Fig.24 1 shows a large multi-RU that can be allocated to a STA in an OFDMA 160MHz EHT PPDU according to an embodiment. Specifically, Fig.24 The table shows the index and combination of large multi-RUs that can be allocated in a bandwidth of 160 MHz. In some embodiments, as later referred to Fig.29A and 29B As described, the value of the RU allocation subfield can be Fig.24 The order of the indices shown in is increasing.

[0184] Reference Fig.24 , a multi-RU including one 484-subcarrier RU and one 242-subcarrier RU may have eight different combinations and may be indexed as a first multi-RU MRU1 to an eighth multi-RU MRU8. In a bandwidth of 160 MHz, four 484-subcarrier RUs may be arranged sequentially, and eight 242-subcarrier RUs may be arranged sequentially. Fig.24 As shown, the first to eighth multi-RUs may respectively correspond to combinations of eight 242-subcarrier RUs that are not allocated in sequence.

[0185] A multi-RU including one 996-subcarrier RU and one 484-subcarrier RU may have four different combinations and may be indexed as a first RU MRU1 to a fourth multi-RU MRU4. In a bandwidth of 160 MHz, two 996-subcarrier RUs may be arranged sequentially, and four 484-subcarrier RUs may be arranged sequentially. Fig.24 As shown, the first to fourth multi-RUs MRU1 to MRU4 may respectively correspond to combinations of four 484-subcarrier RUs that are not allocated in sequence.

[0186] A multi-RU including one 996-subcarrier RU, one 484-subcarrier RU, and one 242-subcarrier RU may have eight different combinations and may be indexed as a first multi-RU MRU1 to an eighth multi-RU MRU8. In a bandwidth of 160 MHz, two 996-subcarrier RUs may be arranged sequentially, four 484-subcarrier RUs may be arranged sequentially, and eight 242-subcarrier RUs may be arranged sequentially. Fig.24 As shown, the first multi-RU MRU1 to the eighth multi-RU MRU8 may respectively correspond to combinations of eight 242-subcarrier RUs that are not allocated in sequence.

[0187] Fig.25A , Fig.25B and Fig.25C1 shows a large multi-RU that can be allocated to a STA in an OFDMA 320MHz EHT PPDU according to an embodiment. Specifically, Fig.25A , Fig.25B and Fig.25C A separate table is shown for illustrative purposes, and Fig.25A , Fig.25B and Fig.25C The table shows the index and combination of large multi-RUs that can be allocated in the bandwidth of 320MHz. In some embodiments, as later referred to Fig.29A and 29B As described, the value of the RU allocation subfield can be Fig.25A , Fig.25B and Fig.25C The order of the indices shown in is increasing.

[0188] Reference Fig.25A , a multi-RU including one 484-subcarrier RU and one 242-subcarrier RU may have 16 different combinations and may be indexed as a first multi-RU MRU1 to a sixteenth multi-RU MRU16. In a bandwidth of 320 MHz, eight 484-subcarrier RUs may be arranged sequentially, and sixteen 242-subcarrier RUs may be arranged sequentially. Fig.25A As shown, the first to sixteenth multi-RUs may respectively correspond to combinations of sixteen 242-subcarrier RUs that are not allocated in sequence.

[0189] A multi-RU including one 996-subcarrier RU and one 484-subcarrier RU may have eight different combinations and may be indexed as a first multi-RU MRU1 to an eighth multi-RU MRU8. In a bandwidth of 320 MHz, four 996-subcarrier RUs may be arranged sequentially, and eight 484-subcarrier RUs may be arranged sequentially. Fig.25A As shown, the first multi-RU MRU1 to the eighth multi-RU MRU8 may respectively correspond to combinations of eight 484-subcarrier RUs that are not allocated in sequence.

[0190] Reference Fig.25B , a multi-RU including one 996-subcarrier RU, one 484-subcarrier RU, and one 242-subcarrier RU may have 16 different combinations and are indexed as a first multi-RU MRU1 to a sixteenth multi-RU MRU16. In a bandwidth of 320 MHz, four 996-subcarrier RUs may be arranged sequentially, eight 484-subcarrier RUs may be arranged sequentially, and sixteen 242-subcarrier RUs may be arranged sequentially. Fig.25BAs shown, the first multi-RU MRU1 to the sixteenth multi-RU MRU16 may respectively correspond to combinations of sixteen 242-subcarrier RUs that are not allocated in sequence.

[0191] The multi-RU including two 996-subcarrier RUs and one 484-subcarrier RU may have 12 different combinations and may be indexed as the first to the twelfth multi-RU MRU1 to the twelfth multi-RU MRU12. In a bandwidth of 320 MHz, the first to the fourth 996-subcarrier RUs may be arranged sequentially, and the first to the eighth 484-subcarrier RUs may be arranged sequentially. Fig.25B As shown, the first multi-RU MRU1 to the fifth multi-RU MRU6 may correspond to the combination of the first 484-subcarrier RU to the sixth 484-subcarrier RU that are not allocated in sequence, respectively, while the fourth 996-subcarrier RU is not allocated. In addition, the seventh multi-RU MRU7 to the twelfth multi-RU MRU12 may correspond to the combination of the third 484-subcarrier RU to the eighth 484-subcarrier RU that are not allocated in sequence, respectively, while the first 996-subcarrier RU is not allocated.

[0192] Reference Fig.25C , a multi-RU including three 996-subcarrier RUs may have four different combinations and may be indexed as a first RU MRU1 to a fourth multi-RU MRU4. In a 320 MHz bandwidth, four 996-subcarrier RUs may be arranged sequentially, and as Fig.25C As shown, the first to fourth multi-RUs MRU1 to MRU4 may respectively correspond to combinations of four 996-subcarrier RUs that are not allocated in sequence.

[0193] A multi-RU including three 996-subcarrier RUs and one 484-subcarrier RU may have 8 different combinations and may be indexed as a first multi-RU MRU1 to an eighth multi-RU MRU8. In a 320 MHz bandwidth, four 996-subcarrier RUs may be arranged sequentially, and eight 484-subcarrier RUs may be arranged sequentially. Fig.25C As shown, the first multi-RU MRU1 to the eighth multi-RU MRU8 may respectively correspond to combinations of eight 484-subcarrier RUs that are not allocated in sequence.

[0194] In EHT, the user information field can define not only a single RU of HE, but also Figures 18 to 25C Hereinafter, an example of defining a user information field of a single RU and a multi-RU in an extended bandwidth of an EHT will be described.

[0195] Fig.26is a flow chart showing a communication method based on extended bandwidth and multiple RUs according to an embodiment. Specifically, Fig.26 Show Fig.17 As shown above with reference to the example of operation S30. Fig.17 As described, the AP 10 may be Fig.26 At least one subfield is generated in operation S30' of . Nine bits or more bits included in the user information field may be used to define at least one RU allocated in the EHT. Fig.16A As described above, the RU allocation subfield may have a length of 9 bits, and the 9 bits may include a first group of 7 bits and a second group of 2 bits to be described later. Fig. 16B As described above, the RU allocation subfield may have a length of 8 bits, and the 8 bits may include at least 7 bits to be described later. A group of at least 2 bits to be described later may include one bit of the RU allocation subfield and one bit of the PS160 subfield. Fig.26 As shown, operation S30′ may include referring to Fig.17 A plurality of operations S31 to S37 are described.

[0196] Reference Fig.26 In operation S31, the AP 10 may set "K" bits, where K is at least 7 and the K bits are associated with at least one RU. Fig.17 The K bits of the RU allocation subfield associated with the at least one RU allocated to the STA 20 in operation S20. The at least one RU may be defined in a subband having only K bits, or may be defined based on at least one bit of M bits (where M is at least 2) described later and K bits. The M bits of the user information field may be set in operations after operation S31 (i.e., S32 to S37).

[0197] In operation S32, the AP 10 may determine whether the bandwidth corresponds to two subbands. Here, the subband may refer to the smallest frequency band (i.e., the frequency band including the channel) including the at least one RU allocated to the STA 20, and may have a width of, for example, 80 MHz, 160 MHz, or 320 MHz. Here, the width of the subband may be simply referred to as a subband. Therefore, the case where the bandwidth corresponds to two subbands in the EHT may include a case where the subband is 80 MHz in a bandwidth of 160 MHz and a case where the subband is 160 MHz in a bandwidth of 320 MHz. When the bandwidth includes multiple subbands, the multiple subbands may include a primary subband and at least one secondary subband. Management and control information may be sent in the primary subband, but management and control information may not be sent in the secondary subband.

[0198] When the bandwidth corresponds to two subbands, in operation S33, the AP 10 may set one bit to a value defining a subband including at least one RU, and in operation S34, the AP 10 may set another bit associated with the at least one RU. That is, one bit of the M=2 bits of the user information field may represent one subband of the two subbands, and another bit of the M=2 bits may define the at least one RU together with the K bits. (Since the K bits and the M bits jointly define the at least one RU, each of the K bits and the M bits is associated with the at least one RU.)

[0199] When the bandwidth does not correspond to two subbands, the AP 10 may determine whether the bandwidth corresponds to four or more subbands in operation S35. For example, a case where the bandwidth corresponds to four subbands in EHT may include a case where the subband is 80 MHz in a bandwidth of 320 MHz.

[0200] When the bandwidth includes four or more subbands, in operation S36, the AP 10 may set M bits to a value defining a subband including at least one RU. For example, the value may be a decimal value defined by a binary sequence of M bits. Thus, the M bits of the user information field may define one of four or more subbands including at least one RU partially defined by the K bits set in operation S31.

[0201] When the bandwidth does not include four or more subbands, for example, when the bandwidth includes a single subband, in operation S37, the AP10 may set M bits associated with the at least one RU. For example, the case where the bandwidth includes a single subband in the EHT includes a case where the bandwidth is 20 MHz, 40 MHz, or 80 MHz, a case where the subband is 160 MHz in a bandwidth of 160 MHz, and a case where the subband is 320 MHz in a bandwidth of 320 MHz.

[0202] Fig. 27 is a flow chart showing a communication method based on extended bandwidth and multiple RUs according to an embodiment. Specifically, Fig. 27 Show Fig.17 As shown above with reference to the example of operation S80. Fig.17 As described in Fig. 27 In operation S80', STA 20 may identify at least one RU assigned to STA 20. In some embodiments, as described above with reference to Fig.16A As described above, the RU allocation subfield may have a length of 9 bits, and the 9 bits may include at least 7 bits and at least 2 bits described below. In addition, in some embodiments, as described above with reference to Fig. 16BAs described above, the RU allocation subfield may have a length of 8 bits, and the 8 bits may include at least 7 bits to be described later. The at least 2 bits to be described later may include one bit of the RU allocation subfield and one bit of the PS160 subfield. Fig. 27 As shown, operation S80' may include a plurality of operations S81 to S87. Fig. 27 of Fig.26 The description of the duplicate description and will refer to Fig.17 describe Fig.26 .

[0203] Reference Fig. 27 , in operation S81, STA20 may identify at least one RU based on K (at least 7) ​​bits. STA20 may identify at least one RU defined in a subband having only K bits, and may identify at least one RU based on at least one bit of M (at least 2) bits and K bits to be described later. K bits of the user information field may be analyzed in operations after operation S81 (ie, S82 to S87).

[0204] In operation S82, STA 20 may determine whether the bandwidth corresponds to two subbands. When the bandwidth corresponds to two subbands, in operation S83, STA 20 may identify the subband including the at least one RU based on one bit among the M bits, and in operation S84, STA 20 may identify the at least one RU based on the other bits among the M bits. Hereinafter, an example in which M is equal to 2 is described.

[0205] When the bandwidth does not correspond to two subbands, in operation S85, the STA 20 may determine whether the bandwidth corresponds to four or more subbands. When the bandwidth includes four or more subbands, in operation S86, the STA 20 may identify the subband including the at least one RU based on M bits. When the bandwidth does not include four or more subbands, in operation S87, the STA 20 may identify the at least one RU based on M bits.

[0206] Fig.28A and Fig.28B is a diagram illustrating an example of a user information field according to an example embodiment. Specifically, Fig.28A shows an example of the RU allocation subfield included in the user information field, and Fig.28B An example of a user information field including a RU allocation subfield and a PS160 subfield is shown.

[0207] Reference Fig.28A , the RU allocation subfield may include 9 bits, namely, the first bit X0 to the ninth bit X8. The third bit X2 to the ninth bit X8 may be Fig.26and Fig. 27 At least 7 bits of the corresponding, and the first bit X0 and the second bit X1 can be Fig.26 and Fig. 27 In some embodiments, Fig.26 and Fig. 27 The at least 2 bits may include Fig.28A The RU Allocation subfield is shown as the least significant bit (LSB) and may include the most significant bit (MSB) or the same as Fig.28A Shown variously include both the LSB and the MSB.

[0208] Reference Fig.28A , as mentioned above Fig.26 and Fig. 27 As described above, when the bandwidth includes multiple sub-bands, the first bit X0 and / or the second bit X1 may define one of the multiple sub-bands. Fig.28A As shown in the first table T1, when the sub-band is 80MHz in the bandwidth of 160MHz, the second bit X1 may define the lower 80MHz or the upper 80MHz, and when the sub-band is 80MHz in the bandwidth of 320MHz, the first bit X0 and the second bit X1 may define one of the lower 80MHz and the upper 80MHz in the lower 160MHz and the lower 80MHz and the upper 80MHz in the upper 160MHz. Therefore, the second bit X1 of the RU allocation subfield defining at least one RU allocated to the primary 80MHz in the 160MHz bandwidth may correspond to "0", and the second bit X1 of the RU allocation subfield defining at least one RU allocated to the secondary 80MHz may correspond to "1".

[0209] Fig.28A The second table T2 represents the values ​​of the first bit X0 and the second bit X1 for indicating at least one RU allocated to each 80 MHz according to the position of the main 160 MHz and / or the main 80 MHz in the bandwidth of 320 MHz. In the bandwidth of 160 MHz, the first bit X0 may be zero, and Fig.28A The third table T3 represents the value of the second bit X1, which is used to indicate at least one RU allocated to each 80 MHz according to the position of the main 80 MHz in the bandwidth of 160 MHz. In a bandwidth of 80 MHz or less, the first bit X0 and the second bit X1 may be zero.

[0210] Reference Fig.28B In some embodiments, the user information field may include an 8-bit RU allocation subfield and a 1-bit PS160 subfield. Fig.28BAs shown, the RU allocation subfield may include the first bit B0 to the eighth bit B7, and the PS160 subfield may include the bit Bx. In some embodiments, the second bit B1 to the eighth bit B7 of the RU allocation subfield may be Fig.26 and Fig. 27 The first bit B0 of the RU allocation subfield and the bit Bx of the PS160 subfield can correspond to at least 7 bits of the RU allocation subfield. Fig.26 and Fig. 27 In some embodiments, the first bit B0 of the RU allocation subfield may be as follows: Fig.28B The LSB of the RU Allocation subfield is shown, or may be the same as Fig.28B The different MSBs are shown.

[0211] Reference Fig.28B , as mentioned above Fig.26 and Fig. 27 As described, when the bandwidth includes multiple subbands, the first bit B0 of the RU allocation subfield and the bit Bx of the PS160 subfield may define one subband among the multiple subbands. In some embodiments, the first bit B0 of the RU allocation subfield may indicate the primary 80MHz or secondary 80MHz for single RU and / or multiple RUs of 80MHz or less in the primary 160MHz. In addition, the first bit B0 of the RU allocation subfield may be used to index multiple RUs for single RU and / or multiple RUs greater than 80MHz. The bit Bx of the PS160 subfield may indicate the primary 160MHz or secondary 160MHz for single RU and / or multiple RUs of 160MHz or less. In addition, the bit Bx of the PS160 subfield may be used to index multiple RUs for single RU and / or multiple RUs greater than 160MHz. Therefore, Fig.28A The first bit X0 and the second bit X1 can be determined according to Fig.28B The conditions defined by the pseudo-code (CD) are derived from the first bit B0 of the RU allocation subfield and the bit Bx of the PS160 subfield.

[0212] Fig.28B The fourth table T4 represents the positions of the main 160MHz and / or main 80MHz in the 320MHz bandwidth, respectively calculated according to the first bit B0 of the RU allocation subfield and the bit Bx of the PS160 subfield. Fig.28A The value of the first bit X0 and the second bit X1. Fig.28B As shown, when the secondary 80 MHz, primary 80 MHz, and secondary 160 MHz are arranged in order ([S80P80 S160]), Fig.28A The first bit X0 of the PS160 subfield may be the same as bit Bx of the PS160 subfield, and Fig.28AThe second bit X1 of the RU allocation subfield may correspond to the negation (or logical complement) of the logical sum (or XOR operation result) of the first bit B0 of the RU allocation subfield and the bit Bx of the PS160 subfield. In addition, Fig.28B The fifth table T5 shows the bit B0 calculated from the first bit B0 of the RU allocation subfield and the bit Bx of the PS160 subfield according to the position of the main 80Mhz in the 160MHz bandwidth. Fig.28A The values ​​of the first bit X0 and the second bit X1 of the RU allocation subfield may be zero. In a bandwidth of 160 MHz, the bit Bx of the PS160 subfield may be zero. In addition, in a bandwidth of 80 MHz or less, the bit Bx of the PS160 subfield and the first bit B0 of the RU allocation subfield may be zero. Fig.28A However, it should be noted that the embodiments may also be applied to Fig.28B .

[0213] Fig.29A and Fig.29B is a diagram illustrating an RU allocation subfield according to an embodiment. Specifically, for the purpose of illustration, Fig.29A and Fig.29B represents a separate table, and Fig.29A and 29B The table represents the value of the RU allocation subfield and the single RU or multiple RUs corresponding to the value.

[0214] Reference Fig.29A , a small single RU, a small multi-RU, and a multi-RU including a 484-subcarrier RU and a 242-subcarrier RU can be included in a sub-band of 80 MHz or less. Fig.29A As shown, the first bit X0 and the second bit X1 of the RU allocation subband can define the channel position (i.e., the subband to which at least one RU is allocated). Figures 18 to 25C The described small multi-RU, and the multi-RU including a 484-subcarrier RU and a 242-subcarrier RU, the 7 bits (ie, the third to ninth bits X2 to X8) of the RU allocation subband can have the following Fig.29A The values ​​shown.

[0215] The index of the RU may be calculated based on the first bit X0 and the second bit X1. Fig.29AAs shown, the variable N may be calculated as "2*X0+X1", and the RU index may be calculated based on the variable N. For example, the index of the 26-subcarrier RU may correspond to the sum of "37*N" and the RU index of the EHT, the index of the 52-subcarrier RU may correspond to the sum of "16*N" and the RU index of the EHT, and the index of the 106-subcarrier RU may correspond to the sum of "8*N" and the RU index of the EHT. The index of the 242-subcarrier RU may correspond to the sum of "4*N" and the RU index of the EHT, the index of the 484-subcarrier RU may correspond to the sum of "2*N" and the RU index of the EHT, and the index of the 996-subcarrier RU may correspond to the sum of N and the RU index of the EHT. The index of a multi-RU including two 996-subcarrier RUs may correspond to the sum of the first bit X0 and the RU index of the EHT, the index of a multi-RU including four 996-subcarrier RUs may be 1, the index of a multi-RU including one 52-subcarrier RU and one 26-subcarrier RU may correspond to the sum of "12*N" and the RU index of the EHT, the index of a multi-RU including one 106-subcarrier RU and one 26-subcarrier RU may correspond to the sum of "8*N" and the RU index of the EHT, and the index of a multi-RU including one 484-subcarrier RU and one 242-subcarrier RU may correspond to the sum of "4*N" and the RU index of the EHT. Fig.29B , in order to define a large multi-RU, in addition to a multi-RU including a 484-subcarrier RU and a 242-subcarrier RU, the first bit X0 to the ninth bit X8 of the RU allocation subband may have the following Fig.29B The value shown. Can be calculated from the first bit X0 Fig.29B For example, the index of a multi-RU including a 996-subcarrier RU and a 484-subcarrier RU may correspond to the sum of "4*X0" and the RU index of EHT, and the index of a multi-RU including a 996-subcarrier RU, a 484-subcarrier RU and a 242-subcarrier RU may correspond to the sum of "8*X0" and the RU index of EHT. The indexes of the remaining multi-RUs may be the same as the RU index of EHT.

[0216] Will refer to later Figure 30 to Figure 34 Describes the values ​​of RU allocation subbands that define large multi-RUs (except for multi-RUs including one 484-subcarrier RU and one 242-subcarrier RU).

[0217] In some embodiments, Fig.29A and 29BOnly some of the single RU and / or multiple RUs shown in the figure may be used for multi-user (MU) transmission. For example, MU-MIMO of EHT is possible in a single RU and / or multiple RU corresponding to 242 or more subcarriers. Therefore, the AP may allocate at least one RU to multiple multiplexed STAs and may generate an RU allocation subfield for MU transmission.

[0218] In some embodiments, the RU Allocation subfield for MU transmission may have a similar structure to the RU Allocation subfield for Single User (SU) transmission. For example, the RU Allocation subfield for MU transmission may include at least 6 bits representing a decimal value, wherein the decimal value is based on Fig.29A The hatched / shaded cells and Fig.29B The values ​​of the third bit X2 to the ninth bit X8 in the cell shown increase sequentially. Therefore, the AP may set at least 6 bits of the RU allocation subfield based on the at least one RU for MU transmission, may set one bit of at least 2 bits to define one subband of two subbands included in the bandwidth, and may set two bits of at least 2 bits to define one subband of four subbands included in the bandwidth. Therefore, the RU allocation subfield for MU transmission may have a length of at least 8 bits.

[0219] The RU allocation subfield for MU transmission may be set independently of the RU allocation subfield for SU transmission. For example, the RU allocation subfield may have one of the values ​​for representing 28 single RUs (i.e., sixteen 242-subcarrier RUs, eight 484-subcarrier RUs, and four 996-subcarrier RUs). In addition, the RU allocation subfield may have one of the values ​​for indicating 67 types of multi-RUs, namely, 2 types of multi-RUs, each of which includes two 996-subcarrier RUs; 1 type of multi-RU including four 996-subcarrier RUs; 16 types of multi-RUs, each of which includes one 484-subcarrier RU and one 242-subcarrier RU; 8 types of multi-RUs, each of which includes one 996-subcarrier RU and one 484-subcarrier RU; 16 types of multi-RUs, each of which includes one 996-subcarrier RU, one 484-subcarrier RU and one 242-subcarrier RU; 12 types of multi-RUs, each of which includes two 996-subcarrier RUs and one 484-subcarrier RU; 4 types of multi-RUs, each of which includes three 996-subcarrier RUs; and 8 types of multi-RUs, each of which includes three 996-subcarrier RUs and one 484-subcarrier RU. Therefore, the RU allocation subfield for MU transmission may have one of a total of 95 values, and for this purpose, may have a length of at least 7 bits.

[0220] Fig.301 shows the value of a multi-RU including one 996-subcarrier RU and one 484-subcarrier RU and the RU allocation subfield according to an embodiment. In this case, the multi-RU including one 996-subcarrier RU and one 484-subcarrier RU may have four different combinations within a subband (e.g., 160 MHz), as described above with reference to Fig.24 Therefore, the first bit X0 of the first bit X0 and the second bit X1 of the RU allocation subfield may define a subband (e.g., 160 MHz) including multiple RUs in the 320 MHz bandwidth, and the second bit X1 may define multiple RUs together with the third bit X2 to the ninth bit X8. Specifically, Fig.30 As shown, the second bit X1 and the third bit X2 may indicate the location of an unallocated 484-subcarrier RU in a subband (eg, 160 MHz). Fig.24 and Fig.25A As described, to define multiple RUs indexed based on the location of unallocated 484-subcarrier RUs, the RU Allocation subfield may have Fig.29B and Fig.30 . Note that in this document, an "unallocated" RU may be a "punctured" RU, where the punctured frequencies of the RU are unused frequencies. Such puncturing of frequencies may be implemented to avoid interference with another AP that uses those frequencies in communication with another STA.

[0221] Fig.31 The value of a multi-RU including a 996-subcarrier RU, a 484-subcarrier RU, and a 242-subcarrier RU according to an embodiment and the RU allocation subfield are shown. Here, as described above with reference to Fig.24 As described, a multi-RU including a 996-subcarrier RU, a 484-subcarrier RU, and a 242-subcarrier RU may have eight different combinations within a subband (e.g., 160 MHz). Therefore, the first bit X0 and the second bit X1 of the RU allocation subfield may define a subband (e.g., 160 MHz) including the multi-RU in a 320 MHz bandwidth, and the second bit X1 may define the multi-RU together with the third bit X2 to the ninth bit X8. Specifically, as Fig.31 As shown, the second bit X1 to the fourth bit X3 may indicate the position of the unallocated 242-subcarrier RU in the subband (eg, 160 MHz). Fig.24 and 25B As described, to define multiple RUs indexed based on the location of unallocated 242-subcarrier RUs, the RU Allocation subfield may have Fig.29B and Fig.31(As mentioned earlier, a punctured RU is an example of an unallocated RU.)

[0222] Fig.32 The value of a multi-RU including two 996-subcarrier RUs and one 484-subcarrier RU and the RU allocation subfield according to an embodiment are shown. Fig.32 In the embodiment, a multi-RU including two 996-subcarrier RUs and one 484-subcarrier RU may have 12 different combinations within one subband (eg, 320 MHz), as described above with reference to Fig.25B Therefore, the first bit X0 and the second bit X1 of the RU allocation subfield can define multiple RUs together with the third bit X2 to the ninth bit X8. Fig.32 As shown, the first bit X0 may indicate the position of an unallocated 996-subcarrier RU in a subband (eg, 320 MHz), and the second bit X1 to the fourth bit X3 may indicate the position of an unallocated 484-subcarrier RU. Fig.25B As described, in order to define multiple RUs indexed based on the positions of unallocated 996-subcarrier RUs and 484-subcarrier RUs, the RU allocation subfield may have Fig.29B and Fig.32 The values ​​shown in .

[0223] Fig.33 The value of a multi-RU including three 996-subcarrier RUs and the RU allocation subfield according to an embodiment are shown. Fig.33 , as mentioned above Fig.25C As described, a multi-RU including three 996-subcarrier RUs may have four different combinations within a subband (i.e., 320 MHz). Therefore, the first bit X0 and the second bit X1 of the RU allocation subfield may define the multi-RU together with the third bit X2 to the ninth bit X8. Specifically, Fig.33 As shown, the first bit X0 and the second bit X1 may indicate the location of an unallocated 996-subcarrier RU in a subband (eg, 320 MHz). Fig.25C As described, to define multiple RUs indexed based on the location of unallocated 996-subcarrier RUs, the RU Allocation subfield may have Fig.29B and Fig.33 The values ​​shown in .

[0224] Fig.34 The value of a multi-RU including three 996-subcarrier RUs and one 484-subcarrier RU according to an embodiment and the RU allocation subfield are shown. In this case, as described above with reference to Fig.25CAs described, a multi-RU including three 996-subcarrier RUs and one 484-subcarrier RU may have eight different combinations within one subband (i.e., 320 MHz). Therefore, the first bit X0 and the second bit X1 of the RU allocation subfield may define the multi-RU together with the third bit X2 to the ninth bit X8. Fig.34 As shown, the first bit X0 to the third bit X2 may indicate the location of an unallocated 484-subcarrier RU in a subband (eg, 320 MHz). Fig.25C As described, to define multiple RUs indexed based on the location of unallocated 484-subcarrier RUs, the RU Allocation subfield may have Fig.29B and Fig.34 The values ​​shown in .

[0225] Fig.35 is a diagram showing the RU allocation subfield according to an embodiment. Fig.35 As shown, the RU allocation subfield may include 9 bits, for example, the first bit X0 to the ninth bit X8. Fig.28A and Fig.28B Compared to the example, Fig.35 The RU allocation subfield of the STA may include a first bit X0 for defining one of two subbands (i.e., lower 160 MHz and upper 160 MHz) in a bandwidth of 320 MHz, and may include a second bit X1 to a ninth bit X8 for defining at least one RU. Figures 18 to 25C The AP may set at least 8 bits, for example, the second bit X1 to the ninth bit X8, when the subband is 160 MHz in the bandwidth of 320 MHz, and the AP may set the first bit X0 to a value representing one of the lower 160 MHz and the upper 160 MHz.

[0226] While aspects of the inventive concept have been particularly shown and described with reference to embodiments thereof, it should be understood that various changes in form and details 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 method for communicating between a first device and at least one second device in a wireless local area network (WLAN) system, the method comprising: Allocating multiple resource units RU within the bandwidth to the at least one second device, wherein the multiple RUs include at least two single RUs; generating at least one subfield defining the multiple RUs; and sending a physical protocol layer data unit PPDU including the at least one subfield to the at least one second device, Wherein, only when each of the at least two single RUs is equal to or greater than a 242-subcarrier RU, the at least two single RUs are separated by an unallocated RU within the bandwidth.

2. The method according to claim 1, wherein: The unallocated RU is equal to or greater than 242-subcarrier RU.

3. The method according to claim 2, wherein: The unallocated RU is a 242-subcarrier RU, and The at least two RUs include a 242-subcarrier RU and a 484-subcarrier RU.

4. The method according to claim 2, wherein: The unallocated RU is a 242-subcarrier RU, and The at least two RUs include a 242-subcarrier RU, a 484-subcarrier RU and a 996-subcarrier RU.

5. The method according to claim 2, wherein: The unallocated RU is a 484-subcarrier RU, and The at least two RUs include a 484-subcarrier RU and a 996-subcarrier RU.

6. The method according to claim 2, wherein: The unallocated RU is a 484-subcarrier RU, and The at least two RUs include one 484-subcarrier RU and two 996-subcarrier RUs.

7. The method according to claim 2, wherein: The unallocated RU is a 484-subcarrier RU, and The at least two RUs include one 484-subcarrier RU and three 996-subcarrier RUs.

8. The method according to claim 2, wherein: The unallocated RU is a 996-subcarrier RU, and Wherein, the at least two RUs include three 996-subcarrier RUs.

9. The method according to claim 1, wherein: When each of the at least two single RUs is smaller than a 242-subcarrier RU, the at least two single RUs are continuously allocated within the bandwidth.

10. A first device configured to communicate with at least one second device in a wireless local area network (WLAN) system, the first device comprising: a transceiver configured to send a physical layer protocol data unit PPDU to the at least one second device, Wherein, the transceiver includes a signal processor, and the signal processor is configured to: Allocating multiple resource units RU to the second device within the bandwidth; generating at least one subfield defining the multiple RUs; generating a trigger frame including a user information field, wherein the user information field includes the at least one subfield; and generating the PPDU including the trigger frame, Wherein, the multi-RU includes at least two single RUs, wherein the signal processor is configured to: when each of at least two single RUs separated by an unallocated RU within the bandwidth is equal to or greater than a 242-subcarrier RU, allocate the multiple RUs including the at least two single RUs, and The signal processor is configured to: when each of at least two single RUs separated by unallocated RUs within the bandwidth is smaller than a 242-subcarrier RU, not allocate the multiple RUs including the at least two single RUs.

11. The first device according to claim 10, wherein: When each of the at least two single RUs is equal to or greater than a 242-subcarrier RU, the unallocated RU is equal to or greater than a 242-subcarrier RU.

12. The first device according to claim 11, wherein: The unallocated RU is a 242-subcarrier RU, and The at least two RUs include a 242-subcarrier RU and a 484-subcarrier RU.

13. The first device according to claim 11, wherein: The unallocated RU is a 242-subcarrier RU, and The at least two RUs include a 242-subcarrier RU, a 484-subcarrier RU and a 996-subcarrier RU.

14. The first device according to claim 11, wherein: The unallocated RU is a 484-subcarrier RU, and The at least two RUs include a 484-subcarrier RU and a 996-subcarrier RU.

15. The first device according to claim 11, wherein: The unallocated RU is a 484-subcarrier RU, and The at least two RUs include one 484-subcarrier RU and two 996-subcarrier RUs.

16. The first device according to claim 11, wherein: The unallocated RU is a 484-subcarrier RU, and The at least two RUs include one 484-subcarrier RU and three 996-subcarrier RUs.

17. The first device according to claim 11, wherein: The unallocated RU is a 996-subcarrier RU, and Wherein, the at least two RUs include three 996-subcarrier RUs.

18. A method for a second device to communicate with a first device in a wireless local area network (WLAN) system, the method comprising: receiving a physical protocol layer data unit PPDU including at least one subfield from a first device; as well as extracting the at least one subfield defining a multiple resource unit RU allocated to the second device within a bandwidth, wherein the multiple RUs include at least two single RUs, Among them, only when each of the at least two single RUs is equal to or greater than the 242-subcarrier RU, the at least two single RUs are separated by an unallocated RU within the bandwidth.

19. The method according to claim 18, wherein: The unallocated RU is equal to or greater than 242-subcarrier RU.

20. The method according to claim 18, wherein: When each of the at least two single RUs is smaller than a 242-subcarrier RU, the at least two single RUs are continuously allocated within the bandwidth.

21. A method for communicating between a first device and at least one second device in a wireless local area network (WLAN) system, the method comprising: Allocating multiple resource units RU within the bandwidth to the at least one second device, wherein the multiple RUs include at least two single RUs; generating at least one subfield defining the multiple RUs; and transmitting a physical protocol layer data unit PPDU including the at least one subfield to the at least one second device, wherein, when the at least two single RUs are separated by an unallocated RU within the bandwidth, each of the at least two single RUs is equal to or greater than a 242-subcarrier RU, and Wherein, when the multi-RU is smaller than 242-subcarrier RU, the at least two single RUs are continuously allocated within the bandwidth.

Images