KR20210131212A - Apparatus and method for communication based on multi-resource unit in wireless local area network system - Google Patents

Abstract

A method for a first device to communicate with at least one second device in a wireless local area network (WLAN) system may include a step of allocating at least one resource unit (RU) to the at least one second device. The step of allocating at least one RU may include the steps of: allocating a single RU or multiple RUs to the second device; and setting up to one multiplexed second device in a single RU and/or multiple RUs corresponding to less than 242 subcarriers.

Description

APPARATUS AND METHOD FOR COMMUNICATION BASED ON MULTI-RESOURCE UNIT IN WIRELESS LOCAL AREA NETWORK SYSTEM

The technical idea of the present disclosure relates to wireless communication, and more particularly, to an apparatus and method for communication based on a multi-resource unit (multi-RU) in a WLAN system.

A wireless local area network (WLAN) is a technology for connecting two or more devices to each other using a wireless signal transmission method, and the WLAN technology may be based on an Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard. The 802.11 standard has evolved into 802.11b, 802.11a, 802.11g, 802.11n, 802.11ac, and 802.11ax. can support

In 802.11ac, data may be simultaneously transmitted to multiple users through a multi-user multi-input multi-output (MU-MIMO) technique. In 802.11ax, referred to as High Efficiency (HE), not only MU-MIMO but also Orthogonal Frequency-Division Multiple Access (OFDMA) technology is applied to provide multiple access by dividing available subcarriers to users. is implementing Through this, the WLAN system to which 802.11ax is applied can effectively support communication in dense areas and outdoors.

In 802.11be, which is called Extremely High Throughput (EHT), it intends to implement 6GHz unlicensed frequency band support, bandwidth utilization of up to 320MHz per channel, Hybrid Automatic Repeat and reQuest (HARQ) introduction, and support for up to 16X16 MIMO. Through this, the next-generation WLAN system is expected to effectively support low latency and high-speed transmission like NR (New Radio), a 5G technology.

The technical idea of the present disclosure provides an apparatus and method for efficiently allocating a multi-resource unit (multi-RU) to a user in a WLAN system.

In order to achieve the above object, according to an aspect of the technical idea of the present disclosure, a method for a first device to communicate with at least one second device in a wireless local area network (WLAN) system, at least one second device Allocating at least one resource unit (RU) to a device, generating a resource unit allocation subfield defining at least one allocated resource unit, a preamble including a resource unit allocation subfield Generating a physical protocol data unit (PPDU) including a (preamble), and transmitting the PPDU to at least one second device, wherein allocating the at least one resource unit comprises: a second Allocating a single resource unit or multiple resource units to a device, and configuring up to one multiplexed second device in a single resource unit and/or multiple resource units corresponding to less than 242 subcarriers may include

According to an aspect of the inventive concept, a first device communicating with at least one second device in a WLAN system may include a transceiver for transmitting a PPDU to the at least one second device, the transceiver allocates a single resource unit (RU) or multiple resource units to the second device, generates a preamble including a resource unit allocation subfield defining at least one allocated resource unit, and generates a PPDU including the preamble and a signal processor configured to configure a maximum of one multiplexed second device in a single resource unit and/or multiple resource units corresponding to less than 242 subcarriers.

According to an aspect of the technical concept of the present disclosure, a method for a second device to communicate with a first device in a WLAN system includes: receiving a PPDU from the first device; extracting a resource unit allocation subfield from a preamble included in the PPDU and identifying the number of allocated and multiplexed devices of the resource unit based on the resource unit allocation subfield, wherein the allocation of the resource unit and identifying the number of multiplexed devices includes: 242 When only a single resource unit and/or multiple resource units corresponding to fewer subcarriers are identified, the method may include identifying at most one multiplexed device.

According to an aspect of the inventive concept, a method for a first device to communicate with at least one second device in a WLAN system includes allocating at least one resource unit (RU) to the at least one second device; generating a resource unit allocation subfield defining at least one allocated resource unit, generating a PPDU including a preamble including a resource unit allocation subfield, and transmitting the PPDU to at least one second device and/or allocating the at least one resource unit, allocating a single resource unit or multiple resource units to the second device, and a single resource unit corresponding to less than 106 subcarriers and/or It may include configuring a maximum of one multiplexed second device in a multi-resource unit.

According to an aspect of the inventive concept, a method for a first device to communicate with at least one second device in a WLAN system includes allocating a single resource unit (RU) or multiple resource units to the second device, at least Generating a resource unit allocation subfield defining at least one resource unit allocated to one second device, generating a PPDU including a preamble including a resource unit allocation subfield, and converting the PPDU to at least one and transmitting to a second device, wherein the generating of the resource unit allocation subfield comprises: a first resource unit allocation subfield transmitted through a first resource unit and a second resource unit among multiple support units, respectively; and generating a second resource unit allocation subfield, wherein each of the first resource unit allocation subfield and the second resource unit allocation subfield is allocated to at least one resource unit and multiplexed to at least one resource unit at least some of the number of second devices that have been used.

According to the method and apparatus according to an exemplary embodiment of the present disclosure, a multi-RU is efficiently provided to a user through the apparatus and method for allocating a multi-RU to a user in a WLAN system. A Physical Protocol Data Unit (PPDU) to be allocated may be configured, and thus spectral efficiency and data transmission rate in the physical layer may be improved.

Effects that can be obtained in the exemplary embodiments of the present disclosure are not limited to the above-mentioned effects, and other effects not mentioned are common knowledge in the art to which exemplary embodiments of the present disclosure pertain from the following description. It can be clearly derived and understood by those who have That is, unintended effects of carrying out the exemplary embodiments of the present disclosure may also be derived by those of ordinary skill in the art from the exemplary embodiments of the present disclosure.

1 is a diagram illustrating a wireless local area network (WLAN) system.
2 is a block diagram illustrating a wireless communication device for transmitting or receiving a PPDU.
3 is a diagram for explaining the structure of a HE SU (Single User) PPDU.
4 is a diagram for explaining the structure of an HE ER (Extended Range) SU PPDU.
5 is a diagram for explaining the structure of a HE TB (Trigger Based) PPDU.
6 is a diagram for explaining the structure of a HE MU (Multi User) PPDU.
FIG. 7 is a diagram for explaining the structure of the HE-SIG-B field of FIG. 6 .
8 is a diagram for explaining a state in which HE MU PPDUs are arranged for each frequency band.
FIG. 9 is a view for explaining the structure of the Common field of FIG. 7 .
FIG. 10 is a view for explaining an example of the User Specific field of FIG. 7 .
11 is a view for explaining another example of the User Specific field of FIG. 7 .
12 is a diagram for explaining an example of the size and location of a resource unit (RU) usable in a 20 MHz OFDMA PPDU.
13 is a diagram for explaining an example of the size and location of an RU usable in a 40 MHz OFDMA PPDU.
14 is a diagram for explaining an example of the size and location of an RU usable in an 80 MHz OFDMA PPDU.
15 is a diagram for explaining the structure of a trigger frame.
16 is a diagram for explaining the structure of an EHT TB PPDU.
17 is a diagram for explaining the structure of an EHT MU PPDU.
18 is a diagram illustrating an example in which multiple RUs are allocated to STAs in a 20 MHz OFDMA PPDU configured with small-size RUs.
19 is a diagram for explaining an example in which multiple RUs are allocated to STAs in an 80 MHz OFDMA PPDU composed of large-size RUs.
20 is a table for explaining the conventional RU batch indexing (indexing).
21 is a message diagram illustrating a method for communication based on multiple RUs according to an exemplary embodiment of the present disclosure.
22 is a flowchart illustrating a method for communication based on multiple RUs according to an exemplary embodiment of the present disclosure.
23 is a diagram illustrating examples of multiple RUs according to an exemplary embodiment of the present disclosure.
24A, 24B and 24C are diagrams illustrating RU allocation indexing according to an exemplary embodiment of the present disclosure.
25A, 25B and 25C are diagrams illustrating RU allocation indexing according to an exemplary embodiment of the present disclosure.
26A, 26B and 26C are diagrams illustrating RU allocation indexing according to an exemplary embodiment of the present disclosure.
27A, 27B and 27C are diagrams illustrating RU allocation indexing according to an exemplary embodiment of the present disclosure.
28A, 28B, 28C, and 28D are diagrams illustrating RU allocation indexing according to an exemplary embodiment of the present disclosure.
29A, 29B, 29C, and 29D are diagrams illustrating RU allocation indexing according to an exemplary embodiment of the present disclosure.
30A, 30B and 30C are diagrams illustrating RU allocation indexing according to an exemplary embodiment of the present disclosure.
31A, 31B and 31C are diagrams illustrating RU allocation indexing according to an exemplary embodiment of the present disclosure.
32 is a flowchart illustrating a method for communication based on multiple RUs according to an exemplary embodiment of the present disclosure.
33A and 33B are diagrams illustrating examples of defining an allocation of an RU based on two or more RU allocation subfields according to exemplary embodiments of the present disclosure.
34 is a block diagram illustrating a transmitter 200 according to an exemplary embodiment of the present disclosure.

Hereinafter, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings.

Advantages and features of the present disclosure, and methods for achieving them, will become apparent with reference to the embodiments described below in detail in conjunction with the accompanying drawings. However, the present disclosure is not limited to the embodiments shown below, but will be implemented in various different forms, and only the present embodiments are intended to complete the description of the present disclosure. In addition, it is provided to fully inform those of ordinary skill in the art to which the present disclosure belongs the scope of the disclosure, and the present disclosure is only defined by the scope of the claims. In addition, specific configurations described only in each embodiment of the present disclosure may be used in other embodiments. Like reference numerals refer to like elements throughout.

The terminology used herein is for the purpose of describing the embodiments and is not intended to limit the present disclosure. As used herein, the singular also includes the plural unless specifically stated otherwise in the phrase. As used herein, "comprises" and/or "comprising" refers to the presence of one or more other components, steps, operations and/or elements mentioned. or addition is not excluded.

Unless otherwise defined, all terms (including technical and scientific terms) used herein may be used with the meaning commonly understood by those of ordinary skill in the art to which this disclosure belongs. In addition, terms defined in a commonly used dictionary are not to be interpreted ideally or excessively unless clearly defined in particular.

In addition, in describing the embodiments of the present disclosure in detail, OFDM or OFDMA-based wireless communication systems, in particular, IEEE 802.11 standards will be mainly targeted, but the main subject matter of the present disclosure may be related to others having a similar technical background and channel type. of a communication system (eg, long term evolution (LTE), LTE-Advanced (LTE-A), New Radio (NR), Wireless Broadband (WiBro), Global System for Mobile Communication (GSM), such as cellular Communication systems or short-distance communication systems such as Bluetooth and NFC (Near Field Communication) can also be applied with slight modifications within a range that does not significantly depart from the scope of the present disclosure, which is a technical skill skilled in the art of the present disclosure. It will be possible with the judgment of those with knowledge.

And before proceeding with the detailed description that follows, it is desirable to set forth definitions of certain words and phrases used throughout this patent document. The word "connects" and its derivatives refer to any direct or indirect communication between two or more components, whether or not they are in physical contact with each other. The terms "transmit", "receive", and "communicate", as well as their derivatives, include both direct and indirect communication. The terms "comprise" and "comprises" and their derivatives mean inclusive without limitation. The word "or" is an inclusive word meaning 'and/or'. "relates to" and its derivatives include, is included in, interconnects with, implies, is implied in, connects to, connects to, binds to, communicates with can, cooperate with, intervene, juxtapose, approximate to, be bound by, have, have the characteristics of, have a relationship with, etc. The term "controller" means any device, system, or part thereof that controls at least one operation. Such a controller may be implemented in hardware or a combination of hardware and software and/or firmware. Functions associated with any particular controller may be centralized or distributed, either locally or remotely. The phrase "at least one" when used with a list of items means that different combinations of one or more of the listed items may be used, and that only one item in the list may be required. For example, “at least one of A, B, and C” includes any one of combinations of A, B, C, A and B, A and C, B and C, and A and B and C.

In addition, various functions described below may be implemented or supported by one or more computer programs, each of which consists of computer readable program code and is implemented in a computer readable medium. The terms "application" and "program" refer to one or more computer programs, software components, sets of instructions, procedures, functions, objects, classes, instances, related data, or portions thereof suitable for implementation of suitable computer readable program code. The term "computer readable program code" includes computer code of any type, including source code, object code, and executable code. The term "computer-readable medium" means a computer, such as read only memory (ROM), random access memory (RAM), hard disk drive, compact disk (CD), digital video disk (DVD), or any other type of memory. It includes all types of media that can be accessed by “Non-transitory” computer-readable media excludes wired, wireless, optical, or other communication links that transmit transitory electrical or other signals. Non-transitory computer readable media includes media in which data can be permanently stored, and media in which data can be stored and later overwritten, such as a rewritable optical disk or a removable memory device.

In various embodiments of the present disclosure described below, a hardware approach is described as an example. However, since various embodiments of the present disclosure include a technology using both hardware and software, the various embodiments of the present disclosure do not exclude a software-based approach.

In addition, terms that refer to control information used in the description to be described later, terms that refer to entries, terms that refer to network entities, terms that refer to messages, terms that refer to components of devices, etc. It is illustrated for convenience of description. Accordingly, the present disclosure is not limited to the terms described below, and other terms having equivalent technical meanings may be used.

1 is a diagram illustrating a wireless local area network (WLAN) system. 2 is a block diagram illustrating a wireless communication device for transmitting or receiving a PPDU.

First, as shown in FIG. 1 , the WLAN system 100 may include APs 101 and 103 (Access Points).

Specifically, the APs 101 and 103 may communicate with at least one network 130 such as the Internet, an Internet protocol (IP) network, or another data network.

In addition, the APs 101 and 103 may provide wireless access to the network 130 for a plurality of STAs 111 to 114 within the coverage areas 120 and 125 of the APs 101 and 103 . Additionally, the APs 101 and 103 may communicate with each other using wireless fidelity (WiFi) or other WLAN communication technologies. In addition, the APs 101 and 103 may communicate with the plurality of STAs 111 to 114 using wireless fidelity (WiFi) or other WLAN communication technologies. In this specification, the AP may be referred to as a first device, and the STA may be referred to as a second device, whereby the first device may communicate with at least one second device.

For reference, depending on the network type, other well-known terms such as "router" and "gateway" may be used instead of "AP" or "access point". Also, in a WLAN, an AP is provided for a radio channel. And, AP may mean STA.

Also, depending on the network type, "STA" or "station" may be referred to as "mobile station", "subscriber station", "remote terminal", "user equipment", may be used in place of other well-known terms such as “wireless terminal,” “user device,” or “user.” For convenience, the term “STA” is used herein to denote a remote wireless device that wirelessly accesses an AP or accesses a wireless channel within a WLAN. Although in this document a STA is considered a mobile device (eg, a mobile phone or smartphone), a STA may be a fixed device (eg, a desktop computer, AP, media player, fixed sensor, television, etc.).

The dashed lines show the approximate extent of the coverage areas 120 , 125 . Here, coverage areas 120 and 125 are shown as generally circular for purposes of illustration and illustration. However, the coverage areas 120 and 125 associated with the APs 101 and 103 may have different shapes reflecting various changes in the wireless environment related to natural or artificial obstructions, or Depending on the settings, it may have other shapes, including irregular shapes.

As will be described later in detail, the APs 101 and 103 include circuitry and/or a program for UL Uplink Multi-User (UL MU) or DL Downlink Multi-User (DL MU) transmission management in a WLAN system. can do.

And Figure 1 shows an example of the WLAN system 100, the embodiment of the present disclosure is not limited thereto. That is, various changes may be made in FIG. 1 .

For example, WLAN system 100 may include any number of APs and any number of STAs, any suitably deployed. Also, the AP 101 can communicate directly with any number of STAs. In addition, the AP 101 may provide a wireless broadband connection with the network 130 to the STAs 111 to 114 .

Similarly, the APs 101 and 103 may communicate directly with the network 130 , respectively, and may provide the network 130 with wireless broadband connectivity with the STAs 111 - 114 . Also, the APs 101 and 103 may implement connections with various external networks, such as external telephone networks or data networks.

Next, in FIG. 2 , a wireless communication device for transmitting or receiving a PPDU is illustrated.

For reference, the wireless communication device 1100 of FIG. 2 may be a transmitting device (eg, AP) or a receiving device (eg, STA) equipped with a transceiver capable of data communication. That is, the wireless communication device of FIG. 2 may be any one of the APs 101 and 103 and the STAs 111 to 114 shown in FIG. 1, for example, a computer, a smart phone, It may be applied to a sensor used in a portable electronic device, a tablet, a wearable device, and the Internet of Things (IoT).

However, for convenience of description, a case in which the wireless communication device 1100 is a transmitting device will be described as an example.

The wireless communication device 1100 may include a main processor 1130 , a memory 1120 , a transceiver 1140 , and antenna arrays 1101 to 1104 . In addition, 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.

Specifically, the main processor 1130 may control the memory 1120 and the transceiver 1140 . In addition, the PPDU format and multi-RU allocation information may be stored in the memory 1120 . In addition, the transceiver 1140 may generate a PPDU by using the PPDU format and multi-RU allocation information stored in the memory 1120 . Furthermore, the transceiver 1140 may transmit the generated PPDU to an external receiving device (eg, an STA) through the antenna arrays 1101 to 1104 .

Here, the memory 1120 may store the PPDU format 1121 including the multi-RU allocation signaling format according to an embodiment of the present disclosure, which will be described later. In addition, the memory 1120 may store processor-executable instructions for executing the multi-RU allocation module 1122 and the PPDU generation module 1123 . In addition, these processor-executable instructions may be executed by the main processor 1130 .

For reference, the multi-RU allocation module 1122 may use an RU allocation algorithm, method, or policy to allocate a multi-RU to a user (eg, an STA) according to an embodiment of the present disclosure. And the PPDU generation module 1123 is the control field of the PPDU (that is, also referred to as a signaling field, hereinafter referred to as a signaling field; for example, HE-SIG-A, HE-SIG-B, EHT-SIG, etc.) Signaling and indication related to multi-RU allocation may be generated.

Meanwhile, the transceiver 1140 may include a signal processor 1150 . and the signal processor 1150 may have various modules (ie, various modules of the transmit path) configured to generate each section of the PPDU or various types of communication transmission units. can

Specifically, the signal processor 1150 is a TX FIFO (1111; transmit First-In-First-Out), an encoder (1112; encoder), a scrambler (1113; scrambler), an interleaver (1114; interleaver), a constellation mapper ( 1115; with constellation mapper, for example, capable of generating QAM symbols), IDFT (1117; Inversed Discrete Fourier Transformer), with guard interval and windowing insertion module 1116; with guard interval and windowing insertion module, for example , a guard interval is put on the frequency to reduce interference on the spectrum, and the signal can be transformed through windowing).

For reference, the transceiver 1140 may include components well known to those skilled in the art as shown in the drawings. And the corresponding parts may be implemented in a manner well known to those skilled in the art, and may be implemented using hardware, firmware, software logic, or a combination thereof.

Of course, when the wireless communication device 1100 is a receiving device, the transceiver 1140 shown in FIG. 2 may also include the components in a receiving path.

That is, when the wireless communication device 1100 is a receiving device, the transceiver 1140 may receive a PPDU including a preamble and a payload from the transmitting device. In addition, the transceiver 1140 may decode the payload based on the preamble of the received PPDU. That is, the transceiver 1140 may identify the RU allocated to the receiving device by decoding the preamble of the PPDU through an internal decoder (not shown), and the payload transmitted to the receiving device based on the identified RU (ie, transmission payload received from the device).

Of course, the subject of the 'decoding operation' may be a component other than the transceiver 1140 (eg, the main processor 1130), but in the embodiment of the present disclosure, the preamble of the PPDU received by the transceiver 1140 Decoding of the payload based on .

Meanwhile, FIG. 2 only shows an example of the wireless communication device 1100, but the embodiment of the present disclosure is not limited thereto. That is, various changes may be made in FIG. 2 .

Hereinafter, an HE PPDU used in the IEEE standard (ie, 802.11ax) will be described with reference to FIGS. 3 to 15 . For reference, the HE PPDU described with reference to FIGS. 3 to 15 may be generated by the wireless communication device 1100 of FIG. 2 .

3 is a diagram for explaining the structure of an HE SU PPDU. 4 is a diagram for explaining the structure of an HE ER (Extended Range) SU PPDU. 5 is a diagram for explaining the structure of a HE TB (Trigger Based) PPDU. 6 is a diagram for explaining the structure of an HE MU PPDU. FIG. 7 is a diagram for explaining the structure of the HE-SIG-B field of FIG. 6 . 8 is a diagram for explaining a state in which HE MU PPDUs are arranged for each frequency band. FIG. 9 is a view for explaining the structure of the Common field of FIG. 7 . FIG. 10 is a view for explaining an example of the User Specific field of FIG. 7 . 11 is a view for explaining another example of the User Specific field of FIG. 7 . 12 is a diagram for explaining an example of the size and location of an RU usable in a 20 MHz OFDMA PPDU. 13 is a diagram for explaining an example of the size and location of an RU usable in a 40 MHz OFDMA PPDU. 14 is a diagram for explaining an example of the size and location of an RU usable in an 80 MHz OFDMA PPDU. 15 is a diagram for explaining the structure of a trigger frame.

3 to 6 , each HE PPDU includes a preamble including a plurality of training fields and a plurality of signaling fields, a data field, and It may include a payload including a packet extension.

Specifically, each HE PPDU is L-STF (Legacy-short training field; 8us length), L-LTF (Legacy-long training field; 8us length), L-SIG (Legacy-signal; 4us length), RL- SIG (Repeated L-SIG; 4us long), HE-SIG-A (High Efficiency-Signal-A; 8us long), HE-STF (High Efficiency-STF; 4us long), HE-LTF (High Efficiency-LTF) , DATA (ie, a data field), and PE (ie, a Packet Extension field).

Of course, the HE SU PPDU of FIG. 3 does not include HE-SIG-B, and the HE MU PPDU of FIG. 6 may further include HE-SIG-B. And, although the HE ER SU PPDU of FIG. 4 does not include HE-SIG-B, a symbol of HE-SIG-A may be repeated (16us in length). In addition, although the HE TB PPDU of FIG. 5 does not include HE-SIG-B, a symbol of HE-STF may be repeated (8us length).

Here, each field included in the preamble will be briefly described as follows.

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

The L-LTF may include a long training orthogonal frequency division multiplexing symbol (OFDM), and may be used for fine frequency/time synchronization and channel prediction.

The L-SIG may be used for transmission of control information and may include information on a data rate and a data length. For reference, the L-SIG may be repeatedly transmitted, and the format in which the L-SIG is repeated in this way is called RL-SIG.

HE-SIG-A may include control information common to the receiving device, which is as follows.

1) DL (Downlink) / UL (Uplink) indicator

2) BSS color field that is an identifier of BSS (Basic Service Set)

3) A field indicating the remaining time of the current TXOP (Transmission Opportunity) section

4) Bandwidth field indicating whether 20/40/80/160/80+80 MHz

5) Field indicating Modulation and Coding Scheme (MCS) technique applied to HE-SIG-B

6) A field indicating whether HE-SIG-B is modulated by a dual subcarrier modulation technique

7) A field indicating the number of symbols used for HE-SIG-B

8) A field indicating whether HE-SIG-B is generated over the entire band

9) Field indicating the number of symbols of HE-LTF

10) A field indicating the length of HE-LTF and the length of CP (Cyclic Prefix)

11) A field indicating whether an additional OFDM symbol exists for LDPC (Low Density Parity Check) coding

12) Field indicating control information about PE (Packet Extension)

13) A field indicating information on the CRC (Cyclical Redundancy Check) field of HE-SIG-A

HE-SIG-A may further include various information in addition to 1) to 13) described above, or may not include some information among 1) to 13). In addition, in an environment other than a multi-user (MU) environment, some information may be further added to HE-SIG-A or some information of HE-SIG-A may be omitted.

HE-SIG-B may be used in case of PPDU for MU. That is, HE-SIG-B may be omitted from the PPDU for a single user (SU). For reference, HE-SIG-A or HE-SIG-B may include RU allocation information for at least one receiving device. For more detailed information on HE-SIG-B, see FIGS. 7 to 11 below. Please refer to to explain.

Specifically, as shown in FIG. 7 , the HE-SIG-B field includes a common field including common control information and a user-specific field including user specific control information. can do.

Here, the common field can be separately encoded from the user-specific field. In addition, the common field includes RU allocation related information and a 'CRC subfield' corresponding thereto, and may be coded as one binary convolutional coding (BCC) block. And the user-specific field is one BCC block including information for decoding the payload of two users (eg, 2 STAs) and a 'CRC subfield' corresponding thereto. can be coded as

For reference, HE-SIG-B may be a duplicate of HE-SIG-B of another frequency band.

For example, referring to FIG. 8 , HE-SIG-B transmitted in some frequency band (eg, fourth frequency band 784 ) is a corresponding frequency band (ie, fourth frequency band 784 )) In addition to the data field of , control information for a data field of another frequency band (eg, the second frequency band 782 ) may be included. Accordingly, HE-SIG-B of a specific frequency band (eg, second frequency band 782 ) duplicates HE-SIG-B of another frequency band (eg, fourth frequency band 784 ). It may be in a standard format (ie, form). For this reason, HE-SIG-B may be transmitted in an encoded form for the entire RU to be transmitted.

Meanwhile, as shown in FIG. 9, the common field of HE-SIG-B includes various subfields (RU Allocation subfield, Center 26-tone RU subfield, CRC subfield, Tail subfield). may include.

Specifically, the RU Allocation subfield may consist of the number of bits of N X 8 (N is one of 1, 2, or 4). And the RU Allocation subfield may indicate the RU allocation in the frequency domain, and may indicate the number of user fields (eg, the number of STAs) in each RU. In addition, in the case of an RU having a size greater than or equal to 106-subcarrier (ie, 106-tone) supporting MU-MIMO, the number of multiplexed users may be indicated using MU-MIMO.

For reference, N=1 for 20MHz and 40MHz HE MU PPDU, N=2 for 80MHz HE MU PPDU, and N=4 for 160MHz or 80+80MHz HE MU PPDU.

On the other hand, the Center 26-tone RU subfield consists of 1 bit, and may exist to indicate whether the total bandwidth is 80 MHz, 160 MHz, and 80+80 MHz. In addition, the CRC (Cyclical redundancy check) subfield consists of 4 bits, and may be used when an error is detected with respect to common field data. In addition, the tail subfield consists of 6 bits, is used to terminate a trellis of a convolution decoder, and may be set to 0.

Subsequently, as shown in FIGS. 10 and 11 , the user-specific field of HE-SIG-B includes various subfields (STA-ID subfield, MCS subfield, Coding subfield, etc.) can do.

For reference, in the case of the user-specific field of HE-SIG-B, the subfield configuration may be changed according to whether it is a field for MU-MIMO allocation.

Specifically, in the case of FIG. 10, when the user-specific field of HE-SIG-B is not a field for MU-MIMO allocation (ie, non-MU-MIMO), HE-SIG-B User-Specific field of STA-ID subfield (B0~B10 - Consists of 11 bits), NSTS subfield (B11~B13 - Consists of 3 bits), TX Beamforming subfield (B14 - Consists of 1 bit), MCS It can include subfield (B15~B18 - composed of 4 bits), DCM subfield (B19 - composed of 1 bit), and Coding subfield (B20 - composed of 1 bit).

The STA-ID subfield may be set to the value of the TXVECTOR parameter STA_ID. In addition, the NSTS subfield may be divided into a case where the STA-ID subfield is 2046 and a case other than 2046, and may indicate the number of space-time streams. Accordingly, when the STA-ID subfield is not 2046, the NSTS subfield may be set to the number of (space-time stream - 1). On the other hand, when the STA-ID subfield is 2046, the NSTS subfield may be set to an arbitrary value.

The TX Beamforming subfield may be divided into a case in which the STA-ID subfield is 2046 and a case other than 2046, and may be used in transmit beamforming. Accordingly, if the STA-ID subfield is not 2046, the TX Beamforming subfield is 1 (that is, when a beamforming steering matrix is applied to the waveform of the SU transmission) or 0 (the otherwise) can be set. On the other hand, when the STA-ID subfield is 2046, the TX Beamforming subfield may be set to an arbitrary value.

The MCS subfield may be divided into a case where the STA-ID subfield is 2046 and a case other than 2046, and may indicate a modulation and coding scheme. Accordingly, when the STA-ID subfield is not 2046, the MCS subfield may be set to n (n=0, 1, 2, ??, 11/ 12-15 are reserved). On the other hand, when the STA-ID subfield is 2046, the MCS subfield may be set to an arbitrary value.

The DCM subfield may be divided into a case in which the STA-ID subfield is 2046 and a case other than 2046, and may indicate whether Dual Carrier Modulation (DCM) is used. Accordingly, if the STA-ID subfield is not 2046, the DCM subfield is 1 (ie, indicating that the payload of the corresponding user of the HE MU PPDU is modulated with DCM) or 0 (ie, the corresponding user of the HE MU PPDU) indicates that the payload is not modulated with DCM). On the other hand, when the STA-ID subfield is 2046, the DCM subfield may be set to an arbitrary value.

The coding subfield may be divided into a case in which the STA-ID subfield is 2046 and a case other than 2046, and may indicate whether BCC or LDPC is used. Accordingly, when the STA-ID subfield is not 2046, the Coding subfield may be set to 0 (using BCC) or 1 (using LDPC). On the other hand, when the STA-ID subfield is not 2046, the Coding subfield may be set to an arbitrary value.

On the other hand, in the case of FIG. 11, when the user-specific field of HE-SIG-B is a field for MU-MIMO allocation (ie, MU-MIMO), the user of HE-SIG-B- Specific fields (User-Specific field) include STA-ID subfield (B0~B10 - composed of 11 bits), Spatial Configuration subfield (B11 ~ B14 - composed of 4 bits), MCS subfield (B15 ~ B18 - composed of 4 bits) ), Reserved subfield (B19 - composed of 1 bit), and Coding subfield (B20 - composed of 1 bit).

The STA-ID subfield may be set to a value indicated by the TXVECTOR parameter STA_ID. In addition, the Spatial Configuration subfield may be used to indicate the number of spatial streams for a user (eg, STA) when MU-MIMO is allocated.

The MCS subfield may indicate a modulation and coding scheme. Accordingly, the MCS subfield may be set to n (n=0, 1, 2, ??, 11/ 12-15 are reserved).

The Reserved subfield is reserved to 0 and can be set. And the Coding subfield may indicate whether BCC or LDPC is used. Accordingly, the Coding subfield may be set to 0 (using BCC) or 1 (using LDPC).

Of course, even in the case of FIG. 11 , the STA-ID subfield may be divided into a case of 2046 and a case other than 2046. That is, when the STA-ID subfield is 2046, the Spatial Configuration subfield, the MCS subfield, the Reserved subfield, and the Coding subfield may all be set to arbitrary values.

As such, since the HE-SIG-B field may be configured, a more detailed description of the HE-SIG-B will be omitted.

Referring back to FIGS. 3 to 6 , the HE-STF may be used to improve automatic gain control estimation in a multiple input multiple output (MIMO) environment or an OFDMA environment.

And HE-LTF may be used to estimate a channel in a MIMO environment or an OFDMA environment.

For reference, the size of FFT (Fast Fourier Transform)/IFFT (Inverse Fast Fourier Transform) applied to fields after HE-STF and HE-STF and the size of FFT/IFFT applied to fields before HE-STF are different. can For example, the size of the FFT/IFFT applied to the HE-STF and the fields after the HE-STF may be larger than the size of the FFT/IFFT applied to the field before the HE-STF.

For this reason, the boundary plane may not exactly match the frequency band used by the field before HE-STF and the frequency band used by the field after HE-STF and HE-STF. However, for convenience of explanation, in FIGS. 3 to 6 , the frequency band used by the fields before the HE-STF and the frequency band used by the fields after the HE-STF and HE-STF will be expressed as exactly the same.

Next, each field included in the payload will be briefly described as follows.

The data field may include data for at least one user. That is, the data field may serve to carry a physical layer service data unit (PSDU) for at least one user.

In addition, in the frequency domain of the data field, at least one RU composed of a different number of tones (that is, subcarriers) may be arranged based on RU allocation information included in the signaling field of the preamble. have.

That is, as shown in FIGS. 12 to 14 , at least one RU may be disposed in the frequency domain of the data field (for reference, the horizontal axis of FIGS. 12 to 14 is the frequency domain).

First, in FIG. 12 , the arrangement of resource units (RUs) usable in a 20 MHz OFDMA PPDU is shown.

Specifically, 6 tones (ie, subcarrier) are used as a guard band in the leftmost band of the 20 MHz band, and 5 tones are used in the rightmost band of the 20 MHz band. It can be used as a guard band. In addition, 7 DC tones are inserted into the center band, that is, a direct current (DC) band, and 26-subcarrier RUs corresponding to each of 13 tones may exist on the left and right sides of the DC band. In addition, 26-subcarrier RUs, 52-subcarrier RUs, and 106-subcarrier RUs may be allocated to other bands. Each RU may be allocated for a receiving device, that is, a user.

For reference, the RU arrangement of FIG. 12 may be utilized not only in a situation for multiple users (MU) but also in a situation for a single user (SU). Accordingly, as shown at the top of FIG. 12 , a plurality of 26-subcarrier RUs may be disposed, and as shown at the bottom of FIG. 12 , one 242-subcarrier RU is disposed (in this case, 3 DC tones may be inserted into the center band).

Of course, in the example of FIG. 12 , RUs of various sizes, that is, 26-subcarrier RU, 52-subcarrier RU, 106-subcarrier RU, 242-subcarrier RU, etc. are proposed, and the specific size of these RUs is Because it can be expanded or increased, embodiments of the present disclosure are not limited to the specific size of each RU (ie, the number of corresponding tones).

Subsequently, in FIG. 13 , the arrangement of resource units (RUs) usable in a 40 MHz OFDMA PPDU is illustrated.

Specifically, 12 tones (ie, subcarrier) are used as a guard band in the leftmost band of the 40 MHz band, and 11 tones are used in the rightmost band of the 40 MHz band. It can be used as a guard band. In addition, five DC tones may be inserted into the center band, that is, a direct current (DC) band. In addition, 26-subcarrier RUs, 52-subcarrier RUs, 106-subcarrier RUs, and 242-subcarrier RUs may be allocated to other bands. Each RU may be allocated for a receiving device, that is, a user.

For reference, the RU arrangement of FIG. 13 may be utilized not only in a situation for multiple users (MU) but also in a situation for a single user (SU). Accordingly, as shown at the bottom of FIG. 13 , one 484-subcarrier RU may be disposed (in this case, 5 DC tones are inserted into the center band).

Of course, in the example of FIG. 13 , RUs of various sizes, that is, 26-subcarrier RU, 52-subcarrier RU, 106-subcarrier RU, 242-subcarrier RU, 484-subcarrier RU, etc. have been proposed, Since the specific size of these RUs can be expanded or increased, the embodiment of the present disclosure is not limited to the specific size of each RU (ie, the number of corresponding tones).

Finally, in FIG. 14 , an arrangement of resource units (RUs) usable in an 80 MHz OFDMA PPDU is shown.

Specifically, 12 tones (ie, subcarrier) are used as a guard band in the leftmost band of the 80MHz band, and 11 tones are used in the rightmost band of the 80MHz band. It can be used as a guard band. In addition, seven DC tones may be inserted into the center band, that is, a direct current (DC) band. In addition, 26-subcarrier RU, 52-subcarrier RU, 106-subcarrier RU, 242-subcarrier RU, and 484-subcarrier RU may be allocated to other bands. Each RU may be allocated for a receiving device, that is, a user.

For reference, the RU arrangement of FIG. 14 may be utilized not only in a situation for multiple users (MU), but also in a situation for a single user (SU). Accordingly, as shown in the lowermost part of FIG. 14 , one 996-subcarrier RU may be disposed (in this case, 5 DC tones are inserted into the center band).

Of course, in the example of FIG. 14 , RUs of various sizes, that is, 26-subcarrier RU (hereinafter, used in combination with RU26), 52-subcarrier RU (hereinafter, used in combination with RU52), 106-subcarrier Carrier RU (hereinafter, used interchangeably with RU106), 242-subcarrier RU (hereinafter, used interchangeably with RU242), 484-subcarrier RU (hereinafter, used interchangeably with RU484), 996-subcarrier RU (Hereinafter, used interchangeably with RU996), etc. have been proposed, since the specific size of such RU can be expanded or increased, the embodiment of the present disclosure provides the specific size of each RU (that is, the number of corresponding tones) is not limited to

For reference, the RU positions available in the 40 MHz OFDMA PPDU are equivalent to two replicas of the RU positions available in the 20 MHz OFDMA PPDU. Also, the RU positions available in the 80 MHz OFDMA PPDU are equivalent to two copies of the RU positions available in the 40 MHz OFDMA PPDU. In addition, one OFDMA PPDU may include a combination of different RU sizes in each of the RU242 boundaries.

In this way, at least one RU may be variously disposed in the frequency domain of the data field.

Referring back to FIGS. 3 to 6 , the Packet Extension (PE) has a duration of 4us, 8us, 12us or 16us, and an additional receive processing time at the end of the HE PPDU. ) can be provided.

As described above, since each field of the preamble and payload of the HE PPDU is configured, any one of the above-described HE PPDUs may be applied to the embodiment of the present disclosure.

For reference, when an uplink (UL) transmission operation by each of one or more STAs (eg, non-AP STAs) is performed in the frequency domain, the AP performs different frequencies for each of the one or more STAs based on OFDMA. Resources may be allocated as uplink transmission resources. Here, the frequency resource may mean an RU, and this frequency resource may be indicated by a trigger frame transmitted by the AP to the STA before an uplink transmission operation.

Accordingly, a trigger frame is required for transmission of the HE TB PPDU of FIG. 5 , and this trigger frame is illustrated in FIG. 15 .

Specifically, the trigger frame allocates an RU for uplink multiple-user transmission (MU) and may be transmitted from the AP to the STA. In addition, the trigger frame may be composed of a MAC frame and may be included in a PPDU.

In addition, the trigger frame may be transmitted through the PPDU shown in FIGS. 3 to 6 or may be transmitted through a PPDU specially designed for the trigger frame. For reference, when transmitted through the PPDU shown in FIGS. 3 to 6 , a trigger frame may be included in the data field.

Specifically, as shown in FIG. 15 , the trigger frame includes a frame control field 400 (2 octets), a Duration field 405 (2 octets), an RA field 410; 6 octets, and a TA. field (415; 6 octets), common information field (420; more than 8 octets), and individual user info field (425-1 to 425-N; N is a natural number greater than or equal to 1, each greater than or equal to 5 octets) ), a padding field 430 (Padding) and a frame check sequence field 435 (Frame Check Sequence (FCS), 4 octets or more).

First, the frame control field 400 includes information about the version of the MAC protocol and other additional control information, and the Duration field 405 is for setting a Network Allocation Vector (NAV). It may include information about time information or an identifier (eg, AID; Association ID) of the terminal. In addition, the RA field 410 includes address information of a receiving device (eg, STA) of the corresponding trigger frame, and may be omitted if necessary. And the TA field 415 includes address information of a device (eg, AP) that transmits the trigger frame, and the common information field 420 includes a receiving device (eg, an AP) that receives the trigger frame. For example, it may include common control information applied to the STA).

For reference, in the TA field 415, a field indicating the length of the L-SIG field of the uplink PPDU transmitted in response to the trigger frame or the SIG-A field of the uplink PPDU transmitted in response to the trigger frame Information for controlling the content of (ie, HE-SIG-A field) may be included. In addition, the TA field 415 may include, as common control information, information on the length of the CP of the uplink PPDU transmitted in response to the corresponding trigger frame or information on the length of the LTF field.

In addition, the trigger frame may include individual user information fields (425-1 to 425-N; N is a natural number greater than or equal to 1) corresponding to the number of receiving devices (eg, STAs) that receive the trigger frame. have. For reference, the individual user information field may be referred to as an “RU allocation field”. In addition, the trigger frame may include a padding field 430 (Padding) and a frame check sequence field 435 (Frame Check Sequence; FCS).

Of course, each field of the trigger frame may be partially omitted, and another field may be added. Also, the length of each field may be changed differently from that shown.

As such, various HE PPDUs are used in the IEEE standard (ie, 802.11ax), and an embodiment of the present disclosure provides a signaling field (eg, HE-SIG-A or HE-SIG-B) of the various HE PPDUs described above. ) can be implemented in

That is, an embodiment of the present disclosure relates to a method and an apparatus for supporting an MU using OFDMA, and more specifically, a transmitting device (eg, an AP) provides a plurality of receiving devices (eg, It relates to a method and apparatus for allocating multiple RUs to at least one of STAs. Accordingly, in an embodiment of the present disclosure, a method and an apparatus for configuring a signaling field indicating information on multiple RUs allocated to each receiving apparatus (eg, STA) are disclosed. However, embodiments of the present disclosure are applicable even when the STA transmits data to the STA and the STA transmits data to the AP. In addition, embodiments of the present disclosure may be applied not only to a downlink OFDMA scheme and an uplink OFDMA scheme, but also to an environment supporting a single user, such as a single user (SU) PPDU.

Furthermore, embodiments of the present disclosure may be applied to 802.11be, which is a next-generation WLAN standard. Accordingly, the multi-RU allocation method and apparatus according to an embodiment of the present disclosure may be implemented in a signaling field (eg, EHT-SIG field) of an Extremely High Throughput (EHT) PPDU. Referring to FIG. 17, an EHT PPDU used in the IEEE standard (ie, 802.11be) will be described. For reference, the EHT PPDU described in FIGS. 16 and 17 may be generated by the wireless communication device 1100 of FIG. 2 .

16 is a diagram for explaining the structure of an EHT TB PPDU. 17 is a diagram for explaining the structure of an EHT MU PPDU.

16 and 17, each EHT PPDU includes a preamble including a plurality of training fields and a plurality of signaling fields, and a data field. It may include a payload that includes.

Specifically, each EHT PPDU is L-STF (Legacy-short training field; 8us length), L-LTF (Legacy-long training field; 8us length), L-SIG (Legacy-signal; 4us length), RL- SIG (Repeated L-SIG; 4us long), U-SIG (Universal-Signal; 8us long), EHT-STF (Extremely High Throughput-STF), EHT-LTF (Extremely High Throughput-LTF), DATA (i.e. data field) can be included.

Of course, the EHT TB PPDU of FIG. 16 does not include an EHT-SIG (Extremely High Throughput-Signal), but a symbol of the EHT-STF may be repeated, and the EHT MU PPDU of FIG. 17 is a plurality of OFDM symbols Consists of, and may further include EHT-SIG. In addition, in the case of the EHT TB PPDU of FIG. 16 , a trigger frame may be required for transmission of the EHT TB PPDU, like the above-described HE TB PPDU of FIG. 5 . Of course, the trigger frame for EHT TB PPDU transmission may have a structure and function similar to the trigger frame of FIG. 15 described above.

For reference, the payload of each EHT PPDU may further include a PE (ie, a Packet Extension field), but in the embodiment of the present disclosure, for convenience of description, it is assumed that each EHT PPDU does not include a PE. listen and explain.

Meanwhile, a brief description of each field included in the EHT PPDU is as follows.

For reference, 'L-STF', 'L-LTF', 'L-SIG', and 'RL-SIG' of the EHT PPDU are 'L-STF', 'L-LTF', 'L- SIG', 'RL-SIG' is the same as or similar to the bar, detailed description thereof will be omitted.

The U-SIG is a field that performs a function similar to that of HE-SIG-A of the HE PPDU, is disposed immediately after the RL-SIG field, and may consist of two OFDM symbols that are jointly encoded.

Specifically, the U-SIG may include 'Version-independent fields' and 'Version-dependent fields', and the 'Version-dependent fields' may be disposed after the 'Version-independent fields'.

Here, 'Version-independent fields' may have static location and bit definitions over different generations/physical versions.

In addition, 'Version-independent fields' may include, for example, the following control information.

1) PHY version identifier (ie, physical version identifier; consists of 3 bits)

2) UL (Uplink)/DL (Downlink) flag (consisting of 1 bit)

3) BSS color (ie, BSS color field that is an identifier of BSS (Basic Service Set))

4) TXOP duration (that is, a field indicating the remaining time of the current TXOP (Transmission Opportunity) section)

5) Bandwidth (ie, bandwidth field; for reference, the bandwidth field may carry some puncturing information)

Meanwhile, 'Version-dependent fields' may have variable bit definitions for each physical version (PHY version).

In addition, 'Version-dependent fields' may include, for example, the following control information.

1) PPDU type (field indicating PPDU type)

2) EHT-SIG MCS (a field indicating the Modulation and Coding Scheme (MCS) technique applied to the EHT-SIG, which is a field present in the U-SIG of the EHT PPDU transmitted to the MU)

3) Number of EHT-SIG Symbols (a field indicating the number of symbols used for EHT-SIG, a field present in U-SIG of EHT PPDU transmitted to MU)

The U-SIG may further include various types of information other than the aforementioned control information, or may not include some of the aforementioned control information. In addition, in an environment other than a multi-user (MU) environment, some information may be further added to the U-SIG or some information of the U-SIG may be omitted.

The EHT-SIG is a field responsible for a function similar to that of HE-SIG-B of the HE PPDU. It is disposed immediately after the U-SIG field in the EHT PPDU transmitted to the MU (Multi-User), and has a variable MCS technique and length ( variable MCS and variable length).

Specifically, the EHT-SIG may include a common field including common control information and a user-specific field including user-specific control information.

Here, the common field can be separately encoded from the user-specific field. In addition, the common field may include RU allocation related information to be described later (that is, information composed of an 'RU Allocation subfield' and an 'Additional RU Allocation subfield' described later), and a user-specific field. ) may include information similar to information included in the user-specific field of the above-described HE-SIG-B (ie, user information allocated to each RU).

For reference, in the common field of the EHT-SIG field of the EHT PPDU transmitted to the MU, at least one compression mode in which the 'RU Allocation subfield' does not exist may exist. In addition, the EHT-SIG may be basically used in the PPDU for the MU, but unlike the 'HE PPDU', when the overhead of the U-SIG increases, it may be used in the PPDU for SU (Single User) transmission. .

As such, since the EHT-SIG field may be configured, a more detailed description of the EHT-SIG will be omitted.

In this way, various EHT PPDUs are used in the IEEE standard (ie, 802.11be), and each field of the preamble and payload of the EHT PPDU can be configured as described above. It may be implemented in a signaling field (eg, U-SIG or EHT-SIG) of .

That is, the multi-RU allocation method (ie, the signaling field configuration method for multi-RU allocation) according to the embodiment of the present disclosure can be applied to both the signaling field of the HE PPDU and the signaling field of the EHT PPDU, see the drawings below. Thus, a method for allocating multiple RUs according to an embodiment of the present disclosure will be described.

18 is a diagram illustrating an example in which multiple RUs are allocated to STAs in a 20 MHz OFDMA PPDU configured with small-size RUs. 19 is a diagram for explaining an example in which multiple RUs are allocated to STAs in an 80 MHz OFDMA PPDU composed of large-size RUs. 20 is a table for explaining conventional RU batch indexing. In some embodiments, the RU is a single RU of any one of 26-subcarrier RU, 52-subcarrier RU, 106-subcarrier RU, 242-subcarrier RU, 484-subcarrier RU, and 996-subcarrier RU. and/or 26+52-subcarrier RU (multiple RU of RU26+RU52), 52+26-subcarrier RU (multiple RU of RU52+RU26), 26+106-subcarrier RU (RU26+ Multiple RU of RU106), 106+26-subcarrier RU (multiple RU of RU106+RU26), 484+242-subcarrier RU (Multiple RU of RU484+RU242), 484+996-subcarrier RU (multiple RU of RU484+RU996) multiple RUs) and three 996-subcarrier RUs (RU996+RU996+RU996 multiple RUs).

Referring first to FIG. 20 , the first table T1 may include various assignments of single RUs and values of corresponding RU assignment subfields, and the RU assignment subfield may have a length of 8-bits. have. In addition, the first table T1 may include, in the rightmost column, the maximum number of multiplexed STAs possible in each of the allocations of single RUs. For example, in the first table T1, the RU allocation subfield corresponding to the allocation of an RU that can have up to 16 multiplexed STAs is a binary number '0100y ₁ y ₀ z _{1 corresponding to values from 96 to 111.} z ₀ ', and the number of multiplexed STAs is calculated from the lower 4 bits, that is, 'y ₁ y ₀ z ₁ z ₀ ' from Equation '2 ³ y ₁ + 2 ² y ₀ + 2z ₁ + z ₀ + 1' can be calculated. When only a single RU is allocated to a single STA, the AP may provide the STA with a signaling field defining the RU allocation, that is, an RU allocation subfield, and the STA may identify the allocation of the RU based on the RU allocation subfield. . For example, the AP may allocate the RU based on the first table T1 of FIG. 20 , and the STA may identify the RU allocation based on the first table T1 . However, as shown in FIGS. 18 and 19 , in order to share multiple RUs allocated to a single STA, an RU allocation subfield different from the RU allocation subfield defined by the first table T1 may be required.

18 and 19 , an example in which multiple RUs are allocated to an STA in a 20 MHz OFDMA PPDU composed of small-size RUs and multiple RUs in an 80 MHz OFDMA PPDU composed of large-size RUs An example in which is allocated to an STA is shown.

For reference, for efficiency of multi-RU allocation, RUs may be divided into small-size RUs and large-size RUs according to their sizes.

Here, the small size RU may be any one of 26-subcarrier RU, 52-subcarrier RU, and 106-subcarrier RU, and the large size RU may be 242-subcarrier RU, 484-subcarrier RU, and 996. - May be any one of subcarrier RUs.

Accordingly, as shown in FIG. 18 (small size RU case), STA-2 receives data from the AP by being allocated RU26+RU52 (ie, 26-subcarrier RU + 52-subcarrier RU), which is a multi-RU. STA-4 may receive data from the AP by being allocated RU52+RU26 (ie, 52-subcarrier RU + 26-subcarrier RU), which is a multi-RU. Of course, the remaining STAs (ie, STA-1, STA-3, STA-5) may receive data from the AP by being allocated one RU as in the prior art.

In addition, as shown in FIG. 19 (large size RU case), STA-2 is assigned a multi-RU RU242+RU484 (ie, 242-subcarrier RU + 484-subcarrier RU) to receive data from the AP. can Of course, the remaining STA (ie, STA-1) may receive data from the AP by being allocated one RU as in the prior art.

In this way, when the STA receives data through multiple RUs, the corresponding STA should know which multi-RU is allocated to itself through the signaling field. Accordingly, an embodiment of the present disclosure intends to propose a method for configuring a signaling field indicating information on multiple RUs allocated to an STA, which will be described in more detail with reference to the drawings below. For reference, the method of configuring the signaling field of the PPDU to be described below will be described on the assumption that it can be applied to both the HE PPDU and the EHT PPDU.

21 is a message diagram illustrating a method for communication based on multiple RUs according to an exemplary embodiment of the present disclosure. Specifically, the message diagram of FIG. 21 shows examples of operations of the AP 10 and the STA 20 communicating with each other. In some embodiments, the AP 10 may communicate with at least one STA, including the STA 20 , included in the coverage area.

Referring to FIG. 21 , in step S10 , the AP 10 may allocate at least one resource unit (RU) to at least one STA. For example, the AP 10 may allocate at least one RU to the at least one STA in order to communicate with the at least one STA including the STA 20 . For example, the AP 10 may allocate a single RU or multiple RUs corresponding to a larger number of subcarriers to an STA requiring a relatively high data throughput, while a relatively low data throughput A single RU or multiple RUs corresponding to a smaller number of subcarriers may be allocated to the required STA. An example of step S10 will be described later with reference to FIG. 22 .

In step S20, the AP 10 may generate a resource unit (RU) allocation subfield. For example, the AP 10 may generate an RU allocation subfield based on the allocation of the RU determined in step S10. In some embodiments, the AP 10 may generate an RU allocation subfield based on a table shared with the STA 20 , and the generated RU allocation subfield controls allocation of a single RU as well as allocation of multiple RUs. can be defined An example of step S20 will be described later with reference to FIG. 32 , and examples of a table shared by the AP 10 and the STA 20 will be described later with reference to FIGS. 23 to 31C .

In step S30, the AP 10 may generate a PPDU. For example, the AP 10 may generate a signaling field including the RU allocation subfield generated in step S20, and may generate a preamble including a training field and a signaling field, including a preamble and a payload. PPDU can be generated. Then, in step S40 , the AP 10 may transmit the PPDU to the STA 20 , and the STA 20 may receive the PPDU from the AP 10 .

In step S50, the STA 20 may extract a resource unit (RU) allocation subfield. For example, the STA 20 may extract a preamble from the PPDU received in step S40 and may extract an RU allocation subfield from a signaling field included in the preamble.

In step S60, the STA 20 may identify allocation of a resource unit (RU). For example, the STA 20 may identify the allocation of the RU corresponding to the RU allocation subfield extracted in step S50 based on the table shared with the AP 10 . The STA 20 may identify an assignment of a single RU as well as an assignment of multiple RUs based on the RU assignment subfield.

In step S70, the STA 20 may identify the number of multiplexed devices. For example, the STA 20 may identify the number of multiplexed STAs corresponding to the RU allocation subfield extracted in step S50 based on the table shared with the AP 10 . In some embodiments, the table shared by the STA 20 and the AP 10 is the maximum number (eg, the EHT MU PPDU) that the number of multiplexed STAs can support due to the limited length of the RU allocation subfield. 16) can be limited to a smaller number.

22 is a flowchart illustrating a method for communication based on multiple RUs according to an exemplary embodiment of the present disclosure. Specifically, the flowchart of FIG. 22 shows an example of step S10 of FIG. 21 . As described above with reference to FIG. 21 , an operation of allocating at least one RU to at least one STA may be performed in step S10 ′ of FIG. 22 . As shown in FIG. 22, step S10' may include steps S12, S14 and S16, and FIG. 22 will be described below with reference to FIG.

Referring to FIG. 22 , at least one STA to transmit data may be identified in step S12. As described above with reference to FIG. 1 , the AP 10 may communicate with at least one STA including the STA 20 and may identify the STA to transmit data to.

In step S14, STAs to which a single resource unit (single RU) or a multi-resource unit (multi-RU) will be commonly allocated may be grouped. For example, the AP 10 may determine whether to allocate each of the at least one STA identified in step S12 to a single resource unit or to a multi-resource unit. The AP 10 may determine at least one STA commonly allocated to the same single resource unit, and may group the determined at least one STA into one group. Also, the AP 10 may determine at least one STA that is commonly allocated to the same multi-resource unit, and may group the determined at least one STA into one group. In this specification, the group to which the STAs grouped in step S12 belong may be referred to as an STA group.

In step S16, a single resource unit or multiple resource units may be allocated to at least one STA. For example, the AP 10 may determine a single resource unit or multiple resource units to be allocated to the grouped group, that is, the STA group in step S14. Accordingly, each of the at least one STA identified in step S12 may be allocated to a single resource unit or multiple resource units allocated to the STA group to which it belongs.

23 is a diagram illustrating examples of multiple RUs according to an exemplary embodiment of the present disclosure. Specifically, the second table T2 of FIG. 23 visually indicates assignments of multiple RUs defined in the EHT.

Referring to FIG. 23 , in the second table T2, RU26+RU52 (including RU52+RU26) and RU26+RU106 (including RU106+RU26) may be defined as small size multiple RUs. Also, in the second table T2, RU484+RU242 (including RU242+RU484), RU242+RU484 (including RU484+RU242), RU484+RU996 (including RU996+RU484), 2xRU996+RU484 (including RU484+2xRU996), 3xRU996+RU484 (including RU484+3xRU996) and 3xRU996 may be defined as large-size multiple RUs. For communication based on multiple RUs, the table shared by the AP 10 and the STA 20 of FIG. 21 includes not only the assignments of a single RU defined in the first table T1 of FIG. It may be required to define assignments of multiple RUs defined in table T2. Hereinafter, various examples of a table defining assignments of multiple RUs will be described with reference to the drawings.

24A, 24B and 24C are diagrams illustrating RU allocation indexing according to an exemplary embodiment of the present disclosure. Specifically, FIGS. 24A, 24B and 24C show a third table T3 defining assignments of an RU and containing values of an RU assignment subfield respectively corresponding to assignments of the RU, the third table T3 ) are shown separately in FIGS. 24A, 24B and 24C for illustration. 24A, 24B and 24C, the RU allocation subfield may have a length of 8-bits. In the following, FIGS. 24A, 24B and 24C will be described with reference to FIG. 21 .

In some embodiments, the number of multiplexed STAs may be limited according to the size of the allocated RU in order to define the allocation of a single RU and the allocation of multiple RUs through the RU allocation subfield of limited length. For example, as shown in FIG. 24A , the third table T3 may define a maximum of one multiplexed STA in single RUs and multiple RUs corresponding to less than 106 subcarriers, and the AP (10) may configure up to one multiplexed STA in single RUs and multiple RUs corresponding to less than 106 subcarriers. Accordingly, as in the ratio shown in FIGS. 24A and 24B , assignments of RUs including only RU26, RU52 and/or RU26+RU52 (including RU52+RU26) may have at most one multiplexed STA.

The third table T3 may define up to 4 multiplexed STAs in single RUs and multiple RUs corresponding to 106 or more and less than 242 subcarriers, and the AP 10 has 106 or more and 242 subcarriers. Up to four multiplexed STAs may be configured in single RUs and multiple RUs corresponding to less than subcarriers. Accordingly, as shown in FIGS. 24A and 24B , the allocation of an RU including one of RU106 and RU106+RU26 (including RU26+RU106) may have a maximum of 4 multiplexed STAs, and RU106 and RU106+RU26 The RU allocation subfield may have one of 16 different values to indicate the allocation of an RU containing two of (including RU26+RU106).

The third table T3 may define up to 8 multiplexed STAs in single RUs and multiple RUs corresponding to 242 or more and less than 996 subcarriers, and the AP 10 has 242 or more and 996 subcarriers. Up to 8 multiplexed STAs may be configured in single RUs and multiple RUs corresponding to less than subcarriers. Accordingly, as shown in FIG. 24C , the allocation of the RU including the RU242 may have a maximum of 8 multiplexed STAs. In addition, as will be described later with reference to FIG. 33A , the number of multiplexed STAs may be defined in a separate RU allocation subfield, and thus single RUs and multiple corresponding to 242 or more and less than 996 subcarriers. Up to 8 multiplexed STAs may be defined in RUs.

The third table T3 may define up to 16 multiplexed STAs in single RUs and multiple RUs corresponding to 996 or more subcarriers, and the AP 10 corresponds to 996 or more subcarriers. Up to 16 multiplexed STAs can be configured in single RUs and multiple RUs. As will be described below with reference to FIG. 33A , the number of multiplexed STAs may be defined in a separate RU allocation subfield, and thus a maximum of 16 in single RUs and multiple RUs corresponding to 996 or more subcarriers. Multiplexed STAs may be defined.

25A, 25B and 25C are diagrams illustrating RU allocation indexing according to an exemplary embodiment of the present disclosure. Specifically, FIGS. 25A, 25B and 25C show a fourth table T4 that defines assignments of an RU and includes values of an RU assignment subfield respectively corresponding to assignments of the RU, the fourth table T4 are shown separately in FIGS. 25A, 25B and 25C for illustration. 25A, 25B and 25C, the RU allocation subfield may have a length of 8-bits. Hereinafter, FIGS. 25A, 25B and 25C will be described with reference to FIG. 21 .

In some embodiments, in order to define the allocation of a single RU and the allocation of multiple RUs by the RU allocation subfield of limited length, the number of multiplexed STAs may be limited according to the size of the allocated RU. For example, as shown in FIGS. 25A, 25B and 25C , the fourth table T4 provides single RUs corresponding to less than 242 subcarriers and up to one multiplexed STA in multiple RUs. may be defined, and the AP 10 may configure up to one multiplexed STA in single RUs and multiple RUs corresponding to less than 242 subcarriers. Accordingly, as shown in FIGS. 25A, 25B and 25C, allocation of RUs including only RU26, RU52, RU106, RU26+RU52 (including RU52+26) and/or RU26+RU106 (including RU106+RU26) They may have up to one multiplexed STA.

Referring to the fourth table T4, when the AP 10 allocates RU26+RU52 to the STA 20, among 7 different values (eg, 29, 30, 31, 32, 37, 49, 51) One value may be selected, and an RU allocation subfield having the selected value may be generated. When the AP 10 allocates RU52+RU26 to the STA 20, the AP 10 may select one of seven different values (eg, 33, 34, 35, 36, 38, 50, 51), and the selected value It is possible to create an RU allocation subfield having . When the AP 10 allocates RU106+RU26 to the STA 20 , the AP 10 may select one of six different values (eg, 39, 40, 41, 42, 43, 50), and has the selected value. An RU allocation subfield may be created. When the AP 10 allocates RU26+RU106 to the STA 20, the AP 10 may select one of six different values (eg, 44, 45, 46, 47, 48, 49), and has the selected value. An RU allocation subfield may be created.

The fourth table T4 may define up to 8 multiplexed STAs in single RUs and multiple RUs corresponding to 242 or more subcarriers, and the AP 10 corresponds to 242 or more subcarriers. Up to 8 multiplexed STAs can be configured in single RUs and multiple RUs. For example, as shown in FIGS. 25A, 25B and 25C , RU242, RU484, RU996, RU484+RU242 (including RU242+RU484), RU484+RU969 (including RU969+RU484) and/or 3xRU969 Allocations of an RU may have up to 8 multiplexed STAs.

Referring to the fourth table T4, when the AP 10 allocates RU484 + RU242 (including RU242 + RU484) to the STA 20, the arrangement of RU484 + RU242 (including RU242 + RU484) and the multiplexed STAs One of 32 different values (eg, from 80 to 111) may be selected based on the number, and an RU allocation subfield having the selected value may be generated. When the AP 10 allocates RU484+RU969 (including RU969+RU484) to the STA 20, based on the arrangement of RU484+RU969 (including RU969+RU484) and the number of multiplexed STAs, 32 different values (eg, , 112 to 143) may be selected, and an RU allocation subfield having the selected value may be generated. When the AP 10 allocates three RU969s to the STA 20 , the AP 10 selects one of 32 different values (eg, from 144 to 175) based on the arrangement of the three RU969s and the number of multiplexed STAs. and may generate an RU allocation subfield having the selected value.

26A, 26B and 26C are diagrams illustrating RU allocation indexing according to an exemplary embodiment of the present disclosure. Specifically, FIGS. 26A, 26B and 26C show a fifth table T5 that defines assignments of an RU and includes values of an RU assignment subfield respectively corresponding to assignments of the RU, the fifth table T5 are shown separately in FIGS. 26A, 26B and 26C for illustration. 26A, 26B and 26C, the RU allocation subfield may have a length of 9-bits. In the following, FIGS. 26A, 26B and 26C will be described with reference to FIG. 21 .

In some embodiments, in order to define the allocation of a single RU and the allocation of multiple RUs by the RU allocation subfield of limited length, the number of multiplexed STAs may be limited according to the size of the allocated RU. For example, as shown in FIGS. 26A, 26B and 26C , the fifth table T5 provides single RUs corresponding to less than 106 subcarriers and up to one multiplexed STA in multiple RUs. may be defined, and the AP 10 may configure up to one multiplexed STA in single RUs and multiple RUs corresponding to less than 106 subcarriers. Accordingly, as shown in FIGS. 26A, 26B and 26C , assignments of RUs including only RU26, RU52 and/or RU26+RU52 (including RU52+RU26) may have at most one multiplexed STA.

The fifth table T5 may define a maximum of 4 or a maximum of 8 multiplexed STAs in single RUs and multiple RUs corresponding to 106 or more and less than 242 subcarriers, and the AP 10 is 106 A maximum of 4 or a maximum of 8 multiplexed STAs may be configured in single RUs and multiple RUs corresponding to more than 242 subcarriers. Accordingly, as shown in FIGS. 26A, 26B and 26C, the allocation of an RU including one of RU106 and RU106+RU26 (including RU26+RU106) can have a maximum of 4 or a maximum of 8 multiplexed STAs. And, the allocation of an RU including two RU106 can have a maximum of 16 multiplexed STAs, and an allocation of an RU including RU106 and RU106 + RU26 (including RU26 + RU106) can have a maximum of 64 multiplexed STAs. have.

The fifth table T5 may define a maximum of 16 multiplexed STAs in single RUs and multiple RUs corresponding to 242 or more subcarriers, and the AP 10 corresponds to 242 or more subcarriers. Up to 16 multiplexed STAs can be configured in single RUs and multiple RUs. Accordingly, as shown in FIGS. 26A, 26B and 26C , the allocation of an RU including the RU242 may have a maximum of 16 multiplexed STAs. Further, in some embodiments, as described below with reference to FIG. 33A , the number of multiplexed STAs may be defined in a separate RU allocation subfield, and thus single RUs corresponding to 242 or more subcarriers. and up to 16 multiplexed STAs may be defined in multiple RUs.

27A, 27B and 27C are diagrams illustrating RU allocation indexing according to an exemplary embodiment of the present disclosure. Specifically, FIGS. 27A, 27B and 27C show a sixth table T6 that defines assignments of an RU and includes values of an RU assignment subfield corresponding to assignments of the RU, respectively, and the sixth table T6 are shown separately in FIGS. 27A, 27B and 27C for illustration. 27A, 27B and 27C, the RU allocation subfield may have a length of 8-bits. In the following, FIGS. 27A, 27B and 27C will be described with reference to FIG. 21 .

In some embodiments, a table defining all assignments of multiple RUs defined in the EHT may be used. For example, when compared with the above-described third table T3, fourth table T4, and fifth table T5, the sixth table T6 is a multiple defined in the second table T2 of FIG. All assignments of RUs can be defined. Accordingly, as shown in FIG. 27C , the AP 10 may allocate two RU996s to the STA 20 with reference to the sixth table T6, and the two RU996s and RU484 may be allocated, three RU996s and RU484 may be allocated to the STA 20 , and three RU996s may be allocated to the STA 20 . In addition, as shown in FIGS. 27A, 27B and 27C, the sixth table T6 can define up to 8 multiplexed STAs in single RUs and multiple RUs corresponding to 242 or more subcarriers. and the AP 10 may configure up to 8 multiplexed STAs in a single RU and/or multiple RUs corresponding to 242 or more subcarriers.

28A, 28B, 28C, and 28D are diagrams illustrating RU allocation indexing according to an exemplary embodiment of the present disclosure. Specifically, FIGS. 28A, 28B and 27C show a seventh table T7 defining assignments of an RU and including values of an RU assignment subfield corresponding to assignments of the RU, respectively, the seventh table T7 is shown separately in FIGS. 28A, 28B, 28C and 28D for illustration. 28A, 28B, 28C and 28D, the RU allocation subfield may have a length of 9-bits. In the following, FIGS. 28A, 28B, 28C and 28D will be described with reference to FIG. 21 .

In some embodiments, a table defining assignments of multiple RUs defined in the EHT as well as assignments of additional multiple RUs may be used. For example, compared to the sixth table T6 described above, the seventh table T7 may define assignments of an RU comprising multiple RUs consisting of a central RU26 and an adjacent RU52, thus RU26+RU52 (including RU52+RU26) may be allocated more uniformly. The AP 10 may allocate multiple RUs composed of a center RU26 and an adjacent RU52 to the STA 20 with reference to the seventh table T7, and the STA 20 is due to the center RU26, which is a DC-tone of the entire bandwidth. Thus, it is possible to more easily process a signal received through the corresponding multi-RU. Accordingly, as shown in FIG. 28B , the seventh table T7 may define 20 allocations of a RU including multiple RUs including the central RU26, and the RU allocation subfield is one of 29 to 48. may indicate one of the 20 assignments of the RU as a value of . In addition, as shown in FIGS. 28A, 28B, 28C and 28D , the seventh table T7 includes single RUs corresponding to 242 or more subcarriers and up to 8 multiplexed STAs in multiple RUs. may be defined, and the AP 10 may configure up to 8 multiplexed STAs in a single RU and/or multiple RUs corresponding to 242 or more subcarriers.

29A, 29B, 29C, and 29D are diagrams illustrating RU allocation indexing according to an exemplary embodiment of the present disclosure. Specifically, FIGS. 29A, 29B and 29C show an eighth table T8 that defines assignments of an RU and includes values of an RU assignment subfield respectively corresponding to assignments of the RU, the eighth table T8 is shown separately in FIGS. 29A, 29B, 29C and 29D for illustration. 29A, 29B, 29C and 29D, the RU allocation subfield may have a length of 8-bits. In the following, FIGS. 29A, 29B, 29C and 29D will be described with reference to FIG. 21 .

The eighth table T8, similar to the seventh table T7 described above, can define assignments of RUs comprising multiple RUs consisting of a central RU26 and an adjacent RU52, while a 9-bit number of RU allocation sub Different from the seventh table T7 defining fields, an 8-bit number of RU allocation subfields may be defined. In order to define up to 8 multiplexed STAs in single RUs and multiple RUs corresponding to 242 or more subcarriers as in the seventh table T7, the number of multiplexed STAs as described below with reference to FIG. 33B may be defined by two or more RU allocation subfields.

30A, 30B and 30C are diagrams illustrating RU allocation indexing according to an exemplary embodiment of the present disclosure. Specifically, FIGS. 30A, 30B and 30C show a ninth table T9 that defines assignments of an RU and includes values of an RU assignment subfield respectively corresponding to assignments of the RU, and the ninth table T9 is shown separately in FIGS. 30A, 30B and 30C for illustration. 30A, 30B, and 30C, the RU allocation subfield may have a length of 7-bits. Hereinafter, FIGS. 30A, 30B and 30C will be described with reference to FIG. 21 .

The ninth table T9 may define assignments of a RU comprising multiple RUs consisting of a center RU26 and an adjacent RU52, similar to the seventh table T7 and eighth table T8 described above, while 9 - A RU allocation subfield with a 7-bit number shorter than the number of bits or 8-bits may be defined. As shown in FIG. 30C , the ninth table T9 may define up to 8 multiplexed STAs in single RUs and multiple RUs corresponding to 242 or more subcarriers, and the AP 10 is Up to 8 multiplexed STAs may be configured in single RUs and multiple RUs corresponding to 242 or more subcarriers. In order to define up to 8 multiplexed STAs using a 7-bit number of RU allocation subfields, as described below with reference to FIG. 33A , the number of multiplexed STAs may be defined in a separate RU allocation subfield and , thus, up to 8 multiplexed STAs may be defined in single RUs and multiple RUs corresponding to 242 or more subcarriers.

31A, 31B and 31C are diagrams illustrating RU allocation indexing according to an exemplary embodiment of the present disclosure. Specifically, FIGS. 31A, 31B and 31C show a tenth table T10 that defines assignments of an RU and includes values of an RU assignment subfield respectively corresponding to assignments of the RU, the tenth table T10 is shown separately in FIGS. 31A, 31B and 31C for illustration. 31A, 31B and 31C, the RU allocation subfield may have a length of 8-bits. Hereinafter, FIGS. 31A, 31B and 31C will be described with reference to FIG. 21 .

The tenth table T10 may define up to eight multiplexed STAs in single RUs and multiple RUs corresponding to 242 or more subcarriers, similarly to the seventh table T7 described above, while Different from the 7 table T7, as RU26+RU52 (including RU52+RU26), only multiple RUs composed of the center RU26 and the adjacent RU52 may be defined, and an 8-bit number of RU allocation subfields may be defined. Accordingly, the AP 10 may allocate only RU26+RU52 (including RU52+RU26) including the central RU26 to the STA 20, and to a single RU and/or multiple RUs corresponding to 242 or more subcarriers. Up to 8 multiplexed STAs can be configured.

32 is a flowchart illustrating a method for communication based on multiple RUs according to an exemplary embodiment of the present disclosure. Specifically, the flowchart of FIG. 32 shows an example of step S20 of FIG. 21 . As described above with reference to FIG. 21 , the RU allocation subfield may be generated in step S20' of FIG. 32 . As shown in FIG. 32 , step S20' may include steps S22 and S24, and FIG. 32 will be described below with reference to FIG. 21 .

Referring to FIG. 32 , a first resource unit allocation subfield transmitted through a first resource unit may be generated in step S22, and a second resource unit allocation subfield transmitted through a second resource unit may be generated in step S24 can be According to HE and EHT, information on RU allocation may be signaled for each subchannel of 20 MHz, and the AP 10 may provide an RU allocation subfield for each subchannel of 20 MHz to the STA 20 . For example, RU484 as a single RU may correspond to two RU allocation subfields, and RU484+RU242 as multiple RUs may correspond to three RU allocation subfields. Accordingly, the AP 10 sets two or more RU allocation subfields corresponding to a single RU or multiple RUs, such as a first RU, in order to provide the STA 20 with more diverse RU assignments and more multiplexed STAs. An allocation subfield and a second RU allocation subfield may be generated. For example, each of the first RU allocation subfield and the second RU allocation subfield may define at least a portion of the allocation of at least one RU and the number of STAs multiplexed to the at least one RU. The STA 20 may identify the allocation of the RU by combining the first RU allocation subfield and the second RU allocation subfield. Accordingly, various allocations of the RU and various numbers of multiplexed STAs may be shared by the AP 10 and the STA 20 without extending the length (ie, the number of bits) of the RU allocation subfield. Examples of the operation of generating the first RU allocation subfield and the second RU allocation subfield to define the RU allocation will be described below with reference to FIGS. 33A and 33B .

33A and 33B are diagrams illustrating examples of defining an allocation of an RU based on two or more RU allocation subfields according to exemplary embodiments of the present disclosure. Specifically, FIGS. 33A and 33B show an example in which RU242, RU242, and RU484 are sequentially allocated, and the first RU242 and RU484 are commonly allocated to the first STA group (STA-1) as multiple RUs. As described above with reference to FIG. 22 , the STA group may refer to a group of STAs to which a single resource unit or multiple resource units are commonly allocated, and may include one STA or a plurality of multiplexed STAs. 33A and 33B , the first STA group STA-1 may include multiplexed STAs commonly allocated to multiple resource units (ie, RU242+RU484). Hereinafter, the operation of the STA belonging to the first STA group STA-1 will be simply described as the operation of the first STA group STA-1, and overlapping descriptions of FIGS. 33A and 33B will be omitted. will be

Referring to FIG. 33A , the first STA group STA-1 includes a first RU allocation subfield F1a corresponding to RU242, a second RU allocation subfield F2a corresponding to RU484, and a third RU allocation subfield corresponding to RU484. (F3a) can be received. In some embodiments, the RU allocation subfield may be signaled for each subchannel corresponding to 20 MHz, and accordingly, the AP may determine that when a single resource unit or multiple resource unit allocated to an STA group has a width greater than 20 MHz (ie, If it is greater than RU242), two or more RU allocation subfields may be generated, and the RU allocation for the STA group may be defined through a combination of two or more RU allocation subfields. For example, as shown in FIG. 33A , the AP may generate a first RU allocation subfield F1a defining an allocation of an RU comprising at least one RU (eg, a single RU and/or multiple RUs). and may generate a second RU allocation subfield F2a defining the number of STAs popularized in at least one RU. When the AP generates an 8-bit number of RU allocation subfields with reference to the above-described third table T3, the AP generates 203, that is, a first RU allocation subfield F1a having a binary number '11001011'. and may generate a second RU allocation subfield (F2a) having a binary number '00001100' representing 13 multiplexed STAs (2 ³ +2 ² +1=13≤16), 217, that is, 2 A third RU allocation subfield F3a having the decimal number '11011001' may be generated. In addition, when the AP generates a 9-bit number of RU allocation subfields with reference to the above-described fifth table T5, the AP 419, that is, the first RU allocation subfield F1a having a binary number '110100011' Can generate a second RU allocation subfield (F2a) having a binary number '000001100' indicating 13 multiplexed STAs (2 ³ +2 ² +1=13≤16), 433, That is, a third RU allocation subfield F3a having a binary number '110110001' may be generated. In addition, when the AP generates a 7-bit number of RU allocation subfields with reference to the ninth table T9, the AP is 84, that is, the first RU allocation subfield F1a having a binary number '1010100'. Can generate a second RU allocation subfield (F2a) having a binary number '0000110' indicating 7 multiplexed STAs (2 ² +2+1=7≤8), 107, that is, A third RU allocation subfield F3a having a binary number '1101011' may be generated.

Referring to FIG. 33B , the first STA group STA-1 includes a first RU allocation subfield F1b corresponding to RU242, a second RU allocation subfield F2b corresponding to RU484, and a third RU allocation subfield corresponding to RU484. (F3b) can be received. In some embodiments, each of the first RU allocation subfield F1b and the second RU allocation subfield F2b includes bits defining an allocation of at least one RU and a multiplexed STA allocated to the at least one RU It may include bits defining part of the number of . For example, as shown in FIG. 33B , the first RU allocation subfield F1b includes six bits 'a5a4a3a2a1a0' including a Most Significant Bit (MSB) and two bits including a Least Significant Bit (LSB). It may include bits 'y11y10'. In addition, the second RU allocation subfield F2b may include the same 6 bits 'a5a4a3a2a1a0' as the first RU allocation subfield F1b, while 2 bits 'y21y20' including the LSB may include The RU allocation may be defined by upper 6 bits 'a5a4a3a2a1a0' commonly included in the first RU allocation subfield F1b and the second RU allocation subfield F2b. In addition, the number of multiplexed STAs may be defined by the lower two bits 'y11y10' of the first RU allocation subfield F1b and the lower two bits 'y21y20' of the second RU allocation subfield F2b. As shown in FIG. 33B , the number of multiplexed STAs ^{may be calculated by '2 3} y11 + 2 ² y10 + 2y21 + y20 + 1'. For example, when the AP generates an 8-bit number of RU allocation subfields with reference to the above-mentioned eighth table T8, the AP may generate '011000' as 6 high-order bits 'a5a4a3a2a1a0' and , 2 '0110' may be generated as 'y11y10y21y20' to define 7 multiplexed STAs (2 ² +2+1=7≤8). Accordingly, the AP may generate a first RU allocation subfield F1b having a binary number '01100001', and may generate a second RU allocation subfield F2b having a binary number '01100010', 176 That is, a third RU allocation subfield F3b having a binary number '101100000' may be generated.

34 is a block diagram illustrating a transmitter 200 according to an exemplary embodiment of the present disclosure. Specifically, the block diagram of FIG. 34 shows the transmitter 200 for multi-user MIMO (MU-MIMO) transmission, proposed in the 802.11 standard specification. In some embodiments, each of the blocks included in the transmitter 200 is a component that provides a fixed function, such as a program executed by a programmable component, an intellectual property (IP) core, or the like. and a reconfigurable component such as a field programmable gate array (FPGA). In FIG. 34, N may correspond to the total number of users.

Referring to FIG. 34, the transmitter 200 includes a pre-FEC (fast Ethernet controller) PHY padding block 201, a scrambler 202, a low density parity check code (LDPC) encoder 203, a post-FEC PHY padding block ( 204), stream parser 205, N _SS constellation mappers 206, N _SS LDPC tone mappers 207, (N _SS -1) CSD (cyclic shift diversity) ) blocks 208 , a spatial frequency mapping block 209 , N _TX inverse discrete Fourier transform (IDFT) blocks 210 , N _TX guard interval (GI) insertion and windowing blocks 211 and N _TX analog and radio frequency (RF) blocks 212 . Here, N _SS and N _TX may correspond to the number of spatial streams and the number of transmission chains, respectively.

A pre-forward error correction code (FEC) PHY padding block 201 , a scrambler 202 , a low-density parity check code (LDPC) encoder 203 and a post-FEC PHY padding block 204 form the PSDU into an encoded sequence of data bits. can be converted to The stream parser 205 may rearrange the sequence of encoded data bits into N _SS data blocks, and one data block may correspond to a specific spatial stream. Each of the N _SS constellation mappers 206 may map the encoded and interleaved bits in the data block to modulation constellation points. Each of N _SS LDPC tone mappers 207 may drive LDPC on modulation constellation points, and (N _SS −1) CSD blocks 208 are cyclic, except for the first spatial stream. A cyclic shift can be inserted.

Spatial frequency mapping block 209 maps _{modulation constellation points of N SS} spatial streams for the first user and modulation constellation points of N _SS spatial streams _{for the Nth user to N TX} transmit chains. can do. In some embodiments, the spatial frequency mapping block 209 may allocate the RU to the first user and/or the Nth user as defined by the RU allocation subfield, as described above with reference to the figures. . Each of the N _TX IDFT blocks 210 may transform a modulation constellation point in a transmit chain into a plurality of time domain OFDM symbols, and each of the N _TX GI insertion and windowing blocks 211 is an OFDM symbol. A circular extension may be added at the beginning of the symbol, and the edges of the OFDM symbol may be smoothed to increase spectral decay. Each of the N _TX analog and RF blocks 212 may convert a plurality of time domain OFDM symbols into an analog signal transmitted through at least one antenna.

Exemplary embodiments have been disclosed in the drawings and specification as described above. Although the embodiments have been described using specific terms in the present specification, these are used only for the purpose of explaining the technical spirit of the present disclosure and are not used to limit the meaning or the scope of the present disclosure described in the claims. . Therefore, it will be understood by those skilled in the art that various modifications and equivalent other embodiments are possible therefrom. Accordingly, the true technical protection scope of the present disclosure should be defined by the technical spirit of the appended claims.

Claims (20)

A method for a first device to communicate with at least one second device in a wireless local area network (WLAN) system, the method comprising:
allocating at least one resource unit (RU) to the at least one second device;
generating a resource unit allocation subfield defining the allocated at least one resource unit;
generating a physical protocol data unit (PPDU) including a preamble including the resource unit allocation subfield; and
transmitting the PPDU to the at least one second device;
Allocating the at least one resource unit comprises:
allocating a single resource unit or multiple resource units to a second device; and
A method comprising the step of configuring at most one multiplexed second device in a single resource unit and/or multiple resource units corresponding to less than 242 subcarriers. The method according to claim 1,
Allocating the at least one resource unit may further include configuring up to 8 multiplexed second devices in a single resource unit and/or multiple resource units corresponding to 242 or more subcarriers. Way. The method according to claim 1,
The single resource unit corresponds to one of 26-subcarrier resource unit, 52-subcarrier resource unit, 106-subcarrier resource unit, 242-subcarrier resource unit, 484-subcarrier resource unit, and 996-subcarrier resource unit,
The multi-resource unit is 26+52-subcarrier resource unit, 52+26-subcarrier resource unit, 106+26-subcarrier resource unit, 26+106-subcarrier resource unit, 484+242-subcarrier resource unit, 484+996- A method, characterized in that it corresponds to a subcarrier resource unit and one of three 996-subcarrier support units. The method according to claim 1,
Allocating the single resource unit or multiple resource units includes allocating 26+52-subcarrier resource units to a second device,
The generating of the resource unit allocation subfield comprises selecting one of seven different values based on other allocated resource units in response to the 26+52-subcarrier resource unit. how to do it The method according to claim 1,
Allocating the single resource unit or multiple resource units includes allocating 52+26-subcarrier resource units to a second device,
The generating of the resource unit allocation subfield includes selecting one of seven different values based on other allocated resource units in response to the 52+26-subcarrier resource unit. how to do it The method according to claim 1,
Allocating the single resource unit or multiple resource units includes allocating 106+26-subcarrier resource units to a second device,
The generating of the resource unit allocation subfield comprises selecting one of six different values based on other allocated resource units in response to the 106+26-subcarrier resource unit. how to do it The method according to claim 1,
Allocating the single resource unit or multiple resource units includes allocating 26+106-subcarrier resource units to a second device,
The generating of the resource unit allocation subfield includes selecting one of six different values based on other allocated resource units in response to the 26+106-subcarrier resource unit. how to do it The method according to claim 1,
Allocating the single resource unit or multiple resource units includes allocating 484-subcarrier resource units and 242-subcarrier resource units to a second device,
The generating of the resource unit allocation subfield includes the arrangement of the 484-subcarrier resource unit and the 242-subcarrier resource unit and the number of multiplexed second devices in response to the 484-subcarrier resource unit and the 242-subcarrier resource unit. and selecting one of the 32 different values based on The method according to claim 1,
Allocating the single resource unit or multiple resource units includes allocating 484-subcarrier resource units and 996-subcarrier resource units to a second device,
The generating of the resource unit allocation subfield includes the arrangement of the 484-subcarrier resource unit and the 996-subcarrier resource unit and the number of multiplexed second devices in response to the 484-subcarrier resource unit and the 996-subcarrier resource unit. and selecting one of the 32 different values based on The method according to claim 1,
Allocating the single resource unit or multiple resource units includes allocating three 996-subcarrier resource units to a second device,
The generating of the resource unit allocation subfield may include, in response to the three 996-subcarrier resource units, 32 different values based on the arrangement of the three 996-subcarrier resource units and the number of multiplexed second devices. and selecting one of the values. The method according to claim 1,
Allocating the single resource unit or multiple resource units comprises:
allocating two 996-subcarrier resource units to a second device;
allocating two 996-subcarrier resources and a 484-subcarrier resource to a second device;
allocating three 996-subcarrier resources and a 484-subcarrier resource to a second device; and
allocating three 996-subcarrier resources to the second device. 12. The method of claim 11,
Allocating the single resource unit or multiple resource units comprises:
and allocating a central 26-carrier resource unit and a 52-carrier resource unit adjacent to the central 26-carrier resource unit to a second device. 13. The method of claim 12,
Allocating the at least one resource unit may further include configuring up to 8 multiplexed second devices in a single resource unit and/or multiple resource units corresponding to 242 or more subcarriers. Way. 13. The method of claim 12,
Allocating the at least one resource unit, characterized in that it further comprises the step of setting up to four multiplexed second devices in a single resource unit and/or multiple resource units corresponding to 484 or more subcarriers. Way. 13. The method of claim 12,
Allocating the at least one resource unit further comprises configuring up to 8 multiplexed second devices in a single resource unit and/or multiple resource units corresponding to 242 or more subcarriers,
The step of generating the resource unit allocation subfield comprises:
generating a first resource unit allocation subfield defining allocation of the at least one resource unit; and
and generating a second resource unit allocation subfield defining the number of second devices multiplexed to the at least one resource unit. 13. The method of claim 12,
26+52-subcarrier resource unit and 52+26-subcarrier resource unit among the allocated multiple resource units include the central 26-carrier resource unit. A first device configured to communicate with at least one second device in a wireless local area network (WLAN) system, comprising:
a transceiver configured to transmit a physical protocol data unit (PPDU) to the at least one second device;
The transceiver allocates a single resource unit (RU) or multiple resource units to the second device, and includes a resource unit allocation subfield defining at least one allocated resource unit. A preamble including a subfield. and a signal processor, configured to generate the PPDU and generate the PPDU including the preamble;
The first device, characterized in that the signal processor is configured to configure at most one multiplexed second device in a single resource unit and/or multiple resource units corresponding to less than 242 subcarriers. 18. The method of claim 17,
The signal processor is configured to configure a maximum of 8 multiplexed second devices in a single resource unit and/or multiple resource units corresponding to 242 or more subcarriers. A method for a second device to communicate with a first device in a wireless local area network (WLAN) system, comprising:
receiving a physical protocol data unit (PPDU) from the first device;
extracting a resource unit allocation subfield from a preamble included in the PPDU; and
based on the resource unit allocation subfield, identifying a resource unit allocation and the number of multiplexed devices;
The allocation of the resource unit and the step of identifying the number of multiplexed devices, when only a single resource unit and/or multiple resource units corresponding to less than 242 subcarriers are identified, identifying at most one multiplexed device A method comprising the steps of. 20. The method of claim 19,
The step of allocating the resource unit and identifying the number of multiplexed devices includes: when a single resource unit and/or multiple resource units corresponding to 242 or more subcarriers are identified, identifying up to 8 multiplexed devices A method comprising:

Images